Pre-compensated type ii coherent joint transmission codebook report
Offset compensation techniques in Type II CJT codebook reports address the issue of TRP offsets, enabling UEs to report optimal CSI parameters and enhance network performance and reliability in wireless communication networks.
Patent Information
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- APPLE INC
- Filing Date
- 2024-11-08
- Publication Date
- 2026-05-15
AI Technical Summary
Existing Type II coherent joint transmission (CJT) codebook reports in wireless communication networks fail to account for time, frequency, and phase offsets among different transmission reception points (TRPs), leading to suboptimal precoding matrix reporting and reduced network performance.
Implement techniques for delay, frequency, and phase offset compensation in Type II CJT codebook reports, including configuring UEs to apply offset compensation to measurement resources, handling invalid offset values, and relaxing CSI processing timelines to support coherent joint transmission.
Enables UEs to report optimal CSI parameters, enhancing network performance and reliability by accounting for TRP offsets, thereby improving signal strength and throughput in CJT operations.
Smart Images

Figure CN2024130815_15052026_PF_FP_ABST
Abstract
Description
PRE-COMPENSATED TYPE II COHERENT JOINT TRANSMISSION CODEBOOK REPORTTECHNICAL FIELD
[0001] The present disclosure relates to wireless communications and, more specifically, to Type II coherent joint transmission (CJT) codebook reports with offset compensation.BACKGROUND
[0002] Wireless communication networks provide integrated communication platforms and telecommunication services to wireless user devices. Example telecommunication services include telephony, data (e.g., voice, audio, and / or video data) , messaging, internet-access, and / or other services. The wireless communication networks have wireless access nodes that exchange wireless signals with the wireless user devices using wireless network protocols, such as protocols described in various telecommunication standards promulgated by the Third Generation Partnership Project (3GPP) . Example wireless communication networks include code division multiple access (CDMA) networks, time division multiple access (TDMA) networks, frequency-division multiple access (FDMA) networks, orthogonal frequency-division multiple access (OFDMA) networks, Long Term Evolution (LTE) , and Fifth Generation New Radio (5G NR) . The wireless communication networks facilitate mobile broadband service using technologies such as OFDM, multiple input multiple output (MIMO) , advanced channel coding, massive MIMO, beamforming, and / or other features.SUMMARY
[0003] The present disclosure describes enhancements to support delay offset compensation in Type II CJT codebook reports.
[0004] In general, in a first aspect, a method includes: receiving an indication to apply offset compensation for one or more measurement resources associated with a channel state information (CSI) report, generating the CSI report based in part on application of the offset compensation to at least one of the measurement resources, and causing transmission of the CSI report to at least one transmission reception point (TRP) .
[0005] In a second aspect combinable with the first aspect, the CSI report is a type II coherent joint transmission (CJT) codebook report.
[0006] In a third aspect combinable with the first or second aspects, the indication includes an indication to apply offset compensation to each of the one or more measurement resources associated with the CSI report.
[0007] In a fourth aspect combinable with any of the preceding aspects, the indication includes an indication to apply offset compensation to a subset of the one or more measurement resources associated with the CSI report.
[0008] In a fifth aspect combinable with any of the preceding aspects, the indication includes an indication to apply offset compensation for a CSI trigger state, where the CSI report is associated with the CSI trigger state.
[0009] In a sixth aspect combinable with any of the preceding aspects, the indication includes an information element in a message configuring the CSI report.
[0010] In a seventh aspect combinable with any of the preceding aspects, the indication includes an information element in a message configuring a CSI trigger state, where the CSI report is associated with the CSI trigger state.
[0011] In an eighth aspect combinable with any of the preceding aspects, the one or more measurement resources are CSI-RS resources.
[0012] In a ninth aspect combinable with any of the preceding aspects, the offset compensation includes at least one of a delay offset compensation, a frequency offset compensation, or a phase offset compensation.
[0013] In a tenth aspect combinable with any of the preceding aspects, generating the CSI report includes: obtaining offset information for the one or more measurement resources; applying the offset information to the one or more measurement resources to produce one or more compensated measurement resources; determining one or more CSI parameters based on the one or more compensated measurement resources; and generating the CSI report including the determined one or more CSI parameters.
[0014] In an eleventh aspect combinable with any of the preceding aspects, the one or more CSI parameters include at least one of a precoding matrix indicator (PMI) , a channel quality indicator (CQI) , or a rank indicator (RI) .
[0015] In a twelfth aspect combinable with any of the preceding aspects, the offset information is obtained from an offset report.
[0016] In a thirteenth aspect combinable with any of the preceding aspects, there is a one-to-one correspondence between one or more tracking reference signal (TRS) resources associated with the offset report and the one or more measurement resources associated with the CSI report.
[0017] In a fourteenth aspect combinable with any of the preceding aspects, a correspondence between one or more TRS resources associated with the offset report and the one or more measurement resources associated with the CSI report is configured by a network.
[0018] In a fifteenth aspect combinable with any of the preceding aspects, operations of the method include: determining that offset information is invalid for at least one of the one or more measurement resources, and generating the CSI report without application of the offset compensation.
[0019] In a sixteenth aspect combinable with any of the preceding aspects, operations of the method include: determining that offset information is invalid for at least one of the one or more measurement resources, and generating the CSI report based in part on application of the offset compensation to measurement resources other than the at least one of the one or more measurement resources.
[0020] In a seventeenth aspect combinable with any of the preceding aspects, a minimum time duration between an end of a last symbol of a message triggering the CSI report and a first uplink symbol carrying the CSI report is increased in response to the CSI report being jointly triggered with an offset report.
[0021] In an eighteenth aspect combinable with any of the preceding aspects, a minimum time duration between an end of a last symbol of a latest of the one or more measurement resources and a first uplink symbol carrying the CSI report is increased in response to the CSI report being jointly triggered with an offset report.
[0022] In a nineteenth aspect combinable with any of the preceding aspects, the method is performed by a user equipment (UE) or one or more baseband processors.
[0023] In general, in a twentieth aspect, one or more baseband processors are configured to perform the method of any of the preceding aspects.
[0024] In general, in a twenty-first aspect, an apparatus includes one or more processors and memory storing instructions executable by the one or more processors to perform the method of any of the first through nineteenth aspects.
[0025] In general, in a twenty-second aspect, one or more non-transitory computer-readable storage mediums store instructions executable by one or more processors to perform the method of any of the first through nineteenth aspects.
[0026] In general, in a twenty-third aspect, a method includes: causing transmission of an indication to apply offset compensation for one or more measurement resources associated with a CSI report, receiving the CSI report, where the CSI report includes one or more CSI parameters determined based in part on application of the offset compensation, and causing transmission of an indication of a configuration based in part on the one or more CSI parameters.
[0027] In a twenty-fourth aspect combinable with the twenty-third aspect, the CSI report includes a type II CJT codebook report.
[0028] In a twenty-fifth aspect combinable with the twenty-third or twenty-fourth aspects, the indication includes an indication to apply offset compensation to each of the one or more measurement resources associated with the CSI report.
[0029] In a twenty-sixth aspect combinable with any of the twenty-third through twenty-fifth aspects, the indication includes an indication to apply offset compensation to a subset of the one or more measurement resources associated with the CSI report.
[0030] In a twenty-seventh aspect combinable with any of the twenty-third through twenty-sixth aspects, the indication includes an indication to apply offset compensation for a CSI trigger state, where the CSI report is associated with the CSI trigger state.
[0031] In a twenty-eighth aspect combinable with any of the twenty-third through twenty-seventh aspects, the indication includes an information element in a message configuring the CSI report.
[0032] In a twenty-ninth aspect combinable with any of the twenty-third through twenty-eighth aspects, the indication includes an information element in a message configuring a CSI trigger state, where the CSI report is associated with the CSI trigger state.
[0033] In a thirtieth aspect combinable with any of the twenty-third through twenty-ninth aspects, the one or more measurement resources are CSI-RS resources.
[0034] In a thirty-first aspect combinable with any of the twenty-third through thirtieth aspects, the offset compensation includes at least one of a delay offset compensation, a frequency offset compensation, or a phase offset compensation.
[0035] In a thirty-second aspect combinable with any of the twenty-third through thirty-first aspects, wherein the one or more CSI parameters include at least one of a PMI, a CQI, or a RI.
[0036] In a thirty-third aspect combinable with any of the twenty-third through thirty-second aspects, operations of the method include causing transmission of an indication of a correspondence between one or more TRS resources associated with an offset report and the one or more measurement resources associated with the CSI report.
[0037] In a thirty-fourth aspect combinable with any of the twenty-third through thirty-third aspects, operations of the method include: selecting a precoding matrix based in part on the CSI report, and causing transmission of an indication of the selected precoding matrix.
[0038] In a thirty-fifth aspect combinable with any of the twenty-third through thirty-fourth aspects, the method is performed by a base station or one or more baseband processors.
[0039] In general, in a thirty-sixth aspect, one or more baseband processors are configured to perform the method of any of the twenty-third through thirty-fifth aspects.
[0040] In general, in a thirty-seventh aspect, an apparatus includes one or more processors and memory storing instructions executable by the one or more processors to perform the method of any of the twenty-third through thirty-fifth aspects.
[0041] In general, in a thirty-eighth aspect, one or more non-transitory computer-readable storage mediums store instructions executable by one or more processors to perform the method of any of the twenty-third through thirty-fifth aspects.
[0042] The details of one or more embodiments of these systems and methods are set forth in the accompanying drawings and the description below. Other features, objects, and advantages of these systems and methods will be apparent from the description and drawings, and from the claims.
[0043] BRIEF DESCRIPTION OF THE FIGURES
[0044] FIG. 1 illustrates a wireless network, according to some implementations.
[0045] FIGS. 2 and 3 illustrates a flowchart of an example method for CSI report enhancement with delay offset compensation.
[0046] FIG. 4 illustrates a user equipment (UE) , according to some implementations.
[0047] FIG. 5 illustrates an access node, according to some implementations.DETAILED DESCRIPTION
[0048] To improve network performance and reliability, 5G NR wireless communications systems utilize multiple transmission reception points (TRPs) to communicate with a single user equipment (UE) . The support of multi-TRP operation in 5G NR wireless communication systems has evolved significantly through various releases of the 3GPP standards. Initially, multi-TRP operation was supported in a transparent mode in which multiple TRPs communicate with a single UE without the UE being explicitly aware of the multiple TRPs’ involvement. Later, explicit multi-TRP operation was introduced, including support for multi-TRP non-coherent joint transmission (NCJT) schemes in which multiple TRPs simultaneously transmit signals to a UE without synchronizing timing, frequency, or phase. More recently, support for a multi-TRP coherent joint transmission (CJT) scheme was introduced, among other enhancements.
[0049] In CJT, the network coordinates the relative phase of signals from different TRPs (e.g., through selection of appropriate precoding matrices or beamforming vectors) to ensure that the signals from each TRP are coherently combined at the UE, thereby increasing signal strength and improving throughput. As such, CJT can achieve better performance relative to NCJT techniques that do not employ such coherent combination. However, CJT requires precise synchronization among TRPs in order to maintain coherency. In practice, different TRPs may experience different time, frequency, or phase offsets (or changes to time, frequency, or phase offsets) due to, for example, the location of the UE, movement of the UE, and / or the hardware implementation of the TRP, among other factors. A UE can measure the time, frequency, and / or phase offset between different TRPs and can report these measurements to the network in an offset report. However, the UE is unable to account for the offset when measuring and reporting the optimal precoding matrix (and other information) in CSI report, such as a Type II CJT codebook report.
[0050] The present disclosure introduces techniques for compensating delay offsets in Type II CJT codebook reports in order to support CJT deployment. In particular, techniques are described for configuring a UE to perform delay (and other) offset compensation based on an offset report for some or all measurement resources associated with a codebook report, or for all codebook reports associated with a particular trigger. These techniques enable the UE to report optimal CSI parameters, such as a precoding matrix indicator (PMI) , channel quality index (CQI) , and / or rank indicator (RI) , in a manner that accounts for time, frequency, and / or phase offsets among different TRPs, thereby facilitating CJT operation. The present disclosure also describes techniques for handling invalid delay offsets values during delay offset compensation. In addition, a design for relaxing the CSI processing timeline is proposed to support delay offset compensation.
[0051] FIG. 1 illustrates a wireless network 100, according to some implementations. The wireless network 100 includes a UE 102 and a base station 104 connected via one or more channels 106A, 106B across an air interface 108. The UE 102 and base station 104 communicate using a system that supports controls for managing the access of the UE 102 to a network via the base station 104.
[0052] In some implementations, the wireless network 100 may be a Non-Standalone (NSA) network that incorporates Long Term Evolution (LTE) and Fifth Generation (5G) New Radio (NR) communication standards as defined by the Third Generation Partnership Project (3GPP) technical specifications. For example, the wireless network 100 may be a E-UTRA (Evolved Universal Terrestrial Radio Access) -NR Dual Connectivity (EN-DC) network, or a NR-EUTRA Dual Connectivity (NE-DC) network. However, the wireless network 100 may also be a Standalone (SA) network that incorporates only 5G NR. Furthermore, other types of communication standards are possible, including future 3GPP systems (e.g., Sixth Generation (6G) ) systems, Institute of Electrical and Electronics Engineers (IEEE) 802.11 technology (e.g., IEEE 802.11a; IEEE 802.11b; IEEE 802.11g; IEEE 802.11-2007; IEEE 802.11n; IEEE 802.11-2012; IEEE 802.11ac; or other present or future developed IEEE 802.11 technologies) , IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc. ) , or the like. While aspects may be described herein using terminology commonly associated with 5G NR, aspects of the present disclosure can be applied to other systems, such as 3G, 4G, and / or systems subsequent to 5G (e.g., 6G) .
[0053] In the wireless network 100, the UE 102 and any other UE in the system may be, for example, laptop computers, smartphones, tablet computers, machine-type devices such as smart meters or specialized devices for healthcare, intelligent transportation systems, or any other wireless devices with or without a user interface. In network 100, the base station 104 provides the UE 102 network connectivity to a broader network (not shown) . This UE 102 connectivity is provided via the air interface 108 in a base station service area provided by the base station 104. In some implementations, such a broader network may be a wide area network operated by a cellular network provider, or may be the Internet. Each base station service area associated with the base station 104 is supported by antennas integrated with the base station 104. The service areas are divided into a number of sectors associated with certain antennas. Such sectors may be physically associated with fixed antennas or may be assigned to a physical area with tunable antennas or antenna settings adjustable in a beamforming process used to direct a signal to a particular sector.
[0054] The UE 102 includes control circuitry 110 coupled with transmit circuitry 112 and receive circuitry 114. The transmit circuitry 112 and receive circuitry 114 may each be coupled with one or more antennas. The control circuitry 110 may include various combinations of application-specific circuitry and baseband circuitry. The transmit circuitry 112 and receive circuitry 114 may be adapted to transmit and receive data, respectively, and may include radio frequency (RF) circuitry or front-end module (FEM) circuitry.
[0055] In various implementations, aspects of the transmit circuitry 112, receive circuitry 114, and control circuitry 110 may be integrated in various ways to implement the operations described herein. The control circuitry 110 may be adapted or configured to perform various operations such as those described elsewhere in this disclosure related to a UE. For instance, the control circuitry 110 can perform CSI measurements and offset compensation, and generate a CSI report (e.g., a Type II CJT codebook report) as described herein.
[0056] The transmit circuitry 112 can perform various operations described in this specification. For example, the transmit circuitry 112 can transmit the generated CSI report to one or more TRPs. Additionally, the transmit circuitry 112 may transmit a plurality of multiplexed uplink physical channels. The plurality of uplink physical channels may be multiplexed according to time division multiplexing (TDM) or frequency division multiplexing (FDM) along with carrier aggregation. The transmit circuitry 112 may be configured to receive block data from the control circuitry 110 for transmission across the air interface 108.
[0057] The receive circuitry 114 can perform various operations described in this specification. For instance, the receive circuitry 114 can receive CSI-RS from multiple TRPs that are used to generate the CSI report. Additionally, the receive circuitry 114 may receive a plurality of multiplexed downlink physical channels from the air interface 108 and relay the physical channels to the control circuitry 110. The plurality of downlink physical channels may be multiplexed according to TDM or FDM along with carrier aggregation. The transmit circuitry 112 and the receive circuitry 114 may transmit and receive both control data and content data (e.g., messages, images, video, etc. ) structured within data blocks that are carried by the physical channels.
[0058] FIG. 1 also illustrates the base station 104. In implementations, the base station 104 may be an NG radio access network (RAN) or a 5G RAN, an E-UTRAN, a non-terrestrial cell, or a legacy RAN, such as a UTRAN or GERAN. As used herein, the term “NG RAN” or the like may refer to the base station 104 that operates in an NR or 5G wireless network 100, and the term “E-UTRAN” or the like may refer to a base station 104 that operates in an LTE or 4G wireless network 100. The UE 102 utilizes connections (or channels) 106A, 106B, each of which includes a physical communications interface or layer.
[0059] The base station 104 circuitry may include control circuitry 116 coupled with transmit circuitry 118 and receive circuitry 120. The transmit circuitry 118 and receive circuitry 120 may each be coupled with one or more antennas that may be used to enable communications via the air interface 108. The transmit circuitry 118 and receive circuitry 120 may be adapted to transmit and receive data, respectively, to any UE connected to the base station 104. The transmit circuitry 118 may transmit downlink physical channels includes of a plurality of downlink subframes. The receive circuitry 120 may receive a plurality of uplink physical channels from various UEs, including the UE 102.
[0060] In FIG. 1, the one or more channels 106A, 106B are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, such as a GSM protocol, a CDMA network protocol, a UMTS protocol, a 3GPP LTE protocol, an Advanced long term evolution (LTE-A) protocol, a LTE-based access to unlicensed spectrum (LTE-U) , a 5G protocol, a NR protocol, an NR-based access to unlicensed spectrum (NR-U) protocol, and / or any of the other communications protocols discussed herein. In implementations, the UE 102 may directly exchange communication data via a ProSe interface. The ProSe interface may alternatively be referred to as a sidelink (SL) interface and may include one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH) , a Physical Sidelink Control Channel (PSCCH) , a Physical Sidelink Discovery Channel (PSDCH) , and a Physical Sidelink Broadcast Channel (PSBCH) .
[0061] To support Type II CJT codebook enhancement with delay offset compensation, the network (e.g., the base station 104) can configure whether a UE (e.g., the UE 102) should apply delay offset compensation for a corresponding aperiodic CJT codebook report. In some examples, an information element (IE) (e.g., CJT-ApplyDelayCompensation-r19) is introduced in a message configuring the report (e.g., CSI-AssociatedReportConfigInfo) . In general, CSI-AssociatedReportConfigInfo can be used to associate an aperiodic CSI trigger state with to up to 16 aperiodic CSI reports, with each CSI-AssociatedReportConfigInfo associating an aperiodic CSI trigger state to one aperiodic CSI report. When the IE (e.g., CJT-ApplyDelayCompensation-r19) is set to ‘enabled, ’ the UE can apply the delay offset compensation for all measurement resources associated with the configured CJT codebook report. In some examples, the CJT-ApplyDelayCompensation-r19 IE (or a similar IE) can be introduced as follows:
[0062] In some examples, the IE CJT-ApplyDelayCompensation-r19 (or a different IE) can include a list of binary bits (e.g., a bitmap) . The number of bits in the list can be equal to the number of CSI-RS resources for the channel measurement in the corresponding report. If a bit =“1,” then the UE can apply delay offset compensation for the corresponding CSI-RS resource for CJT calculation. On the other hand, if a bit = “0, ” then the UE can proceed without applying delay offset compensation for the corresponding CSI-RS resource for CJT. In some examples, the CSI-CJT-ApplyDelayCompensation-r19 IE (or a similar IE) including the bitmap can be introduced as follows:
[0063] In some examples, an IE (e.g., CJT-ApplyDelayCompensation-r19) is introduced in a message configuring a trigger state (e.g., CSI-AperiodicTriggerState) . In general, CSI-AperiodicTriggerState can be used to associate an aperiodic CSI trigger state with up to 16 aperiodic CSI reports. When the IE (e.g., CJT-ApplyDelayCompensation-r19) is set to ‘enabled, ’ for all the aperiodic CSI reports that are associated with the corresponding aperiodic CSI trigger state, if the CSI report is for CJT codebook, the UE can apply delay offset compensation for CJT codebook calculation. In some examples, the CJT-ApplyDelayCompensation-r19 IE (or a similar IE) can be introduced as follows:
[0064] To support Type II CJT codebook enhancement with delay offset compensation, techniques for associating tracking reference signal (TRS) resources configured for a delay offset report and channel state information reference signals (CSI-RS) resources configured for a CJT report are defined. For example, assume K1 TRS resource sets are configured for a delay offset report. Also assume K2 CSI-RS resources are configured for a CJT report. In some examples, if the network configures a UE to apply delay offset compensation for CJT codebook calculation, the network can ensure that K1=K2. In this manner, a direct (e.g., one-to-one) correspondence between the K1 TRS resource sets configured for the delay offset report and the K2 CSI-RS resources configured for the CJT report can be achieved, thereby enabling the UE to resolve which delay offset should be applied to a respective CSI-RS resource measurement.
[0065] In some examples, the network can configure a different number of TRS and CSI-RS resources (e.g., K1≠K2) . In this example, the network can further configure the association between the delay offset measurement on a particular TRS resource set and the CSI-RS resource that the UE shall apply the corresponding delay offset measurement for CJT codebook calculation. In some examples, the network can configure a K1 bit bitmap, among which K2 bits are set to ‘1, ’ and others are set to ‘0. ’ In another example, the network can configure a K2 bit bitmap, among which K1 bits are set to ‘1, ’ and others are set to ‘0. ’ In some examples, the network can configure both a K1 bit bitmap and K2 bit bitmap, among which K bits are set to ‘1, ’ and others to ‘0’ in both bitmaps. With the bitmap configuration, the TRS resource set with the corresponding bit set to ‘1’ is one-to-one mapped to the CSI-RS resource with the corresponding bit set to ‘1’ according to an order, such as an increasing order of the TRS resource set ID, or an increasing order of the CSI-RS resource ID, or the order that the TRS resource sets are configured for measurement, or the order that the CSI-RS resources are configured for measurement. Note, the above configuration of mapping can also be applicable for the case K1=K2. In some examples, a UE can report (e.g., in a capability message) whether it supports the K1≠K2 scenario, and whether the network configures K1≠K2 can depend on this reported UE capability.
[0066] To support Type II CJT codebook enhancement with delay offset compensation, techniques for handling invalid delay offset reports are described. In general, for each TRP, n=0,1, ..., NTRP-1, n≠nref in the delay offset report that is not the reference TRP, UE reports two values: a quantized delay offset Dn, offset with respect to the reference TRP, where Dn, offset can take codepoint of “out of range, ” and a 1 bit indicator dn, indicating whether the measured delay offset, plus a delay spread, is inside or outside a pre-defined range or interval. In some examples, for the delay offset report associated with the corresponding CJT codebook report, if at least one TRP n=0, 1, ..., NTRP-1, n≠nref has a quantized delay offset reported as “out of range, ” then the UE is not expected to report the CJT codebook. Similarly, in some examples, if at least one TRP n=0, 1, ..., NTRP-1, n≠nref has a 1 bit indicator dn, indicating that the measured delay offset plus a delay spread exceeds a pre-defined range or interval, then the UE is not expected to report the CJT codebook. In this manner, generation of a report that involves application of invalid delay offset values by the UE is prevented.
[0067] In some examples, for the delay offset report associated with the corresponding CJT codebook report, if at least one TRP n=0, 1, ..., NTRP-1, n≠nref has a quantized delay offset reported as “out of range” or a 1 bit indicator dn indicating that the measured delay offset plus delay spread exceeds a pre-defined range or interval, then the UE is still expected to report the CJT codebook. To do so, the UE may not perform delay offset compensation for any CSI-RS resource for CJT codebook. Alternatively, the UE may only perform delay offset compensation for the CSI-RS resource (s) for CJT codebook that have valid values in the corresponding delay offset report (e.g., not having a quantized delay offset reported as “out of range, ” and / or not having a 1 bit indicator dn indicating that the measured delay offset plus a delay spread exceeds a pre-defined range or interval) . For the CSI-RS resource for CJT codebook that has the corresponding quantized delay offset reported as “out of range” and / or a 1 bit indicator dn indicating that the measured delay offset plus a delay spread exceeds a pre-defined range or interval, the UE does not perform delay offset compensation. In some examples, when the UE supports the dynamic TRP selection in CSI report for CJT codebook and the network configures the dynamic TRP selection, the UE is not expected to select the TRP (e.g., CSI-RS resource) whose corresponding delay offset is “out of range. ”
[0068] In accordance with an aspect of the present disclosure, the CSI processing timeline can be relaxed to support Type II CJT codebook enhancement with delay offset compensation. In general, the CSI processing timeline is dictated by delay requirements Z and Z’ . Z is the minimum time duration specified in number of symbols between the end of the last symbol of CSI triggering PDCCH and the first uplink symbol carrying the CSI. Z’ is the minimum time duration specified in number of symbols between the end of the last symbol of the latest measurement resource and the first uplink symbol carrying the CSI. Values for Z and Z’ are specified in Table 5.4-1 (low latency) and Table 5.4-2 (regular latency) in 3GPP technical specification (TS) 38.214, reproduced below:
[0069] Table 5.1-1: CSI computation delay requirement 1
[0070] Table 5.4-2: CSI computation delay requirement 2
[0071] In some examples, CSI processing timeline relaxation can always be allowed when the network configures a UE to apply delay offset compensation for the CJT codebook calculation. In other examples, when the network configures a UE to apply delay offset compensation for the CJT codebook calculation, relaxation of the CSI processing timeline can depend on whether the delay offset and the corresponding CJT report are jointly triggered (e.g., triggered by the same CSI request) or separately triggered. For example, CSI processing timeline relaxation may only be allowed when the delay offset and the corresponding CJT report are jointly triggered.
[0072] CSI processing timeline relaxation can include relaxing Z (e.g., increasing the minimum time duration for Z) , relaxing Z’ (e.g., increasing the minimum time duration for Z’ ) , or both. In some examples, if processing time relaxation is allowed (and needed) , the relaxation can be applied on top of Z2 and Z’ 2 in Table 5.4-2, although relaxation of other delay requirements are within the scope of the present disclosure. For example, if processing timeline relaxation is needed for Z’ , then Z’ 2 can be scaled, such as by doubling Z’ 2 (e.g., Z’ = 2Z’ 2) . In another example, if processing timeline relaxation is needed for Z’ , then Z’ 2 can be increased by a number of symbols Y (e.g., Z’ = Z’ 2 + Y) . In some examples, Y can be reported as a UE capability. As another example, Y can be pre-determined and / or hardcoded in 3GPP technical specifications. In some examples, different values for Y can be reported and / or used for different sub-carrier spacings (SCS) .
[0073] In some examples, if processing timeline relaxation is needed for Z, then Z2 can be scaled, such as by doubling Z2 (e.g., Z = 2Z2) . In another example, if processing timeline relaxation is needed for Z, then Z2 can be increased by a number of symbols X (e.g., Z = Z2 + X) . In some examples, X can be reported as a UE capability. As another example, X can be pre-determined and / or hardcoded in 3GPP technical specifications. In some examples, different values for X can be reported and / or used for different sub-carrier spacings (SCS) .
[0074] In some examples, to support Type II CJT codebook enhancement with delay offset compensation, when the network configures a UE to apply delay offset compensation for the CJT codebook calculation, the UE can report capability that the reported delay offset is only valid for up to duration of T, where T is a number of symbols, slots, or milliseconds. When the UE reports the capability T, the UE is not expected to schedule CJT codebook report with delay offset compensation where the associated delay offset is more than T between a time point A and a time point B. The time point A can correspond to the end (e.g., last symbol) of the delay offset report. The time point B can correspond to, for example, the beginning (e.g., first symbol) of the CJT codebook report, the beginning (e.g., first symbol) of the CSI-RS resource used for the CJT codebook report, or the beginning (e.g., first symbol) of the DCI that triggers the CJT codebook report.
[0075] Although some of the techniques disclosed herein are described in the context of a delay offset compensation, in some examples these techniques can also be applied for types of offset compensation, such as frequency offset compensation and / or phase offset compensation.
[0076] FIG. 2 illustrates a flowchart of an example method 200 for CSI report enhancement with delay offset compensation, according to some implementations. For clarity of presentation, the description that follows generally describes method 200 in the context of the other figures in this description. For example, method 200 can be performed by UE 102 of FIG. 1. It will be understood that method 200 can be performed, for example, by any suitable system, environment, software, hardware, or a combination of systems, environments, software, and hardware, as appropriate. In some implementations, various steps of method 200 can be run in parallel, in combination, in loops, or in any order.
[0077] Operations of the method 200 include receiving an indication to apply offset compensation for one or more measurement resources associated with a CSI report (202) . The measurement resources can include, for example, CSI-RS resources, and the CSI report can include, for example, a Type II CJT codebook report. In some examples, the indication includes an indication to apply offset compensation to each of the one or more measurement resources associated with the CSI report. In some examples, the indication includes an indication to apply offset compensation to a subset of the one or more measurement resources associated with the CSI report. In some examples, the indication includes an indication to apply offset compensation for a CSI trigger state, and the CSI report is associated with the CSI trigger state. In some examples, the indication is an IE included in a message configuring the CSI report, or an IE in a message configuring a CSI trigger state.
[0078] At 204, the CSI report is generated based in part on application of the offset compensation to at least one of the measurement resources. The offset compensation can include at least one of a delay offset compensation, a frequency offset compensation, or a phase offset compensation. Once generated, the CSI report is transmitted to at least one TRP (206) .
[0079] In some examples, generating the CSI report includes obtaining offset information for the one or more measurement resources, applying the offset information to the one or more measurement resources to produce one or more compensated measurement resources, determining one or more CSI parameters based on the one or more compensated measurement resources, and generating the CSI report including the determined one or more CSI parameters. The one or more CSI parameters can include, for example, a PMI, a CQI, or an RI. The offset information can be obtained from an offset report (e.g., a delay offset report) that is stored in memory or another storage device.
[0080] The example method 200 shown in FIG. 2 can be modified or reconfigured to include additional, fewer, or different steps described herein (not shown in FIG. 2) , which can be performed in the order shown or in a different order.
[0081] FIG. 3 illustrates a flowchart of an example method 300 for CSI report enhancement with delay offset compensation, according to some implementations. For clarity of presentation, the description that follows generally describes method 300 in the context of the other figures in this description. For example, method 300 can be performed by base station 104 of FIG. 1. It will be understood that method 300 can be performed, for example, by any suitable system, environment, software, hardware, or a combination of systems, environments, software, and hardware, as appropriate. In some implementations, various steps of method 300 can be run in parallel, in combination, in loops, or in any order.
[0082] Operations of the method 300 include transmitting an indication to apply offset compensation for one or more measurement resources associated with a CSI report (302) . The measurement resources can include, for example, CSI-RS resources, and the CSI report can include, for example, a Type II CJT codebook report. In some examples, the indication includes an indication to apply offset compensation to each of the one or more measurement resources associated with the CSI report. In some examples, the indication includes an indication to apply offset compensation to a subset of the one or more measurement resources associated with the CSI report. In some examples, the indication includes an indication to apply offset compensation for a CSI trigger state, and the CSI report is associated with the CSI trigger state. In some examples, the indication is an IE included in a message configuring the CSI report, or an IE in a message configuring a CSI trigger state.
[0083] At 304, the CSI including one or more CSI parameters determined based in part on application of the offset compensation is received. The one or more CSI parameters can include, for example, a PMI, a CQI, and / or a RI, among others. In some examples, the CSI report is received in response to a trigger (e.g., a periodic or aperiodic trigger) , such as a triggering message (e.g., via DCI or RRC) or an event-based trigger. In some examples, the trigger for generation of the CSI report is configured by the base station. The base station can use one or more parameters or values of the CSI report to select one or more parameters for a UE, such as a particular precoding matrix for the UE. At 306, an indication of a configuration based in part on the one or more CSI parameters is transmitted to the UE. For example, the base station can send a message (e.g., via DCI or RRC) configuring one or more parameters of the UE, such as a precoding matrix, among others.
[0084] The example method 300 shown in FIG. 3 can be modified or reconfigured to include additional, fewer, or different steps (not shown in FIG. 3) , which can be performed in the order shown or in a different order.
[0085] FIG. 4 illustrates a UE 400, according to some implementations. The UE 400 may be similar to and substantially interchangeable with UE 102 of FIG. 1.
[0086] The UE 400 may be any mobile or non-mobile computing device, such as, for example, mobile phones, computers, tablets, industrial wireless sensors (for example, microphones, pressure sensors, thermometers, motion sensors, accelerometers, inventory sensors, electric voltage / current meters, etc. ) , video devices (for example, cameras, video cameras, etc. ) , wearable devices (for example, a smart watch) , relaxed-IoT devices.
[0087] The UE 400 may include processors 402, RF interface circuitry 404, memory / storage 406, user interface 408, sensors 410, driver circuitry 412, power management integrated circuit (PMIC) 414, antenna structure 416, and battery 418. The components of the UE 400 may be implemented as integrated circuits (ICs) , portions thereof, discrete electronic devices, or other modules, logic, hardware, software, firmware, or a combination thereof. The block diagram of FIG. 4 is intended to show a high-level view of some of the components of the UE 400. However, some of the components shown may be omitted, additional components may be present, and different arrangement of the components shown may occur in other implementations.
[0088] The components of the UE 400 may be coupled with various other components over one or more interconnects 420, which may represent any type of interface, input / output, bus (local, system, or expansion) , transmission line, trace, optical connection, etc. that allows various circuit components (on common or different chips or chipsets) to interact with one another.
[0089] The processors 402 may include processor circuitry such as, for example, baseband processor circuitry (BB) 422A, central processor unit circuitry (CPU) 422B, and graphics processor unit circuitry (GPU) 422C. The processors 402 may include any type of circuitry or processor circuitry that executes or otherwise operates computer-executable instructions, such as program code, software modules, or functional processes from memory / storage 406 to cause the UE 400 to perform operations as described herein.
[0090] In some implementations, the baseband processor circuitry 422A may access a communication protocol stack 424 in the memory / storage 406 to communicate over a 3GPP compatible network. In general, the baseband processor circuitry 422A may access the communication protocol stack to: perform user plane functions at a physical (PHY) layer, medium access control (MAC) layer, radio link control (RLC) layer, packet data convergence protocol (PDCP) layer, service data adaptation protocol (SDAP) layer, and PDU layer; and perform control plane functions at a PHY layer, MAC layer, RLC layer, PDCP layer, RRC layer, and a non-access stratum layer. In some implementations, the PHY layer operations may additionally / alternatively be performed by the components of the RF interface circuitry 404. The baseband processor circuitry 422A may generate or process baseband signals or waveforms that carry information in 3GPP-compatible networks. In some implementations, the waveforms for NR may be based cyclic prefix orthogonal frequency division multiplexing (OFDM) “CP-OFDM” in the uplink or downlink, and discrete Fourier transform spread OFDM “DFT-S-OFDM” in the uplink.
[0091] The memory / storage 406 may include one or more non-transitory, computer-readable media that includes instructions (for example, communication protocol stack 424) that may be executed by one or more of the processors 402 to cause the UE 400 to perform various operations described herein. The memory / storage 406 include any type of volatile or non-volatile memory that may be distributed throughout the UE 400. In some implementations, some of the memory / storage 406 may be located on the processors 402 themselves (for example, L1 and L2 cache) , while other memory / storage 406 is external to the processors 402 but accessible thereto via a memory interface. The memory / storage 406 may include any suitable volatile or non-volatile memory such as, but not limited to, dynamic random access memory (DRAM) , static random access memory (SRAM) , erasable programmable read only memory (EPROM) , electrically erasable programmable read only memory (EEPROM) , Flash memory, solid-state memory, or any other type of memory device technology.
[0092] The RF interface circuitry 404 may include transceiver circuitry and radio frequency front module (RFEM) that allows the UE 400 to communicate with other devices over a radio access network. The RF interface circuitry 404 may include various elements arranged in transmit or receive paths. These elements may include, for example, switches, mixers, amplifiers, filters, synthesizer circuitry, control circuitry, etc.
[0093] In the receive path, the RFEM may receive a radiated signal from an air interface via antenna structure 416 and proceed to filter and amplify (with a low-noise amplifier) the signal. The signal may be provided to a receiver of the transceiver that downconverts the RF signal into a baseband signal that is provided to the baseband processor of the processors 402.
[0094] In the transmit path, the transmitter of the transceiver up-converts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM may amplify the RF signal through a power amplifier prior to the signal being radiated across the air interface via the antenna 416. In various implementations, the RF interface circuitry 404 may be configured to transmit / receive signals in a manner compatible with NR access technologies.
[0095] The antenna 416 may include antenna elements to convert electrical signals into radio waves to travel through the air and to convert received radio waves into electrical signals. The antenna elements may be arranged into one or more antenna panels. The antenna 416 may have antenna panels that are omnidirectional, directional, or a combination thereof to enable beamforming and multiple input, multiple output communications. The antenna 416 may include microstrip antennas, printed antennas fabricated on the surface of one or more printed circuit boards, patch antennas, phased array antennas, etc. The antenna 416 may have one or more panels designed for specific frequency bands including bands in FR1 or FR2.
[0096] The user interface 408 includes various input / output (I / O) devices designed to enable user interaction with the UE 400. The user interface 408 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual means for accepting an input including, inter alia, one or more physical or virtual buttons (for example, a reset button) , a physical keyboard, keypad, mouse, touchpad, touchscreen, microphones, scanner, headset, or the like. The output device circuitry includes any physical or virtual means for showing information or otherwise conveying information, such as sensor readings, actuator position (s) , or other like information. Output device circuitry may include any number or combinations of audio or visual display, including, inter alia, one or more simple visual outputs / indicators (for example, binary status indicators such as light emitting diodes “LEDs” and multi-character visual outputs) , or more complex outputs such as display devices or touchscreens (for example, liquid crystal displays “LCDs, ” LED displays, quantum dot displays, projectors, etc. ) , with the output of characters, graphics, multimedia objects, and the like being generated or produced from the operation of the UE 400.
[0097] The sensors 410 may include devices, modules, or subsystems whose purpose is to detect events or changes in its environment and send the information (sensor data) about the detected events to some other device, module, subsystem, etc. Examples of such sensors include, inter alia, inertia measurement units including accelerometers, gyroscopes, or magnetometers; microelectromechanical systems or nanoelectromechanical systems including 3-axis accelerometers, 3-axis gyroscopes, or magnetometers; level sensors; temperature sensors (for example, thermistors) ; pressure sensors; image capture devices (for example, cameras or lensless apertures) ; light detection and ranging sensors; proximity sensors (for example, infrared radiation detector and the like) ; depth sensors; ambient light sensors; ultrasonic transceivers; microphones or other like audio capture devices; etc.
[0098] The driver circuitry 412 may include software and hardware elements that operate to control particular devices that are embedded in the UE 400, attached to the UE 400, or otherwise communicatively coupled with the UE 400. The driver circuitry 412 may include individual drivers allowing other components to interact with or control various input / output (I / O) devices that may be present within, or connected to, the UE 400. For example, driver circuitry 412 may include a display driver to control and allow access to a display device, a touchscreen driver to control and allow access to a touchscreen interface, sensor drivers to obtain sensor readings of sensor circuitry 410 and control and allow access to sensor circuitry 410, drivers to obtain actuator positions of electro-mechanic components or control and allow access to the electro-mechanic components, a camera driver to control and allow access to an embedded image capture device, audio drivers to control and allow access to one or more audio devices.
[0099] The PMIC 414 may manage power provided to various components of the UE 400. In particular, with respect to the processors 402, the PMIC 414 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion.
[0100] In some implementations, the PMIC 414 may control, or otherwise be part of, various power saving mechanisms of the UE 400. A battery 418 may power the UE 400, although in some examples the UE 400 may be mounted deployed in a fixed location, and may have a power supply coupled to an electrical grid. The battery 418 may be a lithium ion battery, a metal-air battery, such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, and the like. In some implementations, such as in vehicle-based applications, the battery 418 may be a typical lead-acid automotive battery.
[0101] FIG. 5 illustrates an access node 500 (e.g., a base station or gNB) , according to some implementations. The access node 500 may be similar to and substantially interchangeable with base station 104. The access node 500 may include processors 502, RF interface circuitry 504, core network (CN) interface circuitry 506, memory / storage circuitry 508, and antenna structure 510.
[0102] The components of the access node 500 may be coupled with various other components over one or more interconnects 512. The processors 502, RF interface circuitry 504, memory / storage circuitry 508 (including communication protocol stack 514) , antenna structure 510, and interconnects 512 may be similar to like-named elements shown and described with respect to FIG. 4. For example, the processors 502 may include processor circuitry such as, for example, baseband processor circuitry (BB) 516A, central processor unit circuitry (CPU) 516B, and graphics processor unit circuitry (GPU) 516C.
[0103] The CN interface circuitry 506 may provide connectivity to a core network, for example, a 5th Generation Core network (5GC) using a 5GC-compatible network interface protocol such as carrier Ethernet protocols, or some other suitable protocol. Network connectivity may be provided to / from the access node 500 via a fiber optic or wireless backhaul. The CN interface circuitry 506 may include one or more dedicated processors or FPGAs to communicate using one or more of the aforementioned protocols. In some implementations, the CN interface circuitry 506 may include multiple controllers to provide connectivity to other networks using the same or different protocols.
[0104] As used herein, the terms “access node, ” “access point, ” or the like may describe equipment that provides the radio baseband functions for data and / or voice connectivity between a network and one or more users. These access nodes can be referred to as BS, gNBs, RAN nodes, eNBs, NodeBs, RSUs, TRxPs or TRPs, and so forth, and can include ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell) . As used herein, the term “NG RAN node” or the like may refer to an access node 500 that operates in an NR or 5G system (for example, a gNB) , and the term “E-UTRAN node” or the like may refer to an access node 500 that operates in an LTE or 4G system (e.g., an eNB) . According to various implementations, the access node 500 may be implemented as one or more of a dedicated physical device such as a macrocell base station, and / or a low power (LP) base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.
[0105] In some implementations, all or parts of the access node 500 may be implemented as one or more software entities running on server computers as part of a virtual network, which may be referred to as a CRAN and / or a virtual baseband unit pool (vBBUP) . In V2X scenarios, the access node 500 may be or act as a “Road Side Unit. ” The term “Road Side Unit” or “RSU” may refer to any transportation infrastructure entity used for V2X communications. An RSU may be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, where an RSU implemented in or by a UE may be referred to as a “UE-type RSU, ” an RSU implemented in or by an eNB may be referred to as an “eNB-type RSU, ” an RSU implemented in or by a gNB may be referred to as a “gNB-type RSU, ” and the like.
[0106] Various components may be described as performing a task or tasks, for convenience in the description. Such descriptions should be interpreted as including the phrase “configured to. ” Reciting a component that is configured to perform one or more tasks is expressly intended not to invoke 35 U.S.C. § 112 (f) interpretation for that component.
[0107] For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, or methods as set forth in the example section below. For example, the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.
[0108] Any of the above-described examples may be combined with any other example (or combination of examples) , unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.
[0109] Although the embodiments above have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to embrace all such variations and modifications.
[0110] It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.
Claims
1.A method comprising:receiving an indication to apply offset compensation for one or more measurement resources associated with a channel state information (CSI) report;generating the CSI report based in part on application of the offset compensation to at least one of the measurement resources; andcausing transmission of the CSI report to at least one transmission reception point (TRP) .2.The method of claim 1, wherein the CSI report comprises a type II coherent joint transmission (CJT) codebook report.3.The method of claims 1 or 2, wherein the indication comprises an indication to apply offset compensation to each of the one or more measurement resources associated with the CSI report.4.The method of any preceding claim, wherein the indication comprises an indication to apply offset compensation to a subset of the one or more measurement resources associated with the CSI report.5.The method of any preceding claim, wherein the indication comprises an indication to apply offset compensation for a CSI trigger state, and wherein the CSI report is associated with the CSI trigger state.6.The method of any preceding claim, wherein the indication comprises an information element in a message configuring the CSI report.7.The method of any preceding claim, wherein the indication comprises an information element in a message configuring a CSI trigger state, and wherein the CSI report is associated with the CSI trigger state.8.The method of any preceding claim, wherein the one or more measurement resources comprise CSI-RS resources.9.The method of any preceding claim, wherein the offset compensation comprises at least one of a delay offset compensation, a frequency offset compensation, or a phase offset compensation.10.The method of any preceding claim, wherein generating the CSI report comprises:obtaining offset information for the one or more measurement resources;applying the offset information to the one or more measurement resources to produce one or more compensated measurement resources;determining one or more CSI parameters based on the one or more compensated measurement resources; andgenerating the CSI report including the determined one or more CSI parameters.11.The method of claim 10, wherein the one or more CSI parameters comprise at least one of a precoding matrix indicator (PMI) , a channel quality indicator (CQI) , or a rank indicator (RI) .12.The method of claim 10, wherein the offset information is obtained from an offset report.13.The method of claim 12, wherein there is a one to one correspondence between one or more tracking reference signal (TRS) resources associated with the offset report and the one or more measurement resources associated with the CSI report.14.The method of claim 12, wherein a correspondence between one or more tracking reference signal (TRS) resources associated with the offset report and the one or more measurement resources associated with the CSI report is configured by a network.15.The method of claim 10, further comprising:determining that offset information is invalid for at least one of the one or more measurement resources; andgenerating the CSI report without application of the offset compensation.16.The method of claim 10, further comprising:determining that offset information is invalid for at least one of the one or more measurement resources; andgenerating the CSI report based in part on application of the offset compensation to measurement resources other than the at least one of the one or more measurement resources.17.The method of any preceding claim, wherein a minimum time duration between an end of a last symbol of a message triggering the CSI report and a first uplink symbol carrying the CSI report is increased in response to the CSI report being jointly triggered with an offset report.18.The method of any preceding claim, wherein a minimum time duration between an end of a last symbol of a latest of the one or more measurement resources and a first uplink symbol carrying the CSI report is increased in response to the CSI report being jointly triggered with an offset report.19.The method of any preceding claim, wherein the method is performed by a user equipment (UE) or one or more baseband processors.20.One or more baseband processors configured to perform the method of any preceding claim.21.An apparatus comprising:one or more processors; andmemory storing instructions executable by the one or more processors to perform the method of any of claims 1 through 19.22.A method, comprising:causing transmission of an indication to apply offset compensation for one or more measurement resources associated with a channel state information (CSI) report;receiving the CSI report, wherein the CSI report includes one or more CSI parameters determined based in part on application of the offset compensation; andcausing transmission of an indication of a configuration based in part on the one or more CSI parameters.