Reliable CSI feedback for multiple TRPs

Abstract

Systems and methods are provided for reliable channel state information (CSI) feedback for multiple transmission / reception points (TRPs). In some embodiments, a wireless device receives configurations for one or more of a semi-persistent CSI (SP-CSI) report on a PUCCH comprising a first PUCCH resource, an SP-CSI report on a PUSCH comprising a report periodicity and a slot offset, and a periodic CSI report on a PUCCH comprising a second PUCCH resource activated in a third and fourth spatial relationship or uplink TCI state, and the report periodicity and slot offset. The wireless device also receives appropriate activation commands and transmits the SP-CSI in the PUCCH resource, the periodic CSI in the PUCCH resource, and / or the SP-CSI in the PUSCH resource. In this manner, the reliability of the SP-CSI on the PUSCH, or the SP-CSI on the PUCCH, or the periodic CSI on the PUCCH, can be improved by repeating the SP-CSI or periodic CSI across multiple TRPs.

Description

[Technical field]

[0001] [Related Applications] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims the benefit of Provisional Patent Application No. 63 / 118,841, filed November 27, 2020, the disclosure of which is incorporated herein by reference in its entirety.

[0002] [Technical field] This disclosure relates to reliable channel state information (CSI) feedback. [Background technology]

[0003] New Radio (NR) uses cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) in both the downlink (DL) (i.e., from the network node, gNB, or base station to the user equipment or UE) and uplink (UL) (i.e., from the UE to the gNB). Discrete Fourier transform (DFT) spread OFDM is also supported in the uplink. In the time domain, the NR downlink and uplink are organized into equal sized subframes of 1 ms each. The subframes are further divided into multiple slots of equal duration. The slot length depends on the subcarrier spacing. For a subcarrier spacing of Δf=15 kHz, there is only one slot per subframe, and each slot consists of 14 OFDM symbols.

[0004] Data scheduling in NR is typically slot-based, an example is shown in FIG. 1 with a slot of 14 symbols, where the first two symbols contain the Physical Downlink Control Channel (PDCCH) and the rest contain the Physical Shared Data Channel, either the Physical Downlink Shared Channel (PDSCH) or the Physical Uplink Shared Channel (PUSCH).

[0005] In NR, different subcarrier spacing values ​​are supported. The supported subcarrier spacing values ​​(also called different numerologies) are Δf = (15 × 2 μ ) kHz, where μ∈{0,1,2,3,4}. Δf=15 kHz is the basic subcarrier spacing. The slot durations for different subcarrier spacings are 1 / 2 μ is given by ms.

[0006] In the frequency domain, the system bandwidth is divided into resource blocks (RBs), each corresponding to 12 consecutive subcarriers. The RBs are numbered starting with 0 at one end of the system bandwidth. The basic NR physical time-frequency resource grid is shown in Figure 2, where only one resource block (RB) in a 14-symbol slot is shown. One OFDM subcarrier in one OFDM symbol interval forms one resource element (RE).

[0007] In NR, uplink and downlink data transmissions can be dynamically scheduled using various downlink control information (DCI) formats or semi-statically configured by radio resource control (RRC) signaling. DCI is carried on the physical downlink control channel (PDCCH). The UE first decodes the DCI on the PDCCH, and then receives data on a scheduled PDSCH or transmits data via a scheduled PUSCH based on the decoded DCI. The DCI contains all the necessary information, including modulation order, coding rate, resource allocation, etc., for the UE to decode the PDSCH or encode and modulate the PUSCH. For semi-statically configured PUSCH transmission, it is also called a configuration grant (CG).

[0008] There are two PUSCH mapping types supported in NR: Type A and Type B. Type A is usually referred to as slot-based, and Type B is sometimes referred to as non-slot-based or minislot-based. A slot-based transmission typically starts at the first OFDM symbol and uses the entire slot, i.e., all 14 OFDM symbols, or a portion of the slot. A minislot-based PUSCH transmission can be of any length (i.e., number of OFDM symbols) and therefore can start and end at any symbol within the slot. It should be noted that slot or especially minislot transmissions in NR Release 15 (Rel-15) do not cross slot boundaries.

[0009] In NR Release 15, it is possible to schedule a PUSCH with repetition over multiple slots. The number of repetitions is configured by the RRC parameter pusch-AggregationFactor, which can have values ​​of 2, 4, or 8. In this case, the PUSCH is repeated in multiple adjacent slots (if slots are available for the UL) up to the configured number of repetitions. This is also called slot-based PUSCH repetition or PUSCH repetition type A.

[0010] In NR Release 16, PUSCH repetition type A is enhanced, so that the repetition number may instead be indicated dynamically, i.e., may change from one PUSCH scheduling opportunity to the next. The dynamic repetition number is configured as part of the time domain resource allocation (TDRA) for PUSCH. That is, in addition to the starting symbol S and length L of the PUSCH in the slot, some nominal repetition number K may be added to the TDRA. A list of TDRAs may be configured in the UE, and different TDRAs may be configured with different K values. Different repetition numbers may be used by selecting different TDRAs from the list by using the time domain resource allocation field in the DCI signaled from the gNB to the UE. Note that K is the nominal repetition number. Some of these repetitions may not be valid, for example, if the slot is pre-configured as a DL slot, and thus the actual repetition number may be smaller than the indicated value K. Additionally, the maximum number of aggregated slots in Release 16 has been increased to K=16 to account for DL ​​heavy Time Division Duplex (TDD) patterns (i.e., when the majority of slots are DL slots), otherwise the actual number of repetitions would be too small in these cases.

[0011] NR Release 16 also introduces PUSCH repetition type B, where PUSCH may be repeated multiple times within one slot or across two adjacent slots. When scheduling a transmission with PUSCH repetition type B, in addition to the starting symbol S and length L of the PUSCH, a number of nominal repetitions K are also signaled as part of the time domain resource allocation (TDRA) in NR Release 16. The actual number of transmissions may differ from the nominal number of repetitions due to reasons such as collisions with DL symbols. To determine the actual time domain allocation for PUSCH repetition type B, a two-step process is used: 1. Allocate K nominal repetitions, each of length L consecutively (minislots are placed adjacent to each other in time), ignoring slot boundaries and TDD patterns (i.e., ignoring whether a slot is, for example, DL or UL). 2. If a nominal repetition crosses a slot boundary or occupies a symbol not available for UL transmission (e.g., a UL / DL switching point with a TDD pattern), the violating nominal repetition may be split into two or more shorter actual repetitions. If the number of potentially valid symbols for PUSCH repetition type B transmission is greater than zero for a nominal repetition, the nominal repetition consists of one or more actual repetitions, where each actual repetition consists of multiple consecutive valid symbols for PUSCH repetition type B transmission in a slot.

[0012] The physical uplink control channel (PUCCH) is used in NR to carry uplink control information (UCI) such as hybrid automatic repeat request acknowledgement (HARQ-ACK), scheduling request (SR), or channel state information (CSI). There are five PUCCH formats supported in NR, namely PUCCH formats 0 to 4. PUCCH formats 0 and 2 may be one or two OFDM symbols in a slot and are called short PUCCH, while PUCCH formats 1, 3, and 4 may be 4 to 14 OFDM symbols long and are called long PUCCH. PUCCH repetition on adjacent slots is supported in NR for long PUCCH. The number of repetitions of PUCCH can be configured by RRC.

[0013] Defining spatial relationships

[0014] Spatial relationship is used in NR to refer to the relationship between a UL reference signal (RS) to be transmitted, such as a PUCCH / PUSCH DMRS (Demodulation Reference Signal), and another previously transmitted or received RS, which can be either a DL RS (e.g., CSI-RS (Channel State Information RS) or SSB (Synchronization Signal Block)) or a UL RS (i.e., SRS (Sounding Reference Signal)). This is also defined from the UE's perspective.

[0015] When a UE is configured to transmit a UL RS that is configured or indicated as spatially related to a previously received DL RS, it means that the UE should transmit the UL RS in the opposite (reciprocal) direction in which it previously received the DL RS. More precisely, the UE should apply the "same" transmit (Tx) spatial filtering configuration for the transmission of the UL RS as the Rx spatial filtering configuration that it used to receive the previously spatially related DL RS. Here, the term "spatial filtering configuration" may refer to antenna weightings applied at either the transmitter or receiver for data / control transmission / reception. Another way to explain this is that the signal from the UE should be transmitted using the same antenna "beam" as the beam used to receive the previous DL RS signal. The DL RS is also called a spatially filtered reference signal.

[0016] On the other hand, if the first UL RS is spatially related to the second UL RS, the UE should apply the same Tx spatial filtering configuration to the transmission of the first UL RS as the Tx spatial filtering configuration used to transmit the second UL RS previously, in other words, the same beam is used to transmit the first and second UL RSs at two different times, respectively.

[0017] Since a UL RS is associated with a layer of PUSCH or PUCCH transmission (if the UL RS is a DMRS), and the PUSCH / PUCCH is transmitted on the same filter as the associated DMRS, it will be appreciated that the PUSCH / PUCCH is also transmitted on the same TX spatial filter as the associated UL RS.

[0018] The following is an example of a configuration of a spatial relationship for PUCCH, which includes a serving cell ID, a spatial relationship ID, a reference signal, a path loss reference signal, and a power control parameter for PUCCH. TIFF0007604651000001.tif93154

[0019] For PUSCH, the spatial relationship information is included in the DCI for dynamically scheduled PUSCH and is indicated by a Sounding Reference Resource (SRS) Indicator (SRI) configured by higher layer signaling for semi-statically configured PUSCH. The SRI indicates the SRS resource associated with the PUSCH transmission.

[0020] Channel State Information (CSI) and CSI Feedback

[0021] A core component in LTE and NR is support for multiple-input multiple-output (MIMO) antenna configurations using antenna arrays and MIMO-related techniques. Spatial multiplexing is one of the MIMO techniques used to achieve high data rates in good channel conditions.

[0022] r DL symbols For an antenna array with NT antenna ports in a gNB for transmitting TIFF0007604651000002.tif1245, N in RE n R The received signal at the UE with receive antennas may be expressed as: TIFF0007604651000003.tif1147, where TIFF0007604651000004.tif119 is N R is the x 1 received signal vector, TIFF0007604651000005.tif1010 is the N R ×N T is the channel matrix of TIFF0007604651000006.tif99 is the NT×r precoder matrix, TIFF0007604651000007.tif89 is the noise plus interference vector received in the RE by the UE. TIFF0007604651000008.tif99 can be a wideband precoder, i.e., constant over the entire bandwidth part (BWP), or a subband precoder, i.e., constant over each subband.

[0023] The precoder matrix is ​​typically selected from a codebook of possible precoder matrices and is typically indicated by a precoder matrix indicator (PMI) that specifies a unique precoder matrix in the codebook for a given number of symbol streams. Each of the r symbols in s corresponds to a spatial layer, and r is called the transmission rank.

[0024] For a given block error rate (BLER), the modulation level and coding scheme (MCS) are determined by the signal-to-interference-plus-noise ratio (SINR), or channel quality. The precoding matrix, transmission rank, and channel quality are typically part of the channel state information (CSI) measured by the UE and fed back to the network node or gNB.

[0025] Similar to LTE, NR employs an implicit CSI mechanism where the UE feeds back downlink CSI comprising one or more of a transmission rank indicator (RI), a precoder matrix indicator (PMI), and one or two channel quality indicators (CQIs). NR supports transmission of either one or two transport blocks (TBs) to the UE in a slot depending on the rank. One TB is used for ranks 1-4 and two TBs are used for ranks 5-8. A CQI is associated with each TB. CQI / RI / PMI reporting can be either wideband or subband based on the configuration.

[0026] Channel State Information Reference Signal (CSI-RS)

[0027] Similar to LTE, CSI-RS was introduced in NR for channel measurement in the downlink. CSI-RS is transmitted on each transmit antenna port and is used by the UE to measure the downlink channel associated with each antenna port. An antenna port is also referred to as a CSI-RS port. The number of antenna ports supported in NR is {1, 2, 4, 8, 12, 16, 24, 32}. By measuring the received CSI-RS, the UE can estimate the channel that the CSI-RS is traversing, including the radio propagation channel and the antenna gain. CSI-RS for channel measurement purposes is also referred to as non-zero power (NZP) CSI-RS. NZP CSI-RS may be configured to be transmitted in a specific RE within a PRB.

