User equipment, base station, and method for time domain correlation information reporting

JP2023111797A5Active Publication Date: 2024-11-27SHARP KK
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
JP2022038298
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2022-01-31
Filing Date
2022-03-11
Publication Date
2024-11-27
Estimated Expiration
2042-03-11

AI Technical Summary

Technical Problem

Existing wireless communication systems face challenges in improving communication capacity, speed, flexibility, and efficiency, particularly in managing downlink and uplink transmissions for various services using time, frequency, and spatial resources effectively.

Method used

The implementation of user equipment (UE) and base stations that utilize tracking channel state information-reference signals (CSI-RS) for configuring time domain correlation, enabling efficient reporting of channel state information (CSI) through parameters like trs-Info and reportQuantity, which facilitate better management of downlink and uplink transmissions.

Benefits of technology

Enhances the flexibility and efficiency of wireless communication systems by improving the management of downlink and uplink transmissions, reducing delays, and ensuring reliable and efficient use of time, frequency, and spatial resources.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 00000000_0000_ABST
    Figure 00000000_0000_ABST
Patent Text Reader

Abstract

To provide user equipment (UE), a base station device, and a communication method for time domain correlation information reporting that improves communication flexibility and / or efficiency.SOLUTION: In a communication system, UE includes receiving circuitry configured to receive first information to configure one or more channel state information-reference signals (CSI-RS) for tracking and second information to configure time domain correlation related information from a base station device. The UE also includes transmitting circuitry configured to transmit a channel state information (CSI) report including the time domain correlation related information to the base station device. A first parameter trs-Info is included in the first information. A second parameter reportQuantity is not set to 'none'. The time domain correlation related information is measured by the one or more CSI-RS for tracking.SELECTED DRAWING: Figure 7
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure generally relates to communication systems. More specifically, the present disclosure relates to user equipment, base stations, methods for user equipment, base stations, and methods for time domain alternating information reporting.

Background Art

[0002] Wireless communication devices have become more powerful in order to meet consumer demands and to improve portability and convenience. Consumers have come to rely on wireless communication devices and expect reliable services, extended coverage areas, and improved functionality. A wireless communication system can provide communication to a number of wireless communication devices, and each of the number of wireless communication devices can be provided with a service from a base station. The base station can be a device that communicates with the wireless communication device.

Summary of the Invention

[0003] With the progress of wireless communication devices, improvements in communication capacity, speed, flexibility, and / or efficiency have been sought. However, improving communication capacity, speed, flexibility, and / or efficiency may raise certain issues.

[0004] For example, a wireless communication device can communicate with one or more devices using a communication structure. However, the flexibility and / or efficiency of the communication structure used may be limited. As will be explained in this discussion, systems and methods for improving communication flexibility and / or efficiency can be beneficial.

Brief Description of the Drawings

[0005] [Figure 1] A block diagram showing one implementation form of one or more gNBs and one or more UEs in which a system and method for signaling can be implemented. [Figure 2] A diagram showing examples of multiple numerologies. [Figure 3]This figure shows an example of a resource grid and resource block. [Figure 4] This figure shows an example of a resource area. [Figure 5] This figure shows examples of beamforming and quasi-co-location (QCL) types. [Figure 6] This figure shows an example of a Transmission Configuration Indication (TCI) status. [Figure 7] This flowchart illustrates examples of methods using some of the techniques described herein. [Figure 8] This flowchart illustrates examples of methods using some of the techniques described herein. [Figure 9A] This flowchart illustrates examples of methods using some of the techniques described herein. [Figure 9B] This flowchart illustrates examples of methods using some of the techniques described herein. [Figure 10] This diagram shows various components that can be used in UE. [Figure 11] This figure shows various components that can be used in gNB. [Figure 12] This block diagram shows one implementation of a UE in which one or more of the systems and / or methods described herein may be implemented. [Figure 13] This block diagram shows one implementation of a gNB in ​​which one or more of the systems and / or methods described herein may be implemented. [Figure 14] This is a block diagram showing one implementation of gNB. [Figure 15] This is a block diagram showing one implementation of Unreal Engine (UE). [Modes for carrying out the invention]

[0006] This section describes the user equipment (UE). The UE includes a receiving circuit configured to receive first information for setting one or more tracking channel state information-reference signals (CSI-RS) and second information for setting time-domain correlation information. The UE also includes a transmitting circuit configured to transmit a channel state information (CSI) report containing time-domain correlation information. The first parameter, trs-Info, is included in the first information. The second parameter, reportQuantity, is not set to "none". Time-domain correlation information is measured by one or more tracking CSI-RS.

[0007] Furthermore, the base station is described below. The base station includes a transmitting circuit configured to transmit first information for setting up one or more tracking CSI-RSs, and second information for setting up information regarding time-domain correlation. The base station also includes a receiving circuit configured to receive a CSI report containing information regarding time-domain correlation. The first parameter, trs-Info, is included in the first information. The second parameter, reportQuantity, is not set to "none". Information regarding time-domain correlation is measured by one or more tracking CSI-RSs.

[0008] Furthermore, the UE's communication method is described. The method includes receiving first information for setting up one or more tracking CSI-RSs and second information for setting up information regarding time-domain correlation. The method also includes sending a CSI report containing information regarding time-domain correlation. The first parameter, trs-Info, is included in the first information. The second parameter, reportQuantity, is not set to "none". Information regarding time-domain correlation is measured by one or more tracking CSI-RSs.

[0009] Furthermore, the communication method of the base station equipment is described. The method includes transmitting first information for setting up one or more tracking CSI-RSs and second information for setting up information regarding time-domain correlation. The method also includes receiving a CSI report containing information regarding time-domain correlation. The first parameter, trs-Info, is included in the first information. The second parameter, reportQuantity, is not set to "none". Information regarding time-domain correlation is measured by one or more tracking CSI-RSs.

[0010] Another UE is described below. The UE includes a receiving circuit configured to receive first information for setting up one or more tracking CSI-RSs and second information for setting up information about time-domain correlations. The UE also includes a transmitting circuit configured to transmit a CSI report containing information about time-domain correlations. The first parameter, trs-Info, is included in the first information. The second parameter indicates one of the following: periodic CSI report, semi-persistent CSI report, and aperiodic CSI report. Information about time-domain correlations is measured by one or more tracking CSI-RSs. The CSI report containing information about time-domain correlations is transmitted based on the second parameter.

[0011] The following describes another base station. The base station includes a transmitting circuit configured to transmit first information for setting up one or more tracking CSI-RSs and second information for setting up information about time-domain correlations. The base station also includes a receiving circuit configured to receive CSI reports containing information about time-domain correlations. The first parameter, trs-Info, is included in the first information. The second parameter indicates one of the following: periodic CSI reports, semi-persistent CSI reports, and aperiodic CSI reports. Information about time-domain correlations is measured by one or more tracking CSI-RSs. CSI reports containing information about time-domain correlations are received based on the second parameter.

[0012] Another communication method of a UE is described. The method includes receiving first information for configuring one or more tracking CSI-RSs and second information for configuring information related to time-domain correlation. The method also includes transmitting a CSI report including information related to time-domain correlation. The first parameter trs-Info is included in the first information. The second parameter indicates one of a periodic CSI report, a semi-persistent CSI report, and an aperiodic CSI report. The information related to time-domain correlation is measured by one or more tracking CSI-RSs. The CSI report including information related to time-domain correlation is transmitted based on the second parameter.

[0013] Furthermore, another communication method of a base station device is described. The method includes transmitting first information for configuring one or more tracking CSI-RSs and second information for configuring information related to time-domain correlation. The method also includes receiving a CSI report including information related to time-domain correlation. The first parameter trs-Info is included in the first information. The second parameter indicates one of a periodic CSI report, a semi-persistent CSI report, and an aperiodic CSI report. The information related to time-domain correlation is measured by one or more tracking CSI-RSs. The CSI report including information related to time-domain correlation is received based on the second parameter.

[0014] The 3rd Generation Partnership Project (3GPP), also known as "3GPP", is a collaborative agreement aimed at defining globally applicable technical specifications and technical reports related to 3rd and 4th generation wireless communication systems. In 3GPP, specifications for next-generation mobile networks, systems, and devices can be defined.

[0015] 3GPP's Long Term Evolution (LTE) is the name given to a project to improve the standards for mobile phones or devices for Universal Mobile Telecommunications Systems (UMTS) to address future requirements. In one aspect, UMTS has been modified to provide support and specifications for Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN).

[0016] At least some aspects of the systems and methods disclosed herein may be described in relation to 3GPP standards such as LTE, LTE-Advanced (LTE-A), LTE-Advanced Pro, and other standards (e.g., 3GPP Releases 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, and / or 18). However, the scope of this disclosure should not be limited to this. At least some aspects of the systems and methods disclosed herein may be used in other forms of wireless communication systems.

[0017] A wireless communication device can be an electronic device used to communicate voice and / or data to a base station. Similarly, it can communicate with the device's network (e.g., the public switched telephone network (PSTN), the Internet, etc.). When described in this specification, the system and method may alternatively refer to the wireless communication device as a mobile station, UE, access terminal, subscriber station, mobile terminal, remote station, user terminal, terminal, subscriber unit, mobile device, etc. Examples of wireless communication devices include cellular phones, smartphones, personal digital assistants (PDAs), laptop computers, netbooks, e-book readers, wireless modems, etc. In 3GPP specifications, a wireless communication device is generally referred to as a UE. However, since the scope of this disclosure should not be limited to the 3GPP standard, the terms "UE" and "wireless communication device" may be used interchangeably in this specification to mean the more general term "wireless communication device". A UE may more generally also be referred to as a terminal device.

