Method and device for reporting

Abstract

A method according to an embodiment of the present specification includes the steps of: receiving configuration information from a base station; and reporting, to the base station, information related to at least one downlink reference signal (DL RS). The configuration information includes configurations related to measurement and / or reporting. One or more of the configurations are released or deactivated on the basis of the at least one DL RS.

Description

Method and device for reporting

[0001] This specification relates to a method and apparatus for reporting.

[0002] Mobile communication systems were developed to provide voice services while ensuring user activity. However, they have expanded beyond voice to include data services. Currently, explosive growth in traffic is leading to resource shortages and users are demanding faster services, necessitating a more advanced mobile communication system.

[0003] Next-generation mobile communication systems must support explosive data traffic growth, dramatically increasing data rates per user, a vastly increased number of connected devices, ultra-low end-to-end latency, and high energy efficiency. To achieve these goals, various technologies are being studied, including dual connectivity, massive multiple input multiple output (MIMO), in-band full duplex, non-orthogonal multiple access (NOMA), super wideband support, and device networking.

[0004] According to Rel-19 NES (Network Energy Saving) WI, there is a possibility of standardization for operations such as the base station transmitting a light synch signal or long-period SSB, and then the base station transmitting a normal SSB when the UE transmits a WUS signal. Meanwhile, in Rel-19 AI / ML BM, standardization is in progress for the UE-side AI / ML operation in which the UE measures only the beam set corresponding to Set B and predicts and reports the predicted Top-K beam of Set A. Depending on the UE-side model, the reporting method for which the UE prefers which Set A / B combination (e.g., combination of DL RSs) needs to be specified.

[0005] The purpose of this specification is to propose a method for reporting preferred / non-preferred DL RS(s) and performing actions based on the same in terms of Network Energy Saving (NES).

[0006] Another purpose of this specification is to propose a method for reporting preferred / disliked DL RS(s) and performing actions based on the same in terms of AI / ML.

[0007] The technical problems to be achieved in this specification are not limited to the technical problems mentioned above, and other technical problems not mentioned can be clearly understood by a person having ordinary skill in the technical field to which this specification pertains from the description below.

[0008] A method according to one embodiment of the present disclosure includes the steps of receiving configuration information from a base station and reporting information related to at least one downlink reference signal (DL RS) to the base station.

[0009] The above configuration information includes configurations related to measurement and / or reporting. One or more of the configurations are released or deactivated based on at least one DL RS.

[0010] The at least one DL RS may include a non-preferred DL RS.

[0011] The above one or more settings may include settings based on the non-preferred DL RS.

[0012] Sets related to beam prediction can be determined based on DL RSs other than the above non-preferred DL RSs.

[0013] Positioning measurement reporting can be performed based on a Positioning Reference Signal (PRS) associated with a DL RS other than the above non-preferred DL RS.

[0014] The at least one DL RS may include a preferred DL RS.

[0015] The above one or more settings may include settings other than the settings based on the preferred DL RS among the above settings.

[0016] The above information may be related to a request for a reduction in transmit power of the preferred DL RS.

[0017] Information related to the model can be set based on the above preferred DL RS.

[0018] The above information may include i) a plurality of DL RSs and ii) a coefficient for each DL RS among the plurality of DL RSs. The information related to the model may be related to a DL RS based on a linear combination of each DL RS among the plurality of DL RSs and the coefficients.

[0019] Based on the above information related to the above model, data collection for the model and / or performance monitoring of the model can be performed.

[0020] Based on the above preferred DL RS, sets related to beam prediction can be determined.

[0021] Positioning measurement reporting can be performed based on a Positioning Reference Signal (PRS) associated with the above preferred DL RS.

[0022] The above at least one DL RS may be based on at least one synchronization signal block (SSB).

[0023] The above one or more settings may include one or more sub-settings related to one reporting setting.

[0024] Based on the above information, sets related to at least one DL RS among the sets set for the model can be indicated.

[0025] The sets associated with the at least one DL RS may be determined from among the sets indicated based on group common downlink control information (DCI) among the established sets.

[0026] The above-described sets may include i) sets common to the characteristics and / or ii) sets specific to each of the characteristics.

[0027] A terminal according to another embodiment of the present disclosure includes one or more transceivers, one or more processors, and one or more memories connected to the one or more processors and storing instructions.

[0028] The above instructions are characterized in that they cause the terminal to perform all steps of any one of the above methods based on being executed by the one or more processors.

[0029] According to another embodiment of the present disclosure, a device comprises one or more memories and one or more processors connected to the one or more memories. The one or more memories are characterized in that they store instructions that cause the device to perform all steps of any one of the above methods based on instructions executed by the one or more processors.

[0030] A non-transitory computer-readable storage medium according to another embodiment of the present disclosure stores instructions. The instructions, executable by one or more processors, are characterized in that they cause a terminal to perform all steps of any one of the above methods.

[0031] A method according to another embodiment of the present disclosure includes the steps of transmitting configuration information to a terminal and receiving information related to at least one downlink reference signal (DL RS) from the terminal.

[0032] The above configuration information includes configurations related to measurement and / or reporting. One or more of the configurations are released or deactivated based on at least one DL RS.

[0033] A base station according to another embodiment of the present disclosure includes one or more transceivers, one or more processors, and one or more memories coupled to the one or more processors and storing instructions.

[0034] The above instructions are characterized in that they cause the base station to perform all steps of the method based on being executed by the one or more processors.

[0035] According to embodiments of the present disclosure, one or more settings can be disabled / released based on the reported DL RS, thereby reducing power consumption compared to existing methods. Specifically, the power consumption of the base station / NW can be reduced by the amount of power required to transmit a signal related to the reported DL RS. Furthermore, the power consumption of the terminal can be reduced by the amount of power required to perform measurement / reporting on the settings related to the reported DL RS.

[0036] According to an embodiment of the present specification, sets related to beam prediction can be determined based on reported DL RSs. When a base station and a terminal each use the same AI / ML model (e.g., same model ID or same model functionality), the base station and the terminal can utilize the same sets (e.g., Set A, Set B) to produce the same results. Since there is no need to share the model results of the terminal or base station with the base station or terminal through additional signaling, signaling overhead and delay are reduced when performing subsequent operations (e.g., UL / DL transmission) after performing a model-based operation (e.g., beam prediction).

[0037] According to embodiments of the present disclosure, positioning measurement reporting can be performed based on reported DL RSs. Therefore, the DL PRSs for which a terminal performs positioning measurement reporting can be recognized in advance by the base station / NW. Since the payload size of the report can be predicted in advance, the base station can allocate only the resources necessary for the report to the terminal without waste. Furthermore, only the PRSs required for the terminal to perform positioning measurement reporting can be configured / transmitted based on the reported DL RSs. Since unnecessary PRS configuration / transmission is not performed, power savings can be achieved in terms of the NES.

[0038] The effects that can be obtained from this specification are not limited to the effects mentioned above, and other effects that are not mentioned can be clearly understood by a person having ordinary skill in the technical field to which this specification belongs from the description below.

[0039] Figure 1 is a flowchart showing an example of a CSI-related procedure.

[0040] Figure 2 is a flowchart showing an example of a DL BM procedure.

[0041] FIG. 3 is a flowchart illustrating a method according to one embodiment of the present specification.

[0042] FIG. 4 is a flowchart illustrating a method according to another embodiment of the present specification.

[0043] FIG. 5 is a drawing showing the configuration of a first device and a second device according to an embodiment of the present specification.

[0044] Hereinafter, preferred embodiments according to the present disclosure will be described in detail with reference to the accompanying drawings. The detailed description set forth below, together with the accompanying drawings, is intended to illustrate exemplary embodiments of the present disclosure and is not intended to represent the only embodiments in which the present disclosure may be implemented. The following detailed description includes specific details to provide a thorough understanding of the present disclosure.

[0045] In some cases, to avoid ambiguity in the concepts of this specification, well-known structures and devices may be omitted or illustrated in block diagram form focusing on the core functions of each structure and device.

[0046] Hereinafter, downlink (DL) refers to communication from a base station to a terminal, and uplink (UL) refers to communication from a terminal to a base station. In downlink, a transmitter may be part of a base station, and a receiver may be part of a terminal. In uplink, a transmitter may be part of a terminal, and a receiver may be part of a base station. A base station may be expressed as a first communication device, and a terminal may be expressed as a second communication device. A base station (BS) may be replaced by terms such as a fixed station, Node B, eNB (evolved-NodeB), gNB (Next Generation NodeB), BTS (base transceiver system), access point (AP: Access Point), network (5G network), AI system, RSU (road side unit), vehicle, robot, drone (Unmanned Aerial Vehicle, UAV), AR (Augmented Reality) device, VR (Virtual Reality) device, etc. In addition, the terminal may be fixed or mobile, and may be replaced with terms such as UE (User Equipment), MS (Mobile Station), UT (user terminal), MSS (Mobile Subscriber Station), SS (Subscriber Station), AMS (Advanced Mobile Station), WT (Wireless terminal), MTC (Machine-Type Communication) device, M2M (Machine-to-Machine) device, D2D (Device-to-Device) device, vehicle, robot, AI module, drone (Unmanned Aerial Vehicle, UAV), AR (Augmented Reality) device, VR (Virtual Reality) device, etc.

[0047] < Beam Management (BM) >

[0048] BM procedures are L1 (layer 1) / L2 (layer 2) procedures for acquiring and maintaining a set of base station (e.g., gNB, TRP, etc.) and / or terminal (e.g., UE) beams that can be used for downlink (DL) and uplink (UL) transmission / reception, and may include the following procedures and terminology.

[0049] - Beam measurement: An operation in which a base station or UE measures the characteristics of a received beam-forming signal.

[0050] - Beam determination: An operation in which a base station or UE selects its own transmit beam (Tx beam) / receive beam (Rx beam).

[0051] - Beam sweeping: The operation of covering a spatial area using a transmit and / or receive beam over a predetermined time interval in a predetermined manner.

