Patent Description:
Wireless communication devices have become more powerful in order to meet consumer needs and to improve portability and convenience. Consumers have become dependent upon wireless communication devices and have come to expect reliable service, expanded areas of coverage and increased functionality. A wireless communication system may provide communication for a number of wireless communication devices, each of which may be serviced by a base station. A base station may be a device that communicates with wireless communication devices.

As wireless communication devices have advanced, improvements in communication capacity, speed, flexibility and/or efficiency have been sought. However, improving communication capacity, speed, flexibility and/or efficiency may present certain problems.

For example, wireless communication devices may communicate with one or more devices using a communication structure.

<CIT> discloses a method and apparatus for reporting a channel state of a user equipment in a wireless communication system. The method may comprise the steps of: receiving, from a base station, configuration information for measurement and reporting of a channel state, wherein the configuration information includes at least two from among a first value (L) indicating the number of beams to be reported via a precoding matrix indicator (PMI), a second value (PCSI-RS) indicating the number of ports of a channel state information reference signal (CSI-RS), and a third value (LCSI-RS) indicating the number of beam ports to be used from among the number of ports of the CSI-RS; receiving, from the base station, one or more CSI-RSs that are transmitted via one or more beamformed ports; generating the PMI, on the basis of the result of measuring the received CSI-RSs, and the configuration information; and reporting, to the base station, CSI including the PMI.

<CIT> relates to a method whereby user equipment (UE) transmits channel state information (CSI) in a wireless communication system and to a device therefor. A terminal receives configuration information for CSI reporting from a base station and receives a reference signal from the base station on the basis of the configuration information. The terminal may receive downlink control information (DCI) via a physical downlink control channel (PDCCH), calculate CSI about a particular channel on the basis of the configuration information and the DCI, and report same to the base station.

However, the communication structure used may only offer limited flexibility and/or efficiency. As illustrated by this discussion, systems and methods that improve communication flexibility and/or efficiency may be beneficial.

The problem is solved by the teachings of the independent claims. The invention is defined and limited by the appended claims.

The 3rd Generation Partnership Project, also referred to as "3GPP," is a collaboration agreement that aims to define globally applicable technical specifications and technical reports for third and fourth generation wireless communication systems. The 3GPP may define specifications for next generation mobile networks, systems and devices.

At least some aspects of the systems and methods disclosed herein may be described in relation to the 3GPP LTE, LTE-Advanced (LTE-A), LTE-Advanced Pro and other standards (e.g., 3GPP Releases <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM> and/or <NUM>). However, the scope of the present disclosure should not be limited in this regard. At least some aspects of the systems and methods disclosed herein may be utilized in other types of wireless communication systems.

A wireless communication device may be an electronic device used to communicate voice and/or data to a base station, which in turn may communicate with a network of devices (e.g., public switched telephone network (PSTN), the Internet, etc.). In describing systems and methods herein, a wireless communication device may alternatively be referred to as a mobile station, a UE, an access terminal, a subscriber station, a mobile terminal, a remote station, a user terminal, a terminal, a subscriber unit, a mobile device, etc. Examples of wireless communication devices include cellular phones, smart phones, personal digital assistants (PDAs), laptop computers, netbooks, e-readers, wireless modems, etc. In 3GPP specifications, a wireless communication device is typically referred to as a UE. However, as the scope of the present disclosure should not be limited to the 3GPP standards, the terms "UE" and "wireless communication device" may be used interchangeably herein to mean the more general term "wireless communication device. " A UE may also be more generally referred to as a terminal device.

In 3GPP specifications, a base station is typically referred to as a Node B, an evolved Node B (eNB), a home enhanced or evolved Node B (HeNB), a g Node B (gNB) or some other similar terminology. As the scope of the disclosure should not be limited to 3GPP standards, the terms "base station," "Node B," "eNB," "gNB" and "HeNB" may be used interchangeably herein to mean the more general term "base station. " Furthermore, the term "base station" may be used to denote an access point. An access point may be an electronic device that provides access to a network (e.g., Local Area Network (LAN), the Internet, etc.) for wireless communication devices. The term "communication device" may be used to denote both a wireless communication device and/or a base station. A gNB may also be more generally referred to as a base station device.

It should be noted that as used herein, a "cell" may be any communication channel that is specified by standardization or regulatory bodies to be used for International Mobile Telecommunications-Advanced (IMT-Advanced) or IMT-<NUM>, and all of it or a subset of it may be adopted by 3GPP as licensed bands or unlicensed bands (e.g., frequency bands) to be used for communication between an eNB or gNB and a UE. It should also be noted that in E-UTRA and E-UTRAN overall description, as used herein, a "cell" may be defined as "combination of downlink and optionally uplink resources. " The linking between the carrier frequency of the downlink resources and the carrier frequency of the uplink resources may be indicated in the system information transmitted on the downlink resources.

The 5th generation communication systems, dubbed NR (New Radio technologies) by 3GPP, envision the use of time/frequency/space resources to allow for services, such as eMBB (enhanced Mobile Broad-Band) transmission, URLLC (Ultra Reliable and Low Latency Communication) transmission, and mMTC (massive Machine Type Communication) transmission. And, in NR, transmissions for different services may be specified (e.g., configured) for one or more bandwidth parts (BWPs) in a serving cell and/or for one or more serving cells. A user equipment (UE) may receive a downlink signal(s) and/or transmit an uplink signal(s) in the BWP(s) of one or more serving cells.

In order for the services to use the time, frequency, and/or spatial resources efficiently, it would be useful to be able to efficiently control downlink and/or uplink transmissions. Therefore, a procedure for efficient control of downlink and/or uplink transmissions should be designed. Accordingly, a detailed design of a procedure for downlink and/or uplink transmissions may be beneficial.

In some examples, UCI for URLLC may have higher reliability and lower latency than eMBB. Some examples of the techniques described herein may achieve the lower latency in mini-slot repetition by using an earliest DMRS satisfying timing equal to or greater than the indicated timing in repeated PUSCH.

Various examples of the systems and methods disclosed herein are now described with reference to the Figures, where like reference numbers may indicate functionally similar elements. The systems and methods as generally described and illustrated in the Figures herein could be arranged and designed in a wide variety of different implementations. Thus, the following more detailed description of several implementations, as represented in the Figures, is not intended to limit scope, as claimed, but is merely representative of the systems and methods.

<FIG> is a block diagram illustrating one implementation of one or more gNBs <NUM> and one or more UEs <NUM> in which systems and methods for signaling may be implemented. The one or more UEs <NUM> communicate with one or more gNBs <NUM> using one or more physical antennas 122a-n. For example, a UE <NUM> transmits electromagnetic signals to the gNB <NUM> and receives electromagnetic signals from the gNB <NUM> using the one or more physical antennas 122a-n. The gNB <NUM> communicates with the UE <NUM> using one or more physical antennas 180a-n. In some implementations, the term "base station," "eNB," and/or "gNB" may refer to and/or may be replaced by the term "Transmission Reception Point (TRP). " For example, the gNB <NUM> described in connection with <FIG> may be a TRP in some implementations.