[0028] CSI resource for interference measurement (CSI-IM) is generally used in the NR for the UE to measure noise and interference from other cells. Since the gNB typically does not transmit any signal in the CSI-IM resource, what is observed in the resource is noise and interference from other cells.

[0029] By measuring the channel based on the NZP CSI-RS resource and measuring the interference based on the CSI-IM resource, the UE can estimate the CSI, i.e., RI, PMI, and CQI.

[0030] CSI Report in NR

[0031] In NR, a UE may be configured with one or more CSI reporting configurations, each configured by a higher layer parameter CSI-ReportConfig. Each CSI-ReportConfig is associated with a BWP and includes one or more of the following: CSI resource configuration for channel measurements · CSI-IM resource configuration for interference measurement Reporting configuration type, i.e. aperiodic CSI (on PUSCH), periodic CSI (on PUCCH), or semi-persistent CSI on PUCCH or PUSCH Report volume that specifies report targets such as RI, PMI, CQI, etc. Codebook configurations such as Type I or Type II CSI Frequency domain configuration, i.e. sub-band vs. wideband CQI or PMI, and sub-band size -CQI table to be used

[0032] A UE may be configured with one or more CSI resource configurations for channel measurements and one or more CSI-IM resources for interference measurements. Each CSI resource configuration for channel measurements may include one or more non-zero power (NZP) CSI-RS resource sets. For each NZP CSI-RS resource set, it may further include one or more NZP CSI-RS resources. The NZP CSI-RS resources may be periodic, semi-persistent, or aperiodic.

[0033] Similarly, each CSI-IM resource configuration for interference measurements may include one or more CSI-IM resource sets. For each CSI-IM resource set, it may further include one or more CSI-IM resources. The CSI-IM resources may be periodic, semi-persistent, or aperiodic.

[0034] Semi-persistent (SP) CSI on PUSCH

[0035] The UE performs SP CSI reporting on PUSCH upon successful decoding of DCI format 0_1 ​​or DCI format 0_2 that activates the SP CSI trigger state. DCI format 0_1 ​​and DCI format 0_2 include a CSI request field that indicates the SP CSI trigger state for activating or deactivating reporting. For SP CSI reporting on PUSCH, the set of trigger states is higher layer configured by CSI-SemiPersistentOnPUSCH-TriggerStateList, and the CSI request field in the DCI activates one of the trigger states. Each SP CSI trigger state includes a CSI-ReportConfigId that points to a CSI-ReportConfig with reportConfigType set to semiPersistentOnPUSCH. An example of a SemiPersistentOnPUSCH configuration is shown below, where the semi-persistent CSI (SP-CSI) period is configured by reportSlotConfig to one of the list of 5, 10, 20, 40, 80, 160, and 320 slots and slot offsets, which are indicated in the activation DCI. p0alpha is a power control parameter. TIFF0007604651000009.tif38149

[0036] 3 is an example of SP CSI reporting on the PUSCH, where the first SP CSI report is sent three slots (slot offset) after receiving an activation DCI (SP-CSI activation trigger). SP CSI is reported every five slots (periods) in this example until a deactivation DCI is received (SP-CSI deactivation trigger).

[0037] The codepoints of the CSI request field in the DCI are mapped to the SP-CSI trigger states according to the order of the positions of the configured trigger states in the CSI-SemiPersistentOnPUSCH-TriggerStateList, with codepoint '0' being mapped to the trigger state in the first position.

[0038] The UE shall validate the DL semi-persistent allocation PDCCH on DCI for SP CSI activation or release only if both of the following conditions are met: The Cyclic Redundancy Check (CRC) parity bits of the DCI format are scrambled with the Radio Network Temporary Identifier (RNTI) of the SP-CSI provided by the higher layer parameter sp-CSI-RNTI Special fields for the DCI format are set according to Table 5.2.1.5.2-1 or Table 5.2.1.5.2-2 of 3GPP (registered trademark) technical specification TS38.214.

[0039] If verification is achieved, the UE regards the information in the DCI format as a valid activation or valid release of SP CSI transmission on the PUSCH, and the UE activates or deactivates the CSI reporting configuration indicated by the CSI request field in the DCI. TIFF0007604651000010.tif47148TIFF0007604651000011.tif83143

[0040] It should be noted that the SP CSI reports on the PUSCH activated by the DCI format are not expected to be multiplexed with the uplink data on the PUSCH.

[0041] Semi-persistent (SP) CSI on PUCCH

[0042] For SP CSI reporting on PUCCH, the UE is configured with a CSI reporting configuration where the higher layer parameter reportConfigType is set to semiPersistentOnPUCCH as shown below. TIFF0007604651000012.tif32143

[0043] For SP CSI reporting on PUCCH, the PUCCH resource in each BWP used to transmit the CSI report is configured by PUCCH-CSI-Resource in semiPersistentOnPUCCH. SP CSI reporting on PUCCH is activated (or deactivated) by an activation (or deactivation) command carried on a Medium Access Control (MAC) Control Element (CE), and the MAC CE selects one of the semi-persistent reporting configurations for use by the UE on the PUCCH.

[0044] The MAC CE is shown in Figure 4. It contains the following fields: Serving Cell ID: This field indicates the ID of the serving cell. -BWP ID: This field indicates the UL BWP -S i: indicates the activation / deactivation state of semi-persistent CSI reporting configurations in the list of CSI-ReportConfigs. S0 refers to the reporting configuration with the lowest CSI-ReportConfigId in the list that contains PUCCH resources for SP CSI reporting in the indicated BWP and has type set to semiPersistentOnPUCCH, S1 refers to the reporting configuration with the second lowest CSI-ReportConfigId that contains PUCCH resources for SP CSI reporting in the indicated BWP, etc. i The S field is set to 1 to indicate that the corresponding semi-persistent CSI reporting configuration is activated. i The field is set to 0 to indicate that the corresponding semi-persistent CSI reporting configuration i should be deactivated. -R: Reserved bit, set to 0.

[0045] When the UE transmits a PUCCH with HARQ-ACK information in slot n corresponding to a PDSCH carrying an activation (or deactivation) command, the indicated SP CSI reporting configuration is It will be activated starting from the first slot after TIFF0007604651000013.tif1244, TIFF0007604651000014.tif1230 is the number of slots per subframe, and μ is the subcarrier spacing (SCS) configuration for PUCCH.

[0046] Periodic CSI on PUCCH

[0047] Periodic CSI is always transmitted on the PUCCH. Similar to the SP-CSI on the PUCCH, the PUCCH resources for carrying the periodic CSI are configured in the associated CSI-ReportConfig as shown below, where the PUCCH resources carrying the periodic CSI are configured per BWP. TIFF0007604651000015.tif29143

[0048] Currently, a particular challenge exists: in NR up to Release 16, the problematic repetition is not supported for SP-CSI on PUSCH. The number of transmissions in each reporting period is always assumed to be 1, regardless of the value of the higher layer parameters pusch-AggregationFactor or numberOfRepetitions-r16 configured in the TDRA row indicated by the TDRA field of the DCI activating the SP-CSI. The same applies for periodic CSI and SP-CSI on PUCCH, where a single transmission is always assumed, regardless of whether PUCCH repetition is configured or not.

[0049] Furthermore, in frequency range 2 (FR2), channel blocking is a particular problem that needs to be overcome: if SP-CSI or periodic CSI is transmitted by the UE in a slot when the channel between the UE and the TRP is blocked, the SP CSI or periodic CSI cannot be correctly decoded at the gNB.

[0050] Deploying multiple TRPs is one efficient way to combat channel blocking in a particular FR2. However, in the current SP CSI or periodic CSI reporting in NR, CSI is only transmitted to one TRP by the UE. How to ensure the reliability of SP CSI or periodic CSI in FR2 is an open problem that needs to be solved. Summary of the Invention

[0051] Systems and methods are provided for reliable channel state information (CSI) feedback for multiple transmission / reception points (TRPs). In some embodiments, a wireless device receives configurations for one or more of a semi-persistent CSI (SP-CSI) report on a PUCCH comprising a first PUCCH resource, a SP-CSI report on a PUSCH comprising a report periodicity and a slot offset, and a periodic CSI report on a PUCCH comprising a second PUCCH resource activated with a third and fourth spatial relationship or uplink TCI state, report periodicity, and slot offset. The wireless device also receives appropriate activation commands and transmits the SP-CSI in the PUCCH resource, the periodic CSI in the PUCCH resource, and / or the SP-CSI in the PUSCH resource. In this manner, the reliability of the SP-CSI on the PUSCH, or the SP-CSI on the PUCCH, or the periodic CSI on the PUCCH may be improved by repeating the SP-CSI or the periodic CSI across multiple TRPs.

[0052] Certain aspects of the present disclosure and their embodiments may provide solutions to the above-mentioned or other problems. A method is proposed that allows CSI feedback to be repeated for multiple TRPs for SP-CSI on PUSCH, SP-CSI on PUCCH, and periodic CSI on PUCCH.

[0053] Various embodiments are proposed herein that address one or more of the problems disclosed herein. Particular embodiments may provide one or more of the following technical advantages: The proposed solution improves the reliability of SP-CSI on PUSCH or SP-CSI or periodic CSI on PUCCH by repeating SP-CSI or periodic CSI over multiple TRPs. This solution is particularly beneficial in FR2 scenarios, since at least one TRP can receive SP-CSI or periodic CSI when one of the TRPs is blocked. [Brief description of the drawings]

[0054] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate several aspects of the disclosure and, together with the description, serve to explain the principles of the disclosure.

[0055] [Figure 1] FIG. 1 shows that data scheduling in New Radio (NR) is slot-based, typically with a 14-symbol slot, where the first two symbols contain the Physical Downlink Control Channel (PDCCH) and the rest contain the Physical Shared Data Channel, which is either the Physical Downlink Shared Channel (PDSCH) or the Physical Uplink Shared Channel (PUSCH).

[0056] [Diagram 2] FIG. 2 shows a basic NR physical time-frequency resource grid where only one resource block (RB) in a slot of 14 symbols is shown.

[0057] [Diagram 3] FIG. 3 shows an example of SP CSI reporting on a PUSCH, where the first SP CSI report is sent three slots (slot offset) after receiving an activation DCI (Semi-Persistent CSI (SP-CSI) Activation Trigger).

[0058] [Figure 4] FIG. 4 illustrates a medium access control (MAC) control element (CE) selecting one of the semi-persistent reporting configurations for use by a UE on a PUCCH.

[0059] [Diagram 5] FIG. 5 illustrates an example of a cellular communication system in which embodiments of the present disclosure may be implemented.

[0060] [Figure 6]FIG. 6 illustrates a method performed by a wireless device for reliable CSI feedback according to some embodiments of the present disclosure.

[0061] [Figure 7] FIG. 7 illustrates a method performed by a base station for reliable CSI feedback according to some embodiments of the present disclosure.

[0062] [Figure 8] FIG. 8 illustrates that for PUSCH and PUCCH transmissions directed to multiple TRPs, PUSCH or PUCCH may be repeated for different TRPs according to some embodiments of the disclosure.

[0063] [Figure 9] FIG. 9 illustrates an example in which an SP-CSI report is repeated twice in two slots for two TRPs in each reporting period according to some embodiments of the disclosure.

[0064] [Figure 10] FIG. 10 illustrates an example of embodiment A1 in which a total of four iterations are indicated in TDRA while two SRI (or UL TCI states) are indicated, according to some embodiments of the present disclosure.

[0065] [Figure 11] FIG. 11 illustrates an example in which an SP-CSI report is repeated twice in two minislots for two TRPs in each reporting period according to some embodiments of the disclosure.

[0066] [Figure 12] FIG. 12 illustrates a method performed by a wireless device for reliable CSI feedback according to some embodiments of the present disclosure.

[0067] [Figure 13]FIG. 13 shows an example in which SP-CSI reporting on PUCCH is repeated in two slots for two TRPs in each reporting period.

