CN118523816A - System and method for processing CSI-RS in full-duplex operation mode - Google Patents

Abstract

A system and method for a terminal in a wireless communication system are disclosed. The method includes monitoring at least one of a first condition or a second condition, wherein the first condition includes CSI-RS or PDSCH overlapping with an uplink subband in subband full-duplex operation and becoming non-contiguous in the frequency domain, and wherein the second condition includes a different network antenna mode or power mode being used for CSI-RS transmission in network energy-saving operation; and in response to the first condition or the second condition occurring, relaxing processing requirements related to at least one of a processing timeline or occupied computing resources.

Description

Systems and methods for processing CSI-RS in full duplex mode of operation

Cross Reference to Related Applications

The present application claims priority benefits from U.S. provisional application Ser. Nos. 63/446,614 and 63/455,022, filed on 2 months of 2023 and 28 months of 2023, respectively, the disclosures of each of the foregoing applications are incorporated by reference in their entireties as if fully set forth herein.

Technical Field

The present disclosure relates generally to processing channel state information reference signals (CSI-RS). More particularly, the subject matter disclosed herein relates to improvements to handling CSI-RS in Full Duplex (FD) modes of operation.

Background

Since there is an Uplink (UL) subband in FD operation, CSI-RS or CSI reports may span a wideband and collide with Resource Blocks (RBs) configured/indicated for the UL subband. Thus, it may be beneficial to determine the impact of different solutions on CSI computation time and CSI Processing Unit (CPU) occupation.

In FD operation, the gNB may utilize different antenna elements, different transmit powers, apply different beams, etc. in sub-band full duplex (SBFD) symbols and non-SBFD symbols. Thus, there are also problems encountered in FD operation when the gNB switches between different spatial or power domains for network energy conservation purposes.

The following options in table 1 have been proposed during third generation partnership project (3 GPP) standardization for handling CSI-RS or CSI reports collision with UL subbands.

TABLE 1

As indicated above, in option 1, two CSI-RS resources are associated with one CSI report such that each CSI-RS does not overlap with the UL subband.

In option 2, the same CSI-RS are allocated either in a discontinuous manner in the frequency domain or in a continuous manner in the frequency domain, and the User Equipment (UE) derives a discontinuous portion of the CSI-RS based on the overlap with the UL subband or guard band.

In option 3, the continuous CSI-RS is configured and overlaps with the UL subband. In this case, if any one of CSI-RSs related to CSI reporting collides with an UL subband, the UE skips the entire CSI reporting, skips the CSI subband that collides with the UL subband, or does not require the UE to report the CSI subband that collides with the UL subband.

CSI-RS may also span two sets of Orthogonal Frequency Division Multiplexing (OFDM) symbols in the time domain, one set being SBFD symbols and the other set being non-SBFD symbols. In this case, the same CSI-RS ports may be transmitted in SBFD and non-SBFD symbols, which may affect the measured/reported CSI. Therefore, a solution to deal with this situation is needed.

Furthermore, in the conventional New Radio (NR), when a Tracking Reference Signal (TRS) is configured, it is not associated with any report and does not occupy the CPU. However, the TRS may be further enhanced so that the UE may report Time Domain Channel Properties (TDCPs). Thus, it may be beneficial to use the TRS to report TDCP to determine the timeline, as compared to a TRS that does not make any reports.

Furthermore, if the Precoding Resource Group (PRG) is configured such that the precoding granularity is wideband and the Physical Downlink Shared Channel (PDSCH) is scheduled/configured to span non-contiguous DL subbands, the PDSCH processing timeline should also be defined. In conventional NRs, when the PRG is configured to be wideband, it is not desirable to schedule UEs with non-contiguous Physical Resource Blocks (PRBs), and thus, the UEs may assume that the same precoding is applied to allocated resources associated with the same Transmission Configuration Indication (TCI) state or the same quasi-co-sited (QCL) assumption.

Disclosure of Invention

To overcome these problems, systems and methods are described herein that relax processing requirements in terms of time lines and occupied computing resources when signals (e.g., CSI-RS) or channels (e.g., PDSCH) collide with UL subbands for SBFD operations.

According to one aspect of the present disclosure, a process of adjusting processing time of a discontinuous CSI-RS is provided.

According to another aspect of the present disclosure, an algorithm is provided that reflects the impact of discontinuous CSI-RS on occupied CPU.

According to another aspect of the disclosure, an algorithm is provided that reflects the impact on CPU occupancy when the same CSI-RS or different CSI-RS are associated with different spatial or power modes or sub-configurations during network power saving.

According to another aspect of the present disclosure, a method of accurately reflecting the number of simultaneous active (CSI-RS) is provided.

According to another aspect of the disclosure, a process is provided for handling the case where the same CSI-RS port occupies SBFD and non-SBFD symbols.

According to another aspect of the disclosure, the PDSCH processing timeline is relaxed when PDSCH spans non-contiguous DL subbands and PRG is configured to be wideband.

In accordance with another aspect of the present disclosure, for a TRS for calculating a TDCP, a procedure for acquiring UE processing overhead is provided.

In an embodiment, a method includes monitoring at least one of a first condition or a second condition, wherein the first condition includes that a CSI-RS or PDSCH overlaps with an uplink subband in a subband full duplex operation and becomes discontinuous in the frequency domain, and wherein the second condition includes that a different network antenna mode or power mode is used for CSI-RS transmission in a network power saving operation; and responsive to the first condition or the second condition occurring, relaxing processing requirements associated with at least one of the processing timeline or the occupied computing resources.

In an embodiment, a terminal includes a transceiver; and a processor configured to monitor at least one of a first condition or a second condition, wherein the first condition comprises that the CSI-RS or PDSCH overlaps with an uplink subband in subband full duplex operation and becomes discontinuous in the frequency domain, and wherein the second condition comprises that a different network antenna mode or power mode is used for CSI-RS transmission in network power saving operation; and responsive to the first condition or the second condition occurring, relaxing processing requirements associated with at least one of the processing timeline or the occupied computing resources.

Drawings

In the following sections, aspects of the subject matter disclosed herein will be described with reference to exemplary embodiments shown in the drawings, in which:

Fig. 1 shows an example of a processing timeline of aperiodic CSI reports related to aperiodic CSI-RS or CSI Interference Measurements (IM);

fig. 2 shows an example of a timeline of periodic CSI reporting based on periodic CSI-RS;

FIG. 3 shows an example of CPU occupancy for P/SP CSI reporting;

FIG. 4 illustrates an example of CPU occupancy for aperiodic CSI reporting;

Fig. 5 shows an example in which a predefined value delta is added to the Z' _ref value of the discontinuous CSI-RS according to an embodiment;

fig. 6 illustrates an example of adjusting CSI reference resources and Z' by Δ according to an embodiment;

FIG. 7 illustrates an example of CPU occupancy for P/SP CSI reporting based on P/SP discontinuous CSI-RS in accordance with an embodiment;

fig. 8 is a flowchart illustrating a method performed by a terminal according to an embodiment;

Fig. 9 is a block diagram of an electronic device in a network environment according to an embodiment.

Fig. 10 shows a system including a UE and a gNB in communication with each other.

Detailed Description