The UE <NUM> and the gNB <NUM> may use one or more channels and/or one or more signals <NUM>, <NUM> to communicate with each other. For example, the UE <NUM> may transmit information or data to the gNB <NUM> using one or more uplink channels <NUM>. Examples of uplink channels <NUM> include a physical shared channel (e.g., PUSCH (physical uplink shared channel)) and/or a physical control channel (e.g., PUCCH (physical uplink control channel)), etc. The one or more gNBs <NUM> may also transmit information or data to the one or more UEs <NUM> using one or more downlink channels <NUM>, for instance. Examples of downlink channels <NUM> include a physical shared channel (e.g., PDSCH (physical downlink shared channel) and/or a physical control channel (PDCCH (physical downlink control channel)), etc. Other kinds of channels and/or signals may be used.

Each of the one or more UEs <NUM> may include one or more transceivers <NUM>, one or more demodulators <NUM>, one or more decoders <NUM>, one or more encoders <NUM>, one or more modulators <NUM>, a data buffer <NUM> and a UE operations module <NUM>. For example, one or more reception and/or transmission paths may be implemented in the UE <NUM>. For convenience, only a single transceiver <NUM>, decoder <NUM>, demodulator <NUM>, encoder <NUM> and modulator <NUM> are illustrated in the UE <NUM>, though multiple parallel elements (e.g., transceivers <NUM>, decoders <NUM>, demodulators <NUM>, encoders <NUM> and modulators <NUM>) may be implemented.

The transceiver <NUM> may include one or more receivers <NUM> and one or more transmitters <NUM>. The one or more receivers <NUM> may receive signals from the gNB <NUM> using one or more antennas 122a-n. For example, the receiver <NUM> may receive and downconvert signals to produce one or more received signals <NUM>. The one or more received signals <NUM> may be provided to a demodulator <NUM>. The one or more transmitters <NUM> may transmit signals to the gNB <NUM> using one or more physical antennas 122a-n. For example, the one or more transmitters <NUM> may upconvert and transmit one or more modulated signals <NUM>.

The demodulator <NUM> may demodulate the one or more received signals <NUM> to produce one or more demodulated signals <NUM>. The one or more demodulated signals <NUM> may be provided to the decoder <NUM>. The UE <NUM> may use the decoder <NUM> to decode signals. The decoder <NUM> may produce decoded signals <NUM>, which may include a UE-decoded signal <NUM> (also referred to as a first UE-decoded signal <NUM>). For example, the first UE-decoded signal <NUM> may comprise received payload data, which may be stored in a data buffer <NUM>. Another signal included in the decoded signals <NUM> (also referred to as a second UE-decoded signal <NUM>) may comprise overhead data and/or control data. For example, the second UE-decoded signal <NUM> may provide data that may be used by the UE operations module <NUM> to perform one or more operations.

In general, the UE operations module <NUM> may enable the UE <NUM> to communicate with the one or more gNBs <NUM>. The UE operations module <NUM> may include one or more of a UE scheduling module <NUM>.

The UE scheduling module <NUM> may perform (e.g., schedule) downlink reception(s) and uplink transmission(s). The downlink reception(s) include reception of data, reception of downlink control information, and/or reception of downlink reference signals. Also, the uplink transmissions include transmission of data, transmission of uplink control information, and/or transmission of uplink reference signals.

Also, in a carrier aggregation (CA), the gNB <NUM> and the UE <NUM> may communicate with each other using one or more serving cells. Here the one or more serving cells may include one primary cell and one or more secondary cells. For example, the gNB <NUM> may transmit, by using the RRC message, information used for configuring one or more secondary cells to form together with the primary cell a set of serving cells. Namely, the set of serving cells may include one primary cell and one or more secondary cells. Here, the primary cell may be always activated. Also, the gNB <NUM> may activate one or more secondary cell within the configured secondary cells. Here, in the downlink, a carrier corresponding to the primary cell may be the downlink primary component carrier (i.e., the DL PCC), and a carrier corresponding to a secondary cell may be the downlink secondary component carrier (i.e., the DL SCC). Also, in the uplink, a carrier corresponding to the primary cell may be the uplink primary component carrier (i.e., the UL PCC), and a carrier corresponding to the secondary cell may be the uplink secondary component carrier (i.e., the UL SCC).

In a radio communication system, physical channels (uplink physical channels and/or downlink physical channels) may be defined. The physical channels (uplink physical channels and/or downlink physical channels) may be used for transmitting information that is delivered from a higher layer.

In some examples, in uplink, a Physical Random Access Channel (PRACH) may be defined. In some approaches, the PRACH (e.g., the random access procedure) may be used for an initial access connection establishment procedure, a handover procedure, a connection re-establishment, a timing adjustment (e.g., a synchronization for an uplink transmission, for UL synchronization) and/or for requesting an uplink shared channel (UL-SCH) resource (e.g., the uplink physical shared channel (PSCH) (e.g., PUSCH) resource).

In some examples, a physical uplink control channel (PUCCH) may be defined. The PUCCH may be used for transmitting uplink control information (UCI). The UCI may include hybrid automatic repeat request-acknowledgement (HARQ-ACK), channel state information (CSI) and/or a scheduling request (SR). The HARQ-ACK is used for indicating a positive acknowledgement (ACK) or a negative acknowledgment (NACK) for downlink data (e.g., Transport block(s), Medium Access Control Protocol Data Unit (MAC PDU) and/or Downlink Shared Channel (DL-SCH)). The CSI is used for indicating state of downlink channel (e.g., a downlink signal(s)). Also, the SR is used for requesting resources of uplink data (e.g., Transport block(s), MAC PDU and/or Uplink Shared Channel (UL-SCH)).

Here, the DL-SCH and/or the UL-SCH may be a transport channel that is used in the MAC layer. Also, a transport block(s) (TB(s)) and/or a MAC PDU may be defined as a unit(s) of the transport channel used in the MAC layer. The transport block may be defined as a unit of data delivered from the MAC layer to the physical layer. The MAC layer may deliver the transport block to the physical layer (e.g., the MAC layer delivers the data as the transport block to the physical layer). In the physical layer, the transport block may be mapped to one or more codewords.

In downlink, a physical downlink control channel (PDCCH) may be defined. The PDCCH may be used for transmitting downlink control information (DCI). Here, more than one DCI formats may be defined for DCI transmission on the PDCCH. Namely, fields may be defined in the DCI format(s), and the fields are mapped to the information bits (e.g., DCI bits).

Additionally or alternatively, a physical downlink shared channel (PDSCH) and a physical uplink shared channel (PUSCH) may be defined. For example, in a case that the PDSCH (e.g., the PDSCH resource) is scheduled by using the DCI format(s) for the downlink, the UE <NUM> may receive the downlink data, on the scheduled PDSCH (e.g., the PDSCH resource). Additionally or alternatively, in a case that the PUSCH (e.g., the PUSCH resource) is scheduled by using the DCI format(s) for the uplink, the UE <NUM> transmits the uplink data, on the scheduled PUSCH (e.g., the PUSCH resource). For example, the PDSCH may be used to transmit the downlink data (e.g., DL-SCH(s), a downlink transport block(s)). Additionally or alternatively, the PUSCH may be used to transmit the uplink data (e.g., UL-SCH(s), an uplink transport block(s)).

Furthermore, the PDSCH and/or the PUSCH may be used to transmit information of a higher layer (e.g., a radio resource control (RRC)) layer, and/or a MAC layer). For example, the PDSCH (e.g., from the gNB <NUM> to the UE <NUM>) and/or the PUSCH (e.g., from the UE <NUM> to the gNB <NUM>) may be used to transmit a RRC message (a RRC signal). Additionally or alternatively, the PDSCH (e.g., from the gNB <NUM> to the UE <NUM>) and/or the PUSCH (e.g., from the UE <NUM> to the gNB <NUM>) may be used to transmit a MAC control element (a MAC CE). Here, the RRC message and/or the MAC CE are also referred to as a higher layer signal.

In some approaches, a physical broadcast channel (PBCH) may be defined. For example, the PBCH may be used for broadcasting the MIB (master information block). Here, system information may be divided into the MIB and a number of SIB(s) (system information block(s)). For example, the MIB may be used for carrying include minimum system information. Additionally or alternatively, the SIB(s) may be used for carrying system information messages.

In some approaches, in downlink, synchronization signals (SSs) may be defined. The SS may be used for acquiring time and/or frequency synchronization with a cell. Additionally or alternatively, the SS may be used for detecting a physical layer cell ID of the cell. SSs may include a primary SS and a secondary SS.

An SS/PBCH block may be defined as a set of a primary SS, a secondary SS and a PBCH. Tin the time domain, the SS/PBCH block may include <NUM> OFDM symbols, numbered in increasing order from <NUM> to <NUM> within the SS/PBCH block, where PSS, SSS, and PBCH with associated demodulation reference signal (DMRS) are mapped to symbols. One or more SS/PBCH block may be mapped within a certain time duration (e.g., <NUM> msec).

Additionally, the SS/PBCH block can be used for beam measurement, radio resource management (RRM) measurement and radio link control (RLM) measurement. Specifically, the secondary synchronization signal (SSS) can be used for the measurement.

In the radio communication for uplink, UL RS(s) may be used as uplink physical signal(s). Additionally or alternatively, in the radio communication for downlink, DL RS(s) may be used as downlink physical signal(s). The uplink physical signal(s) and/or the downlink physical signal(s) may not be used to transmit information that is provided from the higher layer, but may be used by a physical layer.

Here, the downlink physical channel(s) and/or the downlink physical signal(s) described herein may be assumed to be included in a downlink signal (e.g., a DL signal(s)) in some implementations for the sake of simple descriptions. Additionally or alternatively, the uplink physical channel(s) and/or the uplink physical signal(s) described herein may be assumed to be included in an uplink signal (i.e. an UL signal(s)) in some implementations for the sake of simple descriptions.