[0068] [Figure 14] FIG. 14 shows an example in which the first four symbols of an eight-symbol PUCCH carrying SP CSI are sent towards TRP1 and the remainder towards TRP2.

[0069] [Figure 15] FIG. 2 is a schematic block diagram of an exemplary embodiment of a radio access node; [Figure 16] FIG. 2 is a schematic block diagram of an exemplary embodiment of a radio access node; [Figure 17] FIG. 2 is a schematic block diagram of an exemplary embodiment of a radio access node;

[0070] [Figure 18] FIG. 2 is a schematic block diagram of a UE. [Figure 19] FIG. 2 is a schematic block diagram of a UE.

[0071] [Figure 20] FIG. 20 illustrates an exemplary embodiment of a communication system in which embodiments of the present disclosure may be implemented.

[0072] [Figure 21] FIG. 21 illustrates an exemplary embodiment of the host computer, base station, and UE of FIG.

[0073] [Figure 22] 21 is a flow chart illustrating an exemplary embodiment of a method implemented in a communication system such as that of FIG. 20. [Figure 23] 21 is a flow chart illustrating an exemplary embodiment of a method implemented in a communication system such as that of FIG. 20. [Figure 24] 21 is a flow chart illustrating an exemplary embodiment of a method implemented in a communication system such as that of FIG. 20. [Diagram 25] 21 is a flow chart illustrating an exemplary embodiment of a method implemented in a communication system such as that of FIG. 20. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0074] The embodiments described below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode for practicing the embodiments. Upon reading the following description in light of the accompanying drawings, those skilled in the art will understand the concepts of the present disclosure and will recognize applications of these concepts not specifically addressed herein. It is understood that these concepts and applications are within the scope of the present disclosure.

[0075] Wireless Node: As used herein, a "wireless node" is either a wireless access node or a wireless communication device.

[0076] Radio Access Node: As used herein, a "radio access node" or "radio network node" or "radio access network node" is any node in a radio access network (RAN) of a cellular communications network that operates to wirelessly transmit and / or receive signals. Some examples of radio access nodes include, but are not limited to, a base station in a 3GPP® Long Term Evolution (LTE) network (e.g., a New Radio (NR) base station (gNB) or an enhanced or evolved Node B (eNB) in a 3rd Generation Partnership Project (3GPP®) Fifth Generation (5G) NR network), a high power or macro base station, a low power base station (e.g., a micro base station, a pico base station, a Home eNB, etc.), a relay node, a network node that performs part of the functionality of a base station (e.g., a network node that performs a gNB Central Unit (gNB-CU) or a network node that performs a gNB Distributed Unit (gNB-DU)), or a network node that performs part of the functionality of some other type of radio access node.

[0077] Core Network Node: As used herein, a "core network node" is any type of node in a core network or any node that implements a core network function. Some examples of core network nodes include, for example, a Mobility Management Entity (MME), a Packet Data Network Gateway (P-GW), a Service Capability Publication Function (SCEF), a Home Subscriber Server (HSS), etc. Some other examples of core network nodes include nodes that implement an Access and Mobility Management Function (AMF), a User Plane Function (UPF), a Session Management Function (SMF), an Authentication Server Function (AUSF), a Network Slice Selection Function (NSSF), a Network Publication Function (NEF), a Network Function (NF) Repository Function (NRF), a Policy Control Function (PCF), a Unified Data Management (UDM), etc.

[0078] Communication Device: As used herein, a "communication device" is any type of device that has access to an access network. Some examples of communication devices include, but are not limited to, a mobile phone, a smartphone, a sensor device, a meter, a vehicle, a home appliance, a medical device, a media player, a camera, or any type of consumer electronics, such as, but not limited to, a television, a radio, a lighting fixture, a tablet computer, a laptop, or a personal computer (PC). A communication device may be a portable, handheld, computer-embedded, or vehicle-mounted mobile terminal capable of communicating voice and / or data over a wireless or wired connection.

[0079] Wireless Communication Device: One type of communication device is a wireless communication device, which may be any type of wireless device that accesses (i.e., is served by) a wireless network (e.g., a cellular network). Some examples of wireless communication devices include, but are not limited to, user equipment devices (UEs) in 3GPP networks, machine type communication (MTC) devices, and Internet of Things (IoT) devices. Such wireless communication devices may be or may be integrated into mobile phones, smartphones, sensor devices, meters, vehicles, home appliances, medical devices, media players, cameras, or any type of consumer electronics, such as, but not limited to, televisions, radios, lighting fixtures, tablet computers, laptops, or PCs. Wireless communication devices may be portable, handheld, computer-embedded, or vehicle-mounted mobile terminals capable of communicating voice and / or data over a wireless connection.

[0080] Network Node: As used herein, a "network node" is any node that is part of either the RAN or core network of a cellular communications network / system.

[0081] Transmission / Reception Point (TRP): In some embodiments, a TRP can be either a network node or a radio head. A TRP can be represented by a spatial relationship or a TCI state in some embodiments. In some embodiments, a TRP can use multiple TCI states. In some embodiments, each TRP that a UE intends to receive signals transmitted in the UL is represented in the standard document by an SRS Resource Indicator (SRI), a spatial relationship, or a TCI state, e.g., a UL TCI state.

[0082] It should be noted that the description given herein focuses on 3GPP cellular communication systems, and therefore 3GPP terminology or terminology similar to 3GPP terminology is often used, however, the concepts disclosed herein are not limited to 3GPP systems.

[0083] It should be noted that although reference may be made in the description herein to the term "cell," it is important to note that, particularly with respect to 5G NR concepts, beams may be used instead of cells, and thus the concepts described herein are equally applicable to both cells and beams.

[0084] FIG. 5 illustrates an example of a cellular communication system 500 in which embodiments of the present disclosure may be implemented. In the embodiments described herein, the cellular communication system 500 is a 5G system (5GS) including a Next Generation RAN (NG-RAN) and a 5G Core (5GC). In this example, the RAN includes base stations 502-1 and 502-2, which in 5GS include NR base stations (gNBs) and optionally Next Generation eNBs (ng-eNBs) (e.g., LTE RAN nodes connected to 5GC) that control corresponding (macrocell) cells 504-1 and 504-2. The base stations 502-1 and 502-2 are generally referred to herein collectively as base stations 502 and individually as base stations 502. Similarly, the (macrocell) cells 504-1 and 504-2 are generally referred to herein collectively as (macrocell) cells 504 and individually as (macrocell) cells 504. The RAN may also include several low power nodes 506-1-506-4 that control corresponding small cells 508-1-508-4. The low power nodes 506-1-506-4 may be small base stations (such as pico or femto base stations) or remote radio heads (RRHs), etc. Notably, although not shown, one or more of the small cells 508-1-508-4 may alternatively be provided by the base station 502. The low power nodes 506-1-506-4 are generally referred to herein collectively as low power nodes 506 and individually as low power nodes 506. Similarly, the small cells 508-1-508-4 are generally referred to herein collectively as small cells 508 and individually as small cells 508. The cellular communication system 500 also includes a core network 510, referred to as 5GC in 5G systems (5GS). The base station 502 (and optionally the low power node 506 ) is connected to a core network 510 .

[0085] Base station 502 and low power node 506 serve wireless communication devices 512-1 through 512-5 in corresponding cells 504 and 508. Wireless communication devices 512-1 through 512-5 are generally referred to herein collectively as wireless communication devices 512 and individually as wireless communication devices 512. In the following description, wireless communication devices 512 are often UEs, although the disclosure is not limited thereto.

[0086] In the following embodiment, the term TRP is used. However, it should be noted that in the 3GPP standard, the term TRP may not be captured. Instead, each TRP that the UE intends to receive signals transmitted in the UL is represented in the standard document by an SRS resource set, an SRS resource indicator (SRI), a spatial relationship, or a TCI state, such as a UL TCI state.

[0087] A method is proposed that enables repeating CSI feedback for multiple TRPs for semi-persistent CSI (SP-CSI) on PUSCH, SP-CSI on PUCCH, and periodic CSI on PUCCH. A system and method for reliable CSI feedback for multiple TRPs are provided. FIG. 6 illustrates a method performed by a wireless device for reliable CSI feedback. The method includes receiving (step 600) one or more configurations for one or more of: an SP-CSI report on PUCCH including a first PUCCH resource, a reporting periodicity, and / or a slot offset activated in a first and second spatial relationship or uplink TCI state; an SP-CSI report on PUSCH including a reporting periodicity and a slot offset; and a periodic CSI report on PUCCH including a second PUCCH resource, a reporting periodicity and a slot offset activated in a third and fourth spatial relationship or uplink TCI state. The method may also include receiving one or more of an activation command to activate the SP-CSI on the PUCCH and an activation downlink control information (DCI) to activate the SP-CSI on the PUSCH (step 602), where the DCI includes first and second SRS resource indicators (SRIs) and a PUSCH resource. Additionally, the method may include transmitting one or more of: SP-CSI in a first PUCCH resource at a first transmission opportunity according to the first spatial relationship and a second transmission opportunity according to a second spatial relationship activated for the first PUCCH resource; periodic CSI in a second PUCCH resource at a third transmission opportunity according to a third spatial relationship and a fourth transmission opportunity according to a fourth spatial relationship configured for the second PUCCH resource; and SP-CSI in a PUSCH resource at a fifth transmission opportunity according to the first SRI and a sixth transmission opportunity according to the second SRI (step 604).

[0088] 7 shows a method performed by a base station for reliable CSI feedback. The method includes transmitting, to a wireless device (step 700), configurations for one or more of: an SP-CSI report on a PUCCH with a first PUCCH resource, reporting periodicity and / or slot offset activated in a first and second spatial relationship or uplink TCI state, an SP-CSI report on a PUSCH with a reporting periodicity and slot offset, and a periodic CSI report on a PUCCH with a second PUCCH resource, reporting periodicity and slot offset activated in a third and fourth spatial relationship or uplink TCI state.

[0089] The method may also include sending one or more of an activation command to the wireless device to activate SP-CSI on the PUCCH and an activation DCI to activate SP-CSI on the PUSCH (step 702), where the DCI comprises the first and second SRIs and a PUSCH resource.

[0090] The method may also include receiving, from the wireless device, SP-CSI in a first PUCCH resource at a first transmission opportunity according to the first spatial relationship and a second transmission opportunity according to a second spatial relationship activated for the first PUCCH resource, periodic CSI in a second PUCCH resource at a third transmission opportunity according to a third spatial relationship and a fourth transmission opportunity according to a fourth spatial relationship configured for the second PUCCH resource, and SP-CSI in a PUSCH resource at a fifth transmission opportunity according to the first SRI and a sixth transmission opportunity according to the second SRI (step 704).

[0091] The proposed solution improves the reliability of SP-CSI on PUSCH or SP-CSI or periodic CSI on PUCCH by repeating SP-CSI or periodic CSI over multiple TRPs. This solution is particularly beneficial in FR2 scenarios, since at least one TRP can receive SP-CSI or periodic CSI when one of the TRPs is blocked.

[0092] When transmitting PUSCH and PUCCH towards multiple TRPs, the PUSCH or PUCCH can be repeated towards another TRP, but now with the first opportunity transmission towards TRP1 and the second opportunity transmission towards TRP2, as shown in Figure 8. In this case, a more reliable PUSCH or PUCCH transmission can be achieved, for example when the path towards one of the TRPs is blocked by an object in the transmission path, since the PUSCH can reach the second TRP.

[0093] The SRI, spatial relationship, or UL TCI state essentially provides an indicator of the spatial filter or beam that the UE should use to target uplink transmissions towards a given TRP. Furthermore, although the following embodiments are discussed using the SRI and spatial relationship, the embodiments are non-limiting and may be equally applicable when the SRI is replaced by the UL TCI state, DL CSI-RS resource, or TCI state in general. In the following description, CSI reporting in the BWP of the serving cell is considered.