In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the present disclosure. However, it will be understood by those skilled in the art that the disclosed aspects may be practiced without these specific details. In other instances, well-known methods, procedures, components, and circuits have not been described in detail so as not to obscure the subject matter disclosed herein.

Reference throughout this specification to "one embodiment" or "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment disclosed herein. Thus, the appearances of the phrase "in one embodiment" or "in an embodiment" or "according to one embodiment" (or other phrases having similar meaning) in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In this regard, as used herein, the word "exemplary" means "serving as an example, instance, or illustration. Any embodiment described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments. Furthermore, depending on the context discussed herein, singular terms may include corresponding plural forms, and plural terms may include corresponding singular forms.

It is also noted that the various figures (including component figures) shown and discussed herein are for illustrative purposes only and are not drawn to scale. For example, the dimensions of some of the elements may be exaggerated relative to other elements for clarity. Furthermore, where considered appropriate, reference numerals have been repeated among the figures to indicate corresponding and/or analogous elements.

The terminology used herein is for the purpose of describing some example embodiments only and is not intended to limit the claimed subject matter. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

It will be understood that when an element or layer is referred to as being "connected to" or "coupled to" another element or layer, it can be directly on, connected or coupled to the other element or layer, or intervening elements or layers may be present. In contrast, when an element or layer is referred to as being "directly on," "directly connected to," or "directly coupled to" another element or layer, there are no intervening elements or layers present. Like numbers refer to like elements throughout. As used herein, the term "and/or" includes any and all combinations of one or more of the associated listed items.

The terms "first," "second," and the like, as used herein, serve as labels for their successor nouns, and do not imply any type of ordering (e.g., spatial, temporal, logical, etc.), unless clearly defined so. Furthermore, the same reference numbers may be used throughout two or more drawings to refer to components, assemblies, blocks, circuits, units, or modules having the same or similar functionality. However, such usage is merely for simplicity of illustration and ease of discussion; it is not intended that the constructional or architectural details of these components or units be the same in all embodiments or that these commonly referenced components/modules be the only way to implement some of the example embodiments disclosed herein.

Unless defined otherwise, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this subject matter belongs. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

As used herein, the term "module" refers to any combination of software, firmware, and/or hardware configured to provide the functionality described herein in connection with the module. For example, software may be embodied as a software package, code, and/or instruction set or instructions, and the term "hardware" as used in any implementation described herein may include, for example, components, hardwired circuitry, programmable circuitry, state machine circuitry, and/or firmware that stores instructions executed by the programmable circuitry, alone or in any combination. These modules may be collectively or individually embodied as circuitry forming part of a larger system, such as, but not limited to, an Integrated Circuit (IC), a system-on-a-chip (SoC), a component, and the like.

CSI processing timeline

Fig. 1 shows an example of a processing timeline of aperiodic CSI reports related to aperiodic CSI-RS or CSI-IM.

Referring to fig. 1, z _ref is defined as a minimum time gap between a last symbol of a Physical Downlink Control Channel (PDCCH) (e.g., downlink Control Information (DCI)) triggering an aperiodic CSI report and a first symbol of a Physical Uplink Shared Channel (PUSCH) carrying the report. The purpose of Z _ref is to ensure that there is enough time for PDCCH detection/decoding to receive CSI report trigger DCI, channel estimation and CSI calculation.

Z' _ref is defined as the minimum time gap between the last symbol carrying an aperiodic CSI-RS for Channel Measurement (CM), an AP-CSI-RS associated with a triggered report, or an AP-CSI-IM. Z' _ref is used when aperiodic CSI reports are associated with the AP-CSI-RS/AP-CSI-IM. When the aperiodic CSI report is associated with a periodic/semi-persistent (P/SP) CSI-RS or CSI-IM, the timeline depends on defining "reference resources", as will be described later.

Here, Z _ref and Z '_ref may also be referred to as Z and Z', respectively.

For aperiodic CSI reporting, the timeline shown in fig. 1 should be satisfied in order for the UE to provide a valid report.

However, if Z _ref is not satisfied, if no hybrid automatic repeat request (HARQ) -Acknowledgement (ACK) or Transport Block (TB) is multiplexed on PUSCH, the UE may ignore the scheduling DCI in the PDCCH.

If Z' _ref is not satisfied, if the number of triggered reports is 1 and no HARQ-ACK or TB is multiplexed on PUSCH, the UE may ignore the scheduling DCI in the PDCCH. Otherwise, the UE is not required to update CSI of the nth triggered CSI report.

When P/SP CSI-RS/CSI-IM is used for channel/interference measurement, the UE is not expected to measure channel/interference on the CSI-RS/CSI-IM, the last OFDM symbol of which is received 0 to Z' symbols before the transmission time of the first OFDM symbol of the AP-CSI report.

Furthermore, the CSI-RS should be on or before the CSI reference resource determined by n _{CSI_ref}, n _{CSI_ref} is greater than or equal toSuch that time slot n-n _{CSI_ref} corresponds to a valid downlink time slot.

Fig. 2 shows an example of a timeline of aperiodic CSI reporting based on periodic CSI-RS.

For P/SP CSI reporting based on P/SP CSI-RS, n _{CSI_ref} is equal to a predefined value provided in 3gpp TS 38.214, based on the DL parameter set (μ) and the number of Reference Signals (RSs) configured for channel measurement.

For example, in the case where CSI reporting does not have CSI-RS resource indicator (CRI), for μ=15khz, n _{CSI_ref} =4; for μ=30 khz, n _{CSI_ref} =8; for μ=60 khz, n _{CSI_ref} =16; for μ=120 khz, n _{CSI_ref} =32. Further, where the CSI report has CRI, n _{CSI_ref} = 5 for μ = 15 khz; for μ=30 khz, n _{CSI_ref} =10; for μ=60 khz, n _{CSI_ref} =20; for μ=120 khz, n _{CSI_ref} =40.

A slot in the serving cell should be considered a valid downlink slot if it includes at least one higher layer configured downlink or flexible symbol and does not fall within the measurement gap configured for the UE.

If there is no valid downlink slot of the CSI reference resource corresponding to the CSI report setting in the serving cell, the CSI report for the serving cell is omitted in the uplink slot n'.

When the DCI triggers multiple aperiodic CSI reports, the values of Z and Z' may be AndWhere M is the number of updated CSI reports, (Z (M), Z' (M)) corresponding to the mth updated CSI report, based on the number of updated CSI reports determined by the available CPU.

A number of tables are provided in 3gpp TS 38.214 for determining Z and Z' based on the amount of reporting.

CPU for CSI processing

The UE indicates to the gNB the total number of available CPUs within one Component Carrier (CC) and across all CCs (N _CPU) via capability signaling (simultaneousCSI-ReportsPerCC and simultaneousCSI-ReportsAllCC).

For CSI reports with CSI-ReportConfig where the higher layer parameter reportquality is set to "none", the CPU is occupied over multiple OFDM symbols.

Fig. 3 shows an example of CPU occupation of P/SP CSI reports.

Referring to fig. 3, a p/SP CSI report (excluding an initial SP CSI report on PUSCH after a PDCCH triggering the report) occupies the CPU from a first symbol of an earliest one of each CSI-RS/CSI-IM/Synchronization Signal Block (SSB) resource for channel or interference measurement or a corresponding latest CSI-RS/CSI-IM/SSB occasion not later than a corresponding CSI reference resource until a last symbol of PUSCH/PUCCH carrying the report.

