EP4292252A1 - Profils d'entité physique d'une unité radio - Google Patents

Profils d'entité physique d'une unité radio

Info

Publication number
EP4292252A1
EP4292252A1 EP22710919.6A EP22710919A EP4292252A1 EP 4292252 A1 EP4292252 A1 EP 4292252A1 EP 22710919 A EP22710919 A EP 22710919A EP 4292252 A1 EP4292252 A1 EP 4292252A1
Authority
EP
European Patent Office
Prior art keywords
phy
indication
profile
profiles
candidate
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
EP22710919.6A
Other languages
German (de)
English (en)
Inventor
Andrei Dragos Radulescu
Fatih Ulupinar
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 US17/650,486 external-priority patent/US20220255688A1/en
Application filed by Qualcomm Inc filed Critical Qualcomm Inc
Publication of EP4292252A1 publication Critical patent/EP4292252A1/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/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H04W88/085—Access point devices with remote components

Definitions

  • aspects of the present disclosure generally relate to wireless communication and to techniques and apparatuses for physical entity profiles of a radio unit.
  • 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).
  • multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency-division multiple access (FDMA) systems, orthogonal frequency-division multiple access (OFDMA) systems, single-carrier frequency-division multiple access (SC- FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and Long Term Evolution (LTE).
  • LTE/LTE- Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).
  • UMTS Universal Mobile Telecommunications System
  • a wireless network may include a number of base stations (BSs) that can support communication for a number of user equipment (UEs).
  • UE may communicate with a BS via the downlink and uplink.
  • Downlink (or “forward link”) refers to the communication link from the BS to the UE
  • uplink (or “reverse link”) refers to the communication link from the UE to the BS.
  • a BS may be referred to as a Node B, a gNB, an access point (AP), a radio head, a transmit receive point (TRP), a New Radio (NR) BS, a 5G Node B, or the like.
  • NR which may also be referred to as 5G
  • 5G is a set of enhancements to the UTE 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 (DF), using CP- OFDM and/or SC-FDM (e.g., also known as discrete Fourier transform spread OFDM (DFT-s- OFDM)) on the uplink (UF), as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.
  • OFDM orthogonal frequency division multiplexing
  • CP-OFDM with a cyclic prefix
  • SC-FDM e.g., also known as discrete Fourier transform spread OFDM (DFT-s- OFDM)
  • MIMO multiple-input multiple-output
  • a method of wireless communication performed by a base station includes providing, by a radio unit (RU) of the base station and to a distributed unit (DU) of the base station, an indication of one or more candidate physical entity (PHY) profdes; and receiving, by the RU and from the DU, an indication of a selected PHY profde, of the one or more candidate PHY profdes, to use for communication with a device.
  • RU radio unit
  • DU distributed unit
  • PHY physical entity
  • a base station for wireless communication includes a memory; and one or more processors coupled to the memory, the one or more processors configured to: provide, to a DU of the base station, an indication of one or more candidate PHY profiles; and receive, from the DU, an indication of a selected PHY profile, of the one or more candidate PHY profiles, to use for communication with a device.
  • a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a base station, cause the base station to: provide, to a DU of the base station, an indication of one or more candidate PHY profiles; and receive, from the DU, an indication of a selected PHY profile, of the one or more candidate PHY profiles, to use for communication with a device.
  • an apparatus for wireless communication includes means for providing, to a DU of the apparatus, an indication of one or more candidate PHY profiles; and means for receiving, from the DU, an indication of a selected PHY profile, of the one or more candidate PHY profiles, to use for communication with a device.
  • aspects are described in the present disclosure by illustration to some examples, those skilled in the art will understand that such aspects may be implemented in many different arrangements and scenarios.
  • Techniques described herein may be implemented using different platform types, devices, systems, shapes, sizes, and/or packaging arrangements.
  • some 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, or artificial intelligence-enabled devices).
  • Aspects may be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, 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 a number of components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processor(s), interleavers, adders, or summers).
  • RF radio frequency
  • Aspects described herein may be practiced in a wide variety of devices, components, systems, distributed arrangements, 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 base station in communication with a user equipment (UE) in a wireless network, in accordance with the present disclosure.
  • UE user equipment
  • FIG. 3 is a diagram illustrating an example of entities of a base station, in accordance with the present disclosure.
  • Fig. 4 is a diagram illustrating an example associated with mapping of physical entity profdes to front end unit profdes via baseband ports, in accordance with the present disclosure.
  • Figs. 5 and 6 are diagrams illustrating examples associated with physical entity profdes of a radio unit, in accordance with the present disclosure.
  • Fig. 7 is a diagram illustrating an example process associated with physical entity profdes of a radio unit, in accordance with the present disclosure.
  • FIG. 8 is a block diagram of an example apparatus for wireless communication, in accordance with the present disclosure.
  • 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 (NR) network and/or an LTE network, among other examples.
  • the wireless network 100 may include a number of base stations 110 (shown as BS 110a, BS 110b, BS 110c, and BS 1 lOd) and other network entities.
  • a base station (BS) is an entity that communicates with user equipment (UEs) and may also be referred to as an NR BS, a Node B, a gNB, a 5G node B (NB), an access point, a transmit receive point (TRP), or the like.
  • Each BS may provide communication coverage for a particular geographic area.
  • the term “cell” can refer to a coverage area of a BS and/or a BS subsystem serving this coverage area, depending on the context in which the term is used.
  • a BS 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 with service subscription.
  • a pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscription.
  • a femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs having association with the femto cell (e.g., UEs in a closed subscriber group (CSG)).
  • CSG closed subscriber group
  • a BS for a macro cell may be referred to as a macro BS.
  • a BS for a pico cell may be referred to as a pico BS.
  • a BS for a femto cell may be referred to as a femto BS or a home BS.
  • a BS 110a may be a macro BS for a macro cell 102a
  • a BS 110b may be a pico BS for a pico cell 102b
  • a BS 110c may be a femto BS for a femto cell 102c.
  • a BS may support one or multiple (e.g., three) cells.
  • the terms “eNB”, “base station”, “NR BS”, “gNB”, “TRP”, “AP”, “node B”, “5G NB”, and “cell” may be used interchangeably herein.
  • a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a mobile BS.
  • the BSs may be interconnected to one another and/or to one or more other BSs or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces, such as a direct physical connection or a virtual network, using any suitable transport network.
  • Wireless network 100 may also include relay stations.
  • a relay station is an entity that can receive a transmission of data from an upstream station (e.g., a BS or a UE) and send a transmission of the data to a downstream station (e.g., a UE or a BS).
  • a relay station may also be a UE that can relay transmissions for other UEs.
  • a relay BS 1 lOd may communicate with macro BS 110a and a UE 120d in order to facilitate communication between BS 110a and UE 120d.
  • a relay BS may also be referred to as a relay station, a relay base station, a relay, or the like.
  • Wireless network 100 may be a heterogeneous network that includes BSs of different types, such as macro BSs, pico BSs, femto BSs, relay BSs, or the like. These different types of BSs may have different transmit power levels, different coverage areas, and different impacts on interference in wireless network 100.
  • macro BSs may have a high transmit power level (e.g., 5 to 40 watts) whereas pico BSs, femto BSs, and relay BSs may have lower transmit power levels (e.g., 0.1 to 2 watts).
  • a network controller 130 may couple to a set of BSs and may provide coordination and control for these BSs.
  • Network controller 130 may communicate with the BSs via a backhaul.
  • the BSs may also communicate with one another, directly or indirectly, via a wireless or wireline backhaul.
  • UEs 120 may be dispersed throughout wireless network 100, and each UE may be stationary or mobile.
  • a UE may also be referred to as an access terminal, a terminal, a mobile station, a subscriber unit, a station, or the like.
  • a UE 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 or equipment, biometric sensors/devices, wearable devices (smart watches, smart clothing, smart glasses, smart wrist bands, smart jewelry (e.g., smart ring, smart bracelet)), an entertainment device (e.g., a music or video device, or a satellite radio), a vehicular component or sensor, smart meters/sensors, industrial manufacturing equipment, a global positioning system device, or any other suitable device that is configured to communicate via a wireless or wired medium.
  • a cellular phone e.g., a smart phone
  • PDA personal digital assistant
  • WLL wireless local loop
  • Some UEs may be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs.
  • MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, and/or location tags, that may communicate with abase station, another device (e.g., remote device), or some other entity.
  • a wireless node may provide, for example, connectivity for or to a network (e.g., a wide area network such as Internet or a cellular network) via a wired or wireless communication link.
  • Some UEs may be considered Intemet-of-Things (IoT) devices, and/or may be implemented as NB-IoT (narrowband internet of things) devices. Some UEs may be considered a Customer Premises Equipment (CPE).
  • UE 120 may be included inside a housing that houses components of 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
  • the processor components e.g., one or more processors
  • the memory components e.g., a memory
  • any number of wireless networks may be deployed in a given geographic area.
  • Each wireless network may support a particular RAT and may operate on one or more frequencies.
  • a RAT may also be referred to as a radio technology, an air interface, or the like.
  • a frequency may also 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 may communicate directly using one or more sidelink channels (e.g., without using a base station 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 or a vehicle-to-infrastructure (V2I) protocol), and/or a mesh network.
  • P2P peer-to-peer
  • D2D device-to-device
  • V2X vehicle-to-everything
  • V2V vehicle-to-everything
  • Devices of wireless network 100 may communicate using the electromagnetic spectrum, which may be subdivided based on frequency or wavelength into various classes, bands, channels, or the like. For example, devices of wireless network 100 may communicate using an operating band having a first frequency range (FR1), which may span from 410 MHz to 7.125 GHz, and/or may communicate using an operating band having a second frequency range (FR2), which may span from 24.25 GHz to 52.6 GHz.
  • FR1 first frequency range
  • FR2 second frequency range
  • the frequencies between FR1 and FR2 are sometimes referred to as mid-band frequencies.
  • FR1 is often referred to as a “sub-6 GHz” band.
  • FR2 is often referred to as a “millimeter wave” band 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
  • millimeter wave may broadly represent frequencies within the EHF band, frequencies within FR2, and/or mid-band frequencies (e.g., less than 24.25 GHz). It is contemplated that the frequencies included in FR1 and FR2 may be modified, and techniques described herein are applicable to those modified frequency ranges.
  • Fig. 1 is provided as an example. Other examples may differ from what is described with regard to Fig. 1.
  • Fig. 2 is a diagram illustrating an example 200 of a base station 110 in communication with a UE 120 in a wireless network 100, in accordance with the present disclosure.
  • Base station 110 may be equipped with T antennas 234a through 234t
  • UE 120 may be equipped with R antennas 252a through 252r, where in general T > 1 and R > 1.
  • a transmit processor 220 may receive data from a data source 212 for one or more UEs, select one or more modulation and coding schemes (MCS) for each UE based at least in part on channel quality indicators (CQIs) received from the UE, process (e.g., encode and modulate) the data for each UE based at least in part on the MCS(s) selected for the UE, and provide data symbols for all UEs. Transmit processor 220 may also 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.
  • MCS modulation and coding schemes
  • Transmit processor 220 may also 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)).
  • a transmit (TX) multiple-input multiple -output (MIMO) processor 230 may perform 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 T output symbol streams to T modulators (MODs) 232a through 232t. Each modulator 232 may process a respective output symbol stream (e.g., for OFDM) to obtain an output sample stream.
  • TX transmit
  • MIMO multiple-input multiple -output
  • Each modulator 232 may process a respective output symbol stream (e.g., for OFDM) to obtain an output sample stream.
  • Each modulator 232 may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal.
  • T downlink signals from modulators 232a through 232t may be transmitted via T antennas 234a through 234t, respectively.
  • antennas 252a through 252r may receive the downlink signals from base station 110 and/or other base stations and may provide received signals to demodulators (DEMODs) 254a through 254r, respectively.
  • Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) a received signal to obtain input samples.
  • Each demodulator 254 may further process the input samples (e.g., for OFDM) to obtain received symbols.
  • a MIMO detector 256 may obtain received symbols from all R demodulators 254a through 254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols.
  • a receive processor 258 may process (e.g., demodulate and decode) the detected symbols, provide decoded data for UE 120 to a data sink 260, and 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
  • RSSQ reference signal received quality
  • CQI parameter CQI parameter
  • Network controller 130 may include communication unit 294, controller/processor 290, and memory 292.
  • Network controller 130 may include, for example, one or more devices in a core network.
  • Network controller 130 may communicate with base station 110 via communication unit 294.
  • Antennas may include, or may be included within, one or more antenna panels, antenna groups, sets of antenna elements, and/or antenna arrays, among other examples.
  • An antenna panel, an antenna group, a set of antenna elements, and/or an antenna array may include one or more antenna elements.
  • An antenna panel, an antenna group, a set of antenna elements, and/or an antenna array may include a set of coplanar antenna elements and/or a set of non-coplanar antenna elements.
  • An antenna panel, an antenna group, a set of antenna elements, and/or an antenna array may include antenna elements within a single housing and/or antenna elements within multiple housings.
  • An antenna panel, an antenna group, a set of antenna elements, and/or an antenna array may include 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 controller/processor 280. Transmit processor 264 may also generate reference symbols for one or more reference signals. The symbols from transmit processor 264 may be precoded by a TX MIMO processor 266 if applicable, further processed by modulators 254a through 254r (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to base station 110.
  • a modulator and a demodulator e.g., MOD/DEMOD 254
  • the UE 120 includes a transceiver.
  • the transceiver may include any combination of antenna(s) 252, modulators and/or demodulators 254, MIMO detector 256, receive processor 258, transmit processor 264, and/or TX MIMO processor 266.
  • the transceiver may be used by a processor (e.g., controller/processor 280) and memory 282 to perform aspects of any of the methods described herein (for example, as described with reference to Figs. 5-8).
  • the uplink signals from UE 120 and other UEs may be received by antennas 234, processed by demodulators 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 UE 120.
  • Receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to controller/processor 240.
  • Base station 110 may include communication unit 244 and communicate to network controller 130 via communication unit 244.
  • Base station 110 may include a scheduler 246 to schedule UEs 120 for downlink and/or uplink communications.
  • a modulator and a demodulator (e.g., MOD/DEMOD 232) of the base station 110 may be included in a modem of the base station 110.
  • the base station 110 includes a transceiver.
  • the transceiver may include any combination of antenna(s) 234, modulators and/or demodulators 232, MIMO detector 236, receive processor 238, transmit processor 220, and/or TX MIMO processor 230.
  • the transceiver may be used by a processor (e.g., controller/processor 240) and memory 242 to perform aspects of any of the methods described herein (for example, as described with reference to Figs. 5-8).
  • Controller/processor 240 of base station 110, controller/processor 280 of UE 120, and/or any other component(s) of Fig. 2 may perform one or more techniques associated with PHY profdes of a radio unit, as described in more detail elsewhere herein.
  • controller/processor 240 of base station 110, controller/processor 280 of UE 120, and/or any other com pone nt(s) of Fig. 2 may perform or direct operations of, for example, process 700 of Fig. 7 and/or other processes as described herein.
  • Memories 242 and 282 may store data and program codes for base station 110 and UE 120, respectively.
  • memory 242 and/or memory 282 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 base station 110 and/or the UE 120, may cause the one or more processors, the UE 120, and/or the base station 110 to perform or direct operations of, for example, process 700 of Fig. 7 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.
  • the base station includes means for providing, by an RU of the base station and to a DU of the base station, an indication of one or more candidate PHY profiles; or means for receiving, by the RU and from the DU, an indication of a selected PHY profile, of the one or more candidate PHY profiles, to use for communication with a device.
  • the means for the base station to perform operations described herein may include, for example, one or more of transmit processor 220, TX MIMO processor 230, modulator 232, antenna 234, demodulator 232, MIMO detector 236, receive processor 238, controller/processor 240, memory 242, or scheduler 246.
  • the base station includes means for providing, by the RU and to the DU, an indication that the selected PHY profile is incompatible with a selected front end unit (FEU) profile.
  • the base station includes means for providing, by the RU and to the DU, an indication of one or more recommended PHY profiles, of the one or more candidate PHY profiles, or means for providing, by the RU and to the DU, an indication of one or more recommended FEU profiles that are compatible with the selected PHY profile.
  • the base station includes means for providing, by the RU and to the DU, an indication of one or more compatible pairs of PHY profiles and FEU profiles that match an intended FEU profile.
  • the base station includes means for providing a mapping of FEU profiles to compatible PHY profiles.
  • the base station includes means for receiving, by the RU and from the DU, an indication of a set of parameters for selection of one or more of a candidate PHY profile or a candidate FEU profile; or means for providing, by the RU and to the DU, an indication of one or more recommended PHY profiles, of the one or more candidate PHY profiles, or one or more recommended FEU profiles based at least in part on the set of parameters, wherein reception of the indication of the selected PHY profile is based at least in part on the indication of the one or more recommended PHY profiles.
  • the base station includes means for providing a set of PHY profiles that satisfy the set of parameters, means for providing a set of PHY profiles that satisfy a subset of the set of parameters, or an indication that the set of parameters is rejected.
  • the base station includes means for receiving, by the RU and from the DU, a request for partition subset capabilities; or means for providing, by the RU and to the DU, an indication of partition subset capabilities.
  • the base station includes means for providing an indication of a dependency of the partition subset capabilities on a selection of a PHY profile or a FEU profile.
  • blocks in Fig. 2 are illustrated as distinct components, 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 controller/processor 280.
  • Fig. 2 is provided as an example. Other examples may differ from what is described with regard to Fig. 2.
  • Fig. 3 is a diagram illustrating an example 300 of entities of a base station, in accordance with the present disclosure.
  • a base station 110 may communicate with another base station 110 using, for example, an Xn interface.
  • the base station 110 and/or the other base station 110 may communicate with an access and mobility management function (AMF) entity and/or a user plane function (UPF) entity using, for example, a next generation (NG) interface.
  • AMF access and mobility management function
  • UPF user plane function
  • the AMF and/or the UPF may include, or may be included in, one or more computing devices, such as a server device, a base station, and/or a mobility management entity.
  • the base station 110 may include a centralized unit 305 and/or one or more distributed units 310.
  • the centralized unit 305 may manage communications via multiple distributed units 310.
  • the one or more distributed units 310 may be in different geographical locations.
  • the one or more distributed units 310 may include multiple TRPs associated with a single cell or multiple TRPs associated with multiple cells, among other examples.
  • Each of the one or more distributed units 310 may be referred to as a base station that communicates (e.g., control information or data, among other examples) with a common centralized unit 305.
  • the one or more distributed units 310 may communicate with the centralized unit 305 via a fronthaul network and/or a fronthaul interface.
  • the distributed unit 310 may include one or more layer 2 and layer 3 (L2/L3) entities 315.
  • the L2/L3 entities 315 may include a radio resources control layer entity 320, a packet data convergence protocol (PDCP) layer entity 325, a radio link control (RLC) layer entity 330, MAC layer entity 335, and/or a control layer entity 340 (e.g., including a radio resource management (RRM) entity and/or a self-organizing networks (SON) entity), among other examples.
  • PDCP packet data convergence protocol
  • RLC radio link control
  • MAC layer entity 335 e.g., a radio link control entity 340
  • RRM radio resource management
  • SON self-organizing networks
  • the L2/L3 entities 315 may manage communications with one or more devices, such as UEs, via the base station 110. For example, L2/L3 entities 315 may read different portions of a data packet received from a UE, may direct the data packet based at least in part on the different portions of the data packet, may determine a communication parameter based at least in part on the different portions of the data packet, and/or may generate a communication for the UE based at least in part on the different portions of the data packet, among other examples. [0059] As shown in Fig. 3, the distributed unit 310 may include an interface for communication between the MAC layer entity 335 and a physical (PHY) layer entity 350.
  • PHY physical
  • the interface may include a functional application platform interface (FAPI) 345.
  • the base station 110 e.g., the distributed unit 310) may use the FAPI 345 to provide control information and/or data between the MAC layer entity 335 and the PHY layer entity 350.
  • the MAC layer entity 335 and the PHY layer entity 350 may communicate via the FAPI 345 in a split-6 configuration.
  • a split-6 configuration may include the distributed unit 310 that is split into a first functional unit that includes the L2/L3 entities 315 including the MAC layer entity 335 and a second functional unit that includes the PHY layer entity 350 and an FEU 355.
  • the FAPI 345 may include a control plane sub-interface for communicating control information between the MAC layer entity 335 and the PHY layer entity 350.
  • the control plane sub-interface may be used to communicate in a stateful communication format.
  • the FAPI 345 may include a data sub-interface for communicating data between the MAC layer entity 335 and the PHY layer entity 350.
  • the data sub-interface may be stateless during some or all communications.
  • the MAC layer entity 335 may configure, for each slot, a PHY channel and/or transport blocks for the PHY channel to use to transmit and/or receive data from one or more UEs.
  • the FEU 355 may receive one or more radio frequency (RF) signals (e.g., via one or more antenna groups).
  • the FEU 355 may perform one or more operations on the RF signals, such as such as an analog to digital conversion and/or one or more digital front end operations, among other examples.
  • the PHY layer entity 350 may receive one or more encoded data packets from the FEU 355 and may decode the one or more data packets before providing a decoded payload to the MAC layer entity 335 via the FAPI 345.
  • the L2/L3 entities 315 may interpret the decoded payload to control one or more communications with the UE and/or to direct the decoded payload to another device (e.g., a device that includes the AMF and/or the UPF).
  • the PHY layer entity 350 may receive, via the FAPI 345, a payload for transmission to the UE
  • the PHY layer entity 350 may encode the payload, may perform beamforming (e.g., digital beamforming), and/or perform one or more baseband operations on the payload in preparation for transmitting.
  • the PHY layer entity 350 may include one or more baseband components that perform the digital beamforming.
  • the PHY layer entity 350 may provide the payload, after performing one or more operations on the payload, to the FEU 355 via one or more baseband ports.
  • the one or more baseband ports may be connected to one or more physical entity partition subsets that provide the payload.
  • the FEU 355 may perform one or more operations (e.g., using one or more devices), such as a digital to analog conversion, analog beamforming, and/or one or more digital front end operations, among other examples to transmit the payload using a radio frequency (e.g., over the air) transmission.
  • the FEU 355 may include one or more digital front end (DFE) entities that receive the payload from the PHY layer entity 350.
  • the one or more DFE entities may perform one or more operations, such as combining payloads from narrowbands (e.g., via narrowband chains) into a wideband payload (e.g., via a wideband chain).
  • the one or more DFE entities may provide the wideband payload to a digital-to -analog converter (DAC) for providing to an RF entity.
  • DAC digital-to -analog converter
  • the RF entity may perform one or more operations on the wideband payload and transmit the wideband payload.
  • the FEU 355 and the PHY layer entity 350 may be separate devices or may be included in a single device. Additionally, or alternatively, the L2/L3 entities 315 may be included in one or more devices that are separate from (e.g., located in one or more different geographical locations from) the PHY layer entity 350 and/or the FEU 355. [0065] As indicated above, 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 illustrating an example 400 associated with mapping of a PHY entity 405 to FEU profdes via baseband ports, in accordance with the present disclosure.
  • the PHY entity 405 and an FEU may be included in an RU of a base station.
  • the PHY entity 405 of the RU may perform one or more operations, such as digital beamforming or baseband processing, among other examples.
  • the PHY entity 405 may provide a payload, via baseband ports 410, to the FEU.
  • the FEU may include multiple candidate FEU profiles, such as a first FEU profile 415 and a second FEU profile 420.
  • the first FEU profile 415 may be connected to multiple baseband ports.
  • the first FEU profile 415 may receive multiple signals via multiple narrowband chains, combine the multiple signals (e.g., using a combiner), and process the combined multiple signals via a wideband chain.
  • the first FEU profile 415 may be configured to output the combined multiple signals to an RF unit for transmission to another device.
  • the second FEU profile 420 may receive multiple signals via multiple narrowband chains, combine the multiple signals, and process the combined multiple signals via multiple wideband chains.
  • the second FEU profile 420 may be configured to output the combined multiple signals to one or more RF units for transmission to one or more other devices.
  • Each narrowband chain of the FEU profiles may be associated with a different component carrier (e.g., a different cell) and/or each wideband chain of the FEU profiles may be associated with a different stream and/or with a different beam direction.
  • An FEU profile may indicate how many narrowband chains are connected per wideband chain.
  • An FEU profile may indicate mapping from the wideband chains to RF units of the RU and/or from the narrowband chains to the wideband chains.
  • Fig. 4 is provided as an example. Other examples may differ from what is described with regard to Fig. 4.
  • a FAPI may provide an interface to indicate control information from a DU (e.g., L2/L3 entities) to a PHY entity and/or an FEU.
  • a DU e.g., L2/L3 entities
  • the DU may indicate a selection of an FEU profile to use for communication with one or more UEs.
  • the DU may indicate a selection of an FEU profile without consideration of whether the FEU profile is compatible with the PHY entity.
  • baseband port labels for communications between the DU and the FEU may be unique and/or hardcoded.
  • the labeling may also include a direction (e.g., downlink or uplink) for the port.
  • a control message may indicate a baseband port with a label that is understood by the DU and the FEU.
  • logical baseband ports for communication between the DU and the PHY entity may not have explicit labels and/or may not have unique and/or hardcoded labels outside of the context of a PHY entity’s, or a PHY partition’s, context.
  • the DU may indicate logical baseband ports implicitly with labels that are understood by the PHY entity, or an instance of the PHY entity.
  • the DU may not understand compatibility between indications of logical baseband port labels of the PHY entity and FEU profiles. This may cause an error, for example, if the PHY entity outputs signals to one or more baseband ports that do not correspond with intended input ports of the FEU. Based at least in part on the error, the base station may not transmit the signals to an intended UE, may receive an indication from the UE of a failure to receive the signals, and may consume power, network, communication, and/or computing resources to attempt to transmit again, or may operate outside of acceptable parameters.
  • an RU of a base station may transmit, to a DU of the base station, an indication of one or more candidate PHY profiles for selection by the DU.
  • the RU may receive, from the DU, an indication of a selected PHY profile, of the one or more candidate PHY profiles, to use for communication with a device, such as a UE.
  • the RU may provide a PHY profile identification, (e.g., a 16 bit profile identification), a number of PHY partition subsets supported, and/or one or more parameters for each PHY partition subset.
  • the PHY entity may be partitioned over a set of uniquely labeled baseband ports at an interface between a set of PHYs (e.g., PHY partition subsets) and a set of FEU components.
  • the parameters may include a PHY partition subset identification, such as a PHY ID, a number of local baseband ports connected to the PHY partition subset, and/or a mapping of local baseband port identifications with baseband port identifications known to an FEU; as an example, the mapping can be via global baseband port identifiers that are unambiguous for the DU and RU configuration.
  • the partition subsets may be non-overlapping.
  • the RU may provide information to the DU to avoid, or correct, selection of a PHY profile that is incompatible with a selected FEU profile (e.g., a DFE profile or including a DFE profile).
  • the RU may provide information to the DU to avoid selection of a PHY profile that would result in pairing the PHY profile with an FEU profile that would result in open ports (e.g., not all baseband ports are assigned to PHY entities), an insufficient number of PHY partition subsets for a number of FEU inputs of the FEU profile, or a number of PHY partition subsets exceeding a threshold number of PHY partition subsets per transmission chain of the RU (e.g., based at least in part on a peak-to-average-power ratio (PAPR) or adjacent channel leakage power ratio (ACLR) restrictions), or a configuration that is incompatible with underlying internal data or control path architecture limitations in PHY entity components, FEU components or a combination thereof.
  • PAPR peak-to-average-power ratio
  • the RU may receive an indication of a selected PHY profde that is incompatible with a selected FEU profde. Based at least in part on the selected PHY profde being incompatible with the selected FEU profde, the RU may provide feedback to the DU to indicate that the selected PHY profde is incompatible with the selected FEU profde. In some aspects, the RU may further indicate a recommended PHY profde to pair with the selected FEU profde and/or a recommended FEU profde to pair with the selected PHY profde.
  • the RU may provide an indication of a profde compatibility mapping that indicates pairings of FEU profdes and compatible PHY profdes.
  • the RU may receive an indication of a selected PHY profde that is compatible with a selected FEU profde based at least in part on the indication of the profde compatibility mapping.
  • a compatibility map may list all allowable mappings. In some other aspects, a full list of allowable maps may be derived from the compatibility map.
  • the compatibility map may indicate compatibility between a PHY profde and a FEU profde where PHYx has N antennas may imply, directly or based at least in part on additional capability signaling, a profde where PHYx has M ⁇ N antennas, where any, or possibly a further restricted, M- size subset of the original N broadband antennas ports can be selected.
  • M ⁇ N further signaling may be used to indicate which broadband ports are selected.
  • the RU may receive a request for partition subset capabilities from the DU.
  • the RU may provide an indication of PHY profde and FEU profde pairings that satisfy at least a portion of the partition subset capabilities.
  • the RU may receive an indication of a selected PHY profde and a selected FEU profde that is based at least in part on the indication of the PHY profde and FEU profde pairings.
  • compatibility between a PHY profde and an FEU profde may imply compatibility involving any, or a restricted, subset of the broadband ports at the interface between the components of the profdes.
  • the configuration of the selected subset may be indicated by further signaling (e.g., with a profde selection, configuration of a PHY in the profde, or configuration of a FEU component in the profde).
  • a compatibility of subsets may be further restricted by signaling that indicates a subset restriction (e.g., “open ports disallowed” or “all ports for the same wideband (WB) chain must be either disable or enabled in the PHY”).
  • the DU may understand compatibility between indications of logical baseband port labels of the PHY entity with FEU profdes. This may reduce errors caused by the PHY entity outputting signals to one or more baseband ports that do not correspond with intended input ports of the FEU. This may conserve power, network, communication, and/or computing resources that may otherwise have been used to attempt to schedule and transmit the signals again.
  • Fig. 5 is a diagram illustrating an example 500 associated with PHY profdes of an RU, in accordance with the present disclosure.
  • a UE e.g., UE 120
  • the UE and the base station may be part of a wireless network (e.g., wireless network 100).
  • the base station may be configured with a split-6 configuration in which a distributed unit of the base station is split into a first functional unit that includes L2/L3 layer entities (e.g., e.g., a DU) and a second functional unit (e.g., an RU).
  • L2/L3 layer entities e.g., e.g., a DU
  • a second functional unit e.g., an RU.
  • operations performed by the DU may be performed by a virtual network function (VNF) of the DU and/or operations performed by the RU may be performed by a physical network function (PNF) of the RU.
  • VNF virtual network function
  • PNF physical network function
  • the RU may provide, and the DU may receive, an indication of one or more candidate PHY profiles.
  • an indication of a PHY profile, of the one or more candidate PHY profiles may indicate a PHY profile identification and/or a number of partition subsets supported in the PHY profile, among other examples.
  • the PHY profile may indicate one or more of a partition subset identifier, a number of local baseband ports associated with the partition subset, and global baseband port identifications for the local baseband ports associated with the partition subset.
  • the RU may provide, and the DU may receive, a mapping of FEU profiles to compatible PHY profiles.
  • the mapping may include a matrix of validity indications, a list of valid (e.g., compatible) pairings, a list of invalid (e.g., incompatible) pairings, and/or an encoded indication of the mapping.
  • the mapping may include Booleans, integers, or bits, among other examples, as validity flags.
  • a list may be represented as a bitmap with dimension cell ⁇ (#PHY profiles* #DFE profiles)/8 ⁇ and/or with deterministic mapping between each bit and a corresponding entry in a validity matrix.
  • the mapping may include a list of valid (PHY profile, FEU profile)- tuples (e.g., all unlisted tuples may be invalid or may have validity derivable based at least in part on the valid tuples).
  • the mapping may include a list of invalid (PHY profile, DFE profile)-tuples.
  • the mapping may include hybrid signaling where some parts (e.g., submatrices) of a validity matrix are represented as an actual matrix and other parts are represented as a list of valid or invalid tuples.
  • the mapping may include a general compression mechanism (e.g., run-length encoding (RLE) or Lempel-Ziv- Welch (LZW), among other examples) that includes values of the mapping.
  • the mapping may include a specialized compression mechanism (e.g., only a subset of salient compatible profiles may be indicated and a remainder of the compatible profiles may be derivable based at least in part on explicitly indicated compatible profiles).
  • multiple encodings may be possible for indicating the mapping. In these scenarios, the RU may signal an indication of a selection of an encoding scheme that is selected for signaling the mapping.
  • the RU may receive, and the DU may provide, an indication of a set of parameters for selection of a candidate PHY profile or a candidate FEU profile.
  • the set of parameters may include a selection of a candidate PHY profile, a selection of a candidate FEU profile, and/or a set of proposed PHY profile and FEU profile pairings, among other examples.
  • the set of parameters may include a selection of a candidate FEU profile and may indicate a request for a recommended PHY profile to pair with the candidate FEU profile.
  • the set of parameters may include an indication of intended parameters associated with the selected PHY profile, intended parameters associated with the selected FEU profile, and/or a number of component carriers to use for communication with the device, among other examples.
  • the set of parameters may include a minimum number or a maximum number of transmit or receive baseband ports and/or an ability to pair with FEU profiles with a minimum number of transmit reference signals in particular bands, among other examples.
  • the RU may provide, and the DU may receive, an indication of one or more recommended candidate PHY profiles and/or one or more recommended candidate FEU profiles.
  • the RU may provide one or more of these indications based at least in part on receiving the indication of the set of parameters for selection of the candidate PHY profile or the candidate FEU profile.
  • the RU may provide a set of PHY profiles that satisfy the set of parameters, a set of PHY profiles that satisfy a subset of the set of parameters, or an indication that the set of parameters is rejected.
  • the RU may indicate that the set of parameters is rejected based at least in part on the RU not being configured with a PHY profile and FEU profile pair that satisfy all of the set of parameters or not being configured with a PHY profile and FEU profile pair that satisfy a threshold number, or percentage, of the set of parameters, among other examples.
  • the RU may indicate a reason for rejection of the set of parameters.
  • the RU may receive, and the DU may provide, a request for partition subset capabilities.
  • the request may be associated with a PHY profile.
  • the DU may request an indication of connections of a partition subset to baseband ports, a supportable bandwidth, a maximum number of layers, a maximum number of supported UEs, and/or a maximum number of physical downlink shared channels per slot, among other examples.
  • the RU may provide, and the DU may receive, an indication of partition subset capabilities.
  • the RU may provide an indication of mapping of FEU profdes to compatible PHY profiles and/or an indication of baseband ports connected to partition subsets, among other examples.
  • the indication of partition subset capabilities may include an indication of a dependency of the partition subset capabilities on a selection of a PHY profile or an FEU profile.
  • the indication of the dependency may include an explicit indication of the dependency and/or an invariant-based dependency.
  • parameters subject to dependency may be signaled as one or more lists of tuples (e.g., a number of baseband ports and capability), where the number of baseband ports can be for a particular direction (e.g., uplink or downlink), or total number of BB ports connected to the partition subset.
  • the parameters indicated with invariant dependency may be interpreted based at least in part on a configured scaling as a function of baseband ports and/or antenna ports.
  • the invariant may be based at least in part on a stated or implied parameter, such as an assumed number of computational units expressed, for example, as a product of other units (e.g., maximum bandwidth x maximum number of layers).
  • the DU may receive, and the RU may provide, an indication of a selected PHY profile, of the one or more candidate PHY profiles.
  • the RU may provide, and the DU may receive, an indication that a selected PHY profile is incompatible with a selected FEU.
  • the selected PHY profile may be incompatible with the selected FEU profile based at least in part on a determination that the selected PHY profile would cause input ports of the FEU to be open ports. In some aspects, the selected PHY profile may be incompatible with the selected FEU profile based at least in part on a determination that the selected PHY profile would cause multiple component carriers configured for the FEU to be connected to a single PHY partition subset. In some aspects, the selected PHY profile may be incompatible with the selected FEU profile based at least in part on a PAPR parameter or an adjacent channel leakage ratio parameter that indicates a single PHY partition subset is to be connected to a transmission RU.
  • the RU may receive the indication of the selected PHY profile that is incompatible with the FEU profile based at least in part on the UE not providing the mapping of FEU profiles to compatible PHY profiles and/or the DU selecting pair of a PHY profile and an FEU profile that are not indicated as being compatible.
  • the DU may store the indication that the PHY profile and the FEU profile are incompatible and/or avoid pairing the selected PHY profile and the selected FEU in subsequent selections.
  • the RU may provide, and the DU may receive, an indication of one or more compatible pairs of PHY profiles and FEU profiles.
  • the RU may provide an indication of one or more recommended PHY profiles, of the one or more candidate PHY profiles, and/or an indication of one or more recommended FEU profiles that are compatible with the selected PHY profile. For example, the RU may provide one or more of these indications based at least in part on determining that the selected PHY profile is incompatible with the selected FEU and/or providing the indication that the selected PHY profile is incompatible with the selected FEU. In some aspects, the RU may provide one or more recommended PHY profiles and/or FEU profiles that are associated with an associated DFE profile (e.g., FEU profile).
  • an associated DFE profile e.g., FEU profile
  • the RU may provide a recommendation of all, or a subset of all, PHY profiles that are compatible with the indicated FEU profile. Additionally, or alternatively, the RU may provide a recommendation of all, or a subset of all, FEU profiles that are compatible with the indicated PHY profile.
  • the base station may communicate with the UE via the RU.
  • the RU of the base station may transmit and or receive communications with the UE based at least in part on selected PHY profiles and/or FEU profiles.
  • the DU may understand compatibility between indications of logical baseband port labels of the PHY entity with FEU profiles. This may reduce errors cause by PHY entity outputting signals to one or more baseband ports that do not correspond with intended input ports of the FEU. This may conserve power, network, communication, and/or computing resources that may otherwise have been used to attempt to schedule and transmit the signals again.
  • Fig. 5 is provided as an example. Other examples may differ from what is described with regard to Fig. 5.
  • the RU and the DU may perform only a subset of operations shown above.
  • the RU and DU may perform the operations described with reference to reference numbers 505, 535, 540, and/or 545.
  • the RU and the DU may perform the operations described with reference to reference numbers 505, 510, and/or 535.
  • the RU and the DU may perform the operations described with reference to reference numbers 505, 515, 520, and/or 535.
  • Fig. 6 is a diagram illustrating an example 600 associated with mapping of PHY entity profiles to FEU profiles via baseband ports, in accordance with the present disclosure.
  • a PHY entity of the RU may include multiple candidate PHY entity profiles, such as a first PHY entity profile 605, a second PHY entity profile 610, and/or a third PHY entity profile 615 that may be connected to baseband ports 620.
  • the first PHY entity profile 605 may include a single PHY partition subset (e.g., with a single PHY connected to all baseband ports 620).
  • the second PHY entity profile 610 may include a first PHY partition subset connected to a first subset of the baseband ports 620 and a second PHY partition subset connected to a second subset of the baseband ports 620.
  • the third PHY entity profile 615 may include a first PHY partition subset connected to a first subset of the baseband ports 620, a second PHY partition subset connected to a second subset of the baseband ports 620, and a third PHY partition subset connected to a third subset of the baseband ports 620.
  • the FEU may include multiple candidate FEU profiles, such as a first FEU profile 625 and a second FEU profile 630.
  • the first FEU profile 625 may be connected to multiple baseband ports.
  • the first FEU profile 625 may receive multiple signals via multiple (e.g., 2) narrowband chains, combine the multiple signals (e.g., using a combiner), and process the combined multiple signals via a wideband chain.
  • the first FEU profile 625 may be configured to output the combined multiple signals to an RF unit for transmission to another device.
  • the second FEU profile 630 may receive multiple (e.g., 4) signals via multiple narrowband chains, combine the multiple signals, and process the combined multiple signals via multiple wideband chains.
  • the second FEU profile 630 may be configured to output the combined multiple signals to one or more RF units for transmission to one or more other devices.
  • Fig. 6 is provided as an example. Other examples may differ from what is described with regard to Fig. 6.
  • Fig. 7 is a diagram illustrating an example process 700 performed, for example, by a base station, in accordance with the present disclosure.
  • Example process 700 is an example where the base station (e.g., base station 110) performs operations associated with PHY profiles of an RU.
  • the base station e.g., base station 110
  • process 700 may include providing, to a DU of the base station, an indication of one or more candidate PHY profiles (block 710).
  • the base station e.g., using communication manager 808, depicted in Fig. 8
  • process 700 may include receiving, from the DU, an indication of a selected PHY profile, of the one or more candidate PHY profiles, to use for communication with a device (block 720).
  • the base station e.g., using communication manager 808, depicted in Fig. 8
  • 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 providing, by the RU and to the DU, an indication that the selected PHY profile is incompatible with a selected FEU profile.
  • the selected PHY profile is incompatible with the selected FEU profile based at least in part on one or more of the selected PHY profile would cause input ports of the FEU to be open ports, the selected PHY profile would cause multiple component carriers configured for the FEU to be connected to a single PHY partition subset, a peak-to-average power ratio parameter or an adjacent channel leakage ratio parameter that indicates a single PHY partition subset is to be connected to a transmission RU, or internal data or control path architecture limitations in PHY components, FEU components or a combination thereof
  • process 700 includes providing, by the RU and to the DU, an indication of one or more recommended PHY profiles, of the one or more candidate PHY profiles, or providing, by the RU and to the DU, an indication of one or more recommended FEU profiles that are compatible with the selected PHY profile.
  • process 700 includes providing, by the RU and to the DU, an indication of one or more compatible pairs of PHY profiles and/or FEU profiles that match an intended FEU profile. [0115] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, process 700 includes providing a mapping of FEU profiles to compatible PHY profiles. [0116] In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the mapping of digital front unit profiles to compatible PHY profiles comprises one or more of a matrix of validity indications, a list of valid parings, a list of invalid pairings, or an encoded indication of the mapping.
  • process 700 includes receiving, by the RU and from the DU, an indication of a set of parameters for selection of one or more of a candidate PHY profile or a candidate FEU profile, and providing, by the RU and to the DU, an indication of one or more recommended PHY profiles, of the one or more candidate PHY profiles, or one or more recommended FEU profiles based at least in part on the set of parameters, wherein reception of the indication of the selected PHY profile is based at least in part on the indication of the one or more recommended PHY profiles.
  • the set of parameters include one or more indications of a selection of a candidate PHY profile, a selection of a candidate FEU profile, intending parameters associated with the selected PHY profile, intending parameters associated with the selected FEU profile, a number of component carriers to use for communication with the device, or a set of proposed PHY profile and FEU profile pairings.
  • providing the indication of one or more recommended PHY profiles comprises providing a set of PHY profiles that satisfy the set of parameters, providing a set of PHY profiles that satisfy a subset of the set of parameters, or an indication that the set of parameters is rejected.
  • the indication that the set of parameters is rejected comprises an indication of a reason for rejection of the set of parameters.
  • a PHY profile, of the one or more candidate PHY profiles comprises indications of one or more of a PHY profile identification, a number of partitions subsets supported in the PHY profile, or for a partition subset supported in the PHY profile, one or more of a partition subset identifier, a number of local baseband ports associated with the partition subset, and global baseband port identifications for the local baseband ports associated with the partition subset.
  • process 700 includes receiving, by the RU and from the DU, a request for partition subset capabilities, and providing, by the RU and to the DU, an indication of partition subset capabilities.
  • the partition subset capabilities are based at least in part on a selection of a PHY profile or a FEU profile.
  • providing the indication of partition subset capabilities that are based at least in part on a selection of a PHY profile or a FEU profile comprises providing an indication of a dependency of the partition subset capabilities on a selection of a PHY profile or a FEU profile.
  • the indication of the dependency of the partition subset capabilities on a selection of a PHY profile or a FEU profile comprises one or more of an explicit indication of the dependency, or an invariant-based dependency.
  • 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 block diagram of an example apparatus 800 for wireless communication.
  • the apparatus 800 may be a base station, or a base station may include the apparatus 800.
  • the apparatus 800 includes a reception component 802 and a transmission component 804, which may be in communication with one another (for example, via one or more buses and/or one or more other components).
  • the apparatus 800 may communicate with another apparatus 806 (such as a UE, a base station, or another wireless communication device) using the reception component 802 and the transmission component 804.
  • the apparatus 800 may include a communication manager 808.
  • the communication manager may include a VNF, a PNF, and/or a FAPI, among other examples.
  • the apparatus 800 may be configured to perform one or more operations described herein in connection with Figs. 5 and 6. Additionally, or alternatively, the apparatus 800 may be configured to perform one or more processes described herein, such as process 700 of Fig. 7.
  • the apparatus 800 and/or one or more components shown in Fig. 8 may include one or more components of the base station described above in connection with Fig. 2. Additionally, or alternatively, one or more components shown in Fig. 8 may be implemented within one or more components described above 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.
  • the reception component 802 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 806.
  • the reception component 802 may provide received communications to one or more other components of the apparatus 800.
  • the reception component 802 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 800.
  • the reception component 802 may include one or more antennas, a demodulator, a MIMO detector, a receive processor, a controller/processor, a memory, or a combination thereof, of the base station described above in connection with Fig. 2.
  • the transmission component 804 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 806.
  • one or more other components of the apparatus 800 may generate communications and may provide the generated communications to the transmission component 804 for transmission to the apparatus 806.
  • the transmission component 804 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 806.
  • the transmission component 804 may include one or more antennas, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the base station described above in connection with Fig. 2. In some aspects, the transmission component 804 may be co-located with the reception component 802 in a transceiver.
  • the communication manager 808 may provide, to a DU of the base station, an indication of one or more candidate PHY profiles.
  • the reception component 802 may receive, from the DU, an indication of a selected PHY profile, of the one or more candidate PHY profiles, to use for communication with a device, such as a UE.
  • the communication manager 808 may provide, to the DU, an indication that the selected PHY profile is incompatible with a selected FEU profile.
  • the communication manager 808 may provide, to the DU, an indication of one or more recommended PHY profiles, of the one or more candidate PHY profiles.
  • the communication manager 808 may provide, to the DU, an indication of one or more recommended FEU profiles that are compatible with the selected PHY profile.
  • the communication manager 808 may provide, to the DU, an indication of one or more compatible pairs of PHY profiles and FEU profiles that match an intended FEU profile. [0136] The communication manager 808 may provide a mapping of FEU profiles to compatible PHY profiles.
  • the communication manager 808 may receive, from the DU, an indication of a set of parameters for selection of one or more of a candidate PHY profile or a candidate FEU profile. [0138] The communication manager 808 may provide, to the DU, an indication of one or more recommended PHY profiles, of the one or more candidate PHY profiles, or one or more recommended FEU profiles based at least in part on the set of parameters wherein reception of the indication of the selected PHY profile is based at least in part on the indication of the one or more recommended PHY profiles. [0139] The communication manager 808 may receive, from the DU, a request for partition subset capabilities.
  • the communication manager 808 may provide, to the DU, an indication of partition subset capabilities.
  • Fig. 8 The number and arrangement of components shown in Fig. 8 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. 8. Furthermore, two or more components shown in Fig. 8 may be implemented within a single component, or a single component shown in Fig. 8 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in Fig. 8 may perform one or more functions described as being performed by another set of components shown in Fig. 8
  • Aspect 1 A method of wireless communication performed by a base station, comprising: providing, by a radio unit (RU) of the base station and to a distributed unit (DU) of the base station, an indication of one or more candidate physical entity (PHY) profiles; and receiving, by the RU and from the DU, an indication of a selected PHY profile, of the one or more candidate PHY profiles, to use for communication with a device.
  • RU radio unit
  • DU distributed unit
  • PHY physical entity
  • Aspect 2 The method of Aspect 1, further comprising: providing, by the RU and to the DU, an indication that the selected PHY profile is incompatible with a selected front end unit profile.
  • Aspect 3 The method of Aspect 2, wherein the selected PHY profile is incompatible with the selected front end unit profile based at least in part on one or more of: the selected PHY profile would cause input ports of the front end unit to be open ports, the selected PHY profile would cause multiple component carriers configured for the front end unit to be connected to a single PHY partition subset, or a peak-to-average power ratio parameter or an adjacent channel leakage ratio parameter that indicates a single PHY partition subset is to be connected to a transmission radio unit.
  • Aspect 4 The method of any of Aspects 2-3, further comprising: providing, by the RU and to the DU, an indication of one or more recommended PHY profiles, of the one or more candidate PHY profiles, or providing, by the RU and to the DU, an indication of one or more recommended front end unit profiles that are compatible with the selected PHY profile.
  • Aspect 5 The method of any of Aspects 2-4, further comprising: providing, by the RU and to the DU, an indication of one or more compatible pairs of PHY profiles - and front end unit profiles that match an intended front end unit profile.
  • Aspect 6 The method of any of Aspects 2-5, further comprising: providing a mapping of front end unit profdes to compatible PHY profiles.
  • Aspect 7 The method of Aspect 6, wherein the mapping of digital front unit profiles to compatible PHY profiles comprises one or more of: a matrix of validity indications, a list of valid parings, a list of invalid pairings, or an encoded indication of the mapping.
  • Aspect 8 The method of Aspect 1, further comprising: receiving, by the RU and from the DU, an indication of a set of parameters for selection of one or more of a candidate PHY profile or a candidate front end unit profile; and providing, by the RU and to the DU, an indication of one or more recommended PHY profiles, of the one or more candidate PHY profiles, or one or more recommended front end unit profiles based at least in part on the set of parameters, wherein reception of the indication of the selected PHY profile is based at least in part on the indication of the one or more recommended PHY profiles.
  • Aspect 9 The method of Aspect 8, wherein the set of parameters include one or more indications of: a selection of a candidate PHY profile, a selection of a candidate front end unit profile, intended parameters associated with the selected PHY profile, intended parameters associated with the selected front end unit profile, a number of component carriers to use for communication with the device, or a set of proposed PHY profile and front end unit profile pairings.
  • Aspect 10 The method of any of Aspects 8-9, wherein providing the indication of one or more recommended PHY profiles comprises: providing a set of PHY profiles that satisfy the set of parameters, providing a set of PHY profiles that satisfy a subset of the set of parameters, or an indication that the set of parameters is rejected.
  • Aspect 11 The method of Aspect 10, wherein the indication that the set of parameters is rejected comprises an indication of a reason for rejection of the set of parameters.
  • Aspect 12 The method of any of Aspects 1-11, wherein a PHY profile, of the one or more candidate PHY profiles, comprises indications of one or more of: a PHY profile identification, a number of partitions subsets supported in the PHY profile, or for a partition subset supported in the PHY profile, one or more of a partition subset identifier, a number of local baseband ports associated with the partition subset, and global baseband port identifications for the local baseband ports associated with the partition subset.
  • Aspect 13 The method of Aspect 1, further comprising: receiving, by the RU and from the DU, a request for partition subset capabilities; and providing, by the RU and to the DU, an indication of partition subset capabilities.
  • Aspect 14 The method of Aspect 13, wherein the partition subset capabilities are based at least in part on a selection of a PHY profile or a front end unit profile.
  • Aspect 15 The method of Aspect 14, wherein providing the indication of partition subset capabilities that are based at least in part on a selection of a PHY profile or a front end unit profile comprises: providing an indication of a dependency of the partition subset capabilities on a selection of a PHY profile or a front end unit profile.
  • Aspect 16 The method of Aspect 15, wherein the indication of the dependency of the partition subset capabilities on a selection of a PHY profile or a front end unit profile comprises one or more of: an explicit indication of the dependency, or an invariant-based dependency.
  • Aspect 17 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-16.
  • Aspect 18 A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the memory and the one or more processors configured to perform the method of one or more of Aspects 1-16.
  • Aspect 19 An apparatus for wireless communication, comprising at least one means for performing the method of one or more of Aspects 1-16.
  • Aspect 20 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-16.
  • Aspect 21 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-16.
  • 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. It will be apparent that systems and/or methods described herein may be implemented in different forms of hardware and/or a combination of hardware and software.
  • 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.
  • 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.
  • a phrase referring to “at least one of’ a list of items refers to any combination of those items, including single members.
  • “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. 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’).