[0052] - Beam report: An operation in which a UE reports information about a beam-formed signal based on beam measurement.

[0053] The BM procedure can be divided into (1) a DL BM procedure using SS (synchronization signal) / PBCH (physical broadcast channel) Block or CSI-RS, and (2) a UL BM procedure using SRS (sounding reference signal).

[0054] Additionally, each BM procedure may include Tx beam sweeping to determine the Tx beam and Rx beam sweeping to determine the Rx beam.

[0055] DL BM

[0056] The DL BM procedure may include (1) transmission of beamformed DL RSs (reference signals) (e.g., CSI-RS or SS Block (SSB)) of the base station and (2) beam reporting of the terminal.

[0057] Here, beam reporting may include preferred DL RS ID(identifier)(s) and corresponding L1-RSRP (Reference Signal Received Power).

[0058] The above DL RS ID may be an SSBRI (SSB Resource Indicator) or a CRI (CSI-RS Resource Indicator).

[0059] An example of beamforming using SSB and CSI-RS is described in detail below.

[0060] Both SSB and CSI-RS beams can be used for beam measurement. The measurement metric is L1-RSRP per resource / block. SSB is used for coarse beam measurement, and CSI-RS can be used for fine beam measurement. SSB can be used for both Tx beam sweeping and Rx beam sweeping.

[0061] Rx beam sweeping using SSB can be performed by the UE changing the Rx beam for the same SSBRI across multiple SSB bursts, where one SS burst contains one or more SSBs, and one SS burst set contains one or more SSB bursts.

[0062] Below we will look at the DL BM procedure.

[0063] The configuration for beam report using SSB is performed during CSI / beam configuration in RRC connected state (or RRC connected mode).

[0064] - The terminal receives configuration information from the base station. As a specific example, the terminal receives a CSI-ResourceConfig IE containing a CSI-SSB-ResourceSetList containing SSB resources used for BM from the base station.

[0065] Table 1 shows an example of the CSI-ResourceConfig IE. As shown in Table 1, BM configuration using SSB is not defined separately, and SSB is configured as a CSI-RS resource.

[0066]

[0067] In Table 1, the csi-SSB-ResourceSetList parameter indicates a list of SSB resources used for beam management and reporting in a single CSI-RS resource set. Here, the SSB resource set can be set to {SSBx1, SSBx2, SSBx3, SSBx4, …}. For example, the SSB index can be defined from 0 to 63.

[0068] - The terminal receives a downlink reference signal (DL RS) from the base station. As a specific example, the terminal receives an SSB resource from the base station based on the CSI-SSB-ResourceSetList.

[0069] - The terminal transmits a beam report to the base station. For example, if CSI-ReportConfig related to reporting on SSBRI (SSB Resource Indicator) and L1-RSRP is set, the terminal reports the best SSBRI and its corresponding L1-RSRP to the base station.

[0070] That is, when the reportQuantity of the above CSI-ReportConfig IE is set to 'ssb-Index-RSRP', the terminal reports the best SSBRI and the corresponding L1-RSRP to the base station.

[0071] And, if the terminal sets the CSI-RS resource in the same OFDM symbol(s) as the SSB (SS / PBCH Block) and 'QCL-TypeD' is applicable, the terminal can assume that the CSI-RS and SSB are quasi co-located from the 'QCL-TypeD' perspective.

[0072] Here, the QCL TypeD may mean that the antenna ports are QCL-connected from a spatial Rx parameter perspective. When a terminal receives multiple DL antenna ports in a QCL Type D relationship, the same reception beam may be applied. In addition, the terminal does not expect the CSI-RS to be configured in an RE that overlaps with the SSB RE.

[0073] < CSI-related actions >

[0074] Figure 1 is a flowchart showing an example of a CSI-related procedure.

[0075] Referring to Fig. 1, in order to perform one of the purposes of CSI-RS, a terminal (e.g., user equipment, UE) receives configuration information related to CSI from a base station (e.g., general Node B, gNB) through RRC (radio resource control) signaling (S110).

[0076] The configuration information related to the above CSI may include at least one of CSI-IM (interference management) resource related information, CSI measurement configuration related information, CSI resource configuration related information, CSI-RS resource related information, or CSI report configuration related information.

[0077] CSI resource configuration related information can be expressed as CSI-ResourceConfig IE. The CSI resource configuration related information defines a group including at least one of a non-zero power (NZP) CSI-RS resource set, a CSI-IM resource set, or a CSI-SSB resource set. That is, the CSI resource configuration related information includes a CSI-RS resource set list, and the CSI-RS resource set list can include at least one of an NZP CSI-RS resource set list, a CSI-IM resource set list, or a CSI-SSB resource set list. A CSI-RS resource set is identified by a CSI-RS resource set ID, and one resource set includes at least one CSI-RS resource. Each CSI-RS resource is identified by a CSI-RS resource ID.

[0078] Information related to the CSI report configuration includes a reportConfigType parameter indicating a time domain behavior and a reportQuantity parameter indicating a CSI-related quantity to be reported. The time domain behavior may be periodic, aperiodic, or semi-persistent.