[0094] Essentially, the UE is indicated multiple SRIs {SRI1, SRI2, ...} (or spatial relationships), and for each SP-CSI transmission, a rule is specified to determine which of the SRIs (or spatial relationships) applies to the actual SP-CSI transmission. The simplest rule is that SRI1 (or a first spatial relationship) is used for a first transmission, SRI2 (or a second spatial relationship) is used for a second transmission, etc., where SRI1 indicates a first SRS resource from a first SRS resource set used to transmit a spatial relationship source RS for a PUSCH transmission carrying SP-CSI towards TRP1. SRI2 indicates a second SRS resource from a second SRS resource set used to transmit a spatial relationship source RS for a PUSCH transmission carrying SP-CSI towards TRP1.

[0095] Slot-based SP-CSI repetition in PUSCH for multiple TRPs

[0096] In this embodiment, repetition is configured for PUSCH Type A scheduling, and when more than one SRI (or UL TCI state) is indicated in the DCI activating the SP-CSI report carried on the PUSCH, the SP-CSI is repeated in more than one slot within the SP-CSI reporting period.

[0097] Each repetition within an SP-CSI reporting period is intended to be received by a different TRP, i.e. the transmission is directed to a different TRP. When using a number of repetitions greater than the number of TRPs, the SP-CSI repetitions can cycle between different TRPs.

[0098] An example is shown in Figure 9, where the SP-CSI report is repeated twice in two slots towards the two TRPs in each reporting period. In this example, the SP-CSI reporting period is equal to P slots. The advantage is that if the channel to one TRP is blocked, the SP-CSI can still be received by the other TRP, thus increasing the reliability of the SP-CSI transmission.

[0099] In one embodiment, the number of repetitions that the UE is transmitting in an SP-CSI reporting period is equal to the number of SRIs (or UL TCI states) indicated in the DCI activating the SP-CSI. In other words, the number of repetitions in the SP-CSI reporting period is always assumed to be equal to the number of SRIs indicated via the DCI, regardless of the number of repetitions indicated by the TDRA field in the activation DCI. In this case, the SP-CSI report on the PUSCH is repeated over time for each indicated SRI value. In one example, when two SRIs are indicated to the UE via the activation DCI for SP-CSI on the PUSCH, the UE assumes two repetitions during each SP-CSI reporting period and ignores the number of repetitions indicated by the TDRA field in the activation DCI. In other words, in this embodiment, the number of SRIs indicated in the activation DCI for SP-CSI on the PUSCH overrides the number of repetitions indicated by the TDRA field in the activation DCI.

[0100] In another alternative embodiment, when two or more SRIs are indicated to the UE via the activation DCI for the SP-CSI on the PUSCH, the SP-CSI report on the PUSCH is transmitted using the spatial relationship indicated by one of the SRIs in each SP-CSI periodicity. The SRI used to derive the spatial relationship for the SP-CSI on the PUSCH is cycled through the two or more SRIs indicated to the UE in different SP-CSI periodicities. For example, when two SRIs are indicated to the UE via the activation DCI, the first indicated SRI is used to derive the spatial relationship for the SP-CSI on the PUSCH in the odd SP-CSI periodicity, and the second indicated SRI is used to derive the spatial relationship for the SP-CSI on the PUSCH in the even SP-CSI periodicity.

[0101] In another embodiment, the number of repetitions that the UE is transmitting within the SP-CSI reporting period is determined by both the number of SRIs and the number of repetitions indicated in the activation DCI. The number of repetitions can be semi-statically configured via RRC or dynamically indicated by the DCI. In a preferred example, the number of repetitions is given by an element of the TDRA (Time Domain Resource Allocation) as indicated in the activation DCI. Thus, the content of both these fields in the activation DCI is used together with the specified rules to determine how and how many times the UE should transmit the repeated SP-CSI report.

[0102] In this case, the number of repetitions is configured in a PUSCH TDRA row selected by the TDRA field in the activation DCI. A TDRA table containing multiple rows is provided by RRC signaling to the UE.

[0103] In one embodiment A1, the value indicated by the TDRA row is the total number of transmissions (across all values ​​of SRI) of the SP-CSI during the SP-CSI reporting period. For example, as indicated by the DCI, the number of repetitions configured in the selected TDRA row applies only if more than one SRI is indicated in the DCI. Furthermore, if the number of repetitions is indicated by the TDRA row and is greater than the number of SRIs (or UL TCI states) for which the number of repetitions is indicated, the repetitions may be cycled across the TRP such that at least one of the SRI values ​​is utilized for more than one transmission. In this way, the TRP receives the SP-CSI report more than once during the SP-CSI reporting period.

[0104] In alternative embodiment A2, the value indicated by the TDRA row is the number of transmissions of SP-CSI per SRI value. If the value indicated by the TDRA row is 2 or more, the repetition may be cycled over the TRP such that at least one of the SRI values ​​is utilized for more than one transmission.

[0105] An example of the former embodiment A1 is shown in Figure 10, where a total of four repetitions are shown in the TDRA while two SRIs (or UL TCI states) are shown. The SP-CSI is repeated four times in four slots for two TRPs in a cyclic manner. Alternatively, it may be specified that the order of these transmissions is arranged differently, for example, the first two repetitions in slots n and n+1 may be transmitted towards TRP1 (i.e., associated with the first SRI), and the next two repetitions in slots n+2 and n+3 may be transmitted towards TRP2 (associated with the second SRI).

[0106] In yet another embodiment, the order of transmissions to the different TRPs is configured by the network to the UE, for example using higher layer RRC signaling, e.g., {SRI1, SRI1, SRI2, SRI2, ...} or {SRI1, SRI2, SRI1, SRI2, ....) which may have different advantages depending on whether the blocking probability of the two links is the same or whether the blocking probability of one link is smaller than the other.

[0107] For both embodiments A1 and A2, the same pattern may be repeated during each SP-CSI reporting period.

[0108] Minislot-based SP-CSI repetition on PUSCH for multiple TRPs

[0109] In this embodiment, when PUSCH repetition type B and more than one SRI (or UL TCI state) are indicated in the DCI activating SP-CSI on the PUSCH, the SP-CSI is repeated in two or more minislots in the SP-CSI reporting period, where a minislot contains several OFDM symbols and is the same as the nominal repetition with a starting symbol and length. Each repetition is toward a different TRP. An example is shown in Figure 11, where the SP-CSI report is repeated twice in two minislots toward two TRPs in each reporting period.

[0110] Similar to PUSCH repetition type A, in one embodiment, the repetition number may be equal to the number of SRIs (or UL TCI Fstate) indicated in the DCI activating the SP-CSI. In another embodiment, the repetition number may be determined by both the number of SRIs and the repetition number configured in the PUSCH TDRA row selected by the TDRA field in the activating DCI. The embodiments A1 and A2 in the previous section on how to use the TDRA row and the DCI field of the SRI to determine the repetition apply equally well to the SP-CSI on the PUSCH with PUSCH repetition type B. In one example, the repetition number configured in the selected TDRA row applies only if more than one SRI is indicated in the DCI.

[0111] SP CSI may be transmitted in a nominal repetition opportunity only if it is the same as the actual repetition opportunity, i.e., if the nominal repetition is not segmented or omitted.

[0112] In some embodiments, when SP CSI on the PUSCH is transmitted towards different TRPs, two different sets of power control parameters may be provided to the UE, so that each of the sets of power control parameters may be used by the UE when transmitting to each of the TRPs. The two different sets of power control parameters may be provided as part of the CSI-ReportConfig information element in 3GPP TS 38.331. An example of this embodiment is shown below, where p0alphaList provides up to two sets of power control parameters. TIFF0007604651000016.tif40147

[0113] 12 illustrates a method performed by a wireless device for reliable CSI feedback according to some embodiments of the present disclosure. The wireless device receives a configuration for SP-CSI reporting on a PUSCH comprising a reporting period and a slot offset (step 1200). The wireless device receives an activation DCI to activate the SP-CSI on the PUSCH, the DCI comprising a first and second SRI and a PUSCH resource (step 1202). The wireless device transmits the SP-CSI on the PUSCH resource at the fifth transmission opportunity according to the first SRI and transmits the SP-CSI at the sixth transmission opportunity according to the second SRI (step 1204).

[0114] SP-CSI Repetition on PUCCH for Multiple TRPs

[0115] Similar to SP CSI on PUSCH, when PUCCH resources for SP CSI on PUCCH are activated with more than one spatial relationship (or UL TCI state), the SP-CSI is repeated in more than one slot in the SP-CSI reporting period. Each repetition is toward a different TRP on the same PUCCH resource. Each TRP is associated with a spatial relationship or UL TCI state. An example is shown in FIG. 13, where the SP-CSI report is repeated in two slots toward two TRPs in each reporting period. In this example, the SP-CSI reporting period is equal to P slots. The activation of more than one spatial relationship (or UL TCI state) for PUCCH resources used for SP-CSI reporting is achieved via a MAC CE that is separate from the MAC CE that activates the SP-CSI report on the PUCCH. The advantage of using different MAC CEs for activating SP-CSI reporting on the PUCCH and for activating two or more spatial relationships (or UL TCI states) for PUCCH resources is that it allows independent control of when to activate SP-CSI reporting on the PUCCH and for which TRP the SP-CSI is transmitted.

[0116] In one embodiment, the number of repetitions is equal to the number of activated spatial relationships or UL TCI states, while in another embodiment, the number of repetitions may be explicitly configured in the associated PUCCH resource.

[0117] As an example, the PUCCH resource configuration may be enhanced as shown below to provide multi-TRP indication (via SpatialRelationList) and the number of repetitions for this PUCCH resource (via NrRepetitions). TIFF0007604651000017.tif119149

[0118] Alternatively, when two or more PUCCH resources, each with an associated spatial relationship or UL TCI state, are configured for SP CSI on the PUCCH in the BWP, the SP-CSI is repeated in two or more slots within the SP-CSI reporting period, with each repetition going to a different TRP associated with one of the two or more spatial relationships or UL TCI states. The number of repetitions is equal to the number of PUCCH resources.

[0119] In yet another embodiment, instead of repetition in different slots, the SP CSI repetition may be within a slot, i.e., intra-slot repetition.

[0120] In a further embodiment, instead of intra-slot repetition, the SP CSI may be hopped between TRPs in a slot where some PUCCH symbols carrying the SP CSI are transmitted on one TRP and the remaining symbols are transmitted on a different TRP. An example is shown in Figure 14 where the first 4 symbols of an 8-symbol PUCCH carrying the SP CSI are transmitted towards TRP1 and the remaining are transmitted to TRP2.

[0121] Other activation and deactivation mechanisms for SP-CSI on PUCCH

[0122] In the above description, it is assumed that the DCI based activation and deactivation mechanism for SP-CSI on PUSCH is a UE specific DCI scheduling PUSCH (aka UL DCI), e.g. DCI formats 0_1 and 0_2. For SP-CSI on PUCCH, activation and deactivation is via MAC CE mechanism.

[0123] Alternatively or additionally, other DCI-based activation and deactivation mechanisms may be used, as described below.

[0124] DL DCI

[0125] In one embodiment, the activation mechanism is a UE-specific DCI that schedules the PDSCH (aka DL DCI), e.g., DCI formats 1_1 and 1_2. The DL DCI is not on the PUSCH, but can trigger an SP-CSI report on the PUCCH. To indicate that a DL DCI is transmitted for activation of the SP-CSI report, the CRC parity bits of the DCI format are scrambled with the SP-CSI-RNTI. PUCCH resources for SP-CSI can be provided in a number of ways. · In one method, the PUCCH resource is provided by the PUCCH Resource Indicator (PRI) field of the DCI, and the activating DL DCI does not schedule the PDSCH. Alternatively, the PUCCH resources are given by the RRC parameter semiPersistentOnPUCCH. The "CSI Request" field must be provided in DCI format. In one method, a new “CSI Request” field is added to the DL DCI format, which the gNB uses to select the SP-CSI trigger state. The codepoints of the CSI Request field in the DCI are mapped to the SP-CSI trigger states according to the order of the positions of the configured trigger states in the CSI-SemiPersistentOnPUSCH-TriggerStateList, with codepoint “0” mapping to the trigger state in the first position. Alternatively, the "CSI Request" field is not introduced as a new field. Rather, an existing field is reused as the "CSI Request" field. For example, the "SRS Request" field is repurposed as the "CSI Request" field. The 'antenna port' field in the DL DCI may be used to provide information for SP-CSI repetition across multiple TRPs. If the 'Antenna Port' field has a size of 0 bits, SP-CSI is transmitted on only a single TRP, e.g. TRP#0. If the 'antenna port' field has a size of 4 bits or more, the bits may provide information about the SP-CSI repetition and / or the cyclic TRP pattern, e.g., 2 bits are used to indicate the number of SP-CSI repetitions and 2 bits are used to indicate the first TRP and the TRP sequence to realize the cyclic TRP pattern. For example, use 2 bits to select one of four possible values ​​for the SP-CSI repetition number {1,2,4,8}. For example, given two TRPs: {{0,1}, {1,0}, {0,0,1,1}, {1,1,0,0}}, two bits are used to select one of four possible sequences to cycle through the TRP. For example, if the TRP sequence {1,0} is selected for 8 repetitions, the TRP used for SP-CSI transmission is 1,0,1,0.

