

CSI RS Codebook in a Nutshell
CSI RS Codebook in DetailThis page is about Beamforming of CSI RS. I think this would be the most complicated part in NR protocol (at least to me). It will be helpful if you have the detailed understanding on LTE Beamforming (TM9) before you start reading on this topic. Simply put, this is all about understanding 38.2145.2.2.2 Precoding Matrix Indicator (PMI), but after reading this section several times I came to conclusion that it would be impossible for me to have complete understanding on this section without studying on additional documents outside of this specification (i.e, 38.2145.2.2.2). I am not sure how long it will take for me to reach to the certain level of understanding on this part but let's just start. This page will get updated by small steps for a long period as I learn more and get a little bit deeper understanding step by step.
What is Codebook ?What is Codebook ? It would many different things in different situation, but the meaning of Codebook under the context of CSIRS is a set of Precoders (a set of Precoding Matrix). Putting it other way, Codebook is a kind of matrix (a matrix having complex value elements) that transform the data bit (PDSCH) to another set of data that maps to each antenna port. Two types of Codebook : Type I and Type IIThere are two types of Codebook defined in 5G.
Do we(the reciever) have to know the precoding matrix to decode the received signal ?Shall we(the reciever) know the precoding matrix to decode the received signal ? The answer varies depending on how the data transmission scheme is designed. There are roughly two cases of implementation as shown below. In short, the reciever does not need to know of the precoding matrix information in Case 1 and the reciever should know of the precoding matrix in case 2. (See Chapter 11 of Ref [10]) NR implementation belong to < Case 1 >. Most of LTE transmission Mode (e.g, TM1,2,3,4 etc) belong to < Case 2 >. That is, only data(e.g, PDSCH) is precoded and the reference signal for channel estimation (i.e, Cell Specific Reference Signal) is not precoded. In this case, UE should know of which precoding matrix is applied by eNB. UE knows of this based on predefined specification (as in TM1,2,3) or signaling information delivered by eNB(i.e, PMI index field in DCI). But even in LTE, TM9 belong to < Case 1 > in which PDSCH carries its own demodulation reference signal. In this case, no precoding matrix is applied at the LTE precoding step. In stead, both PDSCH data and PDSCH DMRS would go through a beamforming process. This beamforming process can be regarded as a kind of precoding. Since both PDSCH data and PDSCH DMRS goes through the same beamforming process, UE does not need to know of the precoding matrix that eNB used. Then why we care of the precoder (codebook) in NR. 'We don't need to know' doesn't mean 'it is useless'. Even if it is not mandatory, it will be definitely helpful for the reciever if it knows of the codebook. Looking further into Reference SignalExtending the explanation a little bit further into various possible cases with different type of reference signals, I classified them into following cases. The comments written here is what I had in my mind when I was drawing this diagram and the comments may not be very clear or even misleading if you go into details, but at least it helped me with understanding overal mathematical flow and refernce signal design in this way. In this case, there is one reference signal called CRS. According to this diagram, the CRS is modified by [H] matrix (Channel Matrix). If we assume that CRS is known to reciever in advance (e.g, by specification), the reciever can use this signal to estimate [H] by comparing the received CRS and the expected CRS (the CRS specified in specification). Then the question is 'can the reciever decode User data(d) only with knowledge of [H] ?'. Highly likely NOT because the user data is modified by not only by [H] but also by [W]. Then next question is 'can the reciever estimate (figure out) [W] ? The reciever cannot know [W] directly from the recieved signal. The information about [W] should be known to the reciever by other means like signaling message or physical control information or predefined specification. LTE using Cell specific Reference Signal belong to this case. In this case, there is one reference signal called DMRS. According to this diagram, the DMRS is modified by [W](Precoding matrix) and [H] matrix (Channel Matrix). If we assume that DMRS is known to reciever in advance (e.g, by specification), the reciever may be able to decode user data by correcting the received signal with DMRS. But if you ask 'Can UE estimate [W] and [H] ?'. Highly likely No. Reciever can estimate the product of [H][W] by comparing the received DMRS and the expected DMRS, but it would not be possible to estimate [H] and [W] separately.
In this case, there is two reference signal called DMRS and CSIRS. According to this diagram, the DMRS is modified by both [W](Precoding matrix) & [H] matrix (Channel Matrix) and CSIRS is modified by [H]. The reciever can estimate [H] matrix, but W matrix may not be directly estimated from DMRS since DMRS is modified by both [W] and [H] so [W] information would be given to the reciever by signaling or predefined specification. (Theoretically, if the reciver using both the [H] estimated from CSIRS and DMRS, it may estimate [W]). In theory, in this case the reciever would be able to decode User Data using DMRS only. If CSIRS would be helpful additional information, but it would not be critical. In this case, both DMRS and CSIRS go through the same process. They are both modified by [X](Beam Forming) & [H] matrix (Channel Matrix). This is the case where PDSCH / DMRS is not precoded.
In this case, there is two reference signal called DMRS and CSIRS. According to this diagram, the DMRS is modified by [W](Precoding matrix), [X](Beam Forming) & [H] matrix (Channel Matrix) and CSIRS is modified by [X] and [H]. The reciever can estimate [H][X] matrix but [X] and [H] cannot be estimated individually. From DMRS, the reciever can estimate [H][X][W] but they cannot be separated individually. In conclusion, in this case none of the matrix can be estimated individually, but in theory the reciever should be able to decode User Data with DMRS only since the DMRS can undo the effect of all combined matrix [H][X][W]. How can UE or gNB knows about the precoder information ?In UE's perspective, a typical way is to send measurement report for PMI to gNB and may assume that gNB would use the PMI(Precoding Matrix Indicator) that it reports... but the important thing to remember is ... it is not mandatory for gNB to use the PMI that UE report. It may or may not use the same PMI depending on its own situation. Even if gNB use different PMI than what UE report, UE can decode the downlink data because the downlink data(PDSCH) carries its own reference signal from the beginning as explained in < Case 2 > in previous section. UE can estimate the channel using the DMRS and in many cases this type of channel estimation would be good enough to decode PDSCH. In gNB's perspective, a typical way is to tell UE to send SRS and pick a specific PMI based the channel estimation of SRS, and tell UE via DCI 0_1 (TMPI field) to use a specific PMI. In this case, UE shall use the specific precoding matrix specified by gNB. If we can assume that UE and gNB is in such a condition where channel reciprocity is guaranteed (like well calibrated TDD channel), gNB can use the channel information from SRS for estimating downlink channel quality and selecting downlink beam. Where to start ?  Understanding basic terminologies.The first problem that I got when I start reading the section 38.2145.2.2.2 was to figure out the meaning of strange looking single character parameters like N1,N2,O1,O2 which is not clearly defined in the TS(Technical Specification) and some other terminology like 'Panel' (as in single panel, multi panel as shown in the RRC message). When some terminolgy is not clearly defined in TS document, it is highly likely that they are described in some TDocs (R1XXXXX) and transferred to TS document without clear explanation. So I started search TDocs about this topic and I found a TDoc Ref [1],[5],[6],[7],[8] which seems to be the origin of this topic and some other documents as in Ref [2] and Ref [3] that would help us to understand other terminology like 'Panel'. NOTE : Basically, most of the fundamental concept of NR CSI Codebook design is inherited from LTE Rel 13 FDMIMO codebook design. You would find a lot of detailed description and diagrams in LTE TDocs. Check in the link in Ref [14] , Ref[15] and take a look into the documents on CSI Coddebook. I found a little bit clearer illustration from SamSung Whitepaper shown below, which can associate each of the beam matrix to the angles of vertical and horizontal beam. Source : Massive MIMO for New Radio (SamSung White Paper) How can we implement these beams in reality ? The physical implementation would vary. One example of implementation can be illustrated as below. Source : Massive MIMO for New Radio (SamSung White Paper) N1, N2, O1, O2 are defined in 3GPP as shown below. I've added some additional column to the table since these additional columns are used often in other parts. <Type 1 Single Panel : Based on 38.214 v15.3Table 5.2.2.2.12: Supported configurations of (N1,N2) and (O1,O2)>
<Type 1 Multi Panel : Based on 38.214 v15.3Table 5.2.2.2.21: Supported configurations of (Ng,N1,N2) and (O1,O2)>
Using this definition, we can visualize the antenna array for each codebook as follows. As you see here, you would notice that there are multiple options of array structure for the same number of CSIRS antenna ports. Why they propose multiple options ? that is, what is the difference between different options. For example, what would be the difference between 4x1 array and 2x2 array with 8 CSI port ? The main difference caused by this different structure is the shape of the beam in 3D space. For more intuitive understanding, I put another type of my notes in www.slide4math.com. Check out [Array Antenna]
<Type 1 Multi Panel>
Linking TDocs to TSAs mentioned above, it is very diffuclt to understand the specification about CSIRS codebook just by reading 3GPP TS specification. So in my case I often look into various TDocs and sometimes textbooks about 5G Physical layer. However, in many case it is hard to find direct connection between what TDoc/Textbook says and what 3GPP TS says. In this section, I would put some tips and hints on how to correlate what you usually see from TDoc/Textbook with what 3GPP TS specifies. The first thing I want to show you is the link shown below. In most TDocs and Textbook, they describe CSI Codebook as W = W1 * W2 (the combination of two matrices) but 3GPP TS does not explicitely describes it in the same way. 3GPP TS just list a whole bunch of tables. The connection between the Codebook in TDoc and 3GPP TS can be illustrated as follows. Focusing further into the codebook matrix format, 3GPP TS defines various different form of W matrix depending on the number of layers and some other parameters as shown below. As you may notice from what is mentioned above, there are several parameters labeled as 'i something' like i1_1, i1_2, i_2. According to what I mentioned above, you would figure out that i1_x (i.e, i1_1,i1_2 etc) determines wideband properties and i2 determines subband properies. This relationship specified in 382145.2.2.2 as below (In my note, i1_3 is not explicitely described. I would mention on this when I have chance to explain on each specific CSI codebook table in the future. For now, just let you know that i1_3 is an additional parameter that are required to determine the codebook for multi layer). The construction process of W1 matrix is illustrated as below. As you see, this matrix is associated with antenna structure. Each colum of this matrix represents the weight vector for each specific beam formed by the antenna array. (NOTE : In some documents, the vector X1 ⊗ X2 is described as B, where ⊗ indicate Kronecker Product). W2 is in the form of vector that functions to select specific beams (columns) of W1. Even though most of TDocs and Textbook explain about Precoding Matrix using two matrix W1 and W2 , you may not recognize clearly separated matrix in the W matrix given in 3GPP PMI tables. So I would like to give you overall structure of the W matrix given in 3GPP PMI tables. You would see roughly two types of W Matrix structure as below depending on the PMI table you pick.
With this general structure in mind, pick a very simple PMI table that you think you can handle and derive the matrix with pen and pencil as I did in Derivation of W matrix Example. There might be some mistakes that I made in this derivation, but at least it helped me to build much clearer picture on the structure and meaning of the matrix. Wideband and Subband Report ConfigurationAs explained in previous section, CSI report in NR is made up of two categories(granularities). One is for Wideband property (Wideband Granularity) and the other one is subband property(subband granularity). These two parameters can be set separately and reported in independent scheduling, which gives more efficiency and flexibility for CSI framework (it may make it difficult for us to understand the mechanism though). According to 38.214  5.2.1.4, Wideband and Subband Report properties can be configured by ReportQuantity in RRC message as follows :
A CSI Reporting Setting is said to have a wideband frequencygranularity if otherwise, the CSI Reporting Setting is said to have a subband frequencygranularity. PMI TablesFollowings are summaries on correlations on Type, number of layers, number of CSI antenna ports & dimension and specific mapping table. But it would not be easy to make sense out of this summary table. To understand each of these tables in detail, I would suggest you go through TDocs in reference section (or at least high level descriptions in this note) to get some big picture first and then you need to construct a few specific PMI matrix by hands as I did in example sections.
< Table 5.2.2.2.11: Codebooks for 1layer and 2layer CSI reporting using antenna ports 3000 to 3001 >
< Table 5.2.2.2.15: Codebook for 1layer CSI reporting using antenna ports 3000 to 2999+P_CSIRS >
< Table 5.2.2.2.16: Codebook for 2layer CSI reporting using antenna ports 3000 to 2999+P_CSIRS >
[ Table 5.2.2.2.13: Mapping of i1,3 to k1 and k2 for 2layer CSI reporting ]
[ Table 5.2.2.2.13: Mapping of i1,3 to k1 and k2 for 2layer CSI reporting ]
[ Table 5.2.2.2.13: Mapping of i1,3 to k1 and k2 for 2layer CSI reporting ]
< Table 5.2.2.2.17: Codebook for 3layer CSI reporting using antenna ports 3000 to 2999+P_CSIRS >
< Table 5.2.2.2.14: Mapping of i1,3 to k1 and k2 for 3layer and 4layer CSI reporting when P_CSIRS < 16 >
< Table 5.2.2.2.18: Codebook for 4layer CSI reporting using antenna ports 3000 to 2999+P_CSIRS >
< Table 5.2.2.2.14: Mapping of i1,3 to k1 and k2 for 3layer and 4layer CSI reporting when P_CSIRS < 16 > Derivation of W1 and W2As briefly mentioned above, W matrix is originally designed to represent the product of two matrix, W1 and W2 (For the original design, refer to Ref [1] and Ref[13]). But it was difficult for me to grasp the practical idea on the concept of the design and had no idea what each of the matrix represents when I first read about an year ago, and then was able to get a little bit of idea when I found a blog (Ref [11]), but not the full picture yet and almost completely forgot about this concept for several month until one of the note reader Daniel(HyungJong) Noh brough up this issue. I still haven't got clear picture about this and Daniel managed to figure out how W1 and W2 can derived quicker quicker than I did and he shared an example showing the derivation of the two matrix and kindly allowed me to share it with readers. Before going into the example shared by HyungJong, let me give you some additional note to help you (myself as well) to follow through the thought process. First, I assume that everybody now knows W is defined as follows. Based on Ref [1],[11],[13] and 34.214, we can expand this equation as follows. I think W1 would make sense for you now, but the meaning of W2 would still be in mystery from this definition. You will see more concrete form of W2 in the example from HyungJong below. (NOTE : ⊗ indicate Kronecker Product).
Now let's follow through the example from HyungJong. In this example, we assume the following case (Same as in W matrix calculation Example 01, but i1,1, i1,2, i2 are not spefified (i.e, remain as generic variable) No of CSI ports = 4 N1 = 2, N2 = 1, O1 = 4, O2 = 1 Let's start with Calculating B. B can be calculated as follows based on the definition that is explained in Linking TDoc to TS section. Based on this, you can construct W1 matrix as follows. From the condition given to this example, you can define W2 matrix as follows. You may refer to Ref [11] and the seciton 6.12.4.2.1 of Ref[32] for further details on W2 definition. With the W1 and W2, you can calculate W matrix as follows. If you modify this W matrix in a little bit different way based on the definition shown at the beginning of this section, you can rewrite this result as follows and you may realize it is the same form described in the table in 38.214 and can understand how the formular in the table is designed. Derivation of W matrix ExamplesIn this section, the final matrix you will derive will be in the form of complex number elements. The user data (i.e, PDSCH data) is also in the form of complex number (I and Q data). Eventually you should be able to visualize the properties of these matrix in your brain to make sense out of those matrix. Here goes another type of my notes that may help you with the intuitive understandings on the matrix with complex number elements being applied to complex data. Play with [Matrix Complex] Example 01 > p4, 1 Layer , N1 = 2, N2 = 1, O1 = 4, O2 = 1, i1,1 = 0 i1,2 = 0 i2 = 0Let's assume that PMI table is configured according to following table(Table 5.2.2.2.15). Suppose we have following report and antenna configuration as follows : No of CSI ports = 4 N1 = 2, N2 = 1, O1 = 4, O2 = 1 i1,1 = 0 i1,2 = 0 i2 = 0. This indicates l = i1,1 = 0, m = i1,2 = 0 , n = i2 = 0 Now, let's plug these parameters into all the equations that lead to final matrix. I hope I did all the steps right. Let me know if you find anything wrong. First, figure out um vector. In this example, N2 is 1. So um becomes as follows. Next, figure out vl,m vector. In this example, l = 0, m = 0. so vl,m become as follows : Transposing the vector, we get following vector Now calculaing Phi value using the parameter n. Plugging into n value given in this example, we get the value as follows. Now plugging into the matrix all the vectors we got above Plugging l,m,n value given in this example, we get following vector Do all the calculation to the end, we get the final matrix(vector) as follows. Example 02 p4, 1 Layer , N1 = 2, N2 = 1, O1 = 4, O2 = 1, i1,1 = 1 i1,2 = 0 i2 = 1Let's assume that PMI table is configured according to following table (Table 5.2.2.2.15). Suppose we have following report and antenna configuration as follows : No of CSI ports = 4 N1 = 2, N2 = 1, O1 = 4, O2 = 1 i1,1 = 1 i1,2 = 0 i2 = 1. This indicates l = i1,1 = 1, m = i1,2 = 0 , n = i2 = 1 Now, let's plug these parameters into all the equations that lead to final matrix. I hope I did all the steps right. Let me know if you find anything wrong. First, figure out um vector. In this example, N2 is 1. So um becomes as follows. Next, figure out vl,m vector. In this example, l = 0, m = 0. so vl,m become as follows : Transposing the vector, we get following vector Now calculaing Phi value using the parameter n. Plugging into n value given in this example, we get the value as follows. Now plugging into the matrix all the vectors we got above Plugging l,m,n value given in this example, we get following vector Do all the calculation to the end, we get the final matrix(vector) as follows. Example 03> p4, 2 Layer , N1 = 2, N2 = 1, O1 = 4, O2 = 1, i1,1 = 0 i1,2 = 0 i2= 0, i1,3 = 0Let's assume that PMI table is configured according to following table ( Table 5.2.2.2.16 ).
Suppose we have following report and antenna configuration as follows : No of CSI ports = 4 N1 = 2, N2 = 1, O1 = 4, O2 = 1 i1,1 = 0, i1,2 = 0, i1,3 = 0, i2= 0. This indicates k1 = 0, k2 = 0 l = i1,1 = 0, l= i1,1+k1=0, m = i1,2 = 0, m = i1,2+k2 = 0, n = i2 = 0 Let's figure out um vector first. Since N2 = 1 in the given condition in this example, um become 1 Now let's derive vl,m vector Since both l and m is 0 in this example, the vector become as follows. Transposing the vector and simplifing it, we get Calculating Phi with n given in this example, we get the phi value as follows. In the same as we did for vl,m, we can calculate vl',m' from following equation. Plugging the number for l' and m', we get following Transposing and Simplifying, we get Now let's plug into the final matrix all the vectors and values that we derived above. Rewriting the matrix by plugging in parameters (l,l',m,m',n), it looks as follows. Then, plugging the vectors and values derived above into the matrix, we get the final result as follows. Example 04> p4, 2 Layer , N1 = 2, N2 = 1, O1 = 4, O2 = 1, i1,1 = 0 i1,2 = 0 i2= 1, i1,3 = 1Let's assume that PMI table is configured according to following table.
Suppose we have following report and antenna configuration as follows : No of CSI ports = 4 N1 = 2, N2 = 1, O1 = 4, O2 = 1 i1,1 = 1, i1,2 = 0, i1,3 = 1, i2= 1. This indicates k1 = O1=4, k2 =0 [Note : Since this is the case where N1 > N2 > 1, k1 becomes O1 and k2 becomes 0 when i1,3 = 1] l = i1,1 = 1, l= i1,1+k1=1+4=5, m = i1,2 = 0, m = i1,2+k2 = 0+0 = 0, n = i2 = 1 Let's figure out um vector first. Since N2 = 1 in the given condition in this example, um become 1 Now let's derive vl,m vector Since both l is 1 and m is 0 in this example, the vector become as follows. Transposing the vector and simplifing it, we get Calculating Phi with n given in this example, we get the phi value as follows. Now let's derive vl',m' from the following vector. Plugging l' and m' into the equation, we get a vector as follows. Trransposing and Symplifying the vector, we get Now let's derive the final matrix from following equation. Plugging the vectors and parameters we got in previous step , we get following Plugging the number and simplifying, we get the final result as follows : Example 05> p16, 1 Layer , N1 = 8, N2 = 1, O1 = 4, O2 = 1Let's assume that we want to figure out the codebook for following configuration. (NOTE : I put the graphical representation of all the possible codebooks in this example in my visual note in 4 pages : here, here, here, here. Check if you can correlate the mathmatical representation shown here and the graphical representation).
Assuming that codebookmode = 2, the codebook table we have to apply is following (Table 5.2.2.2.15 ) Let's figure out um vector first. Since N2 = 1 in the given condition in this example, um become 1 Now let's derive vl,m vector Since N1 is 8 in this example, we would get a huge vector as shown below. (In this example, I haven't specified any specific i_x value. I will leave it as a variable) Plugging this reslut into the codebook matrix format of Table 5.2.2.2.15 and map the result to the logical antenna configuration, it can be illustrated as follow. Example 06> p8, 4 Layer , N1 = 4, N2 = 1, O1 = 4, O2 = 1Let's assume that we want to figure out the codebook for following configuration
Assuming that codebookmode = 2, the codebook table we have to apply is following (Table 5.2.2.2.17 ) You would notice that there are other variable k1, k2 is required to derive this codebook matrix. Those k1, k2 values are defined in the following table(Table 5.2.2.2.14). Let's figure out um vector first. Since N2 = 1 in the given condition in this example, um become 1 Now let's derive vl,m vector Since N1 is 4 in this example, we would get a vector as shown below. (In this example, I haven't specified any specific i_x value. I will leave it as a variable) Plugging this reslut into the codebook matrix format of Table 5.2.2.2.17 and map the result to the logical antenna configuration, it can be illustrated as follow. Base Formula for Type II CodebookCodebook Type II is not using any predefined PMI matrix. In stead, it is generating a beam forming equation based on various information in UE measurement report. To do this, there should a formula (a mathematical template) known both on UE and Network. The detailed equation described in 38.214 may look too complicated to many people including me. I was trying to find a little bit simplified form of the formula for me to get the basic concept more easily/clearly and following is one of the equation that I found in Ref[34] Amplitude Quantization for Type2 Codebook Based CSI Feedback in New Radio System. This paper is about codebook type II, not the Enhanced Codebook Type II but I think the basic concept is same. The overall form of beam forming matrix is as follows. W matrix is made up of Wr,l where r indicates polarization and l indicates layers. The final structure of the matrix is similar to what is shown in Linking TDoc to TS section. The difference lies in how each of the matrix elements is calculated. Now let's take a look at how each of the matrix elements look like. As shown below, the codebook type II is made up of multiple codebook type I formula and amplitude scaler which are linearly combined. Each components of the equation can be further described as below. Type II Codebook< 38.214Table 5.2.2.2.35: Codebook for 1layer and 2layer CSI reporting using antenna ports 3000 to 2999+P_CSIRS > The overall structure of the W matrix is as follows. 'v' term is the one generate the base form of beam forming matrix and the logic of this term is basically as in codebook type I. Refer to Derivation of W matrix Examples section for the details. 'p' term is amplitude scaling factors and 'Phi' term is Phase combining coefficient between polarization 0 and polarization 1. Now let's take a look into the details of each parameters used in the formula. Now the question is how each of the parameter in the formula is determined. Those parameters are determined by the CSI measurement report from UE as summarized below.
< 38.212Table 6.3.2.1.21: PMI of codebookType= typeII > Type II Port Selection Codebook< 38.214Table 5.2.2.2.41: Codebook for 1layer and 2layer CSI reporting using antenna ports 3000 to 2999+P_CSIRS >
< 38.212Table 6.3.2.1.22: PMI of codebookType= typeIIPortSelection > Enhanced Type II Codebook<38.214Table 5.2.2.2.55: Codebook for 1layer. 2layer, 3layer and 4layer CSI reporting using antenna ports 3000 to 2999+PCSIRS>
< 38.214Table 5.2.2.2.51 > For enhanced codebood type II, UE should report a huge set of information as summarized as below.
< 38.212Table 6.3.2.1.21A: PMI of codebookType= typeIIr16 > Putting All these togetherAs I mentioned, it is very challenging to understand the detailed mechanism of CSRRS in terms of each separate component (like CSIRS signal generation, Codebook Configuration, related RRC parameters), but still some overall flow that put all these together has been mystery to me for a long time. Just recently with a lot of TDoc reading and a critical help from one of the active readers of my notes, I think I reached much closer to the understandings on the overall process. Followings short notes for each process. Does UE knows all these detailed mapping information ?In short, UE knows the details of (A) > (B) > (C) via DCI and RRC configuration, but it doesn't know anything about (D). But this technology is designed in such a way that UE does not need to know about (D). We say this as '(C) > (D) mapping is transparent to UE'. How to interpret RRC parameters and i values ?This section describes about RRC parameters for the codebook only but the codebook parameter is associated with CSI RS parameters. For the details of CSIRS parameters, refer to CSIRS page. I will also discuss about UE measurement parameters related to the codebook based CSI report in this section. < Type ISingle Panel >For a while, we may stay with type ISinglePanel. So for now, I would describe only on the codebook setting in RRC for type I Single pannel case. type1 SEQUENCE { subType CHOICE { typeISinglePanel SEQUENCE { nrOfAntennaPorts CHOICE { two SEQUENCE { twoTXCodebookSubsetRestriction BIT STRING (SIZE (6)) }, moreThanTwo SEQUENCE { n1n2 CHOICE { twooneTypeISinglePanelRestriction BIT STRING (SIZE (8)), twotwoTypeISinglePanelRestriction BIT STRING (SIZE (64)), fouroneTypeISinglePanelRestriction BIT STRING (SIZE (16)), threetwoTypeISinglePanelRestriction BIT STRING (SIZE (96)), sixoneTypeISinglePanelRestriction BIT STRING (SIZE (24)), fourtwoTypeISinglePanelRestriction BIT STRING (SIZE (128)), eightoneTypeISinglePanelRestriction BIT STRING (SIZE (32)), fourthreeTypeISinglePanelRestriction BIT STRING (SIZE (192)), sixtwoTypeISinglePanelRestriction BIT STRING (SIZE (192)), twelveoneTypeISinglePanelRestriction BIT STRING (SIZE (48)), fourfourTypeISinglePanelRestriction BIT STRING (SIZE (256)), eighttwoTypeISinglePanelRestriction BIT STRING (SIZE (256)), sixteenoneTypeISinglePanelRestriction BIT STRING (SIZE (64)) }, typeISinglePanelcodebookSubsetRestrictioni2 BIT STRING (SIZE (16)) } }, typeISinglePanelriRestriction BIT STRING (SIZE (8)) }, Even though this is RRC message, you would not get much detailed information from 38.331 (RRC Specification). You should see 38.214 in order to find the detailed information on this part. For typeISinglePanel case, refer to 38.2145.2.2.2.1. Followings are some important statement.
< Type II >type2 SEQUENCE { subType CHOICE { typeII SEQUENCE { n1n2codebookSubsetRestriction CHOICE { twoone BIT STRING (SIZE (16)), twotwo BIT STRING (SIZE (43)), fourone BIT STRING (SIZE (32)), threetwo BIT STRING (SIZE (59)), sixone BIT STRING (SIZE (48)), fourtwo BIT STRING (SIZE (75)), eightone BIT STRING (SIZE (64)), fourthree BIT STRING (SIZE (107)), sixtwo BIT STRING (SIZE (107)), twelveone BIT STRING (SIZE (96)), fourfour BIT STRING (SIZE (139)), eighttwo BIT STRING (SIZE (139)), sixteenone BIT STRING (SIZE (128)) }, typeIIRIRestriction BIT STRING (SIZE (2)) }, typeIIPortSelection SEQUENCE { portSelectionSamplingSize ENUMERATED {n1, n2, n3, n4} OPTIONAL, typeIIPortSelectionRIRestriction BIT STRING (SIZE (2)) } }, phaseAlphabetSize ENUMERATED {n4, n8}, subbandAmplitude BOOLEAN, numberOfBeams ENUMERATED {two, three, four} }
As per 38.2145.2.2.2.3, Followings are some important statement.
< Enhanced Type II >CodebookConfigr16 ::= SEQUENCE { codebookType CHOICE { type2 SEQUENCE { subType CHOICE { typeIIr16 SEQUENCE { n1n2codebookSubsetRestrictionr16 CHOICE { twoone BIT STRING (SIZE (16)), twotwo BIT STRING (SIZE (43)), fourone BIT STRING (SIZE (32)), threetwo BIT STRING (SIZE (59)), sixone BIT STRING (SIZE (48)), fourtwo BIT STRING (SIZE (75)), eightone BIT STRING (SIZE (64)), fourthree BIT STRING (SIZE (107)), sixtwo BIT STRING (SIZE (107)), twelveone BIT STRING (SIZE (96)), fourfour BIT STRING (SIZE (139)), eighttwo BIT STRING (SIZE (139)), sixteenone BIT STRING (SIZE (128)) }, typeIIRIRestrictionr16 BIT STRING (SIZE(4)) }, typeIIPortSelectionr16 SEQUENCE { portSelectionSamplingSizer16 ENUMERATED {n1, n2, n3, n4}, typeIIPortSelectionRIRestrictionr16 BIT STRING (SIZE (4)) } }, numberOfPMISubbandsPerCQISubbandr16 INTEGER (1..2), paramCombinationr16 INTEGER (1..8) } } }
As per 38.2145.2.2.2.3, Followings are some important statement.
< 38.214  Table 5.2.2.2.51: Codebook parameter configurations for L, β and pv > The UE is not expected to be configured with paramCombinationr16 equal to 3,4,5,6,7 or 8 when Pcsirs = 4 7 or 8 when Pcsirs < 32 7 or 8 when higher layer parameter typeIIRIRestrictionr16 is configured with ri=1 for any i > 1 7 or 8 when R = 2 The parameter R is configured with the higherlayer parameter numberOfPMISubbandsPerCQISubband. This parameter controls the total number of precoding matrices N3 indicated by the PMI as a function of the number of configured subbands in csiReportingBand RRC Parameters for CSI RSPortIndexFor8Ranks ::= CHOICE { portIndex8 SEQUENCE{ rank18 PortIndex8 OPTIONAL,  Need R rank28 SEQUENCE(SIZE(2)) OF PortIndex8 OPTIONAL,  Need R rank38 SEQUENCE(SIZE(3)) OF PortIndex8 OPTIONAL,  Need R rank48 SEQUENCE(SIZE(4)) OF PortIndex8 OPTIONAL,  Need R rank58 SEQUENCE(SIZE(5)) OF PortIndex8 OPTIONAL,  Need R rank68 SEQUENCE(SIZE(6)) OF PortIndex8 OPTIONAL,  Need R rank78 SEQUENCE(SIZE(7)) OF PortIndex8 OPTIONAL,  Need R rank88 SEQUENCE(SIZE(8)) OF PortIndex8 OPTIONAL  Need R }, portIndex4 SEQUENCE{ rank14 PortIndex4 OPTIONAL,  Need R rank24 SEQUENCE(SIZE(2)) OF PortIndex4 OPTIONAL,  Need R rank34 SEQUENCE(SIZE(3)) OF PortIndex4 OPTIONAL,  Need R rank44 SEQUENCE(SIZE(4)) OF PortIndex4 OPTIONAL  Need R }, portIndex2 SEQUENCE{ rank12 PortIndex2 OPTIONAL,  Need R rank22 SEQUENCE(SIZE(2)) OF PortIndex2 OPTIONAL  Need R }, portIndex1 NULL }
CodebookConfig ::= SEQUENCE { codebookType CHOICE { type1 SEQUENCE { subType CHOICE { typeISinglePanel SEQUENCE { nrOfAntennaPorts CHOICE { two SEQUENCE { twoTXCodebookSubsetRestriction BIT STRING (SIZE (6)) }, moreThanTwo SEQUENCE { twooneTypeISinglePanelRestriction BIT STRING (SIZE (8)), twotwoTypeISinglePanelRestriction BIT STRING (SIZE (64)), fouroneTypeISinglePanelRestriction BIT STRING (SIZE (16)), threetwoTypeISinglePanelRestriction BIT STRING (SIZE (96)), sixoneTypeISinglePanelRestriction BIT STRING (SIZE (24)), fourtwoTypeISinglePanelRestriction BIT STRING (SIZE (128)), eightoneTypeISinglePanelRestriction BIT STRING (SIZE (32)), fourthreeTypeISinglePanelRestriction BIT STRING (SIZE (192)), sixtwoTypeISinglePanelRestriction BIT STRING (SIZE (192)), twelveoneTypeISinglePanelRestriction BIT STRING (SIZE (48)), fourfourTypeISinglePanelRestriction BIT STRING (SIZE (256)), eighttwoTypeISinglePanelRestriction BIT STRING (SIZE (256)), sixteenoneTypeISinglePanelRestriction BIT STRING (SIZE (64)) }, typeISinglePanelcodebookSubsetRestrictioni2 BIT STRING (SIZE (16)) } }, typeISinglePanelriRestriction BIT STRING (SIZE (8)) }, typeIMultiPanel SEQUENCE { twotwooneTypeIMultiPanelRestriction BIT STRING (SIZE (8)), twofouroneTypeIMultiPanelRestriction BIT STRING (SIZE (16)), fourtwooneTypeIMultiPanelRestriction BIT STRING (SIZE (8)), twotwotwoTypeIMultiPanelRestriction BIT STRING (SIZE (64)), twoeightoneTypeIMultiPanelRestriction BIT STRING (SIZE (32)), fourfouroneTypeIMultiPanelRestriction BIT STRING (SIZE (16)), twofourtwoTypeIMultiPanelRestriction BIT STRING (SIZE (128)), fourtwotwoTypeIMultiPanelRestriction BIT STRING (SIZE (64)) }, riRestriction BIT STRING (SIZE (4)) } }, codebookMode INTEGER (1..2) }, type2 SEQUENCE { subType CHOICE { typeII SEQUENCE { n1n2codebookSubsetRestriction CHOICE { twoone BIT STRING (SIZE (16)), twotwo BIT STRING (SIZE (43)), fourone BIT STRING (SIZE (32)), threetwo BIT STRING (SIZE (59)), sixone BIT STRING (SIZE (48)), fourtwo BIT STRING (SIZE (75)), eightone BIT STRING (SIZE (64)), fourthree BIT STRING (SIZE (107)), sixtwo BIT STRING (SIZE (107)), twelveone BIT STRING (SIZE (96)), fourfour BIT STRING (SIZE (139)), eighttwo BIT STRING (SIZE (139)), sixteenone BIT STRING (SIZE (128)) }, typeIIRIRestriction BIT STRING (SIZE (2)) }, typeIIPortSelection SEQUENCE { portSelectionSamplingSize ENUMERATED {n1, n2, n3, n4} OPTIONAL, typeIIPortSelectionRIRestriction BIT STRING (SIZE (2)) } }, phaseAlphabetSize ENUMERATED {n4, n8}, subbandAmplitude BOOLEAN, numberOfBeams ENUMERATED {two, three, four} } } }
CodebookConfigr16 ::= SEQUENCE { codebookType CHOICE { type2 SEQUENCE { subType CHOICE { typeIIr16 SEQUENCE { n1n2codebookSubsetRestrictionr16 CHOICE { twoone BIT STRING (SIZE (16)), twotwo BIT STRING (SIZE (43)), fourone BIT STRING (SIZE (32)), threetwo BIT STRING (SIZE (59)), sixone BIT STRING (SIZE (48)), fourtwo BIT STRING (SIZE (75)), eightone BIT STRING (SIZE (64)), fourthree BIT STRING (SIZE (107)), sixtwo BIT STRING (SIZE (107)), twelveone BIT STRING (SIZE (96)), fourfour BIT STRING (SIZE (139)), eighttwo BIT STRING (SIZE (139)), sixteenone BIT STRING (SIZE (128)) }, typeIIRIRestrictionr16 BIT STRING (SIZE(4)) }, typeIIPortSelectionr16 SEQUENCE { portSelectionSamplingSizer16 ENUMERATED {n1, n2, n3, n4}, typeIIPortSelectionRIRestrictionr16 BIT STRING (SIZE (4)) } }, numberOfPMISubbandsPerCQISubbandr16 INTEGER (1..2), paramCombinationr16 INTEGER (1..8) } } }
Reference[1] 3GPP TSGRAN WG1 #87 R11612661 : Advanced CSI Codebook Structure [3] 5G New Radio (NR) : Physical Layer Overview and Performance : IEEE Communication Theory Workshop  2018 [4] A Tutorial on Beam Management for 3GPP NR at mmWave Frequencies [5] 3GPP TSGRAN WG1 #86 R1166579 : Discussion on codebook design to support up to 32 ports CSI RS [6] 3GPP TSGRAN WG1 #86 R1167140 : Codebook for up to 32 ports CSIRS [7] 3GPP TSGRAN WG1 #86 R1166342 : Codebook Design for Class A CSI Reporting up to 32 Ports [8] 3GPP TSGRAN WG1 #86 R1166445 : Codebook design for {20, 24, 28, 32} ports [9] Advanced antenna systems for 5G networks [10] 5G NR (THE NEXT GENERATION WIRELESS ACCESS TECHNOLOGY)  Erik Dahlman, Stefan Parkvall, Johan Skold [11] Analyze 5G NR Type I SP Codebook [12] 3GPP TSGRAN WG1 #90 R1171nnnn [DRAFT] Summary on views on CSI reporting for Type I and Type II [13] 3GPP TSG RAN WG1 Meeting #82b R1155490 Rank 12 codebook for Class A CSI reporting [14] RAN1#82BIS (20151005  Malmo(SE)) : TDocs [15] 3GPP TDocs (written contributions) at meeting : R185  20160523 to 20160527, Nanjing [16] 3GPP TSG RAN WG1 Meeting #85 : R1164776 View on class A codebook extension [17] 3GPP TSG RAN WG1 Meeting #85 : R1164777 Hybrid PMI codebook based CSI reporting and simulation results [18] 3GPP TSG RAN WG1 Meeting #85 : R1164780 Linear combination (LC) codebook based CSI reporting and simulation results [19] 3GPP TSG RAN WG1 Meeting #85 : R1164857 Discussion on codebook design to support up to 32 ports CSIRS [20] 3GPP TSGRAN WG1#85 : R1165097 Class A Codebook Design for up to 32 Ports in Rel14 [21] 3GPP TDocs (written contributions) at meeting : R183  20151115 to 20151122, Anaheim [22] 3GPP TSG RAN WG1 Meeting #83 : R1156790 Rank 2 codebook  summary of RAN1 proposals and performance [23] 3GPP TSG RAN WG1 Meeting #83 : R1156791 Rank 38 codebook  summary of RAN1 proposals and performance [24] 3GPP TSG RAN WG1 Meeting #83 : R1156831 Codebook design for Class B [25] 3GPP TSG RAN WG1 Meeting #83 : R1157003 16 port codebook design and evaluations [26] 3GPP TSG RAN WG1 Meeting #83 : R1157164 Codebook design for elevation BF and FDMIMO [27] 3GPP TSGRAN WG1#83 : R1157208 Class A Codebook Design for Rank 12 [28] 3GPP TSGRAN WG1#83 : R1157209 Class A Codebook Design for Rank 38 [29] 3GPP TSG RAN WG1 Meeting #83 : R1157300 Codebook Design for rank 2 for 2D antenna arrays [30] 3GPP TSG RAN WG1 Meeting #83 : R1157301 Codebook Design for rank 3 to 8 for 2D antenna arrays [31] 3GPP TSG RAN WG1 Meeting #83 : R1157427 Samsung, Ericsson, NTT DOCOMO, CATT [32] 5G Technology 3GPP New Radio Edited by Harri Holma, Antti Toskala, Takehiro Nakamura [33] Codebook Based MultiUser MIMO for 5G  Lund University [34] Amplitude Quantization for Type2 Codebook Based CSI Feedback in New Radio System [35] 3GPP TSGRAN WG1 #89 : R11709232 WF on Type I and II CSI codebooks [36] Massive MIMO for New Radio (SamSung Technical White Paper) [37] Beamforming  How does it work (Ericsson) [38] 3GPP Workshop : 3GPP 5G Technology and Self Evaluation Results (Wu Yong) [39] Overhead Reduction of NR type II CSI for NR Release 16 (Nokia) [40] Massive MIMO for New Radio (SamSung White Paper) [41] 5G NR in BULLETS  13.6.3 PRECODING MATRIX INDICATOR