[0079] The above reportQuantity parameter may be related to at least one of a channel quality indicator (CQI), a precoding matrix indicator (PMI), a CSI-RS resource indicator (CRI), an SSB resource block indicator (SSBRI), a layer indicator (LI), a rank indicator (RI), and a layer 1-reference signal received strength (L1-Reference Signal Received Strength (RSRP).

[0080] Measurement resources may include configurations for downlink signals and / or downlink resources on which a terminal will perform measurements to determine feedback information. Measurement resources may be configured as ZP and / or NZP CSI-RS resource sets associated with CSI reporting configurations. The NZP CSI-RS resource set may include a CSI-RS set or an SSB set. For example, L1-RSRP may be measured for a CSI-RS set or an SSB set.

[0081] The terminal measures CSI based on configuration information related to the CSI (S120). The CSI measurement may include (1) a process of receiving a CSI-RS by the terminal (S121) and (2) a process of calculating CSI using the received CSI-RS (S122). The terminal reports the CSI to the base station (S130).

[0082] Resource setting

[0083] Each CSI resource setting 'CSI-ResourceConfig' contains a configuration for S≥1 CSI resource sets (given by the higher layer parameter csi-RS-ResourceSetList). A CSI resource setting corresponds to a CSI-RS-resourcesetlist, where S represents the number of configured CSI-RS resource sets. Wherein, the list of S≥1 CSI resource sets contains either or both of NZP CSI-RS resource set(s) and SS / PBCH block (SSB) set(s) used for L1-RSRP computation, or contains CSI-IM resource set(s).

[0084] One or more CSI resource settings for channel measurement (CM) and interference measurement (IM) are configured via higher layer signaling.

[0085] - CSI-IM resource for interference measurement.

[0086] - NZP CSI-RS resources for interference measurement.

[0087] - NZP CSI-RS resources for channel measurement.

[0088] That is, the CMR (channel measurement resource) can be NZP CSI-RS for CSI acquisition, and the IMR (Interference measurement resource) can be NZP CSI-RS for CSI-IM and IM.

[0089] Here, CSI-IM (or ZP CSI-RS for IM) is mainly used for inter-cell interference measurement.

[0090] And, NZP CSI-RS for IM is mainly used for intra-cell interference measurement from multi-user.

[0091] A UE may assume that the CSI-RS resource(s) configured for channel measurement for one CSI reporting and the CSI-IM / NZP CSI-RS resource(s) for interference measurement (when NZP CSI-RS resource(s) are used for interference measurement) are in a QCL relationship with respect to 'QCL-TypeD' per resource.

[0092] As we have seen, resource setting can mean a resource set list.

[0093] For aperiodic CSI, each trigger state set using the higher layer parameter CSI-AperiodicTriggerState is associated with one or more CSI-ReportConfigs, and each CSI-ReportConfig is linked to a periodic or semi-persistent or aperiodic resource setting.

[0094] One reporting setting can be linked to up to three resource settings.

[0095] < Description of Rel-17 / 18 beam management >

[0096] In Rel-17, both the DL TCI state and the UL TCI state can be indicated through DL DCI (e.g., DCI format 1-1 or 1-2), or only the UL TCI state can be indicated without indicating the DL TCI state. Therefore, the methods used for UL beam and power control (PC) configuration in the existing R15 / R16 are replaced in Rel-17 with the above UL TCI state indication method. More specifically, in R17, one UL TCI state can be indicated through the TCI field of DL DCI, and the UL TCI state is applied to all PUSCHs and all PUCCHs after a certain time called the beam application time, and can be applied to some or all of the indicated SRS resource sets. In addition, the base station can perform a terminal common beam update by using DCI and / or MAC-CE to perform indication / update with one beam in common (using a joint or separate TCI state) for specific DL / UL channel / RS combinations of multiple terminals. The target channels / RS of common beam update include UE-dedicated CORESET, UE-dedicated reception on PDSCH for DL, DG / CG-PUSCH, all or a subset of dedicated PUCCH for UL, and additionally, AP CSI-RS for tracking / BM, SRS can be set as target channels / RS.In Rel-18, considering the M-TRP environment, the method of indicating multiple UL TCI states (and / or DL ​​TCI states) through the TCI field of DL DCI has been standardized, and the uplink / downlink resources to which multiple indicated TCIs are applied can be defined / configured depending on the S-DCI based M-TRP environment and the M-DCI based M-TRP environment.

[0097] < AIML related explanation >

[0098] Advances in AI / ML (Artificial intelligence / machine learning) technology are leading to the intelligence / advanced advancement of the nodes and terminals that make up wireless communication networks.

[0099] Below, a functional framework for AI operation is described with reference to FIG. 2.

[0100] Figure 2 illustrates the functional framework of the AI / ML model.

[0101] Below, to explain AI (or AI / ML) more specifically, the terms can be defined as follows.

[0102] - Data collection: Data collected from network nodes, management entities, or UEs as a basis for AI model training, data analysis, and inference.

[0103] - AI Model: A data-driven algorithm that applies AI technology to generate a set of outputs containing predictive information and / or decision parameters based on a set of inputs.

[0104] - AI / ML Training: An online or offline process of training an AI model by learning features and patterns that best represent the data and obtain a trained AI / ML model for inference.

[0105] - AI / ML Inference: The process of making predictions or inducing decisions based on collected data and the AI ​​model using a trained AI model.

[0106] Referring to FIG. 2, the data collection function (10) is a function that collects input data and provides processed input data to the model training function (20) and the model inference function (30).

[0107] Examples of input data may include measurements from UEs or other network entities, feedback from actors, and output from AI models.

[0108] The Data Collection function (10) performs data preparation based on input data and provides input data processed through data preparation. Here, the Data Collection function (10) does not perform data preparation specific to each AI algorithm (e.g., data pre-processing and cleaning, formatting, and transformation), but can perform data preparation common to AI algorithms.

[0109] After the data preparation process is performed, the Model Training function (10) provides training data (11) to the Model Training function (20) and provides inference data (Inference Data) (12) to the Model Inference function (30). Here, the Training Data (11) is data required as input for the AI ​​Model Training function (20). The Inference Data (12) is data required as input for the AI ​​Model Inference function (30).

[0110] The Data Collection function (10) may be performed by a single entity (e.g., UE, RAN node, network node, etc.) or may be performed by multiple entities. In this case, Training Data (11) and Inference Data (12) may be provided to the Model Training function (20) and Model Inference function (30), respectively, from multiple entities.

[0111] The Model Training function (20) is a function that performs AI model training, validation, and testing, which can generate model performance metrics as part of the AI ​​model testing process. If necessary, the Model Training function (20) also handles data preparation (e.g., data pre-processing and cleaning, forming, and transformation) based on the Training Data (11) provided by the Data Collection function (10).

[0112] Here, Model Deployment / Update (13) is used to initially deploy the trained, verified, and tested AI model to the Model Inference function (30) or to provide the updated model to the Model Inference function (30).

[0113] The Model Inference function (30) is a function that provides AI model inference output (16) (e.g., prediction or decision). If applicable, the Model Inference function (30) may provide model performance feedback (14) to the Model Training function (20). In addition, the Model Inference function (30) is also responsible for data preparation (e.g., data pre-processing and cleaning, forming, and transformation) based on the Inference Data (12) provided by the Data Collection function (10), if necessary.

[0114] Here, Output (16) refers to the inference output of the AI ​​model generated by the Model Inference function (30), and the details of the inference output may vary depending on the use case.

[0115] Model Performance Feedback (14) can be used to monitor the performance of the AI ​​model if available, and this feedback may be omitted.

[0116] The actor function (40) is a function that receives an output (16) from the model inference function (30) and triggers or performs a corresponding task / action. The actor function (40) can trigger tasks / actions for other entities (e.g., one or more UEs, one or more RAN nodes, one or more network nodes, etc.) or for itself.

[0117] Feedback (15) can be used to derive training data (11), inference data (12), or to monitor the performance of the AI ​​model, its impact on the network, etc.

[0118] Meanwhile, the definitions of training / validation / test in the data set used in AI / ML can be distinguished as follows.

[0119] - Training data: This refers to the data set for learning the model.

[0120] - Validation data: This refers to a data set used to validate a model that has already completed training. In other words, it refers to a data set typically used to prevent overfitting of the training data set.

[0121] It also refers to a data set for selecting the best model among the various models learned during the learning process. Therefore, it can be viewed as a type of learning.

[0122] - Test data: This refers to the data set for final evaluation. This data is unrelated to learning.

[0123] In the case of the above data set, if the training set is generally divided, the training data and validation data can be divided and used in a ratio of 8:2 or 7:3 within the entire training set, and if the test is included, it can be divided and used in a ratio of 6:2:2 (training: validation: test).

[0124] The functions exemplified in FIG. 2 above may be implemented in a RAN node (e.g., a base station, a TRP, a central unit (CU) of a base station, etc.), a network node, an operation administration maintenance (OAM) of a network operator, or a UE.

[0125] In this document, ' / ' means 'and', 'or', or 'and / or' depending on the context.

[0126] In this specification, 'beam' may mean a source RS for a 'spatial filter' or a 'spatial relation', and may be interpreted as a QCL (type-D) RS or a TCI state or (in the case of uplink) a spatial relation RS.

[0127] For example, in this specification, 'beam' may mean a spatial filter determined based on the reference RS or the source RS. The spatial filter may include a spatial domain filter, a spatial domain transmission filter, and a spatial domain receive filter. For example, in this specification, 'beam' may be interpreted / replaced with a reference signal index (RS index), a reference signal resource index (RS resource index), and / or a resource indicator (e.g., RS index, SSB index, CSI-RS resource index, SRS resource index, SSB Resource Indicator (SSBRI), CSI-RS Resource Indicator (CRI), etc.).

[0128] For example, a beam associated with UL may be referred to as i) a spatial filter (for uplink transmission or uplink reception), ii) a spatial domain filter (for uplink transmission or uplink reception), iii) an uplink spatial domain transmission filter, iv) an uplink spatial domain receive filter, v) an uplink transmit spatial filter (UL Tx spatial filter), or vi) an uplink receive spatial filter (UL Rx spatial filter).

[0129] For example, a beam associated with DL may be referred to as i) a spatial filter (for downlink transmission or downlink reception), ii) a spatial domain filter (for downlink transmission or downlink reception), iii) a downlink spatial domain transmission filter, iv) a downlink spatial domain receive filter, v) a downlink transmit spatial filter (DL Tx spatial filter) or vi) a downlink receive spatial filter (DL Rx spatial filter).

[0130] In the NR standard, QCL setting and spatialRelation setting by TCI state setting are utilized to configure UL / DL transmission / reception beam of terminal. In the Rel-15 NR standard, RRC and MAC CE signaling are mainly utilized for UL / DL number / transmission beam. Dynamic signaling has been allowed only for PDSCH reception beam by utilizing the TCI state field of DL grant DCI. Through the Rel-17 / 18 NR standard, a unified TCI framework was introduced. Specifically, a method was introduced to dynamically manage common beam by indicating TCI using DCI for reception / transmission beam. In the standardization after Rel-19, there is a possibility that there will be discussions on network energy saving (NES) or AI / ML aspects, such as base stations requesting on / off of specific DL RS(s) or requesting configuration of specific DL RS(s) to collect training data or input data of AI / ML models on the terminal side.

[0131] This specification proposes a method for reporting preferred / non-preferred DL RS of a terminal and proposes subsequent base station / terminal operations.

[0132] < UE initiated BM related background >

[0133] In existing LTE / NR systems, the reporting of CSI / beam information from a UE is determined / controlled by the base station / network (except in the case of BFR). These NW (network)-initiated / triggered reports have limitations in that they require UEs to be configured / instructed to frequently send CSI / beam information in environments where the wireless channel is likely to change rapidly. In such environments, the UL resource overhead for CSI / beam reporting and the related DL measurement RS overhead increase, and the UE's power consumption also increases due to frequent uplink transmission. Furthermore, the more UEs within cell / TRP coverage, the greater the UL resource overhead, as each UE must be allocated UL resources. To overcome these limitations of NW-initiated / triggered reports, recently emerging approaches are UE-initiated / triggered reports or event-based / triggered reports.

[0134] In the UE-initiated / triggered report method or event-based / triggered report method, the UE determines whether and when to report. By performing the report only when necessary (e.g., when a specific event occurs), UL resource overhead and UE power consumption can be reduced. With the above motivation, standardization of UE-initiated / triggered beam reports is expected in NR Rel-19. Furthermore, in 6G communication systems, UE-initiated / triggered or event-based transmission methods can be more actively expanded and adopted to efficiently manage uplink resources.

[0135] In the NR system, there are two representative reporting methods for event-based or UE-initiated / triggered information: SR (scheduling request) and BFR (beam failure recovery). SR reports whether PUSCH allocation is required for UL-SCH transmission, and BFR reports whether BF occurs and new beam-related information. This information is conveyed / transmitted to the base station in an explicit or implicit manner (e.g., conveying a new beam index as PRACH resource selection information). The above-mentioned SR / BFR-related information is conveyed simultaneously or separately through one or two UL resources (e.g., BFRQ on PUCCH + beam information via MAC-CE on PUSCH).

[0136] In this specification, information transmitted to the network based on a terminal event and / or via a UE-initiated / triggered transmission method (e.g., SR, BFRQ, new beam information, etc.) as described above is referred to as “event information” for convenience of explanation. Event information is composed of one or more information parts / blocks, and encoding / rate matching / RE mapping can be performed for each part / block unit. Each information part / unit can also be transmitted via different transmission methods (e.g., BFRQ via UCI as an L1 message, new beam information via MAC-CE as an L2 message).

[0137] < NES related background >

[0138] Energy conservation at base stations can contribute to building eco-friendly networks by reducing carbon emissions and reducing operational expenditures (OPEX) for telecommunications companies. Therefore, energy conservation at base stations is a key consideration in wireless communication systems, including 3GPP. In particular, the introduction of 5G communications will require higher data rates, necessitating more antennas and providing services across wider bandwidths and frequency bands. Consequently, recent studies have shown that base station energy costs have reached up to 20% of total OPEX. This increased interest in base station energy conservation led to the approval of a new study item, "Study on Network Energy Savings," and a new work item, "Network Energy Savings for NR," in 3GPP NR Release 18.

[0139] Specifically, in the study item, the following enhancement techniques are being considered to improve the energy saving capability of the base station from the perspective of transmission and reception.

[0140] - How to achieve more efficient operation dynamically and / or semi-statically and finer granularity adaptation of transmissions and / or receptions in one or more of network energy saving techniques in time, frequency, spatial, and power domains, with potential support / feedback from UE, and potential UE assistance information

