Systems and methods for quasi-co-location (QCL) indication

Abstract

Systems, apparatus, methods, and computer-readable media for QCL indication for A-TRS and / or triggering aperiodic CSI-RS are described. Embodiments may include QCL information determination for A-TRS and / or spatial QCL hypothesis determination for aperiodic CSI-RS. Other embodiments may be described and / or claimed.

Description

[0001] Priority claim

[0002] This application claims the benefit of priority to PCT application serial number PCT / CN2018 / 082684, entitled “QUASI CO-LOCATION (QCL) INDICATION FOR APERIODIC TRACKING REFERENCE SIGNAL (A-TRS)”, filed on April 11, 2018, and PCT application serial number PCT / CN2018 / 083171, entitled “TRIGGERING APERIODIC CHANNEL STATE INFORMATION REFERENCE SIGNAL (CSI-RS) IN NEW RADIO (NR) SYSTEMS”, filed on April 16, 2018, both of which are incorporated herein by reference in their entirety. Technical Field

[0003] Various embodiments herein relate generally to the field of wireless communications, and more specifically, to systems and methods for quasi-co-located (QCL) indication of an aperiodic tracking reference signal (A-TRS) and / or triggered aperiodic channel state information reference signal (CSI-RS). Background Art

[0004] A wireless system typically includes a plurality of user equipment (UE) devices communicatively coupled to one or more base stations (BSs). One or more BSs may be long term evolution (LTE) evolved NodeBs (eNBs) or new radio (NR) next generation NodeBs (gNBs), which may be communicatively coupled to one or more UEs via a third generation partnership project (3GPP) network. A UE may be one or more of a smart phone, a tablet computing device, a laptop computer, an Internet of Things (IoT) device, and / or other types of computing devices configured to provide digital communications. As used herein, digital communications may include data and / or voice communications as well as control information.

[0005] In a wireless system, CSI-RS can be used for channel quality indicator (CQI) measurement, precoding matrix indicator (PMI) measurement, rank indicator (RI) measurement, etc., and tracking reference signal (TRS) can be used for time and frequency offset tracking. In some cases, TRS can also be CSI-RS for tracking. CSI-RS and / or TRS can be transmitted in a periodic or aperiodic manner. For CSI-RS and / or TRS transmitted in an aperiodic manner, its QCL information or QCL assumption can be identified. Summary of the invention

[0006] In some embodiments, the present invention may provide an apparatus for a user equipment (UE), comprising:

[0007] an interface through which the UE is configured to communicate with a base station (BS);

[0008] Processor, configured as:

[0009] At the UE, decoding an aperiodic tracking reference signal (A-TRS) from the BS via a physical downlink shared channel (PDSCH); and

[0010] At a UE, quasi-co-location (QCL) information of an A-TRS is determined, wherein, when the A-TRS spans at least two consecutive time slots and a threshold for a scheduling offset is between at least two consecutive time slots, a QCL assumption is determined based at least in part on a type of QCL configuration information, wherein the type includes at least one of type A and type D.

[0011] In another embodiment, the present invention may provide an apparatus for a user equipment (UE), comprising:

[0012] an interface through which the UE is configured to communicate with a base station (BS);

[0013] Processor, configured as:

[0014] At the UE, decoding an aperiodic channel state information reference signal (CSI-RS) for beam management from the BS through a physical downlink shared channel (PDSCH); and

[0015] At the UE, a spatial quasi-co-location (QCL) assumption of the CSI-RS is determined based on a scheduling offset between a triggering downlink control indicator (DCI) for triggering the CSI-RS and the CSI-RS. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Features and advantages of the present disclosure will become apparent from the following detailed description taken in conjunction with the accompanying drawings, which together with the detailed description illustrate, by way of example, features of the present disclosure, in which:

[0017] Figure 1 A wireless system according to some embodiments is shown.

[0018] Figure 2 Depicted is a QCL indication for a PDSCH according to some embodiments.

[0019] Figure 3 Illustrate the problems associated with TRS QCL assumptions.

[0020] Figure 4Depicted is an example of QCL indication for aperiodic TRS with scheduling restrictions in accordance with some embodiments.

[0021] Figure 5 Depicted is an example of an aperiodic TRS QCL assumption in accordance with some embodiments.

[0022] Figure 6 Depicted is an exemplary aperiodic TRS QCL assumption when Type D QCL is not configured in accordance with some embodiments.

[0023] Figure 7 An example of a method performed by a user equipment (UE) for QCL indication of an aperiodic TRS in accordance with some embodiments is depicted.

[0024] Figure 8 Depicted is an example of a spatial QCL hypothesis of repeated ON according to some embodiments.

[0025] Fig. 9 Depicts an example of a spatial QCL assumption of repeated OFF in accordance with some embodiments.

[0026] Fig.10 An example of frequency division multiplexed (FDMed) CSI-RS and PDSCH is depicted in accordance with some embodiments.

[0027] Fig.11 An example of time division multiplexed (TDMed) CSI-RS and PDSCH is depicted in accordance with some embodiments.

[0028] Fig.12 Depicted are examples of CSI-RS and possible PDSCH according to some embodiments.

[0029] Fig.13 An example of a method performed by a user equipment (UE) for triggering a QCL indication of an aperiodic CSI-RS according to some embodiments is depicted.

[0030] Fig.14 Depicted is an exemplary measurement model in accordance with some embodiments.

[0031] Fig.15 The architecture of a system 1500 of a network according to some embodiments is shown.

[0032] Fig.16 Example components of device 1600 are shown in accordance with some embodiments.

[0033] Fig.17 An example interface of a baseband circuit according to some embodiments is shown.

[0034] Fig.18is a diagram of a control plane protocol stack according to some embodiments.

[0035] Fig.19 is a diagram of a user plane protocol stack according to some embodiments.

[0036] Fig. 20 Components of a core network are shown according to some embodiments.

[0037] Fig.21 is a block diagram illustrating components of a system 2100 for supporting NFV according to some exemplary embodiments; and

[0038] Fig. 22 is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium (eg, a non-transitory machine-readable storage medium) and performing any one or more of the methodologies discussed herein, according to some example embodiments.

[0039] Reference will now be made to the exemplary embodiments illustrated, and specific language will be used herein to describe the same. It will however be understood that no limitation of the scope of the technology is intended thereby. DETAILED DESCRIPTION

[0040] The following detailed description refers to the accompanying drawings. The same reference numerals that may be used in different figures identify the same or similar elements. In the following description, specific details such as specific structures, architectures, interfaces, technologies, etc. are set forth for the purpose of explanation rather than limitation, so as to provide a thorough understanding of various aspects of the claimed embodiments. However, it will be apparent to those skilled in the art who benefit from the present disclosure that various aspects of the claimed embodiments can be practiced in other examples that depart from these specific details. In some cases, descriptions of well-known devices, circuits, and methods are omitted to avoid obscuring the description of the embodiments of the present disclosure by unnecessary details.

[0041] The various aspects of the illustrative embodiments will be described using terms commonly used by those skilled in the art to convey the essence of their work to other persons skilled in the art. However, it will be apparent to those skilled in the art that alternative embodiments may be practiced using only some of the described aspects. For purposes of explanation, specific numbers, materials, and configurations are set forth to provide a thorough understanding of the illustrative embodiments. However, it will be apparent to those skilled in the art that alternative embodiments may be practiced without the specific details. In other cases, well-known features have been omitted or simplified to avoid obscuring the illustrative embodiments.

[0042] In addition, various operations will be described as multiple discrete operations in a manner that is most helpful for understanding the illustrative embodiments. However, the order of description should not be interpreted as implying that these operations must be dependent on the order. Specifically, these operations do not need to be performed in the order presented.

[0043] The phrase "in various embodiments," "in some embodiments," etc. is used repeatedly. The phrase generally does not refer to the same embodiment; however, it may. The terms "comprising," "having," and "including" are synonymous unless the context dictates otherwise. The phrase "A or B" means (A), (B), or (A and B).

[0044] Example embodiments may be described as a process, which is depicted as a flow chart, a flowchart, a data flow diagram, a structure diagram, or a block diagram. Although a flow chart may describe the operations as a sequential process, many operations may be performed in parallel, concurrently, or simultaneously. In addition, the order of the operations may be rearranged. A process may terminate when its operations are completed, but may also have additional operations not included in the figures. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination may correspond to the function returning to the calling function and / or the main function.

[0045] As used herein, the term "processor" refers to, is part of, or includes the following circuits: capable of sequentially and automatically performing a series of arithmetic or logical operations; recording, storing, and / or transmitting digital data. The term "processor" may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and / or any other device capable of executing or operating computer-executable instructions (e.g., program code, software modules, and / or function processing). As used herein, the term "interface" refers to, is part of, or includes the following circuits: providing information exchange between two or more components or devices. The term "interface" may refer to one or more hardware interfaces (e.g., a bus, an input / output (I / O) interface, a peripheral component interface, etc.).

[0046] FIG. Figure 1A wireless system according to some embodiments is shown. In one aspect, the wireless system 100 includes one or more base stations (BS) 110 and one or more user equipment (UE) devices 120, which can be communicatively coupled via a wireless communication protocol. In one instance, one or more BSs can be long term evolution (LTE) evolved NodeBs (eNBs) or new radio (NR) next generation NodeBs (gNBs), which can be communicatively coupled to one or more UEs via a third generation partnership project (3GPP) long term evolution (LTE) network 130. In one embodiment, the UE can be one or more of a smart phone, a tablet computing device, a laptop computer, an Internet of Things (IoT) device, and / or other types of computing devices configured to provide digital communications. As used herein, digital communications can include data and / or voice communications as well as control information.

[0047] I. Quasi-Co-location (QCL) Indication of Aperiodic Tracking Reference Signal (A-TRS)

[0048] Embodiments herein may provide a mechanism for quasi-co-location (QCL) information indication for aperiodic tracking reference signals (TRS).Embodiments may include assumptions of QCL configuration information by a user equipment (UE) and scheduling restrictions based on the QCL assumptions.

[0049] Figure 2 Depicted is a QCL indication for a PDSCH according to some embodiments. Figure 3 Illustrate the problems associated with TRS QCL assumptions. Figure 4 Depicted is an example of QCL indication for aperiodic TRS with scheduling restrictions in accordance with some embodiments. Figure 5 Depicted is an example of an aperiodic TRS QCL assumption in accordance with some embodiments. Figure 6 Depicted is an exemplary aperiodic TRS QCL assumption when no type DQCL is configured in accordance with some embodiments.

[0050] In wireless communication systems such as the fifth generation system (5GS), a tracking reference signal (TRS) may be used for time and frequency offset tracking. TRS may be transmitted in a periodic or aperiodic manner. When TRS is transmitted in an aperiodic manner, its quasi-co-location (QCL) information may be identified. The following types of QCL configuration information may exist:

[0051] QCL-TypeA: {Doppler shift, Doppler spread, average delay, delay spread}

[0052] QCL-TypeB: {Doppler shift, Doppler spread}

[0053] QCL-TypeC: {average delay, Doppler shift}

[0054] QCL-TypeD: {Spatial Receive (Rx) Parameters}

[0055] Then how to determine the QCL assumption of aperiodic TRS may be a problem. For the PDSCH QCL configuration information indication, when the scheduling offset is lower than the threshold, if multiple CORESETs are configured, the PDSCH uses the latest control resource set (CORESET) with the lowest CORESET ID for QCL, where CORESET 0 and the CORESET used for beam failure recovery can be excluded; when the scheduling offset is higher than the threshold, the PDSCH uses the reference signal indicated in the transmission configuration indication (TCI) indicated by the scheduling PDCCH for QCL, such as Figure 2 shown.

[0056] However, a non-periodic TRS can span two consecutive time slots. Therefore, there may be a situation where the threshold is exactly in the middle of two consecutive time slots, such as Figure 3 shown.

[0057] This article is about solving Figure 3 Various exemplary embodiments are described with reference to the problems shown and described. However, the embodiments are not limited in this regard, and the embodiments herein may be applicable to other signals, systems, and the like. For example, TRS-related embodiments may be applicable to a channel state information reference signal (CSI-RS) for tracking. In some embodiments, a TRS resource set may indicate a CSI-RS resource set for tracking. For each CSI-RS resource set for tracking, a parameter TRS-Info may be configured, and corresponding QCL configuration information may be configured through radio resource control (RRC) signaling, which may include at least one of the QCL types, for example, QCL type A+QCL type D or QCL type A. A TRS resource set may include 4 TRS resources mapped to different symbols.

[0058] In some embodiments, if the QCL type D of the TRS is included in the QCL configuration information of the aperiodic TRS resource set, the UE can be configured to set the scheduling offset between the last symbol of the scheduled PDCCH and each aperiodic TRS resource to be higher than the threshold for scheduling. For example, the UE should expect that the scheduling offset between the last symbol of the scheduled PDCCH and each aperiodic TRS resource should be higher than the threshold. The threshold can be based on the UE capability. Then, the aperiodic TRS can be QCLed with the indicated QCL configuration information, such as Figure 4 As shown, CRI indicates the CSI-RS resource index.

[0059] In other embodiments, if the QCL type D of the TRS is included in the QCL configuration information of the non-periodic TRS resource set, the QCL assumption of the non-periodic TRS can be determined by the scheduling offset between the last symbol of the scheduling PDCCH and a specific TRS resource (e.g., the first TRS resource). Then, if the scheduling offset is lower than or equal to the threshold reported by the UE capability, the UE can assume that if multiple CORESETs are configured in the time slot of the current bandwidth part (BWP), the non-periodic TRS is QCLed with the latest CORESET with the lowest CORESET ID, where CORESET 0 and / or CORESET-BFR can be excluded; otherwise, the non-periodic TRS is QCLed with the non-periodic TRS resource set index triggered by the scheduling PDCCH, such as Figure 5 shown.

[0060] If aperiodic TRS is used, only 1-slot based TRS may be triggered.The QCL hypothesis for the aperiodic TRS is then determined at the slot level, based on the scheduling offset between the last symbol of the scheduled PDCCH and the first TRS resource.

[0061] In other embodiments, if the Type D QCL of the TRS is included in the QCL configuration information of the aperiodic TRS resource set, the aperiodic TRS QCL assumption is derived from the QCL parameters configured in the RRC that triggers the aperiodic TRS resource set, regardless of the scheduling offset, such as Figure 6 shown.

[0062] In other embodiments, aperiodic TRS may be used for only one frequency range (FR), FR1 (band < 6 GHz) or FR2 (band > 6 GHz). In addition, the UE may expect that QCL type D should not be configured for aperiodic TRS, so that aperiodic TRS may be used only for FR1. Alternatively, the UE may expect that QCL type D should be configured for aperiodic TRS, so that aperiodic TRS may be used for FR2.

[0063] Figure 7 An example of a method performed by a UE for QCL indication of aperiodic TRS according to some embodiments is depicted.

[0064] At 702, the UE may receive and decode an aperiodic tracking reference signal (A-TRS) from a BS (e.g., a gNB) on a physical downlink shared channel (PDSCH). In another example, the A-TRS may be a channel state information reference signal (CSI-RS) for tracking.

[0065] At 704, the UE may determine quasi-co-location (QCL) information for the A-TRS. When the A-TRS spans at least two consecutive time slots and the threshold for the scheduling offset is between the at least two consecutive time slots, the QCL assumption is determined based at least in part on the type of the QCL configuration information. The type may include at least one of type A and type D. Type A may indicate at least one of Doppler shift, Doppler spread, average delay, and delay spread, and type D may indicate a spatial Rx parameter. In some embodiments, in response to type D being included in the QCL configuration information of the A-TRS resource set, the scheduling offset between the last symbol of the scheduling physical downlink control channel (PDCCH) and each A-TRS resource is set to be higher than the threshold, and the A-TRS is QCLed with the QCL assumption indicated by the scheduling PDCCH.

[0066] In another embodiment, in response to type D being included in the QCL configuration information of the A-TRS resource set: when the scheduling offset between the last symbol of the scheduled physical downlink control channel (PDCCH) and each A-TRS resource is lower than or equal to a threshold, the A-TRS is QCLed with the latest control resource set (CORESET) with the lowest CORESET ID, wherein CORESET 0 and / or CORESET for beam failure recovery are excluded; otherwise, the A-TRS is QCLed with the QCL assumption indicated by the scheduling PDCCH.

[0067] In another embodiment, the QCL assumption is derived from the QCL parameters configured in the radio resource control (RRC) layer that triggers the A-TRS resource set regardless of the scheduling offset.

[0068] In another embodiment, Type D is not configured for A-TRS such that A-TRS is used only for frequency range (FR) 1, and Type D is configured for A-TRS such that A-TRS is used only for FR 2. FR 1 may be below 6 GHz and FR 2 may be above 6 GHz.

[0069] At 706, the UE may send the determined QCL hypothesis to a BS (e.g., gNB) on a physical uplink shared channel (PUSCH).

[0070] Note that the above embodiments and any of the following examples may also be applied to CSI-RS for other purposes.

[0071] II. Quasi-Co-Location (QCL) Indication for Triggering Aperiodic Channel State Information Reference Signal (CSI-RS)

[0072] Embodiments herein provide a mechanism for channel state information reference signal (CSI-RS) resource triggering and spatial quasi-co-location (QCL) determination of CSI-RS.

[0073] Aperiodic CSI-RS including non-zero power (NZP) CSI-RS, zero power (ZP) CSI-RS and CSI-RS / channel state information interference measurement (CSI-IM) resources can be triggered by downlink control information (DCI). Due to the DCI decoding and user equipment (UE) receive (Rx) beam switching delay, the default spatial QCL assumption can be applied if the offset between DCI and CSI-RS is less than a certain threshold.

[0074] Taking into account the different purposes of CSI-RS, for example, whether CSI-RS-ResourceRep is set to ON or OFF (CSI-RS-ResourceRep is ON, indicating Tx beam repetition, and CSI-RS-ResourceRep is OFF, indicating Tx beam non-repetition), different rules may be applied to determine the spatial QCL assumption. If CSI-RS-ResourceRep is set to ON and the scheduling offset between DCI and CSI-RS is less than a specific threshold, the default spatial QCL assumption may be applied for those CSI-RS within the threshold range. For those CSI-RS outside the threshold range, the UE may perform UE Rx beam scanning. If CSI-RS-ResourceRep is set to 'OFF' and the scheduling offset between DCI and CSI-RS is less than a specific threshold, the UE may apply the default spatial QCL assumption for all triggered CSI-RS.

[0075] Aperiodic CSI-RS including NZP CSI-RS, ZP CSI-RS and CSI-RS / CSI-IM resources can be triggered by DCI. Due to DCI decoding and UE Rx beam switching delays, the default spatial QCL assumption can be applied if the offset between DCI and CSI-RS is less than a certain threshold.

[0076] 1. Aperiodic CSI-RS triggering for beam management

[0077] For beam management, the configuration parameter CSI-RS-ResourceRep. If CSI-RS-ResourceRep is set to ON, the base station (e.g., next-generation NodeB (gNB or gNodeB)) can apply the same transmit (Tx) beam. If CSI-RS-ResourceRep is set to OFF, different Tx beams can be applied.