[0126] The deactivation mechanism may also be a UE-specific DCI in which the CRC parity bits of DCI format 1_0, 1_1, or 1_2 are scrambled with the SP-CSI-RNTI.

[0127] When activating and deactivating using the DL DCI, special field values ​​in the DCI are used to verify the SP-CSI activation and deactivation. As an example, the fields shown in Table 1 may be used to verify activation and the fields shown in Table 2 may be used to verify deactivation. TIFF0007604651000018.tif54151TIFF0007604651000019.tif75148

[0128] Group Common DCI

[0129] In another embodiment, a group-common DCI may be used to activate and / or deactivate SP-CSI on the PUCCH.

[0130] For example, a modified DCI format 2_3 or a new DCI format (e.g., DCI format 2_7) may be used for SP-CSI activation / deactivation. To indicate that DL DCI is sent for SP-CSI report activation / deactivation, the CRC parity bits of the DCI format are scrambled with the corresponding group-common RNTI, e.g., the TPC-SRS-RNTI of DCI format 2_3.

[0131] The DCI can carry an SP-CSI field for each UE, where the SP-CSI consists of one or more bits. For example, four bits {S0, S1, S2, S3} are sent to the UE for activation / deactivation of the SP-CSI in the same BWP of the same serving cell where the DCI is sent. i(i=0, 1, 2, 3) indicates the activation / deactivation state of the semi-persistent CSI reporting configuration in the list of CSI-ReportConfigs. S0 points to the reporting configuration with the lowest CSI-ReportConfigId in the list that contains PUCCH resources for SP CSI reporting in the indicated BWP and has type set to semiPersistentOnPUCCH, S1 to the reporting configuration with the second lowest CSI-ReportConfigId that contains PUCCH resources for SP CSI reporting in the indicated BWP, etc. i S is set to 1 to indicate that the corresponding semi-persistent CSI reporting configuration is activated. i is set to 0 to indicate that the corresponding semi-persistent CSI reporting configuration i should be deactivated.

[0132] Activation and deactivation mechanisms for supporting P-CSI on PUCCH

[0133] Some of the embodiments covered above for SP-CSI on PUCCH can also be extended to P-CSI on PUCCH. In this case, when the PUCCH resource for P-CSI on PUCCH is configured with two or more spatial relations (or UL TCI states), the P-CSI is repeated in two or more slots in the P-CSI reporting period. Each repetition is towards a different TRP on the same PUCCH resource. Each TRP is associated with a spatial relation or UL TCI state. The example of Figure 13 is equally valid in this case, where the SP-CSI in the figure is replaced by P-CSI. In this example, the P-CSI report is repeated in two slots towards two TRPs in each reporting period. In this example, the P-CSI reporting period is equal to P slots. The activation of two or more spatial relations (or UL TCI states) for the PUCCH resource used for P-CSI reporting is achieved via the MAC CE. Here, one difference from the case of SP-CSI on PUCCH is that since the CSI is periodic, there is no MAC CE to activate the CSI reporting on PUCCH (i.e., the CSI reporting on PUCCH is periodic).

[0134] In one embodiment, the repetition number is equal to the number of spatial relationships or UL TCI states activated for the PUCCH resource carrying the P-CSI, while in another embodiment, the repetition number may be explicitly configured in the associated PUCCH resource.

[0135] In another embodiment, when two or more spatial relationships (or UL TCI states) are activated for a PUCCH resource carrying P-CSI, the P-CSI report on the PUCCH is transmitted using one of the activated spatial relationships (or UL TCI states) at each P-CSI periodicity. The spatial relationship (or UL TCI state) used for the P-CSI on the PUCCH is cycled through the two or more spatial relationships (or UL TCI states) indicated to the UE in different P-CSI periods. For example, when two spatial relationships (or two UL TCI states) are activated, the first activated spatial relationship (or UL TCI state) is used for the P-CSI during odd SP-CSI periods, and the second activated spatial relationship (or UL TCI state) is used for the P-CSI during even P-CSI periods.

[0136] FIG. 15 is a schematic block diagram of a radio access node 1500 according to some embodiments of the present disclosure. Optional functionality is represented by dashed boxes. The radio access node 1500 may be, for example, a base station 502 or 506 or a network node that implements all or a portion of the functionality of a base station 502 or gNB described herein. As shown, the radio access node 1500 includes a control system 1502 including one or more processors 1504 (e.g., a CPU (Central Processing Unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), etc.), a memory 1506, and a network interface 1508. The one or more processors 1504 are also referred to herein as processing circuits. Additionally, the radio access node 1500 may include one or more radio units 1510, each including one or more transmitters 1512 and one or more receivers 1514 coupled to one or more antennas 1516. The radio units 1510 may be referred to as or be part of a radio interface circuit. In some embodiments, the radio unit 1510 is external to the control system 1502 and is connected to the control system 1502, for example, via a wired connection (e.g., an optical cable). However, in some other embodiments, the radio unit 1510 and potentially the antenna 1516 are integrated with the control system 1502. The one or more processors 1504 operate to provide one or more functions of the wireless access node 1500, as described herein. In some embodiments, the functions are implemented in software, for example, stored in the memory 1506 and executed by the one or more processors 1504.

[0137] 16 is a schematic block diagram illustrating a virtualized embodiment of a radio access node 1500 according to some embodiments of the present disclosure. This description is equally applicable to other types of network nodes. Furthermore, other types of network nodes may have a similar virtualization architecture. Again, optional features are represented by dashed boxes.

[0138] As used herein, a "virtualized" radio access node is an implementation of a radio access node 1500 in which at least a portion of the functionality of the radio access node 1500 is implemented as a virtual component(s) (e.g., via virtual machine(s) running on a physical processing node(s) in a network. As shown, in this example, the radio access node 1500 may include a control system 1502 and / or one or more radio units 1510, as described above. The control system 1502 may be connected to the radio units 1510, for example, via optical cables or the like. The radio access node 1500 includes one or more processing nodes 1600 coupled to or included as part of a network 1602. If present, the control system 1502 or radio units are connected to the processing nodes 1600 via the network 1602. Each processing node 1600 includes one or more processors 1604 (e.g., CPU, ASIC, FPGA, etc.), memory 1606, and a network interface 1608.

[0139] In this example, the functions 1610 of the radio access node 1500 described herein are implemented in one or more processing nodes 1600 or distributed across one or more processing nodes 1600 and the control system 1502 and / or radio unit 1510 in any desired manner. In some particular embodiments, some or all of the functions 1610 of the radio access node 1500 described herein are implemented as virtual components executed by one or more virtual machines implemented in a virtual environment hosted by the processing node 1600. As will be appreciated by those skilled in the art, additional signaling or communication between the processing node 1600 and the control system 1502 is used to perform at least some of the desired functions 1610. Notably, in some embodiments the control system 1502 may not be included, in which case the radio unit 1510 communicates directly with the processing node 1600 via an appropriate network interface.

[0140] In some embodiments, a computer program is provided that includes instructions that, when executed by at least one processor, cause the at least one processor to perform functions of the radio access node 1500 or a node (e.g., processing node 1600) implementing one or more of the functions 1610 of the radio access node 1500 in a virtual environment according to any of the embodiments described herein. In some embodiments, a carrier is provided that includes the aforementioned computer program product. The carrier is one of an electrical signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as a memory).

[0141] 17 is a schematic block diagram of a radio access node 1500 according to some other embodiments of the present disclosure. The radio access node 1500 includes one or more modules 1700, each implemented in software. The modules 1700 provide the functionality of the radio access node 1500 described herein. This description is equally applicable to the processing node 1600 of FIG. 16, where the modules 1700 may be implemented in one of the processing nodes 1600, or may be distributed across multiple processing nodes 1600, and / or may be distributed across the processing nodes 1600 and the control system 1502.