[0141] Additionally, the following enhancement techniques are being considered for the work item:

[0142]

[0143] The base station may perform at least one of the following operations 1) to 5) for NES purposes.

[0144] 1) Control on / off for a certain duration on the time axis

[0145] 2) Control of transmission and reception resources for UE-common or UE-specific signals / channels

[0146] 3) Changes in frequency axis resources

[0147] 4) Transmission power control

[0148] 5) Turn on / off antenna ports or TRPs in the spatial domain.

[0149] The state in which the above-described technology(s) (defined as NES_tech for convenience) is applied can be defined as NES mode or NES state.

[0150] For example, the base station can inform the terminal of which NES_tech(s) applies for each NES_tech (or group thereof) (Approach 1).

[0151] For example, a base station can pre-configure the corresponding NES_tech (or its group)(s) for each codepoint of a specific indicator (the indicator may be indicated by DCI or MAC CE, etc., or may be an indicator set by higher layer signaling) (Approach 2).

[0152] For Approach 1, the state of a terminal to which at least one NES_tech is applied can be defined as NES mode or NES state. Alternatively, it can be referred to as different NES modes or different NES states depending on which NES_tech is applied.

[0153] For Approach 2, the following NES modes or NES states can be defined. For example, when there is a 1-bit indicator, '0' has no corresponding NES_tech and '1' can have one or more NES_techs associated with it. Based on the indicator, when '1' is indicated to the terminal, the corresponding state can be defined as NES mode or NES state. For example, when there is a 2-bit indicator, '00' has no corresponding NES_tech, '01' has one or more NES_tech_As associated with it, '10' has one or more NES_tech_Bs associated with it, and '11' has one or more NES_tech_Cs associated with it. Based on the indicator, when a codepoint other than '00' is indicated to the terminal, the corresponding state can be defined as NES mode or NES state. If '01' is indicated, it can be defined as NES state#1, if '10' is indicated, it can be defined as NES state#2, if '11' is indicated, it can be defined as NES state#3. It can be distinguished whether it is an NES state or not or which NES state it is for each codepoint.

[0154] A base station can turn on or off certain spatial elements or adjust the power value for a downlink signal / channel for the purpose of NES. In this specification, spatial elements may mean antenna ports, active transceiver chains, panels, or TRPs. In order to dynamically apply various NES technologies in the spatial and power domains, the base station can link CSI-RS resources (sets) with different antenna ports or link multiple power offsets for a single CSI report setting (e.g., CSI-ReportConfig). For example, the multiple power offsets can be based on the powerControlOffset parameter, which is a power offset value between a PDSCH and a CSI-RS, the powerControlOffsetSS parameter, which is a power offset value between an SSS and a CSI-RS, etc.

[0155] < Background related to AI / ML beam management >

[0156] In the Rel-18 AI / ML study item, we conducted a study on performance analysis and potential specification impact through evaluation when NW and / or UE-side AI / ML models operate in three use cases: CSI compression / prediction, beam management, and positioning. In particular, in the beam management use case, we divided the sub-use cases into BM-case1 and BM-case2, and studied performance analysis and potential specification impact for spatial domain beam prediction and temporal beam prediction. The WID goals of AI / ML BM, BM-case1, and BM-case2 are summarized in Tables 3 to 5 below.

[0157] - AI / ML BM's WID goals

[0158]

[0159] - BM-case1: Spatial domain downlink beam prediction for beam set A based on measurement results for beam set B.

[0160]

[0161] - BM-case2: Temporal downlink beam prediction for beam set A based on past measurement results for beam set B.

[0162]

[0163] Additionally, an example of the operation for data collection of AI / ML models in the Beam management use case is shown in Table 6 below.

[0164]

[0165] In particular, in the case of UE-side AI / ML, actions such as requesting the base station to transmit the DL RS desired by the terminal for data collection of the terminal AI / ML model can be performed.

[0166] < Background of Rel-18 NES Standardization >

[0167] Rel-18 NES introduces energy-saving technologies in the spatial and power domains at the base station. The sub-configurations introduced for CSI reporting in the Rel-18 NES standardization are summarized below.

[0168] Sub-configuration(s) may be set for a specific CSI report configuration. The sub-configuration(s) may be set based on at least one of the following i) to iii).

[0169] i) Only some resource(s) among the NZP CSI-RS resources in the CMR set of the CSI resource configuration linked to the corresponding CSI report configuration may be configured to be included in the sub-configuration.

[0170] ii) Only a specific subset of ports of multi-port CSI-RS resources (having the same number of ports) within the CMR set of the CSI resource configuration linked to the corresponding CSI report configuration can be configured to be included in the sub-configuration.

[0171] iii) The powerOffset parameter in the sub-configuration can be set to include an additional offset value to the existing powerControlOffset, which sets the relative power offset of CSI-RS and PDSCH.

[0172] A sub-configuration based on the above i) and a sub-configuration based on the above ii) cannot be set together in a single CSI report configuration. A sub-configuration(s) based on a combination of i) and iii) or a sub-configuration(s) based on a combination of ii) and iii) can be set together in a single CSI report configuration.

[0173] Through the above i) and ii), the base station can configure a CSI-RS resource with simplified port virtualization (through the configured sub-configuration) or a CSI-RS resource with a reduced number of ports (through the configured sub-configuration). Afterwards, the base station can determine whether to switch to a CSI report configuration that applies energy saving in the spatial domain after receiving a CSI report related to the sub-configuration from the terminal. The base station can transmit a CSI-RS using a sub-configuration in which a CSI-RS with an additional power offset applied based on the above iii) is configured. The base station can determine whether to apply energy saving in the power domain by receiving a CSI report related to the sub-configuration from the terminal.

[0174] Meanwhile, when a sub-configuration is set for a specific CSI report configuration as described above, in the case of a periodic CSI report, a CSI report must be performed for all of the set sub-configuration(s). In the case of an SP / AP CSI report, the base station instructs the terminal based on MAC CE / DCI which of the set sub-configurations the terminal is to perform reporting on. More specifically, a trigger state for semi-persistent CSI reporting or aperiodic CSI reporting is indicated based on the CSI request field of the DCI. Based on the list included in the trigger state (e.g., CSI-ReportSubConfigTriggerList), N sub-configurations(es) can be indicated among L set sub-configurations. N is an integer greater than or equal to 1. Since the CSI report must be performed for all of the set sub-configuration(s) as described above (especially in the case of a periodic CSI report), the following problems may occur.

[0175] The base station must transmit CSI-RS for multiple configurations (e.g., all configured sub-configurations or one or more indicated sub-configurations), and the terminal will have increased CSI reporting overhead and occupy a lot of UL resources.

[0176] The existing operation for the sub-configuration described below is described.

[0177] A CSI-ReportConfig may contain a list of sub-configurations provided by the upper layer parameter csi-ReportSubConfigToAddModList, each sub-configuration identified by a CSI-ReportSubConfigId and set to nzp-CSI-RS-ResourceList corresponding to one or more CSI-RS resource lists, or portSubsetIndicator corresponding to a subset of CSI-RS antenna ports, or powerOffset corresponding to a power offset of PDSCH for CSI-RS in addition to powerControlOffset of CSI-RS resources.The UE does not expect a CSI-ReportConfig to be configured that contains a mix of sub-configurations, provided by the higher layer parameter csi-ReportSubConfigToAddModList, where each sub-configuration is identified by CSI-ReportSubConfigId and configured with nzp-CSI-RS-ResourceList which corresponds to a list of one or more CSI-RS resources or configured with portSubsetIndicator which corresponds to a CSI-RS antenna port subset, and / or configured with powerOffset which corresponds to a power offset for PDSCH relative to CSI-RS additional to powerControlOffset of the CSI-RS resource(s).A UE is not expected to be configured with a CSI-ReportConfig that contains a mix of sub-configuration(s) each configured with nzp-CSI-RS-ResourceList which corresponds to a list of one or more CSI-RS resources and some other sub-configuration(s) each configured with portSubsetIndicator which corresponds to CSI-RS antenna port subset).

[0178] If the UE is configured with a CSI-ReportConfig with the higher layer parameter reportQuantity set to 'cri-RI-CQI',

[0179] - If the upper layer parameter non-PMI-PortIndication included in CSI-ReportConfig is set in the UE, r ports are indicated in the layer order for rank r, and each CSI-RS resource of the CSI resource configuration is linked to the CSI-ReportConfig according to the order of the associated NZP-CSI-RS-ResourceId of the CSI resource configuration linked for channel measurement provided in the upper layer parameter resourcesForChannelMeasurement. The set upper layer parameter non-PMI-PortIndication includes the port index sequence. is included, where is the CSI-RS port index associated with rank v. and here is the number of ports of the CSI-RS resource. The UE shall report only the RIs corresponding to the configured fields of PortIndexFor8Ranks. If the UE configures CSI-ReportConfig containing a list of sub-configurations with portSubsetIndicator set for each sub-configuration, and the upper layer parameter non-PMI-PortIndication is provided separately for the sub-configuration, corresponds to the number of bits having value 1 in the bitmap portSubsetIndicator of the lower configuration, and the CSI-RS port indices are derived by mapping antenna ports corresponding to all bits having value 1 in portSubsetIndicator to consecutive antenna ports starting from CSI-RS port index 0 in increasing order of bit position of portSubsetIndicator (if the UE is configured with a higher layer parameter non-PMI-PortIndication contained in a CSI-ReportConfig, ports are indicated in the order of layer ordering for rank rand each CSI-RS resource in the CSI resource setting is linked to the CSI-ReportConfig based on the order of the associatedNZP-CSI-RS-ResourceId the linked CSI resource setting for channel measurement given by the higher layer parameter resourcesForChannelMeasurement. The configured higher layer parameter non-PMI-PortIndicationcontains a sequence of port indices, where are the CSI-RS port indices associated with rank v and where is the number of ports in the CSI-RS resource. The UE shall only report RI corresponding to the configured fields ofPortIndexFor8Ranks. If the UE is configured with aCSI-ReportConfigthat contains a list of sub-configurations withportSubsetIndicatorconfigured in each sub-configuration, and the higher layer parameternon-PMI-PortIndicationis separately provided for a sub-configuration, then corresponds to the number of bits with value 1 in the bitmapportSubsetIndicatorfor the sub-configuration and the CSI-RS port indices are derived by mapping antenna ports corresponding to all bits with value of 1 inportSubsetIndicatoras consecutive antenna ports starting at CSI-RS port index 0 in increasing order of the bit position inportSubsetIndicator).