Some techniques for CSI-RS for tracking and time domain correlation and/or Doppler information reporting are described as follows. A UE <NUM> may be configured with NZP CSI-RS for tracking. The UE <NUM> may receive information of one or more NZP CSI-RS resource sets (NZP-CSI-RS-ResourceSet) in a RRC message. Each NZP CSI-RS resource set may include information to configure one or more NZP CSI-RS resources (NZP-CSI-RS-Resource).

A UE <NUM> may be configured with one or more CSI reporting configuration(s). For this purpose, the UE <NUM> may receive information including one or more CSI report configuration(s) in a RRC message. Each CSI report configuration (CSI-ReportConfig) may include information on CSI-RS resources to perform channel measurement, information on CSI-RS resources for interference measurement, a parameter ReportQuantity, which kind of CSI (e.g., L1-RSRP (Layer-<NUM> 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)) is reported by the corresponding CSI report configuration, and a parameter reportConfigType which indicates one of aperiodic CSI reporting, semi-persistent CSI reporting, and/or periodic CSI reporting.

A UE <NUM> in RRC connected mode may be expected to receive the higher layer UE specific configuration of a NZP-CSI-RS-ResourceSet configured with higher layer parameter trs-Info. For a NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info, the UE <NUM> may assume the antenna port with the same port index of the configured NZP CSI-RS resources in the NZP-CSI-RS-ResourceSet is the same.

For frequency range <NUM> (e.g., sub-<NUM>), the UE <NUM> may be configured with one or more NZP-CSI-RS resource set(s), where a parameter NZP-CSI-RS-ResourceSet may include four periodic NZP CSI-RS resources in two consecutive slots with two periodic NZP CSI-RS resources in each slot. If no two consecutive slots are indicated as downlink slots, by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigDedicated, then the UE <NUM> may be configured with one or more NZP CSI-RS set(s), where a NZP-CSI-RS-ResourceSet may include two periodic NZP CSI-RS resources in one slot.

For frequency range <NUM>, the UE <NUM> may be configured with one or more NZP CSI-RS set(s), where a NZP-CSI-RS-ResourceSet may include two periodic CSI-RS resources in one slot or with a NZP-CSI-RS-ResourceSet of four periodic NZP CSI-RS resources in two consecutive slots with two periodic NZP CSI-RS resources in each slot.

A UE <NUM> configured with NZP-CSI-RS-ResourceSet(s) configured with higher layer parameter trs-Info may have the NZP CSI-RS resources configured as periodic, with the CSI-RS resources in the parameter NZP-CSI-RS-ResourceSet configured with same periodicity, bandwidth, and subcarrier location.

A UE <NUM> configured with NZP-CSI-RS-ResourceSet(s) configured with higher layer parameter trs-Info may have the NZP CSI-RS resources configured as periodic CSI-RS resource in one set and aperiodic CSI-RS resources in a second set, with the aperiodic CSI-RS and periodic CSI-RS resource having the same bandwidth (with same RB location) and the aperiodic CSI-RS being configured with qcl-Type set to 'typeA' and 'typeD', where applicable, with the periodic CSI-RS resources. For frequency range <NUM>, the UE does not expect that the scheduling offset between the last symbol of the PDCCH carrying the triggering DCI and the first symbol of the aperiodic CSI-RS resources is smaller than beamSwitchTiming + d · <NUM>µCSIRS/<NUM>µPDCCH in CSI-RS symbols, where the higher layer parameter beamSwitchTiming is a UE reported value, the reported value may be one of the values of {<NUM>, <NUM>, <NUM>}, and the beam switching timing delay may be d if µPDCCH < µCSIRS, else d may be zero. The UE <NUM> may expect that the periodic CSI-RS resource set and aperiodic CSI-RS resource set are configured with the same number of CSI-RS resources and with the same number of CSI-RS resources in a slot. For the aperiodic CSI-RS resource set if triggered, and if the associated periodic CSI-RS resource set is configured with four periodic CSI-RS resources with two consecutive slots with two periodic CSI-RS resources in each slot, the higher layer parameter aperiodicTriggeringOffset may indicate the triggering offset for the first slot for the first two CSI-RS resources in the set.

A UE <NUM> may not expect to be configured with a CSI-ReportConfig that is linked to a CSI-ResourceConfig containing an NZP-CSI-RS-ResourceSet configured with trs-Info and with the CSI-ReportConfig configured with the higher layer parameter timeRestrictionForChannelMeasurements set to 'configured'.

A UE <NUM> may not expect to be configured with a NZP-CSI-RS-ResourceSet configured both with trs-Info and repetition.

If a UE <NUM> is configured with a CSI-ReportConfig with the higher layer parameter reportQuantity set to 'none' for aperiodic NZP CSI-RS resource set configured with trs-Info, the UE <NUM> may receive the NZP CSI-RS for tracking and perform time and frequency channel tracking.

Some examples of techniques for CSI-RS for tracking and time domain correlation and/or Doppler information reporting are provided as follows. A UE <NUM> may be configured with aperiodic CSI-RS for tracking in a NZP-CSI-RS resource set configured with trs-Info. A UE <NUM> may be configured with semi-static CSI-RS for tracking in a NZP-CSI-RS resource set configured with trs-Info. A UE <NUM> may be configured with periodic CSI-RS for tracking in a NZP-CSI-RS resource set configured with trs-Info.

A UE <NUM> may be configured with a CSI-ReportConfig for periodic NZP CSI-RS resource set configured with trs-Info.

If a UE <NUM> is not configured with a CSI-ReportConfig for periodic NZP CSI-RS resource set configured with trs-Info, the UE <NUM> may receive the NZP CSI-RS for tracking and perform time and frequency channel tracking.

A UE <NUM> may be configured with a CSI-ReportConfig for semi-persistent NZP CSI-RS resource set configured with trs-Info. If a semi-persistent NZP CSI-RS resource set configured with trs-Info is configured, the UE <NUM> may be configured with a CSI-ReportConfig and a parameter reportQuantity in the CSI-ReportConfig is set to 'TDCI'.

If a UE <NUM> is configured with a CSI-ReportConfig with the higher layer parameter reportQuantity set to a parameter other than 'none' (e.g., TDCI: Time domain correlation related information), the UE <NUM> may receive CSI-RS for tracking, perform time and frequency channel tracking, and measure the time domain correlation related information. The UE <NUM> may transmit time domain correlation information based on the measurement of CSI-RS for tracking. One or more of the following information as TDCI may be defined:.

In some examples, each CSI-RS resource may be configured by the higher layer parameter NZP-CSI-RS-Resource with one or more of the following restrictions:.

Additionally or alternatively, a UE <NUM> may measure time domain correlation by using CSI-RS for tracking associated with the parameter NZP-CSI-RS-ResourceSet(s) configured with a parameter trs-Info and associated with the parameter CSI-Report-Config(s) configured with reportQuantity as TDCI.

Additionally or alternatively, a UE <NUM> may measure time domain correlation by using CSI-RS for tracking associated with the parameter NZP-CSI-RS-ResourceSet(s) configured with a parameter trs-Info and associated with the parameter CSI-Report-Config(s) configured with reportQuantity as 'none' and TDCI.