[0078] CSI-RS-ResourceRep is set to ON

[0079] Figure 8 Depicted is an example of a spatial QCL hypothesis of repeated ON according to some embodiments.

[0080] When CSI-RS-ResourceRep is set to 'ON', it means that the UE can perform UE Rx beam scanning to refine the Rx beam. However, if the offset between DCI and CSI-RS is less than a certain threshold, it is impossible for the UE to perform Rx beam scanning for those CSI-RS resources that appear within the threshold range because the UE is not aware of the CSI-RS transmission yet. For those CSI-RS resources outside the threshold range, the UE can perform Rx beam scanning on the CSI-RS resources.

[0081] In various embodiments, if CSI-RS-ResourceRep is set to ON and the scheduling offset between DCI and CSI-RS is less than a specific threshold, a default spatial QCL assumption can be applied for those CSI-RS within the threshold range. The default spatial QCL assumption can be the same as the core resource set (CORESET) that triggers the CSI-RS. Or it can be the same as the lowest CORESET in the latest time slot. For those CSI-RS outside the threshold range, the UE can perform UE Rx beam scanning. In other words, the spatial QCL assumption can be determined separately for each symbol carrying CSI-RS, for example, if the offset between the DCI and a symbol carrying CSI-RS is less than a threshold, the default spatial QCL assumption can be applied.

[0082] CSI-RS-ResourceRep is set to OFF

[0083] Fig. 9 Depicts an example of a spatial QCL assumption of repeated OFF in accordance with some embodiments.

[0084] When CSI-RS-ResourceRep is set to 'OFF', it means that the gNB can perform Tx beam scanning to refine the Tx beam and the UE can maintain the same UE Rx beam. In this case, if the offset between DCI and CSI-RS is less than a certain threshold, the UE can maintain the default spatial QCL assumption for all triggered CSI-RS resources.

[0085] In various embodiments, if CSI-RS-ResourceRep is set to 'OFF' and the scheduling offset between DCI and CSI-RS is less than a certain threshold, the UE may apply a default spatial QCL assumption for all triggered CSI-RS. The default spatial QCL assumption may be the same as the CORESET of the triggered CSI-RS. Or it may be the same as the lowest CORESET in the latest slot.

[0086] 2. CSI-RS triggering of CSI

[0087] For CSI measurement, it is expected that the UE uses the same Rx beam for channel measurement and interference measurement. However, CMR and IMR may not exist in the same time slot. In this case, if the same Rx beam cannot be guaranteed for CMR and IMR, the measurement can be discarded. For example, if IMR is FDMed with PDSCH, the UE can use the same beam as PDSCH for IMR.

[0088] In various embodiments, for CSI measurement, if the same UE Rx beam for CMR and IMR cannot be guaranteed, the CSI measurement may be discarded.

[0089] 3. Simultaneous CSI-RS and PDSCH

[0090] If CSI-RS is multiplexed with PDSCH, the spatial QCL hypothesis may be determined according to the multiplexing scheme (eg, time division multiplexed (TDMed) or frequency division multiplexed (FDMed)).

[0091] FDMed CSI-RS and PDSCH

[0092] If FDM is performed on CSI-RS with PDSCH, the same UE Rx beam can be applied to PDSCH and CSI-RS. Since PDSCH reception is more important, the QCL assumption of CSI-RS can follow the QCL assumption of PDSCH regardless of whether the offset between the triggering DCI and CSI-RS is greater than a certain threshold.

[0093] Fig.10 An example of frequency division multiplexed (FDMed) CSI-RS and PDSCH is depicted in accordance with some embodiments.

[0094] In various embodiments, if FDM is performed on CSI-RS using PDSCH, the spatial QCL assumption of CSI-RS can follow the QCL assumption of PDSCH reception regardless of whether the offset between the triggering DCI and CSI-RS is greater than a certain threshold. Even if CSI-RS is configured with a QCL configuration, it can be overwritten by the QCL configuration of PDSCH.

[0095] TDMed CSI-RS and PDSCH

[0096] If TDM is performed on CSI-RS using PDSCH, the spatial QCL of CSI-RS is assumed to reach the offset between triggering DCI and CSI-RS.

[0097] Fig.11 An example of time division multiplexed (TDMed) CSI-RS and PDSCH is depicted in accordance with some embodiments.

[0098] In various embodiments, for TDMed CSI-RS and PDSCH, if the offset between the triggering DCI and the CSI-RS is less than a certain threshold, a default spatial QCL assumption may be applied to the CSI-RS. The default spatial QCL assumption may follow the QCL assumption received for the PDSCH. Alternatively, the default spatial QCL assumption may be the QCL assumption of the triggering DCI, or the QCL assumption of the lowest CORESET ID in the latest slot. If the offset between the triggering DCI and the CSI-RS is greater than a certain threshold, the UE may follow the QCL configuration as indicated.

[0099] Prioritized CSI-RS

[0100] In some cases, if the triggering offset of the CSI-RS is greater than a certain threshold, but the PDSCH scheduling offset is less than a certain threshold, it is determined that there are some conflicts in the spatial QCL assumptions of the CSI-RS and the PDSCH.

[0101] Fig.12 Depicted are examples of CSI-RS and possible PDSCH according to some embodiments.

[0102] like Fig.12 As shown, since the offset between the triggering DCI and the CSI-RS is greater than a certain threshold K, the CSI-RS is expected to use the spatial QCL assumption as indicated by the DCI as #1. In time slot N+2, there is a PDCCHCORESET monitoring with spatial QCL#2, on which there may be a DCI for PDSCH assignment. Due to the DCI decoding delay, the UE does not know whether there is an allocated PDSCH, and the UE does not know the exact starting point of the PDSCH until the DCI is decoded. Therefore, the UE can use the default spatial QCL assumption of #2 to keep monitoring and buffering the PDSCH. Then, in time slot N+5, there is some confusion about whether the spatial QCL assumption can be used for reception. If the UE follows the PDSCH default beam, that is, QCL#2, it means that the QCL assumption for CSI-RS reception can be covered. Since the UE does not know whether the PDSCH transmission actually occurs before the DCI is decoded, if there is no PDSCH transmission, it may cause missed detection of the CSI-RS after the PDSCH default beam. If the QCL assumption of CSI-RS is followed, it means that PDSCH reception can be discarded. So some rules may be defined.

[0103] In various embodiments, if the scheduling offset between the DCI and PDSCH transmission is less than a specific threshold, whether there is a CSI-RS in the time slot in which the UE buffers the PDSCH may be considered when determining the default spatial QCL assumption. If there is a CSI-RS with an indicated QCL assumption, that is, the offset between the DCI that triggers the CSI-RS and the CSI-RS transmission is greater than another specific threshold, the default PDSCH spatial QCL assumption may follow the indicated QCL assumption for CSI-RS reception. That is, in this case, CSI-RS reception is prioritized. Alternatively, PDSCH reception is prioritized, that is, for CSI-RS reception, the spatial QCL assumption of PDSCH or the default spatial QCL assumption of PDSCH may be applied, which means discarding the QCL assumption for CSI-RS indicated by the DCI.

[0104] In various embodiments, if the time offset between the CSI-RS and the DCI triggering the CSI-RS is greater than a specific threshold K determined for the CSI-RS default spatial QCL assumption, and the time offset between the starting point of the CSI-RS and the latest PDCCH CORESET listening opportunity is less than a specific threshold M determined for the PDSCH default spatial QCL assumption, the spatial QCL assumption for the CSI-RS indicated by the DCI may be discarded. Or if the time offset between the CSI-RS and the DCI triggering the CSI-RS is greater than a specific threshold K determined for the CSI-RS default spatial QCL assumption, and there are additional PDCCH CORESET listening opportunities between the CSI-RS and the CSI-RS triggered by the DCI, and the time offset between the starting point of the CSI-RS and the latest PDCCH CORESET listening opportunity is less than a specific threshold M determined for the PDSCH default spatial QCL assumption, the spatial QCL assumption for the CSI-RS indicated by the DCI may be discarded. The spatial QCL assumption CSI-RS may follow the QCL assumption of the PDSCH or the CORESET with the lowest ID in the latest slot.

[0105] In addition, in other embodiments, if TDM is used between CSI-RS and PDSCH and the offset between the triggering DCI and CSI-RS is greater than a certain threshold, the spatial QCL assumption indicated by the DCI can be applied for CSI-RS reception. For possible PDSCH reception, i.e., buffered PDSCH, the default spatial QCL assumption can be applied, which is the QCL assumption of the CORESET with the lowest ID in the latest slot.

[0106] In other embodiments, if FDM is used between CSI-RS and PDSCH, and the offset between the triggering DCI and CSI-RS is greater than a certain threshold, the QCL assumption indicated by the DCI may be applied for CSI-RS reception, and the same QCL assumption as that for CSI-RS may be used for possible PDSCH reception. Alternatively, the QCL assumption for CSI-RS reception may follow the QCL assumption for possible PDSCH reception.

[0107] In other embodiments, FDM between CSI-RS and PDSCH is not allowed.

[0108] In other embodiments, for CSI-RS triggering, the offset between DCI and CSI-RS may always be less than a certain threshold, and then a default spatial QCL assumption may be applied to CSI-RS reception, which is the QCL assumption of the triggered DCI or the QCL assumption of the CORESET with the lowest ID in the latest slot. Alternatively, when CSI-RS is triggered, it may be guaranteed that there are no other PDCCH CORESET listening opportunities between the triggered DCI and CSI-RS transmission.

[0109] In other embodiments, the UE will expect the gNB to schedule PDSCH with a scheduling offset above the threshold it reports when configuring one or more CCs. In the absence of such a restriction, the UE may always use the default Rx beam to receive each symbol that may be allocated for PDSCH transmission, where the default Rx beam for different CCs may be different as it is determined by the CORESET configuration of each CC. Alternatively, in the absence of a beam indication, the UE will use the default Rx beam from the PCell to receive all possible symbols of the PDSCH.

[0110] Note that the embodiments herein may be applied to NZP CSI-RS, ZP CSI-RS, and CSI-IM.

[0111] 4. CSI-RS and PDSCH at different times

[0112] If CSI-RS is not multiplexed with PDSCH, for example, pre-scheduled CSI-RS, the spatial QCL of the CSI-RS is assumed to reach the offset between the triggering DCI and the CSI-RS. If the offset is greater than a certain threshold, the QCL configuration indicated by the DCI can be applied. Otherwise, the default spatial QCL can be applied.

[0113] In various embodiments, if CSI-RS is not multiplexed with PDSCH and the offset between the triggering DCI and CSI-RS is less than a certain threshold, a default spatial QCL assumption may be applied to the CSI-RS. The default spatial QCL assumption may be the QCL assumption of the triggering DCI or the QCL assumption of the lowest CORESET ID in the latest slot.

[0114] Fig.13 An example of a method performed by a user equipment (UE) for triggering a QCL indication of an aperiodic CSI-RS according to some embodiments is depicted.

[0115] At 1302, the UE may receive and decode an aperiodic channel state information reference signal (CSI-RS) for beam management from a BS (e.g., gNB) on a PDSCH. The CSI-RS may be used for channel quality indicator (CQI) measurement, precoding matrix indicator (PMI) measurement, rank indicator (RI) measurement, or time and frequency offset tracking.

[0116] At 1304, the UE may determine a spatial quasi-co-location (QCL) assumption of the CSI-RS based on a scheduling offset between triggering downlink control information (DCI) for triggering the CSI-RS and the CSI-RS. In some embodiments, the CSI-RS is configured with a parameter CSI-RS-ResourceRep to indicate repetition of a Tx beam from a BS (e.g., gNB).

[0117] In some embodiments, when CSI-RS-ResourceRep indicates a repeated Tx beam (CSI-RS-ResourceRep is set to ON) and the scheduling offset is less than the threshold of the CSI-RS, the default spatial QCL assumption is applied to the CSI-RS within the threshold range, and UE Rx beam scanning is performed for the CSI-RS outside the threshold range.

[0118] In some embodiments, when CSI-RS-ResourceRep indicates no repeated Tx beam (CSI-RS-ResourceRep is set to OFF) and the scheduling offset is less than the threshold of CSI-RS, the default spatial QCL assumption is applied to all triggered CSI-RS. In some embodiments, the default spatial QCL assumption is the same as the control resource set (CORESET) of the triggered CSI-RS or the lowest CORESET in the latest slot.

[0119] In another embodiment, if the same UE Rx beam is not guaranteed for the channel measurement resources (CMR) and interference measurement resources (IMR) that do not exist in the same time slot, the CSI measurement is discarded.

[0120] In some embodiments, if the CSI-RS is frequency division multiplexed (FDM) with a physical downlink shared channel (PDSCH), the spatial QCL assumption of the CSI-RS follows the QCL assumption for PDSCH reception.

[0121] In some embodiments, if the CSI-RS is time division multiplexed (TDM) using a physical downlink shared channel (PDSCH), when the scheduling offset is less than a threshold, the default spatial QCL assumption of the CSI-RS is applied, and the spatial QCL assumption of the CSI-RS follows the QCL configuration indicated by the DCI.

[0122] In some embodiments, the default spatial QCL assumption for CSI-RS follows the QCL assumption used for PDSCH reception, or is the QCL assumption of the triggered DCI or the QCL assumption of the lowest CORESET ID in the latest slot.

[0123] In some embodiments, if the scheduling offset between the triggered DCI and CSI-RS is greater than the threshold of the CSI-RS and the scheduling offset between the DCI and the PDSCH is less than the threshold of the PDSCH, the default spatial QCL assumption of the CSI-RS follows the QCL assumption for CSI-RS reception indicated by the DCI, or the QCL assumption for the CSI-RS indicated by the DCI is discarded.

[0124] In some embodiments, if the scheduling offset between the triggering DCI and the CSI-RS is greater than a threshold of the CSI-RS, and the time offset between the starting point of the CSI-RS and the latest physical downlink control channel (PDCCH) CORESET monitoring opportunity is less than a threshold determined for the PDSCH default spatial QCL assumption, the spatial QCL assumption of the CSI-RS indicated by the DCI is discarded.

[0125] In some embodiments, if the scheduling offset between the triggering DCI and the CSI-RS is greater than a threshold of the CSI-RS, and there is an additional latest physical downlink control channel (PDCCH) CORESET monitoring opportunity between the CSI-RS and the triggering DCI, and the time offset between the starting point of the CSI-RS and the latest PDCCH CORESET monitoring opportunity is less than a threshold determined for the PDSCH default spatial QCL assumption, the spatial QCL assumption of the CSI-RS indicated by the DCI is discarded, and the spatial QCL assumption follows the QCL assumption of the CORESET with the lowest CORESET ID in the PDSCH or the latest time slot.

[0126] In some embodiments, if TDM is performed on CSI-RS using PDSCH and the scheduling offset between the triggering DCI and CSI-RS is greater than the threshold of CSI-RS, the spatial QCL assumption indicated by the DCI is applied to CSI-RS reception and the default spatial QCL assumption is applied to PDSCH reception.

[0127] In some embodiments, the default spatial QCL hypothesis is the QCL hypothesis of the CORESET with the lowest CORESET ID in the latest time slot.

[0128] In some embodiments, if FDM is performed on CSI-RS using PDSCH and the scheduling offset between the triggering DCI and CSI-RS is greater than a threshold for CSI-RS, the spatial QCL assumption indicated by the DCI is applied to CSI-RS reception, and the same spatial QCL assumption is applied to possible PDSCH reception.

[0129] In some embodiments, if CSI-RS is FDMed with PDSCH and the scheduling offset between triggering DCI and CSI-RS is greater than a threshold for CSI-RS, the spatial QCL assumption for CSI-RS follows the QCL assumption for possible PDSCH reception.

[0130] In some embodiments, FDM between CSI-RS and PDSCH is not allowed.

[0131] In some embodiments, the scheduling offset between the triggering DCI and the CSI-RS is set to be less than a certain threshold, and the default spatial QCL assumption is applied to CSI-RS reception.

[0132] In some embodiments, the default spatial QCL assumption is the QCL assumption that triggered the DCI or the QCL assumption of the CORESET with the lowest CORESET ID in the latest slot.

[0133] In some embodiments, when CSI-RS is triggered, there are no other PDCCH CORESET listening opportunities between triggering DCI and CSI-RS.

[0134] In some embodiments, the BS is configured to schedule the PDSCH with a scheduling offset higher than a threshold reported by the UE when one or more component carriers (CCs) are configured.

[0135] In some embodiments, the UE is configured to use a default Rx beam to receive each symbol that may be allocated to a PDSCH transmission.

[0136] In some embodiments, the UE is configured to receive all possible symbols of the PDSCH using a default Rx beam from a primary cell (PCell) without beam indication.

[0137] In some embodiments, if CSI-RS is not multiplexed with PDSCH and the scheduling offset between the triggering DCI and CSI-RS is less than a threshold of CSI-RS, a default spatial QCL assumption is applied to CSI-RS.

[0138] In some embodiments, the default spatial QCL assumption is the QCL assumption that triggered the DCI or the QCL assumption of the CORESET with the lowest CORESET ID in the latest slot.

[0139] At 1306, the UE may send the determined QCL assumption or information to a BS (e.g., gNB) on a physical uplink shared channel (PUSCH).

[0140] Note that the embodiments of the present invention can be applied to scenarios with multiple BWPs / CCs. In other words, the spatial QCL assumption can be determined by the active BWP or CC with PDSCH transmission.

[0141] Beam management

[0142] Beam management may refer to a set of L1 / L2 processes for acquiring and maintaining a set of TRPs and / or UE beams that can be used for downlink (DL) and uplink (UL) transmission / reception, which may include: beam determination, which may refer to the ability of TRxP or UE to select its own transmit (Tx) / receive (Rx) beam; beam measurement, which may refer to the ability of a transmit / receive point (TRP or TRxP) or UE to measure the characteristics of a received beamforming signal; beam reporting, which may refer to the ability of a UE to report information about a beamforming signal based on beam measurement; and beam scanning, which may refer to the operation of covering a spatial area in a predetermined manner with beams transmitted and / or received during a time interval.

[0143] The Tx / Rx beam correspondence at the TRxP holds if at least one of the following conditions is satisfied: The TRxP can determine the TRxP Rx beam for uplink reception based on the downlink measurements of one or more Tx beams of the TRxP by the UE; and the TRxP can determine the TRxP Tx beam for downlink transmission based on the uplink measurements of one or more Rx beams of the TRxP by the TRxP. The Tx / Rx beam correspondence at the UE holds if at least one of the following is satisfied: The UE can determine the UE Tx beam for uplink transmission based on the downlink measurements of one or more Rx beams of the UE by the UE; the UE can determine the UE Rx beam for downlink reception according to the indication of the TRxP based on the uplink measurements of one or more Tx beams of the UE; and the ability indication of supporting UE beam correspondence related information to the TRxP.

[0144] In some implementations, DL beam management may include procedures P-1, P-2, and P-3. Procedure P-1 can be used to enable the UE to measure different TRxP Tx beams to support the selection of the TRxP Tx beam / UE Rx beam. For beamforming at the TRxP, procedure P-1 generally includes intra-TRxP / inter-TRxP Tx beam scanning from a set of different beams. For beamforming at the UE, procedure P-1 generally includes UE Rx beam scanning from a set of different beams.