Landscapes

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

Abstract

Divers aspects de la présente divulgation portent d'une manière générale sur la communication sans fil. Selon certains aspects, une station de base peut fournir, à une unité distribuée (DU) de la station de base, une indication d'un ou de plusieurs profils d'entité physique (PHY) candidats. La station de base peut recevoir, en provenance de la DU, une indication d'un profil PHY sélectionné, du ou des profils PHY candidats, à utiliser pour une communication avec un dispositif, tel qu'un équipement utilisateur. De nombreux autres aspects sont décrits.
EP22710919.6A 2021-02-10 2022-02-10 Profils d'entité physique d'une unité radio Pending EP4292252A1 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US202163147970P 2021-02-10 2021-02-10
US17/650,486 US20220255688A1 (en) 2021-02-10 2022-02-09 Physical entity profiles of a radio unit
PCT/US2022/070601 WO2022174238A1 (fr) 2021-02-10 2022-02-10 Profils d'entité physique d'une unité radio

Publications (1)

Publication Number Publication Date
EP4292252A1 true EP4292252A1 (fr) 2023-12-20

Family

ID=80780854

Family Applications (1)

Application Number Title Priority Date Filing Date
EP22710919.6A Pending EP4292252A1 (fr) 2021-02-10 2022-02-10 Profils d'entité physique d'une unité radio