[0018] In 3GPP specifications, a base station is usually referred to by terms such as Node B, evolved Node B (eNB), home enhanced or evolved Node B (HeNB), g Node B (gNB), or other similar specialized terms. Since the scope of this disclosure should not be limited to the 3GPP standard, the terms "base station", "Node B", "eNB", "gNB", and "HeNB" may be used interchangeably in this specification to mean the more general term "base station". Furthermore, the term "base station" may be used to mean an access point. An access point may also be an electronic device that provides access for a wireless communication device to a network (e.g., a local area network (LAN), the Internet, etc.). The term "communication device" may be used to represent both a wireless communication device and / or a base station. A gNB may more generally also be referred to as a base station device.

[0019] It should be noted that, as used herein, “cell” can be any communication channel defined by a standardization or regulatory body for use with International Mobile Telecommunications-Advanced (IMT-Advanced) or IMT-2020, all or part thereof, may be adopted by 3GPP as a licensed or unlicensed band (e.g., frequency bandwidth) for use with communication between an eNB or gNB and a UE. Furthermore, it should be noted that, in the overall description of E-UTRA and E-UTRAN, “cell” may be defined as “a combination of downlink and optionally uplink resources.” The coordination between the carrier frequencies of the downlink resources and the uplink resources may be indicated in the system information transmitted over the downlink resources.

[0020] Fifth-generation communication systems, known as NR (New Radio technologies) by 3GPP, are expected to utilize time / frequency / space resources to enable services such as eMBB (enhanced Mobile Broad-Band) transmission, URLLC (Ultra Reliable and Low Latency Communication) transmission, and mMTC (massive Machine Type Communication) transmission. Furthermore, NR allows for the specification (e.g., configuration) of different service transmissions for one or more bandwidth parts (BWPs) within a single serving cell and / or for one or more serving cells. User equipment (UE) may receive downlink signals and / or transmit uplink signals within the BWPs of one or more serving cells.

[0021] For a service to efficiently utilize time, frequency, and / or spatial resources, it would be useful to be able to efficiently control downlink and / or uplink transmissions. Therefore, procedures for efficiently controlling downlink and / or uplink transmissions should be designed. Thus, a detailed design of procedures for downlink and / or uplink transmissions may be beneficial.

[0022] In some cases, URLLC's UCI may have higher reliability and lower latency than eMBB. Some examples of the techniques described herein may achieve lower latency in mini-slot iterations by using the earliest DMRS that meets timings above the indicated timing in the PUSCH iteration.

[0023] Various examples of the systems and methods disclosed herein are described here with reference to the drawings. The same reference numerals may indicate functionally similar elements. The systems and methods described herein and shown in the drawings can be arranged and designed in a wide variety of different implementations. Accordingly, the following more detailed descriptions of some of the implementations shown in the drawings are not intended to limit the scope of this disclosure in accordance with the claims, but are merely representative of the systems and methods.

[0024] Figure 1 is a block diagram showing one implementation configuration of one or more gNB160s and one or more UE102s in which a system and method for signaling may be implemented. One or more UE102s communicate with one or more gNB160s using one or more physical antennas 122a-n. For example, a UE102 uses one or more physical antennas 122a-n to transmit electromagnetic signals to and receive electromagnetic signals from a gNB160. A gNB160 communicates with a UE102 using one or more physical antennas 180a-n. In some implementation configurations, the terms “base station”, “eNB”, and / or “gNB” may refer to and / or be replaced by “Transmission Reception Point” (TRP). For example, a gNB160 described in relation to Figure 1 may be a TRP in some implementation configurations.

[0025] UE102 and gNB160 may use one or more channels and / or one or more signals 119, 121 to communicate with each other. For example, UE102 may use one or more uplink channels 121 to transmit information or data to gNB160. Examples of uplink channels 121 include physical shared channels (e.g., PUSCH (Physical Uplink Shared Channel)) and / or physical control channels (e.g., PUCCH (Physical Uplink Control Channel)). One or more gNB160 may also use, for example, one or more downlink channels 119 to transmit information or data to one or more UE102. Examples of downlink channels 119 include physical shared channels (e.g., PDSCH (Physical Downlink Shared Channel)) and / or physical control channels (PDCCH (Physical Downlink Control Channel)). Other types of channels and / or signals may also be used.

[0026] Each of the one or more UE102 may include one or more transmit / receive units 118, one or more demodulator units 114, one or more decoders 108, one or more encoding units 150, one or more modulation units 154, a data buffer 104, and a UE operation module 124. For example, one or more receive paths and / or transmit paths may be implemented within the UE102. For convenience, only a single transmit / receive unit 118, decoding unit 108, demodulator unit 114, encoding unit 150, and modulation unit 154 is shown within the UE102, but multiple parallel elements (e.g., transmit / receive unit 118, decoding unit 108, demodulator unit 114, encoding unit 150, and modulation unit 154) may also be implemented.

[0027] The transmitting / receiving unit 118 may include one or more receiving units 120 and one or more transmitting units 158. One or more receiving units 120 may receive signals from the gNB 160 using one or more antennas 122a to n. For example, a receiving unit 120 may receive a signal and then downconvert it to generate one or more received signals 116. One or more received signals 116 may be provided to the demodulation unit 114. One or more transmitting units 158 may transmit signals to the gNB 160 using one or more physical antennas 122a to n. For example, one or more transmitting units 158 may upconvert and transmit one or more modulated signals 156.

[0028] The demodulator 114 may demodulate one or more received signals 116 to generate one or more demodulated signals 112. One or more demodulated signals 112 may be provided to the decoder 108. The UE 102 may decode the signals using the decoder 108. The decoder 108 may generate a plurality of decoded signals 110, which may include a UE decoded signal 106 (also called the first UE decoded signal 106). For example, the first UE decoded signal 106 may include received payload data, which may be stored in the data buffer 104. Another signal included in the decoded signal 110 (also called the second UE decoded signal 110) may include overhead data and / or control data. For example, the second UE decoded signal 110 may provide data that the UE operation module 124 can use to perform one or more operations.

[0029] Generally, the UE operation module 124 may enable the UE 102 to communicate with one or more gNB 160s. The UE operation module 124 may include one or more UE scheduling modules 126.

[0030] The UE scheduling module 126 can perform downlink reception and uplink transmission (for example, scheduling). Downlink reception includes receiving data, receiving downlink control information, and / or receiving downlink reference signals. Uplink transmission includes transmitting data, transmitting uplink control information, and / or transmitting uplink reference signals.

[0031] Furthermore, in carrier aggregation (CA), gNB160 and UE102 may communicate with each other using one or more serving cells, where one or more serving cells may include one primary cell and one or more secondary cells. For example, gNB160 may transmit information used to configure one or more secondary cells to form a set of serving cells together with a primary cell using RRC messages, where this set of serving cells may include one primary cell and one or more secondary cells, where the primary cell may always be activated. gNB160 may also activate one or more secondary cells within the configured secondary cell. Here, in the downlink, the carrier corresponding to the primary cell may be the downlink primary component carrier (i.e., DL PCC), and the carrier corresponding to the secondary cell may be the downlink secondary component carrier (i.e., DL SCC). Similarly, in the uplink, the carrier corresponding to the primary cell may be the uplink primary component carrier (i.e., UL PCC), and the carrier corresponding to the secondary cell may be the uplink secondary component carrier (i.e., UL SCC).

[0032] In wireless communication systems, physical channels (uplink physical channels and / or downlink physical channels) may be defined. These physical channels may be used to transmit information passed from higher layers.

[0033] In some examples, a Physical Random Access Channel (PRACH) may be defined on the uplink. In some approaches, the PRACH (e.g., Random Access Procedure) may be used for initial access connection establishment procedures, handover procedures, connection re-establishment, timing adjustments (e.g., synchronization for uplink transmissions for UL synchronization), and / or requests for uplink shared channel (UL-SCH) resources (e.g., uplink physical shared channel (PSCH) (e.g., PUSCH) resources).

[0034] In some examples, a physical uplink control channel (PUCCH) may be defined. A PUCCH may be used to transmit uplink control information (UCI). The UCI may include a hybrid automatic repeat request-acknowledgement (HARQ-ACK), channel status information (CSI), and / or a scheduling request (SR). The HARQ-ACK is used to indicate an acknowledgment (ACK) or negation (NACK) for downlink data (e.g., transport blocks, Medium Access Control Protocol Data Units (MAC PDUs), and / or downlink shared channels (DL-SCH)). The CSI is used to indicate the state of the downlink channel (e.g., downlink signals). The SR is used to request resources for uplink data (e.g., transport blocks, MAC PDUs, and / or uplink shared channels (UL-SCH)).

[0035] Here, DL-SCH and / or UL-SCH may be transport channels used in the MAC layer. Transport blocks (TBs) and / or MAC PDUs may also be defined as units of transport channels used in the MAC layer. A transport block may be defined as a unit of data passed from the MAC layer to the physical layer. The MAC layer may pass transport blocks to the physical layer (for example, the MAC layer passes data to the physical layer as transport blocks). In the physical layer, a transport block may be mapped to one or more codewords.