[0145] Procedure P-2 can be used to enable the UE to perform UE measurements on different TRxP Tx beams to possibly change the inter-TRxP / TRP-intra Tx beam. Procedure P-2 can be a special case of procedure P-1, where procedure P-2 can be used for a possibly smaller set of beams for beam refinement compared to procedure P-1. In the case where the UE uses beamforming, procedure P-3 can be used to enable the UE to measure the same TRxP Tx beam to change the UE Rx beam. Procedures P-1, P-2, and P-3 can be used for aperiodic beam reporting.

[0146] The RS-based UE measurement (at least CSI-RS) for beam management consists of K beams (where K is the total number of configured beams), and the UE can report the measurement results of N selected Tx beams (where N may or may not be a fixed number). The RS-based procedure for mobility purposes is not excluded. If N < K, the beam information to be reported may include the measurements of N beams and the information indicating N DL Tx beams. Other information or data may be included in or included together with the beam information. When the UE is configured with K'> 1 non-zero power (NZP) CSI-RS resources, the UE can report N' CSI-RS resource indicators (CRIs).

[0147] In some NR implementations, the UE may trigger a mechanism for recovering from a beam failure, which may be referred to as "beam recovery", "beam failure recovery request procedure", etc. A beam failure event may occur when the quality of the beam-pair link of the associated control channel drops below a threshold, when an associated timer times out, etc. The beam recovery mechanism may be triggered when a beam failure occurs. The network may explicitly configure resources for UL transmission signals for the UE for recovery purposes. Configuration of resources is supported where a base station (e.g., TRP, gNB, etc.) is listening from all or some directions (e.g., random access area). The UL transmission / resource for reporting a beam failure may be located in the same time instance as the physical random access channel (PRACH) or resources orthogonal to the PRACH resources, or at a different (UE-configurable) time instance than the PRACH. Transmission of DL signals is supported to allow the UE to listen to beams for identifying new potential beams.

[0148] For beam failure recovery, a beam failure may be declared if all serving PDCCH beams fail. When a beam failure is declared, a beam failure recovery request procedure may be initiated. For example, the beam failure recovery request procedure may be used to indicate a new SSB or CSI-RS to the serving gNB (or TRP) when a beam failure is detected on the serving SSB / CSI-RS. Beam failure may be detected by lower layers and indicated to the medium access control (MAC) entity of the UE.

[0149] In some implementations, beam management may include providing or not providing beam-related indications. When beam-related indications are provided, information related to the UE-side beamforming / reception process for CSI-RS based measurements may be indicated to the UE via QCL. The same or different beams on the control channel and the corresponding data channel transmissions may be supported.

[0150] Downlink (DL) beam indication can be based on a transmission configuration indication (TCI) state. The TCI state can be indicated in a TCI list configured by a radio resource control (RRC) and / or a medium access control (MAC) control element (CE). In some implementations, the UE can configure up to M TCI states through higher layer signaling to decode the PDSCH based on a detected PDCCH with downlink control information (DCI) for the UE and a given serving cell, where M depends on the UE capability. Each configured TCI state includes a reference signal (RS) set TCI-RS-SetConfig. Each TCI-RS-SetConfig may include parameters for configuring a quasi-co-location relationship between the RS in the RS set and the demodulation reference signal (DM-RS) port group of the PDSCH. The RS set may include a reference to one or two DL RSs and an associated quasi-co-location type (QCL type) for each DL RS configured by a higher layer parameter QCL-Type. For the case of two DL RSs, the QCL type should be different, regardless of whether the reference is to the same DL RS or different DL RSs. The quasi-colocation type indicated to the UE is based on the higher layer parameter QCL-Type and can adopt one or a combination of the following types: QCL-TypeA: {Doppler shift, Doppler spread, average delay, delay spread} QCL-TypeB: {Doppler shift, Doppler spread} QCL-TypeC: {average delay, Doppler shift} QCL-TypeD: {spatial Rx parameters}.

[0151] The UE may receive a selection command (e.g., in a MAC CE) that may be used to map up to 8 TCI states to code points of the DCI field TCI state. Until the UE receives a higher layer configuration of the TCI state and before receiving an activation command, the UE may assume that the antenna ports of one DM-RS port group of the PDSCH of the serving cell are spatially quasi-co-located at the SSB determined during the initial access process. When the number of TCI states in the TCI state is less than or equal to 8, the DCI field TCI state directly indicates the TCI state.

[0152] The beam failure recovery request may be delivered via a dedicated PRACH or physical uplink control channel (PUCCH) resource. For example, the UE may configure the serving cell with a set of Periodic CSI-RS resource configuration index, and through the higher layer parameter Candidate-Beam-RS-List configuration as a group CSI-RS resource configuration index and / or SS / PBCH block index for radio link quality measurement on the serving cell. If no configuration is present, beam failure detection may be based on CSI-RS or SSB that is quasi-collocated (QCLed) with the PDCCH demodulation reference signal (DMRS). For example, if the UE is not provided with the higher layer parameter Beam-Failure-Detection-RS-ResourceConfig, the UE may determine The CSI-RS is configured with a higher layer parameter TCI-StatesPDCCH with the same value as the SS / PBCH block and periodicity as the value of the control resource set (CORESET) that the UE is configured to monitor the PDCCH.

[0153] The physical layer of the UE can be based on a set of Resource allocation for threshold Q out,LR To evaluate the quality of the radio link. out,LR Corresponding to the default values ​​of the higher layer parameters RLM-IS-OOS-thresholdConfig and Beam-failure-candidate-beam-threshold, respectively. The UE can evaluate the radio link quality based only on the periodic CSI-RS resource configuration or SS / PBCH block that is quasi-colocated with the DM-RS of the PDCCH reception DM-RS monitored by the UE. in,LR The threshold is applied to the periodic CSI-RS resource configuration. After scaling the SS / PBCH block transmit power with the value provided by the higher layer parameter Pc_SS, the UE sets Q out,LR The threshold is based on the SS / PBCH block.

[0154] In some implementations, if the MAC entity has received a beam failure indication from a lower layer, the MAC entity may start a beam failure recovery timer (beamFailureRecoveryTimer) and initiate a random access process. If the beamFailureRecoveryTimer expires, the MAC entity may indicate to the upper layer that the beam failure recovery request failed. If a downlink assignment or uplink approval is received (e.g., on a PDCCH addressed to a cell radio network temporary identifier (C-RNTI)), the MAC entity may stop and reset the beamFailureRecoveryTimer and consider the beam failure recovery request process to be successfully completed.

[0155] Beam Measurement

[0156] In an embodiment, a UE (e.g., in RRC_CONNECTED mode) may measure multiple beams (at least one) of a cell and average the measurements (power values) to derive cell quality. The UE may be configured to consider a subset of detected beams, such as the N best beams above an absolute threshold. Filtering may be performed at two different levels, including at the physical layer (PHY) to derive beam quality and then at the RRC level to derive cell quality from multiple beams. Cell quality from beam measurements may be derived in the same manner for serving and non-serving cells. If the UE is configured to do so by the gNB, the measurement report may contain measurement results for the X best beams. For channel state estimation purposes, the UE may be configured to measure CSI-RS resources and estimate the downlink channel state based on the CSI-RS measurements. The UE may feed back the estimated channel state to the gNB for link adaptation.

[0157] Fig.14 An exemplary measurement model is shown. Fig.14 In the example, point A may include measurements internal to the PHY (e.g., beam specific samples). Layer 1 (L1) filtering may include internal layer 1 filtering circuitry to filter the input measured at point A. The exact filtering mechanism and how the measurements are actually performed at the PHY may be implementation specific. L1 filtering may be provided to point 3 (L3) beam filtering circuitry and point A. 1 The beam combining / selection circuit at the location reports measurements (e.g., beam-specific measurements).

[0158] The beam combining / selection circuitry may include circuitry to combine beam specific measurements to derive cell quality. For example, if N>1, otherwise when N=1, the best beam measurement may be selected to derive cell quality. The configuration of the beams may be provided via RRC signaling. The measurements (e.g., cell quality) derived from the beam specific measurements after beam combining / selection may then be reported to the L3 filtering for cell quality circuitry. In some embodiments, the reporting period at point B may be equal to that at point A. 1 A measurement period at .

[0159] L3 filtering for the cell quality circuit may be configured to filter the measurements provided at point B. Configuration of the layer 3 filter may be provided by RRC signaling as described above or by different / separate RRC signaling. In some embodiments, the filtered reporting period at point C may be equal to one measurement period at point B. The measurement after processing in the layer 3 filter circuit may be provided to the evaluation of the reporting criteria circuit at point C. In some embodiments, the reporting rate may be the same as the reporting rate at point B. The measurement input may be used for one or more evaluations of the reporting criteria.

[0160] The evaluation of the reporting criteria circuit may be configured to check whether an actual measurement report is required at point D. The evaluation may be based on more than one measurement stream at a reference point C. In one example, the evaluation may involve a comparison between different measurements, such as a measurement provided at point C and a measurement provided at point C. 1 In an embodiment, the UE may provide another measurement at points C, C 1 The reporting criteria are evaluated when reporting new measurement results at point D. The reporting criteria configuration may be provided by the above RRC signaling (UE measurement) or by different / separate RRC signaling. After the evaluation, the measurement report information may be sent on the radio interface at point D (e.g., as a message).

[0161] Refer to point A again 1 , at point A 1 The measurements provided at point E may be provided to L3 beam filtering circuitry, which may be configured to perform beam filtering of the provided measurements (e.g., beam specific measurements). The configuration of the beam filter may be provided via the RRC signaling described above or via different / separate RRC signaling. In an embodiment, the filtered reporting period at point E may be equal to the period at point A. 1 The K beams may correspond to measurements of New Radio (NR)-Synchronization Signal (SS) Block (SSB) or Channel State Information Reference Signal (CSI-RS) resources configured by the gNB for L3 mobility and detected by the UE at L1.

[0162] After processing in the beam filter measurement (e.g., beam specific measurement), a measurement may be provided to the beam selection of the reporting circuit at point E. This measurement may be used as an input for selecting the X measurement to report. In an embodiment, the reporting rate may be similar to that at point A. 1 The beam selection for the beam reporting circuit may be configured to select X measurements from the measurements provided at point E. The configuration of this module may be provided by the RRC signaling described above or by different / separate RRC signaling. The beam measurement information to be included in the measurement report may be sent or scheduled for transmission on the radio interface at point F.

[0163] The measurement report may include a measurement identifier of the associated measurement configuration that triggered the report. The measurement report may include cell and beam measurement quantities to be included in the measurement report configured by the network (e.g., using RRC signaling). The measurement report may include the number of non-service cells to be reported, which may be limited by the configuration of the network. Cells belonging to a blacklist configured by the network may not be used for event evaluation and reporting. Conversely, when the network configures a whitelist, only cells belonging to the whitelist may be used for event evaluation and reporting. The beam measurements to be included in the measurement report may be configured by the network, and such a measurement report may include or indicate only a beam identifier, include or indicate measurement results and a beam identifier, or include or indicate a beam report.

[0164] Fig.15 The architecture of a system 1500 of a network according to some embodiments is shown. System 1500 is shown to include user equipment (UE) 1501 and UE 1502. UE 1501 and 1502 are shown as smart phones (e.g., handheld touch-screen mobile computing devices that can connect to one or more cellular networks), but may also include any mobile or non-mobile computing devices, such as personal data assistants (PDAs), pagers, laptop computers, desktop computers, wireless handheld devices, or any computing device that includes a wireless communication interface.

[0165] In some embodiments, any one of UE 1501 and 1502 may include an Internet of Things (IoT) UE, which may include a network access layer designed for low-power IoT applications that utilize short-term UE connections. The IoT UE may utilize technologies such as machine-to-machine (M2M) or machine-type communication (MTC) to exchange data with an MTC server or device via a public land mobile network (PLMN), proximity-based services (ProSe) or device-to-device (D2D) communication, a sensor network, or an IoT network. The M2M or MTC data exchange may be a machine-initiated data exchange. The IoT network describes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with short-term connections. The IoT UE may execute background applications (e.g., keep valid messages, status updates, etc.) to facilitate connectivity to the IoT network.

[0166] UEs 1501 and 1502 may be configured to connect (e.g., be communicatively coupled) to a radio access network (RAN) 1510, which may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a NextGenRAN (NG RAN), or some other type of RAN. UEs 1501 and 1502 use connections 1503 and 1504, respectively, each of which includes a physical communication interface or layer (discussed in further detail below); in this example, connections 1503 and 1504 are shown as air interfaces to achieve communicatively coupling, and may conform to a cellular communication protocol, such as a Global System for Mobile Communications (GSM) protocol, a Code Division Multiple Access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a Cellular PTT (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, a Fifth Generation (5G) protocol, a New Radio (NR) protocol, etc.

[0167] In this embodiment, UE 1501 and 1502 may also directly exchange communication data via ProSe interface 1505. Optionally, ProSe interface 1505 may be referred to as a sidelink interface including one or more logical channels, including but not limited to a physical sidelink control channel (PSCCH), a physical sidelink shared channel (PSSCH), a physical sidelink discovery channel (PSDCH), and a physical sidelink broadcast channel (PSBCH).

[0168] UE 1502 is shown as being configured to access access point (AP) 1506 via connection 1507. Connection 1507 may include a local wireless connection, such as a connection compliant with any IEEE 802.11 protocol, wherein AP 1506 would include wireless fidelity In this example, AP 1506 is shown connected to the Internet and not to the core network of the wireless system (described in further detail below).

[0169] The RAN 1510 may include one or more access nodes that implement connections 1503 and 1504. These access nodes (ANs) may be referred to as base stations (BS), NodeBs, evolved NodeBs (eNBs), next generation NodeBs (gNBs), RAN nodes, etc., and may include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). The RAN 1510 may include one or more RAN nodes (e.g., macro RAN nodes 1511) for providing macro cells and one or more RAN nodes (e.g., low power (LP) RAN nodes 1512) for providing femto cells or pico cells (e.g., cells with smaller coverage areas, smaller user capacity, or higher bandwidth than macro cells).

[0170] Any of the RAN nodes 1511 and 1512 may terminate the air interface protocol and may be the first point of contact for the UEs 1501 and 1502. In some embodiments, any of the RAN nodes 1511 and 1512 may fulfill various logical functions, where the RAN 1510 includes but is not limited to Radio Network Controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling and mobility management.

[0171] According to some embodiments, according to various communication technologies, such as but not limited to Orthogonal Frequency Division Multiple Access (OFDMA) communication technology (e.g., for downlink communication) or Single Carrier Frequency Division Multiple Access (SC-FDMA) communication technology (e.g., for uplink and ProSe or sidelink communication), UEs 1501 and 1502 may be configured to communicate with each other using Orthogonal Frequency Division Multiplexing (OFDM) communication signals or communicate with any one of RAN nodes 1511 and 1512 through a multi-carrier communication channel, but the scope of the embodiment is not limited thereto. The OFDM signal may include multiple orthogonal subcarriers.

[0172] In some embodiments, a downlink resource grid may be used for downlink transmissions from any of the RAN nodes 1511 and 1512 to the UEs 1501 and 1502, while similar techniques may be used for uplink transmissions. The grid may be a time-frequency grid, referred to as a resource grid or a time-frequency resource grid, which is a physical resource in the downlink in each time slot. This time-frequency plane representation is a common practice in OFDM systems, which makes radio resource allocation intuitive. Each column and each row of the resource grid corresponds to an OFDM symbol and an OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to a time slot in a radio frame. The smallest time-frequency unit in the resource grid is represented as a resource element. Each resource grid includes a plurality of resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block includes a set of resource elements in the frequency domain, which may represent the minimum quantum of resources that may currently be allocated. There are several different physical downlink channels conveyed using such resource blocks.

[0173] The physical downlink shared channel (PDSCH) may carry user data and higher layer signaling to the UEs 1501 and 1502. The physical downlink control channel (PDCCH) may carry, among other things, information about the transport format and resource allocation associated with the PDSCH channel. It may also inform the UEs 1501 and 1502 of the transport format, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request) information associated with the uplink shared channel. Typically, downlink scheduling (assignment of control and shared channel resource blocks to the UEs 1502 within the cell) may be performed at any of the RAN nodes 1511 and 1512 based on channel quality information fed back from any of the UEs 1501 and 102. Downlink resource assignment information may be sent on the PDCCH for (e.g., assigned to) each of the UEs 1501 and 1502.

[0174] PDCCH can use control channel elements (CCE) to transmit control information. Before mapping to resource elements, PDCCH complex symbols can first be organized into quadruplets, which can then be permuted using a sub-block interleaver for rate matching. Each PDCCH can be transmitted using one or more of these CCEs, where each CCE can correspond to nine sets of four physical resource elements called resource element groups (REGs). Four quadrature phase shift keying (QPSK) symbols can be mapped to each REG. Depending on the size of the downlink control information (DCI) and the channel conditions, one or more CCEs can be used to transmit the PDCCH. Four or more different PDCCH formats can be defined in LTE, with different numbers of CCEs (e.g., aggregation levels, L=1, 2, 4, or 8).

[0175] Some embodiments may use the concept of resource allocation for control channel information, which is an extension of the above concept. For example, some embodiments may use an enhanced physical downlink control channel (EPDCCH), which uses PDSCH resources to transmit control information. One or more enhanced control channel elements (ECCEs) may be used to transmit EPDCCH. Similar to the above, each ECCE may correspond to nine sets of four physical resource elements called enhanced resource element groups (EREGs). In some cases, ECCEs may have other numbers of EREGs.

[0176] RAN 1510 is shown as being communicatively coupled to a core network (CN) 1520 via an S1 interface 1513. In an embodiment, CN 1520 may be an Evolved Packet Core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN. In this embodiment, S1 interface 1513 is divided into two parts: S1-U interface 1514, which carries traffic data between RAN nodes 1511 and 1512 and a Serving Gateway (S-GW) 1522; and S1-Mobility Management Entity (MME) interface 1515, which is a signaling interface between RAN nodes 1511 and 1512 and MME 1521.

[0177] In this embodiment, CN 1520 includes MME 1521, S-GW 1522, Packet Data Network (PDN) Gateway (P-GW) 1523 and Home Subscriber Server (HSS) 1524. MME 1521 can be similar in function to the control plane of a conventional Serving General Packet Radio Service (GPRS) Support Node (SGSN). MME 1521 can manage mobility aspects in access, such as gateway selection and tracking area list management. HSS 1524 can include a database of network users, including subscription-related information for supporting network entities to handle communication sessions. CN 1520 can include one or several HSS 1524, depending on the number of mobile subscribers, the capacity of the equipment, the organization of the network, etc. For example, HSS 1524 can provide support for routing / roaming, authentication, authorization, naming / addressing solutions, location dependencies, etc.

[0178] The S-GW 1522 may terminate the S1 interface 1513 towards the RAN 1510 and route data packets between the RAN 1510 and the CN 1520. In addition, the S-GW 1522 may be a local mobility anchor for handovers between RAN nodes and may also provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful interception, charging, and some policy enforcement.