[0142] FIG. 18 is a schematic block diagram of a wireless communication device 1800 according to some embodiments of the present disclosure. As shown, the wireless communication device 1800 includes one or more processors 1802 (e.g., CPU, ASIC, FPGA, etc.), memory 1804, and one or more transceivers (transceivers) 1806, each including one or more transmitters 1808 and one or more receivers 1810 coupled to one or more antennas 1812. The transceiver 1806 includes a radio front-end circuit connected to the antenna 1812 configured to condition signals communicated between the antenna 1812 and the processor 1802, as will be understood by those skilled in the art. The processor 1802 may also be referred to herein as a processing circuit. The transceiver 1806 may also be referred to herein as a radio circuit. In some embodiments, the functionality of the wireless communication device 1800 described above may be implemented fully or partially in software, for example, stored in the memory 1804 and executed by the processor(s) 1802. It should be noted that the wireless communication device 1800 may include additional components not shown in FIG. 18 , such as, for example, one or more user interface components (e.g., input / output interfaces including a display, buttons, a touch screen, a microphone, a speaker, etc., and / or any other components for enabling input of information into and / or output of information from the wireless communication device 1800, a power supply (e.g., a battery and associated power circuitry), etc.

[0143] In some embodiments, a computer program is provided that includes instructions that, when executed by at least one processor, cause the at least one processor to perform the functions of the wireless communication device 1800 according to any of the embodiments described herein. In some embodiments, a carrier is provided that includes the aforementioned computer program product. The carrier is one of an electrical signal, an optical signal, a radio signal, or a computer-readable storage medium (e.g., a non-transitory computer-readable medium such as a memory).

[0144] 19 is a schematic block diagram of a wireless communication device 1800 according to some other embodiments of the present disclosure. The wireless communication device 1800 includes one or more modules 1900, each implemented in software. The modules 1900 provide the functionality of the wireless communication device 1800 described herein.

[0145] Referring to Figure 20, according to one embodiment, a communication system includes a telecommunications network 2000, such as a 3GPP type cellular network, comprising an access network 2002, such as a RAN, and a core network 2004. The access network 2002 comprises a number of base stations 2006A, 2006B, 2006C, such as Node Bs, eNBs, gNBs, or other types of wireless access points (APs), each defining a corresponding coverage area 2008A, 2008B, 2008C. Each base station 2006A, 2006B, 2006C can be connected to the core network 2004 via a wired or wireless connection 2010. A first UE 2012 located in the coverage area 2008C is configured to wirelessly connect to or be paged by the corresponding base station 2006C. A second UE 2014 in the coverage area 2008A can be wirelessly connected to the corresponding base station 2006A. Although multiple UEs 2012, 2014 are shown in this example, the disclosed embodiments are equally applicable to situations where only one UE is within the coverage area or is connected to a corresponding base station 2006.

[0146] The telecommunications network 2000 is itself connected to a host computer 2016, which may be embodied in hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or as processing resources in a server farm. The host computer 2016 may be under the ownership or control of a service provider, or may be operated by or on behalf of the service provider. The connections 2018 and 2020 between the telecommunications network 2000 and the host computer 2016 may extend directly from the core network 2004 to the host computer 2016, or may go through an optional intermediate network 2022. The intermediate network 2022 may be one of a public, private, or hosted network, or a combination of two or more of them, and the intermediate network 2022, if any, may be a backbone network or the Internet, and in particular, the intermediate network 2022 may comprise two or more sub-networks (not shown).

[0147] The communication system of FIG. 20 generally enables connectivity between the connected UEs 2012, 2014 and the host computer 2016. The connectivity may be described as an Over-the-Top (OTT) connection 2024. The host computer 2016 and the connected UEs 2012, 2014 are configured to communicate data and / or signaling over the OTT connection 2024 using the access network 2002, the core network 2004, any intermediate networks 2022, and possible further infrastructure (not shown) as intermediaries. The OTT connection 2024 may be transparent in the sense that the participating communication devices through which the OTT connection 2024 passes are unaware of the routing of the uplink and downlink communications. For example, the base station 2006 does not need to be informed or be informed of the past routing of incoming downlink communications with data originating from the host computer 2016 to be forwarded (e.g., handed over) to the connected UE 2012. Similarly, the base station 2006 does not need to be aware of the future routing of outgoing uplink communications from the UE 2012 to the host computer 2016 .

[0148] An exemplary embodiment according to the embodiment of the UE, base station and host computer discussed in the previous paragraph will now be described with reference to FIG. 21. In the communication system 2100, the host computer 2102 comprises hardware 2104 including a communication interface 2106 configured to set up and maintain wired or wireless connections with interfaces of different communication devices of the communication system 2100. The host computer 2102 further comprises a processing circuit 2108 that may have storage and / or processing capabilities. In particular, the processing circuit 2108 may comprise one or more programmable processors, ASICs, FPGAs, or combinations thereof (not shown) adapted to execute instructions. The host computer 2102 further comprises software 2110 stored in or accessible by the host computer 2102 and executable by the processing circuit 2108. The software 2110 includes a host application 2112. The host application 2112 may be operable to provide services to remote users, such as the UE 2114 connecting via an OTT connection 2116 that terminates at the UE 2114 and the host computer 2102. In providing services to the remote users, the host application 2112 may provide user data that is transmitted using the OTT connection 2116.

[0149] The communication system 2100 further includes a base station 2118 provided within the telecommunications system and equipped with hardware 2120 enabling communication with the host computer 2102 and the UE 2114. The hardware 2120 may include a communication interface 2122 for setting up and maintaining wired or wireless connections with interfaces of different communication devices of the communication system 2100, and a wireless interface 2124 for setting up and maintaining at least a wireless connection 2126 with a UE 2114 located in a coverage area (not shown in FIG. 21) served by the base station 2118. The communication interface 2122 may be configured to facilitate a connection 2128 to the host computer 2102. The connection 2128 may be direct or may pass through a core network (not shown in FIG. 21) of the telecommunications system and / or one or more intermediate networks outside the telecommunications system. In the illustrated embodiment, the hardware 2120 of the base station 2118 further includes processing circuitry 2130, which may comprise one or more programmable processors, ASICs, FPGAs, or combinations thereof (not shown) adapted to execute instructions. The base station 2118 further has software 2132 stored internally or accessible via an external connection.

[0150] The communication system 2100 further includes the UE 2114, already referenced. The hardware 2134 of the UE 2114 may include a wireless interface 2136 configured to set up and maintain a wireless connection 2126 with a base station serving a coverage area in which the UE 2114 is currently located. The hardware 2134 of the UE 2114 further includes a processing circuit 2138, which may comprise one or more programmable processors, ASICs, FPGAs, or combinations thereof (not shown) adapted to execute instructions. The UE 2114 further includes software 2140 stored in or accessible by the UE 2114 and executable by the processing circuit 2138. The software 2140 includes a client application 2142. The client application 2142 may be operable to provide services to a human or non-human user via the UE 2114 with the support of the host computer 2102. At the host computer 2102, an executing host application 2112 can communicate with an executing client application 2142 via an OTT connection 2116 that terminates at the UE 2114 and the host computer 2102. In providing services to a user, the client application 2142 can receive request data from the host application 2112 and provide user data in response to the request data. The OTT connection 2116 can transport both the request data and the user data. The client application 2142 can interact with the user to generate the user data that it provides.

[0151] It should be noted that the host computer 2102, base station 2118, and UE 2114 shown in Figure 21 may be similar to or identical to the host computer 2016, one of the base stations 2006A, 2006B, and 2006C, and one of the UEs 2012 and 2014, respectively, of Figure 20. That is, the internal operation of these entities is as shown in Figure 21, and independently, the surrounding network topology may be that of Figure 20.

[0152] 21, the OTT connection 2116 is depicted abstractly to show communication between the host computer 2102 and the UE 2114 via the base station 2118 and the precise routing of messages through these devices without explicitly referencing any intermediate devices. The network infrastructure can determine the routing, which can be configured to be hidden from the UE 2114, or from the service provider operating the host computer 2102, or both. The network infrastructure can further decide to dynamically change the routing while the OTT connection 2116 is active (e.g., based on load balancing considerations or network reconfiguration).

[0153] The wireless connection 2126 between the UE 2114 and the base station 2118 follows the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of the OTT service provided to the UE 2114 using the OTT connection 2116 of which the wireless connection 2126 forms the last segment. More precisely, the teachings of these embodiments may improve, for example, data rates, latency, power consumption, etc., thereby providing advantages such as, for example, reduced user latency, relaxed file size limitations, better responsiveness, extended battery life, etc.

[0154] Measurement procedures may be provided for the purpose of monitoring data rates, latency, and other factors that one or more embodiments improve. There may further be an optional network function to reconfigure the OTT connection 2116 between the host computer 2102 and the UE 2114 in response to fluctuations in the measurement results. The measurement procedures and / or network functions to reconfigure the OTT connection 2116 may be implemented in the software 2110 and hardware 2104 of the host computer 2102, or in the software 2140 and hardware 2134 of the UE 2114, or both. In some embodiments, sensors (not shown) may be deployed in or associated with the communication devices through which the OTT connection 2116 passes, and the sensors may participate in the measurement procedures by providing values ​​of the monitored quantities exemplified above, or by providing values ​​of other physical quantities from which the software 2110, 2140 can calculate or estimate the monitored quantities. Reconfiguration of the OTT connection 2116 may include message formats, retransmission settings, preferred routing, etc., and the reconfiguration need not affect the base station 2118 and may be unknown or imperceptible to the base station 2118. Such procedures and functions are known in the art and may be practiced. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of the host computer 2102 throughput, propagation time, latency, etc. Measurements may be implemented in that the OTT connection 2116 is used to send messages, particularly empty or "dummy" messages, while the software 2110 and 2140 monitors propagation times, errors, etc.

[0155] FIG. 22 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIG. 20 and FIG. 21. To simplify the disclosure, only drawing references to FIG. 22 are included in this section. In step 2200, the host computer provides user data. In sub-step 2202 (which may be optional) of step 2200, the host computer provides the user data by executing a host application. In step 2204, the host computer initiates a transmission carrying the user data to the UE. In step 2206 (which may be optional), the base station transmits the user data carried in the host computer initiated transmission to the UE according to the teachings of the embodiments described throughout this disclosure. In step 2208 (which may be optional), the UE executes a client application associated with the host application executed by the host computer.

[0156] FIG. 23 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIG. 20 and FIG. 21. To simplify the disclosure, only drawing references to FIG. 23 are included in this section. In step 2300 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides the user data by executing a host application. In step 2302, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass through a base station in accordance with the teachings of the embodiments described throughout this disclosure. In step 2304 (which may be optional), the UE receives the user data carried in the transmission.

[0157] FIG. 24 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIG. 20 and FIG. 21. To simplify this disclosure, only drawing references to FIG. 24 are included in this section. In step 2400 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 2402, the UE provides user data. In sub-step 2404 (which may be optional) of step 2400, the UE provides the user data by executing a client application. In sub-step 2406 (which may be optional) of step 2402, the UE executes a client application that provides the user data in response to the received input data provided by the host computer. In providing the user data, the executed client application may further take into account user input received from a user. Regardless of the particular manner in which the user data is provided, the UE begins transmitting the user data to the host computer in sub-step 2408 (which may be optional). In method step 2410, the host computer receives user data transmitted from the UE according to the teachings of the embodiments described throughout this disclosure.

[0158] FIG. 25 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIG. 20 and FIG. 21. To simplify this disclosure, only a drawing reference to FIG. 25 is included in this section. In step 2500 (which may be optional), the base station receives user data from the UE according to the teachings of the embodiments described throughout this disclosure. In step 2502 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 2504 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0159] Any suitable step, method, feature, function, or benefit disclosed herein may be performed through one or more functional units or modules of one or more virtual devices. Each virtual device may comprise several of these functional units. These functional units may be implemented through one or more microprocessors or microcontrollers, logic processing circuits, as well as logic and other digital hardware such as digital signal processors (DSPs), dedicated digital logic, and the like. The processing circuits may be configured to execute program codes stored in memory, which may include one or several types of memory such as read-only memory (ROM), random access memory (RAM), cache memory, flash memory devices, optical storage devices, and the like. The program codes stored in memory include program instructions for executing one or more telecommunication and / or data communication protocols and instructions for executing one or more of the techniques described herein. In some implementations, the processing circuits may be used to cause the respective functional units to perform corresponding functions according to one or more embodiments of the present disclosure.

[0160] Although the processes in the figures may indicate a particular order of operations performed by some embodiments of the present disclosure, it should be understood that such orders are exemplary (e.g., alternative embodiments may perform operations in a different order, combine some operations, overlap some operations, etc.).

[0161] Embodiment

[0162] Group A Embodiments

[0163] (Embodiment 1) A method performed by a wireless device for reliable channel state information (CSI) feedback, comprising: receiving (600) a configuration for one or more of: i. a semi-persistent CSI (SP-CSI) report on a physical uplink control channel (PUCCH) including a first PUCCH resource, report periodicity, and / or slot offset activated in a first and second spatial relationship or uplink transmission configuration indicator (TCI) state; ii. a SP-CSI report on a physical uplink shared channel (PUSCH) with the report periodicity and slot offset; and iii. a periodic CSI report on the PUCCH with a second PUCCH resource, report periodicity, and slot offset activated in a third and fourth spatial relationship or uplink TCI state; and receiving (602) an activation command for activating the SP-CSI on the PUCCH; and ii. receiving (604) one or more of an activation downlink control information (DCI) activating SP-CSI on the PUSCH, the DCI comprising first and second SRS resource indicators (SRIs) and a PUSCH resource; and transmitting (604) including one or more of: i. SP-CSI on the first PUCCH resource in a first transmission opportunity according to a first spatial relationship and a second transmission opportunity according to a second spatial relationship activated for the first PUCCH resource; ii. periodic CSI on the second PUCCH resource in a third transmission according to a third spatial relationship and a fourth transmission according to a fourth spatial relationship configured for the second PUCCH resource; and iii. SP-CSI on the PUSCH resource in a fifth transmission opportunity according to the first SRI and a sixth transmission opportunity according to the second SRI.

[0164] (Embodiment 2) The method of any of the preceding embodiments, wherein the transmitting is to a radio network node comprising a plurality of transmit / receive points (TRPs), each associated with a spatial relationship or SRI.

[0165] (Embodiment 3) The method according to any of the preceding embodiments, wherein each transmission opportunity is in either a slot or a minislot that includes several OFDM symbols within the slot.

[0166] (Embodiment 4) The method according to any of the preceding embodiments, in which the first transmission opportunity and the second transmission opportunity are in two adjacent slots or minislots in each reporting period for SP-CSI on the PUCCH.

[0167] (Embodiment 5) The method according to any of the preceding embodiments, in which the third transmission opportunity and the fourth transmission opportunity are in two adjacent slots or minislots in each reporting period for P-CSI on the PUCCH.

[0168] (Embodiment 6) The method according to any of the preceding embodiments, in which the fifth and sixth transmission opportunities are within two adjacent slots or minislots for SP-CSI on the PUSCH.

[0169] (Embodiment 7) The method according to any of the preceding embodiments, wherein the activation command may be one of a MAC CE and a DL DCI.

[0170] (Embodiment 8) The method of any of the preceding embodiments, further comprising: transmitting a first CSI in a first slot or minislot in a first reporting period according to a first spatial relationship or SRI; and transmitting a second CSI in a second slot or minislot in a second reporting period according to a second spatial relationship or SRI.

