WO2025171656A1 - Améliorations apportées à un rapport de propriétés de canal du domaine temporel - Google Patents
Améliorations apportées à un rapport de propriétés de canal du domaine temporelInfo
- Publication number
- WO2025171656A1 WO2025171656A1 PCT/CN2024/077429 CN2024077429W WO2025171656A1 WO 2025171656 A1 WO2025171656 A1 WO 2025171656A1 CN 2024077429 W CN2024077429 W CN 2024077429W WO 2025171656 A1 WO2025171656 A1 WO 2025171656A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- tdcp
- report
- reference signal
- threshold
- sinr
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
Definitions
- This application relates generally to wireless communication systems, including systems, devices, apparatuses, and methods in which a user equipment (UE) is configured to generate and transmit a time domain channel properties (TDCP) report.
- UE user equipment
- TDCP time domain channel properties
- Wireless mobile communication technology uses various standards and protocols to transmit data between a network device (e.g., a base station, a radio head, etc. ) and a wireless communication device.
- Wireless communication system standards and protocols can include, for example, 3rd Generation Partnership Project (3GPP) long term evolution (LTE) (e.g., 4G) , 3GPP new radio (NR) (e.g., 5G) , and IEEE 802.11 standard for wireless local area networks (WLAN) (commonly known to industry groups as ) .
- 3GPP 3rd Generation Partnership Project
- LTE long term evolution
- NR 3GPP new radio
- IEEE 802.11 for wireless local area networks (WLAN) (commonly known to industry groups as ) .
- 3GPP radio access networks
- RANs can include, for example, global system for mobile communications (GSM) , enhanced data rates for GSM evolution (EDGE) RAN (GERAN) , Universal Terrestrial Radio Access Network (UTRAN) , Evolved Universal Terrestrial Radio Access Network (E-UTRAN) , and/or Next-Generation Radio Access Network (NG-RAN) .
- GSM global system for mobile communications
- EDGE enhanced data rates for GSM evolution
- GERAN GERAN
- UTRAN Universal Terrestrial Radio Access Network
- E-UTRAN Evolved Universal Terrestrial Radio Access Network
- NG-RAN Next-Generation Radio Access Network
- Each RAN may use one or more radio access technologies (RATs) to perform communication between the network device and the UE.
- RATs radio access technologies
- the GERAN implements GSM and/or EDGE RAT
- the UTRAN implements universal mobile telecommunication system (UMTS) RAT or other 3GPP RAT
- the E-UTRAN implements LTE RAT (sometimes simply referred to as LTE)
- NG-RAN implements NR RAT (sometimes referred to herein as 5G RAT, 5G NR RAT, or simply NR)
- the E-UTRAN may also implement NR RAT.
- NG-RAN may also implement LTE RAT.
- a network device used by a RAN may correspond to that RAN.
- E-UTRAN network device is an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly denoted as evolved Node B, enhanced Node B, eNodeB, or eNB) .
- E-UTRAN Evolved Universal Terrestrial Radio Access Network
- eNodeB enhanced Node B
- NG-RAN network device is a next generation Node B (also sometimes referred to as a g Node B or gNB) .
- a RAN provides its communication services with external entities through its connection to a core network (CN) .
- CN core network
- E-UTRAN may utilize an Evolved Packet Core (EPC)
- EPC Evolved Packet Core
- NG-RAN may utilize a 5G Core Network (5GC) .
- EPC Evolved Packet Core
- 5GC 5G Core Network
- FIG. 1 shows an example method of wireless communication by a user equipment (UE) , according to one or more aspects described herein.
- UE user equipment
- FIG. 2 illustrates a first example flow diagram in which the method of FIG. 1 is implemented.
- FIG. 3 illustrates a first example flow diagram in which the method of FIG. 1 is implemented.
- FIG. 4 shows an example method of wireless communication by a network device, according to one or more aspects described herein.
- FIG. 5 illustrates an example flow diagram in which one or more parameters related to time domain channel properties (TDCP) report reliability are transmitted to a network with a TDCP report.
- TDCP time domain channel properties
- FIG. 6 shows an example extension of the CSI-ReportConfig information element (IE) described in 3GPP Technical Specification (TS) 38.331 v18.0.0 (2023-12) , to not only trigger a TDCP report, but to also trigger a TDCP-RSRP report and/or a TDCP-SINR report, according to one or more aspects described herein.
- IE CSI-ReportConfig information element
- FIG. 7 illustrates an example architecture of a wireless communication system, according to one or more aspects described herein.
- FIG. 8 illustrates an example system for performing signaling between a wireless device and a network device, according to one or more aspects described herein.
- a processor e.g., a baseband processor
- a wireless device e.g., a user equipment (UE)
- UE user equipment
- a network device e.g., a network device
- reference to a processor, wireless device, or network device is merely provided for illustrative purposes.
- the example embodiments may be utilized with any electronic component or device that may establish a wireless connection and is configured with the hardware, software, and/or firmware to exchange information and data over the wireless connection. Therefore, the processors, wireless devices, and network devices described herein are used to represent any appropriate electronic components or devices.
- the wireless device or UE may be a mobile phone (e.g., a smartphone) , a computer (e.g., a laptop or tablet computer) , a wearable device (e.g., an electronic watch, fitness device, or head-mounted device) , or an Internet of Things (IoT) device.
- a mobile phone e.g., a smartphone
- a computer e.g., a laptop or tablet computer
- a wearable device e.g., an electronic watch, fitness device, or head-mounted device
- IoT Internet of Things
- a UE When triggered to do so by a network device (e.g., a gNB) , a UE may generate and transmit a time domain channel properties (TDCP) report.
- the TDCP report is based on one or more TDCP measurements of a tracking reference signal (TRS; e.g., a set of channel state information (CSI) reference signals (CSI-RSs) transmitted according to a predetermined pattern) .
- TRS tracking reference signal
- CSI-RSs channel state information reference signals
- a TDCP measurement characterizes a time domain correlation of a channel at different time offsets, and is further defined in 3GPP Technical Specification (TS) 38.215 v18.1.0 (2023-12) as a “wideband normalized correlation between two CSI-RS transmission occasions, corresponding to CSI-RS resourece (s) from NZP-CSI-RS-ResourceSet (s) configured with higher layer parameter trs-info, that are separated by D n symbols or slots, depending on the configuration, where Dn is the n-th delay configured value among [placeHolderForRrcParameter-D] configured delay values ⁇ D 1 , ..., D Y ⁇ and Y is number of configured delay values. ”
- a TDCP report only supports aperiodic CSI, not periodic or semi-persistent CSI.
- TDCP measurements are highly dependent on channel condition. Another problem is that it is hard to define an ideal TDCP measurement under all channel conditions, which makes it hard to know the accuracy of a particular TDCP measurement for a particular channel. That said, experimental setups indicate that the reliability (or accuracy) of TDCP measurements is generally dependent on parameters such as Doppler, channel correlation, subcarrier spacing, signal-to-noise ratio (SNR) , signal to interference and noise ratio (SINR) , and reference signal received power (RSRP) . For example, the correlation for a channel having a relatively higher Doppler is typically not as good as the correlation for a channel having a relatively lower Doppler, so the correlation value (or TDCP measurement) will decrease.
- SNR signal-to-noise ratio
- SINR signal to interference and noise ratio
- RSRP reference signal received power
- subcarrier spacing determines slot size (e.g., a channel with a 15 kHz SCS may have a one millisecond (1 ms) gap between 2 CSI-RS of a TRS, whereas a channel with a 30 kHZ SCS may have a 0.5 ms gap between 2 CSI-RS of a TRS) .
- SCS subcarrier spacing
- Channels with larger SCS tend to have higher channel correlation.
- Channel correlation is also dependent on SNR, SINR, and RSRP. Generally, a noisier channel has lower channel correlation.
- TDCP measurements tend to be more reliable when the signal-to-noise ratio (SNR) is greater than 10 decibels (> 10 dB) .
- SNR signal-to-noise ratio
- 10 decibels > 10 decibels
- a UE determines whether one or more TDCP report reliability criterions are satisfied, and only transmits a TDCP report after determining that the one or more TDCP report reliability criterions are satisfied.
- a network may transmit one or more thresholds to the UE, which thresholds can be used to evaluate the one or more TDCP report reliability criterions.
- the thresholds may be set based on channel properties such as Doppler, SCS, type of channel, or other parameters.
- the UE can transmit (e.g., with the TDCP report) information that a network can use to determine (or verify) the reliability of the TDCP report.
- FIG. 1 shows an example method 100 of wireless communication by a UE.
- the UE may be the wireless device or UE 702, 704, or 802.
- the method 100 may be performed by a processor (e.g., a baseband processor) of the UE.
- the processor may include one or more processor cores, and memory that is coupled to the processor core (s) .
- the memory may store instructions that, when executed by the processor core (s) , cause the processor to perform the operations of the method 100.
- the processor may also cause other components of the UE (e.g., a transceiver) to perform, or discontinue, various operations.
- the method 100 may include determining that one or more time domain channel properties (TDCP) report reliability criterions are satisfied.
- the TDCP report reliability criterion (s) may be satisfied, for example, based on: a SINR (or SNR) of a received reference signal satisfying a SINR threshold, or a RSRP of a received reference signal satisfying a RSRP threshold, or a measured TDCP satisfying a TDCP threshold. All of these determinations may be made with respect to a network device (e.g., a gNB or transmission and reception point (TRP) ) for which a TDCP report may be generated.
- a network device e.g., a gNB or transmission and reception point (TRP)
- the method 100 may include receiving an aperiodic channel state information (CSI) trigger for a TDCP report.
- the aperiodic CSI trigger for the TDCP report may be received, for example, over the air and via the transceiver.
- the aperiodic CSI trigger for the TDCP report may be received from a network device (e.g., from the network device for which the TDCP report is to be generated) on a physical downlink control channel (PDCCH) .
- the aperiodic CSI trigger may include, for example, an indication that the UE is to generate and transmit a report.
- the aperiodic CSI trigger may also or alternatively include a report configuration and/or the reception of reference signals (e.g., a TRS including a set of CSI-RS, with the CSI-RS transmitted in accord with a particular pattern) .
- reference signals e.g., a TRS including a set of CSI-RS, with the CSI-RS transmitted in accord with a particular pattern
- the method 100 may include transmitting the TDCP report in response to the reception of the aperiodic CSI trigger for the TDCP report, at 104, and in response to the determination that the one or more TDCP report reliability criterions are satisfied, at 106 (i.e., both conditions need to be satisfied) .
- the TDCP report may not be transmitted if the aperiodic CSI trigger is not received, or if the TDCP report reliability criterion (s) are not satisfied.
- the TDCP report may be transmitted to the network device for which the TDCP is generated, or to a network device that is in communication with the network device for which the TDCP is generated.
- the method 100 may be variously embodied, extended, or adapted, as described in the following paragraphs and elsewhere in this description.
- the operations of the method 100 may be performed in different orders (e.g., the operation (s) at 104 may be performed before or after the operation (s) at 102) .
- the method 100 may include receiving a signal (or signals) from the network device for which the TDCP is to be generated, determining (e.g., measuring) a SINR of the received signal (s) , and determining whether the SINR satisfies a SINR threshold (e.g., determining whether a measured SINR > SINR threshold) .
- the relevant signal (s) may include one or more reference signals, such as one or more CSI reference signals (CSI-RSs) .
- the CSI-RS (s) do not have to be (but may be) CSI-RS (s) provided for TDCP measurement.
- the signal (s) may be one or more other reference signals, or one or more non-reference signals, received from the network device for which the TDCP is to be generated.
- the SINR criterion may be evaluated before or after the aperiodic CSI trigger for the TDCP report is received at 104.
- the SINR may be (for example) an average SINR for the signals.
- the SINR may be a filtered Layer 1 (L1) or Layer 3 (L3) measurement.
- the method 100 may include receiving a signal (or signals) from the network device for which the TDCP is to be generated, determining (e.g., measuring) a RSRP of the received signal (s) , and determining whether the RSRP satisfies a RSRP threshold (e.g., determining whether a measured RSRP >RSRP threshold) .
- the relevant signal (s) may include one or more reference signals, such as one or more CSI-RSs.
- the CSI-RS (s) do not have to be (but may be) CSI-RS (s) provided for TDCP measurement.
- the signal (s) may be one or more other reference signals, or one or more non-reference signals, received from the network device for which the TDCP is to be generated.
- the signal (s) may or may not be the same signal (s) for which the SINR is determined.
- the RSRP criterion may be evaluated before or after the aperiodic CSI trigger for the TDCP report is received at 104.
- the RSRP may be (for example) an average RSRP for the signals.
- the RSRP may be a filtered L1 or L3 measurement.
- the method 100 may include receiving a set of signals from the network device for which the TDCP is to be generated, determining (e.g., measuring) a TDCP for the set of received signals, and determining whether the TDCP satisfies a TDCP threshold (e.g., determining whether a measured TDCP >TDCP threshold, or determining whether the measured TDCP ⁇ TDCP threshold, depending on whether the network wants to know whether TDCP is high or low) .
- a TDCP threshold e.g., determining whether a measured TDCP >TDCP threshold, or determining whether the measured TDCP ⁇ TDCP threshold, depending on whether the network wants to know whether TDCP is high or low
- Determining that a measured TDCP is greater than a TDCP threshold, or that the measured TDCP satisfies a relatively higher TDCP threshold, may enable the use of a more advanced codebook (e.g., because of greater channel correlation, a Type II codebook may be used instead of a Type I codebook) .
- Determining that a measured TDCP is less than a TDCP threshold, or that the measured TDCP is less than a relatively lower TDCP threshold may require the use of a less advanced codebook (e.g., because of lower channel correlation, a Type I codebook may be required instead of a Type II codebook) ; or may enable the UE to avoid transmitting a TDCP report that lacks reliability or usefulness; or may suggest that a network device should increase CSI-RS periodicity (or similarly, suggest that the UE should increase sounding reference signal (SRS) periodicity) .
- a less advanced codebook e.g., because of lower channel correlation, a Type I codebook may be required instead of a Type II codebook
- the relevant set of signals may be a set of reference signals received from the network device for which the TDCP is to be generated, such as a set of CSI-RSs configured as a TRS.
- the set of signals may or may not include a same signal or set of signals for which the SINR or RSRP is determined.
- the TDCP criterion may be evaluated before or after the aperiodic CSI trigger for the TDCP report is received at 104.
- the method 100 may include receiving one or more of the TDCP report reliability criterion (s) (e.g., over the air and via the transceiver, from a network device) .
- the method 100 may include receiving one or more of the TDCP report reliability criterion (s) in higher layer signaling, such as radio resource control (RRC) signaling.
- RRC radio resource control
- only the SINR criterion and/or RSRP criterion may be received via RRC signaling.
- one or more of the TDCP report reliability criterion (s) may be specified in a standard (e.g., in a 3GPP Technical Specification (TS) ) .
- TS 3GPP Technical Specification
- the method 100 may include transmitting an indication that the TDCP report reliability criteria is satisfied.
- the indication may be transmitted, for example, over the air and via the transceiver.
- the aperiodic CSI trigger for the TDCP report may be received, at 104, at least partly in response to transmitting the indication that the TDCP report reliability criterion (s) are satisfied.
- a network device may receive the indication that the TDCP report reliability criterion (s) are satisfied and, in response, transmit the aperiodic CSI trigger for the TDCP report to the UE.
- determining the TDCP report reliability criterion (s) are satisfied, at 102 may include one or both of 1) determining a SINR of a received reference signal satisfies a SINR threshold, or 2) determining a RSRP of a received reference signal satisfies a RSRP threshold. An example of these embodiments is illustrated in the flow diagram 200 of FIG. 2.
- the UE 202 may determine that the one or more TDCP report reliability criterion are satisfied at 206.
- the UE 202 may then transmit the indication that the TDCP report reliability criterion (s) are satisfied, to a network device (e.g., a gNB) 204, at 208.
- the network device 204 may transmit the aperiodic CSI trigger for the TDCP report, to the UE 202, at 210.
- the UE 202 may generate the TDCP report at 212, and may transmit the TDCP report, to the network device 204, at 214.
- the UE 202 may generate the TDCP report, or begin to generate the TDCP report, before the aperiodic CSI trigger is received.
- determining the TDCP report reliability criterion (s) are satisfied, at 102 may include determining a measured TDCP satisfies a TDCP threshold.
- Determining the TDCP report reliability criterion (s) are satisfied may also include one or both of 1) determining a SINR of a received reference signal satisfies a SINR threshold, or 2) determining a RSRP of a received reference signal satisfies a RSRP threshold.
- the flow diagram 200 of FIG. 2 is also illustrative of these embodiments.
- the method 100 may include determining the TDCP report reliability criterion (s) are satisfied, at 102, after receiving the aperiodic CSI trigger for the TDCP report, at 104.
- a network device e.g., a gNB
- the UE 302 may determine that the one or more TDCP report reliability criterion are satisfied at 308, and generate the TDCP report at 310.
- the UE 302 may then transmit the TDCP report, to the network device 304, at 312.
- the UE 302 may generate the TDCP report, or begin to generate the TDCP report, before the aperiodic CSI trigger is received.
- Generating the TDCP report may include, for example, determining a wideband normalized correlation between two CSI-RS transmission occasions, such as two CSI-RS transmission occasions corresponding to CSI-RS resources from NZP-CSI-RS-ResourceSet (s) configured with the higher layer parameter trs-info, as described in 3GPP TS 38.215 v18.1.0 (2023-12) .
- FIG. 4 shows an example method 400 of wireless communication by a network device (e.g., a gNB) .
- the network device may be the network device 712, 714, or 820.
- the method 400 may be performed by a processor (e.g., a baseband processor) of the network device.
- the processor may include one or more processor cores, and memory that is coupled to the processor core (s) .
- the memory may store instructions that, when executed by the processor core (s) , cause the processor to perform the operations of the method 400.
- the processor may cause other components of the network device (e.g., a transceiver) to perform, or discontinue, various operations.
- the method 400 may include transmitting, to a UE, an aperiodic CSI trigger for a TDCP report.
- the aperiodic CSI trigger for the TDCP report may be transmitted, for example, over the air and via the transceiver.
- the aperiodic CSI trigger for the TDCP report may be transmitted on a PDCCH.
- the aperiodic CSI trigger may include, for example, an indication that the UE is to generate and transmit a report.
- the aperiodic CSI trigger may also or alternatively be considered to include a report configuration and/or the transmission of reference signals (e.g., a TRS including a set of CSI-RS, with the CSI-RS transmitted in accord with a particular pattern) .
- reference signals e.g., a TRS including a set of CSI-RS, with the CSI-RS transmitted in accord with a particular pattern
- the method 400 may include receiving the TDCP report from the UE.
- the TDCP report may be received in response to transmitting the aperiodic CSI trigger for the TDCP report.
- the receipt of the TDCP report may indicate that one or more TDCP report reliability criterion are satisfied. That is, if the TDCP report is received, the TDCP report can be assumed to meet the TDCP report reliability criterion (s) .
- information received before, with, or after the TDCP report may include or indicate measured parameters of the TDCP report reliability criteria.
- the method 400 may be variously embodied, extended, or adapted, as described in the following paragraphs and elsewhere in this description.
- the method 400 may include transmitting some or all of the TDCP report reliability criteria to the UE (e.g., over the air and via the transceiver) .
- the method 400 may include transmitting some or all of the TDCP report reliability criteria in higher layer signaling, such as RRC signaling.
- RRC signaling such as RRC signaling.
- SINR or SNR
- RSRP criterion may be transmitted via RRC signaling.
- one or more of the TDCP report reliability criterion (s) may be specified in a standard (e.g., in a 3GPP TS) .
- the method 400 may include receiving, from the UE, an indication that the one or more TDCP report reliability criterion are satisfied.
- the indication may be received, for example, over the air and via the transceiver.
- the aperiodic CSI trigger for the TDCP report may be transmitted, at 402, at least partly in response to receiving the indication that the TDCP report reliability criterion (s) are satisfied.
- the method 400 may include transmitting at least one reference signal, and the TDCP report reliability criterion (s) may include one or both of 1) satisfaction of a SINR threshold for reception, by the UE, of a reference signal in the at least one reference signal, or 2) satisfaction of a RSRP threshold for reception, by the UE, of a reference signal in the at least one reference signal.
- the flow diagram 200 of FIG. 2 An example of these embodiments is illustrated in the flow diagram 200 of FIG. 2.
- the TDCP report reliability criterion (s) may also include one or both of 1) satisfaction of a SINR threshold for reception, by the UE, of a reference signal in the at least one reference signal, or 2) satisfaction of a RSRP threshold for reception, by the UE, of a reference signal in the at least one reference signal.
- An example of these embodiments is also illustrated in the flow diagram 200 of FIG. 2.
- the method 400 may include transmitting at least one reference signal after transmitting the aperiodic CSI trigger, and the TDCP report reliability criterion (s) may include one or both of 1) satisfaction of a SINR threshold for reception, by the UE, of a reference signal in the at least one reference signal, or 2) satisfaction of a RSRP threshold for reception, by the UE, of a reference signal in the at least one reference signal.
- the flow diagram 300 of FIG. 3 An example of these embodiments is illustrated in the flow diagram 300 of FIG. 3.
- the method 400 may be further adapted or implemented as described with reference to FIG. 1.
- FIG. 5 illustrates an example flow diagram 500 in which one or more parameters related to TDCP report reliability are transmitted from a UE 502 to a network device 504.
- the parameter (s) may be transmitted along with a TDCP report.
- the UE 502 may be the wireless device or UE 702, 704, or 802, and/or the network device 504 may be the network device 712, 714, or 820.
- the operations performed by the UE 502 or network device 504 e.g., a gNB
- a respective processor e.g., a baseband processor
- each processor may include one or more processor cores, and memory that is coupled to the processor core (s) .
- the memory may store instructions that, when executed by the processor core (s) , cause the processor to perform the operations of the UE 502 or network device 504.
- the processor may also cause other components of the UE or network device (e.g., a transceiver) to perform, or discontinue, various operations.
- the network device 504 may transmit an aperiodic CSI trigger for a TDCP report, to the UE 502, at 506.
- the UE 502 may receive the aperiodic CSI trigger for the TDCP report, at 506, and determine one or more parameters related to TDCP report reliability at 508.
- the UE 502 may generate the TDCP report.
- the UE 502 may transmit the TDCP report and the determined one or more parameters related to TDCP report reliability, to the network device 504, at 512.
- the parameter (s) related to TDCP report reliability may be determined in response to the reception of the aperiodic CSI trigger for the TDCP report. In some embodiments, the parameter (s) related to TDCP report reliability may be determined partly or wholly before the aperiodic CSI trigger for the TDCP report is received.
- the parameter (s) related to TDCP report reliability are provided to a network so that a determination of whether a TDCP report is reliable (or how reliable) can be made by the network.
- This alternative flow involves transmitting TDCP reports that may or may not meet a threshold criteria for reliability (or usability) .
- the flow 500 may be variously embodied, extended, or adapted, as described in the following paragraphs and elsewhere in this description.
- the parameter (s) related to TDCP report reliability may include a SINR of a received reference signal.
- the flow 500 may optionally include transmitting, with the TDCP report, an indication of a CSI-RS on which the SINR is based.
- the CSI-RS should be a CSI-RS associated with the TRS that is used for generating the TDCP report, or a CSI-RS that is quasi-co-located (QCL’d) with the TRS.
- the parameter (s) related to TDCP report reliability may include a RSRP of a received reference signal.
- the flow 500 may include transmitting, with the TDCP report, an indication of a synchronization signal block (SSB) on which the RSRP is based.
- the SSB should be a SSB that is QCL’d with the TRS that is used for generating the TDCP report.
- the indication of the CSI-RS on which the SINR is based may be transmitted with the TDCP report as a first indication, and the indication of the SSB on which the RSRP is based may be transmitted with the TDCP report as a second indication.
- the reportQuantity of the CSI-ReportConfig information element (IE) 600 described in 3GPP TS 38.331 v18.0.0 (2023-12) may be extended to not only trigger a TDCP report, but to also trigger a TDCP-RSRP report (information on a RSRP for a measured SSB, including the first indication described above) and/or a TDCP-SINR report (information on a SINR for a measured CSI-RS, including the second indication described above) .
- a TDCP-RSRP report information on a RSRP for a measured SSB, including the first indication described above
- TDCP-SINR report information on a SINR for a measured CSI-RS, including the second indication described above
- Embodiments contemplated herein include one or more non-transitory computer-readable media storing 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 the method or flow 100, 200, 300, 400, or 500.
- this non-transitory computer-readable media may be, for example, a memory of a UE (such as a memory 806 of a wireless device 802 that is a UE, as described herein) .
- this non-transitory computer-readable media may be, for example, a memory of a network device (such as a memory 824 of a network device 820, as described herein) .
- Embodiments contemplated herein include an apparatus having logic, modules, or circuitry to perform one or more elements of the method or flow 100, 200, 300, 400, or 500.
- this apparatus may be, for example, an apparatus of a UE (such as a wireless device 802 that is a UE) .
- this apparatus may be, for example, an apparatus of a network device (such as a network device 820, as described herein) .
- Embodiments contemplated herein include an apparatus having one or more processors and one or more computer-readable media, using or storing instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of the method or flow 100, 200, 300, 400, or 500.
- this apparatus may be, for example, an apparatus of a UE (such as a wireless device 802 that is a UE, as described herein) .
- this apparatus may be, for example, an apparatus of a network device (such as a network device 820, as described herein) .
- Embodiments contemplated herein include a signal as described in or related to one or more elements of the method or flow 100, 200, 300, 400, or 500.
- Embodiments contemplated herein include a computer program or computer program product having instructions, wherein execution of the program by a processor causes the processor to carry out one or more elements of the method or flow 100, 200, 300, 400, or 500.
- the processor may be a processor of a UE (such as a processor (s) 804 of a wireless device 802 that is a UE, as described herein)
- the instructions may be, for example, located in the processor and/or on a memory of the UE (such as a memory 806 of a wireless device 802 that is a UE, as described herein) .
- FIG. 7 illustrates an example architecture of a wireless communication system, according to embodiments described herein. The following description is provided for an example wireless communication system 700 that operates in conjunction with the LTE system standard and/or 5G or NR system standard, as provided by 3GPP TSs.
- the wireless communication system 700 includes UE 702 and UE 704 (although any number of UEs may be used) .
- the UE 702 and the UE 704 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks) but may also comprise any mobile or non-mobile computing device configured for wireless communication.
- the UE 702 and UE 704 may be configured to communicatively couple with a RAN 706.
- the RAN 706 may be NG-RAN, E-UTRAN, etc.
- the UE 702 and UE 704 utilize connections (or channels) (shown as connection 708 and connection 710, respectively) with the RAN 706, each of which comprises a physical communications interface.
- the RAN 706 can include one or more network devices, such as base station 712 and base station 714, that enable the connection 708 and connection 710.
- connection 708 and connection 710 are air interfaces to enable such communicative coupling and may be consistent with RAT (s) used by the RAN 706, such as, for example, an LTE and/or NR.
- the UE 702 and UE 704 may also directly exchange communication data via a sidelink interface 716.
- the UE 704 is shown to be configured to access an access point (shown as AP 718) via connection 720.
- the connection 720 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP 718 may comprise a router.
- the AP 718 may be connected to another network (for example, the Internet) without going through a CN 724.
- the UE 702 and UE 704 can be configured to communicate using orthogonal frequency-division multiplexing (OFDM) communication signals with each other or with the base station 712 and/or the base station 714 over a multicarrier communication channel in accordance with various communication techniques, such as, but not limited to, an orthogonal frequency-division multiple access (OFDMA) communication technique (e.g., for downlink communications) or a single carrier frequency division multiple access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink communications) , although the scope of the embodiments is not limited in this respect.
- OFDM signals can comprise a plurality of orthogonal subcarriers.
- the base station 712 or base station 714 may be implemented as one or more software entities running on server computers as part of a virtual network.
- the base station 712 or base station 714 may be configured to communicate with one another via interface 722.
- the interface 722 may be an X2 interface.
- the X2 interface may be defined between two or more network devices of a RAN (e.g., two or more eNBs and the like) that connect to an EPC, and/or between two eNBs connecting to the EPC.
- the interface 722 may be an Xn interface.
- the Xn interface is defined between two or more network devices of a RAN (e.g., two or more gNBs and the like) that connect to the 5GC, between a base station 712 (e.g., a gNB) connecting to the 5GC and an eNB, and/or between two eNBs connecting to the 5GC (e.g., CN 724) .
- the RAN 706 is shown to be communicatively coupled to the CN 724.
- the CN 724 may comprise one or more network elements 726, which are configured to offer various data and telecommunications services to customers/subscribers (e.g., users of UE 702 and UE 704) who are connected to the CN 724 via the RAN 706.
- the components of the CN 724 may be implemented in one physical device or separate physical devices including components to read and execute instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) .
- the CN 724 may be an EPC, and the RAN 706 may be connected with the CN 724 via an S1 interface 728.
- the S1 interface 728 may be split into two parts, an S1 user plane (S1-U) interface, which carries traffic data between the base station 712 or base station 714 and a serving gateway (S-GW) , and the S1-MME interface, which is a signaling interface between the base station 712 or base station 714 and mobility management entities (MMEs) .
- S1-U S1 user plane
- S-GW serving gateway
- MMEs mobility management entities
- the CN 724 may be a 5GC, and the RAN 706 may be connected with the CN 724 via an NG interface 728.
- the NG interface 728 may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the base station 712 or base station 714 and a user plane function (UPF) , and the S1 control plane (NG-C) interface, which is a signaling interface between the base station 712 or base station 714 and access and mobility management functions (AMFs) .
- NG-U NG user plane
- UPF user plane function
- S1 control plane S1 control plane
- an application server 730 may be an element offering applications that use internet protocol (IP) bearer resources with the CN 724 (e.g., packet switched data services) .
- IP internet protocol
- the application server 730 can also be configured to support one or more communication services (e.g., VoIP sessions, group communication sessions, etc. ) for the UE 702 and UE 704 via the CN 724.
- the application server 730 may communicate with the CN 724 through an IP communications interface 732.
- FIG. 8 illustrates an example system 800 for performing signaling 838 between a wireless device 802 and a network device 820, according to embodiments described herein.
- the system 800 may be a portion of a wireless communication system as herein described.
- the wireless device 802 may be, for example, a UE of a wireless communication system.
- the network device 820 may be, for example, a base station (e.g., an eNB or a gNB) or a radio head of a wireless communication system.
- the wireless device 802 may include one or more processor (s) 804.
- the processor (s) 804 may execute instructions such that various operations of the wireless device 802 are performed, as described herein.
- the processor (s) 804 may include one or more baseband processors implemented using, for example, a central processing unit (CPU) , a digital signal processor (DSP) , an application specific integrated circuit (ASIC) , a controller, a field programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.
- CPU central processing unit
- DSP digital signal processor
- ASIC application specific integrated circuit
- FPGA field programmable gate array
- the wireless device 802 may include a memory 806.
- the memory 806 may be a non-transitory computer-readable storage medium that stores instructions 808 (which may include, for example, the instructions being executed by the processor (s) 804) .
- the instructions 808 may also be referred to as program code or a computer program.
- the memory 806 may also store data used by, and results computed by, the processor (s) 804.
- the wireless device 802 may include one or more antenna (s) 812 (e.g., one, two, four, eight, or more; also referred to herein as antenna elements) .
- the wireless device 802 may leverage the spatial diversity of such multiple antenna (s) 812 to send and/or receive multiple different data streams on the same time and frequency resources.
- This behavior may be referred to as, for example, MIMO behavior (referring to the multiple antennas used at each of a transmitting device and a receiving device that enable this aspect) .
- MIMO transmissions by the wireless device 802 may be accomplished according to precoding (or digital beamforming) that is applied at the wireless device 802 that multiplexes the data streams across the antenna (s) 812 according to known or assumed channel characteristics such that each data stream is received with an appropriate signal strength relative to other streams and at a desired location in the spatial domain (e.g., the location of a receiver associated with that data stream) .
- Some embodiments may use single user MIMO (SU-MIMO) methods (where the data streams are all directed to a single receiver) and/or multiuser MIMO (MU-MIMO) methods (where individual data streams may be directed to individual (different) receivers in different locations in the spatial domain) .
- SU-MIMO single user MIMO
- MU-MIMO multiuser MIMO
- the wireless device 802 may implement analog beamforming techniques, whereby phases of the signals sent by the antenna (s) 812 are relatively adjusted such that the (joint) transmission of the antenna (s) 812 can be directed (this is sometimes referred to as beam steering) .
- the wireless device 802 may include one or more interface (s) 814.
- the interface (s) 814 may be used to provide input to or output from the wireless device 802.
- a wireless device 802 that is a UE may include interface (s) 814 such as microphones, speakers, a touchscreen, buttons, and the like in order to allow for input and/or output to the UE by a user of the UE.
- Other interfaces of such a UE may be made up of transmitters, receivers, and other circuitry (e.g., other than the transceiver (s) 810/antenna (s) 812 already described) that allow for communication between the UE and other devices and may operate according to known protocols (e.g., and the like) .
- the wireless device 802 may include TDCP reporting module (s) 816.
- the TDCP reporting module (s) 816 may be implemented via hardware, software, or combinations thereof.
- the TDCP reporting module (s) 816 may be implemented as a processor, circuit, and/or instructions 808 stored in the memory 806 and executed by the processor (s) 804.
- the TDCP reporting module (s) 816 may be integrated within the processor (s) 804 and/or the transceiver (s) 810.
- the TDCP reporting module (s) 816 may be implemented by a combination of software components (e.g., executed by a DSP or a general processor) and hardware components (e.g., logic gates and circuitry) within the processor (s) 804 or the transceiver (s) 810.
- the TDCP reporting module (s) 816 may be used for various aspects of the present disclosure, for example, aspects of FIGs. 1-6, from a wireless device or UE perspective.
- the TDCP reporting module (s) 816 may be used, for example, to perform the operations of the method described with reference to FIG. 1, or the UE operations of the flows described with reference to FIGs. 2, 3, and 5.
- the network device 820 may include one or more processor (s) 822.
- the processor (s) 822 may execute instructions such that various operations of the network device 820 are performed, as described herein.
- the processor (s) 822 may include one or more baseband processors implemented using, for example, a CPU, a DSP, an ASIC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.
- the network device 820 may include a memory 824.
- the memory 824 may be a non-transitory computer-readable storage medium that stores instructions 826 (which may include, for example, the instructions being executed by the processor (s) 822) .
- the instructions 826 may also be referred to as program code or a computer program.
- the memory 824 may also store data used by, and results computed by, the processor (s) 822.
- the network device 820 may include one or more transceiver (s) 828 (also collectively referred to as a transceiver 828) that may include RF transmitter and/or receiver circuitry that use the antenna (s) 830 of the network device 820 to facilitate signaling (e.g., the signaling 838) to and/or from the network device 820 with other devices (e.g., the wireless device 802) according to corresponding RATs.
- transceiver (s) 828 also collectively referred to as a transceiver 828) that may include RF transmitter and/or receiver circuitry that use the antenna (s) 830 of the network device 820 to facilitate signaling (e.g., the signaling 838) to and/or from the network device 820 with other devices (e.g., the wireless device 802) according to corresponding RATs.
- the network device 820 may include one or more antenna (s) 830 (e.g., one, two, four, or more; also referred to herein as antenna elements) .
- the network device 820 may perform MIMO, digital beamforming, analog beamforming, beam steering, etc., as has been described.
- the network device 820 may include one or more interface (s) 832.
- the interface (s) 832 may be used to provide input to or output from the network device 820.
- a network device 820 of a RAN e.g., a base station, a radio head, etc.
- the network device 820 may include one or more TDCP reporting management module (s) 834.
- the TDCP reporting management module (s) 834 may be implemented via hardware, software, or combinations thereof.
- the TDCP reporting management module (s) 834 may be implemented as a processor, circuit, and/or instructions 826 stored in the memory 824 and executed by the processor (s) 822.
- the TDCP reporting management module (s) 834 may be integrated within the processor (s) 822 and/or the transceiver (s) 828.
- the TDCP reporting management module (s) 834 may be implemented by a combination of software components (e.g., executed by a DSP or a general processor) and hardware components (e.g., logic gates and circuitry) within the processor (s) 822 or the transceiver (s) 828.
- software components e.g., executed by a DSP or a general processor
- hardware components e.g., logic gates and circuitry
- the TDCP reporting management module (s) 834 may be used for various aspects of the present disclosure, for example, aspects of FIGs. 1-6, from a network device perspective.
- the TDCP reporting management module (s) 834 may be used, for example, to perform the operations of the method described with reference to FIG. 4, or the network device operations of the flows described with reference to FIGs. 2, 3, and 5.
- 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, and/or methods as set forth herein.
- a baseband processor or processor
- circuitry associated with a UE, network device, 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 herein.
- indications that a processor or component “transmits” or “receives” a signal or information means that the processor sets in motion the operation (s) , or configures the component (s) (e.g., a transceiver or radio frequency (RF) subsystem) , or otherwise facilitates the operation (s) that lead to the signal or information being transmitted or received.
- the component e.g., a transceiver or radio frequency (RF) subsystem
- Embodiments and implementations of the systems and methods described herein may include various operations, which may be embodied in machine-executable instructions to be executed by a computer system.
- a computer system may include one or more general-purpose or special-purpose computers (or other electronic devices) .
- the computer system may include hardware components that include specific logic for performing the operations or may include a combination of hardware, software, and/or firmware.
- 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.
- 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.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
L'invention concerne un procédé d'un équipement utilisateur (UE) consistant à déterminer qu'un ou plusieurs critères de fiabilité de rapport de propriétés de canal du domaine temporel (TDCP) sont satisfaits ; à recevoir un déclencheur d'informations d'état de canal (CSI) apériodique pour un rapport de TDCP ; et à transmettre le rapport de TDCP en réponse à la réception du déclencheur de CSI apériodique pour le rapport de TDCP et en réponse à la détermination du fait que le ou les critères de fiabilité de rapport de TDCP sont satisfaits. Le ou les critères de fiabilité de rapport de TDCP peuvent être satisfaits sur la base, au moins en partie, par exemple d'un rapport signal sur interférence et bruit (SINR) d'un signal de référence reçu satisfaisant un seuil de SINR, ou d'une puissance reçue de signal de référence (RSRP) d'un signal de référence reçu satisfaisant un seuil de RSRP, ou d'un TDCP mesuré satisfaisant un seuil de TDCP.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/CN2024/077429 WO2025171656A1 (fr) | 2024-02-18 | 2024-02-18 | Améliorations apportées à un rapport de propriétés de canal du domaine temporel |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/CN2024/077429 WO2025171656A1 (fr) | 2024-02-18 | 2024-02-18 | Améliorations apportées à un rapport de propriétés de canal du domaine temporel |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2025171656A1 true WO2025171656A1 (fr) | 2025-08-21 |
Family
ID=96772457
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2024/077429 Pending WO2025171656A1 (fr) | 2024-02-18 | 2024-02-18 | Améliorations apportées à un rapport de propriétés de canal du domaine temporel |
Country Status (1)
| Country | Link |
|---|---|
| WO (1) | WO2025171656A1 (fr) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023089593A1 (fr) * | 2021-11-22 | 2023-05-25 | Telefonaktiebolaget Lm Ericsson (Publ) | Procédés et noeuds pour rapporter des csi à l'aide de trs |
| CN116489674A (zh) * | 2022-01-17 | 2023-07-25 | 北京紫光展锐通信技术有限公司 | 一种信息上报方法及其装置 |
| WO2024025249A1 (fr) * | 2022-07-26 | 2024-02-01 | 엘지전자 주식회사 | Procédé par lequel un ue transmet des informations de propriété de canal de domaine temporel à une station de base dans un système de communication sans fil, et appareil associé |
| WO2024031683A1 (fr) * | 2022-08-12 | 2024-02-15 | Google Llc | Rapport de propriété de canal dans le domaine temporel |
-
2024
- 2024-02-18 WO PCT/CN2024/077429 patent/WO2025171656A1/fr active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023089593A1 (fr) * | 2021-11-22 | 2023-05-25 | Telefonaktiebolaget Lm Ericsson (Publ) | Procédés et noeuds pour rapporter des csi à l'aide de trs |
| CN116489674A (zh) * | 2022-01-17 | 2023-07-25 | 北京紫光展锐通信技术有限公司 | 一种信息上报方法及其装置 |
| WO2024025249A1 (fr) * | 2022-07-26 | 2024-02-01 | 엘지전자 주식회사 | Procédé par lequel un ue transmet des informations de propriété de canal de domaine temporel à une station de base dans un système de communication sans fil, et appareil associé |
| WO2024031683A1 (fr) * | 2022-08-12 | 2024-02-15 | Google Llc | Rapport de propriété de canal dans le domaine temporel |
Non-Patent Citations (1)
| Title |
|---|
| XUEMING PAN, VIVO: "Further discussion on CSI enhancement for high-medium UE velocities and coherent JT", 3GPP DRAFT; R1-2300438; TYPE DISCUSSION; NR_MIMO_EVO_DL_UL-CORE, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Athens, GR; 20230227 - 20230303, 17 February 2023 (2023-02-17), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052247581 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US12261663B2 (en) | Enhancement of beam management for multi-TRP operation | |
| EP4449763A1 (fr) | Systèmes et procédés pour conserver une puissance de réseau avec une mise à jour de motif de faisceau pour des blocs de signal de synchronisation transmis | |
| US20250071694A1 (en) | Reference power headroom reports and pathloss measurement for a unified transmission control indicator (tci) framework | |
| US12388596B2 (en) | Phase continuity handling for a UE CSI report of time domain channel properties measurements | |
| US20250274793A1 (en) | Channel state information (csi) measurement and reporting for scalable multiple-input multiple-output (mimo) communication on a downlink | |
| WO2025171656A1 (fr) | Améliorations apportées à un rapport de propriétés de canal du domaine temporel | |
| WO2024026720A1 (fr) | Amélioration de procédure de couche 3 et de couche 1 pour activation d'une cellule secondaire | |
| WO2023056611A1 (fr) | Mécanisme de priorisation pour commutation de port d'antenne srs | |
| WO2023050449A1 (fr) | Rapport de csi amélioré pour fonctionnement multi-trp | |
| WO2024207460A1 (fr) | Réduction de facteur de balayage de faisceau pour gestion de ressources radio améliorée | |
| US12149474B2 (en) | Solutions for enhancement of inter-cell operation for multi-TRP | |
| KR102822170B1 (ko) | 이웃 셀에 대한 업링크 빔 트레이닝 | |
| WO2024098186A1 (fr) | Retards de commutation d'indicateur de configuration de transmission (tci) unifié | |
| WO2024168665A1 (fr) | Mécanisme de restriction de planification dynamique et de mesure pour mobilité inter-cellules l1/l2 | |
| US20250267690A1 (en) | User equipment reporting enhancements for coherent joint transmission | |
| WO2024168712A1 (fr) | Améliorations de configuration de ressources et de rapport pour adaptation d'éléments spatiaux de réseau | |
| US20230247452A1 (en) | Systems and methods for new radio (nr) cell addition measurement | |
| WO2024168803A1 (fr) | Agrégation de porteuses non colocalisées intra-bande améliorée | |
| WO2024207448A1 (fr) | Mesure adaptative d'un signal de réveil à faible puissance ou d'un signal de référence hérité pour une gestion de ressources radio | |
| WO2024168717A1 (fr) | Améliorations de csi pour adaptation de puissance de transmission de liaison descendante dynamique | |
| US20250280401A1 (en) | Srs enhancement for multi-trp coherent joint transmission operation | |
| WO2023044771A1 (fr) | Reprise sur défaillance de faisceau avec sélection de panneau d'antenne de liaison montante | |
| EP4552255A1 (fr) | Procédé et appareil pour prendre en charge un rapport de csi d'ue de propriétés de canal de domaine temporel | |
| WO2024036196A1 (fr) | Procédé et appareil pour prendre en charge un rapport de csi d'ue de propriétés de canal de domaine temporel | |
| WO2025212431A1 (fr) | Procédés, systèmes et appareil pour une opération de liaison montante 3tx |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 24924425 Country of ref document: EP Kind code of ref document: A1 |