Fig. 4 shows an example of CPU occupation of aperiodic CSI reports.

Referring to fig. 4, aperiodic CSI report occupies the CPU from the first symbol after the PDCCH triggering CSI report until the last symbol of PUSCH carrying the report.

The initial SP CSI report is processed similarly to the aperiodic CSI report shown in fig. 4, and the subsequent report is processed as shown in fig. 3.

For the P3 procedure for beam management, no report is made. Therefore, the CPU occupancy is defined as follows.

For CSI reports with CSI-ReportConfig where the higher layer parameter reportquality is set to "none" and CSI-RS-resource set where the higher layer parameter trs-Info is not configured, the CPU is occupied over multiple OFDM symbols.

More specifically, the SP CSI report (excluding the initial SP CSI report on PUSCH after the PDCCH triggering the report) occupies the CPU from the first symbol of the earliest one of the P/SP CSI-RS/SSB resources for the channel measurement of the L1-RSRP calculation until Z' ₃ symbols after the last symbol of the CSI-RS/SSB resources for the channel measurement of the L1-RSRP calculation in each transmission occasion.

Aperiodic CSI reporting occupies the CPU from the first symbol after the PDCCH triggering CSI reporting until the last symbol between Z ₃ symbols after the first symbol after the PDCCH triggering CSI reporting and Z' ₃ symbols after the last symbol of the last one in each CSI-RS/SSB resource for channel measurement for L1-RSRP calculation. In other words, the CPU is occupied from the first symbol after the PDCCH to max (Z ₃,Z'₃).

If the UE has only M available CPUs and is triggered with N > M reports, the UE should update the M reports with the highest priority according to the priority rules in section 5.2.5 in 3gpp TS 38.214.

If the UE supports X simultaneous CSI computations, it is not desirable for the UE to be configured with aperiodic CSI trigger states across all CCs that contain more than X CSI reporting settings.

The processing of CSI reports occupies multiple CPUs on multiple symbols as follows:

For CSI reporting with CSI-ReportConfig where the higher layer parameter reportquality is set to "none" and CSI-RS-resource set where the higher layer parameter trs-Info is configured, O _CPU = 0

For reflecting TRS not occupying CPU

For CSI reports with higher layer parameters reportquality set to "cri-RSRP", "ssb-Index-RSRP" or "" none "(and CSI-RS-resource set where higher layer parameters trs-Info are not configured), O _CPU = 1

"None" is used to reflect that P3 in the beam management process occupies one CPU process.

Furthermore, only one CPU is occupied regardless of the number of CSI-RSs in the resource set for beam management. The situation is different when other CSI reports are configured.

CSI reporting based on K _s CSI-RS resources may approximately correspond to calculating K _s CSI-RS reports in terms of CSI calculation time. However, for L1-RSRP reporting based on K _s CSI-RS/SSB resources, the UE may calculate the received power only for each CSI-RS or SSB, without necessarily consuming K _s CPUs.

For a CSI report with CSI-ReportConfig in which the higher-layer parameter reportquality is set to "cri-RI-PMI-CQI", "cri-RI-i1", "cri-RI-i1-CQI", "cri-RI-CQI" or "cri-RI-LI-PMI-CQI",

If CSI reporting is triggered aperiodically without transmitting PUSCH with TB or HARQ-ACK or both, when l=0 CPUs are occupied, where CSI corresponds to single CSI with wideband frequency granularity and corresponds to up to 4 CSI-RS ports in a single resource without CRI reporting, and where codebookType is set to "typeI-SINGLEPANEL" or where reportquality is set to "CRI-RI-CQI", O _CPU＝N_CPU,

For low-latency CSI reporting, there is no UL-SCH TB, all CPUs are occupied for the UE to prepare a fast report with a short time line.

Otherwise, O _CPU＝K_s, where K _s is the number of CSI-RS resources in the CSI-RS resource set for channel measurement.

K _s CPUs are otherwise occupied because each CSI-RS is equivalent to calculating a CSI report.

·

Maximum number of active CSI-RSs

In addition to the number of CPUs, the UE may also indicate other information to the gNB about the maximum number of "active" CSI-RS and CSI-RS ports that can be processed simultaneously via capability signaling (maxNumberSimultaneousNZP-CSI-RS-PerCC and totalNumberPortsSimultaneousNZP-CSI-RS-PerCC).

The definition of when a CSI-RS is considered "active" varies depending on its nature, as follows.

For a-CSI-RS, starting from the end of the PDCCH containing the request to the end of the PUSCH containing the report associated with the a-CSI-RS.

For SP-CSI-RS, starting from the end of the application activation command to the end of the application deactivation command.

For the P-CSI-RS, the activation duration ends when the P-CSI-RS configuration is released.

If the CSI-RS resource is referenced N times by one or more CSI reporting settings, the CSI-RS resource and CSI-RS ports within the CSI-RS resource are counted N times.

Various embodiments of the present disclosure will be described below.

Although the embodiments will be generally described with reference to processing CSI-RS in FD mode of operation, the embodiments may also be applied when the gNB deploys Network Energy Saving (NES) procedures, such as spatial domain adaptation or power domain adaptation.

More specifically, in both FD and NES operation, the gNB may need to adjust its transmit and receive panels by enabling/disabling all subsets of antenna elements associated with logical antenna ports or by using different transmit powers. In FD operation, the gNB may require spatial or power domain adaptation to reduce self-interference to a reasonable level. In NES operation, the gNB may require spatial or power domain adaptation to reduce power consumption.

A scenario where different instances of the same CSI-RS or different CSI-RS associated with the same CSI report collide with the UL subband in SBFD symbols and become discontinuous in the frequency domain may correspond to a particular NES spatial or power domain mode or sub-configuration. However, a scenario where the same CSI-RS or other CSI-RS instances associated with the same CSI report do not collide with the UL subband in the non-SBFD symbols and remain contiguous in the frequency domain may correspond to another NES spatial or power domain mode or sub-configuration. In other words, SBFD and non-SBFD may correspond to two NES spatial or power domain modes or sub-configurations in the context of FD operation.

Thus, when the same CSI-RS or different CSI-RS are associated with different NES spatial or power domain modes or sub-configurations, the various embodiments described for continuous CSI-RS and discontinuous CSI-RS may also be applied.

Processing time

When a CSI-RS collides with a UL subband, the same CSI-RS may occupy non-contiguous RBs. Thus, the UE may require additional time to process the discontinuous CSI-RS compared to the conventional continuous CSI-RS.

According to embodiments of the present disclosure, additional processing time for the discontinuous CSI-RS may be predefined, e.g., provided in a standard specification, and added to an existing minimum duration typically set for the CSI-RS based on the associated CSI report.

For aperiodic CSI reports based on AP-CSI-RS for CM, AP-CSI-RS for IM, or AP-CSI-IM, the predefined value Δ may be added to the Z '_ref value, where Z' _ref may be determined based on, for example, conventional procedures as described above.