[0180] - UE에 상위 계층 파라미터 non-PMI-PortIndication가 설정되지 않은 경우, UE는 CSI-ReportConfig에 연결된 CSI 자원 설정의 각 CSI-RS 자원에 대해 CSI-RS 포트 인덱스 This ranking It is assumed that it is related to here. is the number of ports of the CSI-RS resource. If a CSI-ReportConfig containing a list of sub-configurations is set in the UE, a portSubsetIndicator is set for each sub-configuration, and the upper layer parameter non-PMI-PortIndication is not provided for the sub-configuration, corresponds to the number of bits having value 1 in the bitmap portSubsetIndicator of the lower configuration, and the CSI-RS port index is derived by mapping antenna ports corresponding to all bits having value 1 in portSubsetIndicator to consecutive antenna ports starting from CSI-RS port index 0 in increasing order of bit positions of portSubsetIndicator (if the UE is not configured with higher layer parameter non-PMI-PortIndication, the UE assumes, for each CSI-RS resource in the CSI resource setting linked to theCSI-ReportConfig, that the CSI-RS port indices are associated with ranks where is the number of ports in the CSI-RS resource. If the UE is configured with aCSI-ReportConfigthat contains a list of sub-configurations withportSubsetIndicatorconfigured in each sub-configuration and the higher layer parameternon-PMI-PortIndicationis not provided for a sub-configuration, then corresponds to the number of bits with value 1 in the bitmapportSubsetIndicatorfor the sub-configuration and the CSI-RS port indices are derived by mapping antenna ports corresponding to all bits with value of 1 inportSubsetIndicatoras consecutive antenna ports starting at CSI-RS port index 0 in increasing order of the bit position inportSubsetIndicator).

[0181] When calculating CQI for a rank, the UE must use the indicated port for that rank for the selected CSI-RS resource. The precoder for the indicated port is (When calculating the CQI for a rank, the UE shall use the ports indicated for that rank for the selected CSI-RS resource. The precoder for the indicated ports shall be assumed to be the identity matrix scaled by ).

[0182] In this specification, based on the three backgrounds described above (UE initiated BM, NES, AI / ML), we propose a method for reporting preferred / non-preferred DL RS of a terminal, and propose subsequent base station / terminal operations.

[0183] < Problems to be solved in this specification >

[0184] NES aspect: In Rel-19 NES WI, the possibility of standardizing the following operations is being discussed. Specifically, if the base station transmits a light synch signal or a long-period SSB (e.g., an SSB defined / configured for power saving, a simplified synchronization signal (PSS only or PSS & SSS), or an SSB with a longer period than the existing SSB), and the UE transmits a WUS signal, the base station can transmit a general SSB (e.g., an SSB with the same structure as the existing one (PSS, SSS, PBCH), or an SSB with the same period as the existing one). There is an analysis that base station power saving is possible when the UE transmits a full-SSB within a specific time interval due to the WUS. However, power saving seems difficult when multiple UEs transmit WUS consecutively, and the problem arises that it is inefficient because all SSBs are turned on by a specific UE. In addition, energy at the base station may be wasted due to the sub-configuration introduced in Rel-18 NES. Specifically, the UE must also perform CSI reports for all configured sub-configurations (especially for periodic CSI reports). This can waste energy at the base station, as the base station must transmit CSI-RSs for multiple configurations (e.g., all configured sub-configurations or one or more indicated sub-configurations). Furthermore, increased CSI reporting overhead on the UE side can lead to UL resource congestion.

[0185] AI / ML aspect: A common understanding of Set A and / or Set B between the base station and the UE is required (to some extent). In addition to the DL RS / CMR already configured for UE measurement / reporting purposes (via parameters such as reportConfig / CSI-resourceConfig), if the UE requests transmission of a specific UE-specific DL RS, a discussion is needed on what criteria / methodology will be used to express the DL RS and how to request / report transmission of the DL RS.

[0186] In this specification, ' / ' can be interpreted as 'and', 'or', or 'and / or' depending on the context.

[0187] Proposal 1

[0188] The terminal may report the SSB index(es) to the base station as a preferred DL RS or / and a non-preferred DL RS.

[0189] Example 1)

[0190] [Terminal operation]

[0191] For example, a terminal may report a non-preferred SSB index. The terminal releases / deactivates reportConfig and / or CMR set (or the corresponding CMR) related to a (UE-specific) CMR associated with the reported non-preferred SSB index. Here, the (UE-specific) CMR associated with the non-preferred SSB index may refer to a DL RS having the non-preferred SSB index as a QCL top source. For example, a (UE-specific) CMR (channel measurement resource) associated with an SSB index (e.g., non-preferred SSB index, preferred SSB index) reported in the present specification may be associated with a DL RS having a QCL relationship (e.g., a QCL relationship based on typeD) with an SSB (SS / PBCH block) based on the corresponding SSB index.

[0192] The above release / deactivation may be performed after a certain period of time from the reporting of the non-preferred SSB index or after receiving a confirmation message from the base station. The terminal will no longer perform measurement and reporting related to the released / deactivated reportConfig or / and CMR set (or the corresponding CMR).

[0193] For example, a terminal may report a non-preferred SSB index. The terminal (e.g., a terminal supporting Rel-18 NES) releases / deactivates a sub-configuration related to a (UE-specific) CMR associated with the reported non-preferred SSB index. As a specific example, in case of periodic CSI reporting, the sub-configuration may include a sub-configuration related to a CMR based on the non-preferred SSB index among sub-configurations configured based on the CSI report configuration. As a specific example, in case of semi-persistent / aperiodic CSI reporting, one or more sub-configurations may be indicated based on a trigger state among the configured sub-configurations. The sub-configuration may include a sub-configuration related to a CMR based on the non-preferred SSB index among the one or more indicated sub-configurations.

[0194] Or / and, the terminal no longer performs measurement & reporting related to the sub-configuration. Here, the (UE-specific) CMR related to the non-preferred SSB index may mean a DL RS with the non-preferred SSB index as a QCL top source. The release / deactivation may be performed after a certain period of time from the reporting of the non-preferred SSB index or after receiving a confirmation message from the base station.

[0195] More specifically, when a terminal reports a non-preferred SSB index, a threshold may be set by the base station to determine whether the terminal is non-preferred for the SSB index. For example, the threshold may be related to SSB reception sensitivity.

[0196] For example, a terminal may report a preferred SSB index (determined according to the specific reception sensitivity threshold). After a certain period of time from the report or after receiving a confirmation message from the base station, the terminal releases / deactivates reportConfig, sub-configuration, and / or CMR set (or the corresponding CMR) related to (UE-specific) CMRs related to SSB indices other than the reported SSB index. The terminal no longer performs measurement & reporting related to SSB index(es) other than the reported preferred SSB index. As a specific example, in case of periodic CSI reporting, the sub-configuration may include a sub-configuration related to CMRs based on SSB indices other than the preferred SSB index among the sub-configurations configured based on the CSI report configuration. As a specific example, in case of semi-persistent / aperiodic CSI reporting, one or more sub-configurations may be indicated based on a trigger state among the configured sub-configurations. The above sub-configuration may include a sub-configuration related to CMR based on an SSB index other than the preferred SSB index among the one or more indicated sub-configurations.

[0197] [Base station operation]

[0198] For example, after receiving a non-preferred SSB index from a terminal, the base station releases / deactivates a (UE-specific) CMR related to the non-preferred SSB index from the terminal after a certain period of time from the report or after transmitting a related confirm message, or stops receiving reports on the (UE-specific) CMR related to the non-preferred SSB index. Here, the (UE-specific) CMR related to the non-preferred SSB index may mean a DL RS having the non-preferred SSB index as a QCL top source.

[0199] For example, after receiving a non-preferred SSB index from a terminal, the base station may perform at least one of the following actions after a certain period of time from the report (for a terminal supporting Rel-18 NES) or after transmitting a related confirm message. The base station may release / deactivate a sub-configuration related to the non-preferred SSB index from the terminal. The base station may stop receiving reports on the sub-configuration related to the non-preferred SSB index.

[0200] For example, after receiving a preferred SSB index from a terminal, the base station may perform at least one of the following actions after a certain period of time or after transmitting a related confirm message.

[0201] The base station may release / deactivate (UE-specific) CMRs or / and sub-configurations related to SSB indices other than the preferred SSB index from the corresponding terminal. The base station may stop receiving reports on (UE-specific) CMRs or / and sub-configurations related to SSB indices other than the preferred SSB index.

[0202] For example, in the examples described above, after a certain period of time may be after N slots (where N is a real number excluding negative numbers) or after X slots (where X is a real number excluding negative numbers). For example, after receiving a confirmation message from the base station may mean 3 ms after the terminal receives the A / N confirmation from the base station. Here, the number of slots corresponding to N or X may be configured by the base station or may be determined by a set rule.

[0203] Effect of Embodiment 1) According to Embodiment 1, the following operations can be performed. The terminal monitors the reception sensitivity of a specific SSB index and a (UE-specific) CMR related to the SSB. If it is determined that the reception probability of the corresponding DL RSs decreases or the corresponding DL RSs do not steer the terminal due to the mobility of the terminal or a change in geometry, the terminal can report to the base station that it will stop measuring / tracking / reporting for the specific SSB and the (UE-specific) CMR related to the SSB. Through this operation, the terminal can reduce unnecessary measurements and obtain a power saving effect. In addition, the base station can obtain a power saving effect in terms of NES by turning off the DL RS itself if the corresponding DL RSs are UE-specifically configured DL RSs.