Additionally or alternatively, the parameter reportQuantity set to 'TDCI' may be configured separately from other CSI components (e.g., PMI, CQI, RI, LI, and/or CRI). The parameter reportQuantity set to 'TDCI' may be configured with other CSI components (e.g., PMI, CQI, RI, LI, and/or CRI). In this case, the reportQuantity may be set to another parameter name (e.g., 'TDCI-PMI-CQI-RI' in case that CQI, PMI, RI, and TDCI are reported.

Additionally or alternatively, a UE <NUM> may be configured with time domain prediction from CSI-RSs for tracking by information provided by a RRC message and reflect the time domain correlation to the reported CSI such as CQI, PMI, RI, LI, and/or CRI. In this case, the parameter reportQuantity in the parameter CSI-ReportConfig associated with CSI-RS for tracking configured by the parameter NZP-CSI-RS-ResourceSet(s) configured with a parameter trs-Info may be set 'none'. Additionally or alternatively, the parameter reportQuantity in the parameter CSI-ReportConfig associated with CSI-RS for tracking configured by the parameter NZP-CSI-RS-ResourceSet(s) configured with a parameter trs-Info may be set TDCI.

Additionally or alternatively, a UE <NUM> may transmit UE capability information to support a time domain correlation related information measurement. The UE capability may include the maximum number of simultaneous calculation(s) with other CSI components (e.g., L1-RSRP, PMI, CQI, RI, LI, and/or CRI). The UE capability may be defined per each component carrier, each cell, and/or each band.

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

Additionally or alternatively, DCI on a PDCCH may indicate the report of TDCI to a UE <NUM>. A MAC CE may activate the report of TDCI. Additionally or alternatively, the TDCI may be transmitted on a PUSCH and/or PUCCH.

If periodic CSI reporting including TDCI report is configured, a PUCCH or a PUSCH may be used. If semi-persistent CSI reporting including TDCI report is configured, a PUCCH or a PUSCH may be used. If aperiodic CSI reporting including TDCI report is configured, a PUSCH or a PUCCH may be used. Periodic, semi-persistent, and/or aperiodic CSI reporting may be configured by a parameter in a CSI-ReportConfig.

The UE operations module <NUM> may provide information <NUM> to the one or more receivers <NUM>. For example, the UE operations module <NUM> may inform the receiver(s) <NUM> when to receive retransmissions.

The UE operations module <NUM> may provide information <NUM> to the demodulator <NUM>. For example, the UE operations module <NUM> may inform the demodulator <NUM> of a modulation pattern anticipated for transmissions from the gNB <NUM>.

The UE operations module <NUM> may provide information <NUM> to the decoder <NUM>. For example, the UE operations module <NUM> may inform the decoder <NUM> of an anticipated encoding for transmissions from the gNB <NUM>.

The UE operations module <NUM> may provide information <NUM> to the encoder <NUM>. The information <NUM> may include data to be encoded and/or instructions for encoding. For example, the UE operations module <NUM> may instruct the encoder <NUM> to encode transmission data <NUM> and/or other information <NUM>. The other information <NUM> may include PDSCH HARQ-ACK information.

The UE operations module <NUM> may provide information <NUM> to the modulator <NUM>. For example, the UE operations module <NUM> may inform the modulator <NUM> of a modulation type (e.g., constellation mapping) to be used for transmissions to the gNB <NUM>. The modulator <NUM> may modulate the encoded data <NUM> to provide one or more modulated signals <NUM> to the one or more transmitters <NUM>.

The UE operations module <NUM> may provide information <NUM> to the one or more transmitters <NUM>. This information <NUM> may include instructions for the one or more transmitters <NUM>. For example, the UE operations module <NUM> may instruct the one or more transmitters <NUM> when to transmit a signal to the gNB <NUM>. For instance, the one or more transmitters <NUM> may transmit during a UL subframe. The one or more transmitters <NUM> may upconvert and transmit the modulated signal(s) <NUM> to one or more gNBs <NUM>.

Each of the one or more gNBs <NUM> may include one or more transceivers <NUM>, one or more demodulators <NUM>, one or more decoders <NUM>, one or more encoders <NUM>, one or more modulators <NUM>, a data buffer <NUM> and a gNB operations module <NUM>. For example, one or more reception and/or transmission paths may be implemented in a gNB <NUM>. For convenience, only a single transceiver <NUM>, decoder <NUM>, demodulator <NUM>, encoder <NUM> and modulator <NUM> are illustrated in the gNB <NUM>, though multiple parallel elements (e.g., transceivers <NUM>, decoders <NUM>, demodulators <NUM>, encoders <NUM> and modulators <NUM>) may be implemented.

The transceiver <NUM> may include one or more receivers <NUM> and one or more transmitters <NUM>. The one or more receivers <NUM> may receive signals from the UE <NUM> using one or more physical antennas 180a-n. For example, the receiver <NUM> may receive and downconvert signals to produce one or more received signals <NUM>. The one or more received signals <NUM> may be provided to a demodulator <NUM>. The one or more transmitters <NUM> may transmit signals to the UE <NUM> using one or more physical antennas 180a-n. For example, the one or more transmitters <NUM> may upconvert and transmit one or more modulated signals <NUM>.

The demodulator <NUM> may demodulate the one or more received signals <NUM> to produce one or more demodulated signals <NUM>. The one or more demodulated signals <NUM> may be provided to the decoder <NUM>. The gNB <NUM> may use the decoder <NUM> to decode signals. The decoder <NUM> may produce one or more decoded signals <NUM>, <NUM>. For example, a first eNB-decoded signal <NUM> may comprise received payload data, which may be stored in a data buffer <NUM>. A second eNB-decoded signal <NUM> may comprise overhead data and/or control data. For example, the second eNB-decoded signal <NUM> may provide data (e.g., PDSCH HARQ-ACK information) that may be used by the gNB operations module <NUM> to perform one or more operations.

In general, the gNB operations module <NUM> may enable the gNB <NUM> to communicate with the one or more UEs <NUM>. The gNB operations module <NUM> may include one or more of a gNB scheduling module <NUM>. The gNB scheduling module <NUM> may perform scheduling of downlink and/or uplink transmissions as described herein.

The gNB operations module <NUM> may provide information <NUM> to the demodulator <NUM>. For example, the gNB operations module <NUM> may inform the demodulator <NUM> of a modulation pattern anticipated for transmissions from the UE(s) <NUM>.

The gNB operations module <NUM> may provide information <NUM> to the decoder <NUM>. For example, the gNB operations module <NUM> may inform the decoder <NUM> of an anticipated encoding for transmissions from the UE(s) <NUM>.

The gNB operations module <NUM> may provide information <NUM> to the encoder <NUM>. The information <NUM> may include data to be encoded and/or instructions for encoding. For example, the gNB operations module <NUM> may instruct the encoder <NUM> to encode information <NUM>, including transmission data <NUM>.

The encoder <NUM> may encode transmission data <NUM> and/or other information included in the information <NUM> provided by the gNB operations module <NUM>. For example, encoding the data <NUM> and/or other information included in the information <NUM> may involve error detection and/or correction coding, mapping data to space, time and/or frequency resources for transmission, multiplexing, etc. The encoder <NUM> may provide encoded data <NUM> to the modulator <NUM>. The transmission data <NUM> may include network data to be relayed to the UE <NUM>.

The gNB operations module <NUM> may provide information <NUM> to the modulator <NUM>. This information <NUM> may include instructions for the modulator <NUM>. For example, the gNB operations module <NUM> may inform the modulator <NUM> of a modulation type (e.g., constellation mapping) to be used for transmissions to the UE(s) <NUM>. The modulator <NUM> may modulate the encoded data <NUM> to provide one or more modulated signals <NUM> to the one or more transmitters <NUM>.

The gNB operations module <NUM> may provide information <NUM> to the one or more transmitters <NUM>. This information <NUM> may include instructions for the one or more transmitters <NUM>. For example, the gNB operations module <NUM> may instruct the one or more transmitters <NUM> when to (or when not to) transmit a signal to the UE(s) <NUM>. The one or more transmitters <NUM> may upconvert and transmit the modulated signal(s) <NUM> to one or more UEs <NUM>.

It should be noted that a DL subframe may be transmitted from the gNB <NUM> to one or more UEs <NUM> and that a UL subframe may be transmitted from one or more UEs <NUM> to the gNB <NUM>. Furthermore, both the gNB <NUM> and the one or more UEs <NUM> may transmit data in a standard special subframe.

It should also be noted that one or more of the elements or parts thereof included in the eNB(s) <NUM> and UE(s) <NUM> may be implemented in hardware. For example, one or more of these elements or parts thereof may be implemented as a chip, circuitry or hardware components, etc. It should also be noted that one or more of the functions or methods described herein may be implemented in and/or performed using hardware. For example, one or more of the methods described herein may be implemented in and/or realized using a chipset, an application-specific integrated circuit (ASIC), a large-scale integrated circuit (LSI) or integrated circuit, etc..

<FIG> shows examples of multiple numerologies <NUM>. As shown in <FIG>, multiple numerologies <NUM> (e.g., multiple subcarrier spacing) may be supported. For example, µ (e.g., a subcarrier space configuration) and a cyclic prefix (e.g., the µ and the cyclic prefix for a carrier bandwidth part) may be configured by higher layer parameters (e.g., a RRC message) for the downlink and/or the uplink. Here, <NUM> may be a reference numerology <NUM>. For example, an RE of the reference numerology <NUM> may be defined with a subcarrier spacing of <NUM> in a frequency domain and 2048Ts + CP length (e.g., 160Ts or 144Ts) in a time domain, where Ts denotes a baseband sampling time unit defined as <NUM>/(<NUM>*<NUM>) seconds.

Additionally or alternatively, a number of OFDM symbol(s) <NUM> per slot ( <MAT>) may be determined based on the µ (e.g., the subcarrier space configuration). Here, for example, a slot configuration <NUM> (e.g., the number of OFDM symbols <NUM> per slot may be <NUM>).

<FIG> is a diagram illustrating one example of a resource grid <NUM> and resource block <NUM> (e.g., for the downlink and/or the uplink). The resource grid <NUM> and resource block <NUM> illustrated in <FIG> may be utilized in some implementations of the systems and methods disclosed herein.

In <FIG>, one subframe <NUM> may include <MAT> symbols <NUM>. Additionally or alternatively, a resource block <NUM> may include a number of resource elements (RE) <NUM>. Here, in the downlink, the OFDM access scheme with cyclic prefix (CP) may be employed, which may be also referred to as CP-OFDM. A downlink radio frame may include multiple pairs of downlink resource blocks (RBs) <NUM> which are also referred to as physical resource blocks (PRBs). The downlink RB pair is a unit for assigning downlink radio resources, defined by a predetermined bandwidth (RB bandwidth) and a time slot. The downlink RB pair may include two downlink RBs <NUM> that are continuous in the time domain. Additionally or alternatively, the downlink RB <NUM> may include twelve sub-carriers in frequency domain and seven (for normal CP) or six (for extended CP) OFDM symbols in time domain. A region defined by one sub-carrier in frequency domain and one OFDM symbol in time domain is referred to as a resource element (RE) <NUM> and is uniquely identified by the index pair (k,l), where k and l are indices in the frequency and time domains, respectively.

Additionally or alternatively, in the uplink, in addition to CP-OFDM, a Single-Carrier Frequency Division Multiple Access (SC-FDMA) access scheme may be employed, which is also referred to as Discrete Fourier Transform-Spreading OFDM (DFT-S-OFDM). An uplink radio frame may include multiple pairs of uplink resource blocks <NUM>. The uplink RB pair is a unit for assigning uplink radio resources, defined by a predetermined bandwidth (RB bandwidth) and a time slot. The uplink RB pair may include two uplink RBs <NUM> that are continuous in the time domain. The uplink RB may include twelve sub-carriers in frequency domain and seven (for normal CP) or six (for extended CP) OFDM/DFT-S-OFDM symbols in time domain. A region defined by one sub-carrier in the frequency domain and one OFDM/DFT-S-OFDM symbol in the time domain is referred to as a resource element (RE) <NUM> and is uniquely identified by the index pair (k,l) in a slot, where k and l are indices in the frequency and time domains, respectively.

Each element in the resource grid <NUM> (e.g., antenna port p) and the subcarrier configuration µ is called a resource element <NUM> and is uniquely identified by the index pair (k,l) where <MAT> is the index in the frequency domain and l refers to the symbol position in the time domain. The resource element (k,l) <NUM> on the antenna port p and the subcarrier spacing configuration µ is denoted (k,l)p,µ. The physical resource block <NUM> is defined as <MAT> consecutive subcarriers in the frequency domain. The physical resource blocks <NUM> are numbered from <NUM> to <MAT> in the frequency domain. The relation between the physical resource block number nPRB in the frequency domain and the resource element (k,l) is given by <MAT>.

In the NR, the following reference signals may be defined:.

NZP CSI-RS may be used for channel tracking (e.g., synchronization), measurement to obtain CSI (CSI measurement including channel measurement and interference measurement), and/or measurement to obtain the beam forming performance. NZP CSI-RS may be transmitted in the downlink (gNB to UE). NZP CSI-RS may be transmitted in an aperiodic or semi-persistent or periodic manner. Additionally, the NZP CSI-RS can be used for radio resource management (RRM) measurement and radio link control (RLM) measurement.

ZP CSI-RS may be used for interference measurement and transmitted in the downlink (gNB to UE). ZP CSI-RS may be transmitted in an aperiodic or semi-persistent or periodic manner.

DMRS may be used for demodulation for the downlink (gNB to UE), the uplink (UE to gNB), and the sideling (UE to UE).

SRS may be used for channel sounding and beam management. The SRS may be transmitted in the uplink (UE to gNB).

In some approaches, the DCI may be used. The following DCI formats may be defined:.

DCI format 1_0 may be used for the scheduling of PUSCH in one cell. The DCI may be transmitted by means of the DCI format 0_0 with cyclic redundancy check (CRC) scrambled by Cell Radio Network Temporary Identifiers (C-RNTI) or Configured Scheduling RNTI (CS-RNTI) or Modulation and Coding Scheme - Cell RNTI (MCS-C-RNTI).

DCI format 0_1 may be used for the scheduling of one or multiple PUSCH in one cell, or indicating configured grant downlink feedback information (CG-DFI) to a UE. The DCI may be transmitted by means of the DCI format 0_1 with CRC scrambled by C-RNTI or CS-RNTI or semi-persistent channel state information (SP-CSI-RNTI) or MCS-C-RNTI. The DCI format 0_2 may be used for CSI request (e.g., aperiodic CSI reporting or semi-persistent CSI request). The DCI format 0_2 may be used for SRS request (e.g., aperiodic SRS transmission).

DCI format 0_2 may be used for the scheduling of PUSCH in one cell. The DCI may be transmitted by means of the DCI format 0_2 with CRC scrambled by C-RNTI or CS-RNTI or SP-CSI-RNTI or MCS-C-RNTI. The DCI format 0_2 may be used for scheduling of PUSCH with high priority and/or low latency (e.g., URLLC). The DCI format 0_2 may be used for CSI request (e.g., aperiodic CSI reporting or semi-persistent CSI request). The DCI format 0_2 may be used for SRS request (e.g., aperiodic SRS transmission).

Additionally, for example, the DCI included in the DCI format 0_Y (Y = <NUM>, <NUM>, <NUM>,. ) may be a BWP indicator (e.g., for the PUSCH). Additionally or alternatively, the DCI included in the DCI format 0_Y may be a frequency domain resource assignment (e.g., for the PUSCH). Additionally or alternatively, the DCI included in the DCI format 0_Y may be a time domain resource assignment (e.g., for the PUSCH). Additionally or alternatively, the DCI included in the DCI format 0_Y may be a modulation and coding scheme (e.g., for the PUSCH). Additionally or alternatively, the DCI included in the DCI format 0_Y may be a new data indicator. Additionally or alternatively, the DCI included in the DCI format 0_Y may be a TPC command for scheduled PUSCH. Additionally or alternatively, the DCI included in the DCI format 0_Y may be a CSI request that is used for requesting the CSI reporting. Additionally or alternatively, as described below, the DCI included in the DCI format 0_Y may be information used for indicating an index of a configuration of a configured grant. Additionally or alternatively, the DCI included in the DCI format 0_Y may be the priority indication (e.g., for the PUSCH transmission and/or for the PUSCH reception).

DCI format 1_0 may be used for the scheduling of PDSCH in one DL cell. The DCI is transmitted by means of the DCI format 1_0 with CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI. The DCI format 1_0 may be used for random access procedure initiated by a PDCCH order. Additionally or alternatively, the DCI may be transmitted by means of the DCI format 1_0 with CRC scrambled by system information RNTI (SI-RNTI), and the DCI may be used for system information transmission and/or reception. Additionally or alternatively, the DCI may be transmitted by means of the DCI format 1_0 with CRC scrambled by random access RNTI (RA-RNTI) for random access response (RAR) (e.g., Msg <NUM>) or msgB-RNTI for <NUM>-step RACH. Additionally or alternatively, the DCI may be transmitted by means of the DCI format 1_0 with CRC scrambled by temporally cell RNTI (TC-RNTI), and the DCI may be used for msg3 transmission by a UE <NUM>.

DCI format 1_1 may be used for the scheduling of PDSCH in one cell. The DCI may be transmitted by means of the DCI format 1_1 with CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI. The DCI format 1_1 may be used for SRS request (e.g., aperiodic SRS transmission).

DCI format 1_2 may be used for the scheduling of PDSCH in one cell. The DCI may be transmitted by means of the DCI format 1_2 with CRC scrambled by C-RNTI or CS-RNTI or SP-CSI-RNTI or MCS-C-RNTI. The DCI format 1_2 may be used for scheduling of PDSCH with high priority and/or low latency (e.g., URLLC). The DCI format 1_2 may be used for SRS request (e.g., aperiodic SRS transmission).

Additionally, for example, the DCI included in the DCI format 1_X may be a BWP indicator (e.g., for the PDSCH). Additionally or alternatively, the DCI included in the DCI format 1_X may be frequency domain resource assignment (e.g., for the PDSCH). Additionally or alternatively, the DCI included in the DCI format 1_X may be a time domain resource assignment (e.g., for the PDSCH). Additionally or alternatively, the DCI included in the DCI format 1_X may be a modulation and coding scheme (e.g., for the PDSCH). Additionally or alternatively, the DCI included in the DCI format 1_X may be a new data indicator. Additionally or alternatively, the DCI included in the DCI format 1_X may be a TPC command for scheduled PUCCH. Additionally or alternatively, the DCI included in the DCI format 1_X may be a CSI request that is used for requesting (e.g., triggering) transmission of the CSI (e.g., CSI reporting (e.g., aperiodic CSI reporting)). Additionally or alternatively, the DCI included in the DCI format 1_X may be a PUCCH resource indicator. Additionally or alternatively, the DCI included in the DCI format 1_X may be a PDSCH-to-HARQ feedback timing indicator. Additionally or alternatively, the DCI included in the DCI format 1_X may be the priority indication (e.g., for the PDSCH transmission and/or the PDSCH reception). Additionally or alternatively, the DCI included in the DCI format 1_X may be the priority indication (e.g., for the HARQ-ACK transmission for the PDSCH and/or the HARQ-ACK reception for the PDSCH).

DCI format 2_0 may be used for notifying the slot format, channel occupancy time (COT) duration for unlicensed band operation, available resource block (RB) set, and search space group switching. The DCI may transmitted by means of the DCI format 2_0 with CRC scrambled by slot format indicator RNTI (SFI-RNTI).

DCI format 2_1 may be used for notifying the physical resource block(s) (PRB(s)) and orthogonal frequency division multiplexing (OFDM) symbol(s) where the UE may assume no transmission is intended for the UE. The DCI is transmitted by means of the DCI format 2_1 with CRC scrambled by interrupted transmission RNTI (INT-RNTI).

DCI format 2_2 may be used for the transmission of transmission power control (TPC) commands for PUCCH and PUSCH. The following information is transmitted by means of the DCI format 2_2 with CRC scrambled by TPC-PUSCH-RNTI or TPC-PUCCH-RNTI. In a case that the CRC is scrambled by TPC-PUSCH-RNTI, the indicated one or more TPC commands may be applied to the TPC loop for PUSCHs. In a case that the CRC is scrambled by TPC-PUCCH-RNTI, the indicated one or more TPC commands may be applied to the TPC loop for PUCCHs.

DCI format 2_3 may be used for the transmission of a group of TPC commands for SRS transmissions by one or more UEs. Along with a TPC command, a SRS request may also be transmitted. The DCI may be is transmitted by means of the DCI format 2_3 with CRC scrambled by TPC-SRS-RNTI.

DCI format 2_4 may be used for notifying the PRB(s) and OFDM symbol(s) where the UE cancels the corresponding UL transmission. The DCI may be transmitted by means of the DCI format 2_4 with CRC scrambled by cancellation indication RNTI (CI-RNTI).

DCI format 2_5 may be used for notifying the availability of soft resources for integrated access and backhaul (IAB) operation. The DCI may be transmitted by means of the DCI format 2_5 with CRC scrambled by availability indication RNTI (AI-RNTI).

DCI format 2_6 may be used for notifying the power saving information outside discontinuous reception (DRX) Active Time for one or more UEs. The DCI may transmitted by means of the DCI format 2_6 with CRC scrambled by power saving RNTI (PS-RNTI).

DCI format 3_0 may be used for scheduling of NR physical sidelink control channel (PSCCH) and NR physical sidelink shared channel (PSSCH) in one cell. The DCI may be transmitted by means of the DCI format 3_0 with CRC scrambled by sidelink RNTI (SL-RNTI) or sidelink configured scheduling RNTI (SL-CS-RNTI). This may be used for vehicular to everything (V2X) operation for NR V2X UE(s).

DCI format 3_1 may be used for scheduling of LTE PSCCH and LTE PSSCH in one cell. The following information is transmitted by means of the DCI format 3_1 with CRC scrambled by SL-L-CS-RNTI. This may be used for LTE V2X operation for LTE V2X UE(s).

The UE <NUM> may monitor one or more DCI formats on common search space set (CSS) and/or UE-specific search space set (USS). A set of PDCCH candidates for a UE to monitor may be defined in terms of PDCCH search space sets. A search space set can be a CSS set or a USS set. A UE <NUM> monitors PDCCH candidates in one or more of the following search spaces sets. The search space may be defined by a PDCCH configuration in a RRC layer.

A Type0-PDCCH CSS set may be configured by pdcch-ConfigSIB <NUM> in MIB or by searchSpaceSIB1 in PDCCH-ConfigCommon or by searchSpaceZero in PDCCH-ConfigCommon for a DCI format with CRC scrambled by a SI-RNTI on the primary cell of the MCG.

A Type0A-PDCCH CSS set may be configured by searchSpaceOtherSystemInformation in PDCCH-ConfigCommon for a DCI format with CRC scrambled by a SI-RNTI on the primary cell of the MCG.

A Type1-PDCCH CSS set may be configured by ra-SearchSpace in PDCCH-ConfigCommon for a DCI format with CRC scrambled by a RA-RNTI or a TC-RNTI on the primary cell.

A Type2-PDCCH CSS set may be configured by pagingSearchSpace in PDCCH-ConfigCommon for a DCI format with CRC scrambled by a P-RNTI on the primary cell of the MCG.

A Type3-PDCCH CSS set may be configured by SearchSpace in PDCCH-Config with searchSpaceType = common for DCI formats with CRC scrambled by INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, TPC-SRS-RNTI, CI-RNTI, or PS-RNTI and, only for the primary cell, C-RNTI, MCS-C-RNTI, or CS-RNTI(s), and.

A USS set may be configured by SearchSpace in PDCCH-Config with searchSpaceType = ue-Specific for DCI formats with CRC scrambled by C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, CS-RNTI(s), SL-RNTI, SL-CS-RNTI, or SL-L-CS-RNTI.

The UE <NUM> may monitor a set of candidates of the PDCCH in one or more control resource sets (e.g., CORESETs) on the active DL bandwidth part (BWP) on each activated serving cell according to corresponding search space sets. The CORESETs may be configured from gNB <NUM> to a UE <NUM>, and the CSS set(s) and the USS set(s) are defined in the configured CORESET. One or more CORESET may be configured in a RRC layer.

<FIG> shows examples of resource regions (e.g., resource region of the downlink). One or more sets <NUM> of PRB(s) <NUM> (e.g., a control resource set (e.g., CORESET)) may be configured for DL control channel monitoring (e.g., the PDCCH monitoring). For example, the CORESET is, in the frequency domain and/or the time domain, a set <NUM> of PRBs <NUM> within which the UE <NUM> attempts to decode the DCI (e.g., the DCI format(s), the PDCCH(s)), where the PRBs <NUM> may or may not be frequency contiguous and/or time contiguous, a UE <NUM> may be configured with one or more control resource sets (e.g., the CORESETs) and one DCI message may be mapped within one control resource set. In the frequency-domain, a PRB <NUM> is the resource unit size (which may or may not include DM-RS) for the DL control channel.

<FIG> illustrates an example of beamforming and quasi-colocation (QCL) type. In NR, the gNB <NUM> and UE <NUM> may perform beamforming by having multiple antenna elements. The beamforming is operated by using a directional antenna(s) or applying phase shift for each antenna element (e.g., a high electric field strength to a certain spatial direction can be achieved). In some examples, the beamforming or beam may be rephrased by "spatial domain transmission filter" or "spatial domain filter.

In the downlink, the gNB <NUM> may apply the transmission beamforming and transmit the DL channels and/or DL signals and a UE <NUM> may also apply the reception beamforming and receive the DL channels and/or DL signals.

In the uplink, a UE <NUM> may apply the transmission beamforming and transmit the UL channels and/or UL signals and a gNB <NUM> may also apply the reception beamforming and receive the UL channels and/or UL signals.

The beam correspondence may be defined according to the UE capability. In some examples, the beam correspondence may be defined in accordance with the following. In the downlink, a UE <NUM> can decide the transmission beamforming for UL channels and/or UL signals from the reception beamforming for DL channels and/or DL signals. In the uplink, a gNB <NUM> can decide the transmission beamforming for DL channels and/or DL signals from the reception beamforming for UL channels and/or UL signals.

To adaptively switch, refine, or operate beamforming, beam management may be performed. For the beam management, NZP-CSI-RS(s) and SRS(s) may be used to measure the channel quality in the downlink and uplink, respectively. Specifically, in the downlink, gNB <NUM> may transmit one or more NZP CSI-RSs. The UE <NUM> may measure the one or more NZP CSI-RSs. In addition, the UE <NUM> may change the beamforming to receive each NZP CSI-RS. The UE <NUM> can identify which combination of transmission beamforming at gNB side corresponding to NZP CSI-RS corresponding and the reception beamforming at the UE side. In the uplink, a UE <NUM> may transmit one or more SRSs. The gNB <NUM> measure the one or more SRSs. In addition, the gNB <NUM> may change the reception beamforming to receive each SRS. The gNB <NUM> can identify which combination of transmission beamforming at gNB side corresponding to SRS corresponding and the reception beamforming at the gNB side.

To keep the link with transmission beam and reception for the communication between a gNB <NUM> and a UE <NUM>, the quasi-colocation (QCL) assumption may be defined. Two antenna ports are said to be quasi co-located if the large-scale properties of the channel over which a symbol on one antenna port is conveyed can be inferred from the channel over which a symbol on the other antenna port is conveyed. The large-scale properties include one or more of delay spread, Doppler spread, Doppler shift, average gain, average delay, and spatial Rx parameters. The following QCL types may be defined:.

QCL type D is related to the beam management. For example, two NZP CSI-RS resources are configured to a UE <NUM> and a NZP CSI-RS resource #<NUM> and a NZP CSI-RS resource #<NUM> are used for beam #<NUM> and beam #<NUM>, respectively. At a UE side, Rx beam #<NUM> is used for the reception of the NZP CSI-RS #<NUM> and Rx beam #<NUM> is used for reception of the NZP CSI-RS #<NUM> for beam management. Here, the NZP CSI-RS resource #<NUM> and NZP CSI-RS resource #<NUM> imply Tx beam #<NUM> and Tx beam #<NUM>, respectively. QCL type D assumption may be used for PDCCH and PDSCH and DL signals reception. When a UE <NUM> receives a PDCCH with the QCL type D assumption of NZP CSI-RS #<NUM>, the UE <NUM> may use the Rx beam #<NUM> for the PDCCH reception.

For this purpose, a gNB <NUM> may configure transmission configuration indication (TCI) states to a UE <NUM>. A TCI state may include the following:.

For example, if a TCI state includes QCL type D and NZP CSI-RS #<NUM> and indicated to the UE <NUM>, the UE <NUM> may apply Rx beam #<NUM> to the reception of a PDCCH, a PDSCH, and/or DL signal(s). In other words, a UE <NUM> can determine the reception beam by using TCI states for reception of PDCCH, PDSCH, and/or DL signals.

<FIG> illustrates an example of transmission configuration indication (TCI) states. The seven TCI states may be configured and one of the configured TCI states may be used to receive PDCCH, PDSCH, and/or DL signals. For example, if gNB <NUM> indicates TCI state #<NUM>, a UE <NUM> may assume the PDCCH, PDSCH, and/or DL signals is (are) quasi-colocated with the NZP CSI-RS corresponding to the NZP CSI-RS resource #<NUM>. A UE <NUM> may determine to use the reception beam when the UE <NUM> receives the NZP CSI-RS corresponding to the NZP CSI-RS resource #<NUM>.

Next, how to indicate one TCI state to a UE <NUM> from gNB <NUM>. In the RRC messages, N TCI states may be configured by a RRC message. A gNB <NUM> may indicate one of the configured TCI states by DCI (e.g., DCI format 1_1 or DCI format 1_2). Alternatively or additionally, the gNB <NUM> may indicate one of the configured TCI by MAC CE. Alternatively or additionally, the MAC CE selects more than one TCI states from the configured TCI states and DCI indicates one of the more than one TCI states activated by MAC CE.

<FIG> is a flow diagram illustrating an example of a method <NUM> in accordance with some of the techniques described herein. In some examples, the method <NUM> may be performed by the UE <NUM> described in relation to <FIG>.

The UE may receive <NUM> first information to configure one or more CSI-RS for tracking and second information to configure time domain correlation related information. In some examples, this may be performed as described in relation to <FIG>.

The UE may transmit <NUM> a CSI report including the time domain correlation related information. A first parameter trs-Info may be included in the first information. A second parameter reportQuantity may not be set to 'none'. The time domain correlation related information may be measured by the one or more CSI-RS for tracking. In some examples, this may be performed as described in relation to <FIG>.

<FIG> is a flow diagram illustrating an example of a method <NUM> in accordance with some of the techniques described herein. In some examples, the method <NUM> may be performed by the gNB <NUM> described in relation to <FIG>.

The gNB may transmit <NUM> first information to configure one or more CSI-RS for tracking and second information to configure time domain correlation related information. In some examples, this may be performed as described in relation to <FIG>.

The gNB may receive <NUM> a CSI report including the time domain correlation related information. A first parameter trs-Info may be included in the first information. A second parameter reportQuantity may not be set to 'none'. The time domain correlation related information may be measured by the one or more CSI-RS for tracking. In some examples, this may be performed as described in relation to <FIG>.

Figure 9A is a flow diagram illustrating an example of a method 900a in accordance with some of the techniques described herein. In some examples, the method 900a may be performed by the UE <NUM> described in relation to <FIG>.

The UE may receive 902a first information to configure one or more CSI-RS for tracking and second information to configure time domain correlation related information. In some examples, this may be performed as described in relation to <FIG>.

The UE may transmit 904a a CSI report including the time domain correlation related information. A first parameter trs-Info may be included in the first information. A second parameter may indicate one of a periodic CSI report, semi-persistent CSI report, and aperiodic CSI report. The time domain correlation related information may be measured by the one or more CSI-RS for tracking. The CSI report including the time domain correlation related information may be transmitted based on the second parameter. In some examples, this may be performed as described in relation to <FIG>.

Figure 9B is a flow diagram illustrating an example of a method 900b in accordance with some of the techniques described herein. In some examples, the method 900b may be performed by the gNB <NUM> described in relation to <FIG>.

The gNB may transmit 902b first information to configure one or more CSI-RS for tracking and second information to configure time domain correlation related information. In some examples, this may be performed as described in relation to <FIG>.

The gNB may receive 904b a CSI report including the time domain correlation related information. A first parameter trs-Info may be included in the first information. A second parameter may indicate one of periodic CSI report, semi-persistent CSI report, and aperiodic CSI report. The time domain correlation related information may be measured by the one or more CSI-RS for tracking. The CSI report including the time domain correlation related information may be received based on the second parameter. In some examples, this may be performed as described in relation to <FIG>.

<FIG> illustrates various components that may be utilized in a UE <NUM>. The UE <NUM> described in connection with <FIG> may be implemented in accordance with the UE <NUM> described in connection with <FIG>. The UE <NUM> includes a processor <NUM> that controls operation of the UE <NUM>. The processor <NUM> may also be referred to as a central processing unit (CPU). Memory <NUM>, which may include read-only memory (ROM), random access memory (RAM), a combination of the two or any type of device that may store information, provides instructions 1007a and data 1009a to the processor <NUM>. A portion of the memory <NUM> may also include non-volatile random access memory (NVRAM). Instructions 1007b and data 1009b may also reside in the processor <NUM>. Instructions 1007b and/or data 1009b loaded into the processor <NUM> may also include instructions 1007a and/or data 1009a from memory <NUM> that were loaded for execution or processing by the processor <NUM>. The instructions 1007b may be executed by the processor <NUM> to implement the methods described herein.

The UE <NUM> may also include a housing that contains one or more transmitters <NUM> and one or more receivers <NUM> to allow transmission and reception of data. The transmitter(s) <NUM> and receiver(s) <NUM> may be combined into one or more transceivers <NUM>. One or more antennas 1022a-n are attached to the housing and electrically coupled to the transceiver <NUM>.

<FIG> illustrates various components that may be utilized in a gNB <NUM>. The gNB <NUM> described in connection with <FIG> may be implemented in accordance with the gNB <NUM> described in connection with <FIG>. The gNB <NUM> includes a processor <NUM> that controls operation of the gNB <NUM>. The processor <NUM> may also be referred to as a central processing unit (CPU). Memory <NUM>, which may include read-only memory (ROM), random access memory (RAM), a combination of the two or any type of device that may store information, provides instructions 1107a and data 1109a to the processor <NUM>. A portion of the memory <NUM> may also include non-volatile random access memory (NVRAM). Instructions 1107b and data 1109b may also reside in the processor <NUM>. Instructions 1107b and/or data 1109b loaded into the processor <NUM> may also include instructions 1107a and/or data 1109a from memory <NUM> that were loaded for execution or processing by the processor <NUM>. The instructions 1107b may be executed by the processor <NUM> to implement the methods described herein.

The gNB <NUM> may also include a housing that contains one or more transmitters <NUM> and one or more receivers <NUM> to allow transmission and reception of data. The transmitter(s) <NUM> and receiver(s) <NUM> may be combined into one or more transceivers <NUM>. One or more antennas 1180a-n are attached to the housing and electrically coupled to the transceiver <NUM>.

The various components of the gNB <NUM> are coupled together by a bus system <NUM>, which may include a power bus, a control signal bus and a status signal bus, in addition to a data bus. The gNB <NUM> may also include a digital signal processor (DSP) <NUM> for use in processing signals. The gNB <NUM> may also include a communications interface <NUM> that provides user access to the functions of the gNB <NUM>. The gNB <NUM> illustrated in <FIG> is a functional block diagram rather than a listing of specific components.

<FIG> is a block diagram illustrating one implementation of a UE <NUM> in which one or more of the systems and/or methods described herein may be implemented. The UE <NUM> includes transmit means <NUM>, receive means <NUM> and control means <NUM>. The transmit means <NUM>, receive means <NUM> and control means <NUM> may be configured to perform one or more of the functions described in connection with <FIG> above. <FIG> above illustrates one example of a concrete apparatus structure of <FIG>. Other various structures may be implemented to realize one or more of the functions of <FIG>. For example, a DSP may be realized by software.

<FIG> is a block diagram illustrating one implementation of a gNB <NUM> in which one or more of the systems and/or methods described herein may be implemented. The gNB <NUM> includes transmit means <NUM>, receive means <NUM> and control means <NUM>. The transmit means <NUM>, receive means <NUM> and control means <NUM> may be configured to perform one or more of the functions described in connection with <FIG> above. <FIG> above illustrates one example of a concrete apparatus structure of <FIG>. Other various structures may be implemented to realize one or more of the functions of <FIG>. For example, a DSP may be realized by software.

<FIG> is a block diagram illustrating one implementation of a gNB <NUM>. The gNB <NUM> may be an example of the gNB <NUM> described in connection with <FIG>. The gNB <NUM> may include a higher layer processor <NUM>, a DL transmitter <NUM>, a UL receiver <NUM>, and one or more antenna <NUM>. The DL transmitter <NUM> may include a PDCCH transmitter <NUM> and a PDSCH transmitter <NUM>. The UL receiver <NUM> may include a PUCCH receiver <NUM> and a PUSCH receiver <NUM>.

The higher layer processor <NUM> may manage physical layer's behaviors (the DL transmitter's and the UL receiver's behaviors) and provide higher layer parameters to the physical layer. The higher layer processor <NUM> may obtain transport blocks from the physical layer. The higher layer processor <NUM> may send/acquire higher layer messages such as an RRC message and MAC message to/from a UE's higher layer. The higher layer processor <NUM> may provide the PDSCH transmitter transport blocks and provide the PDCCH transmitter transmission parameters related to the transport blocks.

The DL transmitter <NUM> may multiplex downlink physical channels and downlink physical signals (including reservation signal) and transmit them via transmission antennas <NUM>. The UL receiver <NUM> may receive multiplexed uplink physical channels and uplink physical signals via receiving antennas <NUM> and de-multiplex them. The PUCCH receiver <NUM> may provide the higher layer processor <NUM> UCI. The PUSCH receiver <NUM> may provide the higher layer processor <NUM> received transport blocks.

<FIG> is a block diagram illustrating one implementation of a UE <NUM>. The UE <NUM> may be an example of the UE <NUM> described in connection with <FIG>. The UE <NUM> may include a higher layer processor <NUM>, a UL transmitter <NUM>, a DL receiver <NUM>, and one or more antenna <NUM>. The UL transmitter <NUM> may include a PUCCH transmitter <NUM> and a PUSCH transmitter <NUM>. The DL receiver <NUM> may include a PDCCH receiver <NUM> and a PDSCH receiver <NUM>.

The higher layer processor <NUM> may manage physical layer's behaviors (the UL transmitter's and the DL receiver's behaviors) and provide higher layer parameters to the physical layer. The higher layer processor <NUM> may obtain transport blocks from the physical layer. The higher layer processor <NUM> may send/acquire higher layer messages such as an RRC message and MAC message to/from a UE's higher layer. The higher layer processor <NUM> may provide the PUSCH transmitter transport blocks and provide the PUCCH transmitter <NUM> UCI.

The DL receiver <NUM> may receive multiplexed downlink physical channels and downlink physical signals via receiving antennas <NUM> and de-multiplex them. The PDCCH receiver <NUM> may provide the higher layer processor <NUM> DCI. The PDSCH receiver <NUM> may provide the higher layer processor <NUM> received transport blocks.

The term "computer-readable medium" refers to any available medium that can be accessed by a computer or a processor. The term "computer-readable medium," as used herein, may denote a computer- and/or processor-readable medium that is non-transitory and tangible. By way of example and not limitation, a computer-readable or processor-readable medium may comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer or processor. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Bluray® disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers.

It should be noted that one or more of the methods described herein may be implemented in and/or performed using hardware. For example, one or more of the methods described herein may be implemented in and/or realized using a chipset, an application-specific integrated circuit (ASIC), a large-scale integrated circuit (LSI) or integrated circuit, etc..

A program running on the gNB <NUM> or the UE <NUM> according to the described systems and methods is a program (a program for causing a computer to operate) that controls a CPU and the like in such a manner as to realize the function according to the described systems and methods. Then, the information that is handled in these apparatuses is temporarily stored in a RAM while being processed. Thereafter, the information is stored in various ROMs or HDDs, and whenever necessary, is read by the CPU to be modified or written. As a recording medium on which the program is stored, among a semiconductor (for example, a ROM, a nonvolatile memory card, and the like), an optical storage medium (for example, a DVD, a MO, a MD, a CD, a BD and the like), a magnetic storage medium (for example, a magnetic tape, a flexible disk and the like) and the like, any one may be possible. Furthermore, in some cases, the function according to the described systems and methods described herein is realized by running the loaded program, and in addition, the function according to the described systems and methods is realized in conjunction with an operating system or other application programs, based on an instruction from the program.

Furthermore, in a case where the programs are available on the market, the program stored on a portable recording medium can be distributed or the program can be transmitted to a server computer that connects through a network such as the Internet. In this case, a storage device in the server computer also is included. Furthermore, some or all of the gNB <NUM> and the UE <NUM> according to the systems and methods described herein may be realized as an LSI that is a typical integrated circuit. Each functional block of the gNB <NUM> and the UE <NUM> may be individually built into a chip, and some or all functional blocks may be integrated into a chip. Furthermore, a technique of the integrated circuit is not limited to the LSI, and an integrated circuit for the functional block may be realized with a dedicated circuit or a general-purpose processor. Furthermore, if with advances in a semiconductor technology, a technology of an integrated circuit that substitutes for the LSI appears, it is also possible to use an integrated circuit to which the technology applies.

Moreover, each functional block or various features of the base station device and the terminal device used in each of the aforementioned embodiments may be implemented or executed by a circuitry, which is typically an integrated circuit or a plurality of integrated circuits. The circuitry designed to execute the functions described in the present specification may comprise a general-purpose processor, a digital signal processor (DSP), an application specific or general application integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gates or transistor logic, or a discrete hardware component, or a combination thereof. The general-purpose processor may be a microprocessor, or alternatively, the processor may be a conventional processor, a controller, a microcontroller, or a state machine. The general-purpose processor or each circuit described herein may be configured by a digital circuit or may be configured by an analogue circuit. Further, when a technology of making into an integrated circuit superseding integrated circuits at the present time appears due to advancement of a semiconductor technology, the integrated circuit by this technology is also able to be used.

Claim 1:
A user equipment, UE (<NUM>), comprising:
receiving circuitry (<NUM>) configured to receive first information to configure one or more non-zero power channel state information-reference signal, NZP CSI-RS, resources and second information to configure CSI reporting;
measurement circuitry (<NUM>) configured to measure time domain correlation related information, TDCI, based on the second information; and characterised by
transmitting circuitry (<NUM>) configured to transmit a channel state information, CSI, report including the time domain correlation related information based on the second information, wherein:
the second information is associated with the first information,
the first information includes a first parameter trs-info indicating that each NZP CSI-RS resource of the one or more NZP CSI-RS resources is a NZP CSI-RS resource for tracking in the time and frequency domain,
the second information includes a second parameter reportQuantity indicating which kind of CSI report is set to include the TDCI.