[0036] In a downlink, a physical downlink control channel (PDCCH) may be defined. The PDCCH may be used to transmit downlink control information (DCI). Here, two or more DCI formats may be defined for DCI transmission over the PDCCH. That is, fields may be defined within the DCI format, and these fields are mapped to information bits (e.g., DCI bits).

[0037] Additionally or alternatively, physical downlink shared channels (PDSCHs) and physical uplink shared channels (PUSCHs) may be defined. For example, if a PDSCH (e.g., a PDSCH resource) is scheduled using the DCI format for downlinks, UE102 may receive downlink data on the scheduled PDSCH (e.g., a PDSCH resource). Additionally or alternatively, if a PUSCH (e.g., a PUSCH resource) is scheduled using the DCI format for uplinks, UE102 may transmit uplink data on the scheduled PUSCH (e.g., a PUSCH resource). For example, a PDSCH may be used to transmit downlink data (e.g., DL-SCH, a downlink transport block). Additionally or alternatively, a PUSCH may be used to transmit uplink data (e.g., UL-SCH, an uplink transport block).

[0038] Furthermore, PDSCH and / or PUSCH may be used to transmit information from higher layers (e.g., the radio resource control (RRC) layer and / or the MAC layer). For example, PDSCH (e.g., from gNB160 to UE102) and / or PUSCH (e.g., from UE102 to gNB160) may be used to transmit RRC messages (RRC signals). Additionally or alternatively, PDSCH (e.g., from gNB160 to UE102) and / or PUSCH (e.g., from UE102 to gNB160) may be used to transmit MAC control elements (MAC CEs), where RRC messages and / or MAC CEs are also called higher-layer signals.

[0039] In some approaches, a physical broadcast channel (PBCH) may be defined. For example, a PBCH may be used to broadcast a master information block (MIB). Here, system information may be divided into the MIB and several system information blocks (SIBs). For example, an MIB may be used to carry minimal system information. Additionally or alternatively, SIBs may be used to carry system information messages.

[0040] In some approaches, a synchronization signal (SS) may be defined in the downlink. The SS may be used to obtain time and / or frequency synchronization with the cell. Additionally or alternatively, the SS may be used to detect the physical layer cell ID of the cell. The SS may include a primary SS and a secondary SS.

[0041] An SS / PBCH block can be defined as a set of primary SS, secondary SS, and PBCH. In the time domain, an SS / PBCH block may contain four OFDM symbols numbered in ascending order from 0 to 3 within the SS / PBCH block, with the PSS, SSS, and PBCH mapped to the symbols along with their associated demodulation reference signals (DMRS). One or more SS / PBCH blocks may be mapped within a given time period (e.g., 5 milliseconds).

[0042] Furthermore, the SS / PBCH block can also be used for beam measurement, radio resource management (RRM) measurement, and radio link control (RLM) measurement. Specifically, it can be used for measurement of secondary synchronization signals (SSS).

[0043] In uplink radio communications, UL RS may be used as the uplink physical signal. Additionally or alternatively, in downlink radio communications, DL RS may be used as the downlink physical signal. Uplink and / or downlink physical signals may be used by the physical layer, but they may not be used to transmit information provided from higher layers.

[0044] For the sake of simplicity, the downlink physical channels and / or downlink physical signals described herein may, in some implementations, be assumed to be included in the downlink signals (i.e., DL signals). Additionally or alternatively, for the sake of simplicity, the uplink physical channels and / or uplink physical signals described herein may, in some implementations, be assumed to be included in the uplink signals (i.e., UL signals).

[0045] Several techniques for tracking CSI-RS and time-domain correlation and / or Doppler information reporting are described below. UE102 may be configured using tracking NZP CSI-RS. UE102 may receive information on one or more sets of NZP CSI-RS resources (NZP-CSI-RS-ResourceSet) within an RRC message. Each NZP CSI-RS resource set may contain information for configuring one or more NZP CSI-RS resources (NZP-CSI-RS-Resource).

[0046] UE102 may be configured with one or more CSI reporting settings. For this purpose, UE102 may receive information containing one or more CSI reporting settings within an RRC message. Each CSI reporting setting (CSI-ReportConfig) may include information about CSI-RS resources for channel measurements, information about CSI-RS resources for interference measurements, the parameter ReportQuantity, the type of CSI reported by the corresponding CSI reporting setting (e.g., L1-RSRP (Layer-1 Reference Signal Reception Power), PMI (Precoding Matrix Indicator), CQI (Channel Quality Indicator), RI (Rank Indicator), CRI (CSI-RS Resource Indicator), and / or LI (Layer Indicator)), and the parameter reportConfigType indicating one of aperiodic CSI reporting, semi-persistent CSI reporting, and / or periodic CSI reporting.

[0047] UE102 in RRC connection mode can be expected to receive the upper-layer UE-specific settings of the NZP-CSI-RS-ResourceSet configured using the upper-layer parameter trs-Info. For an NZP-CSI-RS-ResourceSet configured using the upper-layer parameter trs-Info, UE102 can assume that the antenna ports with the same port index are the same for the NZP CSI-RS resources configured within that NZP-CSI-RS-ResourceSet.

[0048] For frequency range 1 (e.g., sub-6GHz), UE102 may be configured to have one or more NZP-CSI-RS resource sets, where the parameter NZP-CSI-RS-ResourceSet may contain four periodic NZP CSI-RS resources in two consecutive slots, with two periodic NZP CSI-RS resources in each slot. If there are no two consecutive slots designated as downlink slots by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigDedicated, UE102 may be configured to have one or more NZP CSI-RS sets, where NZP-CS-RS-ResourceSet may contain two periodic NZP CSI-RS resources in one slot.

[0049] For frequency range 2, UE102 may be configured to have one or more NZP CSI-RS sets, where the NZP-CSI-RS-ResourceSet may contain two periodic NZP CSI-RS resources in one slot, or it may be configured to have an NZP-CSI-RS-ResourceSet with four periodic NZP CSI-RS resources in two consecutive slots, with two periodic NZP CSI-RS resources in each slot.

[0050] UE102 configured with an NZP-CSI-RS-ResourceSet set using the upper layer parameter trs-Info may have NZP CSI-RS resources configured as periodic, provided that the CSI-RS resources within the parameter NZP-CSI-RS-ResourceSet are configured with the same periodicity, bandwidth, and subcarrier position.

[0051] UE102 configured with an NZP-CSI-RS-ResourceSet set using the upper layer parameter trs-Info may have NZP CSI-RS resources configured as periodic CSI-RS resources in one set and a non-periodic CSI-RS resources in a second set, where the non-periodic CSI-RS and periodic CSI-RS resources have the same bandwidth (have the same RB position), and the non-periodic CSI-RS has qcl-Type set to "Type A" and "Type D", and has periodic CSI-RS resources if corresponding. For frequency range 2, the UE may have a scheduling offset between the last symbol of the PDCCH carrying the triggering DCI and the first symbol of the non-periodic CSI-RS resource within the CSI-RS symbol.

number

[0052] UE102 may not be expected to be configured using trs-Info and a CSI-ReportConfig linked to a CSI-ResourceConfig that includes an NZP-CSI-RS-ResourceSet, which is configured using the higher-level parameter timeRestrictionForChannelMeasurements set in "Settings".

[0053] UE102 may not be expected to be configured with an NZP-CSI-RS-ResourceSet that has been set using both trs-Info and repetition.

[0054] If UE102 is configured using CSI-ReportConfig with the upper-layer parameter reportQuantity set to "none" for a non-periodic NZP CSI-RS resource set using trs-Info, UE102 can receive tracking NZP CSI-RS and perform time and frequency channel tracking.

[0055] Several examples of techniques for tracking CSI-RS and time-domain correlation and / or Doppler information reporting are provided below: UE102 may be configured with aperiodic CSI-RS for tracking within an NZP-CSI-RS resource set configured with trs-Info. UE102 may be configured with pseudo-static CSI-RS for tracking within an NZP-CSI-RS resource set configured with trs-Info. UE102 may be configured with periodic CSI-RS for tracking within an NZP-CSI-RS resource set configured with trs-Info.

[0056] UE102 can be configured using CSI-ReportConfig for a periodic NZP-CSI-RS resource set configured using trs-Info.

[0057] If UE102 is not configured using CSI-ReportConfig for a periodic NZP-CSI-RS resource set configured using trs-Info, UE102 may receive NZP CSI-RS for tracking and perform time and frequency channel tracking.

[0058] UE102 can be configured using CSI-ReportConfig for a semi-persistent NZP CSI-RS resource set configured using trs-Info. If the semi-persistent NZP CSI-RS resource set is configured using trs-Info, UE102 may also be configured using CSI-ReportConfig, in which case the parameter reportQuantity in CSI-ReportConfig is set to "TDCI".

[0059] If UE102 is configured using CSI-ReportConfig with the upper-layer parameter reportQuantity set to a parameter other than "none" (e.g., TDCI: information about time-domain interphases), UE102 may receive tracking CSI-RS, perform time and frequency channel tracking, and measure information about time-domain correlation. Based on the measurements of the tracking CSI-RS, UE102 may transmit time-domain correlation information. One or more of the following information may be defined as TDCI: - Information regarding time-domain correlation values ​​measured from multiple tracking CSI-RSs received during different time-domain transmission and reception opportunities. - Information regarding the difference in received power between tracking CSI-RSs received during transmission and reception in different time domains. - Information regarding the difference in signal-to-interference plus noise power ratio (SINR) between the tracking CSI-RS received during different time-domain transmission and reception opportunities. - Information regarding the phase rotation values ​​between the tracking CSI-RS received during transmission and reception in different time domains.