[0204] Example 2)

[0205] A terminal may report a preferred SSB index. The report may be related to i) a request / recommend to reduce the transmission power of the preferred SSB index and ii) the transmission power of (UE-specific) CMRs associated with the preferred SSB index. Here, the CMR may mean a DL RS having the preferred SSB index as a QCL top source. The present embodiment is intended to adjust the transmission power when the reception sensitivity is higher than necessary. For example, it may be assumed that a (UE-specific) CMR associated with a preferred SSB index is determined to be an optimal reception beam for the terminal, and the CMR is being received with a strong reception sensitivity higher than a specific reception sensitivity threshold. In this case, it is necessary to reduce the transmission power of the preferred SSB index and the transmission power of the (UE-specific) CMRs associated with the preferred SSB index.

[0206] Effect of Embodiment 2) According to Embodiment 2, the following operations can be performed. Unlike the operation of Embodiment 1, a preferred SSB index is reported. Based on the preferred SSB index and the (UE-specific) CMRs related to the preferred SSB index having a stronger reception sensitivity (than necessary), the terminal can request the base station to scale down transmission power. If the base station determines that power scale-down is necessary after receiving the terminal report, the base station can reduce the transmission power to obtain a power saving effect in terms of NES.

[0207] Example 3)

[0208] [Terminal operation]

[0209] A UE may report its preferred SSB index. (After a certain period of time from the report or after receiving a confirmation message from the base station) The UE may expect the base station to configure a specific reportConfig and / or a specific CMR set for data collection purposes of the AI / ML model on the UE side, with (UE-specific) CMRs associated with the reported preferred SSB index.

[0210] The above specific reportConfig and / or specific CMR set may be set in advance by the base station to the terminal for the purpose of setting the Set B beam set. Here, the CMR may mean a DL RS with the preferred SSB index as the QCL top source.

[0211] In one embodiment, the preferred SSB index report of the terminal may include i) one SSB index or ii) multiple SSB indexes. For example, if the report includes one SSB index, the report may mean that B CMRs (where B is a natural number) related to the reported SSB index are to be set for a specific reportConfig or / and a specific CMR set. For example, if the report includes multiple SSB indexes, the report may mean that one CMR related to each of the multiple reported SSB indexes is to be set for a specific reportConfig or / and a specific CMR set (e.g., the number of multiple reported SSB indexes = the number of CMRs to be set are set to be mapped 1:1).

[0212] In one embodiment, the preferred SSB index report of the terminal may include multiple SSB indices. The terminal may additionally report coefficient information for each of the multiple SSB indices. The terminal may perform the report by expressing the DL RS required for data collection of the terminal-side AI / ML model as a linear combination of the multiple SSB index beams.

[0213] The method for reporting a preferred SSB index of a terminal to set up a DL RS for the purpose of data collection of the terminal AI / ML model as described above can be utilized to request DL RS settings related to the terminal's AI / ML model. Specifically, the method for reporting a preferred SSB index of a terminal can be utilized to request DL RS settings for comparative / reference measure / monitoring for performance monitoring of the terminal's AI / ML model. In this case, the base station can configure the DL RS according to the request for a specific reportConfig or / and a specific CMR set for performance monitoring of the terminal-side AI / ML model.

[0214] [Base station operation]

[0215] For example, a base station can receive a preferred SSB index from a terminal. (After a certain period of time from the reception of the preferred SSB index or after transmitting a related confirm message) The base station can set a (UE-specific) CMR related to the preferred SSB index from the terminal to a specific reportConfig or / and a specific CMR set for data collection purposes of the terminal-side AI / ML model. Here, the CMR can mean a DL RS that has the preferred SSB index as a QCL top source.

[0216] For example, a base station can receive a preferred SSB index from a terminal (after a certain period of time from the reception of the preferred SSB index or after transmitting a related confirm message). The base station can configure a DL RS in the form of a linear combination of multiple SSB index beams related to the preferred SSB index from the terminal for data collection purposes of an AI / ML model on the terminal side for a specific reportConfig or / and a specific CMR set.

[0217] For example, in the examples described above, after a certain period of time may be after N slots (where N is a real number excluding negative numbers) or after X slots (where X is a real number excluding negative numbers). For example, after receiving a confirmation message from the base station may mean 3 ms after the terminal receives the A / N confirmation from the base station.

[0218] Effect of Example 3) According to Example 3, the following operations can be performed. The terminal can request / report DL RS for data collection of the terminal-side AI / ML model to the base station. At this time, the terminal can request the base station to set (Set B beam) by expressing the beam desired by the terminal using the SSB beam as the anchor beam. Through this operation, the terminal can appropriately perform data collection for training / retraining / inference / monitoring of the AI / ML model for beam prediction of the terminal in the operations of BM-case1 and BM-case2.

[0219] Example 4)

[0220] [Terminal operation]

[0221] The terminal may receive settings for training / retraining / inference / monitoring of a UE-side AI / ML model from the base station. The settings may include information regarding the following i) and / or ii).

[0222] i) (cell / site / area / zone-common) A combination of multiple Sets A or / and Set B that have a common cell / site / area / zone.

[0223] ii) (cell / site / area / zone-specific) A combination of multiple Sets A or / and Set B specific to a cell / site / area / zone.

[0224] A terminal can report a preferred SSB index (or / and a non-preferred SSB index). After a certain period of time from the report or after receiving a confirmation message from the base station, the terminal can perform beam prediction using the UE-side AI / ML model.

[0225] Specifically, the terminal may perform measurement and / or beam prediction operations based on i) a combination of Set A and / or Set B associated with (UE-specific) CMRs associated with a preferred SSB index (or / and not associated with a non-preferred SSB index) and / or ii) a combination of Set A and / or Set B associated with (UE-specific) CMRs not associated with a non-preferred SSB index.

[0226] For the purpose of setting the above Set A / B beam set, a specific reportConfig or / and a specific CMR set can be set in advance by the base station to the terminal.

[0227] In an additional embodiment, the terminal may report to the base station a preferred (or / and non-preferred) combination of Set A or / and Set B of i and ii set by the base station.

[0228] Additionally, the base station can configure multiple cell / site / area / zone-specific combinations of Set A and / or Set B for specific terminals. Group-common DCI can be utilized as a signaling method to indicate which of these combinations to utilize. The group-common DCI has the advantage of reducing signaling overhead and delay. Specifically, when the base station recognizes / confirms terminals located in a specific cell / site / area / zone, a specific Set A / B combination can be indicated to the terminals in a broadcast format based on the group-common DCI. This can reduce signaling overhead and delay.

[0229] [Base station operation]

[0230] The base station may transmit to the terminal settings for training / retraining / inference / monitoring of the UE-side AI / ML model. The settings may include information regarding the following i) and / or ii).

[0231] i) (cell / site / area / zone-common) A combination of multiple Sets A or / and Set B that have a common cell / site / area / zone.

[0232] ii) (cell / site / area / zone-specific) A combination of multiple Sets A or / and Set B specific to a cell / site / area / zone.

[0233] The base station can receive a preferred SSB index (or / and a non-preferred SSB index) from the terminal. After a certain period of time from the reception or after transmitting a related confirm message, the base station can recognize that the terminal is performing beam prediction using the UE-side AI / ML model.

[0234] Specifically, the base station may recognize that the UE performs measurement and / or beam prediction operations based on i) a combination of Set A and / or Set B associated with (UE-specific) CMRs associated with a preferred SSB index (or / and not associated with a non-preferred SSB index) and / or ii) a combination of Set A and / or Set B associated with (UE-specific) CMRs not associated with a non-preferred SSB index. For example, the base station may assume that the above-described measurement and / or beam prediction operations have been performed when performing operations related to a UE-side AI / ML model.

[0235] For this process, the base station can configure / activate the DL RS corresponding to the Set A / B combination preferred by the terminal (after reporting the terminal's preferred SSB index). The base station can set a specific reportConfig and / or a specific CMR set to the terminal in advance for the purpose of setting the Set A / B beam set.

[0236] In an additional embodiment, after receiving a report from the terminal about a preferred (or / and non-preferred) combination among the Set A and / or Set B combinations set as i, ii above, the base station may recognize that the terminal performs a beam prediction operation using the UE side AI / ML model for the preferred combination after a certain period of time or after transmitting a related confirm message.

[0237] Effect of Example 4) This example is a rule / regulation for the base station / terminal to mutually understand Set A or / and Set B used for beam prediction of the terminal AI / ML model, and has the advantage that the base station and the terminal can have a common understanding through SSB index reporting. More progressively, if the base station and the terminal infer the same AI / ML model ID or AI / ML model functionality, the base station and the terminal can produce the same output data by utilizing the same Set A or / and Set B combination. Therefore, there may be an effect in terms of delay reduction in that the base station and the terminal can apply the output data to subsequent uplink / downlink transmissions without having to share the output data (e.g., predicted beam ID, etc.) produced by each AI / ML model.

[0238] Example 5)

[0239] [Terminal operation]

[0240] A terminal may report a preferred SSB index (or / and a non-preferred SSB index). (After a certain period of time from the report or after receiving a confirmation message from a base station) the terminal may perform a positioning measurement report for a DL-PRS associated with the preferred SSB index and / or a DL-PRS not associated with the non-preferred SSB index. For example, a DL-PRS associated with a preferred SSB index may mean a DL-PRS that uses the preferred SSB index as a QCL top source. For example, a DL-PRS not associated with a non-preferred SSB index may mean a DL-PRS that uses an SSB index other than the non-preferred SSB index as a QCL top source.

[0241] More specifically, when a terminal reports a preferred SSB index (or / and a non-preferred SSB index), a threshold may be set by the base station to determine whether the terminal prefers (or / and dislikes) the SSB index. For example, the threshold may be related to SSB reception sensitivity.

