Phase offset report for coherent joint transmission
Subband phase offset reporting and SRS port association techniques address synchronization challenges in multi-TRP CJT systems, improving performance by reducing overhead and maintaining coherency through efficient phase offset measurement and reporting.
Patent Information
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-09-27
- Publication Date
- 2026-04-02
AI Technical Summary
In multi-TRP coherent joint transmission (CJT) systems, maintaining synchronization between antenna elements of different TRPs is challenging due to time, frequency, and phase offsets caused by factors like UE location and hardware implementation, leading to performance degradation.
Implement techniques for subband phase offset reporting and SRS port association to measure and report phase offsets efficiently, reducing signaling overhead and enhancing synchronization by limiting phase offset reports to a subset of subbands and associating receive antenna ports with reference SRSs.
Enhances synchronization between TRPs, improving multi-TRP CJT performance by reducing signaling overhead and accounting for phase offsets, thereby maintaining coherency and enhancing communication efficiency.
Smart Images

Figure CN2024121967_02042026_PF_FP_ABST
Abstract
Description
PHASE OFFSET REPORT FOR COHERENT JOINT TRANSMISSIONTECHNICAL FIELD
[0001] This application relates generally to communication networks and, in particular, to technologies for phase offset reporting for coherent joint transmission.BACKGROUND
[0002] Third Generation Partnership Project (3GPP) Technical Specifications (TSs) define standards for wireless networks. These TSs describe aspects related to signaling traffic through systems that incorporate wireless networks.BRIEF DESCRIPTION OF THE DRAWINGS
[0003] FIG. 1 illustrates a network environment in accordance with some embodiments.
[0004] FIG. 2 illustrates an example of subband phase offset reporting in accordance with some embodiments.
[0005] FIG. 3 illustrates an example timeline for determining a reference sounding reference signal (SRS) for phase offset measurement based on a reference time in accordance with some embodiments.
[0006] FIG. 4 illustrates an example timeline for determining a reference time in accordance with some embodiments.
[0007] FIG. 5 illustrates an operation flow / algorithmic structure in accordance with some embodiments.
[0008] FIG. 6 illustrates another operation flow / algorithmic structure in accordance with some embodiments.
[0009] FIG. 7 illustrates another operation flow / algorithmic structure in accordance with some embodiments.
[0010] FIG. 8 illustrates a user equipment in accordance with some embodiments.
[0011] FIG. 9 illustrates a network device in accordance with some embodiments.DETAILED DESCRIPTION
[0012] The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular structures, architectures, interfaces, and techniques in order to provide a thorough understanding of the various aspects of various embodiments. However, it will be apparent to those skilled in the art having the benefit of the present disclosure that the various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of the present document, the phrases “A / B” and “A or B” mean (A) , (B) , or (A and B) ; and the phrase “based on A” means “based at least in part on A, ” for example, it could be “based solely on A” or it could be “based in part on A. ”
[0013] The following is a glossary of terms that may be used in this disclosure.
[0014] The term “circuitry” as used herein refers to, is part of, or includes hardware components that are configured to provide the described functionality. The hardware components may include an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) or memory (shared, dedicated, or group) , an application specific integrated circuit (ASIC) , a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA) , a programmable logic device (PLD) , a complex PLD (CPLD) , a high-capacity PLD (HCPLD) , a structured ASIC, or a programmable system-on-a-chip (SoC) ) , or a digital signal processor (DSP) . In some embodiments, the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality. The term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.
[0015] The term “processor circuitry” as used herein refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, or transferring digital data. The term “processor circuitry” may refer an application processor, baseband processor, a central processing unit (CPU) , a graphics processing unit, a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, or functional processes.
[0016] The term “interface circuitry” as used herein refers to, is part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term “interface circuitry” may refer to one or more hardware interfaces, for example, buses, I / O interfaces, peripheral component interfaces, and network interface cards.
[0017] The term “user equipment” or “UE” as used herein refers to a device with radio communication capabilities that may allow a user to access network resources in a communications network. The term “user equipment” or “UE” may be considered synonymous to, and may be referred to as, client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, or reconfigurable mobile device. Furthermore, the term “user equipment” or “UE” may include any type of wireless / wired device or any computing device including a wireless communications interface.
[0018] The term “computer system” as used herein refers to any type interconnected electronic devices, computer devices, or components thereof. Additionally, the term “computer system” or “system” may refer to various components of a computer that are communicatively coupled with one another. Furthermore, the term “computer system” or “system” may refer to multiple computer devices or multiple computing systems that are communicatively coupled with one another and configured to share computing or networking resources.
[0019] The term “resource” as used herein refers to a physical or virtual device, a physical or virtual component within a computing environment, or a physical or virtual component within a particular device, such as computer devices, mechanical devices, memory space, processor / CPU time, processor / CPU usage, processor and accelerator loads, hardware time or usage, electrical power, input / output operations, ports or network sockets, channel / link allocation, throughput, memory usage, storage, network, database and applications, or workload units. A “hardware resource” may refer to compute, storage, or network resources provided by physical hardware elements. A “virtualized resource” may refer to compute, storage, or network resources provided by virtualization infrastructure to an application, device, or system. The term “network resource” or “communication resource” may refer to resources that are accessible by computer devices / systems via a communications network. The term “system resources” may refer to any kind of shared entities to provide services, and may include computing or network resources. System resources may be considered as a set of coherent functions, network data objects or services, accessible through a server where such system resources reside on a single host or multiple hosts and are clearly identifiable.
[0020] The term “channel” as used herein refers to any transmission medium, either tangible or intangible, which is used to communicate data or a data stream. The term “channel” may be synonymous with or equivalent to “communications channel, ” “data communications channel, ” “transmission channel, ” “data transmission channel, ” “access channel, ” “data access channel, ” “link, ” “data link, ” “carrier, ” “radio-frequency carrier, ” or any other like term denoting a pathway or medium through which data is communicated. Additionally, the term “link” as used herein refers to a connection between two devices for the purpose of transmitting and receiving information.
[0021] The terms “instantiate, ” “instantiation, ” and the like as used herein refers to the creation of an instance. An “instance” also refers to a concrete occurrence of an object, which may occur, for example, during execution of program code.
[0022] The term “connected” may mean that two or more elements, at a common communication protocol layer, have an established signaling relationship with one another over a communication channel, link, interface, or reference point.
[0023] The term “network element” as used herein refers to physical or virtualized equipment or infrastructure used to provide wired or wireless communication network services. The term “network element” may be considered synonymous to or referred to as a networked computer, networking hardware, network equipment, network node, or a virtualized network function.
[0024] The term “information element” refers to a structural element containing one or more fields. The term “field” refers to individual contents of an information element, or a data element that contains content. An information element may include one or more additional information elements.
[0025] FIG. 1 illustrates a network environment 100 in accordance with some embodiments. The network environment 100 may include a UE 104 and a base station 108. The base station 108 may be coupled with a plurality of transmission-reception points (TRPs) 112 to provide one or more wireless access cells through which the UE 104 may communicate. As shown, the base station 108 may be coupled with two TRPs 112, e.g., TRP 1 and TRP 2. The base station 108 may use the TRPs 112 to provide geographically distributed points of transmission / reception to increase cell coverage and spatial diversity. Each of the TRPs may include a single TRP or a group of TRPs that are generally controlled as a single TRP.
[0026] While FIG. 1 illustrates the base station 108 coupled with the two TRPs directly, in other embodiments, more than one base station may be coupled with the two TRPs and the base stations may communicate with one other over a backhaul link to coordinate communications with the UE 104. The base station 108 and TRPs 112 may be collectively referred to as an access node 116.
[0027] The access node 116 may provide an air interface compatible with 3GPP technical specifications, such as those that define Fifth Generation (5G) new radio (NR) or later system standards. Depending on the technology, the base station 108 may be referred to as an eNB, gNB, an ng-NB, etc. The access node 116 may provide the UE 104 access to other networks, for example, a core network, a data network, etc.
[0028] The access node 116 may control the uplink and downlink operation through the physical (PHY) layer and media access control (MAC) layer. The configuration information may be provided to the UE 104 by the RRC layer.
[0029] The UE 104 and / or access node 116 may support multi-TRP (also referred to as mTRP) operation, in which the UE 104 communicates with multiple TRPs 112. The multi-TRP operation may be single-downlink control information (DCI) in which one DCI is used to schedule uplink or downlink transmissions with respect to more than one TRP. For example, as shown, TRP 1 may send DCI to the UE 104 that schedules uplink / downlink channel transmissions with respect to both the TRP 1 and the TRP 2. Alternatively, the multi-TRP operation may be multi-DCI in which separate DCIs are used to schedule uplink or downlink transmissions for respective TRPs. For example, TRP 1 may send a first DCI to the UE 104 that schedules uplink / downlink channel transmissions with respect to TRP 1 and TRP 2 may send a second DCI to the UE 104 that schedules uplink / downlink channel transmissions with respect to TRP 2.
[0030] In 3GPP NR Release (Rel) -15, multi-TRP operation is supported in transparent mode. Starting with Rel-16, explicit multi-TRP operation is supported. For example, Rel-16 supports five single-DCI multi-TRP non-coherent joint transmission (NCJT) schemes for physical downlink shared channel (PDSCH) . The five schemes include one spatial domain multiplexing (SDM) scheme, two frequency domain multiplexing (FDM) schemes, and two time domain multiplexing (TDM) schemes. Additionally, multi-DCI multi-TRP is supported for both PDSCH and physical uplink shared channel (PUSCH) .
[0031] In Rel-17, support for single-DCI multi-TRP TDM for PUSCH and physical uplink control channel (PUCCH) is added. For physical downlink control channel (PDCCH) , two single frequency network (SFN) schemes and one PDCCH repetition scheme are supported. Additionally, two SFN schemes are supported for PDSCH.
[0032] In Rel-18, support for single-DCI multi-TRP coherent joint transmission (CJT) is added for PDSCH. For PUSCH, simultaneous transmission across multiple panels (STxMP) schemes are supported. The STxMP schemes include single-DCI SFN, single-DCI SDM, and multi-DCI. Additionally, a single-DCI SFN STxMP scheme is supported for PUCCH.
[0033] In some instances, the network may use maximum ratio transmission (MRT) for multi-TRP transmissions. In MRT, the beamforming weights of different TRPs may be adjusted (e.g., based on channel conditions) to improve (e.g., maximize) the signal-to-noise ratio in the combined transmission.
[0034] Multi-TRP CJT operation may require synchronization between antenna elements of different TRPs to maintain coherency. If coherency can be maintained, multi-TRP CJT has the potential to provide better performance compared to NCJT. However, different TRPs may experience different offsets / drifts in time, frequency, and phase, e.g., due to the location and / or movement of the UE, the hardware implementation of the TRP, and / or other factors.
[0035] The UE may measure the time, frequency, and / or phase offset between different TRPs and may report measurement information to the network to enable synchronization between the TRPs (e.g., to maintain coherency) . The UE reporting may be particularly beneficial with CJT deployments with non-ideal synchronization and backhaul between the TRPs. The measurements may be performed on reference signals (e.g., channel state information -reference signals (CSI-RSs) ) transmitted by the respective TRPs. In some instances, the UE may perform aperiodic reporting of the measurement information on PUSCH (e.g., the report may be triggered by a DCI) .
[0036] Various embodiments herein provide techniques related to reporting phase offset for multi-TRP operation. For example, embodiments provide techniques for subband phase offset reporting. Additionally, embodiments provide techniques for sounding reference signal (SRS) port association for a phase offset report.
[0037] Subband phase offset reporting
[0038] FIG. 2 illustrates another network environment 200 in accordance with various embodiments. Aspects of the network environment 200 may correspond to the network environment 100.
[0039] The network environment 200 may include a UE 204 and multiple TRPs 212a-d. The UE 204 may receive reference signals 220a-d (e.g., CSI-RS) from the respective TRPs 212a-d. The reference signals 220a-d may be transmitted in a frequency bandwidth that is divided into a number, TSB, P, of subbands (e.g., subband 0, subband 1, ... subband TSB, P -1) .The subbands may have a size of, for example, 1, 2, 4, 8, or 16 physical resource blocks (PRBs) in the frequency domain. In some embodiments, the size of the subbands may be configured by the network.
[0040] The UE 204 may measure the phase offset of respective TRPs 212a-d at different subbands. In various embodiments, the UE 204 may report phase offset measurements for a subset of the subbands in the frequency bandwidth, e.g., a number NSB, P of subbands where NSB, P is less than TSB, P. For example, the UE 204 may generate and transmit a phase offset report 224. The phase offset report 224 may include phase measurements Φn, s, where n is an index of the respective TRP 212a-d (e.g., n= 0, 1, ... NTRP -1, where NTRP is the number of TRPs 212a-d) and s corresponds to the respective frequency subband of the subset of subbands to be reported (e.g., s = 0, 1, ...NSB, P -1) .
[0041] In some embodiments, the phase offsets may be reported based on a reference TRP. For example, the TRP 212a may be configured as the reference TRP (designated as Nref) . The UE 204 may measure the phase offset of the other TRPs 212b-d with reference to the reference TRP 212a. In some embodiments, the UE 204 may not report the phase offset for the reference TRP (e.g., n ≠ Nref) .
[0042] In some embodiments, the UE 204 may receive a configuration from the network to indicate the number of subbands for which phase offset is to be reported (NSB, P) . The number NSB, P may have any suitable value, such as 1, 2, 4, 8, 16, etc.
[0043] Limiting the phase offset report 224 to a subset of subbands may reduce the signaling overhead of the phase offset reports. For example, in some embodiments, the frequency bandwidth of communication with the TRPs 212a-d (e.g., the reference signals 220a-d) may be up to 275 PRBs. With a subband size of 1 PRB, there would be up to 275 subbands which would cause significant signaling overhead if phase offset for each of the subbands were reported. Additionally, under some circumstances (e.g., when the network performs MRT) , the phase offset for a given TRP may vary linearly across the frequency spectrum. Accordingly, if the network knows the phase offset for the subset of subbands, the phase offset for the other subbands can be inferred based on the linear relationship (e.g., slope) .
[0044] In some embodiments, a maximum number of subbands for which phase offset is reported (e.g., maximum value of NSB, P) may be predefined (e.g., defined in the 3GPP TS (s) ) . Additionally, or alternatively, the UE 204 may send UE capability information to the network that indicates the maximum number of subbands for which the phase offset is reported.
[0045] In some embodiments, the UE 204 may determine the NSB, P subbands to report from among the subbands of the frequency bandwidth. For example, the NSB, P subbands may be selected to distribute the NSB, P subbands with substantially equal frequency spacing. Substantially equal frequency spacing refers to spacing that is equal or as equal as possible given the number of NSB, P subbands and the total number of subbands TSB, P. For example, the sampling frequency may correspond to every or subbands.
[0046] In another example, the subset of subbands may include sequential subbands in the frequency domain. For example, the first NSB, P subbands, the last NSB, P subbands, or a middle subset of NSB, P subbands of the TSB, P subbands in the frequency domain may be selected for phase offset reporting.
[0047] In other embodiments, the network may explicitly configure the NSB, P subbands for which phase offset is to be reported by the UE. In some embodiments, the network may send a bitmap to indicate the NSB, P subbands. For example, the bitmap may include TSB, P bits, which individual bits having a first value (e.g., logic 1) to indicate that a respective subband is configured to have phase offset reported or a second value (e.g., logic 0)to indicate that the respective subband is not configured to have phase offset reported.
[0048] In another example, the network may use combinatorial indexing to indicate the NSB, P subbands. Combinatorialindexing may use fewer bits compared with a bitmap. For example, the combinatorial indexing may include where is the total number of combinatorial selections of NSB, P subbands from total TSB, P subbands, e.g.,
[0049] In some embodiments, the UE may indicate to the network the subbands for which phase offset measurements are reported. For example, the indication may be included in the report with the phase offset measurements. In some embodiments, the UE may indicate the subbands for which phase offset measurements are reported via a bitmap or combinatorial indexing (e.g., similar to the indication from the network described above) .
[0050] As discussed above, in some embodiments, the network may configure the number of subbands to be reported. In other embodiments, the network may configure a maximum number of subbands to be reported. The UE may report the phase offset for up to the maximum number of subbands (e.g., less than or equal to the maximum number) . The UE may include an indication of the number of subbands that are included in the report. For example, the UE may select the subbands to include in the report based on a signal quality of the associated reference signal, a measurement quality metric, and / or one or more other factors.
[0051] In other embodiments, the network may configure a first subset of subbands from among all the subbands in the frequency bandwidth. The UE may select a second subset of subbands from the first subset of subbands. The second subset may include all or less than all of the first subset. The UE may report the phase offset measurements for the second subset of subbands.
[0052] In some embodiments, the UE may receive an indication from the network of whether the network is to perform phase compensation for transmission of the reference signals (e.g., CSI-RS) on which the phase offset measurements are performed. The phase compensation may include, for example, MRT. In some embodiments, the UE may perform the phase offset measurements and / or select the subset of subbands on which to perform the phase offset measurements based on whether the network performs phase compensation. For example, the phase compensation may account for calibration error between the TRPs. There may still be phase offset due to over-the-air phase drift (which may be different for different UEs and / or when the same UE changes location) . The over-the-air phase drift may vary linearly across the frequency bandwidth. Accordingly, the UE may determine to report phase offset measurements for fewer subbands if phase compensation is performed by the network. Additionally, or alternatively, the UE may determine a granularity of the reported phase offset measurements based on whether phase compensation is performed by the network.
[0053] In some instances, the UE may perform phase measurements on all of the TSB, P subbands, even though the phase measurements are reported for a subset of the subbands. Alternatively, the UE may perform phase measurements on a subset of the TSB, P subbands (e.g., the NSB, P subbands for which the phase offset is reported) . In some embodiments, the network may send configuration information to the UE to indicate whether the UE should perform phase offset measurements on all of the subbands or the subset of subbands. In other embodiments, it may be up to UE implementation whether to perform the phase offset measurements on all of the subbands or the subset of subbands.
[0054] In some embodiments, the UE may determine whether to perform the phase offset measurements on all of the TSB, P subbands or the subset of NSB, P subbands based on whether the network performs phase compensation (e.g., MRT) . For example, if the network performs phase compensation, the UE may perform phase offset measurements on additional subbands in addition to the NSB, P subbands (e.g., all of the TSB, P subbands) . Since the phase offset for different subbands may have a linear relationship, the reported phase offset measurements may be refined based on the phase offset measurements for other subbands that are not reported (e.g., to correct for noise and / or other error in the phase offset measurements) . If phase compensation is not performed by the network, there may be no benefit / need to performing phase offset measurements on subbands that will not be reported since the phase offset measurements may not have a predictable mathematical relationship.
[0055] SRS port association for phase offset report
[0056] In embodiments, the network may perform its own phase offset measurements on SRSs transmitted by the UE. The UE may transmit the SRS with antenna switching (e.g., may transmit multiple SRSs with respective SRS ports) . The network may configure the TRPs to compensate for phase offset based on the SRS-based offset measurements and the CSI-RS-based offset measurements reported by the UE. However, the phase offset measurements reported by the UE may be affected by the receive antenna port used by the UE to perform the phase offset measurements.
[0057] Accordingly, various embodiments herein may include techniques to associate the receive antenna port used by the UE to perform the phase offset measurements on the CSI-RSs with a reference SRS transmitted by the UE (with a corresponding reference SRS port) . The reference SRS may be periodic, semi-persistent, or aperiodic. The reference SRS port may be associated with all phase offset measurements for the same report instance (e.g., the UE may use the same receive port, corresponding to the reference SRS port, for all of the phase offset measurements on respective TRPs for a given report) .
[0058] In some embodiments, the reference SRS may be the most recent SRS transmitted before a reference time. In some embodiments, the reference time may be configured for the UE by the network. The UE uses the receive port of the SRS port associated with the reference SRS to receive the CSI-RS resources from the TRPs for which phase offset is reported (e.g., the NTRP TRPs) . In some embodiments, the reference time may correspond to the beginning of the earliest CSI-RS resource of the set of CSI-RS resources the UE is to receive for a corresponding phase offset report. For example, the reference time may be the beginning of the earliest CSI-RS resource or may be an offset before the beginning of the earliest CSI-RS resource (e.g., to allow for some processing time) .
[0059] FIG. 3 illustrates an example timeline 300 of communications by a UE (e.g., UE 104 and / or 204) in accordance with some embodiments. As shown, the UE may receive CSI-RSs 304a-d in respective CSI-RS resources (e.g., from respective TRPs) . The UE may perform phase offset measurements based on the CSI-RSs 304a-d and generate a phase offset report 308 for transmission based on the phase offset measurements.
[0060] The UE may additionally transmit SRSs 312a-c. The SRSs 312a-c may be transmitted using different SRS ports. The UE may identify a reference time for determination of the reference SRS. As shown, the reference time may be the beginning of the earliest CSI-RS resource of the CSI-RSs 304a-d. In some embodiments, the reference time may be earlier than the earliest CSI-RS resource by an offset.
[0061] The reference SRS may be the latest SRS that is transmitted prior to the reference time. Accordingly, in the timeline 300, the SRS 312b is the reference SRS. It is noted that SRS 312c is transmitted prior to CSI-RSs 304c and 304d but after CSI-RSs 304a and 304b. Since the same reference SRS port is used to receive all of the CSI-RSs 304a-d, the SRS 312b is not used as the reference SRS.
[0062] However, in other embodiments, different CSI-RSs for a same phase offset report may be associated with different SRS ports. For example, in the timeline 300, SRS 312b may be the reference SRS for CSI-RSs 304a and 304b, while SRS 312c may be the reference SRS for CSI-RSs 304c and 304d.
[0063] FIG. 4 illustrates another example timeline 400 of communications by a UE (e.g., UE 104 and / or 204) in accordance with some embodiments. The UE may receive sets of CSI-RSs 404a-d, 408a-d, and 412a-d at respective CSI-RS occasions. Within the respective sets, the CSI-RSs may be received from respective TRPs (e.g., the NTRP TRPs) . The UE may generate a phase offset report 416 for transmission to the network.
[0064] As shown, a CSI reference resource may be defined. The CSI reference resource may correspond to a latest resource in which a CSI-RS may be received to be included in the phase offset report 416. For example, the CSI reference resource may be as defined in 3GPP TS38.214, Section 5.2.2.5, V18.3.0 (July 3, 2024) . The UE may identify the CSI-RS resources on which to perform the phase offset measurements for the phase offset report 416 as the most recent CSI-RS resources for the NTRP TRPs that are at or before the CSI reference resource. Accordingly, in the timeline 400, the CSI-RSs 408a-d may be used for the phase offset report 416.
[0065] The reference time may be determined based on the set of CSI-RSs 408a-d that are used for the phase offset report 416. For example, as shown in FIG. 4, the reference time may be the beginning of the earliest CSI-RS resource of the CSI-RSs 408a-d. Accordingly, the reference SRS may be the most recent SRS that is transmitted prior to the reference time.
[0066] Other techniques for determining the reference time may also be used. For example, the reference time may correspond to the DCI (PDCCH) that triggers the phase offset report (e.g., the reference time may be the time at which the DCI is received or separated from the time at which the DCI is received by an offset) . In another example, the reference time may correspond to the CSI reference resource (e.g., the CSI reference resource shown in FIG. 4) . For example, the reference time may be the time of the CSI reference resource or separated from the CSI reference resource by an offset.
[0067] As discussed above, in some embodiments the reference time may be subject to a time offset, also referred to as a timeline relaxation Tr. For example, the reference time may be the reference time illustrated in FIG. 3 or FIG. 4 minus Tr. In some embodiments, the value of Tr may be predefined in the 3GPP TS (s) . In other embodiments, the UE may report UE capability information that indicates a supported timeline relaxation Tr. Example values of Tr may include 7, 14, 21, or 28 symbols, etc.
[0068] Example operation flow / algorithmic structures
[0069] FIG. 5 illustrates an operation flow / algorithmic structure 500 in accordance with some embodiments. The operation flow / algorithmic structure 500 may be performed by a UE, such as UE 104, UE 800, or components therein, for example, baseband processor 804A.
[0070] The operation flow / algorithmic structure 500 may include, at 504, determining a subset of subbands from among a total number of subbands associated with respective TRPs of a set of TRPs. For example, the UE may receive configuration information from the network that indicates a number of subbands to include in the subset, a maximum number of subbands to include in the subset, and / or specific individual subbands to include in the subset. The UE may determine the subset of subbands based on the configuration information. The subset of subbands may include subbands that are spread within the frequency bandwidth of the reference signals transmitted by the TRPs and / or consecutive subbands in the frequency domain. In some embodiments, the UE may send UE capability information that indicates one or more UE capabilities associated with phase offset reporting, such as a maximum number of subbands the UE is capable of reporting in a phase offset report instance.
[0071] The operation flow / algorithmic structure 500 may further include, at 508, obtaining, on reference signals from the respective TRPs, phase offset measurements in the subset of subbands. The reference signals may be, for example, CSI-RSs. The UE may or may not perform measurements on other subbands that are not included in the subset of subbands.
[0072] The operation flow / algorithmic structure 500 may further include, at 512, generating, based on the offset measurements in the subset of subbands, a phase offset report for transmission to a network. In some embodiments, the UE may receive a DCI to trigger the phase offset report.
[0073] FIG. 6 illustrates another operation flow / algorithmic structure 600 in accordance with some embodiments. The operation flow / algorithmic structure 600 may be performed by a UE, such as UE 104, UE 800, or components therein, for example, baseband processor 804A.
[0074] The operation flow / algorithmic structure 600 may include, at 604, identifying a reference time. For example, the reference time may be as shown and described with respect to FIG. 3 and / or FIG. 4.
[0075] The operation flow / algorithmic structure 600 may further include, at 608, determining a SRS port that corresponds to a most recent SRS transmitted prior to the reference time.
[0076] The operation flow / algorithmic structure 600 may further include, at 612, receiving, with a receive antenna port that corresponds to the reference SRS port, CSI-RSs from respective TRPs. In some embodiments, the UE may use the same receive antenna port for all CSI-RSs associated with a same phase offset report. Alternatively, the UE may use different receive antenna ports to receive different CSI-RSs associated with the same phase offset report.
[0077] The operation flow / algorithmic structure 600 may further include, at 616, obtaining, based on the CSI-RSs, phase offset measurements for the respective TRPs.
[0078] The operation flow / algorithmic structure 600 may further include, at 620, generating a phase offset report based on the phase offset measurements. The UE may transmit the phase offset report to the network. For example, the phase offset report may be dynamically triggered, e.g., by a DCI.
[0079] FIG. 7 illustrates another operation flow / algorithmic structure 700 in accordance with some embodiments. The operation flow / algorithmic structure 700 may be performed by a network device, such as an access node (e.g., access node 116) , base station (e.g., base station 108) , TRP (e.g., TRP 112) , and / or network device 900, or components therein, for example, baseband processor 904A.
[0080] The operation flow / algorithmic structure 700 may include, at 704, encoding, for transmission to a UE, configuration information for a subset of subbands on which the UE is to report phase offset measurements for a plurality of TRPs that are used for coherent joint transmission to the UE. For example, the configuration information may indicate a number of subbands to include in the subset, a maximum number of subbands to include in the subset, and / or specific individual subbands to include in the subset.
[0081] The operation flow / algorithmic structure 700 may further include, at 708, receiving a phase offset report based on the configuration information. The phase offset report may include phase offset measurements for the subset of subbands.
[0082] The operation flow / algorithmic structure 700 may further include, at 712, updating a configuration of one or more of the TRPs based on the phase offset report.
[0083] Example devices
[0084] FIG. 8 illustrates a UE 800 in accordance with some embodiments. The UE 800 may be similar to and substantially interchangeable with UE 104.
[0085] The UE 800 may be any mobile or non-mobile computing device, such as, for example, mobile phones, computers, tablets, industrial wireless sensors (for example, microphones, carbon dioxide sensors, pressure sensors, humidity sensors, thermometers, motion sensors, accelerometers, laser scanners, fluid level sensors, inventory sensors, electric voltage / current meters, or actuators) , video surveillance / monitoring devices (for example, cameras or video cameras) , wearable devices (for example, a smart watch) , or Internet-of-things devices.
[0086] The UE 800 may include processors 804, RF interface circuitry 808, memory / storage 812, user interface 816, sensors 820, driver circuitry 822, power management integrated circuit (PMIC) 824, antenna 826, and battery 828. The components of the UE 800 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. 8 is intended to show a high-level view of some of the components of the UE 800. 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.
[0087] The components of the UE 800 may be coupled with various other components over one or more interconnects 832, which may represent any type of interface, input / output, bus (local, system, or expansion) , transmission line, trace, or optical connection that allows various circuit components (on common or different chips or chipsets) to interact with one another.
[0088] The processors 804 may include processor circuitry such as, for example, baseband processor circuitry (BB) 804A, central processor unit circuitry (CPU) 804B, and graphics processor unit circuitry (GPU) 804C. The processors 804 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 812 to cause the UE 800 to perform phase offset reporting as described herein. The processors 804 may also include interface circuitry 804D to enable communication by, for example, communicatively coupling the processor circuitry with one or more other components of the UE 800.
[0089] In some embodiments, the baseband processor 804A may access a communication protocol stack 836 in the memory / storage 812 to communicate over a 3GPP compatible network. In general, the baseband processor 804A may access the communication protocol stack 836 to: perform user plane functions at a PHY layer, MAC layer, RLC layer, PDCP layer, SDAP layer, and PDU layer; and perform control plane functions at a PHY layer, MAC layer, RLC layer, PDCP layer, RRC layer, and a NAS layer. In some embodiments, the PHY layer operations may additionally / alternatively be performed by the components of the RF interface circuitry 808.
[0090] The baseband processor 804A may generate or process baseband signals or waveforms that carry information in 3GPP-compatible networks. In some embodiments, the waveforms for NR may be based on cyclic prefix OFDM (CP-OFDM) in the uplink or downlink, and discrete Fourier transform spread OFDM (DFT-S-OFDM) in the uplink.
[0091] The memory / storage 812 may include one or more non-transitory, computer-readable media that includes instructions (for example, communication protocol stack 836) that may be executed by one or more of the processors 804 to cause the UE 800 to perform phase offset reporting as described herein.
[0092] The memory / storage 812 includes any type of volatile or non-volatile memory that may be distributed throughout the UE 800. In some embodiments, some of the memory / storage 812 may be located on the processors 804 themselves (for example, memory / storage 812 may be part of a chipset that corresponds to the baseband processor 804A) , while other memory / storage 812 is external to the processors 804 but accessible thereto via a memory interface. The memory / storage 812 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.
[0093] The RF interface circuitry 808 may include transceiver circuitry and a radio frequency front module (RFEM) that allows the UE 800 to communicate with other devices over a radio access network. The RF interface circuitry 808 may include various elements arranged in transmit or receive paths. These elements may include, for example, switches, mixers, amplifiers, filters, synthesizer circuitry, and control circuitry.
[0094] In the receive path, the RFEM may receive a radiated signal from an air interface via antenna 826 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 down-converts the RF signal into a baseband signal that is provided to the baseband processor of the processors 804.
[0095] 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 826.
[0096] In various embodiments, the RF interface circuitry 808 may be configured to transmit / receive signals in a manner compatible with NR access technologies.
[0097] The antenna 826 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 826 may have antenna panels that are omnidirectional, directional, or a combination thereof to enable beamforming and multiple input, multiple output communications. The antenna 826 may include microstrip antennas, printed antennas fabricated on the surface of one or more printed circuit boards, patch antennas, or phased array antennas. The antenna 826 may have one or more panels designed for specific frequency bands including bands in FR1 or FR2.
[0098] The user interface 816 includes various input / output (I / O) devices designed to enable user interaction with the UE 800. The user interface 816 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, and projectors) , with the output of characters, graphics, multimedia objects, and the like being generated or produced from the operation of the UE 800.
[0099] The sensors 820 may include devices, modules, or subsystems whose purpose is to detect events or changes in their environment and send the information (sensor data) about the detected events to some other device, module, or subsystem. Examples of such sensors include inertia measurement units comprising accelerometers, gyroscopes, or magnetometers; microelectromechanical systems or nanoelectromechanical systems comprising 3-axis accelerometers, 3-axis gyroscopes, or magnetometers; level sensors; flow sensors; temperature sensors (for example, thermistors) ; pressure sensors; barometric pressure sensors; gravimeters; altimeters; 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; and microphones or other like audio capture devices.
[0100] The driver circuitry 822 may include software and hardware elements that operate to control particular devices that are embedded in the UE 800, attached to the UE 800, or otherwise communicatively coupled with the UE 800. The driver circuitry 822 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 800. For example, driver circuitry 822 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 sensors 820 and control and allow access to sensors 820, 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.
[0101] The PMIC 824 may manage power provided to various components of the UE 800. In particular, with respect to the processors 804, the PMIC 824 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion.
[0102] A battery 828 may power the UE 800, although in some examples the UE 800 may be mounted deployed in a fixed location and may have a power supply coupled to an electrical grid. The battery 828 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 828 may be a typical lead-acid automotive battery.
[0103] FIG. 9 illustrates a network device 900 in accordance with some embodiments. The network device 900 may be similar to, and substantially interchangeable with access node 116, base station 108, and / or TRPs 112.
[0104] The network device 900 may include processors 904, RF interface circuitry 908 (if implemented as a base station) , core network (CN) interface circuitry 914, memory / storage circuitry 912, and antenna structure 926.
[0105] The components of the network device 900 may be coupled with various other components over one or more interconnects 928.
[0106] The processors 904, RF interface circuitry 908, memory / storage circuitry 912 (including communication protocol stack 910) , antenna structure 926, and interconnects 928 may be similar to like-named elements shown and described with respect to FIG. 8.
[0107] The processors 904 may include processor circuitry such as, for example, baseband processor circuitry (BB) 904A, central processor unit circuitry (CPU) 904B, and graphics processor unit circuitry (GPU) 904C. The processors 904 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 circuitry 912 to cause the network device 900 to perform operations associated with phase offset reporting and / or coherent joint transmission as described herein. The processors 904 may also include interface circuitry 904D to communicatively couple the processor circuitry with one or more other components of the network device 900.
[0108] The CN interface circuitry 914 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 network device 900 via a fiber optic or wireless backhaul. The CN interface circuitry 914 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 914 may include multiple controllers to provide connectivity to other networks using the same or different protocols.
[0109] 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.
[0110] 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, or network element 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.
[0111] Examples
[0112] In the following sections, further exemplary embodiments are provided.
[0113] Example 1 includes a method comprising: determining a subset of subbands from among a total number of subbands associated with respective transmission-reception points (TRPs) of a set of TRPs; obtaining, on reference signals from the respective TRPs, phase offset measurements in the subset of subbands; and generating, based on the phase offset measurements in the subset of subbands, a phase offset report for transmission to a network.
[0114] Example 2 includes the method of example 1 or some other example herein, further comprising receiving configuration information from the network, wherein the subset of subbands is determined based on the configuration information.
[0115] Example 3 includes the method of example 2 or some other example herein, further comprising encoding, for transmission to the network, user equipment (UE) capability information to indicate a maximum number of subbands that are supported to be included in the subset of subbands.
[0116] Example 4 includes the method of example 2 or some other example herein, wherein the configuration information indicates a number of subbands to be included in the subset of subbands, and wherein determining the subset of subbands includes: selecting the number of subbands spaced across a frequency bandwidth of the reference signals; or selecting sequential subbands in a frequency domain from the total number of subbands.
[0117] Example 5 includes the method of example 2 or some other example herein, wherein the configuration information indicates respective individual subbands to be included in the subset of subbands.
[0118] Example 6 includes the method of example 5 or some other example herein, wherein the configuration information includes a bitmap or combinatorial indexing to indicate the respective individual subbands.
[0119] Example 7 includes the method of example 2 or some other example herein, wherein the configuration information indicates a maximum number of subbands to include in the subset of subbands, and wherein determining the subset of subbands includes selecting up to the maximum number of subbands to include in the subset of subbands.
[0120] Example 8 includes the method of example 1 or some other example herein, wherein the phase offset report includes an indication of individual subbands that are included in the subset of subbands.
[0121] Example 9 includes the method of example 1 or some other example herein, further comprising receiving, from the network, an indication of whether the network is to perform phase compensation on the reference signals.
[0122] Example 10 includes the method of example 9 or some other example herein, further comprising obtaining measurements on additional subbands outside of the subset of subbands based on the indication indicating that the network is to perform phase compensation on the reference signals.
[0123] Example 11 includes an apparatus comprising processing circuitry to: identify a reference time; determine a reference sounding reference signal (SRS) port that corresponds to a most recent SRS transmitted prior to the reference time; receive, with a receive antenna port that corresponds to the reference SRS port, channel state information (CSI) -reference signals (RSs) from respective transmission-reception points (TRPs) ; obtain, based on the CSI-RSs, phase offset measurements for the respective TRPs; and generate a phase offset report for transmission based on the phase offset measurements. The apparatus of Example 11 further comprises interface circuitry coupled to the processing circuitry to enable communication.
[0124] Example 12 includes the apparatus of example 11 or some other example herein, wherein the reference time corresponds to a beginning of an earliest CSI-RS resource in which one of the CSI-RSs is received.
[0125] Example 13 includes the apparatus of example 12 or some other example herein, wherein the reference time is a relaxation time before the beginning of the earliest CSI-RS resource.
[0126] Example 14 includes the apparatus of example 13 or some other example herein, wherein the processing circuitry is further to generate, for transmission to a network, user equipment (UE) capability information to indicate a supported relaxation time.
[0127] Example 15 includes the apparatus of example 12 or some other example herein, wherein the processing circuitry is further to identify the CSI-RSs for receiving with the receive antenna port based on the CSI-RSs being received no earlier than a CSI reference resource.
[0128] Example 16 includes the apparatus of example 11 or some other example herein, wherein the reference time corresponds to a downlink control information (DCI) that triggers the phase offset report or a CSI reference resource.
[0129] Example 17 includes a method comprising: encoding, for transmission to a user equipment (UE) , configuration information for a subset of subbands on which the UE is to report phase offset measurements for a plurality of transmission-reception points (TRPs) that are used for coherent joint transmission to the UE; receiving a phase offset report based on the configuration information; and updating a configuration of one or more of the TRPs based on the phase offset report.
[0130] Example 18 includes the method of example 17 or some other example herein, further comprising receiving, from the UE, UE capability information that indicates a maximum number of subbands that are supported to be included in the subset of subbands.
[0131] Example 19 includes the method of example 17 or some other example herein, wherein the configuration information indicates a number of subbands to be included in the subset of subbands, and wherein the subset of subbands includes: the number of subbands spaced across a frequency bandwidth of the reference signals; or sequential subbands in a frequency domain.
[0132] Example 20 includes the method of example 17 or some other example herein, wherein the configuration information indicates respective individual subbands to be included in the subset of subbands.
[0133] Example 21 includes the method of example 20 or some other example herein, wherein the configuration information includes a bitmap or combinatorial indexing to indicate the respective individual subbands.
[0134] Example 22 includes the method of example 17 or some other example herein, wherein the configuration information indicates a maximum number of subbands that the UE can include in the subset of subbands.
[0135] Example 23 includes the method of example 17 or some other example herein, wherein the phase offset report includes an indication of individual subbands that are included in the subset of subbands.
[0136] Example 24 includes the method of example 17 or some other example herein, further comprising encoding, for transmission to the UE, an indication of whether a network is to perform phase compensation on reference signals that are used for the phase offset measurements.
[0137] Example 25 includes the method of example 17 or some other example herein, further comprising: identifying a reference sounding reference signal (SRS) associated with the phase offset measurements; and updating the configuration of the one or more TRPs based on the phase offset report and the reference SRS.
[0138] Another example may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1-25, or any other method or process described herein.
[0139] Another example may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1-25, or any other method or process described herein.
[0140] Another example may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of examples 1-25, or any other method or process described herein.
[0141] Another example may include a method, technique, or process as described in or related to any of examples 1-25, or portions or parts thereof.
[0142] Another example may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-25, or portions thereof.
[0143] Another example may include a signal as described in or related to any of examples 1-25, or portions or parts thereof.
[0144] Another example may include a datagram, information element, packet, frame, segment, PDU, or message as described in or related to any of examples 1-25, or portions or parts thereof, or otherwise described in the present disclosure.
[0145] Another example may include a signal encoded with data as described in or related to any of examples 1-25, or portions or parts thereof, or otherwise described in the present disclosure.
[0146] Another example may include a signal encoded with a datagram, IE, packet, frame, segment, PDU, or message as described in or related to any of examples 1-25, or portions or parts thereof, or otherwise described in the present disclosure.
[0147] Another example may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-25, or portions thereof.
[0148] Another example may include a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or process as described in or related to any of examples 1-25, or portions thereof.
[0149] Another example may include a signal in a wireless network as shown and described herein.
[0150] Another example may include a method of communicating in a wireless network as shown and described herein.
[0151] Another example may include a system for providing wireless communication as shown and described herein.
[0152] Another example may include a device for providing wireless communication as shown and described herein.
[0153] 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.
[0154] 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.
Claims
1.A method comprising:determining a subset of subbands from among a total number of subbands associated with respective transmission-reception points (TRPs) of a set of TRPs;obtaining, on reference signals from the respective TRPs, phase offset measurements in the subset of subbands; andgenerating, based on the phase offset measurements in the subset of subbands, a phase offset report for transmission to a network.2.The method of claim 1, further comprising receiving configuration information from the network, wherein the subset of subbands is determined based on the configuration information.3.The method of claim 2, further comprising encoding, for transmission to the network, user equipment (UE) capability information to indicate a maximum number of subbands that are supported to be included in the subset of subbands.4.The method of claim 2, wherein the configuration information indicates a number of subbands to be included in the subset of subbands, and wherein determining the subset of subbands includes:selecting the number of subbands spaced across a frequency bandwidth of the reference signals; orselecting sequential subbands in a frequency domain from the total number of subbands.5.The method of claim 2, wherein the configuration information indicates respective individual subbands to be included in the subset of subbands.6.The method of claim 5, wherein the configuration information includes a bitmap or combinatorial indexing to indicate the respective individual subbands.7.The method of claim 2, wherein the configuration information indicates a maximum number of subbands to include in the subset of subbands, and wherein determining the subset of subbands includes selecting up to the maximum number of subbands to include in the subset of subbands.8.The method of claim 1, wherein the phase offset report includes an indication of individual subbands that are included in the subset of subbands.9.The method of claim 1, further comprising receiving, from the network, an indication of whether the network is to perform phase compensation on the reference signals.10.The method of claim 9, further comprising obtaining measurements on additional subbands outside of the subset of subbands based on the indication indicating that the network is to perform phase compensation on the reference signals.11.An apparatus comprising:processing circuitry to:identify a reference time;determine a reference sounding reference signal (SRS) port that corresponds to a most recent SRS transmitted prior to the reference time;receive, with a receive antenna port that corresponds to the reference SRS port, channel state information (CSI) -reference signals (RSs) from respective transmission-reception points (TRPs) ;obtain, based on the CSI-RSs, phase offset measurements for the respective TRPs; andgenerate a phase offset report for transmission based on the phase offset measurements; andinterface circuitry coupled to the processing circuitry to enable communication.12.The apparatus of claim 11, wherein the reference time corresponds to a beginning of an earliest CSI-RS resource in which one of the CSI-RSs is received.13.The apparatus of claim 12, wherein the reference time is a relaxation time before the beginning of the earliest CSI-RS resource.14.The apparatus of claim 13, wherein the processing circuitry is further to generate, for transmission to a network, user equipment (UE) capability information to indicate a supported relaxation time.15.The apparatus of claim 12, wherein the processing circuitry is further to identify the CSI-RSs for receiving with the receive antenna port based on the CSI-RSs being received no earlier than a CSI reference resource.16.The apparatus of claim 11, wherein the reference time corresponds to a downlink control information (DCI) that triggers the phase offset report or a CSI reference resource.17.A method comprising:encoding, for transmission to a user equipment (UE) , configuration information for a subset of subbands on which the UE is to report phase offset measurements for a plurality of transmission-reception points (TRPs) that are used for coherent joint transmission to the UE;receiving a phase offset report based on the configuration information; andupdating a configuration of one or more of the TRPs based on the phase offset report.18.The method of claim 17, further comprising receiving, from the UE, UE capability information that indicates a maximum number of subbands that are supported to be included in the subset of subbands.19.The method of claim 17, wherein the configuration information indicates a number of subbands to be included in the subset of subbands, and wherein the subset of subbands includes:the number of subbands spaced across a frequency bandwidth of the reference signals; orsequential subbands in a frequency domain.20.The method of claim 17, wherein the configuration information indicates respective individual subbands to be included in the subset of subbands.21.The method of claim 20, wherein the configuration information includes a bitmap or combinatorial indexing to indicate the respective individual subbands.22.The method of claim 17, wherein the configuration information indicates a maximum number of subbands that the UE can include in the subset of subbands.23.The method of claim 17, wherein the phase offset report includes an indication of individual subbands that are included in the subset of subbands.24.The method of claim 17, further comprising encoding, for transmission to the UE, an indication of whether a network is to perform phase compensation on reference signals that are used for the phase offset measurements.25.The method of claim 17, further comprising:identifying a reference sounding reference signal (SRS) associated with the phase offset measurements; andupdating the configuration of the one or more TRPs based on the phase offset report and the reference SRS.
Citation Information
Patent Citations
Communication method, terminal and network equipment
CN117063504A
Communicating channel state information (CSI) of multiple transmission points
US20130003788A1
CSI reporting for multi-TRP coherent joint-transmission
US20240284220A1