Systems and methods for group-based beam scaling restriction for large antenna arrays

Abstract

Systems and methods for group-based beam scaling restriction for large antenna arrays are provided. In some embodiments, a method performed by a User Equipment (UE) includes: receiving a configuration from a network node that provides information; determining mapping between bits in a bitmap and a Spatial Domain (SD) basis vector groups wherein Z ≥ 1 bits in the bitmap map to a single SD basis vector group; determining a Precoding Matrix Indicator (PMI) according to the mapping; and reporting PMI to the network node as part of Channel State Information (CSI) reporting to the network node. In this way, the UE determines the correct mapping between Codebook Subset Restriction (CBSR) bitmap and SD basis vectors in SD basis vector groups when group-based CBSR signaling is used. The UE also determines the correct mapping between scaling factor bitmap and SD basis vectors in SD basis vector groups when group-based CBSR signaling is used.

Description

SYSTEMS AND METHODS FOR GROUP-BASED BEAM SCALING RESTRICTION FOR LARGE ANTENNA ARRAYS RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 681,558, filed August 9, 2024, the disclosure of which is hereby incorporated herein by reference in its entirety. TECHNICAL FIELD

[0002] The current disclosure relates generally to beam scaling. BACKGROUND

[0003] Codebook-based precoding

[0004] Multi-antenna techniques can significantly increase the data rates and reliability of a wireless communication system. The performance is in particular improved if both the transmitter and the receiver are equipped with multiple antennas, which results in a Multiple-Input Multiple- Output (MIMO) communication channel. Such systems and / or related techniques are commonly referred to as MIMO.

[0005] A core component of the fourth and fifth Generation (4G / 5G) wireless network or New Radio (NR) specified in 3GPP is the support of MIMO antenna deployments and MIMO related techniques such as spatial multiplexing. Spatial multiplexing can be used to increase data rates in favorable channel conditions. Figure 1 shown an example of spatial multiplexing, where an information carrying symbol vector s is multiplied by an NT x r (rows × columns) precoding matrix or precoder W, which serves to distribute the transmit energy on the NT transmit antenna ports in r “virtual” spatial directions, each associated to a data stream, such that they can be distinguished at the UE. The precoding matrix is typically selected from a codebook of possible precoding matrices, and typically reported by a UE in the form of a precoding matrix indicator (PMI). PMI indicates a desired precoding matrix in the codebook for a given number of symbol streams. Vector s contains r symbols each corresponding to a MIMO layer or data stream, and r is referred to as the transmission rank or simply rank. In this way, spatial multiplexing is achieved since multiple symbols or data streams can be transmitted simultaneously over the same time / frequency Resource Elements (REs). r is selected to suit the matrix channel H and is typically reported by a UE in the form of a Rank Indicator (RI).

[0006] NR uses Orthogonal Division Multiplexing (OFDM) in downlink. The received NR x 1 vector y at a UE in a scheduled RE can be expressed as ^= ^^^ + ^where e is a receiver noise / interference vector.

[0007] The precoder ^ is chosen to match the characteristics of the ^^ × ^^ MIMO channelmatrix ^. This is also commonly referred to as closed-loop precoding. In closed-loop precoding, the UE feeds back recommendations on a suitable precoder to the gNB in the form of a PMI based on downlink channel measurements. For that purpose, the UE is configured with a channel state information (CSI) report configuration including CSI reference signals (CSI-RS) for channel measurements and a codebook of candidate precoders. In addition to PMI and RI, the feedback typically also includes a channel quality indicator (CQI). RI, PMI and CQI are part of a CSI feedback. In NR, PMI and CQI feedback can be either per wideband or per subband where a subband is defined as a number of contiguous physical resource blocks (PRBs) ranging between 4-32 PRBs depending on the bandwidth part (BWP) size.

[0008] The transmit antennas at the gNB can be a linear antenna array with uniformly spaced antenna ports or a two-dimensional antenna array with uniformly spaced antenna ports in each dimension. The antenna array can be described by a number of antenna ports, ^^, in a first dimension (e.g., the horizontal dimension), a number of antenna ports, ^^, in the second dimension perpendicular to the first dimension (e.g., the vertical dimension), and a number ofpolarizations ^^. The total number of antenna ports is thus ^^ = ^^^^^^. The concept of anantenna port is non-limiting in the sense that it can refer to any virtualization (e.g., linear mapping) to one or multiple physical antenna elements. For example, pairs of physical antenna elements could be fed the same signal, and hence share the same virtualized antenna port.

[0009] An example of a 4x4 (i.e., ^^ × ^^,) array with dual-polarized antenna elements (i.e.,^^ = 2) is illustrated below in Figure 2.

[0010] Precoding may also be interpreted as beamforming where the signal to be transmitted on the antenna ports are multiplied by a set of beamforming weights prior to transmission. The beamforming weights are specified by the precoding matrix. Each MIMO layer is transmitted on an antenna beam.

[0011] DFT-based precoders

[0012] A common type of precoders is Discrete Fourier Transform (DFT) based precoders, where the precoding vector for each MIMO layer is a DFT vector, i.e., each column of ^ is a DFT vector.