[0171] (Embodiment 9) A method according to any of the preceding embodiments, wherein each of the first to fourth spatial relationships comprises a reference signal (RS) that defines a transmit spatial filter and a set of power control parameters for an associated PUCCH.

[0172] (Embodiment 10) The method according to any of the preceding embodiments, wherein each of the first and second SRIs indicates an SRS resource having a number of antenna ports on which the PUSCH is transmitted and a set of power control parameters for the PUSCH.

[0173] (Embodiment 11) The method of any of the preceding embodiments, wherein configuring an SP-CSI report on the PUSCH further comprises configuring first and second open-loop power control parameters associated with the first and second SRIs, respectively.

[0174] (Embodiment 12) The method according to any of the preceding embodiments, further including indicating a number of transmission opportunities in the first or second PUCCH resource or an activation DCI.

[0175] (Embodiment 13) A method according to any of the preceding embodiments, wherein if the number of transmission opportunities is two or more, the spatial relationship is applied to the transmission opportunities in either a cyclic or sequential manner, where a first spatial relationship is applied to a first subset of the transmission opportunities and a second spatial relationship is applied to the remainder of the transmission opportunities.

[0176] (Embodiment 14) The method according to any of the preceding embodiments, in which for SP CSI on a PUSCH, the SP CSI is activated using a DCI including two SRIs, each associated with one of two TRPs.

[0177] (Embodiment 15) The method according to any of the preceding embodiments, in which in each SP CSI reporting period, the wireless device transmits SP CSI in two slots or minislots in the same PUSCH resource, and each SP CSI transmits towards one of two TRPs.

[0178] (Embodiment 16) The method according to any of the preceding embodiments, in which the number of repetitions is determined by the "K" value in the TDRA indicated in the activation DCI, and the mapping between the CSI transmission and the TRP can be either cyclic or sequential.

[0179] (Embodiment 17) A method according to any of the preceding embodiments, in which the number of repetitions is determined jointly by the "K" value in the TDRA and the number of SRIs indicated in the activation DCI, and the CSI is repeated K times only if two or more SRIs are indicated.

[0180] (Embodiment 18) The method according to any of the preceding embodiments, in which when two SRIs are indicated in an activation DCI, the SP CSI is periodically transmitted to different TRPs in different reporting periods.

[0181] (Embodiment 19) The method according to any of the preceding embodiments, in which for SP CSI or periodic CSI on a PUCCH, a PUCCH resource is configured for each BWP having two spatial relationships, each associated with one of two TRPs.

[0182] (Embodiment 20) The method according to any of the preceding embodiments, in which in each SP CSI or periodic CSI reporting period, the SP CSI or periodic CSI is repeated in either two slots in the same PUCCH resource in the CSI reporting period or two mini-slots of the same slot.

[0183] (Embodiment 21) The method according to any of the preceding embodiments, wherein each repeat is directed to one of two TRPs.

[0184] (Embodiment 22) The method according to any of the preceding embodiments, in which the repetition number is configured in the PUCCH resource for SP CSI or periodic CSI.

[0185] (Embodiment 23) The method according to any of the preceding embodiments, in which mapping between the transmission of SP CSI or periodic CSI and the TRPs can be either cyclic or sequential between two TRPs.

[0186] (Embodiment 24) The method according to any of the preceding embodiments, in which different PUCCH resources may be configured for SP CSI or periodic CSI for different TRPs.

[0187] (Embodiment 25) The method according to any of the preceding embodiments, in which SP CSI on a PUCCH is activated / deactivated by DL DCI.

[0188] (Embodiment 26) The method according to any of the preceding embodiments, further comprising: providing user data; and transferring the user data to the host computer via transmission to the base station.

[0189] Group B Embodiments

[0190] (Embodiment 27) A method performed by a base station for reliable channel state information (CSI) feedback, comprising: transmitting (700) configurations to a wireless device, the configurations being for one or more of: i. a semi-persistent CSI (SP-CSI) report in a physical uplink control channel (PUCCH) including a first PUCCH resource activated with a first and second spatial relationship or uplink transmission configuration indicator (TCI) state, a reporting periodicity, and / or a slot offset; ii. a SP-CSI report on a PUSCH with a reporting periodicity and a slot offset; and iii. a periodic CSI report in a PUCCH including a second PUCCH resource activated with a third and fourth spatial relationship or uplink TCI state, a reporting periodicity, and a slot offset; and transmitting (702) configurations to the wireless device, the configurations being for one or more of: i. an activation command to activate the SP-CSI on the PUCCH; and ii. and receiving (704) from the wireless device, the method including: transmitting one or more of: activation downlink control information (DCI) for activating SP-CSI on a PUSCH, the DCI comprising first and second SRS resource indicators (SRIs) and a PUSCH resource; and receiving (705) from the wireless device, the method including: receiving one or more of: i. SP-CSI on a first PUCCH resource at a first transmission opportunity according to a first spatial relationship and a second transmission opportunity according to a second spatial relationship, activated for the first PUCCH resource; ii. periodic CSI on a second PUCCH resource at a third transmission according to a third spatial relationship and a fourth transmission according to a fourth spatial relationship, configured for the second PUCCH resource; and iii. SP-CSI on a PUSCH resource at a fifth transmission opportunity according to the first SRI and a sixth transmission opportunity according to the second SRI.

[0191] (Embodiment 28) The method according to any of the preceding embodiments, wherein the base station is a radio network node comprising a plurality of transmission / reception points (TRPs), each of which is associated with a spatial relationship or SRI.

[0192] (Embodiment 29) The method according to any of the preceding embodiments, wherein each transmission opportunity is in either a slot or a minislot that includes several OFDM symbols within the slot.

[0193] (Embodiment 30) The method according to any of the preceding embodiments, in which the first transmission opportunity and the second transmission opportunity are in two adjacent slots or minislots in each reporting period for SP-CSI on the PUCCH.

[0194] (Embodiment 31) The method according to any of the preceding embodiments, in which the third transmission opportunity and the fourth transmission opportunity are in two adjacent slots or minislots in each reporting period for P-CSI on the PUCCH.

[0195] (Embodiment 32) The method according to any of the preceding embodiments, wherein the fifth and sixth transmission opportunities are within two adjacent slots or minislots for SP-CSI on the PUSCH.

[0196] (Embodiment 33) The method according to any of the preceding embodiments, wherein the activation command may be one of a MAC CE and a DL DCI.

[0197] (Embodiment 34) A method according to any of the preceding embodiments, further comprising receiving a first CSI in a first slot or minislot in a first reporting period according to a first spatial relationship or SRI, and receiving a second CSI in a second slot or minislot in a second reporting period according to a second spatial relationship or SRI.

[0198] (Embodiment 35) A method according to any of the preceding embodiments, wherein each of the first to fourth spatial relationships comprises a reference signal (RS) that defines a transmit spatial filter and a set of power control parameters for an associated PUCCH.

[0199] (Embodiment 36) The method according to any of the preceding embodiments, wherein each of the first and second SRIs indicates an SRS resource having a number of antenna ports over which the PUSCH is transmitted and a set of power control parameters for the PUSCH.

[0200] (Embodiment 37) The method of any of the preceding embodiments, wherein configuring an SP-CSI report in the PUSCH further comprises configuring first and second open-loop power control parameters associated with the first and second SRIs, respectively.

[0201] (Embodiment 38) The method according to any of the preceding embodiments, further including indicating a number of transmission opportunities in the first or second PUCCH resource or an activation DCI.

[0202] (Embodiment 39) A method according to any of the preceding embodiments, wherein if the number of transmission opportunities is two or more, the spatial relationship is applied to the transmission opportunities in either a cyclic or sequential manner, where a first spatial relationship is applied to a first subset of the transmission opportunities and a second spatial relationship is applied to the remainder of the transmission opportunities.

[0203] (Embodiment 40) The method according to any of the preceding embodiments, in which for SP CSI on a PUSCH, the SP CSI is activated using a DCI including two SRIs, each associated with one of two TRPs.

[0204] (Embodiment 41) The method according to any of the preceding embodiments, in which in each SP CSI reporting period, the wireless device transmits SP CSI in two slots or minislots in the same PUSCH resource, and each SP CSI transmits towards one of two TRPs.

[0205] (Embodiment 42) The method according to any of the preceding embodiments, in which the number of repetitions is determined by the "K" value in the TDRA indicated in the activation DCI, and the mapping between the CSI transmission and the TRP can be either cyclic or sequential.

[0206] (Embodiment 43) A method according to any of the preceding embodiments, in which the number of repetitions is determined jointly by the "K" value in the TDRA and the number of SRIs indicated in the activation DCI, and the CSI is repeated K times only if two or more SRIs are indicated.

[0207] (Embodiment 44) The method according to any of the preceding embodiments, in which when two SRIs are indicated in an activation DCI, the SP CSI is periodically transmitted to different TRPs in different reporting periods.

[0208] (Embodiment 45) The method according to any of the preceding embodiments, in which for SP CSI or periodic CSI on a PUCCH, a PUCCH resource is configured for each BWP having two spatial relationships, each associated with one of two TRPs.

[0209] (Embodiment 46) The method according to any of the preceding embodiments, in which in each SP CSI or periodic CSI reporting period, the SP CSI or periodic CSI is repeated in either two slots in the same PUCCH resource in the CSI reporting period or two mini-slots of the same slot.

[0210] (Embodiment 47) The method according to any of the preceding embodiments, wherein each repeat is directed to one of two TRPs.

[0211] (Embodiment 48) The method according to any of the preceding embodiments, in which the repetition number is configured in the PUCCH resource for SP CSI or periodic CSI.

[0212] (Embodiment 49) The method according to any of the preceding embodiments, in which the mapping between the transmission of SP CSI or periodic CSI and the TRPs can be either a cyclic or sequential manner between two TRPs.

[0213] (Embodiment 50) The method according to any of the preceding embodiments, in which different PUCCH resources may be configured for SP CSI or periodic CSI for different TRPs.

[0214] (Embodiment 51) The method according to any of the preceding embodiments, in which SP CSI on a PUCCH is activated / deactivated by DL DCI.

[0215] (Embodiment 52) ​​The method according to any of the preceding embodiments, further comprising obtaining user data and transferring the user data to a host computer or a wireless device.

[0216] Group C Embodiments

[0217] (Embodiment 53) A wireless device for reliable channel state information (CSI) feedback, the wireless device comprising a processing circuit configured to perform any of the steps of any of the embodiments of Group A, and a power supply circuit configured to supply power to the wireless device.

[0218] (Embodiment 54) A base station for reliable channel state information (CSI) feedback, comprising: a processing circuit configured to perform any of the steps of any of the embodiments of Group B; and a power supply circuit configured to supply power to the base station.

[0219] (Embodiment 55) A user equipment (UE) for reliable channel state information (CSI) feedback, the UE comprising: an antenna configured to transmit and receive radio signals; a radio front-end circuit connected to the antenna and the processing circuit and configured to condition signals communicated between the antenna and the processing circuit; the processing circuit configured to perform any of the steps of any of the embodiments of Group A; an input interface connected to the processing circuit and configured to enable input of information into the UE to be processed by the processing circuit; an output interface connected to the processing circuit and configured to output information from the UE that has been processed by the processing circuit; and a battery connected to the processing circuit and configured to supply power to the UE.

[0220] (Embodiment 56) A communications system including a host computer, comprising a processing circuit configured to provide user data, and a communications interface configured to transfer the user data to a cellular network for transmission to a user equipment (UE), the cellular network comprising a base station having a wireless interface and processing circuitry, the processing circuitry of the base station configured to perform any of the steps of any of the embodiments of Group B.

[0221] (Embodiment 57) The communication system described in any of the preceding embodiments, further including a base station.

[0222] (Embodiment 58) The communication system according to the two preceding embodiments, further comprising the UE, the UE being configured to communicate with the base station.

[0223] (Embodiment 59) A communication system as described in any of the preceding three embodiments, wherein the processing circuitry of the host computer is configured to execute a host application thereby to provide user data, and the UE comprises processing circuitry configured to execute a client application associated with the host application.

[0224] (Embodiment 60) A method implemented in a communications system including a host computer, a base station, and a user equipment (UE), the method comprising: providing user data at the host computer; and initiating a transmission at the host computer conveying the user data to the UE via a cellular network including the base station, the base station performing any of the steps of any of the embodiments of Group B.