[0060] In some examples, each CSI-RS resource may be configured by the higher-level parameter NZP-CSI-RS-Resource, subject to one or more of the following limitations: -As defined by the higher-level parameter CSI-RS-resourceMapping, the time-domain location of two CSI-RS resources in one slot, or four CSI-RS resources in two consecutive slots (the same across the two consecutive slots), can be given by one of the following: Regarding frequency range 1 (sub-6GHz) and frequency range 2 (above 6GHz),

number

number

number

number

number

number

number

number

number

number

number

[0061] Additionally or alternatively, UE102 may measure time-domain correlations by using a tracking CSI-RS associated with the parameter NZP-CSI-RS-ResourceSet, which is set using the parameter trs-Info, and the parameter CSI-Report-Config, which is set using reportQuantity as TDCI.

[0062] Additionally or alternatively, UE102 may measure time-domain correlations by using a tracking CSI-RS associated with the parameter NZP-CSI-RS-ResourceSet, which is set using the parameter trs-Info, and the parameter CSI-Report-Config, which is set using "none" and reportQuantity as TDCI.

[0063] Additionally or alternatively, the parameter reportQuantity set for "TDCI" may be set separately from other CSI components (e.g., PMI, CQI, RI, LI, and / or CRI). The parameter reportQuantity set for "TDCI" may be set together with other CSI components (e.g., PMI, CQI, RI, LI, and / or CRI). In this case, reportQuantity may be set to a different parameter name (e.g., "TDCI-PMI-CQI-RI" if CQI, PMI, RI, and TDCI are reported).

[0064] Additionally or alternatively, UE102 may be configured using time-domain predictions from the tracking CSI-RS based on information provided by the RRC message, and may reflect time-domain correlations with reported CSIs such as CQI, PMI, RI, LI, and / or CRI. In this case, the parameter reportQuantity in the parameter CSI-ReportConfig related to the tracking CSI-RS, configured by the parameter NZP-CSI-RS-ResourceSet configured using the parameter trs-Info, may be set to "none". Additionally or alternatively, the parameter reportQuantity in the parameter CSI-ReportConfig related to the tracking CSI-RS, configured by the parameter NZP-CSI-RS-ResourceSet configured using the parameter trs-Info, may be set to TDCI.

[0065] Additionally or alternatively, UE102 may transmit UE capability information to support time-domain correlation information measurement. UE capability may include the maximum number of simultaneous calculations with other CSI components (e.g., L1-RSRP, PMI, CQI, RI, LI, and / or CRI). UE capability may be defined for each component carrier, each cell, and / or each frequency band.

[0066] Additionally or alternatively, UE capability may include processing time separate from the measurement of L1-RSRP, PMI, CQI, RI, LI, and / or CRI.

[0067] Additionally or alternatively, DCI on PDCCH may indicate TDCI reporting to UE102. MAC CE may activate TDCI reporting. Additionally or alternatively, TDCI may be transmitted on PUSCH and / or PUCCH.

[0068] If periodic CSI reporting including TDCI reporting is configured, PUCCH or PUSCH may be used. If semi-persistent CSI reporting including TDCI reporting is configured, PUCCH or PUSCH may be used. If aperiodic CSI reporting including TDCI reporting is configured, PUSCH or PUCCH may be used. Periodic, semi-persistent, and / or aperiodic CSI reporting can be configured by parameters in CSI-ReportConfig.

[0069] The UE operation module 124 may provide information 148 to one or more receivers 120. For example, the UE operation module 124 can notify the receivers 120 of when to receive a retransmission.

[0070] The UE operation module 124 may provide information 138 to the demodulator 114. For example, the UE operation module 124 may notify the demodulator 114 of the expected modulation pattern for transmission from the gNB 160.

[0071] The UE operation module 124 may provide information 136 to the decoding unit 108. For example, the UE operation module 124 may notify the decoding unit 108 of the expected encoding for transmissions from the gNB 160.

[0072] The UE operation module 124 may provide information 142 to the encoding unit 150. The information 142 may include data to be encoded and / or instructions for encoding. For example, the UE operation module 124 may instruct the encoding unit 150 to encode the transmission data 146 and / or other information 142. The other information 142 may include PDSCH HARQ-ACK information.

[0073] The encoding unit 150 can encode the transmission data 146 and / or other information 142 provided by the UE operation module 124. For example, encoding the data 146 and / or other information 142 may involve error detection and / or correction encoding, mapping the data to spatial, temporal, and / or frequency resources for transmission, multiplexing, etc. The encoding unit 150 can provide the encoded data 152 to the modulation unit 154.

[0074] The UE operation module 124 may provide information 144 to the modulation unit 154. For example, the UE operation module 124 may inform the modulation unit 154 of the type of modulation (e.g., signal space mapping) to be used for transmission to the gNB 160. The modulation unit 154 may modulate the encoded data 152 to provide one or more modulated signals 156 to one or more transmitters 158.

[0075] The UE operation module 124 may provide information 140 to one or more transmitters 158. The information 140 may include instructions for one or more transmitters 158. For example, the UE operation module 124 may instruct one or more transmitters 158 when to transmit a signal to the gNB 160. For example, one or more transmitters 158 may transmit in a UL subframe. One or more transmitters 158 may upconvert a modulated signal 156 and transmit it to one or more gNBs 160.

[0076] Each of the one or more gNB160s may include one or more transmit / receive units 176, one or more demodulator units 172, one or more decoders 166, one or more encoding units 109, one or more modulation units 113, a data buffer 162, and a gNB operation module 182. For example, one or more receive and / or transmit paths may be implemented in the gNB160. For convenience, only a single transmit / receive unit 176, decoding unit 166, demodulator unit 172, encoding unit 109, and modulation unit 113 is shown within the gNB160, but multiple parallel elements (e.g., transmit / receive unit 176, decoding unit 166, demodulator unit 172, encoding unit 109, and modulation unit 113) may be implemented.

[0077] The transmitting / receiving unit 176 may include one or more receiving units 178 and one or more transmitting units 117. One or more receiving units 178 may receive signals from UE 102 using one or more physical antennas 180a to n. For example, a receiving unit 178 may receive a signal and then downconvert it to generate one or more received signals 174. One or more received signals 174 may be provided to the demodulation unit 172. One or more transmitting units 117 may transmit signals to UE 102 using one or more physical antennas 180a to n. For example, one or more transmitting units 117 may upconvert and transmit one or more modulated signals 115.

[0078] The demodulation unit 172 may demodulate one or more received signals 174 to generate one or more demodulated signals 170. One or more demodulated signals 170 may be provided to the decoding unit 166. The gNB 160 may decode the signals using the decoding unit 166. The decoding unit 166 may generate one or more decoded signals 164, 168. For example, the first gNB decoded signal 164 may contain received payload data, which may be stored in the data buffer 162. The second gNB decoded signal 168 may contain overhead data and / or control data. For example, the second gNB decoded signal 168 may provide data (e.g., PDSCH HARQ-ACK information) that the gNB operation module 182 can use to perform one or more operations.

[0079] Generally, the gNB operation module 182 may enable the gNB 160 to communicate with one or more UE 102s. The gNB operation module 182 may include one or more gNB scheduling modules 194. The gNB scheduling module 194 may schedule downlink transmissions and / or uplink transmissions as described herein.

[0080] The gNB operation module 182 may provide information 188 to the demodulation unit 172. For example, the gNB operation module 182 may notify the demodulation unit 172 of the expected modulation pattern for transmission from the UE 102.

[0081] The gNB operation module 182 may provide information 186 to the decoding unit 166. For example, the gNB operation module 182 may notify the decoding unit 166 of the expected encoding for a transmission from the UE 102.

[0082] The gNB operation module 182 may provide information 101 to the encoding unit 109. The information 101 may include the data to be encoded and / or instructions for encoding. For example, the gNB operation module 182 may instruct the encoding unit 109 to encode information 101 including the transmission data 105.

[0083] The encoding unit 109 can encode the transmission data 105 and / or other information contained in the information 101 provided by the gNB operating module 182. For example, encoding the data 105 and / or other information contained in the information 101 may involve error detection and / or correction encoding, mapping the data to spatial, temporal, and / or frequency resources for transmission, multiplexing, etc. The encoding unit 109 can provide the encoded data 111 to the modulation unit 113. The transmission data 105 may include network data to be relayed to the UE 102.

[0084] The gNB operation module 182 may provide information 103 to the modulation unit 113. The information 103 may include instructions for the modulation unit 113. For example, the gNB operation module 182 may inform the modulation unit 113 of the type of modulation (e.g., signal space mapping) to be used for transmission to the UE 102. The modulation unit 113 may modulate the encoded data 111 to provide one or more modulated signals 115 to one or more transmitters 117.