[0179] The P-GW 1523 may terminate the SGi interface toward the PDN. The P-GW 1523 may route data packets between the EPC network 1523 and an external network (e.g., a network including an application server 1530 (alternatively referred to as an application function (AF))) via an Internet Protocol (IP) interface 1525. Typically, the application server 1530 may be an element that provides applications that use IP bearer resources with a core network (e.g., a UMTS packet service (PS) domain, a LTE PS data service, etc.). In this embodiment, the P-GW 1523 is shown as being communicatively coupled to the application server 1530 via an IP communication interface 1525. The application server 1530 may also be configured to support one or more communication services (e.g., Voice over Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for UEs 1501 and 1502 via CN 1520.

[0180] The P-GW 1523 may also be a node for policy enforcement and charging data collection. The policy and charging enforcement function (PCRF) 1526 is a policy and charging control element of the CN 1520. In a non-roaming scenario, a single PCRF may exist in a home public land mobile network (HPLMN) associated with an Internet Protocol Connectivity Access Network (IP-CAN) session of the UE. In a roaming scenario with local traffic divergence, two PCRFs may be associated with the UE's IP-CAN session: a home PCRF (H-PCRF) within the HPLMN and a visited PCRF (V-PCRF) within a visited public land mobile network (VPLMN). The PCRF 1526 may be communicatively coupled to the application server 1530 via the P-GW 1523. The application server 1530 may signal the PCRF 1526 to indicate a new service flow and select appropriate quality of service (QoS) and charging parameters. PCRF 1526 may provide the rules to a Policy and Charging Enforcement Function (PCEF) (not shown) with the appropriate Traffic Flow Template (TFT) and QoS Class Identifier (QCI), which initiates the QoS and charging specified by the Application Server 1530 .

[0181] Fig.16Example components of a device 1600 according to some embodiments are shown. In some embodiments, the device 1600 may include an application circuit 1602, a baseband circuit 1604, a radio frequency (RF) circuit 1606, a front end module (FEM) circuit 1608, one or more antennas 1610, and a power management circuit (PCM) 1612, coupled together at least as shown. The components of the device 1600 shown may be included in a UE or a RAN node. In some embodiments, the device 1600 may include fewer elements (e.g., the RAN node may not use the application circuit 1602, but instead include a processor / controller to process IP data received from the EPC). In some embodiments, the device 1600 may include additional elements, such as, for example, memory / storage, a display, a camera, a sensor, or an input / output (I / O) interface. In other embodiments, the components described below may be included in more than one device (e.g., the circuit may be included separately in more than one device for a cloud-RAN (C-RAN) implementation).

[0182] The application circuit 1602 may include one or more application processors. For example, the application circuit 1602 may include circuits such as, but not limited to, one or more single-core processors or multi-core processors. The processor may include any combination of a general-purpose processor and a special-purpose processor (e.g., a graphics processor, an application processor, etc.). The processor may be coupled to or may include a memory / storage, and may be configured to: execute instructions stored in the memory / storage to enable various applications or operating systems to run on the device 1600. In some embodiments, the processor of the application circuit 1602 may process IP data packets received from the EPC.

[0183] The baseband circuit 1604 may include circuits such as, but not limited to, one or more single-core processors or multi-core processors. The baseband circuit 1604 may include one or more baseband processors or control logic to process baseband signals received from the receive signal path of the RF circuit 1606 and generate baseband signals for the transmit signal path of the RF circuit 1606. The baseband circuit 1604 may be connected to the application circuit 1602 for generating and processing baseband signals and controlling the operation of the RF circuit 1606. For example, in some embodiments, the baseband circuit 1604 may include a third generation (3G) baseband processor 1604A, a fourth generation (4G) baseband processor 1604B, a fifth generation (5G) baseband processor 1604C, or other baseband processors 1604D for other existing generations, generations under development, or generations to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.). The baseband circuitry 1604 (e.g., one or more of the baseband processors 1604A-D) may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry 1606. In other embodiments, some or all of the functions of the baseband processors 1604A-D may be included in a module stored in the memory 1604G and executed via the central processing unit (CPU) 1604E. The wireless control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency offset, etc. In some embodiments, the modulation / demodulation circuitry of the baseband circuitry 1604 may include fast Fourier transform (FFT), precoding, or constellation mapping / demapping functions. In some embodiments, the encoding / decoding circuitry of the baseband circuitry 1604 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity check (LDPC) encoder / decoder functions. The embodiments of the modulation / demodulation and encoder / decoder functions are not limited to these examples, and may include other suitable functions in other embodiments.

[0184] In some embodiments, the baseband circuit 1604 may include one or more audio digital signal processors (DSPs) 1604F. The audio DSP 1604F may include elements for compression / decompression and echo cancellation, and may include other suitable processing elements in other embodiments. In some embodiments, the components of the baseband circuit may be appropriately combined in a single chip, a single chipset, or be arranged on the same circuit board. In some embodiments, some or all of the constituent components of the baseband circuit 1604 and the application circuit 1602 may be implemented together, such as, for example, implemented on a system on a chip (SOC).

[0185] In some embodiments, baseband circuitry 1604 may provide communications compatible with one or more radio technologies. For example, in some embodiments, baseband circuitry 1604 may support communications with an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) or other wireless metropolitan area network (WMAN), wireless local area network (WLAN), or wireless personal area network (WPAN). Embodiments in which baseband circuitry 1604 is configured to support wireless communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

[0186] RF circuit 1606 can enable communication with a wireless network using modulated electromagnetic radiation through a non-solid medium. In various embodiments, RF circuit 1606 may include switches, filters, amplifiers, etc. to facilitate communication with a wireless network. RF circuit 1606 may include a receive signal path, which may include circuits for down-converting RF signals received from FEM circuit 1608 and providing baseband signals to baseband circuit 1604. RF circuit 1606 may also include a transmit signal path, which may include circuits for up-converting baseband signals provided by baseband circuit 1604 and providing RF output signals to FEM circuit 1608 for transmission.

[0187] In some embodiments, the receive signal path of the RF circuit 1606 may include a mixer circuit 1606a, an amplifier circuit 1606b, and a filter circuit 1606c. In some embodiments, the transmit signal path of the RF circuit 1606 may include a filter circuit 1606c and a mixer circuit 1606a. The RF circuit 1606 may also include a synthesizer circuit 1606d for synthesizing the frequencies used by the mixer circuit 1606a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuit 1606a of the receive signal path may be configured to down-convert the RF signal received from the FEM circuit 1608 based on the synthesized frequency provided by the synthesizer circuit 1606d. The amplifier circuit 1606b may be configured to amplify the down-converted signal, and the filter circuit 1606c may be a low pass filter (LPF) or a band pass filter (BPF) configured to remove unwanted signals from the down-converted signal to generate an output baseband signal. The output baseband signal may be provided to the baseband circuit 1604 for further processing. In some embodiments, the output baseband signal may be a zero frequency baseband signal, but this is not a requirement.In some embodiments, the mixer circuit 1606a of the receive signal path may include a passive mixer, but the scope of the embodiments is not limited in this regard.

[0188] In some embodiments, mixer circuit 1606a of the transmit signal path may be configured to up-convert an input baseband signal based on a synthesized frequency provided by synthesizer circuit 1606d to generate an RF output signal for FEM circuit 1608. The baseband signal may be provided by baseband circuit 1604 and may be filtered by filter circuit 1606c.

[0189] In some embodiments, the mixer circuit 1606a of the receive signal path and the mixer circuit 1606a of the transmit signal path may include two or more mixers and may be arranged for quadrature down-conversion and up-conversion, respectively. In some embodiments, the mixer circuit 1606a of the receive signal path and the mixer circuit 1606a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuit 1606a of the receive signal path and the mixer circuit 1606a of the transmit signal path may be arranged for direct down-conversion and direct up-conversion, respectively. In some embodiments, the mixer circuit 1606a of the receive signal path and the mixer circuit 1606a of the transmit signal path may be configured for superheterodyne operation.

[0190] In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, but the scope of the embodiments is not limited thereto. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, the RF circuit 1606 may include an analog-to-digital converter (ADC) and a digital-to-analog converter (DAC) circuit, and the baseband circuit 1604 may include a digital baseband interface to communicate with the RF circuit 1606.

[0191] In some dual-mode embodiments, separate radio IC circuits may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this regard.

[0192] In some embodiments, synthesizer circuit 1606d may be a fractional-N synthesizer or a fractional-N / N+1 synthesizer, but the scope of the embodiments is not limited in this regard, as other types of frequency synthesizers may be suitable. For example, synthesizer circuit 1606d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

[0193] The synthesizer circuit 1606d may be configured to synthesize, based on the frequency input and the divider control input, an output frequency used by the mixer circuit 1606a of the RF circuit 1606. In some embodiments, the synthesizer circuit 1606d may be a fractional-N / N+1 synthesizer.

[0194] In some embodiments, the frequency input may be provided by a voltage controlled oscillator (VCO), but this is not a requirement. Depending on the desired output frequency, the divider control input may be provided by the baseband circuit 1604 or the application processor 1602. In some embodiments, the divider control input (e.g., N) may be determined from a lookup table based on the channel indicated by the application processor 1602.

[0195] The synthesizer circuit 1606d of the RF circuit 1606 may include a divider, a delay locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the divider may be a dual-mode divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by N or N+1 (e.g., based on a carry) to provide a fractional division ratio. In some example embodiments, the DLL may include a set of cascaded tunable delay elements, a phase detector, a charge pump, and a D-type flip-flop. In these embodiments, the delay element may be configured to decompose the VCO cycle into Nd equal phase groups, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0196] In some embodiments, the synthesizer circuit 1606d can be configured to generate a carrier frequency as an output frequency, while in other embodiments, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with the quadrature generator and divider circuits to generate multiple signals with multiple different phases relative to each other at the carrier frequency. In some embodiments, the output frequency can be an LO frequency (fLO). In some embodiments, the RF circuit 1606 can include an IQ / polar converter.

[0197] The FEM circuitry 1608 may include a receive signal path, which may include circuitry configured to operate on RF signals received from one or more antennas 1610, amplify the received signals, and provide an amplified version of the received signals to the RF circuitry 1606 for further processing. The FEM circuitry 1608 may also include a transmit signal path, which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 1606 for transmission by one or more of the one or more antennas 1610. In various embodiments, amplification by the transmit or receive signal paths may be performed only in the RF circuitry 1606, only in the FEM 1608, or in both the RF circuitry 1606 and the FEM 1608.

[0198] In some embodiments, the FEM circuit 1608 may include a TX / RX switch to switch between transmit mode and receive mode operation. The FEM circuit may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit may include an LNA to amplify the received RF signal and provide the amplified received RF signal as an output (e.g., to the RF circuit 1606). The transmit signal path of the FEM circuit 1608 may include: a power amplifier (PA) for amplifying an input RF signal (e.g., provided by the RF circuit 1606); and one or more filters for generating an RF signal for subsequent transmission (e.g., by one or more of the one or more antennas 1610).

[0199] In some embodiments, PMC 1612 can manage the power provided to baseband circuit 1604. Specifically, PMC 1612 can control power selection, voltage scaling, battery charging, or DC-DC conversion. When device 1600 is capable of being powered by a battery, for example, when the device is included in a UE, PMC 1612 can generally be included. PMC 1612 can improve power conversion efficiency while providing desired implementation scale and heat dissipation characteristics.

[0200] although Fig.16 PMC 1612 is shown coupled only to baseband circuitry 1604. However, in other embodiments, PMC 1612 may additionally or alternatively be coupled to other components (such as, but not limited to, application circuitry 1602, RF circuitry 1606, or FEM 1608) and perform similar power management operations for the other components.

[0201] In some embodiments, the PMC 1612 may control or otherwise be part of various power saving mechanisms of the device 1600. For example, if the device 1600 is in the RRC_Connected state, where it is still connected to the RAN node because it expects to receive traffic soon, it may enter a state called discontinuous reception mode (DRX) after a period of inactivity. During this state, the device 1600 may be powered off for brief time intervals, thereby saving power.

[0202] If there is no data traffic activity for an extended period of time, the device 1600 may transition to the RRC_Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The device 1600 enters a very low power state, and it performs paging, where it wakes up periodically again to listen to the network, and then powers down again. The device 1600 may not receive data in this state, and in order to receive data, it must transition back to the RRC_Connected state.

[0203] An additional power saving mode may allow the device to be unavailable to the network for a period longer than the paging interval (ranging from a few seconds to a few hours). During this period, the device is completely unable to access the network and may be completely powered off. Any data sent during this period will incur significant latency, assuming that latency is acceptable.

[0204] The processor of the application circuit 1602 and the processor of the baseband circuit 1604 can be used to execute elements of one or more instances of the protocol stack. For example, the processor of the baseband circuit 1604 (alone or in combination) can be used to perform layer 3, layer 2, or layer 1 functions, while the processor of the application circuit 1604 can utilize data received from these layers (e.g., packet data) and further perform layer 4 functions (e.g., transport communication protocol (TCP) and user datagram protocol (UDP) layers). As mentioned herein, layer 3 may include a radio resource control (RRC) layer, which will be further described in detail below. As mentioned herein, layer 2 may include a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, which will be further described in detail below. As mentioned herein, layer 1 may include a physical (PHY) layer of a UE / RAN node, which will be further described in detail below.

[0205] Fig.17 1 shows an example interface of a baseband circuit according to some embodiments. As discussed above, Fig.16 The baseband circuit 1604 may include processors 1604A-1604E and a memory 1604G used by the processors. Each of the processors 1604A-1604E may include a memory interface 1704A-1704E, respectively, to send / receive data to / from the memory 1604G.

[0206] The baseband circuit 1604 may also include one or more interfaces for communicatively coupling to other circuits / devices, such as a memory interface 1712 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 1604), an application circuit interface 1714 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 1604), and a memory interface 1715 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 1604). Fig.16 The application circuit 1602 sends / receives data), the RF circuit interface 1716 (for example, for sending / receiving data to / from Fig.16 an interface for sending / receiving data to / from a RF circuit 1606), a wireless hardware connection interface 1718 (e.g., for sending / receiving data to / from a near field communication (NFC) component, Components (e.g., low power ), components and other communication components to send / receive data) and a power management interface 1720 (for example, an interface for sending / receiving power or control signals to / from the PMC 1612).

[0207] Fig.18 18 is a diagram of a control plane protocol stack according to some embodiments. In this embodiment, the control plane 1800 is shown as a communication protocol stack between UE 1501 (or alternatively, UE 1502), RAN node 1511 (or alternatively, RAN node 1512) and MME 1521.

[0208] The PHY layer 1801 may send or receive information used by the MAC layer 1802 over one or more air interfaces. The PHY layer 1801 may also perform link adaptation or adaptive modulation and coding (AMC), power control, cell search (e.g., for initial synchronization and handover purposes), and other measurements used by higher layers such as the RRC layer 1805. The PHY layer 1801 may further perform error detection on transport channels, forward error correction (FEC) encoding / decoding of transport channels, modulation / demodulation of physical channels, interleaving, rate matching, mapping to physical channels, and multiple-input multiple-output (MIMO) antenna processing.

[0209] The MAC layer 1802 can perform mapping between logical channels and transport channels, multiplex MAC service data units (SDUs) from one or more logical channels into transport blocks (TBs) for delivery to PHY via transport channels, demultiplex MAC SDUs from transport blocks (TBs) delivered from PHY via transport channels to one or more logical channels, multiplex MAC SDUs into TBs, schedule information reporting, error correction through hybrid automatic repeat request (HARQ), and logical channel priority sorting.

[0210] The RLC layer 1803 can operate in multiple operation modes, including: transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM). The RLC layer 1803 can perform transmission of upper layer protocol data units (PDUs), error correction through automatic repeat request (ARQ) for AM data transmission, and concatenation, segmentation, and reassembly of RLC SDUs for UM and AM data transmission. The RLC layer 1803 can also perform re-segmentation of RLC data PDUs for AM data transmission, reordering of RLC data PDUs for UM and AM data transmission, detection of duplicate data for UM and AM data transmission, discarding of RLC SDUs for UM and AM data transmission, detection of protocol errors for AM data transmission, and performance of RLC reconstruction.

[0211] The PDCP layer 1804 can perform header compression and decompression of IP data, maintain the PDCP sequence number (SN), perform in-order delivery of upper layer PDUs when reestablishing lower layers, eliminate duplication of lower layer SDUs when reestablishing lower layers for radio bearers mapped on RLC AM, encrypt and decrypt control plane data, perform integrity protection and integrity verification of control plane data, control timer-based data discard, and perform security operations (e.g., encryption, decryption, integrity protection, integrity verification, etc.).

[0212] The main services and functions of the RRC layer 1805 may include broadcasting of system information (e.g., included in a master information block (MIB) or a system information block (SIB) associated with a non-access stratum (NAS)), broadcasting of system information associated with an access stratum (AS), paging, establishment, maintenance and release of an RRC connection between a UE and an E-UTRAN (e.g., RRC connection paging, RRC connection establishment, RRC connection modification and RRC connection release), establishment, configuration, maintenance and release of point-to-point radio bearers, security functions (including key management), measurement configuration of radio access technology (RAT) mobility and UE measurement reporting. The MIB and SIB may include one or more information elements (IEs), each of which may include a separate data field or data structure.

[0213] UE 1501 and RAN node 1511 may utilize a Uu interface (eg, LTE-Uu interface) to exchange control plane data via a protocol stack, including a PHY layer 1801 , a MAC layer 1802 , an RLC layer 1803 , a PDCP layer 1804 , and an RRC layer 1805 .

[0214] Non-Access Stratum (NAS) protocol 1806 forms the highest layer of the control plane between UE 1501 and MME 1521. NAS protocol 1806 supports mobility of UE 1501 and session management procedures to establish and maintain IP connection between UE 1501 and P-GW 1523.

[0215] The S1 application protocol (S1-AP) layer 1815 may support the functions of the S1 interface and include an elementary procedure (EP). The EP is a unit of interaction between the RAN node 1511 and the CN 1520. The S1-AP layer services may include two groups: UE-associated services and non-UE-associated services. The functions performed by these services include, but are not limited to, E-UTRAN radio access bearer (E-RAB) management, UE capability indication, mobility, NAS signaling transmission, RAN information management (RIM), and configuration transmission.

[0216] The stream control transmission protocol (SCTP) layer (alternatively referred to as the SCTP / IP layer) 1814 may ensure reliable delivery of signaling messages between the RAN node 1511 and the MME 1521 based in part on the IP protocol supported by the IP layer 1813. The L2 layer 1812 and the L1 layer 1811 may refer to communication links (e.g., wired or wireless) used by the RAN node and the MME to exchange information.

[0217] The RAN node 1511 and the MME 1521 may exchange control plane data via a protocol stack using an S1-MME interface, including an L1 layer 1811 , an L2 layer 1812 , an IP layer 1813 , an SCTP layer 1814 , and an S1-AP 1815 layer.

