The present disclosure relates generally to wireless communication systems and, more specifically, to electronic devices and methods for parameter combination for coherent joint transmission.
5th generation (5G) or new radio (NR) mobile communications is recently gathering increased momentum with all the worldwide technical activities on the various candidate technologies from industry and academia. The candidate enablers for the 5G/NR mobile communications include massive antenna technologies, from legacy cellular frequency bands up to high frequencies, to provide beamforming gain and support increased capacity, new waveform (e.g., a new radio access technology (RAT)) to flexibly accommodate various services/applications with different requirements, new multiple access schemes to support massive connections, and so on.
This disclosure relates to apparatuses and methods for parameter combination for coherent joint transmission.
In one embodiment, a user equipment (UE) is provided. The UE includes a transceiver configured to receive information about a channel state information (CSI) report. The information includes codebook parameters NL≥1 combinations of values of {L1, . . . , LN
In another embodiment, a base station (BS) is provided. The BS includes a processor and a transceiver operably coupled to the processor. The transceiver is configured to transmit information about a CSI report and receive the CSI report that is based on the information. The information includes codebook parameters NL≥1 combinations of values of {L1, . . . , LN
In yet another embodiment, a method performed by a UE is provided. The method includes receiving information about a CSI report. The information includes codebook parameters NL≥1 combinations of values of {L1, . . . , LN
Other technical features may be readily apparent to one skilled in the art from the following figures, descriptions, and claims.
Before undertaking the DETAILED DESCRIPTION below, it may be advantageous to set forth definitions of certain words and phrases used throughout this patent document. The term “couple” and its derivatives refer to any direct or indirect communication between two or more elements, whether or not those elements are in physical contact with one another. The terms “transmit,” “receive,” and “communicate,” as well as derivatives thereof, encompass both direct and indirect communication. The terms “include” and “comprise,” as well as derivatives thereof, mean inclusion without limitation. The term “or” is inclusive, meaning and/or. The phrase “associated with,” as well as derivatives thereof, means to include, be included within, interconnect with, contain, be contained within, connect to or with, couple to or with, be communicable with, cooperate with, interleave, juxtapose, be proximate to, be bound to or with, have, have a property of, have a relationship to or with, or the like. The term “controller” means any device, system or part thereof that controls at least one operation. Such a controller may be implemented in hardware or a combination of hardware and software and/or firmware. The functionality associated with any particular controller may be centralized or distributed, whether locally or remotely. The phrase “at least one of,” when used with a list of items, means that different combinations of one or more of the listed items may be used, and only one item in the list may be needed. For example, “at least one of: A, B, and C” includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C.
Moreover, various functions described below can be implemented or supported by one or more computer programs, each of which is formed from computer readable program code and embodied in a computer readable medium. The terms “application” and “program” refer to one or more computer programs, software components, sets of instructions, procedures, functions, objects, classes, instances, related data, or a portion thereof adapted for implementation in a suitable computer readable program code. The phrase “computer readable program code” includes any type of computer code, including source code, object code, and executable code. The phrase “computer readable medium” includes any type of medium capable of being accessed by a computer, such as read only memory (ROM), random access memory (RAM), a hard disk drive, a compact disc (CD), a digital video disc (DVD), or any other type of memory. A “non-transitory” computer readable medium excludes wired, wireless, optical, or other communication links that transport transitory electrical or other signals. A non-transitory computer readable medium includes media where data can be permanently stored and media where data can be stored and later overwritten, such as a rewritable optical disc or an erasable memory device.
Definitions for other certain words and phrases are provided throughout this patent document. Those of ordinary skill in the art should understand that in many if not most instances, such definitions apply to prior as well as future uses of such defined words and phrases.
For a more complete understanding of the present disclosure and its advantages, reference is now made to the following description taken in conjunction with the accompanying drawings, in which like reference numerals represent like parts:
The following documents and standards descriptions are hereby incorporated by reference into the present disclosure as if fully set forth herein: 3GPP TS 36.211 v17.2.0, “E-UTRA, Physical channels and modulation” (herein “REF 1”); 3GPP TS 36.212 v17.1.0, “E-UTRA, Multiplexing and Channel coding” (herein “REF 2”); 3GPP TS 36.213 v17.2.0, “E-UTRA, Physical Layer Procedures” (herein “REF 3”); 3GPP TS 36.321 v17.1.0, “E-UTRA, Medium Access Control (MAC) protocol specification” (herein “REF 4”); 3GPP TS 36.331 v17.1.0, “E-UTRA, Radio Resource Control (RRC) Protocol Specification” (herein “REF 5”); 3GPP TS 38.211 v17.2.0, “NR, Physical channels and modulation” (herein “REF 6”); 3GPP TS 38.212 v17.2.0, “NR, Multiplexing and Channel coding” (herein “REF 7”); 3GPP TS 38.213 v17.2.0, “NR, Physical Layer Procedures for Control” (herein “REF 8”); 3GPP TS 38.214 v17.2.0, “NR, Physical Layer Procedures for Data” (herein “REF 9”); 3GPP TS 38.215 v17.1.0, “NR, Physical Layer Measurements” (herein “REF 10”); 3GPP TS 38.321 v17.1.0, “NR, Medium Access Control (MAC) protocol specification” (herein “REF 11”); and 3GPP TS 38.331 v17.1.0, “NR, Radio Resource Control (RRC) Protocol Specification” (herein “REF 12”).
For a cellular system operating in a sub-1 GHz frequency range (e.g., less than 1 GHz), supporting large number of CSI-RS antenna ports (e.g., 32) at a single location or remote radio head (RRH) or TRP is challenging due to that a larger antenna form factor size is needed at these frequencies than a system operating at a higher frequency such as 2 GHz or 4 GHz. At such low frequencies, the maximum number of CSI-RS antenna ports that can be co-located at a single site (or TRP/RRH) can be limited, for example to 8. This limits the spectral efficiency of such systems. In particular, the MU-MIMO spatial multiplexing gains offered due to large number of CSI-RS antenna ports (such as 32) can't be achieved.
One way to operate a sub-1 GHz system with large number of CSI-RS antenna ports is based on distributing antenna ports at multiple locations (or TRP/RRHs). The multiple sites or TRPs/RRHs can still be connected to a single (common) base unit, hence the signal transmitted/received via multiple distributed TRPs/RRHs can still be processed at a centralized location. This is called distributed MIMO or multi-TRP coherent joint transmission (C-JT).
The discussion of 5G systems and frequency bands associated therewith is for reference as certain embodiments of the present disclosure may be implemented in 5G systems. However, the present disclosure is not limited to 5G systems, or the frequency bands associated therewith, and embodiments of the present disclosure may be utilized in connection with any frequency band. For example, aspects of the present disclosure may also be applied to deployment of 5G communication systems, 6G or even later releases which may use terahertz (THz) bands.
Embodiments of the present disclosure propose methods and apparatuses for parameter combinations for C-JT transmissions.
Embodiments of the present disclosure recognize that CSI enhancement described in Rel-18 MIMO considers Rel-16/17 Type-II CSI codebook refinements to support mTRP coherent joint transmission (C-JT) operations by considering performance-and-overhead trade-off. The Rel-16/17 Type-II CSI codebook has three components W1, W2, and Wf. Rel-18 Type-II CSI codebook for CJT requires {Ln} values and pv, β for the case of Rel-16-based refinement CJT codebook, and {αn} values and M, β for the case of Rel-17-based refinement CJT codebook, respectively. In Rel-16/17 Type-II CSI codebook, a joint parameter combination table is used for NW to configure one of the possible combinations in the table to the UE. However, in Rel-18 Type-II CSI codebook, following the legacy approach using a joint table for the parameters may not be efficient since the joint table can be too long and complicated.
Embodiments of the present disclosure propose two (or more than two) separate tables for configuring codebook parameter combinations (an extension of the tables of paraCombination-r16, paraCombination-r17) having good performance-and-overhead trade-off for mTRP C-JT operations. Additionally, embodiments of the present disclosure propose linkage between two separate tables to provide more efficient parameter-combination framework for Rel-18 Type-II CSI codebook for CJT.
As shown in
The gNB 102 provides wireless broadband access to the network 130 for a first plurality of user equipments (UEs) within a coverage area 120 of the gNB 102. The first plurality of UEs includes a UE 111, which may be located in a small business; a UE 112, which may be located in an enterprise; a UE 113, which may be a WiFi hotspot; a UE 114, which may be located in a first residence; a UE 115, which may be located in a second residence; and a UE 116, which may be a mobile device, such as a cell phone, a wireless laptop, a wireless PDA, or the like. The gNB 103 provides wireless broadband access to the network 130 for a second plurality of UEs within a coverage area 125 of the gNB 103. The second plurality of UEs includes the UE 115 and the UE 116. In some embodiments, one or more of the gNBs 101-103 may communicate with each other and with the UEs 111-116 using 5G/NR, long term evolution (LTE), long term evolution-advanced (LTE-A), WiMAX, WiFi, or other wireless communication techniques.
Depending on the network type, the term “base station” or “BS” can refer to any component (or collection of components) configured to provide wireless access to a network, such as transmit point (TP), transmit-receive point (TRP), an enhanced base station (eNodeB or eNB), a 5G/NR base station (gNB), a macrocell, a femtocell, a WiFi access point (AP), or other wirelessly enabled devices. Base stations may provide wireless access in accordance with one or more wireless communication protocols, e.g., 5G/NR 3rd generation partnership project (3GPP) NR, long term evolution (LTE), LTE advanced (LTE-A), high speed packet access (HSPA), Wi-Fi 802.11a/b/g/n/ac, etc. For the sake of convenience, the terms “BS” and “TRP” are used interchangeably in this patent document to refer to network infrastructure components that provide wireless access to remote terminals. Also, depending on the network type, the term “user equipment” or “UE” can refer to any component such as “mobile station,” “subscriber station,” “remote terminal,” “wireless terminal,” “receive point,” or “user device.” For the sake of convenience, the terms “user equipment” and “UE” are used in this patent document to refer to remote wireless equipment that wirelessly accesses a BS, whether the UE is a mobile device (such as a mobile telephone or smartphone) or is normally considered a stationary device (such as a desktop computer or vending machine).
Dotted lines show the approximate extents of the coverage areas 120 and 125, which are shown as approximately circular for the purposes of illustration and explanation only. It should be clearly understood that the coverage areas associated with gNBs, such as the coverage areas 120 and 125, may have other shapes, including irregular shapes, depending upon the configuration of the gNBs and variations in the radio environment associated with natural and man-made obstructions.
As described in more detail below, one or more of the UEs 111-116 include circuitry, programing, or a combination thereof for supporting parameter combination for coherent joint transmission. In certain embodiments, one or more of the BSs 101-103 include circuitry, programing, or a combination thereof for supporting parameter combination for coherent joint transmission.
Although
As shown in
The transceivers 210a-210n receive, from the antennas 205a-205n, incoming RF signals, such as signals transmitted by UEs in the network 100. The transceivers 210a-210n down-convert the incoming RF signals to generate IF or baseband signals. The IF or baseband signals are processed by receive (RX) processing circuitry in the transceivers 210a-210n and/or controller/processor 225, which generates processed baseband signals by filtering, decoding, and/or digitizing the baseband or IF signals. The controller/processor 225 may further process the baseband signals.
Transmit (TX) processing circuitry in the transceivers 210a-210n and/or controller/processor 225 receives analog or digital data (such as voice data, web data, e-mail, or interactive video game data) from the controller/processor 225. The TX processing circuitry encodes, multiplexes, and/or digitizes the outgoing baseband data to generate processed baseband or IF signals. The transceivers 210a-210n up-converts the baseband or IF signals to RF signals that are transmitted via the antennas 205a-205n.
The controller/processor 225 can include one or more processors or other processing devices that control the overall operation of the gNB 102. For example, the controller/processor 225 could control the reception of UL channel signals and the transmission of DL channel signals by the transceivers 210a-210n in accordance with well-known principles. The controller/processor 225 could support additional functions as well, such as more advanced wireless communication functions. For instance, the controller/processor 225 could support beam forming or directional routing operations in which outgoing/incoming signals from/to multiple antennas 205a-205n are weighted differently to effectively steer the outgoing signals in a desired direction. As another example, the controller/processor 225 could support methods for supporting parameter combination for coherent joint transmission. Any of a wide variety of other functions could be supported in the gNB 102 by the controller/processor 225.
The controller/processor 225 is also capable of executing programs and other processes resident in the memory 230, such as an OS. The controller/processor 225 can move data into or out of the memory 230 as required by an executing process.
The controller/processor 225 is also coupled to the backhaul or network interface 235. The backhaul or network interface 235 allows the gNB 102 to communicate with other devices or systems over a backhaul connection or over a network. The interface 235 could support communications over any suitable wired or wireless connection(s). For example, when the gNB 102 is implemented as part of a cellular communication system (such as one supporting 5G/NR, LTE, or LTE-A), the interface 235 could allow the gNB 102 to communicate with other gNBs over a wired or wireless backhaul connection. When the gNB 102 is implemented as an access point, the interface 235 could allow the gNB 102 to communicate over a wired or wireless local area network or over a wired or wireless connection to a larger network (such as the Internet). The interface 235 includes any suitable structure supporting communications over a wired or wireless connection, such as an Ethernet or transceiver.
The memory 230 is coupled to the controller/processor 225. Part of the memory 230 could include a RAM, and another part of the memory 230 could include a Flash memory or other ROM.
Although
As shown in
The transceiver(s) 310 receives from the antenna 305, an incoming RF signal transmitted by a gNB of the network 100. The transceiver(s) 310 down-converts the incoming RF signal to generate an intermediate frequency (IF) or baseband signal. The IF or baseband signal is processed by RX processing circuitry in the transceiver(s) 310 and/or processor 340, which generates a processed baseband signal by filtering, decoding, and/or digitizing the baseband or IF signal. The RX processing circuitry sends the processed baseband signal to the speaker 330 (such as for voice data) or is processed by the processor 340 (such as for web browsing data).
TX processing circuitry in the transceiver(s) 310 and/or processor 340 receives analog or digital voice data from the microphone 320 or other outgoing baseband data (such as web data, e-mail, or interactive video game data) from the processor 340. The TX processing circuitry encodes, multiplexes, and/or digitizes the outgoing baseband data to generate a processed baseband or IF signal. The transceiver(s) 310 up-converts the baseband or IF signal to an RF signal that is transmitted via the antenna(s) 305.
The processor 340 can include one or more processors or other processing devices and execute the OS 361 stored in the memory 360 in order to control the overall operation of the UE 116. For example, the processor 340 could control the reception of DL channel signals and the transmission of UL channel signals by the transceiver(s) 310 in accordance with well-known principles. As another example, the processor 340 could support methods for parameter combination for coherent joint transmission. In some embodiments, the processor 340 includes at least one microprocessor or microcontroller.
The processor 340 is also capable of executing other processes and programs resident in the memory 360. The processor 340 can move data into or out of the memory 360 as required by an executing process. In some embodiments, the processor 340 is configured to execute the applications 362 based on the OS 361 or in response to signals received from gNBs or an operator. The processor 340 is also coupled to the I/O interface 345, which provides the UE 116 with the ability to connect to other devices, such as laptop computers and handheld computers. The I/O interface 345 is the communication path between these accessories and the processor 340.
The processor 340 is also coupled to the input 350, which includes for example, a touchscreen, keypad, etc., and the display 355. The operator of the UE 116 can use the input 350 to enter data into the UE 116. The display 355 may be a liquid crystal display, light emitting diode display, or other display capable of rendering text and/or at least limited graphics, such as from web sites.
The memory 360 is coupled to the processor 340. Part of the memory 360 could include a random-access memory (RAM), and another part of the memory 360 could include a Flash memory or other read-only memory (ROM).
Although
The 3GPP NR specification supports up to 32 CSI-RS antenna ports which enable a gNB to be equipped with a large number of antenna elements (such as 64 or 128). In this case, a plurality of antenna elements is mapped onto one CSI-RS port. For next generation cellular systems such as 5G, the maximum number of CSI-RS ports can either remain the same or increase.
For mmWave bands, although the number of antenna elements can be larger for a given form factor, the number of CSI-RS ports—which can correspond to the number of digitally precoded ports—tends to be limited due to hardware constraints (such as the feasibility to install a large number of ADCs/DACs at mmWave frequencies) as illustrated in
Since the above system utilizes multiple analog beams for transmission and reception (wherein one or a small number of analog beams are selected out of a large number, for instance, after a training duration—to be performed from time to time), the term “multi-beam operation” is used to refer to the overall system aspect. This includes, for the purpose of illustration, indicating the assigned DL or UL transmit (TX) beam (also termed “beam indication”), measuring at least one reference signal for calculating and performing beam reporting (also termed “beam measurement” and “beam reporting”, respectively), and receiving a DL or UL transmission via a selection of a corresponding receive (RX) beam.
The above system is also applicable to higher frequency bands such as >52.6 GHz (also termed the FR4). In this case, the system can employ only analog beams. Due to the O2 absorption loss around 60 GHz frequency (˜10 dB additional loss @100 m distance), larger number of and sharper analog beams (hence larger number of radiators in the array) will be needed to compensate for the additional path loss.
At lower frequency bands such as <1 GHz, on the other hand, the number of antenna elements may not be large in a given form factor due to the large wavelength. As an example, for the case of the wavelength size (λ) of the center frequency 600 MHz (which is 50 cm), it desires 4 m for uniform-linear-array (ULA) antenna panel of 16 antenna elements with the half-wavelength distance between two adjacent antenna elements. Considering a plurality of antenna elements is mapped to one digital port in practical cases, the desirable size for antenna panel(s) at gNB to support a large number of antenna ports such as 32 CSI-RS ports becomes very large in such low frequency bands, and it leads the difficulty of deploying 2-D antenna element arrays within the size of a conventional form factor. This results in a limited number of CSI-RS ports that can be supported at a single site and limits the spectral efficiency of such systems.
Various embodiments of the present disclosure recognize that for a cellular system operating in a sub-1 GHz frequency range (e.g., less than 1 GHz), supporting large number of CSI-RS antenna ports (e.g., 32) at a single location or remote radio head (RRH) or TRP is challenging due to that a larger antenna form factor size is needed at these frequencies than a system operating at a higher frequency such as 2 GHz or 4 GHz. At such low frequencies, the maximum number of CSI-RS antenna ports that can be co-located at a single site (or TRP/RRH) can be limited, for example to 8. This limits the spectral efficiency of such systems. In particular, the MU-MIMO spatial multiplexing gains offered due to large number of CSI-RS antenna ports (such as 32) can't be achieved.
One way to operate a sub-1 GHz system with large number of CSI-RS antenna ports is based on distributing antenna ports at multiple locations (or TRP/RRHs). The multiple sites or TRPs/RRHs can still be connected to a single (common) base unit, hence the signal transmitted/received via multiple distributed TRPs/RRHs can still be processed at a centralized location. This is called distributed MIMO or multi-TRP coherent joint transmission (C-JT).
Various embodiments of the present disclosure recognize that CSI enhancement described in Rel-18 MIMO considers Rel-16/17 Type-II CSI codebook refinements to support mTRP coherent joint transmission (C-JT) operations by considering performance-and-overhead trade-off. Various embodiments of the present disclosure recognize that utilizing codebook subset restriction (CBSR) is one of the ways to manage CSI feedback overhead. Especially, in multi-TRP C-JT scenarios, CBSR could be useful in terms of reducing overhead.
Accordingly, various embodiments of the present disclosure provide mechanisms for CBSR for multi-TRP C-JT scenarios.
One possible approach to resolving the issue is to form multiple TRPs (multi-TRP) or RRHs with a small number of antenna ports instead of integrating all of the antenna ports in a single panel (or at a single site) and to distribute the multiple panels in multiple locations/sites (or TRPs, RRHs). This approach is shown in
As illustrated in
Note that although the present disclosure has mentioned low frequency band systems (sub-1 GHz band) as a motivation for distributed MIMO (or mTRP), the distributed MIMO technology is frequency-band-agnostic and can be useful in mid- (sub-6 GHz) and high-band (above-6 GHz) systems in addition to low-band (sub-1 GHz) systems.
The terminology “distributed MIMO” is used as an illustrative purpose, it can be considered under another terminology such as multi-TRP, mTRP, cell-free network, and so on.
All the following components and embodiments are applicable for UL transmission with CP-OFDM (cyclic prefix OFDM) waveform as well as DFT-SOFDM (DFT-spread OFDM) and SC-FDMA (single-carrier FDMA) waveforms. Furthermore, all the following components and embodiments are applicable for UL transmission when the scheduling unit in time is either one subframe (which can consist of one or multiple slots) or one slot.
In the present disclosure, the frequency resolution (reporting granularity) and span (reporting bandwidth) of CSI reporting can be defined in terms of frequency “subbands” and “CSI reporting band” (CRB), respectively.
A subband for CSI reporting is defined as a set of contiguous PRBs which represents the smallest frequency unit for CSI reporting. The number of PRBs in a subband can be fixed for a given value of DL system bandwidth, configured either semi-statically via higher-layer/RRC signaling, or dynamically via L1 DL control signaling or MAC control element (MAC CE). The number of PRBs in a subband can be included in CSI reporting setting.
“CSI reporting band” is defined as a set/collection of subbands, either contiguous or non-contiguous, wherein CSI reporting is performed. For example, CSI reporting band can include all the subbands within the DL system bandwidth. This can also be termed “full-band”. Alternatively, CSI reporting band can include only a collection of subbands within the DL system bandwidth. This can also be termed “partial band”.
The term “CSI reporting band” is used only as an example for representing a function. Other terms such as “CSI reporting subband set” or “CSI reporting bandwidth” can also be used.
In terms of UE configuration, a UE can be configured with at least one CSI reporting band. This configuration can be semi-static (via higher-layer signaling or RRC) or dynamic (via MAC CE or L1 DL control signaling). When configured with multiple (N) CSI reporting bands (e.g., via RRC signaling), a UE can report CSI associated with n≤N CSI reporting bands. For instance, >6 GHz, large system bandwidth may require multiple CSI reporting bands. The value of n can either be configured semi-statically (via higher-layer signaling or RRC) or dynamically (via MAC CE or L1 DL control signaling). Alternatively, the UE can report a recommended value of n via an UL channel.
Therefore, CSI parameter frequency granularity can be defined per CSI reporting band as follows. A CSI parameter is configured with “single” reporting for the CSI reporting band with Mn subbands when one CSI parameter for all the Mn subbands within the CSI reporting band. A CSI parameter is configured with “subband” for the CSI reporting band with Mn subbands when one CSI parameter is reported for each of the Mn subbands within the CSI reporting band.
As illustrated in
comprise a first antenna polarization, and antenna ports
comprise a second antenna polarization, where PCSIRS is a number of CSI-RS antenna ports and X is a starting antenna port number (e.g., X=3000, then antenna ports are 3000, 3001, 3002, . . . ). Let Ng be a number of antenna panels at the gNB. When there are multiple antenna panels (Ng>1), we assume that each panel is dual-polarized antenna ports with N1 and N2 ports in two dimensions. This is illustrated in
In one example, the antenna architecture of a D-MIMO or CJT (coherent joint-transmission) system is structured. For example, the antenna structure at each RRH (or TRP) is dual-polarized (single or multi-panel as shown in
In another example, the antenna architecture of a D-MIMO or CJT system is unstructured. For example, the antenna structure at one RRH/TRP can be different from another RRH/TRP.
The remainder of the present disclosure assumes a structured antenna architecture. For simplicity, in the remainder of the present disclosure it is assumed that each RRH/TRP is equivalent to a panel, although, an RRH/TRP can have multiple panels in practice. The present disclosure however is not restrictive to a single panel assumption at each RRH/TRP, and can easily be extended (covers) the case when an RRH/TRP has multiple antenna panels.
In one embodiment, an RRH constitutes (or corresponds to or is equivalent to) at least one of the following:
In one example, when RRH or TRP maps (or corresponds to) a CSI-RS resource or resource group, and a UE can select a subset of RRHs (resources or resource groups) and report the CSI for the selected TRPs/RRHs (resources or resource groups), the selected TRPs/RRHs can be reported via an indicator. For example, the indicator can be a CRI or a PMI (component) or a new indicator.
In one example, when RRH or TRP maps (or corresponds to) a CSI-RS port group, and a UE can select a subset of TRPs/RRHs (port groups) and report the CSI for the selected TRPs/RRHs (port groups), the selected TRPs/RRHs can be reported via an indicator. For example, the indicator can be a CRI or a PMI (component) or a new indicator.
In one example, when multiple (K>1) CSI-RS resources are configured for NRRH TRPs/RRHs, a decoupled (modular) codebook is used/configured, and when a single (K=1) CSI-RS resource for NRRH TRPs/RRHs, a joint codebook is used/configured.
As described in U.S. Pat. No. 10,659,118, issued May 19, 2020, and entitled “Method and Apparatus for Explicit CSI Reporting in Advanced Wireless Communication Systems,” which is incorporated herein by reference in its entirety, a UE is configured with high-resolution (e.g., Type II) CSI reporting in which the linear combination-based Type II CSI reporting framework is extended to include a frequency dimension in addition to the first and second antenna port dimensions.
As illustrated,
The basis sets for 1st and 2nd port domain representation are oversampled DFT codebooks of length-N1 and length-N2, respectively, and with oversampling factors O1 and O2, respectively. Likewise, the basis set for frequency domain representation (i.e., 3rd dimension) is an oversampled DFT codebook of length-N3 and with oversampling factor O3. In one example, O1=O2=O3=4. In one example, O1=O2=4 and O3=1. In another example, the oversampling factors O1 belongs to {2, 4, 8}. In yet another example, at least one of O1, O2, and O3 is higher layer configured (via RRC signaling).
As explained in Section 5.2.2.2.6 of REF8, a UE is configured with higher layer parameter codebookType set to ‘typeII-PortSelection-r16’ for an enhanced Type II CSI reporting in which the pre-coders for all SBs and for a given layer l=1, . . . , v, where v is the associated RI value, is given by either
where:
port selection column vector, where a port selection vector is a defined as a vector which contains a value of 1 in one element and zeros elsewhere,
In a variation, when the UE reports a subset K<2LM coefficients (where K is either fixed, configured by the gNB or reported by the UE), then the coefficient cl,i,f in precoder equations Eq. 1 or Eq. 2 is replaced with xl,i,f×cl,i,f, where
The indication whether xl,i,f=1 or 0 is according to some embodiments of this disclosure. For example, it can be via a bitmap.
In a variation, the precoder equations Eq. 1 or Eq. 2 are respectively generalized to
where for a given i, the number of basis vectors is Mi and the corresponding basis vectors are {bi,f}. Note that Mi is the number of coefficients cl,i,f reported by the UE for a given i, where Mi≤M (where {Mi} or ΣMi is either fixed, configured by the gNB or reported by the UE).
The columns of Wl are normalized to norm one. For rank R or R layers (v=R), the pre-coding matrix is given by
Eq. 2 is assumed in the rest of the disclosure. The embodiments of the disclosure, however, are general and are also application to Eq. 1, Eq. 3 and Eq. 4.
Here
then A is an identity matrix, and hence not reported. Likewise, if M=N3, then B is an identity matrix, and hence not reported. Assuming M<N3, in an example, to report columns of B, the oversampled DFT codebook is used. For instance, bf=wf, where the quantity wf is given by
When O3=1, the FD basis vector for layer l∈{1, . . . , v} (where v is the RI or rank value) is given by
where
and n3,l=[n3,l(0), . . . , n3,l(M-1)] where n3,l(f)∈{0, 1, . . . , N3−1}.
In another example, discrete cosine transform DCT basis is used to construct/report basis B for the 3rd dimension. The m-th column of the DCT compression matrix is simply given by
Since DCT is applied to real valued coefficients, the DCT is applied to the real and imaginary components (of the channel or channel eigenvectors) separately. Alternatively, the DCT is applied to the magnitude and phase components (of the channel or channel eigenvectors) separately. The use of DFT or DCT basis is for illustration purpose only. The disclosure is applicable to any other basis vectors to construct/report A and B.
On a high level, a precoder Wl can be described as follows.
where A=W1 corresponds to the Rel. 15 W1 in Type II CSI codebook [REFS], and B=Wf.
The Cl={tilde over (W)}2 matrix consists of all the required linear combination coefficients (e.g., amplitude and phase or real or imaginary). Each reported coefficient (cl,i,f=pl,i,fϕl,i,f) in {tilde over (W)}2 is quantized as amplitude coefficient (pl,i,f) and phase coefficient (ϕl,i,f). In one example, the amplitude coefficient (pl,i,f) is reported using a A-bit amplitude codebook where A belongs to {2, 3, 4}. If multiple values for A are supported, then one value is configured via higher layer signaling. In another example, the amplitude coefficient (pl,i,f) is reported as pl,i,f=pl,i,f(1)pl,i,f(2) where
For layer l, let us denote the linear combination (LC) coefficient associated with spatial domain (SD) basis vector (or beam) i∈{0, 1, . . . , 2L−1} and frequency domain (FD) basis vector (or beam) f∈{0, 1, . . . , M−1} as cl,i,f, and the strongest coefficient as cl,i*,f*. The strongest coefficient is reported out of the KNZ non-zero (NZ) coefficients that is reported using a bitmap, where KNZ≤K0=[β×2LM]<2LM and β is higher layer configured. The remaining 2LM-KNZ coefficients that are not reported by the UE are assumed to be zero. The following quantization scheme is used to quantize/report the KNZ NZ coefficients.
For the polarization r*∈{0, 1} associated with the strongest coefficient cl,i*,f*, we have
and the reference amplitude pl,i,f(1)=pl,r*(1)=1. For the other polarization r∈{0, 1} and r≠r*, we have
mod 2 and the reference amplitude pl,i,f(1)=pl,r(1) is quantized (reported) using the 4-bit amplitude codebook mentioned above.
In Rel. 16 enhanced Type II and Type II port selection codebooks, a UE can be configured to report M FD basis vectors. In one example,
where R is higher-layer configured from {1, 2} and p is higher-layer configured from
In one example, the p value is higher-layer configured for rank 1-2 CSI reporting. For rank >2 (e.g., rank 3-4), the p value (denoted by v0) can be different. In one example, for rank 1-4, (p, v0) is jointly configured from
for rank 1-2 and
for rank 3-4. In one example, N3=NSB×R where NSB is the number of SBs for CQI reporting. In one example, M is replaced with Mv to show its dependence on the rank value v, hence p is replaced with pv, v∈{1, 2} and v0 is replaced with pv, v∈{3, 4}.
A UE can be configured to report Mv FD basis vectors in one-step from N3 basis vectors freely (independently) for each layer l∈{1, . . . , v} of a rank v CSI reporting. Alternatively, a UE can be configured to report Mv FD basis vectors in two-step as follows.
In one example, one-step method is used when N3≤19 and two-step method is used when N3>19. In one example, N3′=[αMv] where α>1 is either fixed (to 2 for example) or configurable.
The codebook parameters used in the DFT based frequency domain compression (Eq. 5) are (L, pv for v∈{1, 2}, pv for v∈{3, 4}, β, α, NPh). The set of values for these codebook parameters are as follows.
In Rel. 17 (further enhanced Type II port selecting codebook), M∈{1, 2},
where K1=α×PCSIRS, and codebook parameters (M, α, β) are configured from Table 2.
The above-mentioned framework (Eq. 5) represents the precoding-matrices for multiple (N3) FD units using a linear combination (double sum) over 2L (or K1) SD beams/ports and Mv FD beams. This framework can also be used to represent the precoding-matrices in time domain (TD) by replacing the FD basis matrix Wf with a TD basis matrix Wt, wherein the columns of Wt comprises Mv TD beams that represent some form of delays or channel tap locations. Hence, a precoder Wl can be described as follows.
In one example, the Mv TD beams (representing delays or channel tap locations) are selected from a set of N3 TD beams, i.e., N3 corresponds to the maximum number of TD units, where each TD unit corresponds to a delay or channel tap location. In one example, a TD beam corresponds to a single delay or channel tap location. In another example, a TD beam corresponds to multiple delays or channel tap locations. In another example, a TD beam corresponds to a combination of multiple delays or channel tap locations.
In one example, the codebook for the CSI report is according to at least one of the following examples.
In one example, when the codebook is a legacy codebook (e.g., one of Rel. 15/16/17 NR codebooks, according to one of the examples above), then the CSI reporting is based on a CSI resource set comprising one or multiple NZP CSI-RS resource(s), where each NZP CSI-RS resource comprises CSI-RS antenna ports for all TRPs/RRHs, i.e., P=Σr=1N Pr, where P is the total number of antenna ports, and Pr is the number of antenna ports associated with r-th TRP. In this case, a TRP corresponds to (or maps to or is associated with) a group of antenna ports.
In one example, when the codebook is a new codebook (e.g., one of the two new codebooks above), then the CSI reporting is based on a CSI resource set comprising one or multiple NZP CSI-RS resource(s).
In one embodiment, a UE is configured with an mTRP (or D-MIMO or C-JT) codebook, via e.g., higher layer parameter codebookType set to ‘typeII-r18-cjt’, which is designed based on Rel-16/17 Type-II codebook. For example, The mTRP codebook has a triple-stage structure which can be represented as W=W1W2WfH, where the component W1 is used to report/indicate a spatial-domain (SD) basis matrix comprising SD basis vectors, the component Wf is used to report/indicate a frequency-domain (FD) basis matrix comprising FD basis vectors, and the component W2 is used to report/indicate coefficients corresponding to SD and FD basis vectors.
In one example, in Rel-16 Type-II codebook, L vectors, vm
In Rel-18 Type-II codebook for multi-TRP, Ln SD basis vectors for each TRP n can be selected/reported, where we denote that Ln is a number of SD basis vectors for TRP n (CSI-RS resource n).
In one embodiment, on the SD basis selection for (Rel-18) Type-II codebook refinement for CJT mTRP, each of the {Ln, n=1, . . . , NTRP} is configured by NW via higher-layer (RRC) signaling, where NTRP is a number of TRPs configured by the NW.
In one example, Ln∈{2, 4, 6}. In one example, Ln∈{1, 2, 4, 6}. In one example, Ln∈{1, 2, 3, 4, 5, 6}. In one example, Ln∈{1, 2, 3, 4}. In one example, Ln∈{1, 2, 3}. In one example, Ln∈{1, 2, 4}. In one example, Ln can be selected from Ln, where Ln is a subset of {1, 2, 3, 4, 5, 6}.
In embodiment 0, on the SD basis selection for (Rel-18) Type-II codebook refinement for CJT mTRP, Lmax≥Σn=1N
In one example, Lmax∈{2NTRP, 4NTRP, 6NTRP}. In one example, Lmax∈{1NTRP, 2NTRP, 4NTRP, 6NTRP}. In one example, Lmax∈{1NTRP, 2NTRP, 3NTRP, 4NTRP, 55NTRP, 6NTRP}. In one example, Lmax∈{1NTRP, 2NTRP, 3NTRP, 4NTRP}. In one example, Lmax∈{1NTRP, 2NTRP, 3NTRP}.
In one example, Lmax∈{1NTRP, 2NTRP, 4NTRP}. In one example, Lmax can be selected from max, where max is a subset of {1, . . . , 24}.
In one example, Lmax∈max,1 for NTRP≥x and Lmax∈max,2 for NTRP<x, where max,1 and max,2 is a subset of {1, . . . , 24} and x=1, 2, 3, or 4.
In one example, Lmax∈max,1 for NTRP>x and Lmax∈max,2 for NTRP≤x, where max,1 and max,2 is a subset of {1, . . . , 24} and x=1, 2, 3, or 4.
In example 0.1, {Ln, n=1, . . . , NTRP} are explicitly reported via a joint indicator or separate multiple indicators in CSI part 1. For example, a joint indicator can be used to indicate (L1, . . . , LN
In one example, Ln SD basis vector selection for each TRP n is reported via a joint indicator or separate multiple indicators in CSI part 2.
(bit-width), where N1 and N2 are the values of (N1, N2) configured via higher-layer (RRC) signaling by the NW. For any TRP n where Ln=0 (i.e., no SD beam selection case) and/or where TRP n is not selected which can be indicated via NTRP-bit bitmap in CSI part 1, no SD basis vector for TRP n is reported, hence no payload is induced.
(bit-width). For any TRP n where Ln=0 (i.e., no SD beam selection case) and/or where TRP n is not selected which can be indicated via NTRP-bit bitmap in CSI part 1, no SD basis vector for TRP n is reported, hence no additional payload is induced in the sum.
In one example, Lns associated with TRPs that are selected are explicitly reported via a joint indicator or separate multiple indicators in CSI part 1. In CSI part 1, NTRP-bit bitmap is used to indicate selected N TRPs out of NTRP TRPs. For example, when NTRP=4 and NTRP-bit bitmap is ‘1001’ in CSI part 1, the first TRP and the fourth TRP are selected. In this example, Ln associated with the selected TRPs are explicitly reported.
In one example, Ln SD basis vector selection for each TRP n is reported via a joint indicator or separate multiple indicators in CSI part 2.
(bit-width), where N1 and N2 are the values of (N1, N2) configured via higher-layer (RRC) signaling by the NW, where n∈S or n=1, . . . , N.
In one example, Lns associated with TRPs that are selected are explicitly reported via a joint indicator or separate multiple indicators in CSI part 2. The remaining part is similar to other examples described herein. For example, when NTRP=4 and NTRP-bit bitmap is ‘1001’ in CSI part 1, the first TRP and the fourth TRP are selected. In this example, Ln associated with the selected TRPs are explicitly reported.
In one example, Ln SD basis vector selection for each TRP n is reported via a joint indicator or separate multiple indicators in CSI part 2.
(bit-width), where N1 and N2 are the values of (N1, N2) configured via higher-layer (RRC) signaling by the NW, where n∈S or n=1, . . . , N.
In one embodiment, Ltot is determined the UE where Lmax≥Ltot==n=1N
In one example, Ltot∈{2NTRP, 4NTRP, 6NTRP}. In one example, Ltot∈{1NTRP, 2NTRP, 4NTRP, 6NTRP}. In one example, Ltot∈{1NTRP, 2NTRP, 3NTRP, 4NTRP, 5NTRP, 6NTRP}. In one example, Ltot∈{1NTRP, 2NTRP, 3NTRP, 4NTRP}. In one example, Ltot∈{1NTRP, 2NTRP, 3NTRP}.
In one example, Ltot∈{1NTRP, 2NTRP, 4NTRP}. In one example, Ltot can be selected from a subset of {1, . . . , 24}.
In one example, Ltot∈{2NTRP, 4NTRP, 6NTRP}∩{1, 2, . . . , Lmax}. In one example, Ltot∈{1NTRP, 2NTRP, 4NTRP, 6NTRP}∩{1, 2, . . . , Lmax}. In one example, Ltot∈{1NTRP, 2NTRP, 3NTRP, 4NTRP, 5NTRP, 6NTRP}∩{1, 2, . . . , Lmax}. In one example, Ltot∈{1NTRP, 2NTRP, 3NTRP, 4NTRP}∩{1, 2, . . . , Lmax}. In one example, Ltot∈{1NTRP, 2NTRP, 3NTRP}∩{1, 2, . . . , Lmax}.
In one example, Ltot∈{1NTRP, 2NTRP, 4NTRP}∩{1, 2, . . . , Lmax}. In one example, Ltot can be selected from a subset of {1, . . . , 24}∩{1, 2, . . . , Lmax}.
In one example, some of {Ln, n=1, . . . , NTRP} are explicitly reported via a joint indicator or separate multiple indicators in CSI part 1 and the others of {Ln, n=1, . . . , NTRP} are reported implicitly (or determined implicitly hence not explicitly reported).
In one example, Ln SD basis vector selection for each TRP n is reported via a joint indicator or separate multiple indicators in CSI part 2. (Similar to/same as example 0.1.1)
(bit-width), where N1 and N2 are the values of (N1, N2) configured via higher-layer (RRC) signaling by the NW. For any TRP n where Ln=0 (i.e., no SD beam selection case) and/or where TRP n is not selected which can be indicated via NTRP-bit bitmap in CSI part 1, no SD basis vector for TRP n is reported, hence no payload is induced.
(bit-width). For any TRP n where Ln=0 (i.e., no SD beam selection case) and/or where TRP n is not selected which can be indicated via NTRP-bit bitmap in CSI part 1, no SD basis vector for TRP n is reported, hence no additional payload is induced in the sum.
In one example, Ltot SD basis vectors are selected among all candidates of SD basis vectors across NTRP TRPs and the selection of Ltot SD basis vectors is reported via an indicator with size of
in CSI part 1. In this case, Ln is implicitly determined by counting the number of selected SD basis vectors that belong to the candidate SD basis vectors of each TRP.
In one example, Ltot SD basis vectors are selected among all candidates of SD basis vectors across NTRP TRPs and the selection of Ltot SD basis vectors is reported via an indicator with size of
in CSI part 2. In this case, Ln is implicitly determined by counting the number of selected SD basis vectors that belong to the candidate SD basis vectors of each TRP.
In one example, Ltot SD basis vectors are selected among all candidates of SD basis vectors across N TRPs, where N is a number of selected TRPs. For example, in CSI part 1, NTRP-bit bitmap is used to indicate selected N TRPs out of NTRP TRPs. For example, when NTRP=4 and NTRP-bit bitmap is ‘1001’ in CSI part 1, the first TRP and the fourth TRP are selected. The selection of Ltot SD basis vectors is reported via an indicator with size of
in CSI part 1. In this case, Ln is implicitly determined by counting the number of selected SD basis vectors that belong to the candidate SD basis vectors of each of the selected TRPs.
In one example, Ltot SD basis vectors are selected among all candidates of SD basis vectors across N TRPs, where N is a number of selected TRPs. For example, in CSI part 1, NTRP-bit bitmap is used to indicate selected N TRPs out of NTRP TRPs. For example, when NTRP=4 and NTRP-bit bitmap is ‘1001’ in CSI part 1, the first TRP and the fourth TRP are selected. The selection of Ltot SD basis vectors is reported via an indicator with size of
in CSI part 2. In this case, Ln is implicitly determined by counting the number of selected SD basis vectors that belong to the candidate SD basis vectors of each of the selected TRPs.
In one embodiment, Ltot is determined by UE where Lmax≥Ltot=Σn=1N Ln (or Lmax≥Ltot=Σn∈S Ln), and the determined Ltot is reported in CSI part 1. Here, N is a number of selected TRPs out of NTRP TRPs and S is a set of selected TRP indexes (i.e., a subset of {1, 2, . . . , NTRP}). Note that in CSI part 1, NTRP-bit bitmap can be used to indicate selected N TRPs out of NTRP TRPs. In one example, an indicator to indicate Ltot has the size of payload [log2 Lmax] bits, i.e., Ltot is selected from {1, 2, . . . , Lmax}. In another example, an indicator to indicate Ltot has the size of payload [log2|Ltot|] bits, where tot is a set including Lmax and positive integers less than or equal to Lmax, and |tot| is a number of the elements in tot. In one example, tot can be any subset of {1, 2, . . . , Lmax}. In one example, tot can be any subset of
In one example, an indicator to indicate Ltot has the size of payload
i.e., Ltot is selected from
In one example, Ltot∈{2N, 4N, 6N}. In one example, Ltot∈{1N, 2N, 4N, 6N}. In one example, Ltot∈{1N, 2N, 3N, 4N, 5N, 6N}. In one example, Ltot∈{1N, 2N, 3N, 4N}. In one example, Ltot∈{1N, 2N, 3N}.
In one example, Ltot∈{1N, 2N, 4N}. In one example, Ltot can be selected from a subset of {1, . . . , 24}.
In one example, Ltot∈{2N, 4N, 6N}∩{1, 2, . . . , Lmax}. In one example, Ltot∈{1N, 2N, 4N, 6N}∩{1, 2, . . . , Lmax}. In one example, Ltot∈{1N, 2N, 3N, 4N, 5N, 6N}∩{1, 2, . . . , Lmax}. In one example, Ltot∈{1N, 2N, 3N, 4N}∩{1, 2, . . . , Lmax}. In one example, Ltot∈{1N, 2N, 3N}∩{1, 2, . . . , Lmax}.
In one example, Ltot∈{1N, 2N, 4N}∩{1, 2, . . . , Lmax}. In one example, Ltot can be selected from a subset of {1, . . . , 24}∩{1, 2, . . . , Lmax}.
In one example, some of Ls associated with TRPs that are selected are explicitly reported via a joint indicator or separate multiple indicators in CSI part 1 and the others of Ls associated with TRPs that are selected are reported implicitly (or determined implicitly hence not explicitly reported). In CSI part 1, NTRP-bit bitmap is used to indicate selected N TRPs out of NTRP TRPs. For example, when NTRP=4 and NTRP-bit bitmap is ‘1001’ in CSI part 1, the first TRP and the fourth TRP are selected. In this example, some of Ln associated with the selected TRPs are explicitly reported and the others are implicitly determined.
In one example, Ln SD basis vector selection for each TRP n is reported via a joint indicator or separate multiple indicators in CSI part 2. (Similar to/same as example 0.1A.1)
(bit-width), where N1 and N2 are the values of (N1, N2) configured via higher-layer (RRC) signaling by the NW, where n∈S or n=1, . . . , N.
In one example, some of Lns associated with TRPs that are selected are explicitly reported via a joint indicator or separate multiple indicators in CSI part 2 and the others of Lns associated with TRPs that are selected are reported implicitly (or determined implicitly hence not explicitly reported). The remaining part is similar to example 0.2A.1 (examples under example 0.2A.1).
In one example, Ltot SD basis vectors are selected among all candidates of SD basis vectors across N TRPs. The selection of Ltot SD basis vectors is reported via an indicator with size of
in CSI part 1. In this case, Ln is implicitly determined by counting the number of selected SD basis vectors that belong to the candidate SD basis vectors of each of the selected TRPs.
In one example, Ltot SD basis vectors are selected among all candidates of SD basis vectors across N TRPs. The selection of Ltot SD basis vectors is reported via an indicator with size of
in CSI part 2. In this case, Ln is implicitly determined by counting the number of selected SD basis vectors that belong to the candidate SD basis vectors of each of the selected TRPs.
In one embodiment, a bitmap with size of NN1N2 is used to indicate SD basis vectors for selected N TRPs (CSI-RS resources) in CSI part 2. For example, in the bitmap, ‘0’ refers ‘not selected’ for corresponding SD vector and ‘1’ refers ‘selected’ for corresponding SD vector. In this case, Ln can be inferred from the bitmap, by counting the number of selected SD vectors corresponding to each TRP. In this case, a restriction can be described such as “UE shall not report a CSI with Ltot=Σn Ln>Lmax, where Ln is inferred from the bitmap”.
In one embodiment, in all embodiments/examples under embodiment 0, Ln, Ltot, Lmax can be replaced by αn, αtot, αmax where
On Parameter Combination Table with Lmax (Ltot or Lsum), pv, Beta
In one embodiment, a UE is configured with a CSI report (e.g., via higher layer CSI-ReportConfig) based on a codebook for C-JT transmission from multiple TRPs, as described in this disclosure, where codebook parameters (such as α or L, β, pv or Mv) are configured via a higher-layer parameter ‘paramCombination-r18’ or ‘paramCombinationCJT-r18’.
Any table including at least one of the combinations provided in the (sub)-tables in this disclosure can be an example for the table of ‘paraCombination-r18’.
In one embodiment, a table used for ‘paramCombination-r18’ is designed based on the following parameter candidates:
In one example, the parameter names in (or related to) any table of this disclosure can be written in different names of parameters. For example, Lmax can be replaced by Ltot. For example, NTRP can be replaced by N.
In one example, any table including at least one of the combinations provided in the tables in this disclosure can be an example for the table of ‘paraCombination-r18’.
In Table 3, some rows were omitted for the sake of space limitation. The values in the omitted rows can clearly be determined based on earlier rows. Also, the table index numbers (from 1 to 1200) in Table 3 should be interpreted as just indexes for corresponding parameter combinations. That is, the table index number can be any value based on the ordering of parameter combinations and the number of parameter combinations in a table.
In one example, any sub-table of Table 3 can be an example for the table of ‘paraCombination-r18’.
In one embodiment, any table including at least one of parameter combinations in a sub-table of Table 3 can be used for the table of ‘paramCombination-r18’, where the sub-table includes parameter combinations associated with Lmax∈max, where max is a subset of max. For example, if max={8, 10, 12, 14, 16}, the sub-table includes the parameter combinations associated with Lmax=8, 10, 12, 14, 16 in Table 3.
In one embodiment, max can be defined for each value of NTRP={1, 2, 3, 4}, and the sub-table includes parameter combinations associated with Lmax∈max in Table 3 for each value of NTRP={1, 2, 3, 4}.
In one example, max can be defined as follow and the sub-table includes parameter combinations associated with max for each value of NTRP:
In one example, max can be defined as follow and the sub-table includes parameter combinations associated with max for each value of NTRP:
In one example, max can be defined as follow and the sub-table includes parameter combinations associated with max for each value of NTRP:
In one embodiment, any table including at least one of parameter combinations in a sub-table of Table 3 can be used for the table of ‘paramCombination-r18’, where the sub-table includes parameter combinations associated with ({pv}v=1,2, {pv}v=3,4)∈, where is a subset of , where ={(x, y)|x∈12, y∈34}. For example, if
the sub table includes the parameter combinations associated with
and the sub-table includes parameter combinations associated with if
and the Sub-table includes parameter combinations associated with if
and the sub table includes parameter combinations associated with if
and the sub-table includes parameter combinations associated with if
In one embodiment, any table including at least one of parameter combinations in a sub-table of Table 3 can be used for the table of ‘paramCombination-r18’, where the sub-table includes combinations associated with β∈, where is a subset of . For example, if
the sub table includes the parameter combinations associated with
and the sub-table includes parameter combinations associated with
and the sub table includes parameter combinations associated with
and the sub-table includes parameter combinations associated with
and the sub-table includes parameter combinations associated with
and the sub table includes parameter combinations associated with
In one embodiment, any table including at least one of parameter combinations in a sub-table of Table 3 can be used for the table of ‘paramCombination-r18’, where the sub-table includes parameter combinations associated with Lmax∈max and ({pv}v=1,2, {pv}v=3,4)∈ and β∈, where Lmax∈max is defined in embodiment 1.1.1, ({pv}v=1,2, {pv}v=3,4)∈ is defined in one or more embodiments herein, and β∈ is defined in one or more embodiments herein.
In one example, the sub-table includes parameter combinations associated with:
In one embodiment, a subset of parameter combinations in a table designed based on one or more embodiments herein for the table of ‘paramCombination-r18’ can be restricted not to configure based on one or more aspects such as a number of TRPs (NTRP), a number of SBs K (numberOfPMI-SubbandsPerCQI-Subband), and a number of CSI-RS ports (N1N2 or PCSI-RS).
In one example, the parameter combination with Ln=4 and/or 6 for any n can be used/reported (by the UE) or configured (by the NW) under a condition.
In one example, the parameter combination with pv=½ for any n can be used/reported (by the UE) or configured (by the NW) under a condition.
In one example, the parameter combination with pv=⅙ and/or pv=⅛ for any n can be used/reported (by the UE) or configured (by the NW) under a condition.
In one example, the parameter combination with β=½ and/or ¾ and/or 1 for any n can be used/reported (by the UE) or configured (by the NW) under a condition.
In one example, the parameter combination with Ln=4 and/or 6 and/or pv=½ and/or ⅛ and/or ⅙ for any n can be used/reported (by the UE) or configured (by the NW) under a condition.
In one example, the parameter combination with Ln=4 and/or 6 and/or β=½ and/or ¾ and/or 1 for any n can be used/reported (by the UE) or configured (by the NW) under a condition.
In one example, the parameter combination with pv=½ and/or ⅛ and/or ⅙ and/or β=½ and/or ¾ and/or 1 for any n can be used/reported (by the UE) or configured (by the NW) under a condition.
In one example, the parameter combination with Ln=4 and/or 6 and/or pv=½ and/or ⅛ and/or 1/16 and/or β=½ and/or ¾ and/or 1 for any n can be used/reported (by the UE) or configured (by the NW) under a condition.
In one embodiment, on the SD basis selection for (Rel-18) Type-II codebook refinement for CJT mTRP, each of the {Ln, n=1, . . . , NTRP} is configured by NW via higher-layer (RRC) signaling, where NTRP is a number of TRPs configured by the NW.
In one example, Ln∈{2, 4, 6}. In one example, Ln∈{1, 2, 4, 6}. In one example, Ln∈{1, 2, 3, 4, 5, 6}. In one example, Ln∈{1, 2, 3, 4}. In one example, Ln∈{1, 2, 3}. In one example, Ln∈{1, 2, 4}. In one example, Ln can be selected from n, where n is a subset of {1, 2, 3, 4, 5, 6}.
In one embodiment, on the SD basis selection for (Rel-18) Type-II codebook refinement for CJT mTRP, a value of Lmax, where Lmax≥Σn=1N
In one embodiment, on the SD basis selection for (Rel-18) Type-II codebook refinement for CJT mTRP, a set of NL>1 combinations of values for {Ln, n=1, . . . , NTRP} is configured by NW via higher-layer (RRC) signaling, where NTRP is a number of TRPs (CSI-RS resources) configured by the NW. The NL combinations of value(s) for {Ln, n=1, . . . , NTRP} can be signaled by using a joint indicator or multiple separate indicators. In one example, NL=1. In another example, NL>1.
In one example, Ln∈{2, 4, 6}. In one example, Ln∈{1, 2, 4, 6}. In one example, Ln∈{1, 2, 3, 4, 5, 6}. In one example, Ln∈{1, 2, 3, 4}. In one example, Ln∈{1, 2, 3}. In one example, Ln∈{1, 2, 4}. In one example, Ln can be selected from n, where n is a subset of {1, 2, 3, 4, 5, 6}.
In one example, {Ln} values can be configured based on at least one of the tables (or any table (i.e., sub-table, whole table) that can be constructed as) described in this disclosure.
In one example, NL can be explicitly configured via higher-layer (RRC) signaling with a separate parameter. The possible values for NL are a set of , i.e.; one of the values is selected from . Let denote a total number of a table including combinations of values for {Ln, n=1, . . . , NTRP} by NT. In one example,
size parameter can be configured to indicate NL combinations of values for {Ln, n=1, . . . , NTRP}. In one example, the table can be any table (whole table or sub-table) described in this disclosure or any table that can be constructed as described in this disclosure. In one example, the table can be any table described in this disclosure (or any table that can be constructed as described in this disclosure) wherein N is replaced by NTRP. In one example, the table can be any table described in this disclosure (or any table that can be constructed as described in this disclosure) wherein Ltot is replaced by Lmax. In one example, when N is replaced by NTRP in the table, a UE applies Ln for CSI-RS resource (or TRP index) n, for n=1, . . . , NTRP. For example, when an NTRP-bit bitmap for TRP selection is reported, the UE uses Ln values for n values corresponding to the selected TRPs only, which are indicated in the bitmap.
In one example, NL is implicitly determined or configured via higher-layer RRC signaling.
In one example, when NL>1, a UE reports an indicator with the size of [log2 NL]-bit to indicate one selected combination of values for {Ln, n=1, . . . , NTRP} in CSI part 1.
In one example, when NL=1, a UE follows the configured {Ln} values, hence not reported.
In one example, NL combinations of {Ln} is subject to the UE capability on Ltot or Lmax.
When N=NTRP is configured, (a) can be applied. When N=NTRP is not configured (i.e., N<=NTRP), (b) can be applied.
When N=NTRP is configured, one example above can be applied. When N=NTRP is not configured (i.e., N<=NTRP), another example above can be applied.
Table 4 can be used for configuring {Ln} values (or Ltot=Σn Ln). In one example, only a subset of the table is used/configured. For example, the portion of the table corresponding to Ltot>t can't be used, where t is threshold that can be fixed (e.g., 18 or 20 or 22 or 24), or configured, or reported by the UE (via UE capability).
In one example, NW can configure the sub-table of Table 4 associated with N≤NTRP and selects/indicates/configures one index in the sub-table.
When N<NTRP is selected (via NTRP-bit bitmap), the indexes of the selected TRPs (or CSI-RS resources) can be remapped to 1 to N, which will be corresponding to the indexes of indicated {Ln}. In one example, from the lowest index to highest index for the selected TRPs, their indexes are remapped to 1 to N. For example, when NTRP=4 and the 4-bit bitmap indicator for TRP selection is ‘0101’ (assuming LSB corresponds to TRP 1 . . . MSB corresponds to TRP 4), the selected TRP 1 and TRP 3 are associated with L1 and L2, respectively. In another example, from the highest index to lowest index for the selected TRPs, their indexes are remapped to 1 to N. For example, when NTRP=4 and the 4-bit bitmap indicator for TRP selection is ‘0101’ (assuming LSB corresponds to TRP 1 . . . MSB corresponds to TRP 4), the selected TRP 3 and TRP 1 are associated with L1 and L2, respectively. In another example, the selected TRP indexes are not remapped (i.e., the selected TRP 3 and TRP 1 are associated with L1 and L3, respectively).
In one embodiment, a NW considers a sub-table of Table 4 associated with {Ln} such that Ln1≥Ln2 (non-increasing order) when n1<n2, and selects/indicates/configures one index in the sub table.
In one embodiment, a NW considers a sub-table of Table 4 associated with {Ln} such that Ln1<Ln2 (non-decreasing order) when n1<n2, and selects/indicates/configures one index in the sub table.
In one example, the ordering of the TRP can be configured by NW, via e.g., RRC, or MAC CE or, DCI.
In another example/embodiment, Ln can allow 0 in addition to {2, 4, 6}. For example, Table 4 can be used for the above/below examples/embodiments or the examples/embodiments that are related to Table 5.
In one embodiment, a NW considers a sub-table including at least one of the rows in Table 4 or Table 5.
The above approach described for the cases of Ln∈{2, 4, 6} can be extended to the case of any subset of {1, 2, 3, 4, 5, 6} in the same manner. The tables provided in this disclosure can include different parameter names, e.g., N can be replaced by NTRP and/or Ltot can be replaced by Lmax. The parameter names can be used interchangeably. For the sake of space limitation, we omitted those in this disclosure, but it should be interpreted as those variations being included in the present disclosure.
In one embodiment, any combination or some of embodiments described herein can be configured by NW via higher-layer (RRC) signaling. In one example, any combination or some of examples in embodiments described herein can be configured by NW via higher-layer RRC signaling.
In one embodiment, one or more embodiments herein can be configured by NW via higher-layer (RRC) signaling.
In one embodiment, one or more embodiments herein can be used only when N=NTRP is configured, and one or more embodiments can be used otherwise.
In one embodiment, one or more embodiments can be used only when N=NTRP is configured, and one or more embodiments can be used otherwise.
In one embodiment, on the SD basis selection for (Rel-18) Type-II codebook refinement for CJT mTRP (Rel-17 port-selection codebook-based refinement), embodiments in this disclosure are also used for Rel-17 port selection codebook-based refinement. For example, Ln, Ltot, Lmax can be replaced by αn, αtot, αmax where
Two Separate Parameter Combination Tables with Linkage (Parameter)
In one embodiment, a UE is configured with an mTRP (or D-MIMO or C-JT) codebook, via e.g., higher layer parameter codebookType set to ‘typeII-r18-cjt’, wherein codebook parameters for the mTRP codebook are configured using two (parameter-combination) tables.
In one embodiment, a first table is one of the tables (or whole tables/sub-tables, or tables that can be constructed) in/under one or more embodiments herein, and a second table is one of the tables (or whole tables/sub-tables, or tables that can be constructed) in/under another embodiment herein (or vice versa). For example, a first table is used to configure a combination of {Ln}, and a second table is used to configure a combination of (pv, β) or vice versa.
In one embodiment, the two tables can be linked using a (overlapping) parameter that is a function of {Ln}.
In one example, the NW can configure index X in a first table and index Y among indices associated with a value of the linked parameter in a second table. Here, the value of linked parameter is the value associated with index X of the first table.
As an example, by using the illustration shown in
Two Separate Parameter Combination Tables without Linkage (Parameter)
In one embodiment, a UE is configured with an mTRP (or D-MIMO or C-JT) codebook, via e.g., higher layer parameter codebookType set to ‘typeII-r18-cjt’, wherein codebook parameters for the mTRP codebook are configured using two (parameter-combination) tables.
In one embodiment, a first table is one of the tables (or whole tables/sub-tables, or tables that can be constructed) in/under embodiments described herein, and a second table is one of the tables (or whole tables/sub-tables, or tables that can be constructed) in/under another embodiment described herein (or vice versa). For example, a first table is used to configure a combination of {Ln}, and a second table is used to configure a combination of (pv, β) (or vice versa).
In one example, a table for (pv, β) can be one of the tables (or whole tables/sub-tables, or tables that can be constructed) in/under embodiments described herein without the column of Lmax (or L) as shown in
In one example, a table for {Ln} can be in a form as illustrated in
In another example, a table for {Ln} can be in a form as illustrated in
In this embodiment, there can be no linkage between two tables. In other words, the NW can configure index X in a first table and index Y in a second table, without using linkage.
In one embodiment, there can be UE capability on Lmax or Ltot or max {Ln} or min {Ln}.
For any embodiment described herein, there can be UE capability on Lmax or Ltot or max {Ln} or min {Ln}, as shown in this embodiment or one of the examples above.
In one embodiment, a table for (pv, β) (which can be one of the possible tables described in this disclosures) includes at least one of the (pv, β) combinations shown in the following table:
In one example, a in C11 is fixed, e.g., ½ or (½+¾)/2=⅝. In another example, a is ¼ or ⅛.
In one example, b in C12 is fixed, e.g., ¼ or (½+¼)/2=⅜. In another example, b is ⅛.
In one example, a supported number of combinations for the table of (pv, β) is at most S, e.g., S=8, and at least T of C2-C5 combinations, where 1≤T≤4, or one of C2-C5 or all of C2-C5 combinations in Table 6 are included in the at most S combinations. In addition, among the remaining (12-T) combinations in Table 6 (i.e., C1, C7-C12), at least one combination is/are included the at most S combinations. In one example, all of C2-C5 combinations in Table 6 are included (i.e., T=4) in the at most S combinations.
examples are omitted.)
examples are omitted.)
examples are omitted.)
examples are omitted.)
examples are omitted.)
examples are omitted.)
In one example (D1), there is restriction on configuring C7 in Table 6, where the restriction is associated with (related to/based on) {Ln}.
For example, x can be only one of x=2, x=4, or x=6.
For example, x can be only one of x=2, x=4, or x=6.
For example, x can be only one of x=2, x=4, or x=6.
For example, x can be only one of x=2, x=4, or x=6.
For example, x can be only one of x=2, x=4, or x=6.
For example, x can be only one of x=2, x=4, or x=6.
For example, x can be only one of x=2, x=4, or x=6.
In one example, the UE is not expected to be configured with C7 when
For example, x can be only one of x=2, x=4, or x=6.
For example, x can be only one of x=2, x=4, or x=6.
For example, x can be only one of x=2, x=4, or x=6.
For example, x can be only one of x=2, x=4, or x=6.
For example, x can be only one of x=2, x=4, or x=6.
For example, x can be only one of x=2, x=4, or x=6. For example, y can be only one of y=2, y=4, or y=6.
For example, x can be only one of x=2, x=4, or x=6. For example, y can be only one of y=2, y=4, or y=6.
For example, x can be only one of x=2, x=4, or x=6. For example, y can be only one of y=2, y=4, or y=6.
For example, x can be only one of x=2, x=4, or x=6. For example, y can be only one of y=2, y=4, or y=6.
For example, x can be only one of x=2, x=4, or x=6. For example, y can be only one of y=2, y=4, or y=6.
For example, x can be only one of x=2, x=4, or x=6. For example, y can be only one of y=2, y=4, or y=6.
For example, x can be only one of x=2, x=4, or x=6. For example, y can be only one of y=2, y=4, or y=6.
For example, x can be only one of x=2, x=4, or x=6. For example, y can be only one of y=2, y=4, or y=6.
In one example, regarding example D1-L, S0 can be per (pv, β) combination, i.e., above case it is for C7 (or any other (pv, β) combination). For example, linkage between a list/table of {Ln} combinations (which can be one of the possible tables described in this disclosures) and a list/table of (pv, β) combinations (which can be one of the possible tables described in this disclosures) can be via pairing each combination for (pv, β) with at least one combination for {Ln}. For example, S0, . . . , SS-1 index sets can be used for linking each combination for (pv, β) with at least one combination for {Ln}.
In one example (D1-a), there is restriction on configuring C7 according to one of the examples above. In addition, the restriction is UE-optional, i.e., the restriction is on/off depending on UE capability. The UE reports its capability on the restriction, whether it is needed or not, and the NW then follows the reported UE capability.
In one example (D1-b), there is restriction on configuring C7 according to one of the examples above. In addition, the C7 is UE-optional, i.e., C7 can be configured depending on UE capability. The UE reports its capability on the support of C7, and then only the NW can configure C7. This UE-optional feature can correspond to a separate UE capability.
In one example (D2), there is restriction on configuring C7 in Table 6, where the restriction is associated with (related to/based on) NL.
In one example (D2-a), there is restriction on configuring C7 according to one of the examples above. In addition, the restriction is UE-optional, i.e., the restriction is on/off depending on UE capability. The UE reports its capability on the restriction, whether it is needed or not, and the NW then follows the reported UE capability.
In one example (D2-b), there is restriction on configuring C7 according to one of the examples above. In addition, the C7 is UE-optional, i.e., C7 can be configured depending on UE capability. The UE reports its capability on the support of C7, and then only the NW can configure C7. This UE-optional feature can correspond to a separate UE capability.
In one example (D3), there is restriction on configuring C7 in Table 6, where the restriction is associated with (related to/based on) PCSI-RS. In one example, PCSI-RS is a number of CSI-RS ports per CSI-RS-resource (per TRP).
In one example (D3-a), there is restriction on configuring C7 according to one of the examples above. In addition, the restriction is UE-optional, i.e., the restriction is on/off depending on UE capability. The UE reports its capability on the restriction, whether it is needed or not, and the NW then follows the reported UE capability.
In one example (D3-b), there is restriction on configuring C7 according to one of the examples above. In addition, the C7 is UE-optional, i.e., C7 can be configured depending on UE capability. The UE reports its capability on the support of C7, and then only the NW can configure C7. This UE-optional feature can correspond to a separate UE capability.
In one example (D4), there is restriction on configuring C7 in Table 6, where the restriction is associated with (related to/based on) v, where v is a number of layers, i.e., rank.
In one example (D4-a), there is restriction on configuring C7 according to one of the examples above. In addition, the restriction is UE-optional, i.e., the restriction is on/off depending on UE capability. The UE reports its capability on the restriction, whether it is needed or not, and the NW then follows the reported UE capability.
In one example (D4-b), there is restriction on configuring C7 according to one of the examples above. In addition, the C7 is UE-optional, i.e., C7 can be configured depending on UE capability. The UE reports its capability on the support of C7, and then only the NW can configure C7. This UE-optional feature can correspond to a separate UE capability.
In one example (D5), there is restriction on configuring C7 in Table 6, where the restriction is associated with (related to/based on) R, where R is a number of precoders per subband.
In one example (D5-a), there is restriction on configuring C7 according to one of the examples above. In addition, the restriction is UE-optional, i.e., the restriction is on/off depending on UE capability. The UE reports its capability on the restriction, whether it is needed or not, and the NW then follows the reported UE capability.
In one example (D5-b), there is restriction on configuring C7 according to one of the examples above. In addition, the C7 is UE-optional, i.e., C7 can be configured depending on UE capability. The UE reports its capability on the support of C7, and then only the NW can configure C7. This UE-optional feature can correspond to a separate UE capability.
In one example (D6), there is restriction on configuring C7 in Table 6, where the restriction is associated with (related to/based on) NTRP, where NTRP is a number of TRPs, i.e., a number of CSI-RS resources.
In one example (D6-a), there is restriction on configuring according to one of the examples above. In addition, the restriction is UE-optional, i.e., the restriction is on/off depending on UE capability. The UE reports its capability on the restriction, whether it is needed or not, and the NW then follows the reported UE capability.
In one example (D6-b), there is restriction on configuring C7 according to one of the examples above. In addition, the C7 is UE-optional, i.e., C7 can be configured depending on UE capability. The UE reports its capability on the support of C7, and then only the NW can configure C7. This UE-optional feature can correspond to a separate UE capability.
In one example (D7), there is restriction on configuring C7 in Table 6, where the restriction is associated with (related to/based on) K, where K is a number of subbands.
In one example (D7-a), there is restriction on configuring according to one of the examples above. In addition, the restriction is UE-optional, i.e., the restriction is on/off depending on UE capability. The UE reports its capability on the restriction, whether it is needed or not, and the NW then follows the reported UE capability.
In one example (D7-b), there is restriction on configuring C7 according to one of the examples above. In addition, the C7 is UE-optional, i.e., C7 can be configured depending on UE capability. The UE reports its capability on the support of C7, and then only the NW can configure C7. This UE-optional feature can correspond to a separate UE capability.
In one example (any combination of D1-D7 (D1-a-D7-a, D1-b-D7-b), there are multiple restrictions on configuring C7 in Table 6, where the multiple restrictions include at least one of the restrictions D1-D7 (D1-a to D7-a, D1-b-D7-b), described above. The multiple restrictions are associated with (related to/based on) {Ln}, NL, PCSI-RS, v, R, NTRP, and/or K.
In one example, in addition to the multiple restrictions, as described above, the combination C7 can only be configured when the UE reports via UE a separate UE capability that it can support C7.
In one example (similar to each of the above examples), there is restriction on configuring C8 in Table 6, where the restriction is associated with (related to/based on) {Ln}, NL, PCSI-RS, v, R, NTRP, and/or K.
In one example (similar to each of the above examples), there is restriction on configuring C9 in Table 6, where the restriction is associated with (related to/based on) {Ln}, NL, PCSI-RS, v, R, NTRP, and/or K
In one example (similar to each of the above examples), there is restriction on configuring C10 in Table 6, where the restriction is associated with (related to/based on) {Ln}, NL, PCSI-RS, v, R, NTRP, and/or K.
In one example (similar to each of the above examples), there is restriction on configuring C11 in Table 6, where the restriction is associated with (related to/based on) {Ln}, NL, PCSI-RS, v, R, NTRP, and/or K.
In one example (similar to each of the above examples), there is restriction on configuring C12 in Table 6, where the restriction is associated with (related to/based on) {Ln}, NL, PCSI-RS, v, R, NTRP, and/or K
In one example (similar to each of the above examples), there is restriction on configuring C6 in Table 6, where the restriction is associated with (related to/based on) {Ln}, NL, PCSI-RS, v, R, NTRP, and/or K.
In one example (similar to each of the above examples), there is restriction on configuring C5 in Table 6, where the restriction is associated with (related to/based on) {Ln}, NL, PCSI-RS, v, R, NTRP, and/or K.
In one embodiment, a table for {Ln} (which can be one of the possible tables described in this disclosures) does not include at least one of the following combinations {Ln}=(4, 4, 2) and its permutations (e.g., (4, 2, 4), (2,4,4)) for NTRP=3 and {Ln}=(4, 4, 4, 2) and its permutations (e.g., (4, 2, 4, 4), (4, 4, 2, 4), (2, 4, 4, 4)) for NTRP=4.
In one example, a supported number of combinations for the table of {Ln} is at most Q, e.g., Q=34 or, Q=16 or Q=120, and at least U of {E1-E6 and E9-E11 and E15-E18} combinations, where 1≤U≤13, or one of {E1-E6 and E9-E11 and E15-E18} or all of {E1-E6 and E9-E11 and E15-E18} combinations in Table 7 are included in the at most Q combinations. In one example, all of {E1-E6 and E9-E11 and E15-E18} combinations in Table 7 are included (i.e., U=13) in the at most Q combinations.
Note that in Table 7, there are rows having one {Ln} combination and its permutation(s) in Table 7. In one example, for such a row, one combination (among the permutations) can be written as shown in Table 7. In another example, each permutation can be written in another row. In another example, all permutations can be written in one row.
In one example, for only some of rows having one {Ln} combination and its permutation(s) (e.g., E5 and E10), each permutation can be written in another row.
In another example, a subset (some) of permutations can be written in one row. In another example, for each combination in a subset (some) of permutations can be written in another row of the table.
In one example, in addition to the U combinations, among the remaining (22-13) combinations in Table 7 (i.e., E7, E8, E12-E14, E19-E22), at least one combination is/are included the at most Q combinations.
examples are omitted.)
examples are omitted.)
examples are omitted.)
examples are omitted.)
examples are omitted.)
examples are omitted.)
examples are omitted.)
examples are omitted.)
In one example, in addition to the U combinations, among the remaining (22-13) combinations in Table 7 (i.e., E7, E8, E12-E14, E19-E22), at least one combination is/are included the at most Q combinations.
In one example, a table for {Ln} includes at least one of the {Ln} combinations of {E1-E6 and E9-E11 and E15-E18}. For example, a table for {Ln} including {E1-E6 and E9-E11 and E15-E18} can be written as in the following Tables 8-10:
Ex1) including permutations for some {Ln} combinations, i.e., {2, 4} and {2, 2, 4}
Ex2) including permutations for some {Ln} combinations, i.e., {2, 4} and {2, 2, 4}
Ex3) including permutations for some {Ln} combinations, i.e., {2, 4} and {2, 2, 4}
In one example, a table for {Ln} includes 0 in blank. For example, in the tables of Ex1) and Ex2) above, the blanks are filled with 0s.
In another example, the order of {Ln} combinations can be different from above. For example, from top to bottom, {Ln} combinations can be ordered in the order of NTRP=4 to NTRP=1. The tables above are in the order of NTRP=1 to NTRP=4 from top to bottom for example.
In one example (H1), there is restriction on configuring E22 in Table 7, where the restriction is associated with (related to/based on) (pv, β).
In one example, regarding example H1-L, Q0 can be per {Ln} combination, i.e., above case it is for E22 (or any other {Ln} combination). For example, linkage between a list/table of (pv, β) combinations (which can be one of the possible tables described in this disclosures) and a list/table of {Ln} combinations (which can be one of the possible tables described in this disclosures) can be via pairing each combination for {Ln} with at least one combination for (pv, β). For example, Q0, . . . , QQ-1 index sets can be used for linking each combination for {Ln} with at least one combination for (pv, β).
In one example (H1-a), there is restriction on configuring E22 according to one of the examples above. In addition, the restriction is UE-optional, i.e., the restriction is on/off depending on UE capability. The UE reports its capability on the restriction, whether it is needed or not, and the NW then follows the reported UE capability.
In one example (H1-b), there is restriction on configuring E22 according to one of the examples above. In addition, the E22 is UE-optional, i.e., E22 can be configured depending on UE capability. The UE reports its capability on the support of E22, and then only the NW can configure E22. This UE-optional feature can correspond to a separate UE capability.
In one example (H2), there is restriction on configuring E22 in Table 7, where the restriction is associated with (related to/based on) NL.
In one example (H2-a), there is restriction on configuring E22 according to one of the examples above. In addition, the restriction is UE-optional, i.e., the restriction is on/off depending on UE capability. The UE reports its capability on the restriction, whether it is needed or not, and the NW then follows the reported UE capability.
In one example (H2-b), there is restriction on configuring E22 according to one of the examples above. In addition, the E22 is UE-optional, i.e., E22 can be configured depending on UE capability. The UE reports its capability on the support of E22, and then only the NW can configure E22. This UE-optional feature can correspond to a separate UE capability.
In one example (H3), there is restriction on configuring E22 in Table 7, where the restriction is associated with (related to/based on) PCSI-RS In one example, PCSI-RS is a number of CSI-RS ports per CSI-RS-resource (per TRP).
In one example (H3-a), there is restriction on configuring E22 according to one of the examples above. In addition, the restriction is UE-optional, i.e., the restriction is on/off depending on UE capability. The UE reports its capability on the restriction, whether it is needed or not, and the NW then follows the reported UE capability.
In one example (H3-b), there is restriction on configuring E22 according to one of the examples above. In addition, the E22 is UE-optional, i.e., E22 can be configured depending on UE capability. The UE reports its capability on the support of E22, and then only the NW can configure E22. This UE-optional feature can correspond to a separate UE capability.
In one example (H4), there is restriction on configuring E22 in Table 7, where the restriction is associated with (related to/based on) v, where v is a number of layers, i.e., rank.
In one example (H4-a), there is restriction on configuring E22 according to one of the examples above. In addition, the restriction is UE-optional, i.e., the restriction is on/off depending on UE capability. The UE reports its capability on the restriction, whether it is needed or not, and the NW then follows the reported UE capability.
In one example (H4-b), there is restriction on configuring E22 according to one of the examples above. In addition, the E22 is UE-optional, i.e., E22 can be configured depending on UE capability. The UE reports its capability on the support of E22, and then only the NW can configure E22. This UE-optional feature can correspond to a separate UE capability.
In one example (H5), there is restriction on configuring E22 in Table 7, where the restriction is associated with (related to/based on) R, where R is a number of precoders per subband.
In one example (H5-a), there is restriction on configuring E22 according to one of the examples above. In addition, the restriction is UE-optional, i.e., the restriction is on/off depending on UE capability. The UE reports its capability on the restriction, whether it is needed or not, and the NW then follows the reported UE capability.
In one example (H5-b), there is restriction on configuring E22 according to one of the examples above. In addition, the E22 is UE-optional, i.e., E22 can be configured depending on UE capability. The UE reports its capability on the support of E22, and then only the NW can configure E22. This UE-optional feature can correspond to a separate UE capability.
In one example (H6), there is restriction on configuring E22 in Table 7, where the restriction is associated with (related to/based on) K, where K is a number of subbands.
In one example (H6-a), there is restriction on configuring E22 according to one of the examples above. In addition, the restriction is UE-optional, i.e., the restriction is on/off depending on UE capability. The UE reports its capability on the restriction, whether it is needed or not, and the NW then follows the reported UE capability.
In one example (H6-b), there is restriction on configuring E22 according to one of the examples above. In addition, the E22 is UE-optional, i.e., E22 can be configured depending on UE capability. The UE reports its capability on the support of E22, and then only the NW can configure E22. This UE-optional feature can correspond to a separate UE capability.
In one example (any combination of H1-H6 (H1-a-H6-a, H6-b-H6-b), there are multiple restrictions on configuring E22 in Table 7, where the multiple restrictions include at least one of the restrictions H1-H6 (H1-a to H6-a, H1-b-H6-b), described above. The multiple restrictions are associated with (related to/based on) (pv, β), NL, PCSI-RS, v, R, and/or K.
In one example, in addition to the multiple restrictions, as described above, the combination E22 can only be configured when the UE reports via UE a separate UE capability that it can support E22.
In one example (similar to each of the above examples), there is restriction on configuring E21 in Table 7, where the restriction is associated with (related to/based on) (pv, β), NL, PCSI-RS, v, R, and/or K.
In one example (similar to each of the above examples), there is restriction on configuring E20 in Table 7, where the restriction is associated with (related to/based on) (pv, β), NL, PCSI-RS, v, R, and/or K.
In one example (similar to each of the above examples), there is restriction on configuring E19 in Table 7, where the restriction is associated with (related to/based on) (pv, β), NL, PCSI-RS, v, R, and/or K.
In one example (similar to each of the above examples), there is restriction on configuring E14 in Table 7, where the restriction is associated with (related to/based on) (pv, β), NL, PCSI-RS, v, R, and/or K.
In one example (similar to each of the above examples), there is restriction on configuring E13 in Table 7, where the restriction is associated with (related to/based on) (pv, β), NL, PCSI-RS, v, R, and/or K.
In one example (similar to each of the above examples), there is restriction on configuring E12 in Table 7, where the restriction is associated with (related to/based on) (pv, β), NL, PCSI-RS, v, R, and/or K.
In one example (similar to each of the above examples), there is restriction on configuring E8 in Table 7, where the restriction is associated with (related to/based on) (pv, β), NL, PCSI-RS, v, R, and/or K.
In one example (similar to each of the above examples), there is restriction on configuring E7 in Table 7, where the restriction is associated with (related to/based on) (pv, β), NL, PCSI-RS, v, R, and/or K.
In one example (similar to each of the above examples), there is restriction on configuring E3 in Table 7, where the restriction is associated with (related to/based on) (pv, β), NL, PCSI-RS, v, R, and/or K.
In one example, to find a table for (pv, β) and a table for {Ln}, the following methodology can be used.
Metric: according to the agreed EVM, i.e., UPT vs overhead trade-off (just like Rel. 16/17)
Criterion: similar to Rel. 16 (R1-1908499)
SLS simulations were performed to compare Mode 2 performance for all possible pairs of (pv, β) for each {Ln, n=1, . . . , NTRP} combination for each case of NTRP=2, 3, 4, where Ln∈{2, 4} and
Here, pv=x implies pv=x for v∈{1, 2} and
for v∈{3, 4}. Scenarios were considered where the UE is allowed to select dynamic rank up to 2 and up to 4.
For NTRP=2, 3,
For NTRP=4,
As seen in
To find the best pairs of (pv, β), the following approach based on the criterion described in this disclosure was considered.
As seen in
are selected as a best pair for all cases of (NTRP, {Ln}) and
are selected as a best pair for more than or equal to a half of all cases of (NTRP, {Ln}). Here, we considered one case of {Ln} among its possible permutations.
Based on the above approach, the following 6 best pairs of (pv, β) were found.
Observation:
are good candidates to yield better UPT vs overhead trade-off performance than other combinations of (pv, β).
Pruning {Ln} Combinations Performing Worse, Based on the Best Pairs of (pv, β)
Once the best pairs of (pv, β) were found, a comparison of the performance of {Ln} using the best pairs of (pv, β) can be performed.
In one embodiment, for a table of {Ln} that can be one of the tables or the whole tables/sub-tables, or tables that can be constructed in/under one or more embodiments described herein with/without the column of Lmax and other embodiments in this disclosure, NL>1 combinations of {Ln} can be configured to a UE using the table of {Ln}.
In one embodiment, configurable/possible/supported values of NL depend on NTRP, and NL=1 is a supported value for all NTRP=1, 2, 3, 4.
In one example, the configurable values of NL include at least one of the elements in {2, 4} for a given NTRP.
In one example,
In one example, a UE may support none, any, or some or all of NL>1 configurable values based on its capability (UE capability) and report its capability. For example, when NL E {1,2,4} is configurable, UE may report its capability whether to support NL=2 only or NL=4 only or both NL=2 and 4. The NW then follows the reported UE capability on NL.
In one example, the configurable values of NL include at least one of the elements in X for a given NTRP. In one example, X={2, 4, 8, 16}. In one example, X can be any subset of {1, 2, . . . , 32}.
In one embodiment, configuring NL>1 combination(s) of {Ln} can be restricted with one or more indices from the table for {Ln}.
In one example, there are two indices sets S0 and S1 for the table of {Ln}, where the {Ln} combinations associated with the indices in S0 are considered as basic configuration and the {Ln} combinations associated with the indices in S1 are considered as optional configuration. For example, for the optional configuration, it requires UE capability reporting, whether the associated {Ln} combination(s) is/are supported by the UE. In another example, for the basic configuration, the UE needs to support hence it doesn't require UE capability reporting.
In one example, there are multiple (>2) indices sets for the table of {Ln}, where NL>1 {Ln} combinations can be configured within a (single) set. For example, if one {Ln} combination associated with a certain set is configured, other NL−1 configured combinations of {Ln} should also be associated with the same set.
In one example, there are multiple (>2) indices sets for the table of {Ln}, where NL>1 {Ln} combinations can be configured across NL different sets, i.e., the sets are non-overlapping.
In one embodiment, configuring NL>1 combination(s) of {Ln} can be restricted with one or more indices from the table for {Ln} and/or with other parameters that include at least one of the followings: PCSI-RS, R, NTRP, v, Ln, (pv, β).
In one example (F1), there is restriction on configuring NL>1 combinations of {Ln}, where the restriction is associated with (related to/based on) {Ln}.
For example, x can be only one of x=2, x=4, or x=6.
For example, x can be only one of x=2, x=4, or x=6.
For example, x can be only one of x=2, x=4, or x=6.
For example, x can be only one of x=2, x=4, or x=6.
For example, x can be only one of x=2, x=4, or x=6.
For example, x can be only one of x=2, x=4, or x=6.
For example, x can be only one of x=2, x=4, or x=6.
For example, x can be only one of x=2, x=4, or x=6.
For example, x can be only one of x=2, x=4, or x=6.
For example, x can be only one of x=2, x=4, or x=6.
For example, x can be only one of x=2, x=4, or x=6.
For example, x can be only one of x=2, x=4, or x=6.
For example, x can be only one of x=2, x=4, or x=6. For example, y can be only one of y=2, y=4, or y=6.
For example, x can be only one of x=2, x=4, or x=6. For example, y can be only one of y=2, y=4, or y=6.
For example, x can be only one of x=2, x=4, or x=6. For example, y can be only one of y=2, y=4, or y=6.
For example, x can be only one of x=2, x=4, or x=6. For example, y can be only one of y=2, y=4, or y=6.
For example, x can be only one of x=2, x=4, or x=6. For example, y can be only one of y=2, y=4, or y=6.
For example, x can be only one of x=2, x=4, or x=6. For example, y can be only one of y=2, y=4, or y=6.
For example, x can be only one of x=2, x=4, or x=6. For example, y can be only one of y=2, y=4, or y=6.
For example, x can be only one of x=2, x=4, or x=6. For example, y can be only one of y=2, y=4, or y=6.
In one example (F3), there is restriction on configuring NL>1 combinations of {Ln}, where the restriction is associated with (related to/based on) v, where v is a number of layers, i.e., rank.
In one example (F4), there is restriction on configuring NL>1 combinations of {Ln}, where the restriction is associated with (related to/based on) R, where R is a number of precoders per subband.
In one example (F5), there is restriction on configuring NL>1 combinations of {Ln}, where the restriction is associated with (related to/based on) NTRP, where NTRP is a number of TRPs, i.e., a number of CSI-RS resources.
In one example (F6), there is restriction on configuring NL>1 combinations of {Ln}, where the restriction is associated with (related to/based on) (pv, β).
In one example (any combination of F1-F6, there are multiple restrictions on configuring NL>1 combinations of {Ln}, where the multiple restrictions include at least one of the restrictions F1-F6, described above. The multiple restrictions are associated with (related to/based on) (pv, β), NTRP, PCSI-RS, v, R, and/or {Ln}.
In one example, in addition to the multiple restrictions, as described above, NL>1 combinations of {Ln} can only be configured when the UE reports via UE a separate UE capability that it can support NL>1 combinations of {Ln}.
More Details on D1-L and/or H1-L
For illustration purpose, assume that a supported number of (pv, β) combinations is S and a supported number of {Ln} combinations is Q, e.g., S=6, Q=16.
In one example, one linkage matrix with size of S×Q (or Q×S) is used to indicate/refer linking pairs between (pv, β) and {Ln} combinations. For example, each entry (s, q) of the linkage matrix has either 0 or 1, where 0 refers to “not supported” for the linkage between s-th (pv, β) combination and q-th {Ln} combination, or 1 refers to “supported” for the linkage between s-th (pv, β) combination and q-th {Ln} combination.
In one example, the linkage matrix looks as follows.
In one example, the UE is not expected to configure the combination pair of (pv, β) and {Ln} corresponding to any of the “not supported” entries of the linkage matrix.
In one example, the UE is expected to configure the combination pair of (pv, β) and {Ln} corresponding to one (any) of the “supported” entries of the linkage matrix.
In one example, the linkage matrix is pre-determined/fixed.
In one example, the linkage matrix is configured via higher-layer signaling (e.g., RRC).
In one example, NTRP linkage matrices each with size of S×Qr (Qr×S) are used to indicate/refer linking pairs between (pv, β) and {Ln} combinations, where each linkage matrix r corresponds to the linkage matrix for NTRP=r, and r=1, . . . , 4. For example, each entry (s, q) of each linkage matrix r has either 0 or 1, where 0 refers to “not supported” for the linkage between s-th (pv, β) combination and q-th {Ln} combination for NTRP=r, or 1 refers to “supported” for the linkage between s-th (pv, β) combination and q-th {Ln} combination for NTRP=r.
In one example, Qr is the number of supported {Ln} combinations for NTRP=r.
In one example, the UE is not expected to configure the combination pair of (pv, β) and {Ln} corresponding to any of the “not supported” entries of the linkage matrix.
In one example, the UE is expected to configure the combination pair of (pv, β) and {Ln} corresponding to one (any) of the “supported” entries of the linkage matrix.
In one example, the linkage matrix is pre-determined/fixed.
In one example, the linkage matrix is configured via higher-layer signaling (e.g., RRC).
The term linkage matrix is being used for the sake of convenience, but it can be under a different name, e.g., linkage pair, linkage combination, (linkage/supported) pair/combination between {Ln} and (pv, beta) etc.
In one example, a supported number of linkages/pairs between {Ln} and (pv, β) for each NTRP is at most J, e.g., J=8 (as shown in the following table 11). In another example, J=12 or J=16, or J=9.
For example, in Table 11 above, the ones with ‘linked’ are supported linkages/pairs between {Ln} and (pv, β) for each NTRP, wherein the number of supported linkages/pairs for each NTRP is 8.
In one example, possible values of NL are determined/restricted by the linkages for a given (pv, β) and for each NTRP. For example, using the table above as an example, for the case of (pv, β) corresponding to ({⅛, ⅛, 1/16, 1/16}, ½) for NTRP=2, the possible {Ln} combinations are {2, 2} and {2, 4}. In this case, the possible values of NL are 1 and/or 2. That is, the number of rows with ‘linked’ for each column determines the possible {Ln} combinations and the possible values of NL. We denote possible values of NL in the last row for each NTRP in the table above.
In one example, NL=4 can be supported only for NTRP=3. For example, using the following table as an example, for the case of (pv, β) corresponding to ({⅛, ⅛, 1/16, 1/16}, ½) for NTRP=3, the possible {Ln} combinations are {2, 2, 2}, {2, 2, 4}, {2, 4, 2}, and {4, 2, 2}. In this case, the possible values of NL are 1, 2 and/or 4.
In one example, for all NTRP=1, 2, 3, 4, the possible values of NL are 1 and 2 only. In one example, the table above is an example of this case.
In one example, the possible values of NL are 1, 2, and 4, but NL=4 is only for NTRP=2. In one example, NL=4 {Ln} combinations for NTRP=2 include the two permutations {2, 4} and {4, 2}. In one example, the following Table 12 is one example of this case.
In one example, the possible values of NL are 1, 2, and 4, but NL=4 is only for NTRP=3. In one example, NL=4 {Ln} combinations for NTRP=3 include the three permutations {2, 2, 4} and {2, 4, 2} and {4, 2, 2}. In one example, the following Table 13 is one example of this case.
In one example, the possible values of NL are 1, 2, and 4, but NL=4 is only for NTRP=4. In one example, the following Table 14 is one example of this case.
In one example, the possible values of NL are 1, 2, and 4, but NL=4 is only for NTRP=2, 3. In one example, NL=4 {Ln} combinations for NTRP=2 include the two permutations {2, 4} and {4, 2}. In one example, NL=4 {Ln} combinations for NTRP=3 include the three permutations {2, 2, 4} and {2, 4, 2} and {4, 2, 2}. In one example, the following Table 15 is one example of this case.
In one example, the possible values of NL are 1, 2, and 4, but NL=4 is only for NTRP=2, 3, 4. In one example, NL=4 {Ln} combinations for NTRP=2 include the two permutations {2, 4} and {4, 2}. In one example, NL=4 {Ln} combinations for NTRP=3 include the three permutations {2, 2, 4} and {2, 4, 2} and {4, 2, 2}. In one example, the following Table 16 is one example of this case.
In one example, for NL=2 for a given pair of {Ln} combinations, the supported number of the linked (pv, β) combinations is at most 1. For example, in the above Table 16, for NTRP=1 and for the pair of L=2 and L=4, there is only one (pv, β) (second column) linked to both the L=2 and L=4.
In one example, for NL=2 for a given pair of {Ln} combinations, the supported number of the linked (pv, β) combinations is at most 2. For example, in the above table, for NTRP=2 and for the pair of {Ln}={2, 4} and {Ln}={4, 2}, there are two (pv, β) (second and third columns) linked to both the {Ln}={2, 4} and {Ln}={4, 2}.
In one example, for NL=4 for a given quadruple of {Ln} combinations, the supported number of the linked (pv, β) combinations is at most 1. For example, in the above table, for NTRP=3 and for the quadruple of {Ln}={2, 2, 4}, {Ln}={2, 4, 2}, {Ln}={4, 2, 2}, {Ln}={4, 4, 4}, there is only one (pv, β) (third column) linked to all the {Ln}={2, 2, 4}, {Ln}={2, 4, 2}, {Ln}={4, 2, 2}, {Ln}={4, 4, 4}.
In one example, for NL=4 for a given quadruple of {Ln} combinations, the supported number of the linked (pv, β) combinations is at most 2. For example, in the above table, for NTRP=3 and for the quadruple of {Ln}={2, 2, 2, 2}, {Ln}={2, 2, 4, 2}, {Ln}={2, 2, 4, 4}, {Ln}={4, 4, 4, 4}, there are two (pv, β) (third and fourth columns) linked to all the {Ln}={2, 2, 2, 2}, {Ln}={2, 2, 4, 2}, {Ln}={2, 2, 4, 4}, {Ln}={4, 4, 4, 4}.
In one example, the supported linkages/pairs between {Ln} and (pv, β) include all of the ‘linked’ ones described in one of the linkage tables that can be constructed or are described in this disclosure.
In one example, the supported linkages/pairs between {Ln} and (pv, β) include a subset of the ‘linked’ ones described in one of the linkage tables that can be constructed or are described in this disclosure.
In one example, the supported linkages/pairs between {Ln} and (pv, β) include at least one of the ‘linked’ ones described in one of the linkage tables that can be constructed or are described in this disclosure.
In one example, for a given (pv, β) and for each NTRP, the linkages for {Ln} combinations that are in permutation relationship (e.g., {2, 2, 4}, {2, 4, 2}, {4, 2, 2} for NTRP=3) are either ‘all linked or ‘all not linked’.
In one example, for PCSI-RS=4, the UE is not expected to configure with {Ln} combination including 4 or 6.
In one example, for PCSI-RS=4, the UE is expected to configure with {Ln} combination including 2 only.
In one example, for PCSI-RS=8, the UE is not expected to configure with L=6 for NTRP=1.
In one example, for PCSI-RS=8, the UE is not expected to configure with {Ln} combination including 2 or 4.
In one example, for PCSI-RS=4, the supported linkages/pairs are all possible combinations of (pv, β), i.e., 6 (pv, β) combinations, for the combinations of {Ln}={2}, {Ln}={2, 2}, {Ln}={2, 2, 2}, and {Ln}={2, 2, 2, 2}. In other words, in this case, the supported linkages/pairs are separated from a supported linkage table.
In one example, for PCSI-RS=4, the supported linkages follow a same linkage table shown in one of the linkage tables, that can be constructed or are described in this disclosure, for the combinations of {Ln}={2}, {Ln}={2, 2}, {Ln}={2, 2, 2}, and {Ln}={2, 2, 2, 2}.
In one example, for each NTRP, the supported linkages/pairs between {Ln} and (pv, β) include at least one of the highlighted ones described in the following Table 17.
For example, for NTRP=1, the supported linkages/pairs between {Ln} and (pv, β) include at least one of the highlighted ones labelled from W1 to W8. For example, J1 linkages selected from W1-W8 are supported linkages, where 1≤J1≤J, and J2 linkages selected from the ones other than W1-W8 (for NTRP=1) are supported linkages, where 0≤J2≤J−J1.
For example, for NTRP=2, the supported linkages/pairs between {Ln} and (pv, β) include at least one of the highlighted ones labelled from W9 to W15. For example, J1 linkages selected from W9-W15 are supported linkages, where 1≤J1≤J, and Jz linkages selected from the ones other than W9-W15 (for NTRP=2) are supported linkages, where 0≤J2≤J−J1.
For example, for NTRP=3, the supported linkages/pairs between {Ln} and (pv, β) include at least one of the highlighted ones labelled from W16 to W24. For example, J1 linkages selected from W16-W24 are supported linkages, where 1≤J1≤J, and J2 linkages selected from the ones other than W16-W24 (for NTRP=3) are supported linkages, where 0≤J2≤J−J1.
For example, for NTRP=4, the supported linkages/pairs between {Ln} and (pv, β) include at least one of the highlighted ones labelled from W25 to W32. For example, J1 linkages selected from W25-W32 are supported linkages, where 1≤J1≤J, and J2 linkages selected from the ones other than W25-W32 (for NTRP=4) are supported linkages, where 0≤J2≤J−J1.
In one example, for each NTRP, the supported linkages/pairs between {Ln} and (pv, β) include at least one of the highlighted ones described in the following Table 18.
For example, for NTRP=1, the supported linkages/pairs between {Ln} and (pv, β) include at least one of the highlighted ones labelled from Legacy1 to Legacy7. For example, for NTRP=1, the supported linkages/pairs between {Ln} and (pv, β) include all of the highlighted ones labelled from Legacy 1 to Legacy7.
For example, for NTRP=2, the supported linkages/pairs between {Ln} and (pv, β) include at least one of the highlighted ones labelled R1 to R3 and T1 to T8 and S1 to S3.
In one example, for NTRP=2, the supported linkages/pairs between {Ln} and (pv, β) include all of the highlighted ones labelled R1 to R3 and T1 to T8 and S1 to S3.
In one example, for NTRP=2, the supported linkages/pairs between {Ln} and (pv, β) include the highlighted ones labelled R1 to R3 and S1 to S3.
In one example, for NTRP=2, the supported linkages/pairs between {Ln} and (pv, β) include the highlighted ones labelled R1 to R3 and S1 to S3 and at least one of the highlighted ones labelled T1 to T8.
In one example, for NTRP=2, the supported linkages/pairs between {Ln} and (pv, β) include the highlighted ones labelled S1 to S3.
In one example, for NTRP=2, the supported linkages/pairs between {Ln} and (pv, β) include the highlighted ones labelled S1 to S3 and at least one of the highlighted ones labelled R1 to R3.
In one example, for NTRP=2, the supported linkages/pairs between {Ln} and (pv, β) include the highlighted ones labelled S1 to S3 and at least one of the highlighted ones labelled T1 to T8.
In one example, for NTRP=2, the supported linkages/pairs between {Ln} and (pv, β) include the highlighted ones labelled S1 to S3 and at least one of the highlighted ones labelled T1 to T8 and at least one of the highlighted ones labelled R1 to R3.
In one example, for NTRP=2, the supported linkages/pairs between {Ln} and (pv, β) include the highlighted ones labelled S1 to S3 and based on J, they further include J1 linkages from the ones labelled R1 to R3 and T1 to T8, where 0≤J1≤J−3.
In one example, for NTRP=2, the supported linkages/pairs between {Ln} and (pv, β) include the highlighted ones labelled S1 to S3 and R1 to R3, and based on J, they further include J1 linkages from the ones labelled T1 to T8, where 0≤J1≤J−6.
For example, for NTRP=3, the supported linkages/pairs between {Ln} and (pv, β) include at least one of the highlighted ones labelled R4 to R12 and T9 to T18 and S4 to S5.
In one example, for NTRP=3, the supported linkages/pairs between {Ln} and (pv, β) include all of the highlighted ones labelled R4 to R12 and T9 to T18 and S4 to S5.
In one example, for NTRP=3, the supported linkages/pairs between {Ln} and (pv, β) include the highlighted ones labelled R4 to R12 and S4 to S5.
In one example, for NTRP=3, the supported linkages/pairs between {Ln} and (pv, β) include the highlighted ones labelled R4 to R12 and S4 to S5 and at least one of the highlighted ones labelled T9 to T18.
In one example, for NTRP=3, the supported linkages/pairs between {Ln} and (pv, β) include the highlighted ones labelled S4 to S5.
In one example, for NTRP=3, the supported linkages/pairs between {Ln} and (pv, β) include the highlighted ones labelled S4 to S5 and at least one of the highlighted ones labelled R4 to R12.
In one example, for NTRP=3, the supported linkages/pairs between {Ln} and (pv, β) include the highlighted ones labelled S4 to S5 and at least one of the highlighted ones labelled T9 to T18.
In one example, for NTRP=3, the supported linkages/pairs between {Ln} and (pv, β) include the highlighted ones labelled S4 to S5 and at least one of the highlighted ones labelled T9 to T18 and at least one of the highlighted ones labelled R4 to R12.
In one example, for NTRP=3, the supported linkages/pairs between {Ln} and (pv, β) include the highlighted ones labelled S4 to S5 and based on J, they further include J1 linkages from the ones labelled R4 to R12 and T9 to T18, where 0≤J1≤J−2.
In one example, for NTRP=3, the supported linkages/pairs between {Ln} and (pv, β) include the highlighted ones labelled S4 to S5 and R4 to R12, and based on J, they further include J1 linkages from the ones labelled T9 to T18, where 0≤J1≤J−11.
For example, for NTRP=4, the supported linkages/pairs between {Ln} and (pv, β) include at least one of the highlighted ones labelled R13 to R18 and T19 to T25 and S6.
In one example, for NTRP=4, the supported linkages/pairs between {Ln} and (pv, β) include all of the highlighted ones labelled R13 to R18 and T19 to T25 and S6.
In one example, for NTRP=4, the supported linkages/pairs between {Ln} and (pv, β) include the highlighted ones labelled R13 to R18 and S6.
In one example, for NTRP=4, the supported linkages/pairs between {Ln} and (pv, β) include the highlighted ones labelled R13 to R18 and S6 and at least one of the highlighted ones labelled T19 to T25.
In one example, for NTRP=4, the supported linkages/pairs between {Ln} and (pv, β) include the highlighted one labelled S6.
In one example, for NTRP=4, the supported linkages/pairs between {Ln} and (pv, β) include the highlighted one labelled S6 and at least one of the highlighted ones labelled R13 to R18.
In one example, for NTRP=4, the supported linkages/pairs between {Ln} and (pv, β) include the highlighted one labelled S6 and at least one of the highlighted ones labelled T19 to T25.
In one example, for NTRP=4, the supported linkages/pairs between {Ln} and (pv, β) include the highlighted one labelled S6 and at least one of the highlighted ones labelled T19 to T25 and at least one of the highlighted ones labelled R13 to R18.
In one example, for NTRP=4, the supported linkages/pairs between {Ln} and (pv, β) include the highlighted one labelled S6 and based on J, they further include J1 linkages from the ones labelled R13 to R18 and T19 to T25, where 0≤J1≤J−1.
In one example, for NTRP=4, the supported linkages/pairs between {Ln} and (pv, β) include the highlighted one labelled S6 and R13 to R18, and based on J, they further include J1 linkages from the ones labelled T19 to T25, where 0≤J1≤J−7.
In one example, the UE can report UE capability on Ltot. Then, the NW (needs to follow and) can configure a combination of {Ln} under the UE capability, e.g., a combination of {Ln} such that Σn Ln=Ltot.
For example, Ltot≤t is a basic feature and Ltot>t is UE-optional. In one example, t=8. In one example, t=10. In one example, t=12. For Ltot>t, the UE reports its capability to support it or not and the NW can configure one of the parameter combinations in the table only associated with the {Ln} that the UE supports (based on the UE capability and the basic feature).
For example, Ltot<t is a basic feature and Ltot≥t is UE-optional. In one example, t=8. In one example, t=10. In one example, t=12. In one example, t=14. For Ltot≥t, the UE reports its capability to support it or not and the NW can configure one of the parameter combinations in the table only associated with the {Ln} that the UE supports (based on the UE capability and the basic feature).
For example, Ltot∈A is a basic feature and Ltot∈B is UE-optional. In one example, A={4, 6, 8} and B={10, 12, 16}. In one example, A={4, 6, 8, 10} and B={12, 16}. In one example, A={4, 6, 8, 10, 12} and B={16}. For Ltot∈B, the UE reports its capability to support it or not and the NW can configure one of the parameter combinations in the table only associated with the {Ln} that the UE supports (based on the UE capability and the basic feature).
In one example, the UE capability on Ltot in each example above can be a separate capability.
In one example, the UE capability on Ltot in each example above can be one component of a capability.
The following figures are the SLS simulation results in additional scenarios to find best linkages between {Ln} and (pv, β) for each NTRP.
Any of the above variation embodiments can be utilized independently or in combination with at least one other variation embodiment. The above flowcharts illustrate example methods that can be implemented in accordance with the principles of the present disclosure and various changes could be made to the methods illustrated in the flowcharts herein. For example, while shown as a series of steps, various steps in each figure could overlap, occur in parallel, occur in a different order, or occur multiple times. In another example, steps may be omitted or replaced by other steps.
Although the figures illustrate different examples of user equipment, various changes may be made to the figures. For example, the user equipment can include any number of each component in any suitable arrangement. In general, the figures do not limit the scope of this disclosure to any particular configuration(s). Moreover, while figures illustrate operational environments in which various user equipment features disclosed in this patent document can be used, these features can be used in any other suitable system.
Although the present disclosure has been described with exemplary embodiments, various changes and modifications may be suggested to one skilled in the art. It is intended that the present disclosure encompass such changes and modifications as fall within the scope of the appended claims. None of the description in this application should be read as implying that any particular element, step, or function is an essential element that must be included in the claims scope. The scope of patented subject matter is defined by the claims.
This application claims priority under 35 U.S.C. § 119(e) to U.S. Provisional Patent Application No. 63/439,782 filed on Jan. 18, 2023, U.S. Provisional Patent Application No. 63/443,307 filed on Feb. 3, 2023, U.S. Provisional Patent Application No. 63/446,732 filed on Feb. 17, 2023, U.S. Provisional Patent Application No. 63/447,565 filed on Feb. 22, 2023, U.S. Provisional Patent Application No. 63/447,829 filed on Feb. 23, 2023, U.S. Provisional Patent Application No. 63/448,187 filed on Feb. 24, 2023, U.S. Provisional Patent Application No. 63/448,800 filed on Feb. 28, 2023, U.S. Provisional Patent Application No. 63/449,212 filed on Mar. 1, 2023, U.S. Provisional Patent Application No. 63/451,466 filed on Mar. 10, 2023, U.S. Provisional Patent Application No. 63/453,367 filed on Mar. 20, 2023, and U.S. Provisional Patent Application No. 63/457,065 filed on Apr. 4, 2023. The above-identified provisional patent applications are hereby incorporated by reference in their entirety.
Number | Date | Country | |
---|---|---|---|
63439782 | Jan 2023 | US | |
63443307 | Feb 2023 | US | |
63446732 | Feb 2023 | US | |
63447565 | Feb 2023 | US | |
63447829 | Feb 2023 | US | |
63448187 | Feb 2023 | US | |
63448800 | Feb 2023 | US | |
63449212 | Mar 2023 | US | |
63451466 | Mar 2023 | US | |
63453367 | Mar 2023 | US | |
63457065 | Apr 2023 | US |