Fig. 5 shows an example in which a predefined value delta is added to the Z' _ref value of the discontinuous CSI-RS according to an embodiment. More specifically, fig. 5 illustrates an example of a PDCCH triggering aperiodic CSI reporting based on an AP-CSI-RS that collides with a UL subband and becomes a discontinuous CSI-RS.

Referring to fig. 5, a minimum required gap (Z' _ref +Δ) is provided between the last symbol carrying the AP-CSI-RS and the first symbol carrying the PUSCH of the AP-CSI report to allow the UE to process the CSI report.

The value of delta may depend on the subcarrier spacing. For example, a predefined table, e.g., provided in a standard specification, may be used to determine the value of Δ based on μ, which may be min (μ _PDCCH,μ_CSI-RS,μ_UL), where μ _PDCCH corresponds to the subcarrier spacing of the PDCCH transmitting the DCI, μ _UL corresponds to the subcarrier spacing of the PUSCH in which the CSI report is to be transmitted, μ _CSI-RS corresponds to the minimum subcarrier spacing of the aperiodic CSI-RS triggered by the DCI.

When CSI-RS is discontinuous, the behavior of the legacy UE depending on Z ' _ref may be applied based on Z ' _ref +Δ instead of Z ' _ref. For example, if Z' _ref +Δ is not satisfied, the UE may ignore the scheduling DCI if the number of triggered reports is one and there is no HARQ-ACK or transport block multiplexed on PUSCH. Otherwise, the UE is not required to update CSI of an nth triggered CSI report associated with the discontinuous CSI-RS.

Furthermore, when the same DCI triggers multiple aperiodic CSI reports, the values of Z and Z' may beAndWhere M is the number of updated CSI reports based on the available CPU determination, and (Z (M), Z' (M)) corresponds to the mth updated CSI report.

For CSI-RS that do not collide with UL subbands, i.e., continuous CSI-RS, the corresponding Z and Z' may be determined based on conventional methods.

For CSI-RS that collide with UL subbands, i.e., discontinuous CSI-RS, the corresponding Z' may be determined based on conventional methods and the offset Δ described herein. Further, for discontinuous CSI-RS, the value Z may be determined according to conventional methods, or additional offsets may be added similar to the offset added for Z'.

When the P/SP CSI-RS is used for CM or IM of aperiodic CSI reporting, it may not be desirable for the UE to measure channel or interference using the discontinuous CSI-RS, the last symbol of which is received at Z' +Δ symbols before the transmission time of the first OFDM symbol of PUSCH carrying aperiodic CSI reporting. Furthermore, to define CSI reference resources for use in determining the earliest CSI-RS that may be used to derive CSI, n _{CSI_ref} is greater than or equal toSuch that n-n _{CSI_ref} corresponds to a valid downlink slot and n is a slot for transmitting a CSI report.

Not all P/SP CSI-RSs associated with a particular set of resources collide with the UL subband, i.e., some P/SP CSI-RSs will collide with the UL subband while others will not. In this case, to simplify UE implementation, a single timeline may be defined to determine CSI reference resources, regardless of whether the CSI-RS collides with the UL subband.

Fig. 6 illustrates an example of adjusting CSI reference resources and Z' by delta according to an embodiment. More specifically, fig. 6 shows an example of triggering P/SP CSI-RS based aperiodic CSI reporting, where some of the P/SP CSI-RS occasions fall in non-SBFD symbols and other occasions fall in SBFD symbols.

Referring to fig. 6, a time line for determining a minimum time gap between the CSI reference resource and the P/SP CSI-RS and PUSCH is adjusted by Δ.

In the conventional NR, for P/SP CSI reporting based on P/SP CSI-RS, n _{CSI_ref} is equal to a predefined value provided in the specification based on the DL parameter set (μ) and whether beam measurements should be made. Specifically, in the case where CSI reports have no CRI, n _{CSI_ref} = 4 for μ = 15 khz; for μ=30 khz, n _{CSI_ref} =8; for μ=60 khz, n _{CSI_ref} =16; for μ=120 khz, n _{CSI_ref} =32. When the CSI report has CRI, n _{CSI_ref} = 5 for μ = 15 khz; for μ=30 khz, n _{CSI_ref} =10; for μ=60 khz, n _{CSI_ref} =20; for μ=120 khz, n _{CSI_ref} =40. When some (not necessarily all) of the P/SP CSI-RSs associated with the P/SP CSI collide with the UL subband, the additional offset delta provided in the specification, for example, may be added to a conventionally predefined value. For example, for μ=15 kHz and CSI reporting no CRI, n _{CSI_ref} =4+Δ. Further, for μ=15 kHz and CSI reports have CRI, n _{CSI_ref} =5+Δ.

Alternatively, the UE may indicate the supported offset value, e.g., Δ, to the gNB via capability signaling. In this case, the UE may assume that the indicated offset is added to a different parameter to determine the appropriate timeline.

Although the above description adds the same offset value delta to different parameters used to determine the applicable timeline, e.g., Z', n _{CSI_ref}, etc., the offset value may vary in different situations, e.g., aperiodic reporting, periodic reporting, etc. For example, for different CSI reporting types, several offset values may be predefined or indicated by the UE as part of its capability signaling.

When CSI-RS is discontinuous, a new table to determine Z or Z' may be provided and applied instead of adding the offset value delta to different parameters to determine the appropriate timeline. In this case, all parameters depending on Z or Z' will automatically reflect the additional processing time required by the UE. However, for other parameters that are not dependent on Z or Z', such as for P/SP CSI reporting based on P/SP CSI-RS, an offset may still be required that is predefined or indicated to the gNB via UE capability signaling.