[0225] (Embodiment 61) The method according to any of the preceding embodiments, further comprising: transmitting user data at a base station.

[0226] (Embodiment 62) The method according to the preceding two embodiments, wherein user data is provided in the host computer by executing a host application, and the method further includes executing, in the UE, a client application associated with the host application.

[0227] (Embodiment 63) A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to perform the method according to any of the three embodiments.

[0228] (Embodiment 64) A communications system including a host computer, the communications system comprising a processing circuit configured to provide user data and a communications interface configured to transfer the user data to a cellular network for transmission to a user equipment (UE), the UE comprising a wireless interface and a processing circuit, the components of the UE being configured to perform any of the steps of any of the embodiments of Group A.

[0229] (Embodiment 65) The communication system described in the preceding embodiment, wherein the cellular network further includes a base station configured to communicate with the UE.

[0230] (Embodiment 66) A communication system as described in the two preceding embodiments, wherein the processing circuitry of the host computer is configured to execute a host application thereby to provide user data, and the processing circuitry of the UE is configured to execute a client application associated with the host application.

[0231] (Embodiment 67) A method implemented in a communications system including a host computer, a base station, and a user equipment (UE), the method comprising: providing user data at the host computer; and initiating a transmission at the host computer conveying the user data to the UE via a cellular network including the base station, the UE performing any of the steps of any of the embodiments of Group A.

[0232] (Embodiment 68) The method according to any preceding embodiment, further comprising: receiving, at the UE, user data from a base station.

[0233] (Embodiment 69) A communications system including a host computer, the communications system comprising a communications interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, the UE comprising a radio interface and processing circuitry, the processing circuitry of the UE configured to perform any of the steps of any of the embodiments of Group A.

[0234] (Embodiment 70) The communication system described in the previous embodiment, further including a UE.

[0235] (Embodiment 71) The communication system described in the two preceding embodiments, further including a base station, the base station having a wireless interface configured to communicate with the UE and a communication interface configured to transfer user data carried by transmissions from the UE to the base station to a host computer.

[0236] (Embodiment 72) A communication system as described in any of the preceding three embodiments, wherein the processing circuitry of the host computer is configured to execute a host application and the processing circuitry of the UE is configured to execute a client application associated with the host application, thereby providing user data.

[0237] (Embodiment 73) A communication system as described in any of the preceding four embodiments, wherein the processing circuitry of the host computer is configured to execute a host application and thereby provide the requested data, and the processing circuitry of the UE is configured to execute a client application associated with the host application and thereby provide user data in response to the requested data.

[0238] (Embodiment 74) A method implemented in a communications system including a host computer, a base station, and a user equipment (UE), the method including receiving, at the host computer, user data transmitted from the UE to the base station, the UE performing any of the steps of any of the embodiments of Group A.

[0239] (Embodiment 75) The method according to any of the preceding embodiments, further comprising: providing, in the UE, user data to the base station.

[0240] (Embodiment 76) The method according to the two preceding embodiments, further comprising: executing, in the UE, a client application thereby providing user data to be transmitted; and executing, in the host computer, a host application associated with the client application.

[0241] (Embodiment 77) The method according to any of the preceding three embodiments, further comprising: executing a client application in the UE; and receiving, in the UE, input data for the client application, wherein the input data is provided in a host computer by executing a host application associated with the client application, and the user data to be transmitted is provided by the client application in response to the input data.

[0242] (Embodiment 78) A communications system including a host computer having a communications interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, the base station having a wireless interface and processing circuitry, the processing circuitry of the base station being configured to perform any of the steps of any of the Group B embodiments.

[0243] (Embodiment 79) The communication system described in any preceding embodiment, further comprising a base station.

[0244] (Embodiment 80) The communication system according to the preceding two embodiments, further comprising a UE, the UE being configured to communicate with the base station.

[0245] (Embodiment 81) A communication system as described in any of the preceding three embodiments, wherein the processing circuitry of the host computer is configured to execute a host application and the UE is configured to execute a client application associated with the host application, thereby providing user data to be received by the host computer.

[0246] (Embodiment 82) A method implemented in a communications system including a host computer, a base station, and a user equipment (UE), the method including receiving, at the host computer, user data from the base station originating from a transmission received by the base station from the UE, the UE performing any of the steps of any of the embodiments of Group A.

[0247] (Embodiment 83) The method according to any of the preceding embodiments, further comprising: receiving, at the base station, user data from the UE.

[0248] (Embodiment 84) The method according to the preceding two embodiments, further comprising initiating, at the base station, transmission of the received user data to the host computer.

[0249] In this disclosure, at least some of the following abbreviations may be used. In case of discrepancies between abbreviations, how it is used above is preferred. If listed multiple times below, the first listing should take precedence over subsequent listings. 3GPP(registered trademark) 3rd Generation Partnership Project 5G 5th Generation 5GC 5th generation core 5GS 5th Generation System ACK Acknowledgement AF Application Features AMF Access and Mobility Features AN Access Network AP Access point ASIC Application Specific Integrated Circuit AUSF authentication server function BLER Block Error Rate BWP Bandwidth Part CE Control Element CG Composition Grant CP-OFDM Cyclic Prefix Orthogonal Frequency Division Multiplexing CPU Central Processing Unit CQI Channel Quality Indicator CRC Cyclic Redundancy Check CSI Channel State Information CSI-RS Channel State Information Reference Signal DCI Downlink Control Information DFT Discrete Fourier Transform DL Downlink DMRS Demodulation Reference Signal DN Data Network DSP Digital Signal Processor eNB Enhanced or evolved Node B FPGA Field Programmable Gate Array FR Frequency Range gNB new radio base station gNB-CU New Radio Base Station Central Unit gNB-DU New Radio Base Station Distributed Unit HARQ Hybrid Automatic Repeat Request HSS Home Subscriber Server IoT Internet of Things IP Internet Protocol LTE Long Term Evolution MAC Media Access Control MCS Modulation and Coding Scheme MIMO Multiple Input Multiple Output MME Mobility Management Entity MTC Machine Type Communication NEF network publishing function NF Network Function NR New Radio NRF Network Function Repository Function NSSF Network Slice Selection Function NZP Non-zero Power OFDM Orthogonal Frequency Division Multiplexing OTT Over the Top PC Personal Computer PCF Policy Control Function P-GW Packet Data Network Gateway PMI Precoder Matrix Indicator PUCCH Physical Uplink Control Channel PUSCH Physical Uplink Shared Channel RAM Random Access Memory RAN Radio Access Network RB Resource Block RE resource element RI Rank Indicator RNTI Radio Network Temporary Identifier ROM Read Only Memory RRC Radio Resource Control RRH Remote Radio Head RS reference signal RTT Round Trip Time SCEF Service Capability Exposure Function SINR Signal to Interference Power and Noise Ratio SMF Session Management Facility SP Semi-permanent SP-CSI Semi-persistent channel state information SR Scheduling Request SRI SRS Resource Indicator SRS Sounding Reference Signal SSB sync signal block TB Transport Block TCI Transmit Configuration Indicator TDD Time Division Duplex TDRA Time Domain Resource Allocation TRP Submission Point UCI UL Control Information UDM Unified Data Management UE User Equipment UL Uplink UPF User Plane Function

[0250] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure, and all such improvements and modifications are deemed to be within the scope of the concepts disclosed herein.

Claims

1. 1. A method performed by a wireless device for reliable channel state information (CSI) feedback, the method comprising: receiving 600 a configuration for semi-persistent CSI (SP-CSI) reporting on a physical uplink shared channel (PUSCH) comprising a second reporting periodicity and a list of slot offsets and a resource set of a first and a second sounding reference signal (SRS); receiving (602) an activation downlink control information (DCI) for activating the SP-CSI on the PUSCH, the DCI including a PUSCH resource allocation including first and second SRS resource indicators (SRIs) indicating first and second SRS resources of the first and second SRS resource sets, respectively, a second slot offset from the list of slot offsets, and a number of transmission opportunities configured or indicated in a time domain resource allocation (TDRA) field of the activation DCI; determining the number of transmission opportunities in SP-CSI to be transmitted according to the number of SRS resource sets from an SRI indicated in the DCI, regardless of the number of transmission opportunities configured or indicated in the TDRA field of the activation DCI; transmitting an SP-CSI report on the PUSCH resource at a first transmission opportunity according to the first (or the second) SRI and at a second transmission opportunity according to the second (or the first) SRI in each reporting period defined by the reporting periodicity and the slot offset (604); A method comprising:

2. 2. The method of claim 1, wherein the transmitting is performed to a radio network node comprising a plurality of transmission / reception points (TRPs), each associated with a spatial relationship or SRS resource set.

3. 3. The method of claim 1 or 2, wherein each transmission opportunity is in either a slot or a minislot that includes multiple consecutive orthogonal frequency division multiplexing (OFDM) symbols within the slot.

4. 4. The method of claim 1, wherein the first transmission opportunity and the second transmission opportunity are within two consecutive slots or minislots for the SP-CSI on the PUSCH, and the slot or minislot starting earlier of the two adjacent slots or minislots is determined by the reporting periodicity and the slot offset.

5. 5. The method of claim 1, further comprising transmitting the SP-CSI report in a first slot or minislot according to the first SRI and in a second slot or minislot according to the second SRI in the same reporting period.

6. 6. The method of claim 1, wherein the first and second SRIs indicate first and second SRS resources for the PUSCH associated with the first and second transmission opportunities, respectively, and first and second sets of power control parameters.

7. 7. The method of claim 1, wherein the configuration of the SP-CSI report on a PUSCH further comprises a first set and a second set of power control parameters associated respectively with the first and second transmission opportunities of the PUSCH carrying the SP-CSI report.

8. A method according to any one of claims 1 to 7, wherein when the two SRIs are indicated in the activation DCI, the SP CSI transmitted during different reporting periods is associated with the two SRIs in a cyclic manner.

9. A method according to any one of claims 1 to 8, wherein the activation DCI for the SP-CSI in a PUSH is one of DCI format 0_1 ​​and DCI format 0_2.

10. 2. The method of claim 1 , Receiving the configuration includes receiving the configuration for the SP-CSI reporting on the PUSCH comprising a reporting periodicity and one or more slot offsets (1200); Receiving one or more activations includes receiving an activation DCI that activates the SP-CSI on the PUSCH (1202), the DCI comprising the first and second SRIs and the PUSCH resource; 12. The method of claim 1, wherein transmitting the one or more CSIs comprises transmitting the SP-CSI on the PUSCH resources at the first transmission opportunity according to the first SRI and at the second transmission opportunity according to the second SRI (1204).

11. A wireless device (1800), One or more transmitters (1808); One or more receivers (1810); A processing circuit (1802) associated with the one or more transmitters (1808) and the one or more receivers (1810), the processing circuit (1802) being provided to the wireless device (1800): Receive (600) a configuration for semi-persistent CSI (SP-CSI) reporting on a physical uplink shared channel (PUSCH), the configuration comprising a second reporting periodicity and a list of slot offsets, and a resource set for a first and a second sounding reference signal (SRS); receiving (602) an activation downlink control information (DCI) for activating the SP-CSI on the PUSCH, the DCI including a PUSCH resource allocation including first and second SRS resource indicators (SRIs) indicating first and second SRS resources of the first and second SRS resource sets, respectively, a second slot offset from the list of slot offsets, and a number of transmission opportunities configured or indicated in a time domain resource allocation (TDRA) field of the activation DCI; determining the number of transmission opportunities in SP-CSI to be transmitted according to the number of SRS resource sets from an SRI indicated in the DCI, regardless of the number of transmission opportunities configured or indicated in the TDRA field of the activation DCI; transmitting an SP-CSI report on the PUSCH resource at a first transmission opportunity according to the first (or the second) SRI and at a second transmission opportunity according to the second (or the first) SRI in each reporting period defined by the reporting periodicity and the slot offset (604); and a processing circuit configured to:

12. A wireless device (1800) as described in claim 11, further adapted to perform a method as described in any one of claims 2 to 10.

Images