[0085] The gNB operation module 182 may provide information 192 to one or more transmitters 117. The information 192 may include instructions for one or more transmitters 117. For example, the gNB operation module 182 may instruct one or more transmitters 117 when to transmit (or not transmit) a signal to the UE 102. One or more transmitters 117 may upconvert the modulated signal 115 and transmit it to one or more UEs 102.

[0086] It should be noted that DL subframes may be sent from gNB160 to one or more UE102s, and UL subframes may be sent from one or more UE102s to gNB160. Furthermore, both gNB160 and one or more UE102s may send data in standard special subframes.

[0087] It should be noted that one or more of the elements or components included in gNB160 and UE102 may be implemented in hardware. For example, one or more of those elements or components may be implemented as a chip, circuit, or hardware component. Furthermore, it should be noted that one or more of the functions or methods described herein may be implemented in hardware and / or implemented using hardware. For example, one or more of the methods described herein may be implemented in and / or implemented using a chipset, application-specific integrated circuit (ASIC), large-scale integrated circuit (LSI), or integrated circuit.

[0088] Figure 2 shows an example of multiple neurology 201. As shown in Figure 2, multiple neurology 201 (e.g., multiple subcarrier intervals) may be supported. For example, μ (e.g., subcarrier space setting) and cyclic prefixes (e.g., μ and cyclic prefixes for the carrier bandwidth portion) may be set by higher-layer parameters (e.g., RRC messages) for the downlink and / or uplink. Here, 15 kHz may be the reference neurology 201. For example, the RE of the reference neurology 201 may be defined as a subcarrier interval of 15 kHz in the frequency domain and as 2048 Ts + CP length (e.g., 160 Ts or 144 Ts) in the time domain, where Ts represents the baseband sampling time unit defined as 1 / (15000 * 2048) seconds.

[0089] Additionally or alternatively, the number of OFDM symbols 203 per slot.

number

[0090] Figure 3 shows an example of a resource grid 301 and resource block 391 (for example, for downlinks and / or uplinks). The resource grid 301 and resource block 391 shown in Figure 3 may be used in some implementations of the systems and methods disclosed herein.

[0091] In Figure 3, one subframe 369 is,

number

[0092] Additionally or alternatively, in addition to CP-OFDM, a single-carrier frequency division multiple access (SC-FDMA) access scheme may be used on the uplink, also known as discrete Fourier transform-spread OFDM (DFT-S-OFDM). An uplink radio frame may contain multiple pairs of uplink resource blocks 391. An uplink RB pair is a unit for allocating uplink radio resources defined by a given bandwidth (RB bandwidth) and time slot. An uplink RB pair may contain two consecutive uplink RBs 391 in the time domain. An uplink RB may contain 12 subcarriers in the frequency domain and 7 (for normal CP) or 6 (for extended CP) OFDM / DFT-S-OFDM symbols in the time domain. A region defined by one subcarrier in the frequency domain and one OFDM / DFT-S-OFDM symbol in the time domain is called a resource element (RE) 389 and is uniquely identified within the slot by an index pair (k,l), where k and l are indices in the frequency domain and time domain, respectively.

[0093] Each element in the resource grid 301 (e.g., antenna port p) and subcarrier configuration μ is called a resource element 389 and is uniquely identified by an index pair (k,l), where k=0, ...

number

number

number

number

[0094] In NR, the following reference signals may be defined: • NZP CSI-RS (Non-Zero Power Channel Status Information Reference Signal) • ZP CSI-RS (Zero Power Channel Status Information Reference Signal) • DMRS (Demodulated Reference Signal) • SRS (Sounding Reference Signal)

[0095] NZP CSI-RS can be used for channel tracking (e.g., synchronization), measurements to acquire CSI (including channel and interferometric measurements), and / or measurements to acquire beamforming performance. NZP CSI-RS can be transmitted on the downlink (gNB to UE). NZP CSI-RS can be transmitted in a non-periodic, semi-persistent, or periodic manner. Furthermore, NZP CSI-RS can be used for radio resource management (RRM) and radio link control (RLM) measurements.

[0096] ZP CSI-RS is used for interferometric measurements and can be transmitted over the downlink (gNB to UE). ZP CSI-RS can be transmitted in a non-periodic, semi-persistent, or periodic manner.

[0097] DMRS can be used for demodulation of downlinks (gNB to UE), uplinks (UE to gNB), and sidelinks (UE to UE).

[0098] SRS can be used for channel sounding and beam management. SRS can be transmitted on the uplink (UE to gNB).

[0099] Some approaches may use DCI. The following DCI formats may be defined. DCI format 0_0 • DCI Format 0_1 • DCI Format 0_2 • DCI Format 1_0 • DCI Format 1_1 • DCI Format 1_2 • DCI Format 2_0 • DCI Format 2_1 • DCI Format 2_2 • DCI Format 2_3 • DCI Format 2_4 • DCI Format 2_5 • DCI Format 2_6 • DCI Format 3_0 • DCI Format 3_1

[0100] DCI format 1_0 may be used for scheduling pushes within a single cell. DCI may be transmitted in DCI format 0_0, which has a cyclic redundancy check (CRC) scrambled by a Cell Radio Network Temporary Identifier (C-RNTI), a Configured Scheduling RNTI (CS-RNTI), or a Modulation and Coding Scheme-Cell RNTI (MCS-C-RNTI).

[0101] DCI format 0_1 ​​may be used for scheduling one or more pushes within a single cell, or to indicate Configured Grant Downlink Feedback Information (CG-DFI) to the UE. DCI may be transmitted by DCI format 0_1 ​​having a CRC scrambled by C-RNTI or CS-RNTI or Semi-Persistent Channel State Information (SP-CSI-RNTI) or MCS-C-RNTI. DCI format 0_2 may be used for CSI requests (e.g., aperiodic CSI reports or semi-persistent CSI requests). DCI format 0_2 may be used for SRS requests (e.g., aperiodic SRS transmissions).

[0102] DCI format 0_2 can be used for scheduling pushes in a single cell. DCI can be transmitted in DCI format 0_2 with a CRC scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI, or MCS-C-RNTI. DCI format 0_2 can be used for scheduling pushes with high priority and / or low latency (e.g., URLLC). DCI format 0_2 can be used for CSI requests (e.g., aperiodic CSI reports or semi-persistent CSI requests). DCI format 0_2 can be used for SRS requests (e.g., aperiodic SRS transmissions).

[0103] Additionally, for example, a DCI contained in DCI format 0_Y (Y=0, 1, 2, ...) could be a BWP indicator (e.g., for PUSCH). Additionally or alternatively, a DCI contained in DCI format 0_Y could be a frequency-domain resource allocation (e.g., for PUSCH). Additionally or alternatively, a DCI contained in DCI format 0_Y could be a time-domain resource allocation (e.g., for PUSCH). Additionally or alternatively, a DCI contained in DCI format 0_Y could be a modulation and encoding scheme (e.g., for PUSCH). Additionally or alternatively, a DCI contained in DCI format 0_Y could be a new data indicator. Additionally or alternatively, a DCI contained in DCI format 0_Y could be a scheduled TPC command for PUSCH. Additionally or alternatively, a DCI contained in DCI format 0_Y could be a CSI request used to request a CSI report. Additionally or alternatively, the DCIs included in DCI format 0_Y may be information used to indicate the setting index of a setting grant, as described below. Additionally or alternatively, the DCIs included in DCI format 0_Y may be priority indicators (e.g., for push transmit and / or push receive).

[0104] DCI format 1_0 may be used for scheduling PDSCH within a single DL cell. DCI is transmitted in DCI format 1_0 with a CRC scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI. DCI format 1_0 may be used for random access procedures initiated by a PDCCH order. Additionally or alternatively, DCI may be transmitted in DCI format 1_0 with a CRC scrambled by a System Information RNTI (SI-RNTI), and DCI may be used for transmitting and / or receiving system information. Additionally or alternatively, DCI may be transmitted in DCI format 1_0 with a CRC scrambled by a Random Access RNTI (RA-RNTI) for a Random Access Response (RAR) for a 2-step RACH (e.g., Msg2) or for msgB-RNTI. Additionally or alternatively, DCI may be transmitted in DCI format 1_0 with a CRC scrambled by a temporary cell RNTI (TC-RNTI), and DCI may be used for msg3 transmission by UE102.

[0105] DCI format 1_1 can be used for scheduling PDSCHs within a single cell. DCI can be transmitted in DCI format 1_1 with a CRC scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI. DCI format 1_1 can be used for SRS requests (e.g., aperiodic SRS transmissions).

[0106] DCI format 1_2 can be used for scheduling PDSCHs within a single cell. DCI can be transmitted in DCI format 1_2 with a CRC scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI, or MCS-C-RNTI. DCI format 1_2 can be used for scheduling PDSCHs with high priority and / or low latency (e.g., URLLC). DCI format 1_2 can be used for SRS requests (e.g., aperiodic SRS transmissions).