Table 2 below shows an example of defining Z and Z' for the discontinuous CSI-RS. In conventional NRs, there are different timelines for different amounts of CSI reporting. Heretofore, (Z1, Z ' 1), (Z2, Z ' 2) and (Z3, Z ' 3) exist. Thus, table 2 provides (Z4, Z' 4) as a new value to be added to the existing value set.

TABLE 2

A separate table may be defined for low complexity (or low latency) aperiodic CSI reports defined as non-continuous CSI-RS based CSI reports including wideband frequency granularity reports. Another table may be defined for the discontinuous CSI-RS for beam management. Further, another table may be defined for the remaining CSI reports associated with the non-continuous CSI-RS, i.e., high complexity (or high latency).

Some entries of predefined Z and Z' may depend on UE capability signaling. For example, if the discontinuous CSI-RS is used for beam management, e.g. associated with RSRP reports indicated by the reporting quantity "cri-RSRP", some entries may depend on parameters indicated via UE capability signaling. This capability signaling may be separate from the capability signaling associated with legacy CSI-RS (e.g., beamSwitchTiming or beamReportTiming) and is used to indicate X' _i, i=0, 1,2,3 and KB _i, i=1, 2, as shown in table 3 below. The value of X' _i may represent the required time for processing the CSI report in units of symbols. This approach provides further flexibility in that the UE may indicate a preferred value rather than using a predefined value.

TABLE 3 Table 3

Alternatively, the same capability signaling for discontinuous CSI-RS may be used for beam management. In this case, the UE may report the maximum required time to ensure that the UE has enough time for both legacy and non-continuous CSI-RS.

In the case where the PRG is configured to be wideband and the PDSCH occupies non-contiguous RBs in non-contiguous DL subbands surrounding the UL subband, channel estimation may become more complex than the conventional wideband PRG occupies contiguous RBs. Thus, the PDSCH processing timeline may be relaxed to capture the impact of additional processing of wideband PRGs on non-contiguous RBs. For example, as shown in equation (1) below, an additional d3 may be added to the timeline between the last symbol of the PDSCH and the first symbol of the PUCCH carrying HARQ-ACK information to determine whether the UE should provide a valid HARQ-ACK message.

T_Proc,1＝(N₁+d_1,1+d₂+d₃)(2048+144)·k2^-μ·T_C+T_ext…(1)

The value of d3 may be predefined, or the UE may indicate value d3 to the gNB via capability signaling.

When PDSCH is scheduled/configured on consecutive RBs in any DL subband, d3=0 does not span two DL subbands or in non-SBFD symbols/slots.

If the UE indicates that processing capability 2 is supported or is configured to apply processing capability 2 in a particular CC, the UE may default to processing capability 1 when the PDSCH spans a non-contiguous DL subband and the PRG is configured to be wideband. Otherwise, PDSCH is restricted entirely to one of the DL subbands and processing capability 2 is applied.

Even though the PRG is not configured to be wideband, PDSCH processing timeline relaxation may be applied when PDSCH is scheduled to occupy consecutive RBs, e.g., via non-interlace type 1, and PDSCH becomes discontinuous due to the presence of UL subbands.

One way to deal with this is for the UE to treat the wideband PRG as if the PRG were configured with a size of 2 or 4. The selected PRG size may be predefined or configured by the gNB. Further, the selected PRG size may depend on the number of RBs allocated for each portion of PDSCH above and below the UL sub-band. For example, if the number of RBs allocated in a particular portion of PDSCH is below a certain threshold, the UE may assume a PRG size of 2; otherwise, the PRG size is 4. The threshold may be configured or predefined by higher layer signaling.

The UE may indicate to the gNB via its capability signaling how it will handle this situation, for example. The UE informs the gNB whether it will consider a non-contiguous PDSCH with a wideband PRG, as if the PRG were of size 2 or 4 or any other size, or whether the UE will apply wideband processing on each portion, a specific portion (e.g., a portion with more RBs), or both of the non-contiguous PDSCH. Further, the UE may inform the gNB whether the PDSCH processing timeline needs to be relaxed. The UE may also notify the gNB of the additional relaxation time required by the UE if needed.

Influence on CPU occupation

In conventional NR, the UE indicates to the gNB via capability signaling (i.e., simultaneousCSI-ReportsPerCC and simultaneousCSI-ReportsAllCC) the total number of available CPUs within and across all CCs.

In one approach, a single CPU pool may be used for both legacy CSI-RS and discontinuous CSI-RS. The pool may be indicated via conventional capability signaling.

In another approach, new capability signaling may be defined to instruct the discontinuous CSI-RS for each CC and a dedicated CPU pool across all CCs.

Conventional rules may be applied as to when the CPU is occupied, but parameters Z and/or Z' related to CSI reference resources are determined as described above.

Fig. 7 illustrates an example of CPU occupation of P/SP CSI reporting based on P/SP discontinuous CSI-RS according to an embodiment.

Referring to fig. 7, the p/SP CSI report (excluding the initial SP CSI report on PUSCH after PDCCH triggering the report) occupies the CPU from the earliest symbol of the discontinuous CSI-RS (no later than the CSI reference resource calculated as described above) to the end of PUXCH, where X may be one of { C, S } referring to PUCCH or PUSCH carrying the report.

Determining the number of CPUs occupied due to discontinuous CSI-RS may be important to ensure that simultaneous reporting does not exceed the capability of the UE.

One approach is to apply conventional rules to determine the number of occupied CPUs. However, this approach may not accurately reflect the additional processing required on the UE side.

For CSI reports used for beam management and associated with non-contiguous CSI-RSs, e.g. reportquality is set to "cri-RSRP", "ssb-Index-RSRP" or "none", the number of occupied CPUs represented by O _CPU may be X instead of 1, and in the case of conventional CSI-RSs, e.g. x=2.

Alternatively, the number of CPUs to be occupied in this case, i.e., the discontinuous CSI-RS for beam management, may be indicated by UE capability signaling. The indication may provide the absolute number of CPUs (e.g., X) to be occupied when CSI reports are associated with the non-contiguous CSI-RS to the gNB. Alternatively, the indication may provide the gNB with an additional number of CPUs to be added to the number of CPUs that would normally be occupied in the case of a conventional continuous CSI-RS.

For CSI reporting for channel measurement, for example, in case of CSI-ReportConfig having a higher layer parameter reportquality set to "cri-RI-PMI-CQI", "cri-RI-i1", "cri-RI-i1-CQI", "cri-RI-CQI" or "cri-RI-LI-PMI-CQI", the number of occupied CPUs may be determined as follows:

If CSI reporting is triggered aperiodically without transmitting PUSCH with TB, HARQ-ACK, or both, when l=0 CPUs are occupied, where CSI corresponds to single CSI with wideband frequency granularity and corresponds to up to 4 CSI-RS ports in a single resource without CRI reporting, and where codebookType is set to "typeI-SINGLEPANEL" or where reportquality is set to "CRI-RI-CQI", O _CPU＝N_CPU,

Otherwise, O _CPU＝K′_s+X*K″_s, where K' _s is the number of legacy continuous CSI-RS resources, K "_s is the number of discontinuous CSI-RS resources in the CSI-RS resource set for channel measurement, X is a scaling factor reflecting the additional processing of the discontinuous CSI-RS, e.g. x=2. In other words, in the case of the conventional continuous CSI-RS, each discontinuous CSI-RS occupies X CPUs instead of 1. Alternatively, the number of CPUs to be occupied in this case (i.e., discontinuous CSI-RS for channel measurement) may be indicated by UE capability signaling. When CSI reports are associated with non-contiguous CSI-RSs, an indication from the UE to the gNB may provide the gNB with an absolute number of CPUs to occupy, e.g., X. As another possibility, the indication may provide the gcb with an additional number of CPUs to be added to the number of CPUs that would normally be occupied in the case of a conventional continuous CSI-RS.

This concept can also be applied to NES procedures based on spatial mode adaptation or power domain mode adaptation or configuration of multiple sub-configurations associated with different adaptation modes. Assuming that two spatial modes or two power domain modes or two sub-configurations are to be reported, O _CPU＝K′_s+X*K″_s, where K' _s is the number of CSI-RS resources in the CSI-RS resource set associated with the first NES spatial mode or power domain mode or sub-configuration, i.e. similar to the number of non-contiguous CSI-RS resources in FD operation, K "_s is the number of CSI-RS resources in the CSI-RS resource set associated with the second NES spatial mode or power domain mode or sub-configuration, i.e. similar to the number of contiguous CSI-RS resources in FD operation, X is a scaling factor reflecting the additional processing of the additional mode or sub-configuration (i.e. similar to the non-contiguous CSI-RS resources), e.g. x=1.

Although the above description is directed to two NES spatial modes or two power domain modes or two sub-configurations, it may also be applied to more than two modes or sub-configurations. In this case the number of the elements to be formed is, Where N is the number of modes or sub-configurations to report,Is the number of CSI-RS resources in the CSI-RS resource set associated with the i-th mode or sub-configuration.

If a particular report associated with a non-continuous CSI-RS occupies more than 1 CPU representing each portion of the non-continuous CSI-RS and there is not enough required CPU available, the UE may not update the associated CSI report.

In the conventional NR, the CSI-RS may be used as a TRS. In this case, for CSI reports with CSI-ReportConfig in which the higher layer parameter reportquality is set to "none" and with CSI-RS-resource set in which the higher layer parameter trs-Info is configured, O _CPU = 0.

Although TRS-based TDCP reporting is typically independent side information, separate from the traditional CSI reporting framework, it may be beneficial to determine the additional processing overhead of calculating the TDCP based on the TRS.

One approach is to use legacy O _CPU to capture UE processing overhead. In particular, when the TRS is used to report TDCP, the number of occupied CPUs may be determined by O _CPU = K, where K may be predefined, e.g., K = 1, similar to CSI-RS used for beam management. Alternatively, K may be equal to the number of TRS resources related to the TDCP report. Furthermore, the UE may indicate the value of K to the gNB via capability signaling to better reflect the UE implementation.

To avoid negative effects of the CSI framework, a separate resource pool may be used to define the UE capability to process TRS when it is used to report TDCP. Specifically, the UE may indicate to the gNB the maximum number of TDCP reports calculated per CC or across all CCs simultaneously. For example, the UE may indicate such information to the gNB via capability signaling separate from CSI reporting for each CC or maximum number across all CCs. This value may be referred to as N _CPU、TDCP. When the TDCP shares the same pool as the regular CSI report, the number of occupied CPUs in the separate TDCP report pool may be determined as described.

Whether a separate or shared CPU pool is used, for aperiodic TDCP reporting, the CPU may be occupied from the first symbol after the PDCCH triggering the CSI report until the last symbol carrying the reported PUSCH/PUCCH. For periodic or semi-persistent TDCP reporting, the same rules as in the conventional CSI framework may be used to determine when the CPU is occupied.

If the UE has only M available CPUs and is triggered with N > M reports, the UE should update the M reports with the highest priority according to the priority rule. The TDCP may have a priority lower than other CSI reports, the same as CSI reports that do not carry L1-RSRP or L1-SINR, or higher than other CSI reports.

Regarding the processing timeline of the TDCP, similar legacy CSI reporting may be used, or additional delays may be used, as described above for the discontinuous CSI-RS.

Effects on CSI-RS counting

In legacy NRs, the UE may indicate other information to the gNB about the maximum number of simultaneous "active" CSI-RS and CSI-RS ports for each CC that the UE may handle via capability signaling (maxNumberSimultaneousNZP-CSI-RS-PerCC and totalNumberPortsSimultaneousNZP-CSI-RS-PerCC). The definition of when a CSI-RS is considered "active" varies depending on its nature, as follows.

For a-CSI-RS, starting from the end of the PDCCH that includes the request to the end of the PUSCH that contains the report associated with the a-CSI-RS.

For SP-CSI-RS, starting from the end of the application activation command to the end of the application deactivation command.

For the P-CSI-RS, the activation duration ends when the P-CSI-RS configuration is released.

In the presence of discontinuous CSI-RS, it may be important to determine how to count it into the maximum number of simultaneous active CSI-RS and CSI-RS ports for each CC.

One approach is to count the discontinuous CSI-RS as 1+x, where X represents the impact with the discontinuous CSI-RS. The value of X may be predefined, for example x=1.

Alternatively, the UE may indicate the value of X to the gNB via capability signaling. Further, the UE may indicate how the CSI-RS should be counted into the absolute value of the limitation of the CSI-RS and CSI-RS ports for each CC, instead of indicating X as the delta value.

Further, the UE may inform the gNB of the maximum number of legacy CSI-RS and non-consecutive CSI-RS that may be activated simultaneously. In other words, the UE indicates to the gNB two different pools of maximum number of CSI-RS that can be activated simultaneously, one pool for legacy CSI-RS and the other pool for discontinuous CSI-RS, and each type of CSI-RS is counted into its associated pool.

Regarding the determination of when the discontinuous CSI-RS is active, the same rules as the conventional continuous CSI-RS may be applied.

CSI-RS spanning multiple SBFD and non-SBFD symbols

The CSI-RS ports may occupy consecutive OFDM symbols. If some of these OFDM symbols are SBFD symbols and others are non-SBFD symbols, this can be problematic for the UE when estimating the channel, interference, or making beam measurements. For example, the gNB may use different antenna elements, different transmit powers, apply different beams, etc. in the non-SBFD and SBFD symbols, which may corrupt measurements associated with the CSI-RS ports.

More specifically, the UE may not expect the same CSI-RS port to span SBFD symbols and non-SBFD symbols. Thus, to provide greater flexibility to the gNB, the same CSI-RS port may span SBFD and non-SBFD symbols, assuming that the gNB uses the same antenna elements, the transmit power is fixed, and the same beam is applied to all symbols spanned by the CSI-RS port.

Fig. 8 is a flowchart illustrating a method performed by a terminal according to an embodiment.

Referring to fig. 8, in step 801, the terminal monitors a first condition, i.e., whether a CSI-RS or PDSCH overlaps with a UL subband in SBFD operation and becomes discontinuous in the frequency domain, and a second condition, i.e., whether a different network antenna mode or power mode is used for transmission of the CSI-RS in network power saving operation. As described above, for SBFD operations, when a signal (e.g., CSI-RS) or channel (e.g., PDSCH) collides with UL subbands, the processing requirements in terms of time lines and occupied computing resources may be relaxed.

In step 802, the terminal determines whether a first condition or a second condition occurs.

In step 803, in response to determining that the first condition or the second condition occurs, the terminal relaxes the processing requirements associated with the processing timeline and/or the occupied computing resources.

For example, as described above, for aperiodic CSI reporting, the minimum processing period (period) may be determined using Z' +Δ, or the processing timeline for PDSCH may be relaxed by adding d3 to the consecutive PDSCH processing timeline.

As another example, for periodic or semi-periodic CSI reporting, the CSI reference resource may be increased by Δ.

As yet another example, the number of occupied CPUs may be increased by a factor X, where X is a scaling factor reflecting the additional processing of the discontinuous CSI-RS.

Fig. 9 is a block diagram of an electronic device in a network environment 900 according to an embodiment.

Referring to fig. 9, an electronic device 901 in a network environment 900 may communicate with the electronic device 902 via a first network 998 (e.g., a short range wireless communication network) or with the electronic device 904 or server 908 via a second network 999 (e.g., a long range wireless communication network). The electronic device 901 may communicate with the electronic device 904 via the server 908. The electronic device 901 may include a processor 920, a memory 930, an input device 950, a sound output device 955, a display device 960, an audio module 970, a sensor module 976, an interface 977, a haptic module 979, a camera module 980, a power management module 988, a battery 989, a communication module 990, a Subscriber Identity Module (SIM) card 996, or an antenna module 997. In one embodiment, at least one component (e.g., display device 960 or camera module 980) may be omitted from electronic device 901, or one or more other components may be added to electronic device 901. Some of the components may be implemented as a single Integrated Circuit (IC). For example, a sensor module 976 (e.g., a fingerprint sensor, iris sensor, or illuminance sensor) may be embedded in the display device 960 (e.g., a display).

The processor 920 may execute software (e.g., program 940) to control at least one other component (e.g., hardware or software component) of the electronic device 901 that is coupled to the processor 920 and may perform various data processing or calculations. For example, the processor 920 may execute software to perform the method shown in fig. 8.

As at least part of the data processing or calculation, the processor 920 may load commands or data received from another component (e.g., the sensor module 976 or the communication module 990) into the volatile memory 932, process the commands or data stored in the volatile memory 932, and store the resulting data in the nonvolatile memory 934. The processor 920 may include a main processor 921 (e.g., a Central Processing Unit (CPU) or an Application Processor (AP)) and an auxiliary processor 923 (e.g., a Graphics Processing Unit (GPU), an Image Signal Processor (ISP), a sensor hub processor, or a Communication Processor (CP)), and the auxiliary processor 923 may operate independently of the main processor 921 or in conjunction with the main processor 921. Additionally or alternatively, the auxiliary processor 923 may be adapted to consume less power or perform certain functions than the main processor 921. The auxiliary processor 923 may be implemented separately from the main processor 921 or as part of the main processor 921.

The auxiliary processor 923 may replace the main processor 921 when the main processor 921 is in an inactive (e.g., sleep) state, or the auxiliary processor 923 may control at least some functions or states related to at least one of the components of the electronic device 901 (e.g., the display device 960, the sensor module 976, or the communication module 990) along with the main processor 921 when the main processor 921 is in an active state (e.g., executing an application). The auxiliary processor 923 (e.g., an image signal processor or a communication processor) may be implemented as part of another component (e.g., a camera module 980 or a communication module 990) that is functionally associated with the auxiliary processor 923.

The memory 930 may store various data used by at least one component of the electronic device 901 (e.g., the processor 920 or the sensor module 976). The various data may include, for example, input data or output data for the software (e.g., program 940) and commands associated therewith. Memory 930 may include volatile memory 932 or nonvolatile memory 934. The non-volatile memory 934 may include an internal memory 936 and/or an external memory 938.

Programs 940 may be stored as software in memory 930 and may include, for example, an Operating System (OS) 942, middleware 944, or applications 946.

The input device 950 may receive commands or data from outside the electronic device 901 (e.g., a user) to be used by another component of the electronic device 901 (e.g., the processor 920). The input device 950 may include, for example, a microphone, a mouse, or a keyboard.

The sound output device 955 may output a sound signal to the outside of the electronic device 901. The sound output device 955 may include, for example, a speaker or a receiver. The speaker may be used for general purposes, such as playing multimedia or audio recordings, and the receiver may be used to receive incoming calls. The receiver may be implemented separately from the speaker or as part of the speaker.

The display device 960 may visually provide information to an exterior (e.g., a user) of the electronic device 901. The display device 960 may include, for example, a display, a holographic device, or a projector, and control circuitry to control a corresponding one of the display, holographic device, and projector. The display device 960 may include touch circuitry adapted to detect touches, or sensor circuitry (e.g., pressure sensors) adapted to measure the strength of touch-induced forces.

The audio module 970 may convert sound to an electrical signal and vice versa. The audio module 970 may obtain sound via the input device 950 or output sound via the sound output device 955 or headphones of an external electronic device 902 that is directly (e.g., wired) or wirelessly coupled to the electronic device 901.

The sensor module 976 may detect an operational state (e.g., power or temperature) of the electronic device 901 or an environmental state (e.g., a state of a user) external to the electronic device 901, and then generate an electrical signal or data value corresponding to the detected state. The sensor module 976 may include, for example, a gesture sensor, a gyroscope sensor, an atmospheric pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an Infrared (IR) sensor, a biometric sensor, a temperature sensor, a humidity sensor, or an illuminance sensor.

The interface 977 may support one or more specified protocols to be used for coupling the electronic device 901 directly (e.g., wired) or wirelessly with the external electronic device 902. The interface 977 may include, for example, a High Definition Multimedia Interface (HDMI), a Universal Serial Bus (USB) interface, a Secure Digital (SD) card interface, or an audio interface.

The connection terminal 978 may include a connector via which the electronic device 901 may physically connect with the external electronic device 902. The connection terminal 978 may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (e.g., an earphone connector).

The haptic module 979 may convert the electrical signal into a mechanical stimulus (e.g., vibration or movement) or an electrical stimulus that may be recognized by a user via touch or kinesthetic sense. Haptic module 979 may include, for example, a motor, a piezoelectric element, or an electrostimulator.

The camera module 980 may capture still images or moving images. The camera module 980 may include one or more lenses, image sensors, image signal processors, or flash lamps. The power management module 988 may manage power supplied to the electronic device 901. The power management module 988 may be implemented as at least a portion of, for example, a Power Management Integrated Circuit (PMIC).

The battery 989 may provide power to at least one component of the electronic device 901. The battery 989 may include, for example, a primary non-rechargeable battery, a secondary rechargeable battery, or a fuel cell.

The communication module 990 may support establishing a direct (e.g., wired) communication channel or a wireless communication channel between the electronic device 901 and an external electronic device (e.g., the electronic device 902, the electronic device 904, or the server 908), and performing communication via the established communication channel. The communication module 990 may include one or more communication processors that may operate independently of the processor 920 (e.g., an AP) and support direct (e.g., wired) or wireless communication. The communication module 990 may include a wireless communication module 992 (e.g., a cellular communication module, a short-range wireless communication module, or a Global Navigation Satellite System (GNSS) communication module) or a wired communication module 994 (e.g., a Local Area Network (LAN) communication module or a Power Line Communication (PLC) module). A respective one of these communication modules may communicate with external electronic devices via a first network 998 (e.g., a short-range communication network such as BLUETOOTH ^TM, wireless fidelity (Wi-Fi) direct, or infrared data association (IrDA) standard) or a second network 999 (e.g., a long-range communication network such as a cellular network, the internet, or a computer network (e.g., a LAN or Wide Area Network (WAN)). These different types of communication modules may be implemented as a single component (e.g., a single IC) or may be implemented as multiple components (e.g., multiple ICs) that are separate from each other. The wireless communication module 992 may use subscriber information (e.g., an International Mobile Subscriber Identity (IMSI)) stored in the subscriber identification module 996 to identify and authenticate the electronic device 901 in a communication network such as the first network 998 or the second network 999.

The antenna module 997 may transmit signals or power to the outside of the electronic device 901 (e.g., an external electronic device), or receive signals or power from the outside of the electronic device 901 (e.g., an external electronic device). The antenna module 997 may include one or more antennas and, for example, at least one antenna from which a communication scheme suitable for use in a communication network such as the first network 998 or the second network 999 may be selected by the communication module 990 (e.g., the wireless communication module 992). Signals or power may then be transmitted or received between the communication module 990 and the external electronic device via the selected at least one antenna.

Commands or data may be sent or received between the electronic device 901 and the external electronic device 904 via a server 908 coupled to the second network 999. Each of the electronic devices 902 and 904 may be the same type or a different type of device than the electronic device 901. All or some of the operations to be performed at the electronic device 901 may be performed at one or more external electronic devices 902, 904, or 908. For example, if the electronic device 901 should perform a function or service automatically or in response to a request from a user or another device, the electronic device 901 may request one or more external electronic devices to perform at least a portion of the function or service instead of or in addition to performing the function or service. The external electronic device or devices receiving the request may perform at least a portion of the requested function or service or additional functions or additional services related to the request and transmit the result of the performance to the electronic device 901. The electronic device 901 may provide the results, with or without further processing, as at least a portion of the reply to the request. To this end, for example, cloud computing, distributed computing, or client-server computing techniques may be used.

Fig. 10 shows a system including a UE 1005 and a gNB 1010 in communication with each other.

Referring to fig. 10, a ue (or terminal) may include a radio 1015 and processing circuitry (or means for processing) 1020 that may perform various methods disclosed herein, such as the method shown in fig. 8. For example, processing circuitry 1020 may receive a transmission from network node (gNB) 1010 via radio 1015, and processing circuitry 1020 may send a signal to gNB 1010 via radio 1015.

Embodiments of the subject matter and the operations described in this specification can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them. Embodiments of the subject matter described in this specification can be implemented as one or more computer programs, i.e., one or more modules of computer program instructions encoded on a computer storage medium for execution by, or to control the operation of, data processing apparatus. Alternatively or additionally, the program instructions may be encoded on artificially generated propagated signals (e.g., machine-generated electrical, optical, or electromagnetic signals) that are generated to encode information for transmission to suitable receiver apparatus for execution by data processing apparatus. The computer storage medium may be or be included in a computer readable storage device, a computer readable storage substrate, a random or serial access memory array, or a device, or a combination thereof. Furthermore, while the computer storage medium is not a propagated signal, the computer storage medium may be a source or destination of computer program instructions encoded in an artificially generated propagated signal. Computer storage media may also be or be included in one or more separate physical components or media (e.g., a plurality of CDs, discs, or other storage devices). Furthermore, the operations described in this specification may be implemented as operations performed by a data processing apparatus on data stored on one or more computer readable storage devices or received from other sources.

While this specification may contain many specific implementation details, these should not be construed as limitations on the scope of any claimed subject matter, but rather as descriptions of features specific to particular embodiments. Certain features that are described in this specification in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Furthermore, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.

Similarly, although operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In some cases, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.

Thus, particular embodiments of the subject matter have been described herein. Other embodiments are within the scope of the following claims. In some cases, the actions recited in the claims can be performed in a different order and still achieve desirable results. Furthermore, the processes depicted in the accompanying drawings do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some implementations, multitasking and parallel processing may be advantageous.

As will be recognized by those skilled in the art, the innovative concepts described herein can be modified and varied over a wide range of applications. Accordingly, the scope of the claimed subject matter should not be limited to any of the specific exemplary teachings discussed above, but is instead defined by the following claims.

Claims (20)

1. A method performed by a terminal in a wireless communication system, the method comprising:

At least one of the first condition or the second condition is monitored,

Wherein the first condition comprises that the channel state information CSI-reference signal RS or the physical downlink shared channel PDSCH overlaps with an uplink sub-band in a sub-band full duplex operation and becomes discontinuous in a frequency domain, and

Wherein the second condition includes a different network antenna mode or power mode for transmission of CSI-RS in a network power saving operation; and

In response to the first condition or the second condition occurring, a processing requirement associated with at least one of the processing timeline or the occupied computing resources is relaxed.

2. The method of claim 1, wherein, in response to the first condition occurring, for aperiodic CSI reporting, relaxing the processing requirement comprises using Z' +Δ to determine a minimum processing period,

Where Z' indicates a minimum processing period starting immediately after the last symbol of the CSI-RS if the CSI-RS is continuous in the frequency domain, and Δ indicates an additional processing period.

3. The method of claim 2, wherein Δ is determined based on a subcarrier spacing of CSI-RS.

4. A method according to claim 3, wherein the value of Δ is predefined or sent by the terminal to the base station via capability signalling.

5. The method of claim 1, wherein, in response to the first condition occurring, for periodic or semi-periodic CSI reporting, relaxing the processing requirements comprises increasing CSI reference resources by delta,

Where Δ indicates an additional processing period.

6. The method of claim 5, wherein Δ is determined based on a subcarrier spacing of CSI-RS.

7. The method of claim 6, wherein the value of Δ is predefined or transmitted by the terminal to the base station via capability signaling.

8. The method of claim 1, wherein relaxing the processing requirement in response to the first condition occurring comprises: the processing timeline for PDSCH is relaxed by adding d3 to the consecutive PDSCH processing timeline, where d3 indicates additional processing periods.

9. The method of claim 8, wherein the value of d3 is predefined or transmitted by the terminal to the base station via capability signaling.

10. The method of claim 1, wherein relaxing the processing requirement in response to the first condition or the second condition occurring comprises: the number of occupied CSI processing unit CPUs is increased by a factor X, where X is a scaling factor reflecting the additional processing of CSI-RS.

11. The method of claim 10, further comprising: the number of occupied CPUs is determined as the sum of all CSI-RSs associated with each of the different antenna patterns or power patterns.

12. The method of claim 10, wherein the value of X is predefined or sent by the terminal to the base station via capability signaling.

13. A terminal for use in a wireless communication system, the terminal comprising:

a transceiver; and

A processor configured to:

At least one of the first condition or the second condition is monitored,

Wherein the first condition comprises that the channel state information CSI-reference signal RS or the physical downlink shared channel PDSCH overlaps with an uplink sub-band in a sub-band full duplex operation and becomes discontinuous in a frequency domain, and

Wherein the second condition includes a different network antenna mode or power mode for transmission of CSI-RS in a network power saving operation; and

In response to the first condition or the second condition occurring, a processing requirement associated with at least one of the processing timeline or the occupied computing resources is relaxed.

14. The terminal of claim 13, wherein, in response to the first condition occurring, the processor is further configured to relax processing requirements for aperiodic CSI reporting by determining a minimum processing period using Z' +Δ,

Where Z' indicates a minimum processing period starting immediately after the last symbol of the CSI-RS if the CSI-RS is continuous in the frequency domain, and Δ indicates an additional processing period.

15. The terminal of claim 14, wherein Δ is determined based on a subcarrier spacing of CSI-RS.

16. The terminal of claim 13, wherein, in response to the first condition occurring, the processor is further configured to relax processing requirements for periodic or semi-periodic CSI reports by increasing CSI reference resources by delta,

Where Δ indicates an additional processing period.

17. The terminal of claim 16, wherein Δ is determined based on a subcarrier spacing of CSI-RS.

18. The terminal of claim 13, wherein in response to the first condition occurring, the processor is further configured to relax a processing timeline for PDSCH by adding d3 to a consecutive PDSCH processing timeline, wherein d3 indicates an additional processing period.

19. The terminal of claim 13, wherein in response to the first condition or the second condition occurring, the processor is further configured to relax processing requirements by increasing the number of occupied CSI processing unit CPUs by a factor X, wherein X is a scaling factor reflecting additional processing of CSI-RS.

20. The terminal of claim 19, wherein the processor is further configured to determine the number of occupied CPUs as a sum of all CSI-RS associated with each sub-configuration of a different antenna mode or power mode.