[0242] (Effect of Example 5) In the existing positioning-related terminal measurement and report operation, the NW can configure DL PRS resources to the terminal based on the recommendation of the Location Management Function (LMF). The terminal may not be able to measure all of the configured DL PRS resources. In other words, only a portion of the configured DL PRS resources can be measured by the terminal. The terminal is standardized to perform a measurement report (using PUSCH transmission) only for measurable PRS resources. In Example 5, there is an advantage in that the NW can recognize in advance the DL PRS on which the terminal will perform a measurement report. The NW can predict in advance the payload size including the contents of the positioning-related measurement report, which allows the base station to allocate uplink resources to the terminal's measurement report without wasting resources. In addition, according to the report of Example 5, the LMF can recommend a DL PRS to the NW based on the reported preferred SSB index. Accordingly, unnecessary PRS configuration / transmission is not performed by the NW, resulting in a power saving effect in terms of the NES.

[0243] For example, the preferred / dispreferred SSB index report of Proposal 1 above may include one SSB index or multiple SSB indexes.

[0244] For example, the preferred / non-preferred DL RS report of Proposal 1 can be transmitted based on UCI such as PUCCH, PUSCH, etc. For example, the preferred / non-preferred DL RS report of Proposal 1 can be reported through MAC CE during PUSCH transmission. For example, the UE reporting of Proposal 1 can be performed in an event-triggered manner. Specifically, the UE reporting of Proposal 1 can be performed based on specific resources (e.g., SR-PUCCH, SPS PUCCH / PUSCH, PRACH) set by the base station when a specific condition related to an event is met.

[0245] The above embodiments may be operated by a combination of specific embodiments.

[0246] An example of a terminal (or base station) operation based on at least one of the embodiments described above (e.g., at least one of the embodiments of Proposal 1) is as follows.

[0247] 1) The terminal (base station) receives (transmits) settings related to preferred / non-preferred DL RS reports.

[0248] The above settings may include signaling medium, payload, etc. for preferred / non-preferred DL / RS reporting of the terminal.

[0249] 2) The terminal (base station) receives (transmits) a message scheduling transmission of the preferred / non-preferred DL RS report.

[0250] 3) The terminal (base station) transmits (receives) a preferred / non-preferred DL RS report based on the above message.

[0251] Preferred / non-preferred DL / RS reporting can be performed by UE-triggered operations (e.g., event-triggered operations). In this case, operation 2) above can be omitted.

[0252] The above uplink transmission may be based on at least one of embodiments 1 to 5 of the above proposal 1.

[0253] 4) The terminal (base station) performs the promised / contracted operation based on at least one of embodiments 1 to 5 of proposal 1.

[0254] The above terminal / base station operations are only an example, and each operation (or step) is not necessarily required, and the beam reporting operation of the terminal according to the above-described embodiments may be omitted or added depending on the terminal / base station implementation method.

[0255] In terms of implementation, the operations of the base station / terminal according to the embodiments described above (e.g., operations based on at least one of embodiments 1 to 5 of proposal 1) can be processed by the device of FIG. 5 (e.g., the processor (110, 210) of FIG. 5).

[0256] In addition, the operations of the base station / terminal according to the above-described embodiment (e.g., operations based on at least one of Embodiments 1 to 5 of Proposal 1) may be stored in a memory (e.g., 140, 240 of FIG. 5) in the form of commands / programs (e.g., instructions, executable codes) for driving at least one processor (e.g., 110, 210 of FIG. 5).

[0257] The embodiments described below are specifically described with reference to FIGS. 3 and 4 in terms of the operation of the terminal and base station. The methods described below are distinguished for convenience of explanation, and it is understood that some components of one method may be substituted for or combined with some components of another method.

[0258] FIG. 3 is a flowchart illustrating a method according to one embodiment of the present specification.

[0259] Referring to FIG. 3, a method according to one embodiment of the present specification includes a step of receiving configuration information (S310) and a step of reporting information related to at least one DL RS (S320).

[0260] In S310, the terminal receives configuration information from the base station.

[0261] For example, the configuration information may be received based on higher layer signaling (e.g., RRC signaling).

[0262] For example, the configuration information may include information related to a CSI report. A report quantity may be set based on the configuration information. The report quantity may be related to information reported by the terminal. For example, the report quantity may be set to indicate at least one of i) a Reference Signal (RS) index (e.g., SSB Resource Indicator (SSBRI) and / or CSI-RS Resource Indicator (CRI), ii) Reference Signal Received Power (RSRP), iii) a Channel Quality Indicator (CQI), and / or iv) a Precoding Matrix Indicator (PMI).

[0263] For example, the configuration information may include information based on at least one of embodiments 1 to 5 of proposal 1. The configuration information may include configurations related to measurement and / or reporting. The configurations may include configurations related to CSI. As a specific example, the configuration information (e.g., CSI-MeasConfig) may include information on one or more resource configurations (e.g., csi-ResourceConfigToAddModList) and / or information on one or more report configurations (e.g., csi-ReportConfigToAddModList).

[0264] Each CSI resource configuration (e.g., CSI-ResourceConfig) may include information about RS resources used for measurements. More specifically, each CSI resource configuration may include a list of references (e.g., NZP-CSI-RS-ResourceSetIds or CSI-SSB-ResourceSetIds) to RS resources used for measurements.

[0265] Each CSI reporting configuration (e.g., CSI-ReportConfig) may include a list of one or more sub-configurations (e.g., csi-ReportSubConfigToAddModList). The one or more sub-configurations may be based on the description of the sub-configuration described above.

[0266] In S320, the terminal reports information related to at least one downlink reference signal (DL RS) to the base station. The embodiments of Proposal 1 are described in detail below.

[0267] In one embodiment, one or more of the settings may be released or deactivated based on the at least one DL RS. This embodiment may be based on Embodiment 1 of Proposal 1. The at least one DL RS may include i) a non-preferred DL RS and / or ii) a preferred DL RS. In this embodiment, RS transmission / reception, terminal measurement, and / or terminal reporting based on the one or more settings may not be performed. Accordingly, terminal / base station power consumption may be reduced. Hereinafter, embodiments of Proposal 1 are described by dividing them into non-preferred DL RS and preferred DL RS. However, this is for convenience of explanation and does not mean that the application scope of the embodiments of Proposal 1 is limited to any one type of DL RS (preferred DL RS or non-preferred DL RS). Embodiments of Proposal 1 may also be applied even when preferred DL RS and non-preferred DL RS are reported.

[0268] In one embodiment, the at least one DL RS may include non-preferred DL RS(s).

[0269] For example, the one or more settings may include a setting based on the non-preferred DL RS. This embodiment may be based on Embodiment 1 of Proposal 1.

[0270] For example, sets related to beam prediction can be determined based on DL RSs other than the non-preferred DL RSs. This embodiment can be based on embodiment 4 of proposal 1.

[0271] For example, positioning measurement reporting may be performed based on a Positioning Reference Signal (PRS) associated with a DL RS other than the non-preferred DL RS. This embodiment may be based on embodiment 5 of proposal 1.

[0272] In one embodiment, the at least one DL RS may include preferred DL RS(s).

[0273] For example, the one or more settings may include settings other than those based on the preferred DL RS among the settings. This embodiment may be based on Embodiment 1 of Proposal 1.

[0274] For example, the information may relate to a request for a reduction in the transmit power of the preferred DL RS. This embodiment may be based on embodiment 2 of proposal 1.

[0275] For example, information related to a model may be set based on the preferred DL RS. This embodiment may be based on embodiment 3 of proposal 1. The model may include i) a UE-sided model and / or ii) a network-sided model. As a specific example, the information may include i) a plurality of DL RSs and ii) a coefficient for each DL RS among the plurality of DL RSs. The information related to the model may be related to a DL RS based on a linear combination of each DL RS among the plurality of DL RSs and the coefficients. As a specific example, based on the information related to the model, data collection for the model and / or performance monitoring of the model may be performed. The method may further include a step of receiving the information related to the model. Specifically, the UE receives the information related to the model from a base station.

[0276] For example, sets related to beam prediction can be determined based on the preferred DL RS. This embodiment can be based on embodiment 4 of proposal 1.

[0277] For example, positioning measurement reporting may be performed based on a Positioning Reference Signal (PRS) associated with the preferred DL RS. This embodiment may be based on embodiment 5 of proposal 1.

[0278] In one embodiment, the at least one DL RS may be based on at least one synchronization signal block (SSB). The synchronization signal block may be interpreted / replaced with a synchronization signal / physical broadcast channel block (SS / PBCH block). For example, information related to the at least one DL RS may include at least one SSB index.

[0279] In one embodiment, the one or more configurations may include one or more sub-configurations (e.g., one or more sub-configurations) related to one reporting configuration. For example, one or more sub-configurations related to each of the one or more reporting configurations may be released / deactivated based on the at least one DL RS. As a specific example, the one or more configurations may include one or more sub-configurations related to one of the one or more reporting configurations based on the configuration information. As a specific example, the one or more configurations may include one or more sub-configurations related to each of the one or more reporting configurations based on the configuration information.

[0280] This embodiment may be based on Embodiment 1 of Proposal 1. According to the existing operation defined for sub-configuration (e.g., periodic CSI reporting), reporting is performed by the terminal for all sub-configurations (e.g., sub-configurations contained in CSI-ReportConfig) based on the reporting configuration. According to this embodiment, since measurement and / or reporting are not performed for one or more of the sub-configurations, terminal power consumption may be reduced.

[0281] In one embodiment, at least one set of DL RSs among the sets set for the model may be indicated based on the above information. This embodiment may be based on embodiment 4 of proposal 1.

[0282] For example, the sets associated with the at least one DL RS may be determined from among the sets indicated based on group common downlink control information (DCI) among the established sets. As a specific example, the group common DCI may be based on a DCI format (e.g., DCI format 2_3, DCI format 2_6, DCI format 2_7, DCI format 2_9, or a new DCI format) associated with one or more UEs.