[0107] Additionally, for example, a DCI included in DCI format 1_X may be a BWP indicator (e.g., for a PDSCH). Additionally or alternatively, a DCI included in DCI format 1_X may be a frequency domain resource allocation (e.g., for a PDSCH). Additionally or alternatively, a DCI included in DCI format 1_X may be a time domain resource allocation (e.g., for a PDSCH). Additionally or alternatively, a DCI included in DCI format 1_X may be a modulation and encoding scheme (e.g., for a PDSCH). Additionally or alternatively, a DCI included in DCI format 1_X may be a new data indicator. Additionally or alternatively, a DCI included in DCI format 1_X may be a TPC command for a scheduled PUCCH. Additionally or alternatively, a DCI included in DCI format 1_X may be a CSI request used to request (e.g., trigger) the transmission of a CSI (e.g., a CSI report (e.g., aperiodic CSI report)). Additionally or alternatively, DCIs included in DCI format 1_X may be PUCCH resource indicators. Additionally or alternatively, DCIs included in DCI format 1_X may be PDSCH to HARQ feedback timing indicators. Additionally or alternatively, DCIs included in DCI format 1_X may be priority indicators (e.g., PDSCH transmission and / or PDSCH reception). Additionally or alternatively, DCIs included in DCI format 1_X may be priority indicators (e.g., PDSCH HARQ-ACK transmission and / or PDSCH HARQ-ACK reception).

[0108] DCI format 2_0 may be used to indicate the slot format, the duration of channel occupancy time (COT) during unlicensed band operation, the available resource block (RB) set, and search space group switching. DCI may be transmitted in DCI format 2_0 with a CRC scrambled by the slot format indicator RNTI (SFI-RNTI).

[0109] DCI format 2_1 may be used to notify a UE of physical resource blocks (PRBs) and orthogonal frequency division multiplexing (OFDM) symbols when it can be assumed that transmission to that UE is not intended. DCI is transmitted in DCI format 2_1 with a CRC scrambled by an Interrupted Transmission RNTI (INT-RNTI).

[0110] DCI format 2_2 can be used to transmit Transmission Power Control (TPC) commands for PUCCH and PUSCH. The following information is transmitted in DCI format 2_2 with a CRC scrambled by TPC-PUSCH-RNTI or TPC-PUCCH-RNTI. If the CRC is scrambled by TPC-PUSCH-RNTI, one or more TPC commands indicated may be applied to the TPC loop of PUSCH. If the CRC is scrambled by TPC-PUCCH-RNTI, one or more TPC commands indicated may be applied to the TPC loop of PUCCH.

[0111] DCI format 2_3 can be used to send a group of TPC commands for SRS transmission by one or more UEs. Along with the TPC commands, an SRS request may also be sent. The DCI may be sent in DCI format 2_3 with a CRC scrambled by TPC-SRS-RNTI.

[0112] DCI format 2_4 may be used to notify PRB and OFDM symbols when a UE cancels a corresponding UL transmission. DCI may be transmitted in DCI format 2_4 with a CRC scrambled by a Cancellation Indication RNTI (CI-RNTI).

[0113] DCI format 2_5 may be used to notify the availability of soft resources for Integrated Access and Backhaul (IAB) operations. DCI may be transmitted in DCI format 2_5 with a CRC scrambled by Availability Indication RNTI (AI-RNTI).

[0114] DCI format 2_6 may be used to notify power saving information outside of the intermittent reception (DRX) active time of one or more UEs. DCI may be transmitted in DCI format 2_6 with a CRC scrambled by a power saving RNTI (PS-RNTI).

[0115] DCI format 3_0 can be used for scheduling NR physical sidelink control channels (PSCCH) and NR physical sidelink shared channels (PSSCH) within a single cell. DCI can be transmitted in DCI format 3_0 with a CRC scrambled by a sidelink RNTI (SL-RNTI) or sidelink configured scheduling RNTI (SL-CS-RNTI). This can be used for V2X (Vehicle to Everything) operation of an NR V2X UE.

[0116] DCI format 3_1 can be used for scheduling LTE PSCCH and LTE PSSCH within a single cell. The following information is transmitted in DCI format 3_1 with a CRC scrambled by SL-L-CS-RNTI. This can be used for LTE V2X operation of an LTE V2X UE.

[0117] UE102 may monitor one or more DCI formats on a shared search space set (CSS) and / or a UE-specific search space set (USS). The set of PDCCH candidates for UE to monitor may be defined in terms of a PDCCH search space set. A search space set may be a CSS set or a USS set. UE102 monitors PDCCH candidates in one or more of the following search space sets. A search space may be defined by the PDCCH configuration within the RRC layer.

[0118] The Type0-PDCCH CSS set can be configured for DCI formats having a CRC scrambled by SI-RNTI on the primary cell of the MCG, by pdcch-ConfigSIB1 in the MIB, by searchSpaceSIB1 in PDCCH-ConfigCommon, or by searchSpaceZero in PDCCH-ConfigCommon.

[0119] The Type0A-PDCCH CSS set can be configured by searchSpaceOtherSystemInformation within PDCCH-ConfigCommon for DCI formats having CRCs scrambled by SI-RNTI on the primary cell of the MCG.

[0120] The Type1-PDCCH CSS set can be configured by ra-SearchSpace in PDCCH-ConfigCommon for DCI formats having CRCs scrambled by RA-RNTI or TC-RNTI on the primary cell.

[0121] The Type2-PDCCH CSS set can be configured by pagingSearchSpace in PDCCH-ConfigCommon for DCI formats with CRCs scrambled by P-RNTI above in the primary cell of the MCG.

[0122] The Type3-PDCCH CSS set can be configured by SearchSpace in PDCCH-Config with searchSpaceType=common for DCI formats having CRCs scrambled by INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, TPC-SRS-RNTI, CI-RNTI, or PS-RNTI, and only for primary cells, C-RNTI, MCS-C-RNTI, or CS-RNTI.

[0123] The USS set can be configured by SearchSpace in PDCCH-Config, where searchSpaceType=ue-Specific, for DCI formats having CRCs scrambled by C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, CS-RNTI, SL-RNTI, SL-CS-RNTI, or SL-L-CS-RNTI.

[0124] UE102 may monitor a set of candidate PDCCHs within one or more control resource sets (e.g., CORESETs) on the Active DL Bandwidth Portion (BWP) on each activated serving cell, according to the corresponding search space set. CORESETs may be configured from gNB160 to UE102, and CSS sets and USS sets are defined within the configured CORESETs. One or more CORESETs may be configured within the RRC layer.

[0125] Figure 4 shows an example of a resource area (e.g., a resource area for a downlink). For DL ​​control channel monitoring (e.g., PDCCH monitoring), one or more sets 401 of PRB491 (e.g., a control resource set (e.g., CORESET)) may be configured. For example, CORESET is a set 401 of PRB491 that UE102 attempts to decode DCI (e.g., DCI format, PDCCH) in the frequency domain and / or time domain, where PRB491 may or may not be frequency continuous and / or time continuous, and UE102 may be configured to have one or more control resource sets (e.g., CORESET), where one DCI message may be mapped within one control resource set. In the frequency domain, PRB491 is the resource unit size of the DL control channel (may or may not include DM-RS).

[0126] Figure 5 shows examples of beamforming and quasi-collocation (QCL) types. In NR, the gNB560 and UE502 can perform beamforming by having multiple antenna elements. Beamforming is operated by using directional antennas or by applying phase shifts to each antenna element (for example, high electric field intensity can be achieved in a specific spatial direction). In some examples, beamforming or beam is rephrased as "spatial domain transmit filter" or "spatial domain filter".

[0127] On the downlink, the gNB560 can apply transmit beamforming to transmit DL channels and / or DL ​​signals, and the UE502 can apply receive beamforming to receive DL channels and / or DL ​​signals.

[0128] On the uplink, the UE560 can apply transmit beamforming to transmit UL channels and / or UL signals, and the gNB560 can apply receive beamforming to receive UL channels and / or UL signals.

[0129] Beam correspondence can be defined according to UE capabilities. In some examples, beam correspondence can be defined as follows: On a downlink, UE502 can determine the transmit beamforming for UL channels and / or UL signals from the receive beamforming for DL ​​channels and / or DL ​​signals. On an uplink, gNB560 can determine the transmit beamforming for DL ​​channels and / or DL ​​signals from the receive beamforming for UL channels and / or UL signals.

[0130] Beam management may be performed to adaptively switch, fine-tune, or manipulate beamforming. For beam management, channel quality on the downlink and uplink may be measured using NZP-CSI-RS and SRS, respectively. Specifically, on the downlink, gNB560 may transmit one or more NZP CSI-RSs. These one or more NZP CSI-RSs may be measured by UE502. Furthermore, UE502 may change beamforming to receive each NZP CSI-RS. UE502 can identify which combination of transmit beamforming on the gNB side corresponds to the corresponding NZP CSI-RS and the receive beamforming on the UE side. On the uplink, UE502 may transmit one or more SRSs. These one or more SRSs are measured by gNB502. Furthermore, gNB560 may change receive beamforming to receive each SRS. The gNB560 can identify which combination of transmit beamforming on the UE side corresponds to the corresponding SRS, as well as the receive beamforming on the gNB side.

[0131] To maintain the transmit beam-receive link for communication between the gNB560 and UE502, a pseudo-collocation (QCL) assumption can be defined. Two antenna ports are said to be pseudo-collocated if the large-scale characteristics of the channel on which symbols are transmitted on one antenna port can be inferred from the channel on which symbols are transmitted on the other antenna port. Large-scale characteristics include one or more of the following: delay spread, Doppler spread, Doppler shift, mean gain, mean delay, and spatial Rx parameters. The following QCL types can be defined: QCL Type A ("QCL-TypeA"): {Doppler shift, Doppler spread, mean delay, delay spread} QCL Type B ("QCL-TypeB"): {Doppler shift, Doppler spread} QCL-Type C: {Doppler shift, mean delay} • QCL Type D ("QCL-TypeD"): {Spatial Rx parameter}