[0218] Fig.19 1 is a diagram of a user plane protocol stack according to some embodiments. In this embodiment, the user plane 1900 is shown as a communication protocol stack between the UE 1501 (or alternatively, the UE 1502), the RAN node 1511 (or alternatively, the RAN node 1512), the S-GW 1522, and the P-GW 1523. The user plane 1900 may utilize at least some of the same protocol layers as the control plane 1800. For example, the UE 1501 and the RAN node 1511 may utilize a Uu interface (e.g., an LTE-Uu interface) to exchange user plane data via a protocol stack including a PHY layer 1801, a MAC layer 1802, an RLC layer 1803, and a PDCP layer 1804.

[0219] The General Packet Radio Service (GPRS) Tunneling Protocol for User Plane (GTP-U) layer 1904 can be used to carry user data within the GPRS core network and between the radio access network and the core network. For example, the transmitted user data can be in any of IPv4, IPv6, and PPP formats. The UDP and IP Security (UDP / IP) layer 1903 can provide checksums for data integrity, port numbers for addressing different functions at the source and destination, and encryption and authentication of selected data flows. The RAN node 1511 and the S-GW 1522 can utilize the S1-U interface to exchange user plane data via a protocol stack, including the L1 layer 1811, the L2 layer 1812, the UDP / IP layer 1903, and the GTP-U layer 1904. S-GW 1522 and P-GW 1523 may utilize an S5 / S8a interface to exchange user plane data via a protocol stack, including L1 layer 1811, L2 layer 1812, UDP / IP layer 1903, and GTP-U layer 1904. Fig.18 As discussed, the NAS protocol supports the mobility of UE 1501 and session management procedures to establish and maintain an IP connection between UE 1501 and P-GW 1523.

[0220] Fig. 20 Components of a core network according to some embodiments are shown. The components of CN 1520 can be implemented in one physical node or separate physical nodes, including components that read and execute instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some embodiments, network function virtualization (NFV) is used to virtualize any or all of the above-mentioned network node functions (described in further detail below) via executable instructions stored in one or more computer-readable storage media. A logical instance of CN 1520 can be referred to as a network slice 2001. A logical instance of a portion of CN 1520 can be referred to as a network sub-slice 2002 (e.g., network sub-slice 2002 is shown as including PGW 1523 and PCRF 1526).

[0221] The NFV architecture and infrastructure can be used to virtualize one or more network functions, instead of being performed by dedicated hardware, onto physical resources including a combination of industry-standard server hardware, storage hardware, or switches. In other words, the NFV system can be used to perform a virtual or reconfigurable implementation of one or more EPC components / functions.

[0222] Fig.21 21 is a block diagram illustrating components of a system 2100 for supporting NFV according to some exemplary embodiments. The system 2100 is shown to include a virtualization infrastructure manager (VIM) 2102, a network function virtualization infrastructure (NFVI) 2104, a VNF manager (VNFM) 2106, a virtualized network function (VNF) 2108, an element manager (EM) 2110, a NFV orchestrator (NFVO) 2112, and a network manager (NM) 2114.

[0223] The VIM 2102 manages the resources of the NFVI 2104. The NVVI 2104 may include physical or virtual resources and applications (including hypervisors) used to execute the system 2100. The VIM 2102 may utilize the NFVI 2104 to manage the lifecycle of virtual resources (e.g., create, maintain, and tear down virtual machines (VMs) associated with one or more physical resources), track VM instances, track the performance, failures, and security of VM instances and associated physical resources, and expose VM instances and associated physical resources to other management systems.

[0224] The VNFM 2106 may manage the VNF 2108. The VNF 2108 may be used to perform EPC components / functions. The VNFM 2106 may manage the lifecycle of the VNF 2108 and track the performance, failures, and security of the virtual aspects of the VNF 2108. The EM 2110 may track the performance, failures, and security of the functional aspects of the VNF 2108. The tracking data from the VNFM 2106 and the EM 2110 may include, for example, performance measurement (PM) data used by the VIM 2102 or the NFVI 2104. Both the VNFM 2106 and the EM 2110 may scale up / down the amount of VNFs of the system 2100.

[0225] NFVO 2112 can coordinate, authorize, release, and participate in the resources of NFVI 2104 in order to provide the requested service (e.g., execute EPC functions, components, or slices). NM 2114 can provide a grouping of end-user functions, which is responsible for managing the network, which can include network elements with VNFs, non-virtualized network functions, or both (management of VNFs can be performed via EM 2110).

[0226] Fig. 22 is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and executing any one or more of the methods discussed herein, according to some example embodiments. Specifically, Fig. 22 A graphical representation of hardware resources 2200 is shown, including one or more processors (or processor cores) 2210, one or more memory / storage devices 2220, and one or more communication resources 2230, each of which may be communicatively coupled via a bus 2240. For embodiments utilizing node virtualization (e.g., NFV), a hypervisor 2202 may be executed to provide an execution environment for one or more network slices / sub-slices to utilize the hardware resources 2200.

[0227] Processor 2210 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP) (such as a baseband processor), an application specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), other processors, or any suitable combination thereof) may include, for example, processor 2212 and processor 2214.

[0228] The memory / storage device 2220 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 2220 may include, but is not limited to, any type of volatile or non-volatile memory, such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state storage, etc.

[0229] The communication resources 2230 may include an interconnect or network interface component or other suitable device to communicate with one or more peripheral devices 2204 or one or more databases 2206 via the network 2208. For example, the communication resources 2230 may include a wired communication component (e.g., for coupling via a universal serial bus (USB)), a cellular communication component, an NFC component, Components (e.g., low power ), components and other communication components.

[0230] The instructions 2250 may include software, programs, applications, applet programs, apps, or other executable code for causing at least any processor 2210 to perform any one or more of the methods discussed herein. The instructions 2250 may reside in whole or in part within at least one of the processors 2210 (e.g., within a cache memory of the processor), within the memory / storage device 2220, or any suitable combination thereof. In addition, any portion of the instructions 2250 may be transmitted to the hardware resources 2200 from any combination of the peripheral device 2204 or the database 2206. Therefore, the memory of the processor 2210, the memory / storage device 2220, the peripheral device 2204, and the database 2206 are examples of computer-readable and machine-readable media.

[0231] For one or more embodiments, at least one of the components described in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes and / or methods as described in the example section below. For example, the baseband circuit described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more examples described below. For another example, the circuits associated with the UE, base station, network element, etc. described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more examples described in the example section below.

[0232] Example

[0233] Example 1 may include an apparatus for a user equipment (UE), comprising: an interface, the UE being configured to communicate with a base station (BS) through the interface; a processor configured to: at the UE, decode an aperiodic tracking reference signal (A-TRS) from the BS via a physical downlink shared channel (PDSCH); and at the UE, determine quasi-co-location (QCL) information of the A-TRS, wherein, when the A-TRS spans at least two consecutive time slots and a threshold for scheduling offset is between at least two consecutive time slots, the QCL information is determined at least in part based on a type of the QCL information, wherein the type includes at least one of type A and type D.

[0234] Example 2 may include the subject matter of Example 1 and / or some other examples herein, wherein Type A represents at least one of Doppler shift, Doppler spread, average delay, and delay spread, and Type D represents spatial Rx parameters.

[0235] Example 3 may include the subject matter of Example 1 and / or some other examples herein, wherein, in response to type D being included in the QCL information of an A-TRS resource set, a scheduling offset between the last symbol of a scheduled physical downlink control channel (PDCCH) and each A-TRS resource is set to be higher than a threshold, and the A-TRS is QCLed using the QCL information indicated by the scheduling PDCCH.

[0236] Example 4 may include the subject matter of Example 1 and / or some other examples herein, wherein, in response to type D being included in the QCL information of the A-TRS resource set: when the scheduling offset between the last symbol of the scheduled physical downlink control channel (PDCCH) and each A-TRS resource is lower than or equal to a threshold, the A-TRS is QCLed with the latest control resource set (CORESET) with the lowest CORESET ID, excluding CORESET 0 and / or CORESET for beam failure recovery; otherwise, the A-TRS is QCLed with the QCL information indicated by the scheduling PDCCH.

[0237] Example 5 may include the subject matter of Example 1 and / or some other examples herein, wherein the QCL information is derived from QCL parameters configured in a radio resource control (RRC) layer that triggers an A-TRS resource set regardless of a scheduling offset.

[0238] Example 6 may include the subject matter of Example 1 and / or some other examples herein, wherein Type D is not configured for A-TRS such that A-TRS is used only for frequency range (FR) 1, and Type D is configured for A-TRS such that A-TRS is used only for FR 2.

[0239] Example 7 may include the subject matter of Example 6 and / or some other examples herein, wherein FR1 is below 6 GHz and FR2 is above 6 GHz.

[0240] Example 8 may include an apparatus for a gNB, comprising: an interface, the gNB being configured to communicate with a user equipment (UE) through the interface; a processor configured to: at the gNB, encode an aperiodic tracking reference signal (A-TRS) that arrives at the UE through a physical downlink shared channel (PDSCH); enable the UE to determine quasi-co-location (QCL) information of the A-TRS, wherein, when the A-TRS spans at least two consecutive time slots and a threshold for scheduling offset is between the at least two consecutive time slots, the QCL information is determined at least in part based on a type of the QCL information, wherein the type includes at least one of type A and type D.

[0241] Example 9 may include the subject matter of Example 8 and / or some other examples herein, wherein Type A represents at least one of Doppler shift, Doppler spread, average delay, and delay spread, and Type D represents spatial Rx parameters.

[0242] Example 10 may include the subject matter of Example 8 and / or some other examples herein, wherein, in response to type D being included in the QCL information of an A-TRS resource set, a scheduling offset between the last symbol of a scheduled physical downlink control channel (PDCCH) and each A-TRS resource is set to be above a threshold, and the A-TRS is QCLed using the QCL information indicated by the scheduling PDCCH.

[0243] Example 11 may include the subject matter of Example 8 and / or some other examples herein, wherein, in response to type D being included in the QCL information of the A-TRS resource set: when the scheduling offset between the last symbol of the scheduled physical downlink control channel (PDCCH) and each A-TRS resource is lower than or equal to a threshold, the A-TRS is QCLed with the latest control resource set (CORESET) with the lowest CORESET ID, wherein CORESET 0 for beam failure recovery and / or CORESET for beam failure recovery are excluded; otherwise, the A-TRS is QCLed with the QCL information indicated by the scheduling PDCCH.

[0244] Example 12 may include the subject matter of Example 8 and / or some other examples herein, wherein the QCL information is derived from QCL parameters configured in a radio resource control (RRC) layer that triggers the A-TRS resource set, regardless of the scheduling offset.

[0245] Example 13 may include the subject matter of Example 8 and / or some other examples herein, wherein Type D is not configured for A-TRS such that A-TRS is used only for frequency range (FR) 1, and Type D is configured for A-TRS such that A-TRS is used only for FR 2.

[0246] Example 14 may include the subject matter of Example 13 and / or some other examples herein, wherein FR 1 is below 6 GHz and FR 2 is above 6 GHz.

[0247] Example 15 may include an apparatus comprising modules for performing one or more elements of a method described or related to any of Examples 1 to 14 or other methods or processes described herein.

[0248] Example 16 may include one or more non-transitory computer-readable media comprising instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of a method described in or related to any of Examples 1 to 14 or other methods or processes described herein.

[0249] Example 17 may include an apparatus comprising logic, modules, or circuits for performing one or more elements of a method described or related to any of Examples 1-14 or other methods or processes described herein.

[0250] Example 18 may include a method, technique, or process described or related to any one of Examples 1 to 14, or a portion thereof.

[0251] Example 19 may include a device comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process described in or related to any of Examples 1 to 14, or a portion thereof.

[0252] Example 20 may include a signal or a portion thereof described or related to any one of Examples 1 to 14.

[0253] Example 21 may include signals in a wireless network as shown and described herein.

[0254] Example 22 may include a method of communicating in a wireless network as shown and described herein.

[0255] Example 23 may include a system for providing wireless communications as shown and described herein.

[0256] Example 24 may include an apparatus for a user equipment (UE), comprising: an interface, the UE being configured to communicate with a base station (BS) through the interface; a processor configured to: at the UE, decode a non-periodic channel state information reference signal (CSI-RS) for beam management from the BS; and at the UE, determine a spatial quasi-co-location (QCL) assumption of the CSI-RS based on a scheduling offset between triggering downlink control information (DCI) for triggering the CSI-RS and the CSI-RS.

[0257] Example 25 may include the subject matter of Example 24 and / or some other examples herein, wherein the CSI-RS is configured with a parameter CSI-RS-ResourceRep to indicate a repetition of a Tx beam from the BS.

[0258] Example 26 may include the subject matter of Example 25 and / or some other examples herein, wherein, when CSI-RS-ResourceRep indicates a repeated Tx beam and the scheduling offset is less than a threshold of the CSI-RS, a default spatial QCL assumption is applied to the CSI-RS within the threshold range, and UE Rx beam scanning is performed for the CSI-RS outside the threshold range.

[0259] Example 27 may include the subject matter of Example 25 and / or some other examples herein, wherein, when CSI-RS-ResourceRep indicates non-repeating Tx beams and the scheduling offset is less than a threshold for the CSI-RS, a default spatial QCL assumption is applied to all triggered CSI-RSs.

[0260] Example 28 may include the subject matter of Example 26 or 27 and / or some other examples herein, wherein the default spatial QCL assumption is the same as the control resource set (CORESET) that triggers the CSI-RS or the lowest CORESET in the latest time slot.

[0261] Example 29 may include the subject matter of Example 24 and / or some other examples herein, wherein the CSI measurement is discarded if the same UE Rx beam is not guaranteed for channel measurement resources (CMR) and interference measurement resources (IMR) that do not exist in the same time slot.

[0262] Example 30 may include the subject matter of Example 24 and / or some other examples herein, wherein, if the CSI-RS is frequency division multiplexed (FDM) utilizing a physical downlink shared channel (PDSCH), the spatial QCL assumption of the CSI-RS follows the QCL assumption used for PDSCH reception.

[0263] Example 31 may include the subject matter of Example 24 and / or some other examples in this document, wherein, if the CSI-RS is time division multiplexed (TDM) using a physical downlink shared channel (PDSCH), then when the scheduling offset is less than a threshold, the default spatial QCL assumption of the CSI-RS is applied, and the spatial QCL assumption of the CSI-RS follows the QCL configuration indicated by the DCI.

[0264] Example 32 may include the subject matter of Example 31 and / or some other examples herein, wherein the default spatial QCL assumption for CSI-RS follows the QCL assumption for PDSCH reception, or is the QCL assumption that triggered the DCI or the QCL assumption of the lowest CORESET ID in the latest time slot.

[0265] Example 33 may include the subject matter of Example 24 and / or some other examples herein, wherein, if the scheduling offset between the triggered DCI and CSI-RS is greater than a threshold for the CSI-RS and the scheduling offset between the DCI and the PDSCH is less than a threshold for the PDSCH, the default spatial QCL assumption for the CSI-RS follows the QCL assumption for CSI-RS reception indicated by the DCI, or the QCL assumption for the CSI-RS indicated by the DCI is discarded.

[0266] Example 34 may include the subject matter of Example 24 and / or some other examples herein, wherein, if the scheduling offset between the triggering DCI and the CSI-RS is greater than a threshold of the CSI-RS, and the time offset between the starting point of the CSI-RS and the latest physical downlink control channel (PDCCH) CORESET listening opportunity is less than a threshold determined for the PDSCH default spatial QCL assumption, the spatial QCL assumption of the CSI-RS indicated by the DCI is discarded.

[0267] Example 35 may include the subject matter of Example 24 and / or some other examples herein, wherein, if the scheduling offset between the triggering DCI and the CSI-RS is greater than a threshold of the CSI-RS, and there are additional PDCCH CORESET listening opportunities between the CSI-RS and the triggering DCI, and the time offset between the starting point of the CSI-RS and the latest physical downlink control channel (PDCCH) CORESET listening opportunity is less than a threshold determined for the PDSCH default spatial QCL assumption, the spatial QCL assumption for the CSI-RS indicated by the DCI is discarded, and the spatial QCL assumption for the CSI-RS follows the QCL assumption of the CORESET with the lowest CORESET ID in the PDSCH or the latest time slot; or regardless of whether the CSI-RS is FDM or TDM with the PDSCH, the spatial QCL assumption for PDSCH reception follows the indicated QCL assumption for the CSI-RS.

[0268] Example 36 may include the subject matter of Example 24 or 34 and / or some other examples in this document, wherein, if TDM is performed on CSI-RS using PDSCH and the scheduling offset between the triggering DCI and CSI-RS is greater than a threshold of CSI-RS, the spatial QCL assumption indicated by the DCI is applied to CSI-RS reception and the default spatial QCL assumption is applied to PDSCH reception.

[0269] Example 37 may include the subject matter of Example 36 and / or some other examples herein, wherein the default spatial QCL assumption is the QCL assumption of the CORESET with the lowest CORESET ID in the latest time slot.

[0270] Example 38 may include the subject matter of Example 24 or 34 and / or some other examples herein, wherein, if FDM is performed on CSI-RS using PDSCH and the scheduling offset between the triggering DCI and CSI-RS is greater than a threshold for CSI-RS, the spatial QCL assumption indicated by the DCI is applied to CSI-RS reception and the same spatial QCL assumption is applied to possible PDSCH reception.

[0271] Example 39 may include the subject matter of Example 24 or 34 and / or some other examples herein, wherein, if FDM is performed on the CSI-RS using PDSCH and the scheduling offset between the triggered DCI and the CSI-RS is greater than a threshold for the CSI-RS, the spatial QCL assumption for the CSI-RS follows the QCL assumption for possible PDSCH reception.

[0272] Example 40 may include the subject matter of Example 24 and / or some other examples herein, wherein FDM between CSI-RS and PDSCH is not allowed.

[0273] Example 41 may include the subject matter of Example 24 and / or some other examples herein, wherein the scheduling offset between the triggered DCI and the CSI-RS is set to be less than a specific threshold and the default spatial QCL assumption is applied to CSI-RS reception.

[0274] Example 42 may include the subject matter of Example 41 and / or some other examples herein, wherein the default spatial QCL assumption is the QCL assumption that triggered the DCI or the QCL assumption of the CORESET with the lowest CORESET ID in the latest time slot.

[0275] Example 43 may include the subject matter of Example 24 and / or some other examples herein, wherein, when CSI-RS is triggered, there are no other PDCCH CORESET monitoring opportunities between triggering DCI and CSI-RS.

[0276] Example 44 may include the subject matter of Example 24 and / or some other examples herein, wherein the BS is configured to schedule a PDSCH with a scheduling offset higher than a threshold reported by the UE when configuring one or more component carriers (CCs).

[0277] Example 45 may include the subject matter of Example 24 and / or some other examples herein, wherein the UE is configured to receive each symbol that may be allocated to a PDSCH transmission using a default Rx beam.

[0278] Example 46 may include the subject matter of Example 44 and / or some other examples herein, wherein the UE is configured to receive all possible symbols of the PDSCH using a default Rx beam from a primary cell (PCell) without a beam indication.

