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.
FIGURES 1 through 10, discussed below, and the various embodiments used to describe the principles of the disclosure in this patent document are by way of illustration only and should not be construed in any way to limit the scope of the disclosure. Those skilled in the art will understand that the principles of the disclosure may be implemented in any suitably-arranged system or device.
The following documents and standards descriptions are hereby incorporated by reference into the 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.2.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"); 3GPP TS 38.331 v17.1.0, "NR, Radio Resource Control (RRC) Protocol Specification" (herein "REF 12").
Wireless communication has been one of the most successful innovations in modern history. Recently, the number of subscribers to wireless communication services exceeded five billion and continues to grow quickly. The demand of wireless data traffic is rapidly increasing due to the growing popularity among consumers and businesses of smart phones and other mobile data devices, such as tablets, "note pad" computers, net books, eBook readers, and machine type of devices. In order to meet the high growth in mobile data traffic and support new applications and deployments, improvements in radio interface efficiency and coverage is of paramount importance.
To meet the demand for wireless data traffic having increased since deployment of 4G communication systems and to enable various vertical applications, 5G/NR communication systems have been developed and are currently being deployed. The 5G/NR communication system is considered to be implemented in higher frequency (mmWave) bands, e.g., 28 GHz or 60GHz bands, so as to accomplish higher data rates or in lower frequency bands, such as 6 GHz, to enable robust coverage and mobility support. To decrease propagation loss of the radio waves and increase the transmission distance, the beamforming, massive multiple-input multiple-output (MIMO), full dimensional MIMO (FD-MIMO), array antenna, an analog beam forming, large scale antenna techniques are discussed in 5G/NR communication systems.
In addition, in 5G/NR communication systems, development for system network improvement is under way based on advanced small cells, cloud radio access networks (RANs), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, moving network, cooperative communication, coordinated multi-points (CoMP), reception-end interference cancelation and the like.
The discussion of 5G systems and frequency bands associated therewith is for reference as certain embodiments of the disclosure may be implemented in 5G systems. However, the disclosure is not limited to 5G systems, or the frequency bands associated therewith, and embodiments of the disclosure may be utilized in connection with any frequency band. For example, aspects of the disclosure may also be applied to deployment of 5G communication systems, 6G or even later releases which may use terahertz (THz) bands.
FIGURES 1-3 below describe various embodiments implemented in wireless communications systems and with the use of orthogonal frequency division multiplexing (OFDM) or orthogonal frequency division multiple access (OFDMA) communication techniques. The descriptions of FIGURES 1-3 are not meant to imply physical or architectural limitations to the manner in which different embodiments may be implemented. Different embodiments of the disclosure may be implemented in any suitably arranged communications system.
FIGURE 1 illustrates an example wireless network according to an embodiment of the disclosure. The embodiment of the wireless network shown in FIGURE 1 is for illustration only. Other embodiments of the wireless network 100 could be used without departing from the scope of this disclosure.
As shown in FIGURE 1, the wireless network includes a gNB 101 (e.g., base station, BS), a gNB 102, and a gNB 103. The gNB 101 communicates with the gNB 102 and the gNB 103. The gNB 101 also communicates with at least one network 130, such as the Internet, a proprietary Internet Protocol (IP) network, or other data network.
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 CSI codebook parameters. In certain embodiments, one or more of the BSs 101-103 include circuitry, programing, or a combination thereof for supporting CSI codebook parameters.
Although FIGURE 1 illustrates one example of a wireless network, various changes may be made to FIGURE 1. For example, the wireless network could include any number of gNBs and any number of UEs in any suitable arrangement. Also, the gNB 101 could communicate directly with any number of UEs and provide those UEs with wireless broadband access to the network 130. Similarly, each gNB 102-103 could communicate directly with the network 130 and provide UEs with direct wireless broadband access to the network 130. Further, the gNBs 101, 102, and/or 103 could provide access to other or additional external networks, such as external telephone networks or other types of data networks.
FIGURE 2 illustrates an example gNB 102 according to an embodiment of the disclosure. The embodiment of the gNB 102 illustrated in FIGURE 2 is for illustration only, and the gNBs 101 and 103 of FIGURE 1 could have the same or similar configuration. However, gNBs come in a wide variety of configurations, and FIGURE 2 does not limit the scope of this disclosure to any particular implementation of a gNB.
As shown in FIGURE 2, the gNB 102 includes multiple antennas 205a-205n, multiple transceivers 210a-210n, a controller/processor 225, a memory 230, and a backhaul or network interface 235.
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 CSI codebook parameters. 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 FIGURE 2 illustrates one example of gNB 102, various changes may be made to FIGURE 2. For example, the gNB 102 could include any number of each component shown in FIGURE 2. Also, various components in FIGURE 2 could be combined, further subdivided, or omitted and additional components could be added according to particular needs.
FIGURE 3 illustrates an example UE 116 according to an embodiment of the disclosure. The embodiment of the UE 116 illustrated in FIGURE 3 is for illustration only, and the UEs 111-115 of FIGURE 1 could have the same or similar configuration. However, UEs come in a wide variety of configurations, and FIGURE 3 does not limit the scope of this disclosure to any particular implementation of a UE.
As shown in FIGURE 3, the UE 116 includes antenna(s) 305, a transceiver(s) 310, and a microphone 320. The UE 116 also includes a speaker 330, a processor 340, an input/output (I/O) interface (IF) 345, an input 350, a display 355, and a memory 360. The memory 360 includes an operating system (OS) 361 and one or more applications 362.
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. 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 FIGURE 3 illustrates one example of UE 116, various changes may be made to FIGURE 3. For example, various components in FIGURE 3 could be combined, further subdivided, or omitted and additional components could be added according to particular needs. As a particular example, the processor 340 could be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). In another example, the transceiver(s) 310 may include any number of transceivers and signal processing chains and may be connected to any number of antennas. Also, while FIGURE 3 illustrates the UE 116 configured as a mobile telephone or smartphone, UEs could be configured to operate as other types of mobile or stationary devices.
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.
FIGURE 4 illustrates an example antenna blocks or arrays 400 according to an embodiment of the disclosure. The embodiment of the antenna blocks or arrays 400 illustrated in FIGURE 4 is for illustration only. FIGURE 4 does not limit the scope of this disclosure to any particular implementation of the antenna blocks or arrays.
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 FIGURE 4. In this case, one CSI-RS port is mapped onto a large number of antenna elements which can be controlled by a bank of analog phase shifters 401. One CSI-RS port can then correspond to one sub-array which produces a narrow analog beam through analog beamforming 405. This analog beam can be configured to sweep across a wider range of angles 420 by varying the phase shifter bank across symbols or subframes. The number of sub-arrays (equal to the number of RF chains) is the same as the number of CSI-RS ports N
CSI-PORT. A digital beamforming unit 410 performs a linear combination across N
CSI-PORT analog beams to further increase precoding gain. While analog beams are wideband (hence not frequency-selective), digital precoding can be varied across frequency sub-bands or resource blocks. Receiver operation can be conceived analogously.
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.6GHz (also termed the FR4). In this case, the system can employ only analog beams. Due to the O2 absorption loss around 60GHz frequency (~10dB additional loss @100m 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 <1GHz, 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 disclosure recognize that for a cellular system operating in a sub-1GHz 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-1GHz system with a 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).
Accordingly, various embodiments of the disclosure consider the multi-TRP C-JT scenario and propose methods and apparatus for codebook parameters considering feedback overhead in the scenario.
Various embodiments of the 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
,
, and
. Among them,
is the component that could induce large CSI feedback overhead especially in mTRP CJT operations.
Accordingly, various embodiments of the disclosure provide codebook parameter configurations to alleviate the amount of CSI reporting overhead to have good performance-and-overhead trade-off for C-JT operations. The codebook parameter configurations (an extension of the tables of paraCombination-r16, paraCombination-r17) are proposed to have good performance-and-overhead trade-off for mTRP C-JT operations.
FIGURE 5 illustrates an example distributed MIMO system 500 according to an embodiment of the disclosure. The embodiment of the distributed MIMO system 500 illustrated in FIGURE 5 is for illustration only. FIGURE 5 does not limit the scope of this disclosure to any particular implementation of the distributed MIMO system 500.
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 FIGURE 5.
FIGURE 6 illustrates an example distributed MIMO system 600 according to an embodiment of the disclosure. The embodiment of the distributed MIMO system 600 illustrated in FIGURE 6 is for illustration only. FIGURE 6 does not limit the scope of this disclosure to any particular implementation of the distributed MIMO system 600.
As illustrated in FIGURE 6, the multiple TRPs at multiple locations can still be connected to a single base unit, and thus the signal transmitted/received via multiple distributed TRPs can be processed in a centralized manner through the single base unit.
Note that although the disclosure has mentioned low frequency band systems (sub-1GHz band) as a motivation for distributed MIMO (or mTRP), the distributed MIMO technology is frequency-band-agnostic and can be useful in mid- (sub-6GHz) and high-band (above-6GHz) systems in addition to low-band (sub-1GHz) 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 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, >6GHz, 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 M
n subbands when one CSI parameter for all the M
n subbands within the CSI reporting band. A CSI parameter is configured with "subband" for the CSI reporting band with M
n subbands when one CSI parameter is reported for each of the M
n subbands within the CSI reporting band.
FIGURE 7 illustrates an example antenna port layout 700 according to an embodiment of the disclosure. The embodiment of the antenna port layout 700 illustrated in FIGURE 13 is for illustration only. FIGURE 7 does not limit the scope of this disclosure to any particular implementation of the antenna port layout.
As illustrated in FIGURE 7,
N
1 and
N
2 are the number of antenna ports with the same polarization in the first and second dimensions, respectively. For 2D antenna port layouts,
N
1 > 1,
N
2 > 1, and for 1D antenna port layouts
N
1 > 1 and
N
2 = 1. Therefore, for a dual-polarized antenna port layout, the total number of antenna ports is 2
N
1
N
2 when
each antenna maps to an antenna port. An illustration is shown in FIGURE 7 where "X" represents two antenna polarizations. In this disclosure, the term "polarization" refers to a group of antenna ports. For example, antenna ports
comprise a first antenna polarization, and antenna ports
comprise a second antenna polarization, where
is a number of CSI-RS antenna ports and
is a starting antenna port number (e.g.,
, then antenna ports are 3000, 3001, 3002, …). Let
be a number of antenna panels at the gNB. When there are multiple antenna panels
, we assume that each panel is dual-polarized antenna ports with
and
ports in two dimensions. This is illustrated in FIGURE 7. Note that the antenna port layouts may or may not be the same in different antenna panels.
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 FIGURE 7. The antenna structure at each RRH/TRP can be the same. Alternatively, the antenna structure at an RRH/TRP can be different from another RRH/TRP. Likewise, the number of ports at each RRH/TRP can be the same. Alternatively, the number of ports at one RRH/TRP can be different from another RRH/TRP. In one example,
, a number of RRHs/TRPs in the D-MIMO transmission.
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.
We assume a structured antenna architecture in the rest of the disclosure. For simplicity, we assume each RRH/TRP is equivalent to a panel, although, an RRH/TRP can have multiple panels in practice. The 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, an RRH corresponds to a TRP.
In one example, an RRH or TRP corresponds to a CSI-RS resource. A UE is configured with
non-zero-power (NZP) CSI-RS resources, and a CSI reporting is configured to be across multiple CSI-RS resources. This is similar to Class B, K > 1 configuration in Rel. 14 LTE. The
NZP CSI-RS resources can belong to a CSI-RS resource set or multiple CSI-RS resource sets (e.g.,
resource sets each comprising one CSI-RS resource). The details are as explained earlier in this disclosure.
In one example, an RRH or TRP corresponds to a CSI-RS resource group, where a group comprises one or multiple NZP CSI-RS resources. A UE is configured with
non-zero-power (NZP) CSI-RS resources, and a CSI reporting is configured to be across multiple CSI-RS resources from resource groups. This is similar to Class B, K > 1 configuration in Rel. 14 LTE. The
NZP CSI-RS resources can belong to a CSI-RS resource set or multiple CSI-RS resource sets (e.g.,
resource sets each comprising one CSI-RS resource). The details are as explained earlier in this disclosure. In particular, the
CSI-RS resources can be partitioned into
resource groups. The information about the resource grouping can be provided together with the CSI-RS resource setting/configuration, or with the CSI reporting setting/configuration, or with the CSI-RS resource configuration.
In one example, an RRH or TRP corresponds to a subset (or a group) of CSI-RS ports. A UE is configured with at least one NZP CSI-RS resource comprising (or associated with) CSI-RS ports that can be grouped (or partitioned) multiple subsets/groups/parts of antenna ports, each corresponding to (or constituting) an RRH/TRP. The information about the subsets of ports or grouping of ports can be provided together with the CSI-RS resource setting/configuration, or with the CSI reporting setting/configuration, or with the CSI-RS resource configuration.
In one example, an RRH or TRP corresponds to one or more examples described above depending on a configuration. For example, this configuration can be explicit via a parameter (e.g., an RRC parameter). Alternatively, it can be implicit.
In one example, when implicit, it could be based on the value of
. For example, when
CSI-RS resources, an RRH corresponds to one or more examples described above, and when
CSI-RS resource, an RRH corresponds to one or more examples described above.
In another example, the configuration could be based on the configured codebook. For example, an RRH corresponds to a CSI-RS resource or resource group when the codebook corresponds to a decoupled codebook (modular or separate codebook for each RRH), and an RRH corresponds to a subset (or a group) of CSI-RS ports when codebook corresponds to a coupled (joint or coherent) codebook (one joint codebook across TRPs/RRHs).
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
CSI-RS resources are configured for
TRPs/RRHs, a decoupled (modular) codebook is used/configured, and when a single
CSI-RS resource for
TRPs/RRHs, a joint codebook is used/configured.
As described in U.S. Patent 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.
FIGURE 8 illustrates a 3D grid of oversampled DFT beams 800 according to an embodiment of the disclosure. The embodiment of the 3D grid of oversampled DFT beams 800 illustrated in FIGURE 8 is for illustration only. FIGURE 8 does not limit the scope of this disclosure to any particular implementation of the 3D grid of oversampled DFT beams.
As illustrated, FIGURE 8 shows a 3D grid 800 of the oversampled DFT beams (1st port dim., 2nd port dim., freq. dim.) in which:
a 1st dimension is associated with the 1st port dimension,
a 2nd dimension is associated with the 2nd port dimension, and
a 3rd dimension is associated with the frequency dimension.
The basis sets for 1st and 2nd port domain representation are oversampled DFT codebooks of length-N
1 and length-N
2, respectively, and with oversampling factors O
1 and O
2, respectively. Likewise, the basis set for frequency domain representation (i.e., 3rd dimension) is an oversampled DFT codebook of length-N
3 and with oversampling factor O
3. In one example, O
1 =
O
2 = O
3 = 4. In one example, O
1 =
O
2 = 4 and O
3 = 1. In another example, the oversampling factors O
i belongs to {2, 4, 8}. In yet another example, at least one of O
1,
O
2 , and O
3 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
, where
is the associated RI value, is given by either
or
where:
is a number of antenna ports in a first antenna port dimension (having the same antenna polarization),
is a number of antenna ports in a second antenna port dimension (having the same antenna polarization),
is a number of CSI-RS ports configured to the UE,
is a number of SBs for PMI reporting or number of FD units or number of FD components (that comprise the CSI reporting band) or a total number of precoding matrices indicated by the PMI (one for each FD unit/component),
is a
(Eq. 1) or
(Eq. 2) column vector, or
is a
(Eq. 1) or
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,
is a complex coefficient.
In a variation, when the UE reports a subset
coefficients (where
is either fixed, configured by the gNB or reported by the UE), then the coefficient
in precoder equations Eq. 1 or Eq. 2 is replaced with
, where:
if the coefficient
is reported by the UE according to some embodiments of this disclosure.
otherwise (i.e.,
is not reported by the UE).
The indication whether
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
and
where for a given
i, the number of basis vectors is
and the corresponding basis vectors are
Note that
is the number of coefficients
reported by the UE for a given
i,
where
(where
or
is either fixed, configured by the gNB or reported by the UE).
The columns of
are normalized to norm one. For rank
R or
R layers (
), 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
L ≤
and
M ≤
N
3. If
L =
, then
A is an identity matrix, and hence not reported. Likewise, if
M = N
3, then
B is an identity matrix, and hence not reported. Assuming
M <
N
3, in an example, to report columns of
B, the oversampled DFT codebook is used. For instance,
, where the quantity
is given by
When
, the FD basis vector for layer
(where
is the RI or rank value) is given by:
In another example, discrete cosine transform DCT basis is used to construct/report basis
B for the 3
rd dimension. The
-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 purposes only. The disclosure is applicable to any other basis vectors to construct/report A and B.
On a high level, a precoder
can be described as follows.
where
corresponds to the Rel. 15
in Type II CSI codebook [REF8], and
.
The
matrix consists of all the required linear combination coefficients (e.g., amplitude and phase or real or imaginary). Each reported coefficient (
) in
is quantized as amplitude coefficient
and phase coefficient (
). In one example, the amplitude coefficient
is reported using a A-bit amplitude codebook where
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
is reported as
where:
is a reference or first amplitude which is reported using an A1-bit amplitude codebook where
belongs to {2, 3, 4}, and
is a differential or second amplitude which is reported using a A2-bit amplitude codebook where
belongs to {2, 3, 4}.
For layer
let us denote the linear combination (LC) coefficient associated with spatial domain (SD) basis vector (or beam)
and frequency domain (FD) basis vector (or beam)
as
, and the strongest coefficient as
. The strongest coefficient is reported out of the
non-zero (NZ) coefficients that is reported using a bitmap, where
and
is higher layer configured. The remaining
coefficients that are not reported by the UE are assumed to be zero. The following quantization scheme is used to quantize/report the
NZ coefficients.
UE reports the following for the quantization of the NZ coefficients in
A
-bit indicator for the strongest coefficient index
, where
or
.
i. Strongest coefficient
(hence its amplitude/phase are not reported)
Two antenna polarization-specific reference amplitudes is used.
i. For the polarization associated with the strongest coefficient
, since the reference amplitude
= 1, it is not reported
ii. For the other polarization, reference amplitude
is quantized to 4 bits .
1. The 4-bit amplitude alphabet is
.
i. For each polarization, differential amplitudes
of the coefficients calculated relative to the associated polarization-specific reference amplitude and quantized to 3 bits.
1. The 3-bit amplitude alphabet is
.
2. Note: The final quantized amplitude
is given by
ii. Each phase is quantized to either 8PSK (
) or 16PSK (
) (which is configurable).
For the polarization
associated with the strongest coefficient
, we have
and the reference amplitude
. For the other polarization
and
, we have
and the reference amplitude
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
FD basis vectors. In one example,
, where
is higher-layer configured from
and
is higher-layer configured from
. In one example, the
value is higher-layer configured for rank 1-2 CSI reporting. For rank > 2 (e.g., rank 3-4), the
value (denoted by
) can be different. In one example, for rank 1-4,
is jointly configured from
, i.e.,
for rank 1-2 and
for rank 3-4. In one example,
where
is the number of SBs for CQI reporting. In one example,
is replaced with
to show its dependence on the rank value
, hence
is replaced with
and
is replaced with
.
A UE can be configured to report
FD basis vectors in one-step from
basis vectors freely (independently) for each layer
of a rank
CSI reporting. Alternatively, a UE can be configured to report
FD basis vectors in two-step as follows.
In
step 1, an intermediate set (InS) comprising
basis vectors is selected/reported, wherein the InS is common for all layers.
In
step 2, for each layer
of a rank
CSI reporting,
FD basis vectors are selected/reported freely (independently) from
basis vectors in the InS.
In one example, one-step method is used when
and two-step method is used when
In one example,
where
is either fixed (to 2 for example) or configurable.
The codebook parameters used in the DFT based frequency domain compression (Eq. 5) are
. The set of values for these codebook parameters are as follows.
: the set of values is
in general, except
for rank 1-2, 32 CSI-RS antenna ports, and
.
The set of values for these codebook parameters are as in Table 1.
[Table 1]
In Rel. 17 (further enhanced Type II port selecting codebook),
,
where
, and codebook parameters
are configured from Table 2.
[Table 2]
The above-mentioned framework (Eq. 5) represents the precoding-matrices for multiple
FD units using a linear combination (double sum) over
(or
) SD beams/ports and
FD beams. This framework can also be used to represent the precoding-matrices in time domain (TD) by replacing the FD basis matrix
with a TD basis matrix
, wherein the columns of
comprises
TD beams that represent some form of delays or channel tap locations. Hence, a precoder
can be described as follows.
In one example, the
TD beams (representing delays or channel tap locations) are selected from a set of
TD beams, i.e.,
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, the codebook can be a Rel. 15 Type I single-panel codebook (cf. 5.2.2.2.1, TS 38.214).
In one example, the codebook can be a Rel. 15 Type I multi-panel codebook (cf. 5.2.2.2.2, TS 38.214).
In one example, the codebook can be a Rel. 15 Type II codebook (cf. 5.2.2.2.3, TS 38.214).
In one example, the codebook can be a Rel. 15 port selection Type II codebook (cf. 5.2.2.2.4, TS 38.214).
In one example, the codebook can be a Rel. 16 enhanced Type II codebook (cf. 5.2.2.2.5, TS 38.214).
In one example, the codebook can be a Rel. 16 enhanced port selection Type II codebook (cf. 5.2.2.2.6, TS 38.214).
In one example, the codebook can be a Rel. 17 further enhanced port selection Type II codebook (cf. 5.2.2.2.7, TS 38.214).
In one example, the codebook is a new codebook for C-JT CSI reporting.
In one example, the new codebook is a decoupled codebook comprising the following components:
Intra-TRP: per TRP Rel. 16/17 Type II codebook components, i.e., SD basis vectors (W1), FD basis vectors (Wf), W2 components (e.g., SCI, indices of NZ coefficients, and amplitude/phase of NZ coefficients).
Inter-TRP: co-amplitude and co-phase for each TRP.
In one example, the new codebook is a joint codebook comprising following components:
Per TRP SD basis vectors (W1),
Single joint FD basis vectors (Wf), and
Single joint W2 components (e.g., SCI, indices of NZ coefficients, and amplitude/phase of NZ coefficients).
FIGURE 9 illustrates two new codebooks 900 according to an embodiment of the disclosure. The embodiment of the two new codebooks 900 illustrated in FIGURE 9 is for illustration only. FIGURE 9 does not limit the scope of this disclosure to any particular implementation of the two new codebooks 900.
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.,
, where
is the total number of antenna ports, and
is the number of antenna ports associated with
-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 example, each NZP CSI-RS resource comprises CSI-RS antenna ports for all TRPs/RRHs. i.e.,
, where
is the total number of antenna ports, and
is the number of antenna ports associated with
-th TRP. In this case, a TRP corresponds to (or maps to or is associated with) a group of antenna ports.
In one example, each NZP CSI-RS resource corresponds to (or maps to or is associated with) a TRP/RRH.
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 the codebook parameters (such as
or
) are configured via a higher-layer parameter '
paramCombination-r18'.
In one example, the Rel. 16 parameter combination table for '
paraCombination-r16' is reused for '
paramCombination-r18' (cf. Table 1).
In one example, the Rel. 17 parameter combination table for '
paraCombination-r17' is reused for '
paramCombination-r18' (cf. Table 2).
In one example, a new table of parameter combination is used for '
paramCombination-r18'.
In one example, a table including existing Rel. 16 or Rel. 17 parameter combination(s) and new parameter combination(s) is used for '
paramCombination-r18'.
In one embodiment,
value configured for TRPs depends on the number of TRPs
.
In one example,
is the same for all TRPs (i.e., TRP-common), and it depends on the number of TRPs (i.e., it can change depending on the value of
). For example,
In one example, the Rel.16 table of '
paraCombination-r16' is used (or not used), and the
value depends on the number of TRPs
, for example,
for 1 TRP,
(or
) for 2 TRPs,
(or
) for 3 TRPs, and
(or
) for 4 TRPs, where
is the configured value. For example, for the case of 4 TRPs, if
is indicated using the table of '
paraCombination-r16', the actual
value for each TRP is
.
In another example, the Rel. 16 table of '
paraCombination-r16' is used (or not used), and the
value depends on the number of TRPs in a pair-wise manner, for example,
for
, and
for
.
In another example, the Rel. 16 table of '
paraCombination-r16' is used (or not used), and the
value depends on the number of TRPs, for example,
for
,
for
,
for
.
In one example,
can be different for some or all TRPs.
In one example, the configured
value is applied to a strongest TRP, and
(or
) value is applied to the other remaining TRPs, where
or
can be fixed (e.g.,
,
) or configured, or reported by the UE.
In one example, the configured
value is applied to two strongest TRPs, and
(or
) value is applied to the other remaining TRPs, where
or
can be fixed (e.g.,
,
) or configured, or reported by the UE.
In another example,
is configured, where
is
value for TRP
. Under the constraint with the configured value of
, the UE (freely) selects
for TRP
. In this example,
can be configured using a similar table (or the same table) of '
paraCombination-r16', e.g., replacing
by
. In one example,
where
is the configured value and
is fixed (e.g., 2) or configured. In one example,,
. In one example,
. In one example,
.
In another example,
is configured for each TRP
. In one example,
is indicated using the table of '
paraCombination-r16'. In another example,
is indicated using a new table of '
paraCombination-r18'.
In another example,
is configured for a first group of TRPs, and
is configured for a second group of TRPs. In one example,
and
are indicated using the table of '
paraCombination-r16'. In one example,
and
are indicated using a new table of '
paraCombination-r18'. In anotherexample, a constraint of
should satisfy when selecting/indicating
.
In one example,
can be different for some or all TRPs, and it depends on the number of TRPs.
In one example,
depends on the number of TRPs. For example,
Under the constraint with the configured value of
, the UE (freely) selects
for TRP
. In this example,
can be configured using a similar table (or the same table) of '
paraCombination-r16', e.g., replacing
by
.
In one example, a pair of
can be configured. For example, gNB or NW can indicate one pair among (2,2), (3,2), (4,2), (1,3), (2,3), (3,3), (1,4), and (2,4).
In one example, the UE determines
value for TRPs, e.g.,
for strong TRPs, and
for weak TRPs, and the UE reports strong/weak TRP indices.
In one example,
is the same for all TRPs (i.e., TRP-common), and it depends on the number of TRPs (i.e., it can change depending on the value of
). For example,
In one example, the Rel.17 table of '
paraCombination-r17' is used (or not used), and the
value depends on the number of TRPs
, for example,
for 1 TRP,
for 2 TRPs,
for 3 TRPs, and
for 4 TRPs, where
is the configured value. For example, for the case of 4 TRPs, if
is indicated using the table of '
paraCombination-r17', the actual
value for each TRP is
.
In another example, the Rel. 17 table of '
paraCombination-r17' is used (or not used), and the
value depends on the number of TRPs in a pair-wise manner, for example,
for
, and
for
.
In another example, the Rel. 17 table of '
paraCombination-r17' is used (or not used), and the
value depends on the number of TRPs, for example,
for
,
for
,
for
.
In one example,
can be different for some or all TRPs.
In one example, the configured
value is applied to a strongest TRP, and
value is applied to the other remaining TRPs, where
can be fixed (e.g.,
) or configured, or reported by the UE.
In one example, the configured
value is applied to two strongest TRPs, and
value is applied to the other remaining TRPs, where
can be fixed (e.g.,
) or configured, or reported by the UE.
In another example,
is configured, where
is
value for TRP
. Under the constraint with the configured value of
, the UE (freely) selects
corresponding to
for TRP
. In this example,
can be configured using a similar table (or the same table) of '
paraCombination-r17', e.g., replacing
by
. In one example,
where
is the configured value and
is fixed (e.g., 2) or configured. In one example,
corresponding to
is less than or equal to
. In one example,
corresponding to
is less than or equal to 1. In one example,
corresponding to
is less than or equal to
.
In another example,
is configured for each TRP
. In one example,
is indicated using the Rel-17 table of '
paraCombination-r17'. In another example,
is indicated using a new table of '
paraCombination-r18'.
In another example,
is configured for a first group of TRPs, and
is configured for a second group of TRPs. In one example,
and
are indicated using the table of '
paraCombination-r17'. In one example,
and
are indicated using a new table of '
paraCombination-r18'. In another example, a constraint of
should satisfy when selecting/indicating
.
In one example,
can be different for some or all TRPs, and it depends on the number of TRPs.
In one example,
depends on the number of TRPs. For example,
Under the constraint with the configured value of
, the UE (freely) selects
corresponding to
for TRP
. In this example,
can be configured using a similar table (or the same table) of '
paraCombination-r17', e.g., replacing
by
.
In one example, a pair of
can be configured. For example, gNB or NW can indicate one pair among (1/2,2), (3/4,2), (1,2), (1/4,3), (1/2,3), (1,3), (1/4,4), and (1/2,4).
In one example, the UE determines
value for TRPs, e.g.,
for strong TRPs, and
for weak TRPs, and the UE reports strong/weak TRP indices.
In embodiment,
value for TRPs depends on the number of TRPs
.
can be configured to indicate
similar to Rel-16, e.g.,
.
can directly be configured without
value.
value can be rank-dependent (similar to Rel-16).
value is rank-dependent similar to Rel-16, that is
. We drop
index when it is not needed.
In one example,
is the same for all TRPs (i.e., TRP-common), and it depends on the number of TRPs (i.e., it can change depending on the value of
). For example,
In one example, the Rel-16 table of '
paraCombination-r16' is used (or not used), and the
value depends on the number of TRPs, for example,
for 1 TRP,
for 2 TRPs,
for 3 TRPs, and
for 4 TRPs, where
is the configured value. For example, for the case of 4 TRPs, if
is indicated using the table of '
paraCombination-r16', the actual
value for each TRP is
.
In another example, the Rel-16 table of '
paraCombination-r16' is used (or not used), and the
value depends on the number of TRPs in a pair-wise manner, for example,
for
, and
for
.
In another example, the Rel-16 table of '
paraCombination-r16' is used (or not used), and the
value depends on the number of TRPs, for example,
for
,
for
,
for
.
In one example,
can be different for some or all TRPs.
In one example,
value is applied to a strongest TRP, and
value is applied to the other remaining TRPs, where e.g.,
can be fixed to 2 or 3, or configured, or reported by the UE.
In one example,
value is applied to two strongest TRPs, and
value is applied to the other remaining TRPs, where e.g.,
can be fixed to 2 or 3, or configured, or reported by the UE.
In another example, let
and
is configured to indicate
, where
is
value for TRP
. Under the constraint with the configured value of
, the UE (freely) selects
for TRP
. In this example,
can be configured using a similar table (or the same table) of '
paraCombination-r16', e.g., replacing
by
. In one example,
where
is the configured value and
is fixed (e.g., 2) or configured. In one example,
. In one example,
. In one example,
.
In another example,
is configured for each TRP
. In one example,
is indicated using the table of '
paraCombination-r16'. In another example,
is indicated using a new table of '
paraCombination-r18'.
In another example,
is configured for a first group of TRPs, and
is configured for a second group of TRPs. In one example,
and
are indicated using the table of '
paraCombination-r16'. In one example,
and
are indicated using a new table of '
paraCombination-r18'. In another example, a constraint of
should satisfy when selecting/indicating
.
In one example,
can be different for some or all TRPs, and it depends on the number of TRPs.
In one example,
depends on the number of TRPs, and
is configured to indicate
. For example,
Under the constraint with the configured value of
(i.e.,
) , the UE (freely) selects
for TRP
. In this example,
can be configured using a similar table (or the same table) of '
paraCombination-r16', e.g., replacing
by
.
In one example,
can be rank-dependent similar to Rel-16 for
.
In one example, a pair of
can be configured. For example, gNB or NW can indicate one pair among
In one example, the UE determines
value for TRPs, e.g.,
for strong TRPs, and
for weak TRPs, and the UE reports strong/weak TRP indices.
In one example,
is the same for all TRPs (i.e., TRP-common), and it depends on the number of TRPs (i.e., it can change depending on the value of
). For example,
In one example, the Rel-17 table of '
paraCombination-r17' is used (or not used), and the
value depends on the number of TRPs, for example,
for 1 TRP,
(or
) for 2 TRPs,
(or
) for 3 TRPs, and
(or
) for 4 TRPs, where
is the configured value. For example, for the case of 4 TRPs, if
is indicated using the table of '
paraCombination-r16', the actual
value for each TRP is
.
In another example, the Rel-17 table of '
paraCombination-r17' is used (or not used), and the
value depends on the number of TRPs in a pair-wise manner, for example,
for
, and
for
.
In another example, the Rel-17 table of '
paraCombination-r17' is used (or not used), and the
value depends on the number of TRPs, for example,
for
,
for
,
for
.
In one example,
can be different for some or all TRPs.
In one example,
value is applied to a strongest TRP, and
value is applied to the other remaining TRPs, where e.g.,
can be fixed to 2 or 3, or configured, or reported by the UE.
In one example,
value is applied to two strongest TRPs, and
value is applied to the other remaining TRPs, where e.g.,
can be fixed to 2 or 3, or configured, or reported by the UE.
In another example,
is configured, where
is
value for TRP
. Under the constraint with the configured value of
, the UE (freely) selects
for TRP
. In this example,
can be configured using a similar table (or the same table) of '
paraCombination-r17', e.g., replacing
by
. In one example,
where
is the configured value and
is fixed (e.g., 2) or configured. In one example,
. In one example,
. In one example,
.
In another example,
is configured for each TRP
. In one example,
is indicated using the table (or a similar table) of '
paraCombination-r17'. In another example,
is indicated using a new table of '
paraCombination-r18'.
In another example,
is configured for a first group of TRPs, and
is configured for a second group of TRPs. In one example,
and
are indicated using the table (or a similar table) of '
paraCombination-r17'. In one example,
and
are indicated using a new table of '
paraCombination-r18'. In another example, a constraint of
should satisfy when selecting/indicating
.
In one example,
can be different for some or all TRPs, and it depends on the number of TRPs.
In one example,
depends on the number of TRPs, For example,
Under the constraint with the configured value of
, the UE (freely) selects
for TRP
. In this example,
can be configured using a similar table (or the same table) of '
paraCombination-r17', e.g., replacing
by
.
In one example,
can be rank-dependent similar to Rel-16 for
.
In one example, a pair of
can be configured. For example, gNB or NW can indicate one pair among (1,2), (2,2), (3,2), (1,3), (2,3), (3,3), (1,4), and (2,4).
In one embodiment,
values for TRPs depend on the number of TRPs
. Any combination of
in certain embodiments herein and
(or
) in certain embodiments herein can be applicable to this embodiment.
In one embodiment,
value configured for TRPs depends on the number of TRPs
.
In one example,
is the same for all TRPs (i.e., TRP-common), and it depends on the number of TRPs (i.e., it can change depending on the value of
).
In one example, the Rel.16 table of '
paraCombination-r16' is used (or not used), and the
and
values depend on the number of TRPs
, for example,
for 1 TRP,
(or
) and
for 2 TRPs,
(or
) and
for 3 TRPs, and
(or
) and
for 4 TRPs, where
is the configured value. For example, for the case of 4 TRPs, if
is indicated using the table of '
paraCombination-r16', the actual
value for each TRP is
and
.
In another example, the Rel. 16 table of '
paraCombination-r16' is used (or not used), and the
and
values depend on the number of TRPs in a pair-wise manner, for example,
and
for
, and
and
for
.
In another example, the Rel. 16 table of '
paraCombination-r16' is used (or not used), and the
and
values depend on the number of TRPs, for example,
and
for
,
and
for
,
and
for
.
In one example,
and
can be different for some or all TRPs.
In one example, the configured
and
values are applied to a strongest TRP, and
(or
) and
values are applied to the other remaining TRPs, where
or
and
can be fixed
or configured, or reported by the UE. In one example,
.
In one example, the configured
and
values are applied to two strongest TRPs,
(or
) and
values are applied to the other remaining TRPs, where
or
and
can be fixed
or configured, or reported by the UE. In one example,
.
In another example,
and
are configured, where
is
value for TRP
and
is
value for TRP
n. Under the constraint with the configured values of
and
, the UE (freely) selects
and
(corresponding to
) for TRP
. In this example,
and
can be configured using a similar table (or the same table) of '
paraCombination-r16', e.g., replacing
by
and
by
, respectively. In one example,
where
is the configured value and
is fixed (e.g., 2) or configured. In one example,
. In one example,
. In one example,
. In one example,
where
is the configured value and
is fixed (e.g., 2) or configured. In one example,
. In one example,
. In one example,
. In one example,
.
In another example,
and
are configured for each TRP
. In one example,
and
are indicated using the table of '
paraCombination-r16'. In another example,
and
are indicated using a new table of '
paraCombination-r18'.
In another example,
and
are configured for a first group of TRPs, and
and
configured for a second group of TRPs. In one example,
and
, and
and
are indicated using the table of '
paraCombination-r16'. In one example,
and
and
and
are indicated using a new table of '
paraCombination-r18'. In another example, a constraint of
should satisfy when selecting/indicating
. In another example, a constraint of
should satisfy when selecting/indicating
.
In one example,
and
can be different for some or all TRPs, and it depends on the number of TRPs.
In one example,
and
depend on the number of TRPs.
Under the constraint with the configured values of
and
, the UE (freely) selects
and
for TRP
. In this example,
and
can be configured using a similar table (or the same table) of '
paraCombination-r16', e.g., replacing
by
and
by
, respectively.
In one example, a tuple of
can be configured. For example, gNB or NW can indicate one tuple among (2,1/4, 2), (3,1/4,2), (4,1/8,2), (1,1/4,3), (2,1/8,3), (3,1/8,3), (1,1/8,4), and (2,1/8,4).
In one example, the UE determines
and
values for TRPs, e.g.,
and
for strong TRPs, and
and
for weak TRPs, and the UE reports strong/weak TRP indices.
In one embodiment, a table of 'paraCombination-r18' is designed based on the existing Rel. 16/17 table for 'paraCombination-r16' (Table 1) or 'paraCombination-r17' (Table 2), and the UE can be configured using the table for codebook parameters.
In one example, one value (
) from the table of '
paraCombination-r16' or '
paraCombination-r17' is configured for a strongest TRP (or two strongest TRPs), and another value (
) from the table of '
paraCombination-r16' or '
paraCombination-r17' is configured for the remaining TRPs.
In one example, one value (
) from the table of '
paraCombination-r16' or '
paraCombination-r17' is configured for a strongest TRP (or two strongest TRPs), and another value (
) from the table of '
paraCombination-r16' or '
paraCombination-r17' is fixed for the remaining TRPs, e.g.,
.
In one example, one value (
) from the table of '
paraCombination-r16' or '
paraCombination-r17' is configured for a strongest TRP (or two strongest TRPs), and another value (
) from the table of '
paraCombination-r16' or '
paraCombination-r17' is determined based on
for the remaining TRPs, in one example,,
. For example,
, or
.
In one example, one value (
) from the table of '
paraCombination-r16' or '
paraCombination-r17' is configured for a strongest TRP (or two strongest TRPs), and another value (
) from the table of '
paraCombination-r16' or '
paraCombination-r17' is configured with a restriction based on
for the remaining TRPs, e.g.,
. For example, if
, then
is selected from {1,2,3,4}.
The UE can report a strongest TRP index (or indices of 2 or a few strongest TRPs) in the relevant examples above or below.
In one example,
from the table of '
paraCombination-r16' or '
paraCombination-r17' is configured for TRP
for
.
In one example, some restriction on
can be applied to select
. For example, a total number of
beams across TRPs (i.e.,
) can be constrained. For example, if
and
,
can be one possible value.
In one example, some restriction on
(or
) can be applied to select
. For example, a total number of
beams across TRPs (i.e.,
) can be constrained.
In one example, some restriction on
(or
) and
can be applied to select
. For example, a total number of
beams across TRPs (i.e.,
) and a total number of
beams (i.e.,
) can be constrained.
In one example, a table of 'paraCombination-r18' is designed based on a mixed version of the existing tables for 'paraCombination-r16' or 'paraCombination-r17' and a new parameter-combination table, and the UE can be configured using the table for codebook parameters.
In one example, the new table includes combinations with new
value(s). For example, the new L value(s) can include 1 or 3 (or 5). An example is described in Table 3.
In one example,
is not included in the table.
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'.
[Table 3]
In one example, the new table includes combinations with new
value(s). For example, the new
value(s) can include 1/4 or 1/8, or1/16. An example is described in Table 4.
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'.
[Table 4]
In one example, the new table includes combinations with new
value(s). For example, the new
value(s) can include 1/6 or 1/10 or 1/16. An example is described in Table 5.
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'.
[Table 5]
In one example, the new table includes combinations with new
value(s). For example, the new
value(s) can include (1,1/8) or (1,1/6), (1,1/10), (1,1/16), (3,1/8), (3,1/6), (3,1/10), or (3,16). An example is described in Table 6.
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'.
[Table 6]
In one example, the new table includes new
(or
) and
(or
) values.
In one example, the new table includes
(or
) and
values. In one example, new values of
such as
,
, … can be included in the table.
In one example, the new table includes
(or
) and
values. In one example, new values of
such as
, … can be included in the table.
In one example, the new table includes
(or
),
(or
), and
values. In one example, new values of
such as
, … can be included in the table.
In one example, the new table includes
(or
) values.
In one example, the new table includes
(or
) and
(or
) values.
In one example, the new table includes
(or
) and
values.
In one example, the new table includes
(or
) and
values.
In one example, the new table includes
(or
),
(or
), and
values.
Here, the '
X' in the new table means a relationship from X value selected/configured using the existing table. In one example, the relationship corresponds to subtraction (e.g.,
, where
is a value selected from the existing table, and
is a value selected from the new table. Here, e.g.,
could be 0,1,2,..and so on). In another example, the relationship corresponds to division, (e.g.,
, where
is a value selected from the existing table, and
is a value selected from the new table. Here,
and so on.)
In one example, the new table includes any combination of the above parameters. For example, the new table includes
,
, and
.
In one example, one value (
) from the table of '
paraCombination-r16' (Table 1) or '
paraCombination-r17' (Table 2) is configured for a strongest TRP (or two strongest TRPs), and another value (
) from a new parameter-combination table (e.g., a table including at least one of combinations provided in Tables 3-6) is configured for the remaining TRPs.
In one example, one value (
) from the table of '
paraCombination-r16' (Table 1) or '
paraCombination-r17' (Table 2) is configured for a strongest TRP (or two strongest TRPs), and another value (
) from a new parameter-combination table (e.g., a table including at least one of combinations provided in Tables 3-6) is (implicitly) determined based on
for the remaining TRPs.
In one example, one value (
) from the table of '
paraCombination-r16' (Table 1) or '
paraCombination-r17' (Table 2) is configured for a strongest TRP (or two strongest TRPs), and another value (
) from a new parameter-combination table (e.g., a table including at least one of combinations provided in Tables 3-6) is configured with a restriction based on
for the remaining TRPs.
The UE can report a strongest TRP index (or indices of 2 or a few strongest TRPs) in the relevant examples above or below.
In embodiment, a new parameter-combination table of 'paraCombination-r18' is designed, and the UE can be configured using the table for codebook parameters.
In one example, a new parameter-combination table of '
paraCombination-r18' is codebook-common and the number of TRPs-common (i.e.,
-common). Here the codebook-common means that a same table is used for CB1 and CB2.
In one example, a new parameter-combination table of '
paraCombination-r18' is codebook-specific and
-common. For example, as shown in Figure 9, a new parameter-combination table of '
paraCombination-r18' is specifically designed for CB1 and CB2, respectively.
In one example, a new parameter-combination table of '
paraCombination-r18' is codebook-common and
-specific. For example, as shown in Figure 9, a new parameter-combination table of '
paraCombination-r18' is specifically designed for
.
In one example, a new parameter-combination table of '
paraCombination-r18' is codebook-specific and
-specific. For example, as shown in Figure 9, for
, a new parameter-combination table of '
paraCombination-r18' is specifically designed for CB1 and CB2, respectively.
In one embodiment, a common table of 'paraCombination-r18' is designed for both Rel-16 Type-II codebook-based mTRP CJT codebook and Type-II port selection codebook-based mTRP CJT codebook. In other words, one common table is used for both the mTRP CJT codebooks design based on Rel-16 Type-II (regular) codebook and Rel-17 Type-II port selection codebook. The UE can be configured using the table for codebook parameters for mTRP CJT codebooks.
In one example, the common table is designed using parameters (
) (similar to Rel-16 parameter combination). For example, any combination of parameters for
described in certain embodiments herein can be included in the common table.
In one example, the common table is designed using parameters (
) (similar to Rel-17 parameter combination). For example, any combination of parameters for
described in certain embodiments herein can be included in the common table.
In one example, the common table is designed using parameters (
). For example, any combination of parameters for
described in certain embodiments herein can be included in the common table.
In one example, the common table is designed using parameters (
). For example, any combination of parameters for
described in certain embodiments herein can be included in the common table.
In one example, the common table is designed using a combination of legacy parameters (
). and new parameter value(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
, where the component
is used to report/indicate a spatial-domain (SD) basis matrix comprising SD basis vectors, the component
is used to report/indicate a frequency-domain (FD) basis matrix comprising FD basis vectors, and the component
is used to report/indicate coefficients corresponding to SD and FD basis vectors.
In one example, in Rel-16 Type-II codebook,
vectors,
, are identified by the indices
,
, indicated by
,
, obtained as in 5.2.2.2.3, where the values of
are given in Table 5.2.2.2.5-4 of [9].
In Rel-18 Type-II codebook for multi-TRP,
SD basis vectors for each TRP
can be selected/reported, where we denote that
is a number of SD basis vectors for TRP
(CSI-RS resource
).
In one embodiment, on the SD basis selection for (Rel-18) Type-II codebook refinement for CJT mTRP, each of the
is configured by NW via higher-layer (RRC) signaling, where
is a number of TRPs configured by the NW.
In one example,
. In one example,
. In one example,
. In one example, In one example,
. In one example,
. In one example,
. In one example,
can be selected from
, where
is a subset of
.
In one embodiment, on the SD basis selection for (Rel-18) Type-II codebook refinement for CJT mTRP,
is configured by NW via higher-layer (RRC) signaling and the relative value(s) of
are reported by the UE, where
is a number of TRPs configured by the NW. Although we denote
for
, another notation can be used for
, such as
,
,
, etc. In one example,
.
In one example,
. In one example,
. In one example,
. In one example, In one example,
. In one example,
.
In one example,
. In one example,
can be selected from
, where
is a subset of
.
In one example,
for
and
for
, where
and
is a subset of
and
.
In one example,
for
and
for
, where
and
is a subset of
and
.
In one example,
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
under the constraint of
and
for
where
is a non-negative integer. In another example, an indicator can be used to indicate each
for
under the constraint of
and
.
In one example,
SD basis vector selection for each TRP
is reported via a joint indicator or separate multiple indicators in
CSI part 2.
In one example, an indicator to indicate (each)
SD basis vectors has the payload of
bits (bit-width), where
and
are the values of (
) configured via higher-layer (RRC) signaling by the NW. For any TRP
where
(i.e., no SD beam selection case) and/or where TRP
is not selected which can be indicated via
-bit bitmap in
CSI part 1, no SD basis vector for TRP
is reported, hence no payload is induced.
In one example, a joint indicator to indicate
SD basis vectors has the payload of
bits (bit-width). For any TRP
where
(i.e., no SD beam selection case) and/or where TRP
is not selected which can be indicated via
-bit bitmap in
CSI part 1, no SD basis vector for TRP
is reported, hence no additional payload is induced in the sum.
In one example,
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,
-bit bitmap is used to indicate selected
TRPs out of
TRPs. For example, when
and
-bit bitmap is '1001' in CSI part 1, the first TRP and the fourth TRP are selected. In this example,
associated with the selected TRPs are explicitly reported.
In one example, a joint indicator can be used to indicate
under the constraint of
and
for
where
is a positive integer and
is a set of selected TRP indexes (i.e., a subset of
.
In one example, a joint indicator can be used to indicate
under the constraint of
and
for
where
is a positive integer.
In one example, an indicator can be used to indicate each
for
under the constraint of
and
where
is a positive integer and
is a set of selected TRP indexes (i.e., a subset of
.
In one example, an indicator can be used to indicate each
for
under the constraint of
and
, for
where
is a positive integer.
In one example,
SD basis vector selection for each TRP
is reported via a joint indicator or separate multiple indicators in
CSI part 2.
In one example, an indicator to indicate (each)
SD basis vectors has the payload of
bits (bit-width), where
and
are the values of (
) configured via higher-layer (RRC) signaling by the NW, where
or
.
In one example, a joint indicator to indicate
SD basis vectors has the payload of
bits or
bits.
In one example,
s 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.
In one example, some of
are explicitly reported via a joint indicator or separate multiple indicators in
CSI part 1 and the others of
are reported implicitly (or determined implicitly hence not explicitly reported).
In one example, a joint indicator can be used to indicate
, (i.e., excluding
with the highest index), and
is implicitly determined by
and
hence
is not reported. Here,
for
where
is a non-negative integer.
In one example, a joint indicator can be used to indicate
, (i.e., excluding
with the lowest index), and
is implicitly determined by
and
hence
is not reported. Here,
for
where
is a non-negative integer.
In one example, a joint indicator can be used to indicate
(i.e., excluding
with a reference TRP index
, which can be determined by UE or configured by NW or determined by a pre-defined rule), and
is implicitly determined by
and
hence
is not reported. Here,
for
where
is a non-negative integer.
In one example, an indicator can be used to indicate each
for
(i.e., excluding
with the highest index), and
is implicitly determined by
and
hence
is not reported. Here,
for
where
is a non-negative integer.
In one example, an indicator can be used to indicate each
for
(i.e., excluding
with the lowest index), and
is implicitly determined by
and
hence
is not reported. Here,
for
where
is a non-negative integer.
In one example, an indicator can be used to indicate each
for
(i.e., excluding
with a reference TRP index
, which can be determined by UE or configured by NW or determined by a pre-defined rule), and
is implicitly determined by
and
hence
is not reported. Here,
for
where
is a non-negative integer.
In one example,
SD basis vector selection for each TRP
is reported via a joint indicator or separate multiple indicators in
CSI part 2.
In one example, an indicator to indicate (each)
SD basis vectors has the payload of
bits (bit-width), where
and
are the values of (
) configured via higher-layer (RRC) signaling by the NW. For any TRP
where
(i.e., no SD beam selection case) and/or where TRP
is not selected which can be indicated via
-bit bitmap in
CSI part 1, no SD basis vector for TRP
is reported, hence no payload is induced.
· In one example, a joint indicator to indicate
SD basis vectors has the payload of
bits (bit-width). For any TRP
where
(i.e., no SD beam selection case) and/or where TRP
is not selected which can be indicated via
-bit bitmap in
CSI part 1, no SD basis vector for TRP
is reported, hence no additional payload is induced in the sum.
In one example, some of
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
associated with TRPs that are selected are reported implicitly (or determined implicitly hence not explicitly reported). In CSI part 1,
-bit bitmap is used to indicate selected
TRPs out of
TRPs. For example, when
and
-bit bitmap is '1001' in
CSI part 1, the first TRP and the fourth TRP are selected. In this example, some of
associated with the selected TRPs are explicitly reported and the others are implicitly determined.
In one example, a joint indicator can be used to indicate
and
is implicitly determined by
and
and
for
where
is a positive integer and
is a set of selected TRP indexes (i.e., a subset of
) and
is the lowest index in
.
In one example, a joint indicator can be used to indicate
and
is implicitly determined by
and
and
for
where
is a positive integer and
is a set of selected TRP indexes (i.e., a subset of
) and
is the highest index in
.
In one example, a joint indicator can be used to indicate
and
is implicitly determined by
and
and
for
where
is a positive integer and
is a set of selected TRP indexes (i.e., a subset of
) and
is a reference TRP index in
, which can be determined by UE or configured by NW or determined by a pre-defined rule
.
In one example, a joint indicator can be used to indicate
and
is implicitly determined by
and
and
for
where
is a positive integer.
In one example, a joint indicator can be used to indicate
and
is implicitly determined by
and
and
for
where
is a positive integer.
In one example, a joint indicator can be used to indicate
and
is implicitly determined by
and
and
for
where
is a positive integer.
In one example, an indicator can be used to indicate each
for
and
is implicitly determined by
and
and
for
where
is a positive integer and
is a set of selected TRP indexes (i.e., a subset of
) and
is the lowest index in
.
In one example, an indicator can be used to indicate each
for
and
is implicitly determined by
and
and
for
where
is a positive integer and
is a set of selected TRP indexes (i.e., a subset of
) and
is the highest index in
.
In one example, an indicator can be used to indicate each
for
and
is implicitly determined by
and
and
for
where
is a positive integer and
is a set of selected TRP index
es (i.e., a subset of
)
and
is a reference TRP index in
, which can be determined by UE or configured by NW or determined by a pre-defined rule
.
In one example, an indicator can be used to indicate each
for
and
is implicitly determined by
and
and
for
where
is a positive integer.
In one example, an indicator can be used to indicate each
for
and
is implicitly determined by
and
and
for
where
is a positive integer.
In one example, an indicator can be used to indicate each
for
and
is implicitly determined by
and
and
for
where
is a positive integer.
In one example,
SD basis vector selection for each TRP
is reported via a joint indicator or separate multiple indicators in
CSI part 2.
In one example, an indicator to indicate (each)
SD basis vectors has the payload of
bits (bit-width), where
and
are the values of (
) configured via higher-layer (RRC) signaling by the NW, where
or
.
In one example, a joint indicator to indicate
SD basis vectors has the payload of
bits or
bits.
In one example, some of
s 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
s associated with TRPs that are selected are reported implicitly (or determined implicitly hence not explicitly reported). The remaining part is similar to other examples described herein.
In one example,
are reported implicitly, according to at least one of the following examples.
In one example,
SD basis vectors are selected among all candidates of SD basis vectors across
TRPs and the selection of
SD basis vectors is reported via an indicator with size of
bits in CSI part 1. In this case,
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,
SD basis vectors are selected among all candidates of SD basis vectors across
TRPs and the selection of
SD basis vectors is reported via an indicator with size of
bits in CSI part 2. In this case,
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,
SD basis vectors are selected among all candidates of SD basis vectors across
TRPs, where
is a number of selected TRPs. For example, in CSI part 1,
-bit bitmap is used to indicate selected
TRPs out of
TRPs. For example, when
and
-bit bitmap is '1001' in
CSI part 1, the first TRP and the fourth TRP are selected. The selection of
SD basis vectors is reported via an indicator with size of
bits in CSI part 1. In this case,
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,
SD basis vectors are selected among all candidates of SD basis vectors across
TRPs, where
is a number of selected TRPs. For example, in CSI part 1,
-bit bitmap is used to indicate selected
TRPs out of
TRPs. For example, when
and
-bit bitmap is '1001' in
CSI part 1, the first TRP and the fourth TRP are selected. The selection of
SD basis vectors is reported via an indicator with size of
bits in CSI part 2. In this case,
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, for a given
, a set
for the value of
for
is predetermined and an element of the set is selected and reported. For example, a combination of the elements each of which corresponds to
is reported via a joint indicator or separate multiple indicators (that indicate(s) the index of the selected element in the set) in
CSI part 1.
In one example,
is a subset of
. In one example,
is a subset of
. For example,
. For example,
. For example,
. For example,
.
In one example,
SD basis vector selection for each TRP
is reported via a joint indicator or separate multiple indicators in
CSI part 2.
In one example, an indicator to indicate (each)
SD basis vectors has the payload of
bits (bit-width), where
and
are the values of (
) configured via higher-layer (RRC) signaling by the NW. For any TRP
where
(i.e., no SD beam selection case) and/or where TRP
is not selected which can be indicated via
-bit bitmap in
CSI part 1, no SD basis vector for TRP
is reported, hence no payload is induced.
In one example, a joint indicator to indicate
SD basis vectors has the payload of
bits (bit-width). For any TRP
where
(i.e., no SD beam selection case) and/or where TRP
is not selected which can be indicated via
-bit bitmap in
CSI part 1, no SD basis vector for TRP
is reported, hence no additional payload is induced in the sum.
In one example, for a given
, a set
for the value of
for
or
is predetermined and an index of the set is selected and reported, where
is a set of selected TRPs. (For example, in CSI part 1,
-bit bitmap is used to indicate selected
TRPs out of
TRPs. For example, when
and
-bit bitmap is '1001' in
CSI part 1, the first TRP and the fourth TRP are selected.) In one example, a combination of indexes each of which corresponds to
is reported via a joint indicator or separate multiple indicators in
CSI part 1.
In one example,
is a subset of
. In one example,
is a subset of
. For example,
. For example,
. For example,
. For example,
.
In one example,
SD basis vector selection for each TRP
is reported via a joint indicator or separate multiple indicators in
CSI part 2.
In one example, an indicator to indicate (each)
SD basis vectors has the payload of
bits (bit-width), where
and
are the values of (
) configured via higher-layer (RRC) signaling by the NW, where
or
.
In one example, a joint indicator to indicate
SD basis vectors has the payload of
bits or
bits.
In one example, for a given
, a set for the value of
for
or
is predetermined and an index of the set is selected and reported, where
is a set of selected TRPs. (For example, in CSI part 1,
-bit bitmap is used to indicate selected
TRPs out of
TRPs. For example, when
and
-bit bitmap is '1001' in
CSI part 1, the first TRP and the fourth TRP are selected.) In one example, a combination of indexes each of which corresponds to
is reported via a joint indicator or separate multiple indicators in
CSI part 2. The remaining part is similar to or same as other examples described herein.
In one embodiment, on the SD basis selection for (Rel-18) Type-II codebook refinement for CJT mTRP, an
parameter is configured by NW via higher-layer (RRC) signaling and
are determined from the value of
, where
is a number of TRPs configured by the NW. In one example,
.
In one example, one
value is associated with a reference TRP
and another value determined from
is associated with the remaining
(or
) TRPs. In one example,
and
for
. In one example,
and
for
, where
and so on.
In one example, a reference TRP
is configured by NW.
In one example, a reference TRP
is determined by UE and reported in
CSI part 1 or
CSI part 2.
In one example, a reference TRP
is fixed to 1 or the last index, e.g.,
or
, or another value
In one embodiment, on the SD basis selection for (Rel-18) Type-II codebook refinement for CJT mTRP,
is configured by NW via higher-layer (RRC) signaling and the relative value(s) of
are reported by the UE, where
is a number of TRPs configured by the NW. Although we denote
for an upper bound of
, another notation can be used for
, such as
,
,
, etc. In one example,
.
In one example,
. In one example,
. In one example,
. In one example, In one example,
. In one example,
.
In one example,
. In one example,
can be selected from
, where
is a subset of
.
In one example,
for
and
for
, where
and
is a subset of
and
.
In one example,
for
and
for
, where
and
is a subset of
and
.
In one example,
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
under the constraint of
and
for
where
is a non-negative integer. In another example, an indicator can be used to indicate each
for
under the constraint of
and
. In one example, each
is selected from a set
and indicated via
-bit indicator. So, in this case,
-bit indicators can be used. In one example,
In one example,
In one example,
In one example,
In one example,
In one example,
In one example,
is a subset of {1,2,3,4,5,6}.
In one example,
SD basis vector selection for each TRP
is reported via a joint indicator or separate multiple indicators in
CSI part 2.
In one example, an indicator to indicate (each)
SD basis vectors has the payload of
bits (bit-width), where
and
are the values of (
) configured via higher-layer (RRC) signaling by the NW. For any TRP
where
(i.e., no SD beam selection case) and/or where TRP
is not selected which can be indicated via
-bit bitmap in
CSI part 1, no SD basis vector for TRP
is reported, hence no payload is induced.
In one example, a joint indicator to indicate
SD basis vectors has the payload of
bits (bit-width). For any TRP
where
(i.e., no SD beam selection case) and/or where TRP
is not selected which can be indicated via
-bit bitmap in
CSI part 1, no SD basis vector for TRP
is reported, hence no additional payload is induced in the sum.
In one example,
s 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,
-bit bitmap is used to indicate selected
TRPs out of
TRPs. For example, when
and
-bit bitmap is '1001' in CSI part 1, the first TRP and the fourth TRP are selected. In this example,
associated with the selected TRPs are explicitly reported.
In one example, a joint indicator can be used to indicate
under the constraint of
and
for
where
is a positive integer and
is a set of selected TRP indexes (i.e., a subset of
.
In one example, a joint indicator can be used to indicate
under the constraint of
and
for
where
is a positive integer.
In one example, an indicator can be used to indicate each
for
under the constraint of
and
where
is a positive integer and
is a set of selected TRP indexes (i.e., a subset of
. In one example, each
is selected from a set
and indicated via
-bit indicator. So, in this case,
-bit indicators can be used. In one example,
In one example,
In one example,
In one example,
In one example,
In one example,
In one example,
is a subset of {1,2,3,4,5,6}.
In one example, an indicator can be used to indicate each
for
under the constraint of
and
, for
where
is a positive integer. In one example, each
is selected from a set
and indicated via
-bit indicator. So, in this case,
-bit indicators can be used. In one example,
In one example,
In one example,
In one example,
In one example,
In one example,
In one example,
is a subset of {1,2,3,4,5,6}.
In one example,
SD basis vector selection for each TRP
is reported via a joint indicator or separate multiple indicators in
CSI part 2.
In one example, an indicator to indicate (each)
SD basis vectors has the payload of
bits (bit-width), where
and
are the values of (
) configured via higher-layer (RRC) signaling by the NW, where
or
.
In one example, a joint indicator to indicate
SD basis vectors has the payload of
bits or
bits.
In one example,
s 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
and
-bit bitmap is '1001' in CSI part 1, the first TRP and the fourth TRP are selected. In this example,
associated with the selected TRPs are explicitly reported.
In one example, a joint indicator can be used to indicate
under the constraint of
and
for
where
is a positive integer and
is a set of selected TRP indexes (i.e., a subset of
.
In one example, a joint indicator can be used to indicate
under the constraint of
and
for
where
is a positive integer.
In one example, an indicator can be used to indicate each
for
under the constraint of
and
where
is a positive integer and
is a set of selected TRP indexes (i.e., a subset of
. In one example, each
is selected from a set
and indicated via
-bit indicator. So, in this case,
-bit indicators can be used. In one example,
In one example,
In one example,
In one example,
In one example,
In one example,
In one example,
is a subset of {1,2,3,4,5,6}.
In one example, an indicator can be used to indicate each
for
under the constraint of
and
, for
where
is a positive integer. In one example, each
is selected from a set
and indicated via
-bit indicator. So, in this case,
-bit indicators can be used. In one example,
In one example,
In one example,
In one example,
In one example,
In one example,
In one example,
is a subset of {1,2,3,4,5,6}.
In one example,
SD basis vector selection for each TRP
is reported via a joint indicator or separate multiple indicators in
CSI part 2.
In one example, an indicator to indicate (each)
SD basis vectors has the payload of
bits (bit-width), where
and
are the values of (
) configured via higher-layer (RRC) signaling by the NW, where
or
.
In one example, a joint indicator to indicate
SD basis vectors has the payload of
bits or
bits.
In one embodiment,
is determined by UE where
and the determined
is reported in
CSI part 1. In one example, an indicator to indicate
has the size of payload
bits, i.e.,
is selected from
. In another example, an indicator to indicate
has the size of payload
bits, where
is a set including
and positive integers less than or equal to
, and
is a number of the elements in
. In one example,
can be any subset of
. In one example,
can be any subset of
.
In one example,
. In one example,
. In one example,
. In one example, In one example,
. In one example,
.
In one example,
. In one example,
can be selected from a subset of
.
In one example,
. In one example,
. In one example,
. In one example, In one example,
. In one example,
.
In one example,
. In one example,
can be selected from a subset of
.
In one example, some of
are explicitly reported via a joint indicator or separate multiple indicators in
CSI part 1 and the others of
are reported implicitly (or determined implicitly hence not explicitly reported).
In one example, a joint indicator can be used to indicate
, (i.e., excluding
with the highest index), and
is implicitly determined by
and
hence
is not reported. Here,
for
where
is a non-negative integer.
In one example, a joint indicator can be used to indicate
, (i.e., excluding
with the lowest index), and
is implicitly determined by
and
hence
is not reported. Here,
for
where
is a non-negative integer.
In one example, a joint indicator can be used to indicate
(i.e., excluding
with a reference TRP index
, which can be determined by UE or configured by NW or determined by a pre-defined rule), and
is implicitly determined by
and
hence
is not reported. Here,
for
where
is a non-negative integer.
In one example, an indicator can be used to indicate each
for
(i.e., excluding
with the highest index), and
is implicitly determined by
and
hence
is not reported. Here,
for
where
is a non-negative integer.
In one example, an indicator can be used to indicate each
for
(i.e., excluding
with the lowest index), and
is implicitly determined by
and
hence
is not reported. Here,
for
where
is a non-negative integer.
In one example, an indicator can be used to indicate each
for
(i.e., excluding
with a reference TRP index
, which can be determined by UE or configured by NW or determined by a pre-defined rule), and
is implicitly determined by
and
hence
is not reported. Here,
for
where
is a non-negative integer.
In one example,
SD basis vector selection for each TRP
is reported via a joint indicator or separate multiple indicators in
CSI part 2.
· In one example, an indicator to indicate (each)
SD basis vectors has the payload of
bits (bit-width), where
and
are the values of (
) configured via higher-layer (RRC) signaling by the NW. For any TRP
where
(i.e., no SD beam selection case) and/or where TRP
is not selected which can be indicated via
-bit bitmap in
CSI part 1, no SD basis vector for TRP
is reported, hence no payload is induced.
· In one example, a joint indicator to indicate
SD basis vectors has the payload of
bits (bit-width). For any TRP
where
(i.e., no SD beam selection case) and/or where TRP
is not selected which can be indicated via
-bit bitmap in
CSI part 1, no SD basis vector for TRP
is reported, hence no additional payload is induced in the sum.
In one example,
SD basis vectors are selected among all candidates of SD basis vectors across
TRPs and the selection of
SD basis vectors is reported via an indicator with size of
bits in CSI part 1. In this case,
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,
SD basis vectors are selected among all candidates of SD basis vectors across
TRPs and the selection of
SD basis vectors is reported via an indicator with size of
bits in CSI part 2. In this case,
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,
SD basis vectors are selected among all candidates of SD basis vectors across
TRPs, where
is a number of selected TRPs. For example, in CSI part 1,
-bit bitmap is used to indicate selected
TRPs out of
TRPs. For example, when
and
-bit bitmap is '1001' in
CSI part 1, the first TRP and the fourth TRP are selected. The selection of
SD basis vectors is reported via an indicator with size of
bits in CSI part 1. In this case,
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,
SD basis vectors are selected among all candidates of SD basis vectors across
TRPs, where
is a number of selected TRPs. For example, in CSI part 1,
-bit bitmap is used to indicate selected
TRPs out of
TRPs. For example, when
and
-bit bitmap is '1001' in
CSI part 1, the first TRP and the fourth TRP are selected. The selection of
SD basis vectors is reported via an indicator with size of
bits in CSI part 2. In this case,
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,
is determined by UE where
(or
), and the determined
is reported in CSI part 1. Here,
is a number of selected TRPs out of
TRPs and
is a set of selected TRP indexes (i.e., a subset of
). Note that in CSI part 1,
-bit bitmap can be used to indicate selected
TRPs out of
TRPs. In one example, an indicator to indicate
has the size of payload
bits, i.e.,
is selected from
. In another example, an indicator to indicate
has the size of payload
bits, where
is a set including
and positive integers less than or equal to
, and
is a number of the elements in
. In one example,
can be any subset of
. In one example,
can be any subset of
. In one example, an indicator to indicate
has the size of payload
bits, i.e.,
is selected from
.
In one example,
. In one example,
. In one example,
. In one example, In one example,
. In one example,
.
In one example,
. In one example,
can be selected from a subset of
.
In one example,
. In one example,
. In one example,
. In one example, In one example,
. In one example,
.
In one example,
. In one example,
can be selected from a subset of
.
In one example, some of
s 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
s associated with TRPs that are selected are reported implicitly (or determined implicitly hence not explicitly reported). In CSI part 1,
-bit bitmap is used to indicate selected
TRPs out of
TRPs. For example, when
and
-bit bitmap is '1001' in
CSI part 1, the first TRP and the fourth TRP are selected. In this example, some of
associated with the selected TRPs are explicitly reported and the others are implicitly determined.
In one example, a joint indicator can be used to indicate
and
is implicitly determined by
and
and
for
where
is a positive integer and
is a set of selected TRP indexes (i.e., a subset of
and
is the lowest index in
.
In one example, a joint indicator can be used to indicate
and
is implicitly determined by
and
and
for
where
is a positive integer and
is a set of selected TRP indexes (i.e., a subset of
) and
is the highest index in
.
In one example, a joint indicator can be used to indicate
and
is implicitly determined by
and
and
for
where
is a positive integer and
is a set of selected TRP indexes (i.e., a subset of
) and
is a reference TRP index in
, which can be determined by UE or configured by NW or determined by a pre-defined rule
.
In one example, a joint indicator can be used to indicate
and
is implicitly determined by
and
and
for
where
is a positive integer.
In one example, a joint indicator can be used to indicate
and
is implicitly determined by
and
and
for
where
is a positive integer.
In one example, a joint indicator can be used to indicate
and
is implicitly determined by
and
and
for
where
is a positive integer.
In one example, an indicator can be used to indicate each
for
and
is implicitly determined by
and
and
for
where
is a positive integer and
is a set of selected TRP indexes (i.e., a subset of
) and
is the lowest index in
.
In one example, an indicator can be used to indicate each
for
and
is implicitly determined by
and
and
for
where
is a positive integer and
is a set of selected TRP indexes (i.e., a subset of
and
is the highest index in
.
In one example, an indicator can be used to indicate each
for
and
is implicitly determined by
and
and
for
where
is a positive integer and
is a set of selected TRP indexes (i.e., a subset of
) and
is a reference TRP index in
, which can be determined by UE or configured by NW or determined by a pre-defined rule.
In one example, an indicator can be used to indicate each
for
and
is implicitly determined by
and
and
for
where
is a positive integer.
In one example, an indicator can be used to indicate each
for
and
is implicitly determined by
and
and
for
where
is a positive integer.
In one example, an indicator can be used to indicate each
for
and
is implicitly determined by
and
and
for
where
is a positive integer.
In one example,
SD basis vector selection for each TRP
is reported via a joint indicator or separate multiple indicators in
CSI part 2.
In one example, an indicator to indicate (each)
SD basis vectors has the payload of
bits (bit-width), where
and
are the values of (
) configured via higher-layer (RRC) signaling by the NW, where
or
.
In one example, a joint indicator to indicate
SD basis vectors has the payload of
bits or
bits.
In one example, some of
s 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
s associated with TRPs that are selected are reported implicitly (or determined implicitly hence not explicitly reported). The remaining part is similar to other examples described herein.
In one example,
SD basis vectors are selected among all candidates of SD basis vectors across
TRPs. The selection of
SD basis vectors is reported via an indicator with size of
bits in CSI part 1. In this case,
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,
SD basis vectors are selected among all candidates of SD basis vectors across
TRPs. The selection of
SD basis vectors is reported via an indicator with size of
bits in CSI part 2. In this case,
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
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,
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
, where
is inferred from the bitmap".
In one embodiment, any combination or some of certain embodiments described herein can be configured by NW via higher-layer (RRC) signalling. In one example, any combination or some of examples in embodiments described herein can be configured by NW via higher-layer RRC signalling.
In one embodiment, in all embodiments/examples under a certain embodiment described herein,
,
,
can be replaced by
,
,
where
,
(or
), and
(or
).
FIGURE 10 illustrates an example method 1000 performed by a UE in a wireless communication system according to an embodiment of the disclosure. The method 1000 of FIGURE 10 can be performed by any of the UEs 111-116 of FIGURE 1, such as the UE 116 of FIGURE 3, and a corresponding method can be performed by any of the BSs 101-103 of FIGURE 1, such as BS 102 of FIGURE 2. The method 1000 is for illustration only and other embodiments can be used without departing from the scope of the disclosure.
The method 1000 begins with the UE receiving information about a CSI report (1010). For example, in 1010, the information can indicate
CSI-RS resources, a codebook, and codebook parameters. In this example, the codebook includes a SD basis component, a FD basis component, and a coefficient component. The SD basis component includes
basis vectors for each CSI-RS resource
. The FD basis component includes
basis vectors. The coefficient component includes coefficients associated with (SD, FD) basis vector pairs. The codebook parameters include
,
, and
where
p
v is a parameter to determine a value of
based on a total number of precoding matrices
,
v is a number of layers, and
is a parameter to determine an upper bound
of a number of non-zero coefficients of the coefficient component.
In various embodiments, when
,
and
,
, or
. In another embodiment, when
,
and
. In various embodiments, when
,
or
and
,
,
,
, or
. In various embodiments, when
,
and
, or
. In another embodiment, when
,
and
.
The UE then measures the
CSI-RS resources (1020). For example, in 1020, the measurement is based on the information received about the CSI report. The UE then determines the SD basis component, the FD basis component, and the coefficient component (1030). For example, in 1030, the determination may be based on the codebook parameters and information received about the CSI report. In various embodiments, the codebook parameters further include
, where
. In one example, the UE further determines
for
under a constraint of
, and the CSI report further includes an indicator indicating
for
.
The UE then transmits the CSI report (1040). For example, in 1040, the CSI report may include or indicate the determined SD basis component, the FD basis component, and the coefficient component.
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 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 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 disclosure encompasses such changes and modifications as falls within the scope of the appended claims. None of the descriptions 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.