[0013] For a two-dimensional (2-D) uniform planar array (UPA) with ^^antenna ports in one dimension and ^^antenna ports in another dimension, for each polarization a DFT beam associated to the 2-D UPA can be expressed as a Kronecker product of two one-dimension (1- D) DFT vectors, one in each dimension, i.e., as: ^^,^ = ^^,^^^^,^,^^ / ^ ^⋅^⋅ ^^^⋅^⋅of^^ , = … , ^ ^ − 7 =0,1, … , ^ 1^ − 1( are the 1- indices along N1 and N2 dimensions, respectively. Inspecification TS 38.214 the terminologies ‘beam’ or ‘2D-beam’ are not used, but only ^^,^is referred .

[0015] A rank one precoder for a dual-polarized UPA can then be expressed as ^8%2, 7, 9( = : ^,^^^;^ < = : ^^,^ = 1= ^ < > ^;? ,between the two polarizations and may be selectedfrom M-PSK alphabets such as QPK with 9 ∈ {0, ^^ , B, C^^ }. The above assumes that the sameDFT beam, ^ , is used for both

[0017] rank two or higher, a precoder for each layer comprise one or more DFT beams. The precoding matrix ^ for rank E can be expressed as: ^= F8%2^, 7^, 9^( 8%2^, 7^, 9^( ⋯ 8%2H, 7H, 9H(I^^where 8%2 , 7 , 9 ( = K,^K(L = 1,2, … , E( is a pre MNJ J : coder for the L layer associated to aDFT beam, ^,^K,

[0018] precoders are used in NR Type I CSI feedback, where each layer is associated with one 2-D DFT beam.

[0019] For CSI feedback based on various NR type II codebooks, the precoder for each data layer is a linear combination of multiple DFT beams. The PMI comprises multiple selected DFT beams and a set of combining coefficients for each layer. The details of NR type I and Type II codebooks can be found in 3GPP TS 38.214 v18.0.0.

[0020] Codebook Subset Restriction (CBSR)

[0021] In some deployment scenarios, to reduce potential inter-cell interference for example, it may be desirable to avoid DL transmission at certain spatial directions such as at or above the horizontal directions. An example is shown in Figure 3, where there are ^^1^^^1^beams and each beam is represented by a circle. The beams with red circles are restricted, i.e., not to be considered for precoder feedback.

[0022] The restricted beams are informed to a UE via CBSR configuration in NR. For NR type I single panel codebook, the CBSR configuration comprises a bitmap parameter n1-n2, whichforms a bit sequence OPQ'^, ... , O^, O^ where O^ is the LSB and OPQ'^ is the MSB. The number ofbits is given by ST = ^^1^^^1^, where each bit is associated to an oversampled DFT beam.Except when the number of layers U ∈ {3,4} and the number of antenna ports is 16, 24, or 32, bitO&0X0^Y^ is associated the oversampled DFT beam Z^,^, 2 = 0, … , ^^1^ − 1, 7 = 0, … , ^^1^ −1. A bit value of zero indicates that PMI reporting is not allowed to correspond to any precoder associated with the beam indicated by the bit.

[0023] When the number of layers U ∈ {3,4} and the number of antenna ports is 16, 24, or 32,the antenna array is divided into two subarrays along the ^^dimension. - bits O%&0X0%^^'^(Y^( ^[\ &"X"&0X0, O&0X0%^^(Y^, O&0X0%^^Y^(Y^are each associated with all precoders based on the quantity Z] &"X"^,^, 2 = 0, … , ^ − 1, 7 = 0, … , ^^1^ − 1;- if one or more of the associatedreporting is not allowed to correspond to any precoder based on Z]^,^.`a b#"^ c"d

[0024] ^^ `a^^0is the DFT beam of each subarray.SUMMARY

[0025] Systems and methods for group-based beam scaling restriction for large antenna arrays are provided. In some embodiments, a method performed by a User Equipment (UE) includes: receiving a configuration from a network node that provides information; determining mapping between bits in a bitmap and a Spatial Domain (SD) basis vector group; determining one or more SD basis vectors to be included as part of Precoding Matrix Indicator (PMI) according to the mapping; and reporting PMI to the network node as part of Channel State Information (CSI) reporting to the network node. In this way, the UE can determine the correct mapping betweenCodebook Subset Restriction (CBSR) bitmap and SD basis vectors in SD basis vector groups when group-based CBSR signaling is used. The UE can also determine the correct mapping between scaling factor bitmap and SD basis vectors in SD basis vector groups when group-based CBSR signaling is used.

[0026] In some embodiments, the information is on one or more of the following: a number of antenna ports in one or more dimensions; a number of ports per SD basis vector group; a bitmap providing a CBSR; and a bitmap providing scaling factors to be applied for SD basis vectors.

[0027] In some embodiments, the method also includes: determining the scaling factors to be applied to SD basis vectors when determining one or more SD basis vectors to be included as part of PMI and during Channel Quality Indicator (CQI) determination according to the mapping.

[0028] In some embodiments, reporting the PMI further comprises reporting CQI. In some embodiments, the configuration received includes information on the number of ports ^^in a first dimension, and the number of ports ^^in a second dimension.

[0029] In some embodiments, the number of ports ^^is 1 in which case the port layout is onedimensional wherein ^^ > 1 and ^^ = 1.

[0030] In some received by the UE includes information onthe number of ports g^per SD basis vector group in the first dimension, and the number of ports g^per SD basis vector group in the second dimension.

[0031] In some embodiments, ^^ = 1, the number of ports g^ per SD basis vector group isone and information on g^is not explicitly configured.

[0032] In some embodiments, the configuration received by the UE includes information onCBSR bitmap h h h … h h wherein h de MNi i'^ i'^ ^ ^ j notes the CBSR bit corresponding to the k SDbasis vector group, and l = m^⋅n^⋅m.⋅n.o^⋅o. is the number of SD basis vector groups.

[0033] In some embodiments, the configuration received by the UE includes information ona bit sequence pC = p%^(C p%^(C ⋯ p%i(C which is the concatenation of the bit sequencesp%j(C corresponding mand l = ^⋅n^⋅m.⋅n. is the number of SD basis vectorgroups.

[0034] In some embodiments, wherein 1^and 1^are pre-defined in 3GPP specifications. In some embodiments, 1^and 1^arepart of the configuration information.

[0035] In somethe bitmap comprises a CBSR bitmap and determining mapping between bits in the CBSR bitmap and the SD basis vector groups comprises determining according to at least one mapping alternative.

[0036] In some embodiments, the bitmap comprises a scaling factor bitmap and determining mapping between bits in the CBSR bitmap and the SD basis vector groups comprises determining according to at least one mapping alternative.

[0037] In some embodiments, determining the one or more SD basis vectors to be included as part of PMI comprises: only including SD basis vectors belonging to SD basis vector groups from which UE is allowed to include SD basis vectors as part of PMI according to the mapping. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.

[0039] Figure 1 illustrates a transmission structure of spatial multiplexing in New Radio (NR);

[0040] Figure 2 illustrates a two-dimensional antenna array of dual-polarized antennaelements ( ^^ = 2( , with ^^ = 4 horizontal antenna elements and ^^ = 4 vertical antennaelements;

[0041] Figure 3 illustrates an example of CBSR with %^^, ^^( = %4,2( and %1^, 1^( = %4,4(;

[0042] Figure 4 illustrates an example illustrating the mapping of the SD basis vector group or beam group associated with the kMNbit in the CBSR bitmap according to an embodiment in this disclosure for mapping alternative A (the value of k corresponding to the SD basis vector group is shown inside the respective heptagons);

[0043] Figure 5 illustrates an example illustrating the mapping of the SD basis vector group or beam group associated with the kMNbit in the CBSR bitmap according to the above embodiment in this disclosure (the value of k corresponding to the SD basis vector group is shown inside the respective heptagons);

[0044] Figure 6 illustrates an example of a cyclically shifted mapping with mapping alternative E;

[0045] Figure 7 illustrates a method performed by a UE in accordance with some embodiments of the present disclosure;

[0046] Figure 8 shows an example of a communication system in accordance with some embodiments of the present disclosure;

[0047] Figure 9 shows a User Equipment device (UE) in accordance with some embodiments of the present disclosure;

[0048] Figure 10 shows a network node in accordance with some embodiments of the present disclosure; and

[0049] Figure 11 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized in accordance with some embodiments of the present disclosure. DETAILED DESCRIPTION

[0050] The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure.

[0051] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0052] There currently exist certain challenge(s). The current CBSR can be used to remove some of the DFT beams from PMI feedback and thus, to avoid DL data transmission in directions associated to the DFT beams.

[0053] In NR Rel-19, support for large antenna arrays with 48, 64, and 128 antenna ports is to be specified with the following port layouts being supported: Number of AntennaPort Layout %^^, ^^(Ports 48 (8,3) (6,4) 64 (16,2) (8,4) 128 (16,4) (8,8)

[0054] However, simply extending the beam based CBSR with ^^1^^^1^bits will result in high signaling overhead for the newly agreed port layouts above. For instance, for port layout%^^, ^^( = %16,4(, ^^1^^^1^ = 1024 bits are needed to signal the bitmap which results in quitehigh overhead. To this end, a&"⋅X"⋅&0⋅X0s"⋅s0-bit CBSR is agreed for Rel-19 Type-I codebooks wherein each bit in the CBSR is associated with a set of g^g^SD basis vectors, where the set includes g^adjacent SD basis vectors along the ^^direction and g^adjacent SD bases along the ^^direction (wherein g^and g^are positive integers). Here, a beam group is given by a set of g^g^SD basisvectors. Although a&"⋅X"⋅&0⋅X0s"⋅s0-bit CBSR is agreed, the details of which beam group of size g^g^a given bit in the&"⋅X"⋅&0⋅X0s"⋅s0-bit CBSR is mapped to is an open problem to be solved.

[0055] CBSR is used to restrict certain beam directions that may cause interference to neighboring cells. In some scenarios, however, DL transmission in certain beam directions may still be allowed with a reduced transmit power to meet certain regulatory requirements. For example, when terrestrial mobile communication systems share a same frequency spectrum with satellite communication systems, reducing terrestrial DL transmission power in the beam directions of the satellites may be needed to avoid interference. This issue cannot be addressed by CBSR as CBSR can only be used to completely restrict DL transmission in certain directions and cannot support transmission with reduced transmission power in the beam directions of the satellites. To this end, 3GPP in Rel-19 has agreed to support signaling of 3-bit scaling factors for each group of beams wherein each beam group consists of g′^g′^SD basis vectors. Here, each beam group includes g′^adjacent SD basis vectors along the ^^direction and g′^adjacent SD bases along the ^^direction (wherein g′^and g′^are positive integers). The 3-bit scaling factor signals a power reduction factor to be applied for the corresponding beam group, and each 3-bit scaling factor is mapped to one of the following values: u√1, w1 / 2, w1 / 3 , w1 / 4, w1 / 6, w1 / 8, w1 / 12, w1 / 16z

[0056] Note that the beam group size parameters g′^and g′^here can be different from the beam group size parameters g^and g^used for signaling CBSR in Rel-19. There will be a total ofC&"⋅X"⋅&0⋅X0bits for signC&"⋅X"⋅&0⋅X0sq"⋅sq0aling the beam group scaling factors. Althoughsq"⋅sq0bits areof 3 among theC&"⋅X"⋅&0⋅X0sq"⋅sq0bits is mapped to is another open problem to be solved.

[0057] of the disclosure and their embodiments may provide solutions to these or other challenges. When group based CBSR bitmap is signaled, this disclosure proposes several mapping alternatives for mapping bits in the CBSR bitmap to SD basis vector groups in a codebook.

[0058] When group based scaling factor bitmap is signaled, this disclosure proposes several mapping alternatives for mapping bits in the scaling factor bitmap to SD basis vector groups in a codebook.

[0059] Some embodiments disclosed herein are for mapping bits in CBSR bitmap to SD basis vector group. In some embodiments, the UE receives configuration from the gNB that provides information on one or more of the following: a number of antenna ports in one or more dimensions:the configuration received by the UE includes information on the number of ports ^^in a first dimension, and the number of ports ^^in a second dimension. In a special case, the number ofports ^^ is 1 in which case the port layout is one dimensional wherein ^^ > 1^^ = 1; anumber of ports per SD basis vector group: the configuration received by the UE includes information on the number of ports g^per SD basis vector group in the first dimension, and the number of ports g^per SD basis vector group in the second dimension. In the special case where^^ = 1, the number of ports g^ per SD basis vector group is one and information on g^ may notbe explicitly configured. That is, when the configuration information indicates ^^ = 1, it impliesthat g^ = 1; and a bitmap providing the CBSR: the configuration received by the UE includesinformation on CBSR bitmap hihi'^hi'^ … h^h^ wherein hj denotes the CBSR bitcorresponding to the kMN SD basis vector group, and l = m^⋅n^⋅m.⋅n.o^⋅o. is the number of SD basisvector groups. It should be noted that in some embodiments, 1^(oversampling factor in the 1stdimension) and 1^(oversampling factor in the 2nddimension) are pre-defined in 3GPP specifications. In an alternative embodiment, 1^and 1^are signaled to the UE by the gNB as part of the configuration information.

[0060] Some embodiments include the UE determining mapping between bits in the CBSR bitmap and the SD basis vector groups according to at least one of the mapping alternatives A, B, C, D, or E in Embodiment 1. Some embodiments include the UE determining one or more SD basis vectors to be included as part of PMI according to the mapping determined in previous step (UE only includes SD basis vectors belonging to SD basis vector groups from which UE is allowed to include SD basis vectors as part of PMI according to the mapping determined in previous step). Some embodiments include the UE reporting PMI to network as part of CSI reporting to the gNB.

[0061] Core Essence for mapping bits in scaling factor bitmap to SD basis vector group. In some embodiments, the UE receives configuration from the gNB that provides information on one or more of the following:

[0062] Number of antenna ports in one or more dimensions: the configuration received by the UE includes information on the number of ports ^^in a first dimension, and the number of ports ^^in a second dimension. In a special case, the number of ports ^^is 1 in which case the portlayout is one dimensional wherein ^^ > 1 and ^^ = 1.

[0063] Number of ports perbasis vector group: the configuration received by the UE includes information on the number of ports g′^per SD basis vector group in the first dimension, and the number of ports g′^per SD basis vector group in the second dimension. In the specialcase where ^^ = 1, the number of ports g′^ per SD basis vector group is one and information ong′^may not be explicitly configured. That is, when the configuration information indicates ^^= 1, it implies that g′^ = 1.

[0064] A bitmap providing the scaling factors to be applied for SD basis vectors: the configuration received by the UE includes information on a bit sequence p = %^( %^( %i(C pC pC ⋯ pCwhich is the concatenation of the bit sequences p%j(C corresponding to the k-th beam group, and l= m^⋅n^⋅m.⋅n.oq^⋅oq. is the number of SD basis vector groups. It should be noted that in some(oversampling factor in the 1stdimension) and 1^(oversampling factor in theare pre-defined in 3GPP specifications. In an alternative embodiment, 1^and 1^are signaled to the UE by the gNB as part of the configuration information.

[0065] In some embodiments, the UE determines a mapping between bits in the scaling factor bitmap and the SD basis vector groups according to at least one of the mapping alternatives A’, B’, C’, or D’ in Embodiment 2.

[0066] UE determining the scaling factors to be applied to SD basis vectors when determining one or more SD basis vectors to be included as part of PMI and during CQI determination according to the mapping determined in previous step.

[0067] UE reporting the determined PMI and CQI to network as part of CSI reporting to the gNB.

[0068] Certain embodiments may provide one or more of the following technical advantage(s). With the proposed solutions, the UE can determine the correct mapping between CBSR bitmap and SD basis vectors in SD basis vector groups when group-based CBSR signaling is used.

[0069] With the proposed solutions, the UE can determine the correct mapping between scaling factor bitmap and SD basis vectors in SD basis vector groups when group-based CBSR signaling is used. The teachings of certain embodiments may improve the e.g., data rate, latency, power consumption, etc.

[0070] Embodiment 1: Mapping of bits in CBSR bitmap to beam groups

[0071] In case of CBSR, the UE receives configuration from the gNB that provides information on one or more of the following:

[0072] Number of antenna ports in one or more dimensions: the configuration received by the UE includes information on the number of ports ^^in a first dimension, and the number of ports ^^in a second dimension. In a special case,number of ports ^^is 1 in which case the port layout is one dimensional wherein ^^ > 1 and ^^ = 1.

[0073] Number of ports per SD basis vector group or beam group: the configuration received by the UE includes information on the number of ports g^per SD basis vector group or beam group in the first dimension, and the number of ports g^per SD basis vector group or beam groupin the second dimension. In the special case where ^^ = 1, the number of ports g^ per SD basisvector group or beam group is one and information on g^may not be explicitly configured. Thatis, when the configuration information indicates ^^ = 1, it implies that g^ = 1.

[0074] A bitmap or bit string providing the CBSR: the configuration received by the UEincludes information on CBSR bitmap (or bit string) hihi'^hi'^ … h^h^ wherein hj %k =1, 2, … , l − 1, l( denotes the CBSR bit corresponding to the kMN SD basis vector group or beamgroup, and l = m^⋅n^⋅m.⋅n.o^⋅o. is the number of SD basis vector groups or beam groups. It should benoted that in some embodiments, 1^and 1^are pre-defined in 3GPP specifications. In an alternative embodiment, 1^and signaled to the UE by the gNB as part of the configurationinformation.

[0075] Let the kMNSD basis vector group or beam group be composed of the following g^g^2-D DFT vectors: ^{|,",{|,0 , ^{|,"Y^,{|,0 , … ^{|,"Ys"'^,{|,0 ,^{|,",{|,0Y^ , ^{|,"Y^,{|,0Y^ , … ^{|,"Ys"'^,{|,0Y^ ,… ^{|,",{|,0Ys0'^ , ^{|,"Y^,{|,0Ys0'^ , … ^{|,"Ys"'^,{|,0Ys0'^ ,where ^{|,",{|,0represents the ‘first’ or ‘starting’ SD basis vector in the kMNSD basis vector group or beam group. Note that the SD basis vector group or beam group defined above involves 2-D DFT vectors involving g^consecutive SD basis vectors or beams in the first dimension, and g^consecutive SD basis vectors or beams in the second dimension.

[0076] In order to identify the set of g^g^SD basis vectors corresponding to the kMNSD basis vector group or beam group, the SD basis vector ^{|,",{|,0needs to be identified.

[0077] Mapping Alternative A:

[0078] In one embodiment, when the SD basis vector group index or beam group index k isdefined in the range k = {1, 2, … , l − 1, l}, } MNj,^ and }j,^ corresponding to the k SD basisvector group or beam group are defined as follows:}j,^ = ~Oj,^ − 1^g^−1wherein⌈∙⌉and 7^^%∙( operator, respectively.

[0079] Mapping Alternative B:

[0080] In an alternative embodiment, k may be defined in the range k = {0, 1, … , l − 2, l −1}. In the alternative embodiment, }j,^and }j,^corresponding to the kMNSD basis vector group or beam group are defined as follows: }j,^ = Oj,^g^}j,^ = Oj,^g^^^1O ,^ = ^j 7^^%k, ^ ^(^wherein ⌊∙⌋ represents floor

[0081] An example illustrating the mapping between the kMNbit in the CBSR bitmap and theSD basis vector group for mapping alternative A is shown in Figure 4, where ^^ = 6, ^^ = 3,and 1^ = 1^ = 4. Furthermore, the values of g^ and g^ are both 4of Figure 4.The ‘starting’ beam ^{|,",{|,0for the kMNbeam group using the above embodiment is determined as follows:k }j,^}j,^1 0 0 2 0 4 3 0 8 4 4 05 4 4 6 4 8 7 8 0 8 8 4 9 8 8 10 12 0 11 12 4 12 12 8 13 16 0 14 16 4 15 16 8 16 20 0 17 20 4 18 20 8

[0082] Mapping Alternative C:

[0083] In an alternative embodiment, when the SD basis vector group index or beam groupindex k is defined in the range k = {1, 2, … , l − 1, l}, } MNj,^ and }j,^ corresponding to the k SDbasis vector group or beam group are defined as follows: }j,^ = ~Oj,^ − 1^g^}j,^ = %Oj,^ − 1(g^1wherein ⌈∙⌉ and 7^^%∙(operator, respectively.

[0084] Mapping Alternative D:In an alternative embodiment, k may be defined in the range k = {0, 1, … , l − 2, l − 1}. In thealternative embodiment, }j,^and }j,^corresponding to the kMNSD basis vector group or beamgroup are defined as follows: }j,^ = Oj,^g^}j,^ = Oj,^g^^O = 7^^ ^1^j,^ %k, ^g ^(^kgO ^j,^ = ^^ ^^1^

[0085] An example illustrating the mapping between the kMNbit in the CBSR bitmap and theSD basis vector group for mapping alternative C is shown in Figure 5 for range k = {1, 2, … , l −1, l}, where ^^ = 6, ^^ = 3, and 1^ = 1^ = 4. Furthermore, the values of g^ and g^ are both 4in the example of Figure 5. The ‘starting’ beam ^{|,",{|,0for the kMNbeam group using the above embodiment is determined as follows: k }j,^}j,^1 0 0 2 4 0 3 8 0 4 12 0 5 16 0 6 20 0 7 0 4 8 4 4 9 8 4 10 12 4 11 16 4 12 20 4 13 0 8 14 4 8 15 8 8 16 12 8 17 16 8 18 20 8

[0086] Mapping Alternative E:In another embodiment, offsets h st^, h^, can be added to the starting SD basis vector in the 1 and / or2nddimension, where the magnitude of the offset can be smaller than g^and g^, respectively, i.e.,|h^| < g^ and |h^| < g^ . This can be useful to better align the SD basis vector groups to thedirections in which it is desired to reduce interference. In one embodiment. the starting SD basis vectors for the groups are cyclically shifted so that if the starting SD basis vector of a group afteradding the offset is outside the range [0, l − 1I it is mapped back into this range with the modulooperator according to }j,^ = 7^^ b~Oj,^ − 1^g^ + h^, ^^1^dand similarly for }j,^. This example with h^ = −2 andh = 0.^k }j,^}j,^1 22 0 2 2 0 3 6 0 4 10 0 5 14 0 6 18 0 7 22 4 8 2 4 9 6 4 10 10 4 11 14 4 12 18 4 13 22 8 14 2 8 15 6 8 16 10 8 17 14 8 18 18 8

[0087] Embodiment 2: Mapping of bits in scaling factor bitmap to beam groups

[0088] In case of scaling factor signaling, the UE receives configuration from the gNB that provides information on one or more of the following:

[0089] Number of antenna ports in one or more dimensions: the configuration received by the UE includes information on the number of ports ^^in a first dimension, and the number of ports ^^in a second dimension. In a special case, the number of ports ^^is 1 in which case the port layout is one dimensional wherein ^^> 1 and = 1.

[0090] Number of ports per SD basis vector group or beam group: the configuration received by the UE includes informationthe number of ports g′^per SD basis vector group or beam group in the first dimension, and the number of ports g′^per SD basis vector group or beam group in the second dimension. In the special case where ^^ = 1, the number of ports g′^ per SD basisvector group or beam group is one and information on g′^may not be explicitly configured. That is, when the configuration information indicates ^^ = 1, it implies that g′^ = 1.

[0091] Let the kMNSD basis vector group or beam group specific to the beam scaling factor signaling be composed of the following g′^g′^2-D DFT vectors: ^{|,",{|,0 , ^{|,"Y^,{|,0 , … ^{|,"Ysq"'^,{|,0 ,^{|,",{|,0Y^ , ^{|,"Y^,{|,0Y^ , … ^{|,"Ysq"'^,{|,0Y^ ,… ^{|,",{|,0Ysq0'^ , ^{|,"Y^,{|,0Ysq0'^ , … ^{|,"Ysq"'^,{|,0Ysq0'^ ,where ^{|,",{|,0represents the ‘first’ or ‘starting’ SD basis vector in the kMNSD basis vector groupspecific to scaling factor signaling. Note that the SD basis vector group or beam group defined above involves 2-D DFT vectors involving g′^consecutive SD basis vectors or beams in the first dimension, and g′^consecutive SD basis vectors or beams in the second dimension.

[0092] In an embodiment, the scaling factors for the beam groups is configured / indicated to a UE through a bit sequence p %^( %^( %i(C = pC pC ⋯ pC which is the concatenation of the bit sequencesp%j(corresponding to the k-th beam groupthe number of groups is l = m^⋅n^⋅m.⋅n.. Thesequence p%j(C is defined asp%j( %j,^( %j,^( %j,^(C = hC hC hC .

[0093] Bits h%j,^(C h%j,^(C h%j,^(C indicate the amplitude scaling factor to be applied for the k-th beam group where the amplitude scaling factors are given in Table.Table 1: Amplitude scaling factors for beam groups h%j,^( %j,^( %j,^(ChC hCAmplitude scaling000w1 / 16001w1 / 12010w1 / 8011w1 / 6100w1 / 4101w1 / 3110w1 / 2111√1

[0094] In order to identify the set of g′^g′^SD basis vectors corresponding to the kMNSD basis vector group or beam group, the SD basis vector ^{|,",{|,0needs to be identified. For the case of scaling factor signaling, to apply the correct scaling factor to the appropriate SD basis vector group, identification of this mapping is necessary. This mapping can be identified by any one of the following mapping alternatives:

[0095] Mapping Alternative A’:

[0096] In one embodiment, when the SD basis vector group index or beam group index k isdefined in the range k = {1, 2, … , l − 1, l}, } MNj,^ and }j,^ corresponding to the k SD basisvector group or beam group are defined as follows: }j,^ = ~Oj,^ − 1^g′^}j,^ = %Oj,^ − 1(g′^^^%k − ^ ^1= 7^ ^ ^ + 1wherein ⌈∙⌉ and 7^^%∙(operator, respectively.

[0097] Mapping Alternative B’:

[0098] In an alternative embodiment, k may be defined in the range k = {0, 1, … , l − 2, l −1}. In the alternative embodiment, }j,^and }j,^corresponding to the kMNSD basis vector group or beam group are defined as follows: }j,^ = Oj,^g′^}j,^ = Oj,^g′^^7^^%k, ^ ^1O = ^j,^ g′ ^(^wherein ⌊∙⌋ represent floor

[0099] Mapping Alternative C’:

[0100] In an alternative embodiment, when the SD basis vector group index or beam groupindex k is defined in the range k = {1, 2, … , l − 1, l}, } MNj,^ and }j,^ corresponding to the k SDbasis vector group or beam group are defined as follows: }j,^ = ~Oj,^ − 1^g′^}j,^ = %Oj,^ − 1(g′^^O = 7^^%k ^1^j,^ − 1, ^ ^( + 1wherein⌈∙⌉and 7^^%∙(operator, respectively.

[0101] Mapping Alternative D’:

[0102] In an alternative embodiment, k may be defined in the range k = {0, 1, … , l − 2, l −1}. In the alternative embodiment, }j,^and }j,^corresponding to the kMNSD basis vector group or beam group are defined as follows: }j,^ = Oj,^g′^}j,^ = Oj,^g′^^O = 7^^ ^1^j,^ %k, ^g′ ^(^

[0103] Embodiment 3: UE behavior for case of mapping of bits in CBSR bitmap to beam groups

[0104] Mapping Alternative A:

[0105] In an embodiment, when the beam group index k is defined in the range k =1, 2, … , l − 1, l, a UE determines the group index corresponding to CBSR of a beam Z^,^ ask = ⌊2 / g^⌋ × ^&0X0s0 ^ + ⌊7 / g^⌋ + 1.

[0106] Mapping

[0107] In an embodiment, when the beam group index k is defined in the range k =0, 1, … , l − 2, l − 1, a UE determines the group index corresponding to CBSR of a beam Z^,^ ask = ⌊2 / g^⌋ × ^&0X0s0 ^ + ⌊7 / g^⌋.

[0108] Mapping

[0109] In an embodiment, when the beam group index k is defined in the range k =1, 2, … , l − 1, l, a UE determines the group index corresponding to CBSR of a beam Z^,^ ask = ⌊7 / g^⌋ × ^&"X"s" ^ + ⌊2 / g^⌋ + 1.

[0110] Mapping

[0111] In an embodiment, when the beam group index k is defined in the range k =0, 1, … , l − 2, l − 1, a UE determines the group index corresponding to CBSR of a beam Z^,^ ask = ⌊7 / g^⌋ × ^&"X"s" ^ + ⌊2 / g^⌋.

[0112] In an embodimentk of a beam Z^,^), a UE is allowed to include beam Z^,^as part of a PMI only if the bit corresponding to the kMNgroup in the CBSR bitmap indicatesbeams from the kMNgroup is allowed to be included as part of the PMI. If the bit corresponding to the kMNgroup in the CBSR bitmap indicates if the beams from the kMNgroup is not allowed to be included as part of the PMI, then the UE is not allowed to include beam Z^,^as part of a PMI. Stated otherwise, the UE only includes beams belonging tobeam groups from which UE is allowed to include beams as part of PMI according to the CBSR bitmap.

[0113] Embodiment 4: UE behavior for case of mapping of bits in scaling factor bitmap to beam groups

[0114] Mapping Alternative A’:

[0115] In an embodiment, when the beam group index k is defined in the range k =1, 2, … , l − 1, l, a UE determines the group index related to scaling factor of a beam Z^,^ ask = ⌊2 / g′^⌋ × ^&0X0sq0 ^ + ⌊7 / g′^⌋ + 1.

[0116] Mapping

[0117] In an embodiment, when the beam group index k is defined in the range k =0, 1, … , l − 2, l − 1, a UE determines the group index related to scaling factor of a beam Z^,^ ask = ⌊2 / g′^⌋ × ^&0X0sq0 ^ + ⌊7 / g′^⌋.

[0118] Mapping

[0119] In an embodiment, when the beam group index k is defined in the range k =1, 2, … , l − 1, l, a UE determines the group index related to scaling factor of a beam Z^,^ ask = ⌊7 / g′ &"X^⌋ × ^ "sq" ^ + ⌊2 / g′^⌋ + 1.

[0120] Mapping Alternative D’:

[0121] In an embodiment, when the beam group index k is defined in the range k =0, 1, … , l − 2, l − 1, a UE determines the group index related to scaling factor of a beam Z^,^ ask = ⌊7 / g′^⌋ × ^&"X"sq" ^ + ⌊2 / g′^⌋.

[0122] In an embodimentk of a beam Z^,^), a UE uses thescaling factor indicated by the bit sequence p%j( %j,^( %j,^( %j,^(C = hC hC hC to the beam Z^,^ belongingto beam group k when determining onea PMI and / or CQI.

[0123] In a related embodiment, a UE may adjust the scaling factor indicated for a beam Z^,^by the number of layers that are transmitted with the beam and the total number of layers in the PMI.

[0124] Figure 7 illustrates a method performed by a UE. The method includes one or more of: receiving (step 700) a configuration from the gNB that provides information; determining (step702) mapping between bits in a bitmap and a SD basis vector groups wherein ^ ≥ 1 bits in thebitmap map to a single SD basis vector group; determining (step 704) one a PMI according to the mapping; and reporting (step 706) PMI to network as part of CSI reporting to the gNB.

[0125] Figure 8 shows an example of a communication system 800 in accordance with some embodiments.

[0126] In the example, the communication system 800 includes a telecommunication network 802 that includes an access network 804, such as a Radio Access Network (RAN), and a core network 806, which includes one or more core network nodes 808. The access network 804 includes one or more access network nodes, such as network nodes 810A and 810B (one or more of which may be generally referred to as network nodes 810), or any other similar Third Generation Partnership Project (3GPP) access nodes or non-3GPP Access Points (APs). Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network 802 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 802 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network 802, including one or more network nodes 810 and / or core network nodes 808.

[0127] Examples of an ORAN network node include an Open Radio Unit (O-RU), an Open Distributed Unit (O-DU), an Open Central Unit (O-CU), including an O-CU Control Plane (O- CU-CP) or an O-CU User Plane (O-CU-UP), a RAN intelligent controller (near-real time or non- real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1, F1, W1, E1, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes 810 facilitate direct orindirect connection of User Equipment (UE), such as by connecting UEs 812A, 812B, 812C, and 812D (one or more of which may be generally referred to as UEs 812) to the core network 806 over one or more wireless connections.

[0128] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 800 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 800 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0129] The UEs 812 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 810 and other communication devices. Similarly, the network nodes 810 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 812 and / or with other network nodes or equipment in the telecommunication network 802 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 802.

[0130] In the depicted example, the core network 806 connects the network nodes 810 to one or more hosts, such as host 816. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 806 includes one more core network nodes (e.g., core network node 808) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 808. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-Concealing Function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0131] The host 816 may be under the ownership or control of a service provider other than an operator or provider of the access network 804 and / or the telecommunication network 802, andmay be operated by the service provider or on behalf of the service provider. The host 816 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0132] As a whole, the communication system 800 of Figure 8 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 800 may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable Second, Third, Fourth, or Fifth Generation (2G, 3G, 4G, or 5G) standards, or any applicable future generation standard (e.g., Sixth Generation (6G)); Wireless Local Area Network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any Low Power Wide Area Network (LPWAN) standards such as LoRa and Sigfox.

[0133] In some examples, the telecommunication network 802 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunication network 802 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 802. For example, the telecommunication network 802 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing enhanced Mobile Broadband (eMBB) services to other UEs, and / or massive Machine Type Communication (mMTC) / massive Internet of Things (IoT) services to yet further UEs.

[0134] In some examples, the UEs 812 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 804 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 804. Additionally, a UE may be configured for operating in single- or multi-Radio Access Technology (RAT) or multi-standard mode. For example, a UE may operate with any one or combination of WiFi, New Radio (NR), and LTE, i.e. being configured for Multi-Radio Dual Connectivity (MR-DC), such as Evolved UMTS Terrestrial RAN (E-UTRAN) NR - Dual Connectivity (EN-DC).

[0135] In the example, a hub 814 communicates with the access network 804 to facilitate indirect communication between one or more UEs (e.g., UE 812C and / or 812D) and network nodes (e.g., network node 810B). In some examples, the hub 814 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 814 may be a broadband router enabling access to the core network 806 for the UEs. As another example, the hub 814 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 810, or by executable code, script, process, or other instructions in the hub 814. As another example, the hub 814 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 814 may be a content source. For example, for a UE that is a Virtual Reality (VR) headset, display, loudspeaker or other media delivery device, the hub 814 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 814 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 814 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy IoT devices.

[0136] The hub 814 may have a constant / persistent or intermittent connection to the network node 810B. The hub 814 may also allow for a different communication scheme and / or schedule between the hub 814 and UEs (e.g., UE 812C and / or 812D), and between the hub 814 and the core network 806. In other examples, the hub 814 is connected to the core network 806 and / or one or more UEs via a wired connection. Moreover, the hub 814 may be configured to connect to a Machine-to-Machine (M2M) service provider over the access network 804 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 810 while still connected via the hub 814 via a wired or wireless connection. In some embodiments, the hub 814 may be a dedicated hub – that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 810B. In other embodiments, the hub 814 may be a non-dedicated hub – that is, a device which is capable of operating to route communications between the UEs and the network node 810B, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0137] Figure 9 shows a UE 900 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged, and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, Voice over Internet Protocol (VoIP) phone, wireless local loopphone, desktop computer, Personal Digital Assistant (PDA), wireless camera, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, Laptop Embedded Equipment (LEE), Laptop Mounted Equipment (LME), smart device, wireless Customer Premise Equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3GPP, including a Narrowband Internet of Things (NB-IoT) UE, a Machine Type Communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0138] A UE may support Device-to-Device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), Vehicle-to-Vehicle (V2V), Vehicle-to-Infrastructure (V2I), or Vehicle- to-Everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0139] The UE 900 includes processing circuitry 902 that is operatively coupled via a bus 904 to an input / output interface 906, a power source 908, memory 910, a communication interface 912, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 9. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0140] The processing circuitry 902 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 910. The processing circuitry 902 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 902 may include multiple Central Processing Units (CPUs).

[0141] In the example, the input / output interface 906 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices.Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 900. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0142] In some embodiments, the power source 908 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 908 may further include power circuitry for delivering power from the power source 908 itself, and / or an external power source, to the various parts of the UE 900 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 908. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 908 to make the power suitable for the respective components of the UE 900 to which power is supplied.

[0143] The memory 910 may be or be configured to include memory such as Random Access Memory (RAM), Read Only Memory (ROM), Programmable ROM (PROM), Erasable PROM (EPROM), Electrically EPROM (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 910 includes one or more application programs 914, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 916. The memory 910 may store, for use by the UE 900, any of a variety of various operating systems or combinations of operating systems.

[0144] The memory 910 may be configured to include a number of physical drive units, such as Redundant Array of Independent Disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, High Density Digital Versatile Disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, Holographic Digital Data Storage (HDDS) optical disc drive, external mini Dual In-line Memory Module (DIMM), Synchronous Dynamic RAM (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a tamper resistant module in the form of a Universal Integrated Circuit Card (UICC) includingone or more Subscriber Identity Modules (SIMs), such as a Universal SIM (USIM) and / or Internet Protocol Multimedia Services Identity Module (ISIM), other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as a ‘SIM card.’ The memory 910 may allow the UE 900 to access instructions, application programs, and the like stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system, may be tangibly embodied as or in the memory 910, which may be or comprise a device-readable storage medium.

[0145] The processing circuitry 902 may be configured to communicate with an access network or other network using the communication interface 912. The communication interface 912 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 922. The communication interface 912 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 918 and / or a receiver 920 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 918 and receiver 920 may be coupled to one or more antennas (e.g., the antenna 922) and may share circuit components, software, or firmware, or alternatively be implemented separately.

[0146] In the illustrated embodiment, communication functions of the communication interface 912 may include cellular communication, WiFi communication, LPWAN communication, data communication, voice communication, multimedia communication, short- range communications such as Bluetooth, NFC, location-based communication such as the use of the Global Positioning System (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband CDMA (WCDMA), GSM, LTE, NR, UMTS, WiMax, Ethernet, Transmission Control Protocol / Internet Protocol (TCP / IP), Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), Quick User Datagram Protocol Internet Connection (QUIC), Hypertext Transfer Protocol (HTTP), and so forth.

[0147] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 912, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports thesensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected, an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0148] As another example, a UE comprises an actuator, a motor, or a switch related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0149] A UE, when in the form of an IoT device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application, and healthcare. Non-limiting examples of such an IoT device are a device which is or which is embedded in: a connected refrigerator or freezer, a television, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or VR, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an IoT device comprises circuitry and / or software in dependence of the intended application of the IoT device in addition to other components as described in relation to the UE 900 shown in Figure 9.

[0150] As yet another specific example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship, an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0151] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator and handle communication of data for both the speed sensor and the actuators.

[0152] Figure 10 shows a network node 1000 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged, and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment in a telecommunication network. Examples of network nodes include, but are not limited to, APs (e.g., radio APs), Base Stations (BSs) (e.g., radio BSs, Node Bs, evolved Node Bs (eNBs), NR Node Bs (gNBs)), and O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0153] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node), and / or Remote Radio Units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such RRUs may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a Distributed Antenna System (DAS).

[0154] Other examples of network nodes include multiple Transmission Point (multi-TRP) 5G access nodes, Multi-Standard Radio (MSR) equipment such as MSR BSs, network controllers such as Radio Network Controllers (RNCs) or BS Controllers (BSCs), Base Transceiver Stations (BTSs), transmission points, transmission nodes, Multi-Cell / Multicast Coordination Entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0155] The network node 1000 includes processing circuitry 1002, memory 1004, a communication interface 1006, and a power source 1008. The network node 1000 may be composed of multiple physically separate components (e.g., a NodeB component and an RNC component, or a BTS component and a BSC component, etc.), which may each have their ownrespective components. In certain scenarios in which the network node 1000 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair may in some instances be considered a single separate network node. In some embodiments, the network node 1000 may be configured to support multiple RATs. In such embodiments, some components may be duplicated (e.g., separate memory 1004 for different RATs) and some components may be reused (e.g., a same antenna 1010 may be shared by different RATs). The network node 1000 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1000, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, Long Range Wide Area Network (LoRaWAN), Radio Frequency Identification (RFID), or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within the network node 1000.

[0156] The processing circuitry 1002 may comprise a combination of one or more of a microprocessor, controller, microcontroller, CPU, DSP, ASIC, FPGA, or any other suitable computing device, resource, or combination of hardware, software, and / or encoded logic operable to provide, either alone or in conjunction with other network node 1000 components, such as the memory 1004, to provide network node 1000 functionality.

[0157] In some embodiments, the processing circuitry 1002 includes a System on a Chip (SOC). In some embodiments, the processing circuitry 1002 includes one or more of Radio Frequency (RF) transceiver circuitry 1012 and baseband processing circuitry 1014. In some embodiments, the RF transceiver circuitry 1012 and the baseband processing circuitry 1014 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of the RF transceiver circuitry 1012 and the baseband processing circuitry 1014 may be on the same chip or set of chips, boards, or units.

[0158] The memory 1004 may comprise any form of volatile or non-volatile computer- readable memory including, without limitation, persistent storage, solid state memory, remotely mounted memory, magnetic media, optical media, RAM, ROM, mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD), or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device- readable, and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 1002. The memory 1004 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of beingexecuted by the processing circuitry 1002 and utilized by the network node 1000. The memory 1004 may be used to store any calculations made by the processing circuitry 1002 and / or any data received via the communication interface 1006. In some embodiments, the processing circuitry 1002 and the memory 1004 are integrated.

[0159] The communication interface 1006 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface 1006 comprises port(s) / terminal(s) 1016 to send and receive data, for example to and from a network over a wired connection. The communication interface 1006 also includes radio front-end circuitry 1018 that may be coupled to, or in certain embodiments a part of, the antenna 1010. The radio front-end circuitry 1018 comprises filters 1020 and amplifiers 1022. The radio front-end circuitry 1018 may be connected to the antenna 1010 and the processing circuitry 1002. The radio front-end circuitry 1018 may be configured to condition signals communicated between the antenna 1010 and the processing circuitry 1002. The radio front-end circuitry 1018 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 1018 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of the filters 1020 and / or the amplifiers 1022. The radio signal may then be transmitted via the antenna 1010. Similarly, when receiving data, the antenna 1010 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1018. The digital data may be passed to the processing circuitry 1002. In other embodiments, the communication interface 1006 may comprise different components and / or different combinations of components.

[0160] In certain alternative embodiments, the network node 1000 does not include separate radio front-end circuitry 1018; instead, the processing circuitry 1002 includes radio front-end circuitry and is connected to the antenna 1010. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1012 is part of the communication interface 1006. In still other embodiments, the communication interface 1006 includes the one or more ports or terminals 1016, the radio front-end circuitry 1018, and the RF transceiver circuitry 1012 as part of a radio unit (not shown), and the communication interface 1006 communicates with the baseband processing circuitry 1014, which is part of a digital unit (not shown).

[0161] The antenna 1010 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 1010 may be coupled to the radio front-end circuitry 1018 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 1010 is separate from the network node 1000 and connectable to the network node 1000 through an interface or port.

[0162] The antenna 1010, the communication interface 1006, and / or the processing circuitry 1002 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node 1000. Any information, data, and / or signals may be received from a UE, another network node, and / or any other network equipment. Similarly, the antenna 1010, the communication interface 1006, and / or the processing circuitry 1002 may be configured to perform any transmitting operations described herein as being performed by the network node 1000. Any information, data, and / or signals may be transmitted to a UE, another network node, and / or any other network equipment.

[0163] The power source 1008 provides power to the various components of the network node 1000 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 1008 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1000 with power for performing the functionality described herein. For example, the network node 1000 may be connectable to an external power source (e.g., the power grid or an electricity outlet) via input circuitry or an interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 1008. As a further example, the power source 1008 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0164] Embodiments of the network node 1000 may include additional components beyond those shown in Figure 10 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 1000 may include user interface equipment to allow input of information into the network node 1000 and to allow output of information from the network node 1000. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1000. In some embodiments providing a core network node, such as core network node 108 of FIG. 8, some components, such as the radio front-end circuitry 1018 and the RF transceiver circuitry 1012 may be omitted.

[0165] Figure 11 is a block diagram illustrating a virtualization environment 1100 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices, and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates toan implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more Virtual Machines (VMs) implemented in one or more virtualization environments 1100 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, a UE, a core network node, or a host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 1100 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface. Virtualization may facilitate distributed implementations of a network node, a UE, a core network node, or a host.

[0166] Applications 1102 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 1100 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0167] Hardware 1104 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, an input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1106 (also referred to as hypervisors or Virtual Machine Monitors (VMMs)), provide VMs 1108A and 1108B (one or more of which may be generally referred to as VMs 1108), and / or perform any of the functions, features, and / or benefits described in relation with some embodiments described herein. The virtualization layer 1106 may present a virtual operating platform that appears like networking hardware to the VMs 1108.

[0168] The VMs 1108 comprise virtual processing, virtual memory, virtual networking, or interface and virtual storage, and may be run by a corresponding virtualization layer 1106. Different embodiments of the instance of a virtual appliance 1102 may be implemented on one or more of VMs 1108, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as Network Function Virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers and customer premise equipment.

[0169] In the context of NFV, a VM 1108 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine.Each of the VMs 1108, and that part of the hardware 1104 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 1108 on top of the hardware 1104 and corresponds to the application 1102.

[0170] The hardware 1104 may be implemented in a standalone network node with generic or specific components. The hardware 1104 may implement some functions via virtualization. Alternatively, the hardware 1104 may be part of a larger cluster of hardware (e.g., such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 1110, which, among others, oversees lifecycle management of the applications 1102. In some embodiments, the hardware 1104 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 1112 which may alternatively be used for communication between hardware nodes and radio units.

[0171] Although the computing devices described herein (e.g., UEs, network nodes) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions, and methods disclosed herein. Determining, calculating, obtaining, or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may beimplemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0172] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

[0173] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein.

[0174] EMBODIMENTS

[0175] Group A Embodiments

[0176] Embodiment 1: A method performed by a User Equipment, UE, the method comprising one or more of: receiving (700) a configuration from the gNB that provides information; determining (702) mapping between bits in a bitmap and a SD basis vector groups; determining (704) one or more SD basis vectors to be included as part of PMI according to the mapping; and reporting (706) PMI to network as part of CSI reporting to the gNB.

[0177] Embodiment 2: The method of any of the previous embodiments where the information is on one or more of the following: a number of antenna ports in one or more dimensions; a number of ports per SD basis vector group; a bitmap providing the CBSR; and a bitmap providing the scaling factors to be applied for SD basis vectors.

[0178] Embodiment 3: The method of any of the previous embodiments further comprising: determining the scaling factors to be applied to SD basis vectors when determining one or more SD basis vectors to be included as part of PMI and during CQI determination according to the mapping. Embodiment 4: The method of any of the previous embodiments where reporting the PMI further comprises reporting CQI. Embodiment 5: The method of any of the previous embodiments where the configurationreceived includes information on the number of ports ^^in a first dimension, and the number of ports ^^in a second dimension. Embodiment 6: The method of any of the previous where the number of ports ^^is 1 in which case the port layout is one dimensional wherein ^^ > 1 and ^^ = 1.Embodiment 7: The method of any of the previous embodiments where the configuration received by the UE includes information on the number ofg^per SD basis vector group in the first dimension, and the number of ports g^per SD basis vector group in the second dimension.Embodiment 8: The method of any of the previous embodiments where ^^ = 1, the number ofports g^per SD basis vector group is one and information on g^may not be explicitly configured.That is, when the configuration information indicates ^^ = 1, it implies that g^ = 1.Embodiment 9: The method of any of the previous embodiments where the configurationreceived by the UE includes information on CBSR bitmap hihi'^hi'^ … h^h^ wherein hjdenotes the CBSR bit corresponding to the kMN SD basis vector group, and l = m^⋅n^⋅m.⋅n.o^⋅o. is thenumber of SD basis vector groups. Embodiment 10: The method of any of the previous embodiments where the configurationreceived by the UE includes information on a bit sequence p %^( %^( %i(C = pC pC ⋯ pC which is theconcatenation of the bit sequences p%j(corresponding to the k-th beam gr m^⋅n^⋅m.⋅n.C oup, and l = oq^⋅oq.is the number of SD basis vector groups. Embodiment 11: The method of any of the previous embodiments where 1^(e.g., oversampling factor in the 1stdimension) and 1^(e.g., oversampling factor in the 2nddimension) are pre-defined in 3GPP specifications. Embodiment 12: The method of any of the previous embodiments where 1^and 1^are signaled to the UE by the gNB as part of the configuration information. Embodiment 13: The method of any of the previous embodiments where the bitmap comprises a CBSR bitmap and determining mapping between bits in the CBSR bitmap and the SD basis vector groups comprises determining according to at least one of the mapping alternatives A, B, C, D, or E in Embodiment 1. Embodiment 14: The method of any of the previous embodiments where the bitmap comprises a scaling factor bitmap and determining mapping between bits in the CBSR bitmap and the SD basis vector groups comprises determining according to at least one of the mapping alternatives A’, B’, C’, or D’ in Embodiment 2. Embodiment 15: The method of any of the previous embodiments where determining the one or more SD basis vectors to be included as part of PMI comprises: only including SD basis vectorsbelonging to SD basis vector groups from which UE is allowed to include SD basis vectors as part of PMI according to the mapping. Group B Embodiments Embodiment 16: A method performed by a network node, the method comprising one or more of: transmitting a configuration, to a User Equipment, UE, that provides information; and receiving, from the UE, a report of PMI as part of CSI reporting. Embodiment 17: The method of the previous embodiment further comprising the features of any of the Group A Embodiments. Group C Embodiments Embodiment 18: A user equipment, comprising: processing circuitry configured to perform any of the steps of any of the Group A embodiments; and power supply circuitry configured to supply power to the processing circuitry. Embodiment 19: A network node, the network node comprising: processing circuitry configured to perform any of the steps of any of the Group B embodiments; power supply circuitry configured to supply power to the processing circuitry.

[0179] Embodiment 20: A user equipment (UE), the UE comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the Group A embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.ABBREVIATIONS At least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s). 3GPP 3rd Generation Partnership Project 5G 5th Generation 6G 6thGeneration ABS Almost Blank Subframe ARQ Automatic Repeat Request AWGN Additive White Gaussian Noise BCCH Broadcast Control Channel BCH Broadcast Channel CA Carrier Aggregation CBSR Codebook Subset Restriction CC Carrier Component CCCH SDU Common Control Channel SDU CDMA Code Division Multiplex Access CGI Cell Global Identity CIR Channel Impulse Response CP Cyclic Prefix CPICH Common Pilot Channel CQI Channel Quality Information C-RNTI Cell RNTI CSI Channel State Information DCCH Dedicated Control Channel DFT Discrete Fourier Transform DL Downlink DM Demodulation DMRS Demodulation Reference Signal DRX Discontinuous Reception DTX Discontinuous Transmission DTCH Dedicated Traffic Channel DUT Device Under Test E-CID Enhanced Cell-ID (positioning method) Ec / No Received energy per chip divided by the power density in the band eMBMS Evolved Multimedia Broadcast Multicast Services ECGI Evolved CGI eNB E-UTRAN NodeB ePDCCH Enhanced Physical Downlink Control Channel E-SMLC Evolved Serving Mobile Location Center E-UTRAN Evolved Universal Terrestrial Radio Access Network FDD Frequency Division Duplex FFS For Further Study gNB Base station in NR GNSS Global Navigation Satellite System HARQ Hybrid Automatic Repeat Request HO Handover HSPA High Speed Packet AccessHRPD High Rate Packet Data LOS Line of Sight LPP LTE Positioning Protocol LTE Long-Term Evolution MAC Medium Access Control MAC Message Authentication Code MBSFN Multimedia Broadcast Multicast Service Single Frequency Network MBSFN ABS MBSFN Almost Blank Subframe MDT Minimization of Drive Tests MIB Master Information Block MIMO Multiple Input Multiple Output MME Mobility Management Entity MSC Mobile Switching Center NPDCCH Narrowband Physical Downlink Control Channel NR New Radio OCNG OFDMA Channel Noise Generator OFDM Orthogonal Frequency Division Multiplexing OFDMA Orthogonal Frequency Division Multiple Access OSS Operations Support System OTDOA Observed Time Difference of Arrival O&M Operation and Maintenance PBCH Physical Broadcast Channel P-CCPCH Primary Common Control Physical Channel PCell Primary Cell PCFICH Physical Control Format Indicator Channel PDCCH Physical Downlink Control Channel PDCP Packet Data Convergence Protocol PDP Power Delay Profile PDSCH Physical Downlink Shared Channel PGW Packet Gateway PHICH Physical Hybrid-ARQ Indicator Channel PLMN Public Land Mobile Network PMI Precoding Matrix Indicator PRACH Physical Random Access Channel PRS Positioning Reference Signal PSS Primary Synchronization Signal PUCCH Physical Uplink Control Channel PUSCH Physical Uplink Shared Channel RACH Random Access Channel QAM Quadrature Amplitude Modulation RAN Radio Access Network RAT Radio Access Technology RLC Radio Link Control RLM Radio Link Monitoring RNC Radio Network Controller RNTI Radio Network Temporary Identifier RRC Radio Resource Control RRM Radio Resource Management RS Reference Signal RSCP Received Signal Code Power RSRP Reference Symbol Received Power ORReference Signal Received Power RSRQ Reference Signal Received Quality OR Reference Symbol Received Quality RSSI Received Signal Strength Indicator RSTD Reference Signal Time Difference SCH Synchronization Channel SCell Secondary Cell SDAP Service Data Adaptation Protocol SDU Service Data Unit SFN System Frame Number SGW Serving Gateway SI System Information SIB System Information Block SNR Signal to Noise Ratio SON Self-Organizing Network SS Synchronization Signal SSS Secondary Synchronization Signal TDD Time Division Duplex TDOA Time Difference of Arrival TOA Time of Arrival TSS Tertiary Synchronization Signal TTI Transmission Time Interval UE User Equipment UL Uplink UMTS Universal Mobile Telecommunications System USIM Universal Subscriber Identity Module UTDOA Uplink Time Difference of Arrival WCDMA Wideband CDMA WLAN Wireless Local Area Network

Claims

CLAIMS 1. A method performed by a User Equipment, UE, the method comprising: receiving (700) a configuration from a network node that provides information; determining (702) mapping between bits in a bitmap and Spatial Domain, SD, basis vectorgroups wherein ^ ≥ 1 bits in the bitmap map to a single SD basis vector group;determining (704) a Precoding Matrix Indicator, PMI, according to the mapping; and reporting (706) PMI to the network node as part of Channel State Information, CSI, reporting to the network node.

2. The method of claim 1 wherein the information is on one or more of the following: a number of antenna ports in one or more dimensions; a number of SD basis vectors per SD basis vector group; a bitmap providing a Codebook Subset Restriction, CBSR; and a bitmap providing scaling factors to be applied for SD basis vectors.

3. The method of any of claims 1-2 where the configuration received includes information on the number of ports ^^in a first dimension, and the number of ports ^^in a second dimension.

4. The method of claim 3 where the number of ports ^^is 1 in which case the port layout isone dimensional wherein ^^ > 1 and ^^ = 1.

5. The method of any of claims 1-4 further comprising: determining the scaling factors to be applied to SD basis vectors when determining the PMI and during Channel Quality Indicator, CQI, determination according to the mapping.

6. The method of any of claims 1-5 wherein reporting the PMI further comprises reporting CQI.

7. The method of any of claims 1-6 where the configuration received by the UE includes information on a number g′^of SD basis vectors in the first dimension per SD basis vector group to be used when determining the scaling factors to be applied to SD basis vectors, and a number g′^of SD basis vectors in the second dimension per SD basis vector group to be used when determining the scaling factors to be applied to SD basis vectors.

8. The method of any of claims 1-7 where in the case ^^ = 1, the number g′^ of SD basisvectors in the second dimension per SD basis vector group is one and information on g′^is not explicitly configured.

9. The method of any of claims 1-7, where the number g′^of SD basis vectors in the first dimension per SD basis vector group correspond to SD basis vectors in the first dimension that are consecutive.

10. The method of any of claims 1-7, where the number g′^of SD basis vectors in the second dimension per SD basis vector group correspond to SD basis vectors in the second dimension that are consecutive.

11. The method of any of claims 1-10 where the configuration received by the UE comprises the bitmap providing scaling factors to be applied for SD basis vectors including information on a bitsequence p %^( %^( %i( %j(C = pC pC ⋯ pC which is the concatenation of the bit sequences pC %k =1, 2, … , l)p%j(C provides the scaling factor value to beSDbasis vectors corresponding to the k-th SD basis vector group, and l = m^⋅n^⋅m.⋅n.oq^⋅oq. is the numberof SD basis vector groups.

12. The method of claim 11, wherein the number of bits in the bit sequence p%j(C is ^ = 3 bits.

13. The method of any of claims 5-12 where the k-th SD basis vector group comprises g^qg^qtwo dimensional DFT vectors: ^{|,",{|,0 , ^{|,"Y^,{|,0 , … ^{|,"Ysq"'^,{|,0 ,^{|,",{|,0Ysq0'^ , ^{|,"Y^,{|,0Ysq0'^ , … ^{|,"Ysq"'^,{|,0Ysq0'^ ,wherein }j,^and }j,^are integers.

14. The method of claim 13, wherein the integers }j,^and }j,^are determined according to at least one of the mapping alternatives: a. }j,^ = Oj,^g′^=^(b.=^(.

15. The method of any of claims 1-14, wherein the scaling factor value provided by the bit sequence p%j(C is applied to the SD basis vectors corresponding to the k-th SD basis vector group when the PMI.

16. The method of any of claims 1-4 further comprising: determining one or more SD basis vectors to be included as part of the PMI according to the mapping using the bitmap providing the CBSR.

17. The method of any of claims 1-6 and 16 where the configuration received by the UE includes information on a number g^of SD basis vectors in the first dimension per SD basis vector group to be used when determining one or more SD basis vectors to be included as part of the PMI according to the mapping using the bitmap providing the CBSR, and a number g^of SD basis vectors in the second dimension per SD basis vector group to be used when determining one or more SD basis vectors to be included as part of the PMI according to the mapping using the bitmap providing the CBSR.

18. The method of any of claims 1-6 and 16-17 where in the case ^^ = 1, the number g^ of SDbasis vectors in the second dimension per SD basis vector group is one and information on g^is not explicitly configured.

19. The method of any of claims 1-6 and 16-18, where the number g^of SD basis vectors in the first dimension per SD basis vector group correspond to SD basis vectors in the first dimension that are consecutive.

20. The method of any of claims 1-6 and 16-18, where the number g^of SD basis vectors in the second dimension per SD basis vector group correspond to SD basis vectors in the second dimension that are consecutive.

21. The method of any of claims 1-6 and 16-20 where the configuration received by the UEincludes information on CBSR bitmap hihi'^hi'^ … h^h^ wherein hj denotes the CBSR bitcorresponding to the kMN SD basis vector group, ^ = 1, and l = m^⋅n^⋅m.⋅n.o^⋅o. is the number of SDbasis vector groups.

22. The method of any of claims 16-21 where the k-th SD basis vector group comprises g^g^two dimensional DFT vectors: ^{|,",{|,0 , ^{|,"Y^,{|,0 , … ^{|,"Ys"'^,{|,0 ,^{|,",{|,0Y^ , ^{|,"Y^,{|,0Y^ , … ^{|,"Ys"'^,{|,0Y^ ,… ^{|,",{|,0Ys0'^ , ^{|,"Y^,{|,0Ys0'^ , … ^{|,"Ys"'^,{|,0Ys0'^ ,wherein }j,^and }j,^are integers.

23. The method of claim 22 where the integers }j,^and }j,^bare determined according to at least one of the mapping alternatives: a. }j,^ = Oj,^g^}j,^ = Oj,^g^^j,^ ^^%k, ^ ^1O = 7 ^g ^(^^(24. The method of any of claims 1-4 and 16-23 wherein determining the one or more SD basis vectors to be included as part of PMI when determining the PMI comprises: only including SD basis vectors belonging to SD basis vector groups for which the corresponding CBSR bits are set to a value of 1from which UE is allowed to include SD basis vectors as part of PMI according to the mapping.

25. The method of any of claims 1-24 wherein 1^and 1^are pre-defined in 3GPP specifications.

26. The method of any of claims 1-24 wherein 1^and 1^are signaled as part of the configuration information.

27. A method performed by a network node, the method comprising: transmitting a configuration, to a User Equipment, UE, that provides information; and receiving, from the UE, a report of PMI as part of CSI reporting.

28. The method of claim 16 wherein the information is on one or more of the following: a number of antenna ports in one or more dimensions; a number of ports per SD basis vector group; a bitmap providing a Codebook Subset Restriction, CBSR; and a bitmap providing scaling factors to be applied for SD basis vectors.

29. The method of any of claims 16-17 wherein receiving the PMI further comprises reporting CQI.

30. The method of any of claims 16-18 wherein the configuration includes information on the number of ports ^^in a first dimension, and the number of ports ^^in a second dimension.

31. The method of claim 19 wherein the number of ports ^^is 1 in which case the port layout isone dimensional wherein ^^ > 1 and ^^ = 1.

32. The method of any of claims 16-20 wherein the configuration includes information on a number g′^of SD basis vectors in the first dimension per SD basis vector group to be used when determining the scaling factors to be applied to SD basis vectors, and a number g′^of SD basis vectors in the second dimension per SD basis vector group to be used when determining the scaling factors to be applied to SD basis vectors.

33. The method of any of claims 16-21 wherein the configuration includes information on CBSRbitmap h MNihi'^hi'^ … h^h^ wherein hj denotes the CBSR bit corresponding to the k SD basisvector group, and l = m^⋅n^⋅m.⋅n.o^⋅o. is the number of SD basis vector groups.

34. The method of any of claims 16-22 wherein the configuration comprises the bitmap providing scaling factors to be applied for SD basis vectors including information on a bit sequencep = p%^(p%^( ⋯ p%i( which is the concatenation of the %j(C C C C bit sequences pC %k = 1, 2, … , l )p%j(C provides the scaling factor value to be applied for SD basis vectorscorresponding to the k-th SD basis vector group, and l = m^⋅n^⋅m.⋅n.oq^⋅oq. is the number of SD basisvector groups.

35. The method of claim 34, wherein the number of bits in the bit sequence p%j(C is ^ = 3 bits.

36. The method of any of claims 16-23 wherein 1^and 1^are pre-defined in 3GPP specifications.

37. The method of any of claims 16-23 wherein 1^and 1^are signaled as part of the configuration information.

38. A User Equipment, UE, (900) comprising processing circuitry (902) and memory (910), the memory (910) comprising instructions to cause the UE (900) to: receive (700) a configuration from a network node that provides information; determine (702) mapping between bits in a bitmap and a Spatial Domain, SD, basis vectorgroups wherein ^ ≥ 1 bits in the bitmap map to a single SD basis vector group;determine (704) a Precoding Matrix Indicator, PMI, according to the mapping; and report (706) PMI to the network node as part of Channel State Information, CSI, reporting to the network node.

39. The UE (900) of claim 26 further comprising instructions to cause the UE (900) to: implement any of the features of claims 2-26.

40. A computer-readable medium comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to any one of claims 1-26.

41. A network node (1000) comprising processing circuitry (1002) and memory (1004), the memory (1004) comprising instructions to cause the network node (1000) to: transmitting a configuration, to a User Equipment, UE, that provides information; and receiving, from the UE, a report of Precoding Matrix Indicator, PMI, as part of Channel State Information, CSI, reporting.

42. The network node (1000) of claim 28 further comprising instructions to cause the network node (1000) to: implement any of the features of claims 28-37.

43. A computer-readable medium comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to any one of claims 27-37.

Images