Country Status (2)

Country Link
EP (1) EP4292252A1 (fr)
WO (1) WO2022174238A1 (fr)

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8139535B2 (en) * 2008-10-31 2012-03-20 Intel Corporation Blind channel detection techniques
CN109565901B (zh) * 2016-08-12 2021-10-22 富士通株式会社 无线基站、无线装置、无线控制装置、无线通信系统、通信方法以及无线终端

Also Published As

Publication number Publication date
WO2022174238A1 (fr) 2022-08-18

Similar Documents

Publication Publication Date Title
US11728877B2 (en) Polarization and antenna panel configuration and communication diversity configuration
WO2021243354A1 (fr) Identification de liaison pour informations transportées par trame
US20220039103A1 (en) Multicast downlink control information configuration
US20220255688A1 (en) Physical entity profiles of a radio unit
US11876754B2 (en) Signaling of intended time division duplexing downlink-uplink configuration
US20220256376A1 (en) Conformance testing of segmentation
WO2022236461A1 (fr) Mise à jour d'état d'indicateur de commande de transmission pour une pluralité de points de réception/transmission
US11705954B2 (en) Transmission configuration indicator state group indication
EP4268408A1 (fr) Détermination dynamique d'intervalles disponibles pour la transmission d'informations de signaux de référence de sondage (srs)
EP4292252A1 (fr) Profils d'entité physique d'une unité radio
US20220368395A1 (en) Beam group based channel state information reporting
US11706660B2 (en) Sidelink and UU link buffer status report
CN116848824A (zh) 无线电单元的物理实体简档
WO2023065209A1 (fr) Configuration de mode de point d'émission/réception
US20220377794A1 (en) Downlink control information for licensed and unlicensed new radio
WO2022135452A1 (fr) Détermination dynamique d'intervalles disponibles pour la transmission d'informations de signaux de référence de sondage (srs)
US20210321365A1 (en) Quality of service or priority configuration for relay user equipment
EP4289090A1 (fr) Décodage d'informations d'état de canal
WO2021092610A1 (fr) Signalisation pour schémas de point de réception/multi-transmission (multi-trp)
EP4388665A1 (fr) Type de section de configuration de porteuses et extension de formation de faisceaux analogique
EP4378241A1 (fr) Conception d'indication précoce de radiomessagerie unifiée
WO2021243374A1 (fr) Techniques d'optimisation de mode de double connectivité
CN117981427A (zh) 未被配置用于单频网传输的服务小区的多个传输配置指示符状态

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: 20230609

AK Designated contracting states

Kind code of ref document: A1

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 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)