[0132] QCL type D is related to beam management. For example, two NZP CSI-RS resources are configured for UE502, and NZP CSI-RS resource #1 and NZP CSI-RS resource #2 are used for beam #1 and beam #2, respectively. On the UE side, Rx beam #1 is used to receive NZP CSI-RS #1, and Rx beam #2 is used to receive NZP CSI-RS #2 for beam management. Here, NZP CSI-RS resource #1 and NZP CSI-RS resource #2 imply Tx beam #1 and Tx beam #2, respectively. The QCL type D assumption can be used to receive PDCCH, PDSCH, and DL signals. When UE502 receives PDCCH with the QCL type D assumption of NZP CSI-RS #1, UE502 may use Rx beam #2 for PDCCH reception.

[0133] For this purpose, the gNB560 may set a Transmit Configuration Instruction (TCI) state for the UE502. The TCI state may include the following: • One or more reference resource indicators • QCL type for each of the one or more referenced resource indexes

[0134] For example, if the TCI state includes QCL type D and NZP CSI-RS#1 and is indicated in UE502, UE502 may apply Rx beam #1 to the reception of PDCCH, PDSCH, and / or DL ​​signals. In other words, UE502 can determine the receiving beam by using the TCI state for the reception of PDCCH, PDSCH, and / or DL ​​signals.

[0135] Figure 6 shows an example of a Transmit Setting Instruction (TCI) state. Seven TCI states can be set, and one of the set TCI states may be used to receive PDCCH, PDSCH, and / or DL ​​signals. For example, if gNB560 indicates TCI state #1, UE502 may assume that the PDCCH, PDSCH, and / or DL ​​signals are pseudo-collocated with the NZP CSI-RS corresponding to NZP CSI-RS resource #1. UE502 may decide to use the received beam when UE502 receives the NZP CSI-RS corresponding to NZP CSI-RS resource #1.

[0136] Next, we will describe how gNB560 can indicate a single TCI state to UE502. Within an RRC message, N TCI states may be set by the RRC message. gNB560 may indicate one of the set TCI states by DCI (e.g., DCI format 1_1 or DCI format 1_2). Alternatively or additionally, gNB560 may indicate one of the set TCI states by MAC CE. Alternatively or additionally, MAC CE may select two or more of the set TCI states, and DCI may indicate one of the two or more TCI states activated by MAC CE.

[0137] Figure 7 is a flowchart illustrating an example of Method 700 by some of the techniques described herein. In some examples, Method 700 may be carried out by UE102, which is described in relation to Figure 1.

[0138] In 702, the UE may receive first information for setting up one or more tracking CSI-RSs, and second information for setting up information regarding time-domain correlations. In some examples, this may be done as described in relation to Figure 1.

[0139] In 704, the UE may send a CSI report containing information about time-domain correlations. The first parameter, trs-Info, may be included in the first information. The second parameter, reportQuantity, cannot be set to "none". Information about time-domain correlations may be measured by one or more tracking CSI-RSs. In some examples, this may be done as described in relation to Figure 1.

[0140] Figure 8 is a flowchart illustrating an example of Method 800 by some of the techniques described herein. In some examples, Method 800 may be carried out by gNB160, which was described in relation to Figure 1.

[0141] In 802, the gNB may transmit first information for setting up one or more tracking CSI-RSs, and second information for setting up information regarding time-domain correlations. In some examples, this may be done as described in relation to Figure 1.

[0142] In 804, the gNB may receive a CSI report containing information about time-domain correlations. The first parameter, trs-Info, may be included in the first information. The second parameter, reportQuantity, cannot be set to "none". Information about time-domain correlations may be measured by one or more tracking CSI-RSs. In some examples, this may be done as described in relation to Figure 1.

[0143] Figure 9A is a flowchart illustrating an example of Method 900a by some of the techniques described herein. In some examples, Method 900a may be carried out by UE102, which was described in relation to Figure 1.

[0144] In 902a, the UE may receive first information for setting up one or more tracking CSI-RSs, and second information for setting up information regarding time-domain correlations. In some examples, this may be done as described in relation to Figure 1.

[0145] In 904a, the UE may transmit a CSI report containing information on time-domain correlations. A first parameter, trs-Info, may be included in the first information. A second parameter may indicate one of the following: a periodic CSI report, a semi-persistent CSI report, or a non-periodic CSI report. Information on time-domain correlations may be measured by one or more tracking CSI-RSs. A CSI report containing information on time-domain correlations may be transmitted based on the second parameter. In some examples, this may be done as described in relation to Figure 1.

[0146] Figure 9B is a flowchart illustrating an example of Method 900b by some of the techniques described herein. In some examples, Method 900b may be carried out by gNB160, which was described in relation to Figure 1.

[0147] In 902b, the gNB may transmit first information for setting up one or more tracking CSI-RSs, and second information for setting up information regarding time-domain correlations. In some examples, this may be done as described in relation to Figure 1.

[0148] In 904b, the gNB may receive a CSI report containing information about time-domain correlations. The first parameter, trs-Info, may be included in the first information. The second parameter may indicate one of the following: a periodic CSI report, a semi-persistent CSI report, or a non-periodic CSI report. Information about time-domain correlations may be measured by one or more tracking CSI-RSs. A CSI report containing information about time-domain correlations may be received based on the second parameter. In some examples, this may be done as described in relation to Figure 1.

[0149] Figure 10 shows various components that may be used in UE1002. UE1002, as described in relation to Figure 10, may be implemented in accordance with UE102, as described in relation to Figure 1. UE1002 includes a processor 1003 that controls the operation of UE1002. The processor 1003 may also be called a central processing unit (CPU). Memory 1005, which may include read-only memory (ROM), random access memory (RAM), a combination of the two, or any type of device capable of storing information, provides instructions 1007a and data 1009a to the processor 1003. A portion of memory 1005 may also include non-volatile random access memory (NVRAM). Further instructions 1007b and data 1009b may also exist within the processor 1003. Instruction 1007b and / or data 1009b loaded into processor 1003 may include instruction 1007a and / or data 1009b from memory 1005 loaded for execution or processing by processor 1003. Instruction 1007b may be executed by processor 1003 to perform one or more of the methods described above.

[0150] UE1002 may also include a housing that accommodates one or more transmitters 1058 and one or more receivers 1020 to enable the transmission and reception of data. The transmitters 1058 and receivers 1020 may be combined within one or more transceivers 1018. One or more antennas 1022a to n are mounted on the housing and electrically coupled to the transceivers 1018.

[0151] The various components of UE1002 are integrated by a bus system 1011, which may include a data bus, a power bus, a control signal bus, and a status signal bus. However, for clarity, in Figure 10, the various buses are shown as the bus system 1011. UE1002 may also include a digital signal processor (DSP) 1013 for use in processing signals. UE1002 may also include a communication interface 1015 that provides user access to the functions of UE1002. The UE1002 shown in Figure 10 is a functional block diagram, not a list of specific components.

[0152] Figure 11 shows various components that may be used in the gNB1160. The gNB1160 described in relation to Figure 11 may be implemented in accordance with the gNB160 described in relation to Figure 1. The gNB1160 includes a processor 1103 that controls the operation of the gNB1160. The processor 1103 may also be called a central processing unit (CPU). Memory 1105, which may include read-only memory (ROM), random access memory (RAM), a combination of the two, or any type of device capable of storing information, provides the processor 1103 with instructions 1107a and data 1109b. A portion of memory 1105 may also include non-volatile random access memory (NVRAM). Further instructions 1107b and data 1109b may also exist within the processor 1103. Instruction 1107b and / or data 1109b loaded into processor 1103 may include instruction 1107a and / or data 1109b from memory 1105 loaded for execution or processing by processor 1103. Instruction 1107b may be executed by processor 1103 to perform one or more of the methods described above.

[0153] The gNB1160 may also include a housing that houses one or more transmitters 1117 and one or more receivers 1178 to enable the transmission and reception of data. The transmitters 1117 and receivers 1178 may be combined within one or more transceivers 1176. One or more antennas 1180a to n are mounted on the housing and electrically coupled to the transceivers 1176.

[0154] The various components of the gNB1160 are integrated by a bus system 1111, which may include a power bus, control signal bus, and status signal bus in addition to the data bus. However, for clarity, in Figure 11, the various buses are shown as the bus system 1111. The gNB1160 may also include a digital signal processor (DSP) 1113 for use in processing signals. The gNB1160 may also include a communication interface 1115 that provides user access to the functions of the gNB1160. The gNB1160 shown in Figure 11 is a functional block diagram, not a list of specific components.

[0155] Figure 12 is a block diagram showing one implementation of UE1202 in which one or more of the systems and / or methods described herein may be implemented. UE1202 includes a transmitting means 1258, a receiving means 1220, and a control means 1224. The transmitting means 1258, the receiving means 1220, and the control means 1224 may be configured to perform one or more of the functions described above in relation to Figure 1. Figure 10 above shows an example of the structure of the specific device of Figure 12. Various other structures may also be implemented to realize one or more of the functions of Figure 1. For example, the DSP may be implemented by software.