[0279] Example 47 may include the subject matter of Example 24 and / or some other examples in this document, wherein if the CSI-RS is not multiplexed with PDSCH and the scheduling offset between the triggering DCI and the CSI-RS is less than a threshold for the CSI-RS, a default spatial QCL assumption is applied to the CSI-RS.

[0280] Example 48 may include the subject matter of Example 47 and / or some other examples herein, wherein the default spatial QCL assumption is the QCL assumption that triggered the DCI or the QCL assumption of the CORESET with the lowest CORESET ID in the latest time slot.

[0281] Example 49 may include an apparatus for a gNB, comprising: an interface, the gNB being configured to communicate with a user equipment (UE) through the interface; a processor configured to: at the gNB, encode a non-periodic channel state information reference signal (CSI-RS) for beam management that arrives at the UE; and enable the UE to determine a spatial quasi-co-location (QCL) assumption of the CSI-RS based on a scheduling offset between triggering downlink control information (DCI) for triggering the CSI-RS and the CSI-RS.

[0282] Example 50 may include the subject matter of Example 49 and / or some other examples herein, wherein the CSI-RS is configured with a parameter CSI-RS-ResourceRep to indicate a repetition of a Tx beam from the gNB.

[0283] Example 51 may include the subject matter of Example 50 and / or some other examples herein, wherein, when CSI-RS-ResourceRep indicates a repeated Tx beam and the scheduling offset is less than a threshold of the CSI-RS, a default spatial QCL assumption is applied to the CSI-RS within the threshold range, and UE Rx beam scanning is performed for the CSI-RS outside the threshold range.

[0284] Example 52 may include the subject matter of Example 50 and / or some other examples herein, wherein, when CSI-RS-ResourceRep indicates non-repeating Tx beams and the scheduling offset is less than a threshold for the CSI-RS, a default spatial QCL assumption is applied to all triggered CSI-RSs.

[0285] Example 53 may include the subject matter of Example 51 or 52 and / or some other examples herein, wherein the default spatial QCL assumption is the same as the control resource set (CORESET) that triggers the CSI-RS or the lowest CORESET in the latest time slot.

[0286] Example 54 may include the subject matter of Example 49 and / or some other examples herein, wherein the CSI measurement is discarded if the same UE Rx beam is not guaranteed for channel measurement resources (CMR) and interference measurement resources (IMR) that do not exist in the same time slot.

[0287] Example 55 may include the subject matter of Example 49 and / or some other examples herein, wherein, if the CSI-RS is frequency division multiplexed (FDM) utilizing a physical downlink shared channel (PDSCH), the spatial QCL assumption for the CSI-RS follows the QCL assumption for PDSCH reception.

[0288] Example 56 may include the subject matter of Example 49 and / or some other examples herein, wherein, if the CSI-RS is time division multiplexed (TDM) using a physical downlink shared channel (PDSCH), then when the scheduling offset is less than a threshold, a default spatial QCL assumption of the CSI-RS is applied, and the spatial QCL assumption of the CSI-RS follows the QCL configuration indicated by the DCI.

[0289] Example 57 may include the subject matter of Example 56 and / or some other examples herein, wherein the default spatial QCL assumption for CSI-RS follows the QCL assumption for PDSCH reception, or is the QCL assumption that triggered the DCI or the QCL assumption of the lowest CORESET ID in the latest time slot.

[0290] Example 58 may include the subject matter of Example 49 and / or some other examples herein, wherein, if the scheduling offset between the triggered DCI and CSI-RS is greater than a threshold for the CSI-RS and the scheduling offset between the DCI and the PDSCH is less than a threshold for the PDSCH, the default spatial QCL assumption for the CSI-RS follows the QCL assumption for CSI-RS reception indicated by the DCI, or the QCL assumption for the CSI-RS indicated by the DCI is discarded.

[0291] Example 59 may include the subject matter of Example 49 and / or some other examples herein, wherein, if the scheduling offset between the triggering DCI and the CSI-RS is greater than a threshold of the CSI-RS, and the time offset between the starting point of the CSI-RS and the latest physical downlink control channel (PDCCH) CORESET listening opportunity is less than a threshold determined for the PDSCH default spatial QCL assumption, the spatial QCL assumption of the CSI-RS indicated by the DCI is discarded.

[0292] Example 60 may include the subject matter of Example 49 and / or some other examples herein, wherein, if the scheduling offset between the triggering DCI and the CSI-RS is greater than a threshold of the CSI-RS, and there are additional PDCCH CORESET listening opportunities between the CSI-RS and the triggering DCI, and the time offset between the starting point of the CSI-RS and the latest physical downlink control channel (PDCCH) CORESET listening opportunity is less than a threshold determined for the PDSCH default spatial QCL assumption, the spatial QCL assumption for the CSI-RS indicated by the DCI is discarded, and the spatial QCL assumption for the CSI-RS follows the QCL assumption of the CORESET with the lowest CORESET ID in the PDSCH or the latest time slot; or the spatial QCL assumption for PDSCH reception follows the indicated QCL assumption for the CSI-RS regardless of whether the CSI-RS is FDM or TDM with the PDSCH.

[0293] Example 61 may include the subject matter of Example 49 or 59 and / or some other examples herein, wherein, if TDM is performed on CSI-RS using PDSCH and the scheduling offset between the triggering DCI and CSI-RS is greater than a threshold for CSI-RS, the spatial QCL assumption indicated by the DCI is applied to CSI-RS reception and the default spatial QCL assumption is applied to PDSCH reception.

[0294] Example 62 may include the subject matter of Example 60 and / or some other examples herein, wherein the default spatial QCL assumption is the QCL assumption of the CORESET with the lowest CORESET ID in the latest time slot.

[0295] Example 63 may include the subject matter of Example 49 or 59 and / or some other examples herein, wherein, if FDM is performed on CSI-RS using PDSCH and the scheduling offset between the triggering DCI and CSI-RS is greater than a threshold for CSI-RS, the spatial QCL assumption indicated by the DCI is applied to CSI-RS reception and the same spatial QCL assumption is applied to possible PDSCH reception.

[0296] Example 64 may include the subject matter of Example 49 or 59 and / or some other examples herein, wherein, if FDM is performed on the CSI-RS using PDSCH and the scheduling offset between the triggered DCI and the CSI-RS is greater than a threshold for the CSI-RS, the spatial QCL assumption for the CSI-RS follows the QCL assumption for possible PDSCH reception.

[0297] Example 65 may include the subject matter of Example 49 and / or some other examples herein, wherein FDM between CSI-RS and PDSCH is not allowed.

[0298] Example 66 may include the subject matter of Example 49 and / or some other examples herein, wherein the scheduling offset between the triggered DCI and the CSI-RS is set to be less than a specific threshold and the default spatial QCL assumption is applied to CSI-RS reception.

[0299] Example 67 may include the subject matter of Example 66 and / or some other examples herein, wherein the default spatial QCL assumption is the QCL assumption that triggered the DCI or the QCL assumption of the CORESET with the lowest CORESET ID in the latest time slot.

[0300] Example 68 may include the subject matter of Example 49 and / or some other examples herein, wherein, when CSI-RS is triggered, there are no other PDCCH CORESET monitoring opportunities between triggering DCI and CSI-RS.

[0301] Example 69 may include the subject matter of Example 49 and / or some other examples herein, wherein the BS is configured to schedule a PDSCH with a scheduling offset higher than a threshold reported by the UE when configuring one or more component carriers (CCs).

[0302] Example 70 may include the subject matter of Example 49 and / or some other examples herein, wherein the UE is configured to receive each symbol that may be allocated to a PDSCH transmission using a default Rx beam.

[0303] Example 71 may include the subject matter of Example 69 and / or some other examples herein, wherein the UE is configured to receive all possible symbols of the PDSCH using a default Rx beam from a primary cell (PCell) in the absence of a beam indication.

[0304] Example 72 may include the subject matter of Example 49 and / or some other examples herein, wherein, if the CSI-RS is not multiplexed with PDSCH and the scheduling offset between the triggered DCI and the CSI-RS is less than a threshold for the CSI-RS, a default spatial QCL assumption is applied to the CSI-RS.

[0305] Example 73 may include the subject matter of Example 72 and / or some other examples herein, wherein the default spatial QCL assumption is the QCL assumption that triggered the DCI or the QCL assumption of the CORESET with the lowest CORESET ID in the latest time slot.

[0306] Example 74 may include an apparatus comprising modules for performing one or more elements of a method described or related to any of Examples 24 to 73 or other methods or processes described herein.

[0307] Example 75 may include one or more non-transitory computer-readable media comprising instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of a method described in or related to any of Examples 24 to 73 or other methods or processes described herein.

[0308] Example 76 may include an apparatus comprising logic, modules, or circuits for performing one or more elements of a method described or related to any of Examples 24-73 or other methods or processes described herein.

[0309] Example 77 may include a method, technique, or process described or related to any one of Examples 24 to 73, or a portion thereof.

[0310] Example 78 may include a device comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process described in or related to any of Examples 24 to 73, or a portion thereof.

[0311] Example 79 may include a signal or portion thereof described or related to any one of Examples 1 to 14.

[0312] Example 80 may include signals in a wireless network as shown and described herein.

[0313] Example 81 may include a method of communicating in a wireless network as shown and described herein.

[0314] Example 82 may include a system for providing wireless communications as shown and described herein.

[0315] Example 83 may include a method for quasi-co-location (QCL) indication of a non-periodic tracking reference signal (A-TRS), comprising: at a UE, decoding an non-periodic tracking reference signal (A-TRS) from a base station (BS) via a physical downlink shared channel (PDSCH); and at the UE, determining quasi-co-location (QCL) information of the A-TRS, wherein, when the A-TRS spans at least two consecutive time slots and a threshold for scheduling offset is between at least two consecutive time slots, the QCL information is determined at least in part based on a type of the QCL information, wherein the type includes at least one of type A and type D.

[0316] Example 84 may include the subject matter of Example 83 and / or some other examples herein, wherein Type A represents at least one of Doppler shift, Doppler spread, average delay, and delay spread, and Type D represents spatial Rx parameters.

[0317] Example 85 may include the subject matter of Example 83 and / or some other examples herein, wherein, in response to type D being included in the QCL information of the A-TRS resource set, a scheduling offset between the last symbol of a scheduled physical downlink control channel (PDCCH) and each A-TRS resource is set to be above a threshold, and the A-TRS is QCLed using the QCL information indicated by the scheduling PDCCH.

[0318] Example 86 may include the subject matter of Example 83 and / or some other examples herein, wherein, in response to type D being included in the QCL information of the A-TRS resource set: when the scheduling offset between the last symbol of the scheduled physical downlink control channel (PDCCH) and each A-TRS resource is lower than or equal to a threshold, the A-TRS is QCLed with the latest control resource set (CORESET) with the lowest CORESET ID, excluding CORESET 0 and / or CORESET for beam failure recovery; otherwise, the A-TRS is QCLed with the QCL information indicated by the scheduling PDCCH.

[0319] Example 87 may include the subject matter of Example 83 and / or some other examples herein, wherein the QCL information is derived from QCL parameters configured in a radio resource control (RRC) layer that triggers the A-TRS resource set, regardless of the scheduling offset.

[0320] Example 88 may include the subject matter of Example 83 and / or some other examples herein, wherein Type D is not configured for A-TRS such that A-TRS is used only for frequency range (FR) 1, and Type D is configured for A-TRS such that A-TRS is used only for FR 2.

[0321] Example 89 may include the subject matter of Example 88 and / or some other examples herein, wherein FR 1 is below 6 GHz and FR 2 is above 6 GHz.

[0322] Example 90 may include a method for quasi-co-location (QCL) indication of an aperiodic tracking reference signal (A-TRS), comprising: at a gNB, encoding an aperiodic tracking reference signal (A-TRS) that arrives at a user equipment (UE) via a physical downlink shared channel (PDSCH); enabling the UE to determine quasi-co-location (QCL) information of the A-TRS, wherein, when the A-TRS spans at least two consecutive time slots and a threshold for scheduling offset is between the at least two consecutive time slots, the QCL information is determined at least in part based on a type of the QCL information, wherein the type includes at least one of type A and type D.

[0323] Example 91 may include the subject matter of Example 90 and / or some other examples herein, wherein Type A represents at least one of Doppler shift, Doppler spread, average delay, and delay spread, and Type D represents spatial Rx parameters.

[0324] Example 92 may include the subject matter of Example 90 and / or some other examples herein, wherein, in response to type D being included in the QCL information of the A-TRS resource set, a scheduling offset between the last symbol of a scheduled physical downlink control channel (PDCCH) and each A-TRS resource is set to be above a threshold, and the A-TRS is QCLed using the QCL information indicated by the scheduling PDCCH.

[0325] Example 93 may include the subject matter of Example 90 and / or some other examples herein, wherein, in response to type D being included in the QCL information of the A-TRS resource set: when the scheduling offset between the last symbol of the scheduled physical downlink control channel (PDCCH) and each A-TRS resource is lower than or equal to a threshold, the A-TRS is QCLed with the latest control resource set (CORESET) with the lowest CORESET ID, excluding CORESET 0 and / or CORESET for beam failure recovery; otherwise, the A-TRS is QCLed with the QCL information indicated by the scheduling PDCCH.

[0326] Example 94 may include the subject matter of Example 90 and / or some other examples herein, wherein the QCL information is derived from QCL parameters configured in a radio resource control (RRC) layer that triggers the A-TRS resource set regardless of the scheduling offset.

[0327] Example 95 may include the subject matter of Example 90 and / or some other examples herein, wherein Type D is not configured for A-TRS such that A-TRS is used only for frequency range (FR) 1, and Type D is configured for A-TRS such that A-TRS is used only for FR 2.

[0328] Example 96 may include the subject matter of Example 95 and / or some other examples herein, wherein FR 1 is below 6 GHz and FR 2 is above 6 GHz.

[0329] Example 97 may include a method for triggering a quasi-co-location (QCL) indication of a non-periodic channel state information reference signal (CSI-RS), comprising: at a user equipment (UE), decoding a non-periodic channel state information reference signal (CSI-RS) for beam management from a base station; and at the UE, determining a spatial quasi-co-location (QCL) assumption of the CSI-RS based on a scheduling offset between triggering downlink control information (DCI) for triggering the CSI-RS and the CSI-RS.

[0330] Example 98 may include the subject matter of Example 97 and / or some other examples herein, wherein the CSI-RS is configured with a parameter CSI-RS-ResourceRep to indicate a repetition of a Tx beam from the BS.

[0331] Example 99 may include the subject matter of Example 98 and / or some other examples herein, wherein, when CSI-RS-ResourceRep indicates a repeated Tx beam and the scheduling offset is less than a threshold of the CSI-RS, a default spatial QCL assumption is applied to the CSI-RS within the threshold range, and UE Rx beam scanning is performed for the CSI-RS outside the threshold range.

[0332] Example 100 may include the subject matter of Example 98 and / or some other examples herein, wherein, when CSI-RS-ResourceRep indicates non-repeating Tx beams and the scheduling offset is less than a threshold for the CSI-RS, a default spatial QCL assumption is applied to all triggered CSI-RSs.

[0333] Example 101 may include the subject matter of Example 99 or 100 and / or some other examples herein, wherein the default spatial QCL assumption is the same as the control resource set (CORESET) that triggers the CSI-RS or the lowest CORESET in the latest time slot.

[0334] Example 102 may include the subject matter of Example 90 and / or some other examples herein, wherein the CSI measurement is discarded if the same UE Rx beam is not guaranteed for channel measurement resources (CMR) and interference measurement resources (IMR) that do not exist in the same time slot.

[0335] Example 103 may include the subject matter of Example 90 and / or some other examples herein, wherein, if the CSI-RS is frequency division multiplexed (FDM) utilizing a physical downlink shared channel (PDSCH), the spatial QCL assumption of the CSI-RS follows the QCL assumption used for PDSCH reception.

[0336] Example 104 may include the subject matter of Example 90 and / or some other examples herein, wherein, if the CSI-RS is time division multiplexed (TDM) using a physical downlink shared channel (PDSCH), then when the scheduling offset is less than a threshold, a default spatial QCL assumption of the CSI-RS is applied, and the spatial QCL assumption of the CSI-RS follows the QCL configuration indicated by the DCI.

[0337] Example 105 may include the subject matter of Example 104 and / or some other examples herein, wherein the default spatial QCL assumption for CSI-RS follows the QCL assumption for PDSCH reception, or is the QCL assumption that triggered the DCI or the QCL assumption of the lowest CORESET ID in the latest time slot.

[0338] Example 106 may include the subject matter of Example 90 and / or some other examples herein, wherein, if the scheduling offset between the triggered DCI and CSI-RS is greater than a threshold of the CSI-RS and the scheduling offset between the DCI and the PDSCH is less than a threshold of the PDSCH, the default spatial QCL assumption for the CSI-RS follows the QCL assumption for CSI-RS reception indicated by the DCI, or the QCL assumption for the CSI-RS indicated by the DCI is discarded.

[0339] Example 107 may include the subject matter of Example 90 and / or some other examples herein, wherein, if the scheduling offset between the triggering DCI and the CSI-RS is greater than a threshold of the CSI-RS, and the time offset between the starting point of the CSI-RS and the latest physical downlink control channel (PDCCH) CORESET listening opportunity is less than a threshold determined for the PDSCH default spatial QCL assumption, the spatial QCL assumption of the CSI-RS indicated by the DCI is discarded.

[0340] Example 108 may include the subject matter of Example 90 and / or some other examples herein, wherein, if the scheduling offset between the triggering DCI and the CSI-RS is greater than a threshold of the CSI-RS, and there are additional PDCCH CORESET listening opportunities between the CSI-RS and the triggering DCI, and the time offset between the starting point of the CSI-RS and the latest physical downlink control channel (PDCCH) CORESET listening opportunity is less than a threshold determined for the PDSCH default spatial QCL assumption, the spatial QCL assumption of the CSI-RS indicated by the DCI is discarded, and the spatial QCL assumption follows the QCL assumption of the CORESET with the lowest CORESET ID in the PDSCH or the latest time slot; or the spatial QCL assumption for PDSCH reception follows the indicated QCL assumption for the CSI-RS regardless of whether the CSI-RS is FDM or TDM with the PDSCH.

[0341] Example 109 may include the subject matter of Example 90 or 100 and / or some other examples herein, wherein, if TDM is performed on CSI-RS using PDSCH and the scheduling offset between the triggering DCI and CSI-RS is greater than a threshold of the CSI-RS, the spatial QCL assumption indicated by the DCI is applied to CSI-RS reception and the default spatial QCL assumption is applied to PDSCH reception.

[0342] Example 110 may include the subject matter of Example 109 and / or some other examples herein, wherein the default spatial QCL assumption is the QCL assumption of the CORESET with the lowest CORESET ID in the latest time slot.

[0343] Example 111 may include the subject matter of Example 90 or 100 and / or some other examples herein, wherein, if FDM is performed on CSI-RS using PDSCH and the scheduling offset between the triggering DCI and CSI-RS is greater than a threshold for CSI-RS, the spatial QCL assumption indicated by the DCI is applied to CSI-RS reception and the same spatial QCL assumption is applied to possible PDSCH reception.