[0283] For example, the established sets may include i) sets common to the characteristics and / or ii) sets specific to each of the characteristics. The characteristics may be based on at least one of a cell, a site, an area, and / or a zone.

[0284] The operations based on S310 to S320 described above can be implemented by the device of FIG. 5. For example, referring to FIG. 5, the terminal (200) can control one or more transceivers (230) and / or one or more memories (240) to perform operations based on S310 to S320.

[0285] The embodiments described below are specifically described in terms of base station operation.

[0286] S410 to S420 described below correspond to S310 to S320 described in FIG. 3. Considering the above correspondence, redundant descriptions are omitted. That is, the specific description of the base station operation described below may be replaced with the description / example of FIG. 3 corresponding to the operation.

[0287] FIG. 4 is a flowchart illustrating a method according to another embodiment of the present specification.

[0288] Referring to FIG. 4, a method according to another embodiment of the present specification includes a step of transmitting setup information (S410) and a step of receiving information related to at least one DL RS (S420).

[0289] In S410, the base station transmits configuration information to the terminal. The configuration information may include settings related to measurement and / or reporting.

[0290] In S420, the base station receives information related to at least one downlink reference signal (DL RS) from the terminal.

[0291] One or more of the above settings may be released or deactivated based on at least one DL RS.

[0292] The operations based on S410 to S420 described above can be implemented by the device of FIG. 5. For example, referring to FIG. 5, the base station (100) can control one or more transceivers (130) and / or one or more memories (140) to perform the operations based on S410 to S420.

[0293] The operations / terms based on the embodiments described above have been described assuming a 5G system. However, this is for convenience of explanation and is not intended to limit the scope of application of the technical problems and problem-solving means to be solved by this specification to a specific system. That is, the technical problems / technical issues / problems mentioned in this specification may equally exist in other systems (e.g., 6G systems). It is self-evident that the embodiments of this specification can be expanded and applied to solve problems equally existing in the other systems. Therefore, for the expanded application of the embodiments of this specification to other systems, the terms defined / described based on the 5G system may be replaced / changed with terms defined in the other systems (or generalized terms not specific to a system). For example, PRACH, PUSCH, PUCCH, or SRS may be replaced / changed with uplink signals (or uplink channels). For example, SSB, CSI-RS, PDSCH, and PDCCH may be replaced / changed with downlink signals (or downlink channels).

[0294] Hereinafter, a device to which an embodiment of the present specification can be applied (a device that implements a method / operation according to an embodiment of the present specification) is described with reference to FIG. 5.

[0295] FIG. 5 is a drawing showing the configuration of a first device and a second device according to an embodiment of the present specification.

[0296] The first device (100) may include a processor (110), an antenna unit (120), a transceiver (130), and a memory (140).

[0297] The processor (110) performs baseband-related signal processing and may include a higher layer processing unit (111) and a physical layer processing unit (115). The higher layer processing unit (111) may process operations of a MAC layer, an RRC layer, or higher layers. The physical layer processing unit (115) may process operations of a PHY layer. For example, when the first device (100) is a base station device in base station-terminal communication, the physical layer processing unit (115) may perform uplink reception signal processing, downlink transmission signal processing, etc. For example, when the first device (100) is a first terminal device in terminal-to-terminal communication, the physical layer processing unit (115) may perform downlink reception signal processing, uplink transmission signal processing, sidelink transmission signal processing, etc. In addition to performing baseband-related signal processing, the processor (110) may also control the overall operation of the first device (100).

[0298] The antenna unit (120) may include one or more physical antennas, and when it includes multiple antennas, it may support MIMO transmission and reception. The transceiver (130) may include an RF (Radio Frequency) transmitter and an RF receiver. The memory (140) may store information processed by the processor (110), and software, an operating system, applications, etc. related to the operation of the first device (100), and may also include components such as a buffer.

[0299] The processor (110) of the first device (100) may be configured to implement the operation of the base station in the base station-to-terminal communication (or the operation of the first terminal device in the terminal-to-terminal communication) in the embodiments described in the present disclosure.

[0300] The second device (200) may include a processor (210), an antenna unit (220), a transceiver (230), and a memory (240).

[0301] The processor (210) performs baseband-related signal processing and may include a higher layer processing unit (211) and a physical layer processing unit (215). The higher layer processing unit (211) may process operations of a MAC layer, an RRC layer, or higher layers. The physical layer processing unit (215) may process operations of a PHY layer. For example, when the second device (200) is a terminal device in base station-terminal communication, the physical layer processing unit (215) may perform downlink reception signal processing, uplink transmission signal processing, etc. For example, when the second device (200) is a second terminal device in terminal-to-terminal communication, the physical layer processing unit (215) may perform downlink reception signal processing, uplink transmission signal processing, sidelink reception signal processing, etc. In addition to performing baseband-related signal processing, the processor (210) may also control the overall operation of the second device (210).

[0302] The antenna unit (220) may include one or more physical antennas, and when it includes multiple antennas, it may support MIMO transmission and reception. The transceiver (230) may include an RF transmitter and an RF receiver. The memory (240) may store information processed by the processor (210), software, an operating system, applications, etc. related to the operation of the second device (200), and may also include components such as a buffer.

[0303] The processor (210) of the second device (200) may be configured to implement operations of the terminal in base station-to-terminal communication (or operations of the second terminal device in terminal-to-terminal communication) in the embodiments described in the present disclosure.

[0304] In the operation of the first device (100) and the second device (200), the same explanations given for the base station and the terminal (or the first terminal and the second terminal in the terminal-to-terminal communication) in the examples of the present disclosure may be applied, and redundant explanations are omitted.

[0305] Here, the wireless communication technology implemented in the device of the present disclosure may include LTE, NR, and 6G, as well as Narrowband Internet of Things (NB-IoT) for low-power communication. For example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology and may be implemented in standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-described names.

[0306] Additionally or alternatively, the wireless communication technology implemented in the device of the present disclosure may perform communication based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and may be called by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology may be implemented by at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the above-described names.

[0307] Additionally or alternatively, the wireless communication technology implemented in the device of the present disclosure may include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN), which take low-power communication into account, and is not limited to the above-described names. For example, ZigBee technology can create personal area networks (PANs) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and may be called by various names.

Claims

1. In the method, A step of receiving configuration information from a base station, wherein the configuration information includes configurations related to measurement and / or reporting; and A step of reporting information related to at least one downlink reference signal (DL RS) to the base station; including: A method characterized in that one or more of the settings are released or deactivated based on the at least one DL RS.

2. In paragraph 1, A method characterized in that the at least one DL RS comprises a non-preferred DL RS.

3. In paragraph 2, A method characterized in that said one or more settings include a setting based on said non-preferred DL RS.

4. In paragraph 2, A method characterized in that sets related to beam prediction are determined based on DL RSs other than the above non-preferred DL RSs.

5. In paragraph 2, A method characterized in that positioning measurement reporting is performed based on a positioning reference signal (PRS) associated with a DL RS other than the above non-preferred DL RS.

6. In paragraph 1, A method characterized in that the at least one DL RS comprises a preferred DL RS.

7. In paragraph 6, A method characterized in that the one or more settings include settings other than the settings based on the preferred DL RS among the settings.

8. In paragraph 6, A method characterized in that the above information is related to a request for reduction of transmit power of the preferred DL RS.

9. In paragraph 6, A method characterized in that information related to a model is set based on the above preferred DL RS.

10. In paragraph 9, The above information includes i) a plurality of DL RSs and ii) a coefficient for each DL RS among the plurality of DL RSs, A method characterized in that the information related to the model is related to a DL RS based on a linear combination of each DL RS among the plurality of DL RSs and the coefficients.

11. In paragraph 9, A method characterized in that data collection for the model and / or performance monitoring of the model are performed based on the information related to the model.

12. In paragraph 6, A method characterized in that sets related to beam prediction are determined based on the above preferred DL RS.

13. In paragraph 6, A method characterized in that positioning measurement reporting is performed based on a positioning reference signal (PRS) associated with the preferred DL RS.

14. In paragraph 1, A method characterized in that the at least one DL RS is based on at least one synchronization signal block (SSB).

15. In paragraph 1, A method characterized in that said one or more settings include one or more sub-settings related to one reporting setting.

16. In paragraph 1, A method characterized in that, based on the above information, sets related to at least one DL RS among the sets set for the model are indicated.

17. In paragraph 16, A method characterized in that the sets associated with the at least one DL RS are determined from among the sets indicated based on group common downlink control information (DCI) among the set sets.

18. In paragraph 16, A method characterized in that the above-described sets include i) sets common to the characteristics and / or ii) sets specific to each of the characteristics.

19. At the terminal, One or more transmitters and receivers; one or more processors; and One or more memories connected to said one or more processors and storing instructions, A terminal characterized in that the instructions, based on being executed by the one or more processors, cause the terminal to perform all steps of the method according to any one of claims 1 to 18.

20. In a device comprising one or more memories and one or more processors connected to the one or more memories, A device characterized in that said one or more memories store instructions that cause said device to perform all steps of a method according to any one of claims 1 to 18, based on being executed by said one or more processors.

21. In a non-transitory computer-readable storage medium storing instructions, A non-transitory computer-readable storage medium characterized in that the instructions executable by one or more processors cause a terminal to perform all steps of a method according to any one of claims 1 to 18.

22. In the method, A step of transmitting configuration information to a terminal, wherein the configuration information includes configurations related to measurement and / or reporting; and A step of receiving information related to at least one downlink reference signal (DL RS) from the terminal; including: A method characterized in that one or more of the settings are released or deactivated based on the at least one DL RS.

23. At the base station, One or more transmitters and receivers; one or more processors; and One or more memories connected to said one or more processors and storing instructions, A base station characterized in that the instructions, based on being executed by the one or more processors, cause the base station to perform all steps of the method according to claim 22.

Images