[0156] Figure 13 is a block diagram showing one implementation of gNB1360 in which one or more of the systems and / or methods described herein may be implemented. gNB1360 includes a transmitting means 1317, a receiving means 1378, and a control means 1382. The transmitting means 1317, the receiving means 1378, and the control means 1382 may be configured to perform one or more of the functions described above in relation to Figure 1. Figure 11 above shows an example of the structure of the specific device of Figure 13. Various other structures may also be implemented to realize one or more of the functions of Figure 1. For example, the DSP may be implemented by software.

[0157] Figure 14 is a block diagram showing one implementation configuration of gNB1460. gNB1460 may be an example of gNB160, which was described in relation to Figure 1. gNB1460 may include a higher-layer processor 1423, a DL transmitter 1425, an UL receiver 1433, and one or more antennas 1431. The DL transmitter 1425 may include a PDCCH transmitter 1427 and a PDSCH transmitter 1429. The UL receiver 1433 may include a PUCCH receiver 1435 and a PUSCH receiver 1437.

[0158] The upper-layer processor 1423 manages the behavior of the physical layer (behavior of the DL transmitter and UL receiver) and can provide upper-layer parameters to the physical layer. The upper-layer processor 1423 can obtain transport blocks from the physical layer. The upper-layer processor 1423 can send and / or retrieve upper-layer messages such as RRC messages and MAC messages to the upper layer of the UE. The upper-layer processor 1423 can provide PDSCH transmitter transport blocks and provide PDCCH transmitter transmission parameters associated with the transport blocks.

[0159] The DL transmitter 1425 can multiplex downlink physical channels and downlink physical signals (including reserved signals) and transmit them via the transmitting antenna 1431. The UL receiver 1433 can receive the multiplexed uplink physical channels and uplink physical signals via the receiving antenna 1431 and demultiplex them. The PUCCH receiver 1435 can provide the UCI to the upper layer processor 1423. The PUSCH receiver 1437 can provide the received transport block to the upper layer processor 1423.

[0160] Figure 15 is a block diagram showing one implementation configuration of UE1502. UE1502 may be an example of UE102 as described in relation to Figure 1. UE1502 may include a higher-layer processor 1523, a UL transmitter 1551, a DL receiver 1543, and one or more antennas 1531. The UL transmitter 1551 may include a PUCCH transmitter 1553 and a PUSCH transmitter 1555. The DL receiver 1543 may include a PDCCH receiver 1545 and a PDSCH receiver 1547.

[0161] The upper-layer processor 1523 manages the behavior of the physical layer (behavior of the UL transmitter and DL receiver) and can provide upper-layer parameters to the physical layer. The upper-layer processor 1523 can obtain transport blocks from the physical layer. The upper-layer processor 1523 can send and / or retrieve upper-layer messages such as RRC messages and MAC messages to the upper layer of the UE. The upper-layer processor 1523 can provide transport blocks to the PUSCH transmitter and provide UCI to the PUCCH transmitter 1553.

[0162] The DL receiver 1543 can receive the multiplexed downlink physical channels and downlink physical signals via the receiving antenna 1531 and demultiplex them. The PDCCH receiver 1545 can provide the DCI to the upper layer processor 1523. The PDSCH receiver 1547 can provide the received transport block to the upper layer processor 1523.

[0163] The term “computer-readable medium” refers to any available medium that can be accessed by a computer or processor. As used herein, the term “computer-readable medium” can mean a non-temporary, tangible medium that is readable by a computer and / or processor. By example, but not limited to, computer-readable medium or processor-readable medium may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, magnetic disk storage devices or other magnetic storage devices, or any other medium that can be used to hold or store desired program code in the form of instructions or data structures and is accessible by a computer or processor. As used herein, disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray® disc, where disk typically reproduces data magnetically and disc uses a laser to reproduce data optically.

[0164] It should be noted that one or more of the methods described herein can be implemented in hardware form and / or can be carried out using hardware. For example, one or more of the methods described herein can be implemented and / or carried out using a chipset, application-specific integrated circuit (ASIC), large-scale integrated circuit (LSI), or integrated circuit, etc.

[0165] Each of the methods disclosed herein includes one or more steps or actions to achieve the described method. The steps and / or actions of a method may be interchanged with one another and / or incorporated into a single step without departing from the claims. In other words, the order and / or use of any particular steps and / or actions may be changed without departing from the claims, unless a particular order of steps or actions is required for the proper operation of the described method.

[0166] It should be understood that the claims are not limited to the exact configurations and components exemplified above. Various modifications, changes, and variations may be made to the arrangement, operation, and details of the systems, methods, and apparatus described herein without departing from the claims.

[0167] The programs that operate on the gNB160 or UE102 using the system and method described above are programs that control the CPU and other components (programs that operate the computer) to realize their functions according to the system and method described. The information handled by these devices is temporarily stored in RAM during processing. Subsequently, the information is stored in various ROMs or HDDs, and is read, modified, or written by the CPU as needed. Possible recording media for storing programs include, for example, semiconductors (e.g., ROM, non-volatile memory cards, etc.), optical storage media (e.g., DVD, MO, MD, CD, BD, etc.), magnetic storage media (e.g., magnetic tape, flexible disk, etc.), and similar media. Furthermore, in some cases, the functions of the system and method described are realized by executing the loaded program, and furthermore, the functions of the system and method described are realized in conjunction with the operating system or other application programs based on instructions from the program.

[0168] Furthermore, if the program is available on the market, it is possible to distribute the program stored on a portable recording medium, or to transmit the program to a server computer connected via a network such as the Internet. In this case, the storage device within the server computer is also included. Moreover, some or all of the gNB160 and UE102 according to the system and method described above can be realized as a general-purpose integrated circuit (LSI). Each functional block of the gNB160 and UE102 may be individually incorporated into a chip, or some or all of the functional blocks may be integrated into a chip. Furthermore, the technology of the integrated circuit is not limited to LSIs; the integrated circuits of the functional blocks may be realized using dedicated circuits or general-purpose processors. Also, as semiconductor technology advances, if integrated circuit technology that replaces LSIs emerges, it is possible to use integrated circuits that apply that technology.

[0169] Furthermore, the functional blocks and various features of the base station and terminal equipment used in each of the above-described implementations can generally be implemented or executed by electrical circuits which are integrated circuits or multiple integrated circuits. Circuits designed to perform the functions described herein may comprise a general-purpose processor, a digital signal processor (DSP), an application-specific or general-purpose application integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, discrete gates or transistor logic, or individual hardware components, or a combination thereof. The general-purpose processor may be a microprocessor, or the processor may be a conventional processor, controller, microcontroller, or state machine. The general-purpose processor or each circuit described above may consist of digital circuits or analog circuits. Furthermore, if advances in semiconductor technology lead to the emergence of integrated circuit technologies that replace current integrated circuits, integrated circuits using these technologies will also become available.

[0170] As used herein, the term "and / or" should be interpreted as meaning one or more items. For example, the phrase "A, B and / or C" should be interpreted as meaning A only, B only, C only, A and B (other than C), B and C (other than A), A and C (other than B), or all of A, B, and C. As used herein, the phrase "at least one of" should be interpreted as meaning one or more items. For example, the phrase "at least one of A, B, and C" or "at least one of A, B, or C" should be interpreted as meaning A only, B only, C only, A and B (other than C), B and C (other than A), A and C (other than B), or all of A, B, and C. As used herein, the phrase "one or more of" should be interpreted as meaning one or more items. For example, the phrases "one or more of A, B, and C" or "one or more of A, B, or C" should be interpreted as meaning A only, B only, C only, A and B (excluding C), B and C (excluding A), A and C (excluding B), or all of A, B, and C.

Claims

1. A receiver for receiving first information for configuring one or more Non-Zero Power Channel State Information (CSI)-Reference Signal (RS) resources and second information for configuring a CSI report; a measurement unit that measures information regarding time domain correlation based on the second information; a transmitter for transmitting a CSI report including information regarding the time domain correlation based on the second information; the second information is related to the first information; The first information includes a first parameter trs-Info, the first parameter trs-Info indicating one or more CSI-RS resources for time and frequency channel tracking; The second information includes a second parameter reportQuantity, and the second parameter reportQuantity is set to TDCI; The TDCI indicates information regarding time domain correlation. User equipment.

2. A transmitter for transmitting first information for configuring one or more Non-Zero Power Channel State Information (CSI)-Reference Signal (RS) resources and second information for configuring a CSI report; a receiving unit for receiving a CSI report including information regarding the time-domain correlation measured based on the second information; the second information is related to the first information; The first information includes a first parameter trs-Info, the first parameter trs-Info indicating one or more CSI-RS resources for time and frequency channel tracking; The second information includes a second parameter reportQuantity, and the second parameter reportQuantity is set to TDCI; The TDCI indicates information regarding time domain correlation. Base station.

3. receiving first information for configuring one or more Non-Zero Power Channel State Information (CSI)-Reference Signal (RS) resources and second information for configuring CSI reporting; determining information regarding time domain correlation based on the second information; and transmitting a CSI report including information regarding the time domain correlation; the second information is related to the first information; The first information includes a first parameter trs-Info, the first parameter trs-Info indicating one or more CSI-RS resources for time and frequency channel tracking; The second information includes a second parameter reportQuantity, and the second parameter reportQuantity is set to TDCI; The TDCI indicates information regarding time domain correlation. A method for communicating with user equipment.