[0344] Example 112 may include the subject matter of Example 90 or 100 and / or some other examples herein, wherein, if FDM is performed on the CSI-RS using PDSCH and the scheduling offset between the triggered DCI and the CSI-RS is greater than a threshold for the CSI-RS, the spatial QCL assumption of the CSI-RS follows the QCL assumption for possible PDSCH reception.

[0345] Example 113 may include the subject matter of Example 90 and / or some other examples herein, wherein FDM between CSI-RS and PDSCH is not allowed.

[0346] Example 114 may include the subject matter of Example 90 and / or some other examples herein, wherein the scheduling offset between the triggered DCI and the CSI-RS is set to be less than a specific threshold and the default spatial QCL assumption is applied to CSI-RS reception.

[0347] Example 115 may include the subject matter of Example 114 and / or some other examples herein, wherein the default spatial QCL assumption is the QCL assumption that triggered the DCI or the QCL assumption of the CORESET with the lowest CORESET ID in the latest time slot.

[0348] Example 116 may include the subject matter of Example 90 and / or some other examples herein, wherein, when the CSI-RS is triggered, there are no other PDCCH CORESET listening opportunities between the triggered DCI and the CSI-RS.

[0349] Example 117 may include the subject matter of Example 90 and / or some other examples herein, wherein the BS is configured to schedule a PDSCH with a scheduling offset higher than a threshold reported by the UE when configuring one or more component carriers (CCs).

[0350] Example 118 may include the subject matter of Example 90 and / or some other examples herein, wherein the UE is configured to receive each symbol that may be allocated to a PDSCH transmission using a default Rx beam.

[0351] Example 119 may include the subject matter of Example 117 and / or some other examples herein, wherein the UE is configured to receive all possible symbols of the PDSCH using a default Rx beam from a primary cell (PCell) in the absence of a beam indication.

[0352] Example 120 may include the subject matter of Example 90 and / or some other examples herein, wherein, if the CSI-RS is not multiplexed with PDSCH and the scheduling offset between the triggered DCI and the CSI-RS is less than a threshold for the CSI-RS, a default spatial QCL assumption is applied to the CSI-RS.

[0353] Example 121 may include the subject matter of Example 120 and / or some other examples herein, wherein the default spatial QCL assumption is the QCL assumption that triggered the DCI or the QCL assumption of the CORESET with the lowest CORESET ID in the latest time slot.

[0354] Example 122 may include a method for quasi-co-location (QCL) indication of an aperiodic tracking reference signal (A-TRS), comprising: at a gNB, encoding an aperiodic channel state information reference signal (CSI-RS) for beam management that arrives at a user equipment (UE); and causing the UE to determine a spatial quasi-co-location (QCL) assumption of the CSI-RS based on a scheduling offset between triggering downlink control information (DCI) for triggering the CSI-RS and the CSI-RS.

[0355] Example 123 may include the subject matter of Example 122 and / or some other examples herein, wherein the CSI-RS is configured with a parameter CSI-RS-ResourceRep to indicate a repetition of a Tx beam from the gNB.

[0356] Example 124 may include the subject matter of Example 123 and / or some other examples herein, wherein, when CSI-RS-ResourceRep indicates a repeated Tx beam and the scheduling offset is less than a threshold of the CSI-RS, a default spatial QCL assumption is applied to the CSI-RS within the threshold range, and UE Rx beam scanning is performed for the CSI-RS outside the threshold range.

[0357] Example 125 may include the subject matter of Example 123 and / or some other examples herein, wherein, when CSI-RS-ResourceRep indicates non-repeating Tx beams and the scheduling offset is less than a threshold for the CSI-RS, a default spatial QCL assumption is applied to all triggered CSI-RSs.

[0358] Example 126 may include the subject matter of Example 124 or 125 and / or some other examples herein, wherein the default spatial QCL assumption is the same as the control resource set (CORESET) that triggers the CSI-RS or the lowest CORESET in the latest time slot.

[0359] Example 127 may include the subject matter of Example 122 and / or some other examples herein, wherein the CSI measurement is discarded if the same UE Rx beam is not guaranteed for channel measurement resources (CMR) and interference measurement resources (IMR) that do not exist in the same time slot.

[0360] Example 128 may include the subject matter of Example 122 and / or some other examples herein, wherein, if the CSI-RS is frequency division multiplexed (FDM) using a physical downlink shared channel (PDSCH), the spatial QCL assumption of the CSI-RS follows the QCL assumption used for PDSCH reception.

[0361] Example 129 may include the subject matter of Example 122 and / or some other examples herein, wherein, if the CSI-RS is time division multiplexed (TDM) using a physical downlink shared channel (PDSCH), then when the scheduling offset is less than a threshold, a default spatial QCL assumption of the CSI-RS is applied, and the spatial QCL assumption of the CSI-RS follows the QCL configuration indicated by the DCI.

[0362] Example 130 may include the subject matter of Example 129 and / or some other examples herein, wherein the default spatial QCL assumption for CSI-RS follows the QCL assumption for PDSCH reception, or is the QCL assumption that triggered the DCI or the QCL assumption of the lowest CORESET ID in the latest time slot.

[0363] Example 131 may include the subject matter of Example 122 and / or some other examples herein, wherein, if a scheduling offset between a triggered DCI and CSI-RS is greater than a threshold for the CSI-RS and a scheduling offset between the DCI and the PDSCH is less than a threshold for the PDSCH, the default spatial QCL assumption for the CSI-RS follows the QCL assumption for CSI-RS reception indicated by the DCI, or the indicated QCL assumption for the CSI-RS is discarded.

[0364] Example 132 may include the subject matter of Example 122 and / or some other examples herein, wherein, if the scheduling offset between the triggering DCI and the CSI-RS is greater than a threshold of the CSI-RS, and the time offset between the starting point of the CSI-RS and the latest physical downlink control channel (PDCCH) CORESET listening opportunity is less than a threshold determined for the PDSCH default spatial QCL assumption, the spatial QCL assumption of the CSI-RS indicated by the DCI is discarded.

[0365] Example 133 may include the subject matter of Example 122 and / or some other examples herein, wherein, if the scheduling offset between the triggering DCI and the CSI-RS is greater than a threshold for the CSI-RS, and there are additional PDCCH CORESET listening opportunities between the CSI-RS and the triggering DCI, and the time offset between the starting point of the CSI-RS and the latest physical downlink control channel (PDCCH) CORESET listening opportunity is less than a threshold determined for the PDSCH default spatial QCL assumption, then the spatial QCL assumption for the CSI-RS indicated by the DCI is discarded, and the spatial QCL assumption follows the QCL assumption of the CORESET with the lowest CORESET ID in the PDSCH or the latest time slot; or the spatial QCL assumption for PDSCH reception follows the indicated QCL assumption for the CSI-RS regardless of whether the CSI-RS is FDM or TDM with the PDSCH.

[0366] Example 134 may include the subject matter of Example 122 or 132 and / or some other examples in this document, wherein, if TDM is performed on CSI-RS using PDSCH and the scheduling offset between the triggering DCI and CSI-RS is greater than a threshold of the CSI-RS, the spatial QCL assumption indicated by the DCI is applied to CSI-RS reception and the default spatial QCL assumption is applied to PDSCH reception.

[0367] Example 135 may include the subject matter of Example 133 and / or some other examples herein, wherein the default spatial QCL assumption is the QCL assumption of the CORESET with the lowest CORESET ID in the latest time slot.

[0368] Example 136 may include the subject matter of Example 122 or 132 and / or some other examples herein, wherein, if FDM is performed on CSI-RS using PDSCH and the scheduling offset between the triggering DCI and CSI-RS is greater than a threshold for CSI-RS, the spatial QCL assumption indicated by the DCI is applied to CSI-RS reception and the same spatial QCL assumption is applied to possible PDSCH reception.

[0369] Example 137 may include the subject matter of Example 122 or 132 and / or some other examples herein, wherein, if FDM is performed on the CSI-RS using PDSCH and the scheduling offset between the triggered DCI and the CSI-RS is greater than a threshold for the CSI-RS, the spatial QCL assumption for the CSI-RS follows the QCL assumption for possible PDSCH reception.

[0370] Example 138 may include the subject matter of Example 122 and / or some other examples herein, wherein FDM between CSI-RS and PDSCH is not allowed.

[0371] Example 139 may include the subject matter of Example 122 and / or some other examples herein, wherein the scheduling offset between the triggered DCI and the CSI-RS is set to be less than a specific threshold and a default spatial QCL assumption is applied to CSI-RS reception.

[0372] Example 140 may include the subject matter of Example 139 and / or some other examples herein, wherein the default spatial QCL assumption is the QCL assumption that triggered the DCI or the QCL assumption of the CORESET with the lowest CORESET ID in the latest time slot.

[0373] Example 141 may include the subject matter of Example 122 and / or some other examples herein, wherein, when CSI-RS is triggered, there are no other PDCCH CORESET monitoring opportunities between triggering DCI and CSI-RS.

[0374] Example 142 may include the subject matter of Example 122 and / or some other examples herein, wherein the BS is configured to schedule a PDSCH with a scheduling offset higher than a threshold reported by the UE when configuring one or more component carriers (CCs).

[0375] Example 143 may include the subject matter of Example 122 and / or some other examples herein, wherein the UE is configured to receive each symbol that may be allocated to a PDSCH transmission using a default Rx beam.

[0376] Example 144 may include the subject matter of Example 142 and / or some other examples herein, wherein the UE is configured to receive all possible symbols of the PDSCH using a default Rx beam from a primary cell (PCell) without a beam indication.

[0377] Example 145 may include the subject matter of Example 122 and / or some other examples herein, wherein, if the CSI-RS is not multiplexed with PDSCH and the scheduling offset between the triggering DCI and the CSI-RS is less than a threshold for the CSI-RS, a default spatial QCL assumption is applied to the CSI-RS.

[0378] Example 146 may include the subject matter of Example 145 and / or some other examples herein, wherein the default spatial QCL assumption is the QCL assumption that triggered the DCI or the QCL assumption of the CORESET with the lowest CORESET ID in the latest time slot.

[0379] Example 147 may include an apparatus comprising a module for performing one or more elements of a method described or related to any of Examples 83 to 146 or other methods or processes described herein.

[0380] Example 148 may include one or more non-transitory computer-readable media comprising instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of a method described in or related to any of Examples 83 to 146 or other methods or processes described herein.

[0381] Example 149 may include a device comprising logic, modules, or circuits for performing one or more elements of a method described or related to any of Examples 83 to 146 or other methods or processes described herein.

[0382] Example 150 may include a method, technique, or process described or related to any one of Examples 83 to 146, or a portion thereof.

[0383] Example 151 may include a device comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process, or portion thereof, described in or related to any of Examples 83 to 146.

[0384] Example 152 may include a signal or portion thereof described or related to any one of Examples 83 to 146.

[0385] Example 153 may include an apparatus for a user equipment (UE), comprising: an interface, the UE being configured to communicate with an access node (AN) through the interface; one or more processors coupled to the interface and configured to: at the UE, decode an aperiodic tracking reference signal (A-TRS) from the AS via a physical downlink shared channel (PDSCH); and at the UE, determine a QCL assumption of the A-TRS based on quasi-co-location (QCL) configuration information and a comparison between a scheduling offset and a threshold, the scheduling offset being a scheduling offset between a physical downlink control channel (PDCCH) that schedules the A-TRS and the A-TRS, wherein the QCL configuration information includes an indication of QCL type A or QCL type D.

[0386] Example 154 may include the subject matter of Example 153 and / or some other examples herein, wherein the QCL type A represents QCL assumptions about Doppler shift, Doppler spread, average delay, or delay spread, and the QCL type D represents QCL assumptions about spatial receive (Rx) parameters.

[0387] Example 155 may include the subject matter of Example 153 and / or some other examples herein, wherein the QCL configuration information includes an indication of QCL type D, and the one or more processors set the scheduling offset between the last symbol of the PDCCH and each A-TRS resource to be higher than the threshold and determine to QCL the A-TRS using the QCL configuration information included in the PDCCH.

[0388] Example 156 may include the subject matter of Example 153 and / or some other examples herein, wherein the QCL configuration information includes an indication of QCL type D, and the one or more processors: based on determining that the scheduling offset between the last symbol of the PDCCH and each A-TRS resource is lower than or equal to the threshold, determine to perform QCL on the A-TRS using the latest control resource set (CORESET) ID with the lowest CORESET, wherein CORESET 0 and / or CORESET for beam failure recovery are excluded; based on determining that the scheduling offset between the last symbol of the PDCCH and each A-TRS resource is greater than the threshold, determine to perform QCL on the A-TRS using the QCL configuration information indicated by the PDCCH.

[0389] Example 157 may include the subject matter of Example 153 and / or some other examples herein, wherein the QCL configuration information is derived from QCL parameters configured in a radio resource control (RRC) layer that triggers the A-TRS resource set, regardless of the scheduling offset.

[0390] Example 158 may include the subject matter of Example 153 and / or some other examples herein, wherein the QCL type D is not configured for A-TRS such that the A-TRS is used only for frequency range (FR) 1, and the QCL type D is configured for A-TRS such that the A-TRS is used only for FR 2.

[0391] Example 159 may include the subject matter of Example 158 and / or some other examples herein, wherein the FR 1 is below 6 GHz and the FR 2 is above 6 GHz.

[0392] Example 160 may include an apparatus for a user equipment (UE), comprising: an interface, the UE being configured to communicate with an access node (AN) through the interface; one or more processors coupled to the interface and configured to: at the UE, decode a non-periodic channel state information reference signal (CSI-RS) for beam management from the AN via a physical downlink shared channel (PDSCH); and at the UE, determine a spatial quasi-co-location (QCL) assumption of the CSI-RS based on a comparison of a scheduling offset between downlink control information (DCI) for triggering the CSI-RS and the CSI-RS and a threshold for the CSI-RS.

[0393] Example 161 may include the subject matter of Example 160 and / or some other examples herein, wherein the CSI-RS is configured with a parameter CSI-RS-ResourceRep to indicate a repetition of a transmit (Tx) beam from the AN.

[0394] Example 162 may include the subject matter of Example 161 and / or some other examples herein, wherein, based on determining that the CSI-RS-ResourceRep indicates repeating the Tx beam and the scheduling offset is less than the threshold, the one or more processors determine that a default spatial QCL assumption is applied to the CSI-RS within a threshold range, and perform UE receive (Rx) beam scanning for the CSI-RS outside the threshold range.

[0395] Example 163 may include the subject matter of Example 161 and / or some other examples herein, wherein, based on determining that the CSI-RS-ResourceRep indicates non-repetition of the Tx beam and the scheduling offset is less than a threshold of the CSI-RS, the one or more processors determine that a default spatial QCL assumption is applied to all CSI-RS.

[0396] Example 164 may include the subject matter of Example 162 or 163 and / or some other examples herein, wherein the default spatial QCL assumption is the same as the lowest CORESET in the control resource set (CORESET) that triggers the CSI-RS or the latest time slot.

[0397] Example 165 may include the subject matter of Example 160 and / or some other examples herein, wherein the one or more processors determine to discard CSI measurements based on determining that the same UE Rx beam is not guaranteed for channel measurement resources (CMRs) and interference measurement resources (IMRs) that do not exist in the same time slot.

[0398] Example 166 may include the subject matter of Example 160 and / or some other examples herein, wherein, based on determining that the CSI-RS is frequency division multiplexed (FDM) utilizing the PDSCH, the one or more processors determine that the spatial QCL assumption of the CSI-RS follows the spatial QCL assumption used for PDSCH reception.

[0399] Example 167 may include the subject matter of Example 160 and / or some other examples herein, wherein, based on determining that the CSI-RS is time division multiplexed (TDM) using the PDSCH, the one or more processors determine that when the scheduling offset is less than the threshold, a default spatial QCL assumption of the CSI-RS is applied, and when the scheduling offset is greater than the threshold, the spatial QCL assumption of the CSI-RS follows the QCL configuration indicated by the DCI, wherein the default spatial QCL assumption of the CSI-RS follows one of the spatial QCL assumption for PDSCH reception, the spatial QCL assumption of the DCI, and the spatial QCL assumption of the CORESET with the lowest CORESETID in the latest time slot.

[0400] Example 168 may include the subject matter of Example 160 and / or some other examples herein, wherein, based on determining that the scheduling offset between the DCI and the CSI-RS is greater than a threshold of the CSI-RS, and the scheduling offset between the DCI and the PDSCH is less than a threshold of the PDSCH, the one or more processors determine that a default spatial QCL assumption for the CSI-RS follows the spatial QCL assumption for CSI-RS reception indicated by the DCI, or discards the QCL assumption for the CSI-RS indicated by the DCI.

[0401] Example 169 may include the subject matter of Example 160 and / or some other examples herein, wherein, based on determining that the scheduling offset between the DCI and the CSI-RS is greater than a threshold of the CSI-RS, and the time offset between the starting point of the CSI-RS and the latest physical downlink control channel (PDCCH) CORESET listening opportunity is less than a threshold determined for the PDSCH default spatial QCL assumption, the one or more processors determine to discard the spatial QCL assumption of the CSI-RS indicated by the DCI.

[0402] Example 170 may include the subject matter of Example 160 and / or some other examples herein, wherein, based on determining that the scheduling offset between the triggering DCI and the CSI-RS is greater than a threshold of the CSI-RS, and there are additional physical downlink control channel (PDCCH) CORESET listening opportunities between the CSI-RS and the triggering DCI, and the time offset between the starting point of the CSI-RS and the latest PDCCH CORESET listening opportunity is less than a threshold determined for the PDSCH default spatial QCL assumption, the one or more processors determine: the spatial QCL assumption of the CSI-RS follows the spatial QCL assumption of the CORESET with the lowest CORESET ID in the PDSCH or the latest time slot; or regardless of whether the CSI-RS is FDM or TDM with the PDSCH, the spatial QCL assumption for PDSCH reception follows the indicated QCL assumption for the CSI-RS.

[0403] Example 171 may include the subject matter of Example 160 or 169 and / or some other examples herein, wherein, based on determining that the CSI-RS is TDMed using the PDSCH and the scheduling offset between the DCI and the CSI-RS is greater than a threshold of the CSI-RS, the one or more processors determine that the spatial QCL assumption indicated by the DCI is applied to CSI-RS reception and the default spatial QCL assumption is applied to PDSCH reception, wherein the default spatial QCL assumption is the spatial QCL assumption of the CORESET with the lowest CORESET ID in the latest time slot.

[0404] Example 172 may include the subject matter of Example 160 or 169 and / or some other examples herein, wherein, based on determining that FDM is performed on the CSI-RS using the PDSCH and that the scheduling offset between the DCI and the CSI-RS is greater than a threshold of the CSI-RS, the one or more processors determine that the spatial QCL assumption indicated by the DCI is applied to CSI-RS reception and that the same spatial QCL assumption is applied to PDSCH reception.

[0405] Example 173 may include the subject matter of Example 160 or 169 and / or some other examples herein, wherein, based on determining that FDM is performed on the CSI-RS using the PDSCH and that the scheduling offset between the DCI and the CSI-RS is greater than a threshold of the CSI-RS, the one or more processors determine that the spatial QCL assumption of the CSI-RS follows the spatial QCL assumption used for PDSCH reception.

[0406] Example 174 may include the subject matter of Example 160 and / or some other examples herein, wherein the one or more processors determine to set the scheduling offset between the DCI and the CSI-RS to be less than the threshold, and determine that a default spatial QCL assumption is applied to the CSI-RS reception, wherein the default spatial QCL assumption is the spatial QCL assumption of the triggered DCI or the spatial QCL assumption of the CORESET with the lowest CORESET ID in the latest time slot.

[0407] Example 175 may include the subject matter of Example 160 and / or some other examples herein, wherein, based on determining that the CSI-RS is not multiplexed with the PDSCH and the scheduling offset between the DCI and the CSI-RS is less than a threshold of the CSI-RS, a default spatial QCL assumption is applied to the CSI-RS, wherein the default spatial QCL assumption is the spatial QCL assumption of the triggered DCI or the spatial QCL assumption of the CORESET with the lowest CORESET ID in the latest time slot.

[0408] Example 176 may include one or more computer-readable media, including instructions, which, when executed by one or more processors of a user equipment (UE), cause the processor to: at the UE, decode a non-periodic channel state information reference signal (CSI-RS) for beam management from the AN via a physical downlink shared channel (PDSCH); and at the UE, determine a spatial quasi-co-location (QCL) assumption of the CSI-RS based on a comparison of a scheduling offset between downlink control information (DCI) for triggering the CSI-RS and the CSI-RS and a threshold for the CSI-RS.

[0409] As used herein, the term "circuit" may refer to, be part of, or include an application specific integrated circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group) and / or memory (shared, dedicated, or group) that executes one or more software or firmware programs, a combinational logic circuit, and / or other suitable hardware components that provide the functionality. In some aspects, a circuit may be implemented in one or more software or firmware modules, or the functionality associated with a circuit may be implemented by one or more software or firmware modules. In some aspects, a circuit may include logic that operates at least partially in hardware.

[0410] Various techniques or some aspects or parts thereof may take the form of program codes (i.e., instructions) embodied in tangible media, such as floppy disks, compact disk read-only memories (CD-ROMs), hard disk drives, transient or non-transient computer-readable storage media, or any other machine-readable storage media, wherein when the program code is loaded into and executed by a machine such as a computer, the machine becomes a device for practicing various techniques. Circuits may include hardware, firmware, program codes, executable codes, computer instructions, and / or software. Non-transient computer-readable storage media may be computer-readable storage media that do not include signals. In the case of executing program codes on a programmable computer, a computing device may include a processor, a storage medium (including volatile and non-volatile memory and / or storage elements) readable by the processor, at least one input device, and at least one output device. Volatile and non-volatile memory and / or storage elements may be random access memory (RAM), erasable programmable read-only memory (EPROM), flash drives, optical disk drives, magnetic hard disk drives, solid-state drives, or other media for storing electronic data. Nodes and wireless devices may also include transceiver modules (i.e., transceivers), calculator modules (i.e., calculators), processing modules (i.e., processors), and / or clock modules (i.e., clocks) or timer modules (i.e., timers). One or more programs that may implement or utilize the various techniques described herein may use application programming interfaces (APIs), reusable controls, and the like. Such programs may be implemented in high-level programs or object-oriented programming languages ​​to communicate with a computer system. However, if desired, the program may be implemented in assembly or machine language. In any case, the language may be a compiled or interpreted language, and combined with a hardware implementation.

[0411] It should be understood that many of the functional units described in this specification have been labeled as modules in order to more particularly emphasize their implementation independence. For example, a module can be implemented as a hardware circuit including a customized very large scale integration (VLSI) circuit or gate array, an off-the-shelf semiconductor such as a logic chip, a transistor or other discrete component. A module can also be implemented in a programmable hardware device such as a field programmable gate array / programmable array logic / programmable logic device.

[0412] Modules may also be implemented in software for execution by various types of processors. An identifiable executable code module may, for example, include one or more physical or logical blocks of computer instructions, which may, for example, be organized as objects, processes, or functions. However, the executable files of the identified modules may not be physically located together, but may include different instructions stored in different locations, which, when logically combined together, constitute the module and achieve the stated purpose of the module.

[0413] In fact, the module of executable code can be a single instruction or many instructions, and can even be distributed on several different code segments, between different programs and on several memory devices. Similarly, operational data can be identified and shown in this article in the module, and can be embodied and organized in the data structure of any suitable type in any suitable form. Operational data can be collected as a single data set, or can be distributed on different locations including different storage devices, and can exist at least in part as an electronic signal on a system or network. These modules can be passive or active, including agents that can be operated to realize the desired function.

[0414] References throughout this specification to "example" or "exemplary" mean that a particular feature, structure, or characteristic described in conjunction with the example is included in at least one embodiment of the present technology. Thus, the phrase "in an example" or the word "exemplary" appearing in various places throughout this specification do not necessarily all refer to the same embodiment.

[0415] As used herein, for convenience, multiple items, structural elements, constituent elements and / or materials may be presented in a common list. However, these lists should be interpreted as each component in the list being individually identified as a separate and unique component. Therefore, any component in such a list should not be interpreted as being in fact equivalent to any other component in the same list based solely on their presentation in a common group without any contrary representation. In addition, various embodiments and examples of the present technology may be cited herein together with alternatives to its various components. It should be understood that these embodiments, examples and alternatives should not be interpreted as in fact equivalents to each other, but should be interpreted as separate and autonomous representations of the present technology.

[0416] In addition, in one or more embodiments, the described features, structures or characteristics may be combined in any suitable manner. In the following description, many specific details, such as examples of layouts, distances, network examples, etc., are provided to provide a comprehensive understanding of embodiments of the present technology. However, those skilled in the relevant art will recognize that the technology can be practiced without one or more of the specific details, or with other methods, components, layouts, etc. In other cases, well-known structures, materials, or operations are not shown or described in detail to avoid covering up aspects of the technology.

[0417] Although the foregoing examples illustrate the principles of the present technology in one or more specific applications, it is obvious to those skilled in the art that various modifications can be made in the form, use, and details of the implementation without inventive effort and without departing from the principles and concepts of the technology. Therefore, it is not intended to limit the technology except as set forth in the claims below.

Claims

1. A device for user equipment UE, comprising: an interface, the UE being configured to communicate with an access node AN through the interface; One or more processors coupled to the interface and configured to: Decoding an aperiodic channel state information reference signal CSI-RS for beam management from the AN through a physical downlink shared channel PDSCH; and determining a spatial quasi-co-located QCL assumption for the aperiodic CSI-RS based on a comparison of a scheduling offset with a threshold for the CSI-RS, the scheduling offset being an offset between downlink control information DCI for triggering the CSI-RS and the CSI-RS, wherein the QCL configuration information includes an indication of a QCL type A or a QCL type D, Wherein, based on determining that the scheduling offset between the DCI and the CSI-RS is greater than a threshold for the CSI-RS and the scheduling offset between the DCI and the PDSCH is less than a threshold for the PDSCH, the one or more processors are used to determine that the default spatial QCL assumption for the CSI-RS follows the spatial QCL assumption for CSI-RS reception indicated by the DCI or discards the spatial QCL assumption for CSI-RS reception indicated by the DCI.

2. The device according to claim 1, wherein: The CSI-RS is configured with a parameter CSI-RS-ResourceRep to indicate the repetition of the transmit Tx beam from the AN.

3. The device according to claim 2, wherein: Based on determining that the CSI-RS-ResourceRep indicates repetition of the Tx beam and the scheduling offset between the DCI and the CSI-RS is less than the threshold for the CSI-RS, the one or more processors are used to determine that a default spatial QCL assumption is applied to the CSI-RS within the range of the threshold, and perform user equipment UE receive Rx beam scanning for the CSI-RS outside the range of the threshold.

4. The device according to claim 2, wherein: Based on determining that the CSI-RS-ResourceRep indicates that the Tx beam is not repeated and the scheduling offset between the DCI and the CSI-RS is less than the threshold for CSI-RS, the one or more processors are used to determine that a default spatial QCL assumption is applied to all CSI-RS.

5. The device according to claim 3 or 4, wherein: The default spatial QCL is assumed to be the same as the control resource set CORESET used to trigger the CSI-RS or the lowest CORESET in the latest slot.

6. The device according to claim 1, wherein: Based on determining that the same UE Rx beam is not guaranteed for the channel measurement resources CMR and the interference measurement resources IMR not existing in the same time slot, the one or more processors are used to determine to discard the CSI measurement.

7. The device according to claim 1, wherein: Based on determining that the CSI-RS is frequency division multiplexed (FDM) with the PDSCH, the one or more processors are configured to determine that a spatial QCL assumption for the CSI-RS follows a spatial QCL assumption for PDSCH reception.

8. The device according to claim 1, wherein: Based on determining to time division multiplex TDM the CSI-RS using the PDSCH, the one or more processors are configured to determine that when the scheduling offset between the DCI and the CSI-RS is less than the threshold for the CSI-RS, a default spatial QCL assumption for the CSI-RS is applied, and when the scheduling offset between the DCI and the CSI-RS is greater than the threshold for the CSI-RS, the spatial QCL assumption for the CSI-RS follows the QCL configuration indicated by the DCI, Among them, the default spatial QCL assumption for CSI-RS follows the spatial QCL assumption for PDSCH reception, the spatial QCL assumption for DCI, and one of the spatial QCL assumptions of the CORESET with the lowest CORESET ID in the latest time slot.

9. The device according to claim 1, wherein: Based on determining that the scheduling offset between the DCI and the CSI-RS is greater than a threshold for the CSI-RS, and the time offset between the starting point of the CSI-RS and the latest physical downlink control channel PDCCHCORESET monitoring opportunity is less than a threshold determined for the PDSCH default spatial QCL assumption, the one or more processors are used to determine to discard the spatial QCL assumption for the CSI-RS indicated by the DCI.

10. The device according to claim 1, wherein: Based on determining that a scheduling offset between the DCI and the CSI-RS is greater than a threshold for the CSI-RS, and that an additional physical downlink control channel PDCCH CORESET monitoring opportunity exists between the CSI-RS and the DCI, and that a time offset between a starting point of the CSI-RS and a latest PDCCH CORESET monitoring opportunity is less than a threshold determined for a PDSCH default spatial QCL assumption, the one or more processors are configured to determine: The spatial QCL assumption for CSI-RS follows the spatial QCL assumption of the CORESET with the lowest CORESET ID in the PDSCH or latest slot; or Regardless of whether the CSI-RS is FDMed or TDMed with PDSCH, the spatial QCL assumption for PDSCH reception follows the indicated QCL assumption for CSI-RS.

11. The device according to claim 1 or 9, wherein: Based on determining that the CSI-RS is TDMed using the PDSCH and the scheduling offset between the DCI and the CSI-RS is greater than a threshold for the CSI-RS, the one or more processors are used to determine that the spatial QCL assumption indicated by the DCI is applied to CSI-RS reception and the default spatial QCL assumption is applied to PDSCH reception, wherein the default spatial QCL assumption is the spatial QCL assumption of the CORESET with the lowest CORESET ID in the latest time slot.

12. The device according to claim 1 or 9, wherein: Based on determining that the CSI-RS is FDMed using the PDSCH and that the scheduling offset between the DCI and the CSI-RS is greater than a threshold for the CSI-RS, the one or more processors are used to determine that a spatial QCL assumption indicated by the DCI is applied to CSI-RS reception and that the same spatial QCL assumption is applied to PDSCH reception.

13. The device according to claim 1 or 9, wherein: Based on determining that the CSI-RS is FDMed using the PDSCH and that the scheduling offset between the DCI and the CSI-RS is greater than a threshold for the CSI-RS, the one or more processors are configured to determine that a spatial QCL assumption for the CSI-RS follows a spatial QCL assumption for PDSCH reception.

14. The device according to claim 1, wherein: The one or more processors are used to set the scheduling offset between the DCI and the CSI-RS to be less than the threshold, and determine that a default spatial QCL assumption is applied to the CSI-RS reception, wherein the default spatial QCL assumption is the spatial QCL assumption used for the DCI or the spatial QCL assumption of the CORESET with the lowest CORESET ID in the latest time slot.

15. The device according to claim 1, wherein: Based on determining that the CSI-RS is not multiplexed with the PDSCH and the scheduling offset between the DCI and the CSI-RS is less than a threshold for the CSI-RS, a default spatial QCL assumption is applied to the CSI-RS, wherein the default spatial QCL assumption is the spatial QCL assumption for the DCI or the spatial QCL assumption of the CORESET with the lowest CORESET ID in the latest time slot.

16. A method for user equipment UE, comprising: Decoding a non-periodic channel state information reference signal CSI-RS for beam management from the access node AN through the physical downlink shared channel PDSCH; and determining a spatial quasi-co-located QCL assumption for the aperiodic CSI-RS based on a comparison of a scheduling offset with a threshold for the CSI-RS, the scheduling offset being an offset between downlink control information DCI for triggering the CSI-RS and the CSI-RS, wherein the QCL configuration information includes an indication of a QCL type A or a QCL type D, The method also includes: based on determining that the scheduling offset between the DCI and the CSI-RS is greater than a threshold for the CSI-RS and the scheduling offset between the DCI and the PDSCH is less than a threshold for the PDSCH, determining that the default spatial QCL assumption for the CSI-RS follows the spatial QCL assumption for CSI-RS reception indicated by the DCI.

17. The method according to claim 16, wherein: The CSI-RS is configured with a parameter CSI-RS-ResourceRep to indicate the repetition of the transmit Tx beam from the AN.

18. The method according to claim 17, wherein: The method also includes: based on determining that the CSI-RS-ResourceRep indicates repetition of the Tx beam and the scheduling offset between the DCI and the CSI-RS is less than the threshold for the CSI-RS, determining that a default spatial QCL assumption is applied to the CSI-RS within the range of the threshold, and performing user equipment UE receive Rx beam scanning for the CSI-RS outside the range of the threshold.

19. The method according to claim 17, wherein: The method also includes determining that a default spatial QCL assumption is applied to all CSI-RSs based on determining that the CSI-RS-ResourceRep indicates that the Tx beam is not repeated and the scheduling offset between the DCI and the CSI-RS is less than the threshold for CSI-RS.

20. The method according to claim 18 or 19, wherein: The default spatial QCL is assumed to be the same as the control resource set CORESET used to trigger the CSI-RS or the lowest CORESET in the latest slot.

21. The method according to claim 16, wherein: The method further includes determining to discard the CSI measurement based on determining that the same UE Rx beam is not guaranteed for the channel measurement resources CMR and the interference measurement resources IMR not existing in the same time slot.

22. The method according to claim 16, wherein: The method further includes: based on determining to frequency division multiplex (FDM) the CSI-RS using the PDSCH, determining that a spatial QCL assumption for the CSI-RS follows a spatial QCL assumption for PDSCH reception.

23. The method according to claim 16, wherein: The method further includes: based on determining to time division multiplex TDM the CSI-RS using the PDSCH, determining that when the scheduling offset between the DCI and the CSI-RS is less than the threshold for the CSI-RS, a default spatial QCL assumption for the CSI-RS is applied, and when the scheduling offset between the DCI and the CSI-RS is greater than the threshold for the CSI-RS, a spatial QCL assumption for the CSI-RS follows the QCL configuration indicated by the DCI, Among them, the default spatial QCL assumption for CSI-RS follows the spatial QCL assumption for PDSCH reception, the spatial QCL assumption for DCI, and one of the spatial QCL assumptions of the CORESET with the lowest CORESET ID in the latest time slot.

24. The method according to claim 16, wherein: The method also includes: determining to discard the spatial QCL assumption for the CSI-RS indicated by the DCI based on determining that the scheduling offset between the DCI and the CSI-RS is greater than a threshold for the CSI-RS, and the time offset between the starting point of the CSI-RS and the latest physical downlink control channel PDCCH CORESET monitoring opportunity is less than a threshold determined for the PDSCH default spatial QCL assumption.

25. The method of claim 16, wherein: The method further includes: based on determining that a scheduling offset between the DCI and the CSI-RS is greater than a threshold for the CSI-RS, and an additional physical downlink control channel PDCCH CORESET monitoring opportunity exists between the CSI-RS and the DCI, and a time offset between a starting point of the CSI-RS and a latest PDCCH CORESET monitoring opportunity is less than a threshold determined for a PDSCH default spatial QCL assumption, The spatial QCL assumption for CSI-RS follows the spatial QCL assumption of the CORESET with the lowest CORESET ID in the PDSCH or latest slot; or Regardless of whether the CSI-RS is FDMed or TDMed with PDSCH, the spatial QCL assumption for PDSCH reception follows the indicated QCL assumption for CSI-RS.

26. The method according to claim 16 or 24, wherein: The method also includes: based on determining that the CSI-RS is TDMed using the PDSCH and the scheduling offset between the DCI and the CSI-RS is greater than a threshold for the CSI-RS, determining that the spatial QCL assumption indicated by the DCI is applied to CSI-RS reception and the default spatial QCL assumption is applied to PDSCH reception, wherein the default spatial QCL assumption is the spatial QCL assumption of the CORESET with the lowest CORESET ID in the latest time slot.

27. The method according to claim 16 or 24, wherein: The method also includes: based on determining that FDM is performed on the CSI-RS using the PDSCH and that the scheduling offset between the DCI and the CSI-RS is greater than a threshold for the CSI-RS, determining that the spatial QCL assumption indicated by the DCI is applied to CSI-RS reception and the same spatial QCL assumption is applied to PDSCH reception.

28. The method according to claim 16 or 24, wherein: The method also includes: based on determining that the CSI-RS is FDMed using the PDSCH and the scheduling offset between the DCI and the CSI-RS is greater than a threshold for the CSI-RS, determining that the spatial QCL assumption for the CSI-RS follows the spatial QCL assumption for PDSCH reception.

29. The method of claim 16, wherein: The method also includes: setting the scheduling offset between the DCI and the CSI-RS to be less than the threshold, and determining that a default spatial QCL assumption is applied to the CSI-RS reception, wherein the default spatial QCL assumption is the spatial QCL assumption used for the DCI or the spatial QCL assumption of the CORESET with the lowest CORESET ID in the latest time slot.

30. The method of claim 16, wherein: Based on determining that the CSI-RS is not multiplexed with the PDSCH and the scheduling offset between the DCI and the CSI-RS is less than a threshold for the CSI-RS, a default spatial QCL assumption is applied to the CSI-RS, wherein the default spatial QCL assumption is the spatial QCL assumption for the DCI or the spatial QCL assumption of the CORESET with the lowest CORESET ID in the latest time slot.

31. A computer-readable medium comprising instructions, which, when executed by one or more processors of a user equipment (UE), cause the processors to implement the method according to any one of claims 16 to 30.

32. A computer program product comprising instructions which, when executed by one or more processors of a user equipment, cause the processors to implement the method of any one of claims 16-30.

Images