Method performed by terminal or network in wireless communication system, and apparatus therefor

Abstract

A terminal, according to one embodiment of the present disclosure, may: receive configuration information regarding activation or deactivation of second synchronization signal blocks (SSBs); receive a channel state information (CSI) reporting configuration; on the basis of the CSI reporting configuration, perform channel measurement on at least one SSB from among the periodically transmitted second SSBs or first SSBs; and transmit a CSI report on the basis of the channel measurement, wherein the CSI reporting configuration may include information on the at least one SSB for the channel measurement from among the first SSBs or the second SSBs.

Description

A method performed by a terminal or network in a wireless communication system and an apparatus for the same

[0001] The present disclosure relates to a wireless communication system, and more specifically, to a method and apparatus for performing wireless communication between terminals or networks in a wireless communication system.

[0002] The 5G mobile communication system is a successor technology to LTE (Long Term Evolution) and is a new clean-slate type of mobile communication system characterized by high performance, low latency, and high availability. In the case of 5G NR, all available spectrum resources can be utilized, ranging from low-frequency bands below 1 GHz to intermediate frequency bands between 1 GHz and 10 GHz, and high-frequency (millimeter wave) bands above 24 GHz. Based on the underlying technology of 5G mobile communication, 6G mobile communication systems are being developed.

[0003] In 5G NR mobile communication systems, a signal block containing an SS / PBCH (synchronization signal / physical broadcast channel) is referred to as an SSB, and within an SSB burst, multiple SSBs are transmitted through different beams. In the initial NR version, Rel. 15 NR, the SSB burst was defined as always-on, meaning transmission was always performed. However, in next-generation mobile communication systems such as NR Rel. 19 or 6G, SSBs provided on-demand according to network signaling / terminal requests may be introduced to save network energy (NES).

[0004] The technical problem to be solved by the present disclosure is to provide a method for efficiently performing a wireless signal transmission and reception process and an apparatus for such a method. According to one embodiment, a method for setting CSI reporting considering an SSB provided / activated in response to a network signaling / terminal request may be provided. Additionally, a method for determining CPU occupancy considering such an SSB may be provided. Furthermore, a method for determining a CPU / CSI timeline considering such an SSB may be provided.

[0005] In addition to the technical challenges described above, other technical challenges can be inferred from the description below.

[0006] A method performed by a terminal according to one aspect of the present disclosure comprises receiving setting information for the activation / deactivation of second SSBs (synchronization signal blocks); receiving a CSI (channel state information) reporting setting; performing a channel measurement for at least one of the first SSBs or the second SSBs that is periodically transmitted based on the CSI reporting setting; and transmitting a CSI report based on the channel measurement, wherein the CSI reporting setting may include information for the at least one of the first SSBs or the second SSBs for the channel measurement.

[0007] Based on the activation of the second SSB, the CPU (CSI processing unit) may begin to be occupied starting from the first symbol of the earliest SSB among the first SSBs and the second SSBs.

[0008] Based on the deactivation of the second SSB, the CPU (CSI processing unit) may begin to be occupied starting from the first symbol of the earliest SSB among the first SSBs.

[0009] During the time interval in which the above CPU is occupied, the terminal may not expect the activation / deactivation state of the above second SSB to change.

[0010] Based on the activation of the second SSB, the channel measurement can be performed up to the latest SSB among the first SSBs and the second SSBs that is not later than the CSI reference resource.

[0011] Based on the deactivation of the second SSB, the channel measurement can be performed up to the most recent SSB among the first SSBs that is not later than the CSI reference resource.

[0012] The above CSI reporting settings may include one or more SSB resource lists. The one or more SSB resource lists may include at least one of a first SSB resource list linked only to the first SSBs or a second SSB resource list linked only to the second SSBs.

[0013] The above CSI reporting configuration may include a plurality of sub-configurations. Among the plurality of sub-configurations, the first sub-configuration may be linked to the first SSB resource list, and the second sub-configuration may be linked to the second SSB resource list.

[0014] The above CSI reporting settings may include a list of SSB resources linked to the first SSBs and the second SSBs.

[0015] The above second SSBs may be OD (on-demand) SSBs.

[0016] The above second SSBs can be enabled or disabled based on at least one of RRC (radio resource control) signaling or MAC (medium access control) CE (control element).

[0017] The above channel measurement may be an L1 (layer 1) measurement related to SSB RSRP (reference signal received power) or SSB SINR (signal to interference and noise ratio).

[0018] The above CSI report can be transmitted via PUCCH (physical uplink control channel) or PUSCH (physical uplink shared channel).

[0019] According to another aspect of the present disclosure, a computer-readable non-transitory recording medium may be provided that records a program for performing the method described above.

[0020] An apparatus according to another aspect of the present disclosure comprises: at least one processor; and at least one memory configured to store instructions that cause the at least one processor to perform operations by being executed by the at least one processor, wherein the operations of the processor include receiving setting information for the activation / deactivation of second SSBs (synchronization signal blocks); receiving a CSI (channel state information) reporting setting; performing channel measurements on at least one of the first SSBs or the second SSBs that are periodically transmitted based on the CSI reporting setting; and transmitting a CSI report based on the channel measurements, wherein the CSI reporting setting may include information on the at least one SSB among the first SSBs or the second SSBs for the channel measurements.

[0021] The above device may further include a transmitter and receiver.

[0022] The above device may be a terminal.

[0023] The above device may be a processing device configured to control a terminal.

[0024] According to another aspect of the present disclosure, a method performed by a base station comprises: transmitting configuration information for the activation / deactivation of second SSBs (synchronization signal blocks); transmitting a CSI (channel state information) reporting configuration to a terminal; and receiving from the terminal a CSI report related to channel measurement for at least one of the first SSBs or the second SSBs that is transmitted periodically, wherein the CSI reporting configuration may include information for the at least one of the first SSBs or the second SSBs for channel measurement.

[0025] A base station according to another aspect of the present disclosure comprises: at least one processor; and at least one memory configured to store instructions that are executed by the at least one processor to cause the at least one processor to perform operations, wherein the operations of the processor include transmitting configuration information for the activation / deactivation of second SSBs (synchronization signal blocks); transmitting a CSI (channel state information) reporting configuration to a terminal; and receiving from the terminal a CSI report related to channel measurement for at least one of the first SSBs or the second SSBs that is transmitted periodically, and the CSI reporting configuration may include information for the at least one SSB among the first SSBs or the second SSBs for channel measurement.

[0026] According to the present disclosure, signal transmission and reception can be performed efficiently in a wireless communication system. According to one embodiment, the problem of ambiguity arising from the introduction of such an SSB can be resolved by providing a method for setting CSI reporting considering an SSB provided / activated according to a network signaling / terminal request, a method for determining CPU occupancy, and / or a method for determining a CPU / CSI timeline. Furthermore, according to one embodiment, unnecessary CPU occupancy can be minimized by calculating CPU occupancy differently depending on whether the corresponding SSB is activated.

[0027] In addition to the technical effects described above, other technical effects can be inferred from the description below.

[0028] FIG. 1 illustrates an exemplary flexible network topology to which some of the examples of the present specification may be applied.

[0029] FIG. 2 illustrates an example of a communication system applicable to the present disclosure.

[0030] FIG. 3 illustrates an example of a wireless device that can be applied to the present disclosure.

[0031] FIG. 4 illustrates a communication procedure between a first node (e.g., a terminal) and a second node (e.g., a base station) applicable to the present disclosure.

[0032] Figure 5 illustrates a general functional architecture for an AI / ML model.

[0033] FIG. 6 illustrates a communication procedure between a first node (e.g., terminal) and a second node (e.g., base station) to which an AI / ML model is applied.

[0034] FIG. 7 shows an electromagnetic spectrum according to one embodiment of the present disclosure.

[0035] FIG. 8 illustrates an example of a procedure for transmitting system information for THz communication to which the present disclosure applies.

[0036] FIG. 9 illustrates a beam management procedure applicable to the present disclosure.

[0037] FIG. 10 shows an example of a sensing operation according to one embodiment of the present disclosure.

[0038] FIG. 11 illustrates a time / frequency resource for a sensing operation according to one embodiment of the present specification.

[0039] FIG. 12 illustrates a procedure related to a sensing operation according to one embodiment of the present specification.

[0040] Figure 13 illustrates an example of the operation procedure of a base station supporting NES technology.

[0041] Figure 14 illustrates an example of a procedure for cell DTX / DRX operation.

[0042] Figure 15 illustrates an example of a procedure for CA operation using an SSB-less SCell.

[0043] Figure 16 illustrates an example of a Conditional Handover (CHO) procedure.

[0044] Figure 17 illustrates an example of on-demand SSB transmission.

[0045] Figure 18 is a diagram illustrating the CPU occupancy period according to the existing NR standard.

[0046] FIG. 19 is a diagram illustrating the operation of a terminal and a base station according to one embodiment.

[0047] FIG. 20 illustrates the flow of a method performed by a terminal according to one embodiment.

[0048] FIG. 21 illustrates the flow of a method performed by a base station according to one embodiment.

[0049] In this specification, "A or B" may mean "only A," "only B," or "both A and B." Alternatively, in this specification, "A or B" may be interpreted as "A and / or B." For example, in this specification, "A, B or C" may mean "only A," "only B," "only C," or "any combination of A, B and C."

[0050] A slash ( / ) or a comma used in this specification may mean "and / or." For example, "A / B" may mean "A and / or B." Accordingly, "A / B" may mean "only A," "only B," or "both A and B." For example, "A, B, C" may mean "A, B or C."

[0051] In this specification, "at least one of A and B" may mean "only A," "only B," or "both A and B." Additionally, in this specification, the expressions "at least one of A or B" or "at least one of A and / or B" may be interpreted as synonymous with "at least one of A and B."

[0052] Additionally, in this specification, "at least one of A, B and C" may mean "only A," "only B," "only C," or "any combination of A, B and C." Also, "at least one of A, B or C" or "at least one of A, B and / or C" may mean "at least one of A, B and C."

[0053] Additionally, parentheses used in this specification may mean "for example." Specifically, when indicated as "control information (ABC)," "ABC" may be described as an example of "control information." For example, "control information" may include DEF as another example. In other words, "control information" in this specification is not limited to "ABC," and "ABC" may be described as an example of "control information." Also, when indicated as "control information (i.e., ABC)," "ABC" may be described as an example of "control information."

[0054] In addition, terms such as "first," "second," etc. in this specification are used solely for the purpose of distinguishing one component from another and are not used to limit the components, nor are they used to limit the order or importance of the components unless specifically limited. Accordingly, a first component in one embodiment of this specification may be referred to as a second component in another embodiment, and likewise, a second component in one embodiment may be referred to as a first component in another embodiment.

[0055] In the following explanation, 'when, if, in case of' can be replaced with 'based on'.

[0056] Technical features described individually within a single drawing in this specification may be implemented individually or simultaneously.

[0057] In this specification, a terminal is a user-side device (user equipment, UE) or a consumer-side device, and may also be referred to as a first node that receives / transmits signals from / to a base station / second node / IAB node / Transmission-Reception Point (TRP). A terminal may correspond to a physical node or a logical node. A terminal may correspond to a user-side endpoint or an intermediate point between other endpoints. In communication between two points not limited to endpoints (including one-to-one / many-to-one / one-to-many / many-to-many communication), a terminal may correspond to a served node. A terminal may be a fixed-location node or a non-fixed-location (or mobile) node.

[0058] In this specification, a Base Station (BS) is a device on the network side and may also be referred to as a second node / IAB node / x-NodeB (x-NodeB, where x may be an abbreviation related to Radio Access Technology (RAT)) / Transmission-Reception Point (TRP). A Base Station may correspond to a physical node or a logical node. A Base Station may correspond to an endpoint on the network side or an intermediate point between other endpoints. In communication between two points not limited to endpoints (including one-to-one / many-to-one / one-to-many / many-to-many communication), a Base Station may correspond to a serving node. A Base Station may be a node with a fixed location or a node with an indefinite location.

[0059] In this specification, higher layer parameters may be set for the terminal, pre-set, or pre-defined. For example, a base station may transmit higher layer parameters to the terminal. For example, the terminal may transmit parameters such as capability to the base station as higher layer parameters. For example, higher layer parameters may be transmitted via RRC (radio resource control) signaling or MAC (medium access control) signaling.

[0060] In this specification, information / state / parameters being "configured" or "pre-configured" may be interpreted as the information / state / parameters being provided / pre-provided to the terminal through pre-defined signaling (e.g., SIB, MAC, RRC) from the base station. In this specification, information / state / parameters being "defined" or "pre-defined" may be interpreted as being known or stored in advance by the base station and the terminal without signaling between the base station and the terminal.

[0061] The technology described in this specification can be used in various wireless communication systems such as CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), and SC-FDMA (single carrier frequency division multiple access). CDMA can be implemented with wireless technologies such as UTRA (universal terrestrial radio access) or CDMA2000. TDMA can be implemented with wireless technologies such as GSM (global system for mobile communications) / GPRS (general packet radio service) / EDGE (enhanced data rates for GSM evolution). OFDMA can be implemented with wireless technologies such as IEEE (institute of electrical and electronics engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, E-UTRA (evolved UTRA), LTE (long term evolution), and 5G NR.

[0062] The technology described in this specification can be implemented as 6G wireless technology and applied to various 6G systems. For example, 6G systems may have key factors such as eMBB (enhanced mobile broadband), URLLC (ultra-reliable low latency communications), mMTC (massive machine-type communication), AI (artificial intelligence) integrated communication, tactile internet, high throughput, high network capacity, high energy efficiency, low backhaul and access network congestion, and enhanced data security.

[0063] <Symbols, Abbreviations, Terms>

[0064] - PDCCH: Physical Downlink Control CHannel

[0065] - DCI: Downlink Control Information

[0066] - PDSCH: Physical Downlink Shared CHannel

[0067] - PUSCH: Physical Uplink Shared CHannel

[0068] - CSI: Channel state information

[0069] - RRM: Radio resource management

[0070] - SCS: Sub-carrier spacing

[0071] - RLM: Radio link monitoring

[0072] - DCI: Downlink Control Information

[0073] - CAP: Channel Access Procedure

[0074] - Ucell: Unlicensed cell

[0075] - TBS: Transport Block Size

[0076] - TDRA: Time Domain Resource Allocation

[0077] - SLIV: Starting and Length Indicator Value (An indicator value for the starting symbol index and number of symbols within a slot of a PDSCH and / or PUSCH; it can be set as a component of an entry constituting the TDRA field within the PDCCH scheduling the said PDSCH and / or PUSCH.)

[0078] - BWP: Bandwidth Part (It can consist of consecutive resource blocks (RBs) on the frequency axis and correspond to a single numerology (e.g., sub-carrier spacing, CP length, slot / mini-slot duration). Additionally, multiple BWPs can be configured on a single carrier (the number of BWPs per carrier may also be limited), but the number of activated BWPs per carrier may be limited to a fraction of them (e.g., 1).)

[0079] - CORESET: Control Resource Set (Refers to the time and frequency resource range where PDCCH can be transmitted, and the number of CORESETs per BWP may be limited.)

[0080] - REG: Resource element group

[0081] - SFI: Slot Format Indicator (An indicator that indicates the symbol level DL / UL direction within a specific slot(s), transmitted via the group common PDCCH.)

[0082] - COT: Channel occupancy time

[0083] - SPS: Semi-persistent scheduling

[0084] - QCL: Quasi-Co-Location (The QCL relationship between two reference signals implies that QCL parameters, such as Doppler shift, Doppler spread, average delay, delay spread, and spatial Rx parameters obtained from one reference signal, can be applied to another reference signal (or the antenna port(s) of the corresponding RS). In NR systems, four QCL types are defined as follows: 'typeA': {Doppler shift, Doppler spread, average delay, delay spread}, 'typeB': {Doppler shift, Doppler spread}, 'typeC': {Doppler shift, average delay}, 'typeD': {Spatial Rx parameter}. For a certain DL RS antenna port(s), the first DL RS is set as a reference for QCL type X (X=A, B, C, or D), and additionally, the second DL RS is set as a reference for QCL type Y (Y=A, B, C, or D but X≠Y). It can be set to.)

[0085] - TCI: Transmission Configuration Indication (A single TCI state contains QCL relationships between one or more DL RSs, such as DM-RS ports of the PDSCH, the DM-RS port of PDCCH, or the CSI-RS port(s) of a CSI-RS resource. For 'Transmission Configuration Indication' among the fields within the DCI that schedule PDSCH, the TCI state index corresponding to each code point constituting the field is activated by MAC CE, and the TCI state setting for each TCI state index is configured via RRC signaling. In Rel-16 NR systems, the corresponding TCI state is configured between DL RSs, but configuration between DL RSs and UL RSs, or between UL RSs and UL RSs, may be permitted in future releases. Examples of UL RSs include SRS, PUSCH DM-RS, and PUCCH DM-RS.)

[0086] - SRI: SRS resource indicator (Indicates one of the SRS resource index values ​​set in the 'SRS resource indicator' among the fields within the DCI that schedule PUSCH. When transmitting a PUSCH, the terminal can transmit the PUSCH by utilizing the same spatial domain transmission filter used for transmitting and receiving the reference signal associated with the corresponding SRS resource. In this case, the reference RS is set by RRC signaling via the SRS-SpatialRelationInfo parameter for each SRS resource, and the SS / PBCH block, CSI-RS, or SRS can be set as the reference RS.)

[0087] - TRP: Transmission and Reception Point

[0088] - TAG: Timing advance group

[0089] - AmIoT: Ambient Internet of Things

[0090] - CW: Carrier Wave

[0091] - BSC: Backscattering

[0092] - BSS: Backscattered signal

[0093] - SIC: Self-Interference Cancellation

[0094] - RFID: Radio Frequency Identifier

[0095] - IN: Intermediate Node

[0096] FIG. 1 illustrates an exemplary flexible network topology to which some of the examples of the present specification may be applied.

[0097] To compensate for incomplete areas of network coverage, a network topology in which the Split Radio Access Network (RAN) is configured more flexibly and resiliently may be considered. To this end, various nodes such as IAB nodes, relays, and RF repeaters, as exemplified in Fig. 1, may be applied, and NTN may be integrated. For example, an IAB node may correspond to a node that provides wireless backhaul. For example, a relay may refer to any intermediate point, and in the case of a sidelink relay where a terminal functions as a relay, it may collectively refer to a terminal-to-network (U2N) relay and a terminal-to-terminal (U2U) relay. For example, an RF repeater may correspond to a node that performs simple signal amplification and forwarding functions, and in the case of a network-controlled repeater, it may adjust transmit / receive settings based on information provided by the network as well as signal amplification and forwarding. For example, an NTN node may correspond to a satellite or aircraft that provides NTN coverage that is difficult for a terrestrial network to provide. In addition to these examples, various intermediate points can be introduced to improve network topology.

[0098] Referring to FIG. 1, a split RAN can support the division of a base station into one centralized unit (CU) and one or more distributed units (DU). The CU and DU may correspond to logical units. The CU may be further divided into a control plane (CP) portion and one or more user plane (UP) portions. Since a failure in the CU-CP affects not only the CU-UP but also the DU, various intermediate points may be introduced to compensate for this.

[0099] An intermediate point may correspond to a terminal or a base station depending on its relative relationship with other nodes. For example, an IAB node may include a mobile-termination (MT) portion and a DU. The MT can connect the IAB node to a donor node. The DU of the IAB node may serve other terminals or connect to other IAB nodes to provide multi-hop wireless backhaul to terminals. In other words, an IAB node may correspond to a base station in its relative relationship with user-side nodes and to a terminal in its relative relationship with network-side nodes.

[0100] In some examples of this specification, the description of a terminal may apply equally to an intermediate point corresponding to a terminal in relation to a network-side endpoint as well as to a user-side endpoint. Similarly, in some examples of this specification, the description of a base station may apply equally to an intermediate point corresponding to a base station in relation to a user-side endpoint as well as to a network-side endpoint. However, in most cases where there is no additional description of the operation of three or more entities, the communication entities in this specification are briefly described by the term terminal and / or base station (or first node and / or second node), wherein the term terminal and / or base station (or first node and / or second node) is interpreted to include or replace any endpoint or any intermediate point in relation to other nodes.

[0101] That is, for the sake of brevity of description in some examples of this specification, the subject of the operation may be referred to as a base station and / or terminal (or a first node and / or a second node). Additionally, the term base station and / or terminal (or a first node and / or a second node) may be interpreted or substituted as in the following examples: for example, the base station (or the first node) and the terminal (or the second node) may correspond to a first endpoint and a second endpoint, respectively; may correspond to an endpoint and an intermediate point, respectively; may correspond to an intermediate point and an endpoint, respectively; or may correspond to a first intermediate point and a second intermediate point, respectively.

[0102] In this specification, there may be no intermediate points between the base station and the terminal, or there may be one or more. If intermediate points exist, the intermediate points may correspond to IAB nodes, relays, RF repeaters, NTN (non-terrestrial network) nodes, or nodes supporting other functions. The intermediate points may be nodes with a fixed location or nodes with an indefinite location.

[0103] FIG. 2 illustrates a communication system applicable to the present disclosure.

[0104] The communication system (100) of FIG. 2 includes a wireless device (110), a network device (120), and a network (130). Here, the wireless device (110) refers to a device that performs communication using wireless access technology (e.g., LTE, LTE-A, LTE-A pro, NR, 5G, 5G-A, 6G) and may be referred to as a communication / wireless / 5G / 6G device. Although not limited thereto, the wireless device (110) may include a robot (110a), a vehicle (110b-1, 110b-2), an XR (extended reality) device (110c), a hand-held device (110d), a home appliance (110e), an IoT (Internet of Thing) device (110f), and an AI (artificial intelligence) device / server (110g). For example, the vehicle may include a vehicle equipped with wireless communication capabilities, an autonomous vehicle, a vehicle capable of performing inter-vehicle communication, etc. Here, the vehicle (110b-1, 110b-2) may include an unmanned aerial vehicle (UAV) (e.g., a drone). The XR device (110c) includes an augmented reality (AR) / virtual reality (VR) / mixed reality (MR) device and may be implemented in the form of a head-mounted device (HMD), a head-up display (HUD) equipped in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance, digital signage, a vehicle, a robot, etc. The portable device (110d) may include a smartphone, a smartpad, a wearable device (e.g., a smartwatch, smart glasses), a computer (e.g., a laptop, etc.). The home appliance (110e) may include a TV, a refrigerator, a washing machine, etc. The IoT device (110f) may include a sensor, a smart meter, etc. The wireless device (110) may correspond to a terminal (or first node) or an intermediate point.The network device (120) may correspond to a base station (or a second node) or another intermediate point. For example, the network device (120) may also be implemented as a wireless device (110), and a specific wireless device (120a) may operate as a network device (120) to another wireless device (110).

[0105] Wireless devices (110a to 110f) can be connected to a network (130) through a network device (120). AI technology may be applied to the wireless devices (110a to 110f), and the wireless devices (110a to 110f) can be connected to an AI server (110g) through the network (130). The network (130) can be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, or a 6G network. The wireless devices (110a to 110f) may communicate with each other through the network device (120) / network (130), but may also communicate directly (e.g., sidelink communication) without going through the network device (120) / network (130). For example, vehicles (110b-1, 110b-2) can communicate directly (e.g., V2V (vehicle to vehicle) / V2X (vehicle to everything) communication). Also, an IoT device (110f) (e.g., a sensor) can communicate directly with another IoT device (e.g., a sensor) or other wireless devices (110a to 110f).

[0106] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (110a to 110f) / network devices (120) and between network devices (120). Here, wireless communication / connection can be established through various wireless access technologies such as uplink / downlink communication (150a), sidelink communication (150b) (or D2D communication), and communication between network devices (150c) (e.g., relay, IAB (integrated access backhaul)). Through wireless communication / connection (150a, 150b, 150c), wireless devices and network devices / wireless devices, and network devices and network devices can transmit / receive wireless signals to / from each other. For example, wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, based on the various descriptions of the present disclosure, at least some of the following may be performed: a process for setting various configuration information for transmitting / receiving wireless signals, a process for various signal processing (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), a resource allocation process, etc.

[0107] FIG. 3 illustrates an example of a wireless device that can be applied to the present disclosure.

[0108] Referring to FIG. 3, the wireless device (200) can transmit and receive wireless signals through various wireless access technologies (e.g., LTE, LTE-A, LTE-A pro, NR, 5G, 5G-A, 6G). The wireless device (200) includes at least one processor (202) and at least one memory (204), and may additionally include at least one transceiver (206) and / or at least one antenna (208).

[0109] The processor (202) controls the memory (204) and / or the transceiver (206) and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or sequences of operation disclosed in this document. For example, the processor (202) may process information within the memory (204) to generate a first information / signal and then transmit a wireless signal containing the first information / signal through the transceiver (206). Additionally, the processor (202) may receive a wireless signal containing a second information / signal through the transceiver (206) and then store information obtained from the signal processing of the second information / signal in the memory (204). The memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, memory (204) may store software code containing instructions for performing some or all of the processes controlled by the processor (202) or for performing the descriptions, functions, procedures, proposals, methods, and / or sequences of operations disclosed in this document. Here, the processor (202) and memory (204) may be part of a communication modem / circuit / chip designed to implement wireless communication technology. A transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals through at least one antenna (208). The transceiver (206) may include a transmitter and / or receiver. The transceiver (206) may be interchangeable with a radio frequency (RF) unit. In this disclosure, a wireless device may mean a communication modem / circuit / chip.

[0110] Hereinafter, hardware elements of the wireless device (200) will be described in more detail. Although not limited thereto, at least one protocol layer may be implemented by at least one processor (202). For example, at least one processor (202) may implement at least one layer (e.g., functional layers such as PHY (physical), MAC (media access control), RLC (radio link control), PDCP (packet data convergence protocol), RRC (radio resource control), and SDAP (service data adaptation protocol). At least one processor (202) may generate at least one PDU (Protocol Data Unit) and / or at least one SDU (service data unit) according to the descriptions, functions, procedures, proposals, methods and / or operation sequences disclosed in this document. At least one processor (202) may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods and / or operation sequences disclosed in this document. At least one processor (202) may generate a signal (e.g., baseband signal) including a PDU, SDU, message, control information, data, or information according to the functions, procedures, proposals, and / or methods disclosed in this document and provide it to at least one transceiver (206). At least one processor (202) may receive a signal (e.g., baseband signal) from at least one transceiver (206) and may obtain a PDU, SDU, message, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this document.

[0111] At least one processor (202) may be referred to as a controller, microcontroller, microprocessor, or microcomputer. At least one processor (202) may be implemented by hardware, firmware, software, or a combination thereof. For example, at least one application-specific integrated circuit (ASIC), at least one digital signal processor (DSP), at least one digital signal processing device (DSPD), at least one programmable logic device (PLD), or at least one field programmable gate array (FPGA) may be included in at least one processor (202). The descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this document may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. Firmware or software configured to perform the descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this document may be included in at least one processor (202) or stored in at least one memory (204) and driven by at least one processor (202). The descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed in this document may be implemented using firmware or software in the form of code, instructions, and / or sets of instructions.

[0112] At least one memory (204) may be connected to at least one processor (202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. At least one memory (204) may be composed of ROM (read-only memory), RAM (random access memory), EPROM (erasable programmable read-only memory), flash memory, hard drive, registers, cache memory, computer read storage media, and / or combinations thereof. At least one memory (204) may be located inside and / or outside of at least one processor (202). Additionally, at least one memory (204) may be connected to at least one processor (202) via various technologies, such as wired or wireless connections.

[0113] At least one transceiver (206) may transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or operation flowcharts, etc. of this document to at least one other device. At least one transceiver (206) may receive user data, control information, wireless signals / channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and / or operation flowcharts, etc. disclosed in this document from at least one other device. For example, at least one transceiver (206) may be connected to at least one processor (202) and may transmit and receive wireless signals. For example, at least one processor (202) may control at least one transceiver (206) to transmit user data, control information, or wireless signals to at least one other device. Additionally, at least one processor (202) may control at least one transceiver (206) to receive user data, control information, or wireless signals from at least one other device. Additionally, at least one transceiver (206) may be connected to at least one antenna (208), and at least one transceiver (206) may be configured to transmit and receive user data, control information, wireless signals / channels, etc., as described in the descriptions, functions, procedures, proposals, methods, and / or operation sequence diagrams disclosed in this document through at least one antenna (208). In this document, at least one antenna may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports). At least one transceiver (206) may convert the received wireless signals / channels, etc., from RF band signals to baseband signals in order to process the received user data, control information, wireless signals / channels, etc., using at least one processor (202). At least one transceiver (206) may convert the processed user data, control information, wireless signals / channels, etc., from baseband signals to RF band signals using at least one processor (202).To this end, at least one transceiver (206) may include an (analog) oscillator and / or filter.

[0114] The components of the wireless device described with reference to FIG. 3 may be referred to by other terms in terms of their function. For example, the processor (202) may be referred to as the control unit, the transceiver (206) as the communication unit, and the memory (204) as the storage unit. In some cases, the communication unit may be used to mean at least a part of the processor (202) and the transceiver (206).

[0115] The structure of the wireless device described with reference to FIG. 3 can be understood as the structure of at least part of various devices. For example, the structure of the wireless device illustrated in FIG. 3 may be at least part of the various devices described with reference to FIG. 2 (e.g., robot (110a), vehicle (110b-1, 110b-2), XR device (110c), portable device (110d), home appliance (110e), IoT device (110f), AI device / server (110g)). Furthermore, according to various embodiments, the device may include other components in addition to the components illustrated in FIG. 3.

[0116] For example, the device may be a portable device such as a smartphone, smartpad, wearable device (e.g., smart watch, smart glasses), or portable computer (e.g., laptop, etc.). In this case, the device may further include at least one of a power supply unit that supplies power and includes a wired / wireless charging circuit, a battery, etc., an interface unit that includes at least one port for connection with another device (e.g., audio input / output port, video input / output port), and an input / output unit for inputting and outputting video information / signals, audio information / signals, data, and / or information input by a user.

[0117] For example, the device may be a mobile device such as a mobile robot, vehicle, train, manned / unmanned aerial vehicle (AV), or ship. In this case, the device may further include at least one of a drive unit comprising at least one of an engine, motor, power train, wheel, brake, and steering device of the device; a power supply unit that supplies power and includes a wired / wireless charging circuit, battery, etc.; a sensor unit that senses state information, environmental information, and user information of the device or its surroundings; an autonomous driving unit that performs functions such as path maintenance, speed control, and destination setting; and a position measurement unit that acquires position information of the moving body through a GPS (global positioning system) and various sensors.

[0118] For example, the device may be an XR device such as an HMD, a HUD (head-up display) equipped in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance, digital signage, a vehicle, a robot, etc. In this case, the device may further include at least one of a power supply unit that supplies power and includes a wired / wireless charging circuit, a battery, etc., an input / output unit that acquires control information, data, etc. from the outside and outputs a generated XR object, and a sensor unit that senses state information, environment information, and user information of the device or the surroundings of the device.

[0119] For example, the device may be a robot that can be classified into industrial, medical, household, military, etc., depending on the purpose or field of use. In this case, the device may further include at least one of a sensor unit that senses state information, environmental information, and user information of the device or its surroundings, and a drive unit that performs various physical actions, such as moving robot joints.

[0120] For example, the device may be an AI device such as a TV, projector, smartphone, PC, laptop, digital broadcasting terminal, tablet PC, wearable device, set-top box (STB), radio, washing machine, refrigerator, digital signage, robot, vehicle, etc. In this case, the device may further include at least one of an input unit that acquires various types of data from the outside, an output unit that generates output related to sight, hearing, or touch, a sensor unit that senses state information, environmental information, and user information of the device or its surroundings, and a training unit that learns a model composed of an artificial neural network using training data.

[0121] The structure of the wireless device exemplified in FIG. 3 may be understood as part of a terminal (or first node), or part of an intermediate point, or part of a base station (or second node). If the device exemplified in FIG. 3 is a base station (or second node), the device may further include a wired transceiver for front haul and / or back haul communication. However, if the front haul and / or back haul communication is based on wireless communication, at least one transceiver (206) exemplified in FIG. 3 is used for front haul and / or back haul communication, and the wired transceiver may not be included.

[0122] FIG. 4 illustrates a communication procedure between a first node (e.g., a terminal) and a second node (e.g., a base station) applicable to the present disclosure.

[0123] The second node of FIG. 4 supports dynamic spectrum sharing (DSS) and can provide connectivity to both nodes where 6G technology is implemented and nodes where pre-6G wireless communication technology (e.g., 5G, 4G) is implemented. That is, the first node of FIG. 4 may have 6G technology implemented or pre-6G wireless communication technology (e.g., 5G, 4G) implemented. Additionally, the first node and / or the second node may support full duplex mode as well as non-overlapping full duplex mode.

[0124] In FIG. 4, for the sake of simplicity of explanation, the first node and the second node are assumed to be a terminal and a base station, respectively, and the operation of the terminal (110) and the base station (120) transmitting and / or receiving data, and the operation performed prior to this, are illustrated. However, the operation of FIG. 4 is not limited to the operation between the terminal and the base station, but can be interpreted as the operation between the first node and the second node. Additionally, FIG. 4 illustrates the operation of direct transmission and reception of wireless signals between the terminal (110) and the base station (120), but there may be one or more intermediate points between the terminal (110) and the base station (120), and wireless signals may be transmitted and received via one or more intermediate points.

[0125] Referring to FIG. 4, the terminal (110) and the base station (120) can perform synchronization (401). For example, the terminal (110) performs an initial cell search operation. Specifically, the terminal (110) can detect a synchronization signal for at least one base station connection transmitted from the base station (120) according to a predefined rule. Here, the synchronization signal may include a plurality of synchronization signals classified according to structure or use (e.g., a first synchronization signal (e.g., a primary synchronization signal), a second synchronization signal (e.g., a secondary synchronization signal), etc.). Through this, the terminal (110) can identify the boundary of the unit (e.g., frame, subframe, slot and / or symbol) constituting the wireless signal transmission of the base station (120) and obtain information about the base station (120) (e.g., cell identifier).

[0126] The terminal (110) can obtain system information transmitted from the base station (120) (403). The system information is information related to the attributes, characteristics, and / or capabilities of the base station (120) required to connect to the base station (120) and use the service, and can be classified according to content (e.g., whether it is essential for connection), transmission structure (e.g., channel used, whether it is provided on-demand), etc., and can be classified, for example, into first system information (e.g., MIB (master information block), primary system information), second system information (e.g., SIB (system information block), secondary system information), etc. If necessary, the terminal (110) may transmit a signal requesting system information prior to receiving the system information. However, the request and provision of system information may be performed after the random access procedure described later.

[0127] A terminal (110) and a base station (120) can perform a random access procedure (405). The terminal (110) can transmit and / or receive at least one message for a random access procedure (e.g., random access preamble, RAR (random access response) message, etc.) based on information related to the channel for the random access procedure of the base station (120) obtained through system information (e.g., channel location, channel structure, structure of supported preamble, etc.). For example, the terminal (110) can transmit a first message (e.g., preamble, MSG1) through the channel for the random access procedure, receive a second message (e.g., RAR message, MSG2), transmit a third message (e.g., MSG3) containing information related to the terminal (110) (e.g., identification information) to the base station (120) using scheduling information included in the second message, and receive a fourth message (e.g., MSG4) for contention resolution and / or connection establishment. As another example, the first message and the third message can be transmitted and received as a single message, or the second message and the fourth message can be transmitted and received as a single message.

[0128] The terminal (110) and the base station (120) can perform signaling of control information (407). Here, the control information can be defined in various layers, such as a layer that controls the connection (e.g., a radio resource control (RRC) layer), a layer that handles mapping between logical channels and transmission channels (e.g., a media access control (MAC) layer), and a layer that handles physical channels (e.g., a physical (PHY) layer). For example, the terminal (110) and the base station (120) can perform at least one of signaling to establish a connection, signaling to determine settings related to communication, and signaling to indicate allocated resources.

[0129] The terminal (110) and the base station (120) can transmit and / or receive data (409). In other words, the terminal (110) and the base station (120) can process data based on the signaling of control information and transmit and / or receive data. For example, when transmitting data, the terminal (110) or the base station (120) can perform at least one of channel encoding, rate matching, scrambling, constellation mapping, layer mapping, waveform modulation, antenna mapping, and resource mapping on the information bits. Conversely, when receiving data, the terminal (110) or the base station (120) can perform at least one of signal extraction from resources, antenna-specific waveform demodulation, signal placement considering layer mapping, constellation demapping, descrambling, and channel decoding.

[0130] 6G System Core Technology

[0131] The 6G (wireless communication) system aims for (i) very high data rates per device, (ii) a very large number of connected devices, (iii) global connectivity, (iv) very low latency, (v) reduced energy consumption of battery-free IoT (internet of things) devices, (vi) ultra-reliable connectivity, and (vii) connected intelligence with machine learning capabilities. The vision of the 6G system can be four aspects: intelligent connectivity, deep connectivity, holographic connectivity, and ubiquitous connectivity.

[0132] As core implementation technologies for 6G systems, technologies such as artificial intelligence (AI), THz (Terahertz) communication, optical wireless technology, FSO backhaul network, massive MIMO technology, blockchain, 3D networking, quantum communication, unmanned aerial vehicles, cell-free communication, wireless information and energy transfer (WIET), integration of sensing and communication, integration of access backhaul networks, holographic beamforming, big data analysis, and large intelligent surface (LIS) can be adopted.

[0133] artificial intelligence

[0134] The introduction of AI into communications can streamline and enhance real-time data transmission. AI can determine how complex target tasks are performed using numerous analyses. In other words, AI can increase efficiency and reduce processing latency. Time-consuming tasks such as handover, network selection, and resource scheduling can be performed instantly using AI. AI can also play a significant role in M2M, machine-to-human, and human-to-machine communication. Furthermore, AI can enable rapid communication in Brain-Computer Interfaces (BCI). AI-based communication systems can be supported by metamaterials, intelligent structures, intelligent networks, intelligent devices, intelligent cognitive radios, self-sustaining wireless networks, and machine learning.

[0135] The following describes a functional framework for AI / ML operations.

[0136] Below, to provide a more specific explanation of AI (or AI / ML), terms may be defined as follows.

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

[0138] - 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.

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

[0140] - AI / ML Inference: A process of making predictions or deriving decisions based on collected data and AI models using trained AI models.

[0141] Life Cycle Management (LCM) procedures for AI / ML models (i.e., model training, model deployment, model inference, model monitoring, model updating, etc.) can be classified into functionality-based LCM and model-based LCM. In functionality-based LCM, AI / ML models may not be identifiable within the network, and the network can direct the activation, deactivation, fallback, or switching of AI / ML functionality. In model-ID (identifier)-based LCM, AI / ML models can be identified within the network, and the network or terminal can activate, deactivate, select, or switch AI / ML models via the model ID.

[0142] Figure 5 illustrates a general functional architecture for an AI / ML model.

[0143] In particular, Figure 5 illustrates a general functional architecture related to both Functionality-based LCM and Model-based LCM. Some functions or some data / information / command flows (i.e., arrows) illustrated in Figure 5 may be omitted.

[0144] Referring to FIG. 5, a general functional framework may be configured to include a data collection function (10), a model training function (20), a management function (30), an inference function (40), and a model storage function (50).

[0145] The Data Collection function (10) is a function that provides input data to the Model Training function (20), Management function (30), and Inference function (40). The Data Collection function (10) performs data preparation based on raw data and can provide input data processed through data preparation. Examples of raw data may include received data / measurement data from terminals or other network entities, inference / output of AI / ML models, etc. The Data Collection function (10) may be performed by a single entity (e.g., terminal, network node, etc.) but may also be performed by multiple entities.

[0146] Here, training data (11) refers to data required as input for the AI / ML model training function (20). monitoring data (12) refers to data required as input for the management (30) of the AI / ML model or AI / ML function. inference data (13) refers to data required as input for the AI / ML inference function (30).

[0147] The Model Training function (20) is a function that performs AI / ML model training, validation, and testing, which can generate model performance metrics that can be used as part of the AI / ML model testing procedure. If necessary, the Model Training function (20) can perform data preparation (e.g., data pre-processing and cleaning, forming and transformation) based on the Training Data (11) delivered from the Data Collection function (10).

[0148] Trained / Updated Model (21): If there is a Model Storage function (50), it is used to transfer trained, validated, and tested AI / ML models to the Model Storage function (50) or to transfer updated versions of the models to the Model Storage function (50).

[0149] The Management function (30) is a function that supervises the operation of an AI / ML model or an AI / ML function. Additionally, the Management function (30) may make decisions to ensure appropriate inference operations based on data received from the Data Collection function (10) (i.e., Monitoring Data (12)) and / or data received from the Inference function (40) (i.e., Inference Output (41)).

[0150] Management Instruction (32) is information required as input to manage the Inference function (40). The relevant information may include the selection / (de)activation / switching of an AI / ML model or an AI / ML-based function, and may also include a fallback to a non-AI / ML operation (i.e., not relying on the inference process).

[0151] A Model Transfer / Delivery Request (33) can be used to request model(s) from Model Storage (50).

[0152] Performance Feedback / Retraining Request (31) refers to information required as input to Model Training function (20) (e.g., for the purpose of retraining or updating the model).

[0153] The inference function (40) is a function that provides output from the process of applying an AI / ML model or AI / ML function using data (i.e., inference data (13)) provided by the data collection (10) as input. Data preparation (e.g., data preprocessing and cleaning, formatting and transformation) may also be performed based on the inference data (13) delivered by the data collection (10). If necessary, the inference function (40) may also perform data preparation (e.g., data pre-processing and cleaning, forming and transformation) based on the inference data (13) provided by the data collection function (10).

[0154] Inference Output (41) is data used in the Management function (30) to monitor the performance of an AI / ML model or AI / ML function. Inference Output (41) may include the inference output of an AI / ML model generated by the Inference function (30), and the details of the inference output may vary depending on the use case.

[0155] The Model Storage function (50) is a function that stores a trained / updated model that can be used to perform the Inference function (40). The Model Storage function (50) exemplified in FIG. 5 can be used as a reference point (if any) applicable to protocol termination, model transmission / delivery, and related processes. Additionally, the Model Storage function (50) is an example and is not intended to restrict the storage location of the actual AI / ML model, and may be omitted.

[0156] Model Transfer / Delivery (51) is used to transfer an AI / ML model to an inference function.

[0157] Cooperation levels can be defined as follows based on the capability of AI / ML functions among multiple nodes, and variations resulting from the combination of multiple levels or the separation of any one level are also possible.

[0158] Cat 0a) No collaboration framework: AI / ML algorithms are based on pure implementation and do not require changes to the wireless interface.

[0159] Cat 0b) This level corresponds to a framework that involves a wireless interface modified to fit efficient implementation-based AI / ML algorithms but without cooperation.

[0160] Cat 1) Inter-node support is involved to improve the AI / ML algorithms of each node. For example, this applies when a specific node receives support from other nodes (for training, adaptation, etc.) and vice versa. At this level, model exchange between network nodes is not required.

[0161] Cat 2) Collaborative AI / ML tasks can be performed among multiple nodes. This level requires the exchange of AI / ML model commands or network nodes.

[0162] FIG. 5 is a diagram illustrating an overall functional framework for an AI / ML model, and all functions and / or all data / information / command signals illustrated in FIG. 5 may not be performed within a specific node, and only some may be performed.

[0163] AI / ML models can be classified into one-side models and two-side models depending on whether training and / or inference are performed on a single node or jointly / sequentially on multiple nodes.

[0164] A one-side model can refer to an AI / ML model where inference is performed entirely by a single node (e.g., a terminal or a network). Here, the training of the AI / ML model can also be performed entirely by a single node. The training and inference of the AI / ML model may be performed by the same node, or they may be performed by different nodes.

[0165] A two-side model can refer to an AI / ML model in which joint inference is performed across multiple nodes (e.g., terminals and networks). Joint inference means that inference is performed collaboratively across multiple nodes; for example, the first part of the inference may be performed by the first node, and the remainder by the second node. Two-side models can be classified into various types as follows, depending on the training method of the AI / ML model.

[0166] - First type: An AI / ML model can be trained on a single node. In this case, joint training can be performed. The trained model can then be distributed to other nodes / entities.

[0167] - Second type: Joint training of AI / ML models can be performed on multiple nodes / entities (e.g., networks and terminals). Joint training can mean that model generation (e.g., CSI generation) and model reconstruction (CSI compression by sub-use cases) are trained in the same loop for forward activation and backward gradient. In this type, joint training can include both simultaneous training (i.e., model generation training and model reconstruction training are performed simultaneously) and sequential training (i.e., model reconstruction training is performed after model generation training).

[0168] - Third Type: Separate training of AI / ML models can be performed at multiple nodes (e.g., networks and terminals). Separate training may mean that training starts sequentially at one node and continues at another node. In this case, if the first node performs the AI / ML model first and shares the training data with the second node, the second node can perform the AI / ML model using the shared training data. For example, training for the CSI generation part may be performed by the terminal, while CSI reconstruction may be performed by the network.

[0169] FIG. 6 illustrates a communication procedure between a first node (e.g., terminal) and a second node (e.g., base station) to which an AI / ML model is applied.

[0170] The operations described below may be explained / interpreted based on an AI / ML model as shown in FIG. 6 below, even without separate mention (i.e., without explicit mention of being by / based on / for an AI / ML model). Furthermore, unless specifically limited, the AI / ML model may correspond to a one-side model in which inference is performed entirely by a single node or a two-side model in which joint inference is performed by multiple nodes.

[0171] First signaling (601): In the following description, the signaling (e.g., information / data / channel / signal, etc.) or set of signaling between a specific node (e.g., terminal, network, etc.) and another node may be interpreted as the signaling or set of signaling of the first signaling (601) used to perform an operation based on an AI / ML model, even if not otherwise mentioned. For example, it may correspond to training data for training (i.e., creation and / or reconstruction) of the AI / ML model of FIG. 5, or to inference data used for inference of the AI / ML model, or to feedback for the AI / ML model. If, in this specification, signaling between nodes is not required prior to an operation based on an AI / ML model, the first signaling (601) may be omitted. In this specification, if a one-side model is used, the unidirectional / bidirectional signaling (set) in this specification may correspond to the signaling of the first signaling (601). Additionally, when a two-side model is used in the present specification, unidirectional / bidirectional signaling in the present specification may correspond to the first signaling (601), and a repetitive signaling operation may also correspond to the first signaling (601).

[0172] For example, in AI / ML model-based beam management, when a base station predicts (i.e., infers) high-quality beam(s) based on an AI / ML model, the base station can receive quality / intensity information for multiple beams from the terminal. Additionally, when a terminal predicts (i.e., infers) high-quality beam(s) based on an AI / ML model, the terminal can receive multiple beams from the base station.

[0173] AI / ML model-based operation (602): In the following description, an operation (e.g., computation, selection, prediction, etc.) at a specific node (e.g., terminal, network, etc.) or a common operation (e.g., computation, selection, prediction, etc.) at multiple nodes (e.g., terminal, network, etc.) may correspond to an AI / ML model-based operation (602) based on one or more functions in the functional framework of the AI / ML model, even without separate mention. For example, it may correspond to the training (i.e., creation and / or reconstruction) of the AI / ML model of FIG. 5 or to the inference of the AI / ML model. When a one-side model is used, an operation performed by a single node in this specification may correspond to an AI / ML model-based operation (602), and when a two-side model is used, a common operation performed by multiple nodes in this specification may correspond to an AI / ML model-based operation (602).

[0174] For example, in an AI / ML model-based BM, a base station can predict (i.e., infer) high-quality beam(s) based on an AI / ML model by using quality / intensity information for multiple beams received from a terminal as inference data. Additionally, a terminal can measure multiple beams received from a base station and predict (i.e., infer) high-quality beam(s) based on an AI / ML model by using the measurement results as inference data.

[0175] Second signaling (603): In the following description, signaling (e.g., information / data / channel / signal, etc.) or a set of signaling between a specific node (e.g., terminal, network, etc.) and another node may be interpreted as the second signaling (603) or a set of signaling generated as a result of an operation based on an AI / ML model, even without separate mention. For example, it may correspond to the output resulting from the inference of the AI / ML model of FIG. 5. If signaling between nodes is not required as a result of an operation based on an AI / ML model in this specification, the second signaling (603) may be omitted. If a one-side model is used in this specification, the unidirectional / bidirectional signaling (set) in this specification may correspond to the second signaling (603). Additionally, when a two-side model is used in this specification, unidirectional / bidirectional signaling in this specification may correspond to the second signaling (603), and repetitive signaling operation may also correspond to the second signaling (603).

[0176] For example, in an AI / ML model-based BM, the base station may transmit beam(s) predicted based on the AI / ML model as candidates to the terminal so that the terminal can determine the optimal beam. Additionally, the terminal may report the beam(s) predicted based on the AI / ML model to the base station to request the base station to transmit candidate beams as candidates for determining the optimal beam.

[0177] THz communication

[0178] Data transmission rates can be increased by expanding bandwidth. This can be achieved by using sub-THz communication with wide bandwidth and applying advanced large-scale MIMO technology. THz waves, also known as sub-millimeter radiation, generally refer to a frequency band between 0.1 THz and 10 THz with corresponding wavelengths ranging from 0.03 mm to 3 mm. The 100 GHz–300 GHz band range (Sub-THz band) is considered the primary portion of the THz band for cellular communication. Adding the Sub-THz band to the mmWave band increases 6G cellular communication capacity. Among the defined THz bands, the 300 GHz–3 THz band is located in the far-infrared (IR) frequency band. Although the 300 GHz–3 THz band is part of the broadband, it lies at the boundary of the broadband and immediately following the RF band. Therefore, this 300 GHz–3 THz band exhibits similarities to RF.

[0179] FIG. 7 illustrates an electromagnetic spectrum according to one embodiment of the present disclosure. The embodiment of FIG. 7 may be combined with various embodiments of the present disclosure. Key characteristics of THz communication include (i) a widely available bandwidth to support very high data transmission rates, and (ii) high path loss occurring at high frequencies (highly directional antennas are indispensable). The narrow beam width generated by highly directional antennas reduces interference. The small wavelength of THz signals allows a much larger number of antenna elements to be integrated into devices and BSs operating in this band. This enables the use of advanced adaptive array techniques that can overcome range limitations.

[0180] Transmitting system information (i.e., information related to the attributes, characteristics, and / or capabilities of the BS required to use the service, etc.) (e.g., MIB, SIB, etc.) in the THz frequency band can be inefficient because, in the case of high frequency bands, beam sweeping must be performed more frequently to cover the entire area of ​​the cell as the beam width becomes narrow. In particular, transmitting system information in this manner is even more inefficient when there are not many users in the cell. Accordingly, a system information transmission procedure as shown in FIG. 8 below may be used.

[0181] FIG. 8 illustrates an example of a procedure for transmitting system information for THz communication to which the present disclosure applies. Although this example is written with THz conditions in mind, it is also applicable to 6G communication environments where THz is not applied. Furthermore, the procedure exemplified in FIG. 8 can be combined with various embodiments of the present disclosure described below. For example, the embodiments described below may be performed based on the system information obtained by the procedure exemplified in FIG. 8.

[0182] Referring to FIG. 8, the base station can transmit system information of cell #1 through cell #2 (801). That is, the base station provides at least two cells, cell #1 uses the THz frequency band, and cell #2 uses a frequency band other than the THz frequency band. Here, the system information may include at least one information / state / parameter / setting generated at the higher layer and the physical layer, respectively. For example, at least one information / state / parameter / setting generated at the higher layer may include at least one of SFN, control information setting for SIB1 (e.g., PDCCH configuration for SIB1, etc.), information related to cell selection / entry (e.g., cell barring, cell re-selection, etc.), and subcarrier spacing, and at least one information / state / parameter / setting generated at the physical layer may include at least one of SFN, half frame indicator, and SSB index. However, this is merely an example, and system information may include information, status, parameters, and settings related to Cell #1 / Cell #2 generated at various types of physical layers / upper layers. To this end, as an example, Cell #1 and Cell #2 may have a secondary cell and primary cell relationship.

[0183] The UE can obtain synchronization for cell #1 (803). Synchronization can be obtained by detecting a synchronization signal. Generally, synchronization is obtained prior to receiving system information, but since the system information for cell #1 is received in cell #2, synchronization for cell #1 can be obtained after receiving system information. For example, the UE can obtain synchronization based on system information. However, unlike FIG. 8, synchronization may be obtained before step 801 according to other examples.

[0184] The UE can transmit a signal to connect to Cell #1 (805). For example, the signal may include information for connecting to Cell #1 (e.g., a random access preamble). The structure of the signal and the resources for transmitting the signal (e.g., a channel) can be identified through system information. Subsequently, the UE and the base station can perform a connection procedure to Cell #1 and perform communication (807). In this process, operations according to various embodiments described below may be performed.

[0185] The procedure described with reference to FIG. 8 may be performed when the UE (801) first connects to cell #1 of the base station. Alternatively, a similar procedure may be performed when the UE (801) handovers to cell #1 of the base station. However, in the case of a handover, the system information of cell #1 may be received from a cell of a different base station rather than cell #2 of the base station.

[0186] Communication in the THz band is expected to experience severe path loss, and to overcome this, terminals and base stations must use very sharp beams. The use of sharp beams means that terminals and base stations must perform beam control along with beamforming, and the number of beams used becomes very large. Therefore, it takes a very long time to align the transmit and receive beams between the base station and the terminal. In addition, if the beam alignment between the base station and the terminal is misaligned due to the movement of the terminal, time is frequently required to realign the beams, which may result in an unstable link. Accordingly, a beam management procedure as shown in Fig. 9 below may be used.

[0187] FIG. 9 illustrates a beam management procedure applicable to the present disclosure. FIG. 9 illustrates an example of a procedure for searching and / or selecting beams for THz communication, but is not limited to a THz environment and is applicable to a 6G communication environment. Additionally, the procedure exemplified in FIG. 9 may be combined with various embodiments of the present disclosure described below. Here, a beam may be interpreted as 'spatial (configuration) information', 'spatial domain filter', 'spatial domain transmit filter', 'spatial domain receive filter', or / and a term having an equivalent technical meaning capable of distinguishing a beam (e.g., Reference signal, SSB (Synchronization Signal Block) Index, TRP (transmission reception point), panel, cell, TP (transmission point), base station, control resource-related information (e.g., CORESET (control resource set)-related information, etc.).

[0188] Referring to FIG. 9, the base station can configure resources for beam management (901). Here, the resources may include at least one of time-frequency resources, channels, and spatial resources (e.g., antenna ports). For example, the base station may utilize a beam search signal (BSS) that is spatially separated from existing downlink signals / channels for beam search. Here, the BSS may be transmitted based on a dedicated port for beam search. The dedicated port may be a port different from the port for transmitting existing downlink signals / channels (e.g., synchronization signals (e.g., SSB, etc.), data channels (e.g., PDSCH, etc.)). BSS is a term defined for convenience of explanation, and the technical concept according to the present embodiment is not limited to the term BSS itself. That is, a signal transmitted based on a dedicated port defined / configured for beam search may be included in the technical concept according to the present embodiment.

[0189] The base station can transmit measurement signals using multiple transmission beams (903). For example, the measurement signals may include at least one of a reference signal and a synchronization signal. At this time, the measurement signals may be transmitted as many times as the number of beams required for measurement, and may be transmitted using a multi-beam transmission method that forms multiple beams simultaneously to reduce sweeping time. Here, multi-beam transmission may be performed based on at least one of a multi-panel, a sub-array, and a true time delay (TTD).

[0190] The UE can transmit a feedback signal to the base station (905). The feedback signal indicates at least one beam selected by the UE. The UE can select at least one preferred beam based on the received measurement signals. The UE and the base station can perform communication (907). At this time, the UE and the base station can perform communication using the previously selected beam. If channel reciprocity is established, the UE's transmission beam can also be determined through operations 903 and 905, so the UE's transmission can also be performed using the beam selected in operation 905. If channel reciprocity is not established, a procedure including the transmission of the UE's measurement signals and the transmission of the base station's feedback signal may be performed first to determine the UE's transmission beam. In operation 907, operations according to various embodiments described below may be performed.

[0191] Integrated Sensing and Communication (ISAC)

[0192] Wireless sensing is a technology that utilizes radio frequencies to determine the instantaneous linear velocity, angle, and distance (range) of an object, thereby obtaining information about the characteristics of the environment and / or objects within that environment. Since radio frequency sensing capabilities do not require connecting to objects via devices within a network, they can provide services for determining object locations without the need for devices. The ability to obtain range, velocity, and angle information from radio frequency signals can provide a wide range of new functions, such as various object detection, object recognition (e.g., vehicles, humans, animals, UAVs), and high-precision localization, tracking, and activity recognition. Wireless sensing services can provide information to various industries (e.g., unmanned aerial vehicles, smart homes, V2X, factories, railways, public safety, etc.) that enable applications such as intruder detection, assisted vehicle steering and navigation, trajectory tracking, collision avoidance, traffic management, and health and traffic management. In some cases, wireless sensing may utilize non-3GPP type sensors (e.g., radar, cameras) to further support 3GPP-based sensing. For example, the operation of a wireless sensing service, that is, the sensing operation, may depend on the transmission, reflection, and scattering processing of wireless sensing signals. Therefore, wireless sensing can provide an opportunity to enhance existing communication systems from communication networks into wireless communication and sensing networks.

[0193] FIG. 10 illustrates an example of a sensing operation according to an embodiment of the present disclosure. The embodiment of FIG. 10 may be combined with various embodiments of the present disclosure. Specifically, FIG. 10(a) illustrates an example of sensing using a sensing receiver and a sensing transmitter located at the same position (e.g., monostatic sensing), and FIG. 10(b) illustrates an example of sensing using a separated sensing receiver and a sensing transmitter (e.g., bistatic sensing).

[0194] For example, in a wireless communication system based on a 6G network of the present specification, referring to FIG. 10(a), the sensing transmitter and the sensing receiver may be configured to be included in a single base station (i.e., the same base station) or a single terminal (i.e., the same terminal). Alternatively, referring to FIG. 10(b), the sensing transmitter and the sensing receiver may be configured to be included in different base stations, in different terminals, or in a terminal and a base station, respectively.

[0195] In this regard, based on whether the sensing transmitter and the sensing receiver are each included in a base station or a terminal, the following six types of sensing modes can be defined.

[0196] - Mode 1: A mode in which the sensing transmitter and sensing receiver are included in a single base station (e.g., base station-based sensing mode in monostatic mode)

[0197] - Second mode: A mode in which the sensing transmitter is included in the first base station and the sensing receiver is included in a second base station different from the first base station (e.g., base station-based sensing mode in bistatic mode)

[0198] - 3rd Mode: A mode in which the sensing transmitter is included in the base station and the sensing receiver is included in the terminal (e.g., base station-terminal sensing mode)

[0199] - 4th Mode: A mode in which the sensing transmitter is included in the terminal and the sensing receiver is included in the base station (e.g., terminal-base station sensing mode)

[0200] - 5th Mode: A mode in which the sensing transmitter and the sensing receiver are contained in a single terminal (e.g., terminal-based sensing mode in monostatic mode)

[0201] - 6th mode: A mode in which the sensing transmitter is included in the first terminal and the sensing receiver is included in a second terminal different from the first terminal (e.g., terminal-based sensing mode in bistatic mode)

[0202] In a wireless communication system based on a 6G network of the present specification, one or more of the six types of sensing modes described above may be utilized independently or in combination.

[0203] In relation to the sensing operation in FIG. 10, the sensing transmitter may transmit a sensing signal for sensing one or more objects (and / or the environment surrounding the objects). For example, the sensing signal may correspond to a radio (frequency) signal defined to be transmittable by a base station / terminal in a wireless communication system based on a 6G network of the present specification. The sensing receiver may receive a signal that is scattered / reflected by one or more objects (and / or the environment surrounding the objects) from the sensing signal transmitted from the sensing transmitter. In the sensing receiver, sensing data may be derived from the scattered / reflected signal, and sensing results may be generated / obtained through processing of the sensing data. Here, the sensing result may include characteristic information (e.g., location, distance, speed, angle, etc.) about one or more objects (and / or the environment surrounding the objects). The sensing result thus generated / acquired may be utilized for wireless sensing services (e.g., detection, tracking, etc. of objects and / or environments) provided by a wireless communication system based on a 6G network of the present specification, or may be provided / disclosed to a trusted third party.

[0204] Additionally, the sensing operation in FIG. 10 is described using a representative example of operation in a wireless communication system based on a 6G network, but it can be extended and applied to cases where terminals / base stations / signals based on previous generations (e.g., 4G, 5G, etc.) networks are utilized.

[0205] Additionally, with respect to the wireless sensing described in this specification, in a wireless communication system based on a 6G network of this specification, time / frequency resources for sensing operations and time / frequency resources for general communication (e.g., UL / DL / sidelink-based communication, etc.) may be scheduled / configured separately.

[0206] FIG. 11 illustrates a time / frequency resource for a sensing operation according to one embodiment of the present specification. The embodiment of FIG. 11 may be combined with various embodiments of the present disclosure.

[0207] Referring to FIG. 11, the time / frequency resources (hereinafter, sensing resources) for the aforementioned sensing operation (e.g., sensing operation based on FIG. 10) can be set / assigned separately from the time / frequency resources (hereinafter, communication resources) for general communication.

[0208] For example, as illustrated in FIG. 11, sensing resources may be configured / assigned in units of symbols in the time domain and / or in units of resource blocks in the frequency domain. Resources other than those configured / assigned to the sensing resources may be utilized as resources for general communication. That is, sensing resources and communication resources may be configured / assigned based on time-division multiplexing (TDM) and / or frequency-division multiplexing (FDM) methods in terms of base station / terminal operation. Additionally or alternatively, unlike that illustrated in FIG. 10, sensing resources may be configured / assigned based on other units in the time domain (e.g., slot, frame, absolute time (ms, us), etc.) and / or other units in the frequency domain (e.g., subcarrier, carrier, absolute frequency (MHz, GHz), etc.).

[0209] Additionally or alternatively, in relation to the setup / allocation / scheduling of resources for general communication described herein, it may be necessary to consider the relationship between said resources and the aforementioned sensing resources. For example, when setting / allocating resources for general communication according to the embodiments of the present disclosure, said resources may be set / allocated to rate-match or puncturing resource areas corresponding to the sensing resources. For example, when scheduling resources for general communication according to the embodiments of the present disclosure, said resources may be scheduled so as not to overlap with resource areas corresponding to the sensing resources. If resources for general communication and resource areas corresponding to the sensing resources are set / allocated / scheduled to overlap according to the embodiments of the present disclosure, either one or both operations may be dropped, skipped, or postponed based on priority, predefined rules, etc. That is, in the embodiments of this specification, resources related to general communication (e.g., resources for signals / channels related to UL / DL / Sidelink-based data / control, etc.) may be configured / assigned / scheduled so as not to overlap with the aforementioned sensing resources.

[0210] Additionally, various channel modeling methods may be applied in relation to the wireless sensing described herein. Channel modeling related to sensing may mean constructing a path for transmitting and receiving sensing signals and / or scattered / reflected signals by considering the object to be sensed and / or the environment to which the object belongs. Since channel modeling may be related to the performance / requirements of sensing in a wireless communication system, it may be an important matter for verifying the validity of the sensing function.

[0211] Channels related to sensing can be classified into channels between an object (e.g., target of interest) and a sensing transmitter / receiver, and channels between the environment to which the object belongs and a sensing transmitter / receiver. In this regard, channel modeling related to sensing can be classified based on the sensing mode (e.g., the six types of modes mentioned above), whether it is an object or an environment, and / or sensing scenarios. For example, channel modeling for a target in a base station / terminal-based monostatic sensing mode, channel modeling for a target in a base station / terminal-based bistatic sensing mode, channel modeling for an environment in a base station / terminal-based monostatic sensing mode, and channel modeling for an environment in a base station / terminal-based bistatic sensing mode can be optimized and configured differently. For example, when various sensing scenarios are classified, they can be divided into channel modeling for detection, location, and tracking scenarios, channel modeling for motion recognition, and channel modeling for imaging / environment reconstruction scenarios. Additionally, channel modeling related to sensing may be based on statistical channel modeling techniques and / or deterministic channel modeling techniques. For example, modeling for sensing in a wireless communication system based on a 6G network of this specification may be based on stochastic geometry channel modeling techniques and / or hybrid with ray tracing channel modeling techniques. Here, the stochastic geometry channel model may be based on various statistical characteristics of the channel state. Furthermore, the hybrid channel model may be based on both ray tracing techniques and stochastic techniques.In the case of a hybrid approach, channels for objects requiring high accuracy and consistency (e.g., targets of interest) can be modeled using ray tracing techniques, while channels for the environment can be modeled using probabilistic techniques.

[0212] FIG. 12 illustrates a procedure related to a sensing operation according to one embodiment of the present specification. The embodiment of FIG. 12 may be combined with various embodiments of the present disclosure.

[0213] For example, in a wireless communication system based on a 6G network of the present specification, in the case of a sensing operation in which a terminal participates, the base station may need to verify (1205) the terminal's capability for the sensing operation. In this regard, the terminal may be configured to report capability information to the base station regarding whether it supports the sensing operation. Additionally, or alternatively, if the terminal is defined in advance in the specification as supporting the sensing operation, the procedure may be omitted. Furthermore, in the case of a sensing operation in which only the base station participates, the base station may be configured to report capability information regarding whether it supports the sensing operation to the entity that sets / controls its sensing operation (e.g., a network entity at the upper level / layer of the base station).

[0214] For example, a base station may perform signaling with a terminal to exchange configuration information related to a sensing operation. For example, the base station may set / instruct the terminal information regarding the mode of the sensing operation (e.g., based on the six types of modes mentioned above), the subject of the sensing operation (e.g., a sensing transmitter, a sensing receiver), the resource of the sensing operation (e.g., a sensing resource as shown in FIG. 11), the target of utilization of the sensing result (e.g., a type of wireless sensing service based on a 6G network, a trusted third party), and channel modeling for sensing (e.g., a channel between the base station / terminal and an object / environment) (1210). For example, the base station may receive such information from a network entity at the upper level / layer of the base station.

[0215] For example, a base station and / or terminal may perform a sensing operation on information set / instructed (1215). For example, the base station and / or terminal may perform procedures such as transmitting a sensing signal as in FIG. 9 described above, receiving scattered / reflected signals, deriving sensing data, obtaining a sensing result through processing the sensing data, and providing the sensing result, as a role of a sensing transmitter and / or sensing receiver. For example, in the operation of the base station / terminal described in this specification, the sensing result provided through the sensing operation may be utilized.

[0216] < Network Energy Saving, NES >

[0217] Rel-18 Network Energy Saving Technology

[0218] Energy conservation in base stations is considered important in wireless communication systems, including 3GPP, as it contributes to building eco-friendly networks by reducing carbon emissions and lowering the operational expenditures (OPEX) of telecommunications operators. In particular, as the introduction of 5G communication demands high transmission rates, base stations must be equipped with a greater number of antennas and provide services through wider bandwidths and frequency bands. Consequently, recent studies indicate that the energy costs of base stations have reached 20% of total OPEX. Accordingly, 5G systems are adopting various technologies to reduce energy consumption under the name of Network Energy Savings (NES), and the standardization of related technologies is expected to continue.

[0219] With the application of NES technology, the base station can perform operations such as controlling on / off for a certain duration in the time axis, controlling transmit / receive resources for UE-common or UE-specific signals / channels, changing the amount of resources in the frequency axis, controlling transmission power, or turning on / off antenna ports, TRPs (transmission-reception points), etc. in the spatial domain.

[0220] Figure 13 illustrates an example of the operation procedure of a base station supporting NES technology.

[0221] Referring to FIG. 13, the base station can identify the NES solution(s) to be applied (1305). The NES solution(s) may be related to the control of signal transmission and reception (e.g., on / off), beam operation, handover procedures, channel measurement and reporting, etc. Which NES solution(s) to apply may be adaptively selected based on the current situation (e.g., cell load level, characteristics of connected terminals, etc.) or may be predefined. The base station that has identified the NES solution(s) can perform signaling for the NES (1310). The specific signaling procedure may vary depending on the identified NES solution(s). For example, the base station may transmit common information regarding the NES solution(s), transmit configuration information necessary for NES operation to at least one terminal, or transmit control information regarding the progress of the NES operation to at least one terminal. Additionally, the base station may receive capability information related to the NES from at least one terminal. Subsequently, the base station performs operations for the NES. At this time, the base station can perform operations for NES based on the signaling performed earlier (1315). That is, depending on the system information, configuration information, and control information transmitted through the signaling, the base station can turn on / off the transmission and reception of a specific signal, turn on / off elements of the spatial domain, or adjust resources for the transmission and reception of a measurement signal.

[0222] NES technology can be performed through a procedure as shown in Fig. 13. Examples of NES solutions that can be performed by a procedure as shown in Fig. 13 are as follows.

[0223] - Intra-system energy saving solution: A RAN node may request a neighboring RAN node to switch at least one SSB beam into its inactive cell, or perform paging using a limited set of beams to an inactive terminal (e.g., a stationary terminal).

[0224] - Inter-system energy saving solution: An NG-RAN node owning a capacity booster cell can autonomously switch the cell to an inactive state.

[0225] - SSB-less SCell solution: If no SSB or SMTC (SSB-based RRM measurement timing configuration) settings are provided for the SCell, the terminal can obtain timing reference and AGC sources from other serving cells. In FR1 or FR2, the base station can set up intra-band CA or inter-band CA including an SSB-less SCell, in which case SSB / SIB transmission can be triggered by the terminal's WUS (wake-up signal). Accordingly, as the period of common channels / signals such as SSB increases, the base station can remain in a sleep state for a longer period of time.

[0226] - Cell DTX / DRX Solution: To reduce the downlink transmit / uplink receive activity time of a base station, periodic cell DTX / DRX patterns (e.g., active and inactive periods) may be set commonly for terminals within a cell having the corresponding feature. Here, the cell DTX pattern and the cell DRX pattern may be set and activated separately, and up to two cell DTX / DRX patterns may be set per MAC entity. When cell DTX is set and activated, at least one of monitoring SPS opportunities or PDCCH monitoring may be suspended during the cell DTX inactive period. When cell DRX is set and activated, at least one of transmitting from CG resources or SR transmitting may be suspended during the cell DRX inactive period. Cell DTX / DRX may be enabled / disabled via RRC signaling or L1 group common signaling.

[0227] Parameters such as active duration and cycle may be set for the cell DTX / DRX. The active duration is the period during which the terminal waits to transmit an SR or CG after receiving a PDCCH or SPS opportunity, and the cycle specifies the periodic repetition of the active duration and the inactive duration. When both the cell DTX and cell DRX are set, parameters such as the active duration and cycle are common. If the base station recognizes an emergency call or public safety-related service (e.g., MPS or MCS), the network may release or disable the cell DTX / DRX settings so as not to affect the service. Additionally, at least some overlap is required between the active duration of the terminal's connected mode DRX and the active duration of the cell DTX / DRX. For example, the period of the terminal's connected mode DRX may be a multiple of the cell DTX / DRX period, or vice versa.

[0228] - Conditional Handover (CHO) Solution: A CHO procedure, performed in such a way that the execution of a handover is determined by the terminal, is used while NES technology is applied (e.g., when a cell enables or disables Cell DTX / DRX). In this case, the terminal may use an NES-specific CHO event to execute a CHO for a candidate cell, and as an additional triggering condition for this, the reception of a DCI that enables CHO condition(s) set as an NES event indication may be applied.

[0229] - Spatial and power domain adaptation solution: To support the gNB for transceiver muting and / or transmission power adaptation, the terminal may be configured to report multiple CSI entries in the CSI report based on multiple sub-configurations. Each sub-configuration corresponds to a spatial domain adaptation pattern (e.g., a subset of available spatial elements) and / or a data channel (e.g., PDSCH) and a power offset between CSI and RS. Depending on the application of the spatial and power domain adaptation solution, CSI configuration, measurement, and / or reporting behavior may be affected.

[0230] Cell DTX / DRX

[0231] To operate the base station in sleep mode for a relatively long period without frequent wake-ups, base station DTX / DRX is proposed for NES purposes. The base station can reduce energy consumption by using DTX transmission under low system load conditions by setting cell DTX and setting the on-duration of terminals' C-DRX within the active period of cell DTX. Figure 14 illustrates an example of a procedure for cell DTX / DRX operation.

[0232] Referring to FIG. 14, the base station transmits system information to the terminal (1401), and the terminal checks information related to cell DTX / DRX (1402). For example, the system information may include MIB, SIB1, etc. In relation to NES technology, MIB may include information related to cell barring (e.g., cellBarred), and SIB1 may include information related to cell barring status (e.g., cellBarredNES). Specifically, if cellBarred included in the MIB is set to a value indicating that it is not barred (e.g., notBarred), the terminal may determine that the cell is not barred, regardless of whether it supports NES cell DTX / DRX. Conversely, if cellBarred included in the received MIB is set to a value indicating that the cell is barred (e.g., barred), the terminal that does not support NES cell DTX / DRX may determine that the cell is barred. However, if the terminal has the capability to support NES cell DTX / DRX, the terminal checks SIB1 to determine the cell blocking status. If cellBarred in the MIB is set to barred and cellBarredNES is absent in SIB1, the terminal supporting NES cell DTX / DRX treats the cell as blocked and can perform cell reselection to another cell. On the other hand, if cellBarred in the MIB is set to barred and cellBarredNES is included in SIB1, the terminal supporting NES cell DTX / DRX can determine that the cell is not blocked.

[0233] In the case of FIG. 14, the terminal has the capability to support NES cell DTX / DRX, and it is assumed that cellBarred in the MIB is set to notBarred or cellBarred in the MIB is set to barred, and cellBarredNES is included in SIB1. Accordingly, the terminal can perform a random access procedure to connect to the base station (1403) and then perform communication. At this time, the base station performs a cell DTX / DRX operation and transmits configuration information related to the cell DTX / DRX operation to the terminal (1404). The configuration information related to the cell DTX / DRX operation (e.g., CellDTXDRX-Config) includes at least one parameter related to the cell DTX / DRX, and may include, for example, at least one of an on-duration timer, a cycle start offset, a slot offset, a configuration type (e.g., DTX, DRX, or DTX-DRX), and an activation state of the DTX / DRX (e.g., active, inactive). In addition, the configuration information may further include information for receiving and interpreting control information related to cell DRX / DRX (e.g., DCI-related information).

[0234] Subsequently, the base station transmits control information related to cell DTX / DRX to the terminal (1405). The control information related to cell DTX / DRX may include DCI having a specified format (e.g., format 2_9). When an operation for a serving cell according to at least one of cell DTX operation and cell DRX operation is set by configuration information (e.g., cellDTXDRX-Config), the terminal can identify a set of search spaces (e.g., Type3-PDCCH CSS set) for monitoring PDCCH that transmits control information of the specified format during the active time through an upper layer parameter (e.g., SearchSpace), and obtain the location of information about the serving cell within the control information through an upper layer parameter (e.g., positionInDCI-cellDTRX). Then, the terminal can obtain the control information based on the identified set of search spaces and location.

[0235] Control information related to cell DTX / DRX may be used to indicate the activation or deactivation of cell DTX and / or cell DRX, and / or to provide an NES-mode indicator, and may include, for example, at least one block including a cell DTX / DRX indicator and an NES-mode indicator. In this case, when the serving cell is set to a supplementary uplink (SUL) carrier, the indication for the activation or deactivation of cell DRX by the cell DTX / DRX indicator may be applied to both the UL carrier and the SUL carrier.

[0236] Subsequently, the terminal and the base station can communicate based on the cell DTX / DRX (1406). Specifically, the base station can turn on / off the transmission and reception of signals according to the settings related to the cell DTX / DRX, and accordingly, the terminal can selectively monitor signals from the base station. During DTX-OFF, the base station enters sleep mode to reduce energy consumption. At this time, the base station DTX cycle can be aligned with the terminal DRX cycle. The base station DTX-ON can completely cover the terminal's DRX-ON. Furthermore, the base station can align the transmission of Xn / NG and the transmission of Uu for NES purposes. The DTX / DRX mechanism triggers the switching of reference signal resource set groups, and the base station can perform dormancy-like behavior of transmitting SSB, SIB, and CSI-RS sparingly or not transmitting them to reduce energy consumption. The terminal can receive downlink signals / channels sparingly or not receive them according to the base station's settings. Once the base station DTX / DRX operation is triggered, during the DTX / DRX OFF period, the terminal can discontinuously receive the corresponding CSI-RS, SSB, or PDCCH.

[0237] SSB-less SCell

[0238] Figure 15 illustrates an example of a procedure for CA operation using an SSB-less SCell.

[0239] Referring to FIG. 15, the base station transmits configuration information for SCell to the terminal. That is, the base station transmits configuration information for CA to provide services to the terminal through CA operation. Here, the CA operation may be intra-band CA or inter-band CA. For example, the configuration information for SCell may include information related to SCell addition (e.g., sCellToAddModList), and specifically, may include a cell index, physical cell identifier, information related to DL-UL settings, information related to BWP, information related to cell DTX / DRX, and information related to downlink frequency (e.g., FrequencyInfoDL). Subsequently, the terminal determines the settings for CA operation and can perform communication using the base station's PCell and SCell. At this time, the terminal can confirm that the SCell is an SSB-free SCell based on the information related to the downlink frequency included in the configuration information, and can check the related parameters. For example, the terminal can determine that the SCell is an SSB-less SCell by confirming the existence of a parameter (e.g., SSBlessSCell) indicating that the SCell is an SSB-less SCell, and can determine the timing reference and AGC source for the SCell based on information about the reference cell (e.g., referenceCell). In the case of FIG. 15, the reference cell may be a PCell. Therefore, the terminal can use the PCell as the timing reference and AGC source for communication in the SCell.

[0240] Conditional Hand Over (CHO)

[0241] FIG. 16 illustrates an example of a Conditional HandOver (CHO) procedure. The order of the actions exemplified in FIG. 16 may vary depending on the case.

[0242] Referring to FIG. 16, the base station transmits configuration information for CHO to the terminal (1601). The configuration information for CHO may include information related to conditional reconfiguration (e.g., ConditionalReconfiguration, CondReconfigToAddModList) and information related to the configuration for reporting (e.g., ReportConfigNR). Here, the information related to the configuration for reporting may include information related to events related to reporting, identifiers of events (e.g., condEventId), information indicating whether it is an NES-specific CHO event (e.g., nesEvent), etc. In the example of FIG. 16, event information indicating that it is an NES-specific CHO event is received.

[0243] The base station transmits information to the terminal that enables NES-specific CHO execution conditions (1602). The information that enables NES-specific CHO execution conditions may be transmitted via control information of a specified format (e.g., DCI format 2_9). The information that enables NES-specific CHO execution conditions may be referred to as an NES-mode indicator, and, for example, as 1-bit information, an associated upper layer parameter (e.g., nesEvent) is set, and if the serving cell of the associated block in the corresponding DCI is the primary cell, it indicates that NES-specific CHO execution conditions are enabled.

[0244] Subsequently, the terminal performs a measurement (1603) and transmits the measurement report to the base station (1604). The base station determines the CHO based on the measurement report and performs signaling for a handover request with adjacent base stations indicated by the measurement report (1606). The base station determines the adjacent base stations that have affirmed admission through signaling as candidate base stations and transmits information about the candidate base stations to the terminal (1607). Accordingly, the terminal evaluates the CHO execution conditions for the candidate base stations (1608). Accordingly, when a candidate cell satisfying the conditions is determined, the terminal detaches from the old cell and synchronizes with the new cell (1609). At this time, since the terminal has previously received event information indicating that it is an NES-specific CHO event and has also received information enabling the NES-specific CHO execution conditions, it can determine whether the event is satisfied. In other words, when an NES-mode indicator is received through a lower layer and conditional triggering configuration information (e.g., condTriggerConfig) includes information indicating that it is an NES-specific CHO event (e.g., nesEvent), the terminal determines that an event associated with a corresponding measurement identifier (e.g., measId) is satisfied, and accordingly, can determine that the CHO execution condition is satisfied.

[0245] NES Enhancement

[0246] In 3GPP NR release 19, discussions on NES enhancement are scheduled to take place, and (1) on-demand SSB, (2) on-demand SIB1 transmission and (3) adaptation of common signal / channel transmissions are being considered as major targets.

[0247] (1) On-demand SSB

[0248] A method to reduce energy consumption can be discussed in which the base station transmits SSBs to specific cells through an on-demand SSB process and does not transmit SSBs to those cells when the on-demand SSB process is not present. In existing NR systems, it was difficult to reduce energy consumption even when the base station had no data to receive or send, as SSBs had to be transmitted periodically at all times for purposes such as time / frequency synchronization or RRM measurement. Considering this, the base station's energy consumption can be reduced by allowing it to refrain from transmitting SSBs and only perform transmissions when the on-demand SSB process is involved. This on-demand SSB process can be triggered through one of the following methods.

[0249] 1) The terminal requests the base station's SSB transmission by transmitting an uplink signal / channel (e.g., PRACH, PUCCH, PUSCH, SRS, etc. in an NR system).

[0250] 2) Base Station (or TRP) #1 requests SSB transmission from Base Station (or TRP) #2 via an interface between base stations (e.g., Xn interface in an NR system) or backhaul signaling.

[0251] 3) Signal whether the corresponding SSB is transmitted via Scell ​​activation / deactivation signaling

[0252] Considering coexistence with existing NR terminals, the on-demand SSB operation for connected mode terminals and SCells in Release 19 is limited, but in future releases or next-generation communication systems, on-demand SSB operation (for SSB transmission on a PCell) may be defined considering inactive or idle mode terminals or initial connected terminals. Additionally, carrier aggregation (CA) including the SCell may be applied to both intra-band CA and inter-band CA, and the SSB on the SCell transmitted through the on-demand SSB process may be utilized for at least time / frequency synchronization, L1 / L3 measurement, SCell activation, and other functionalities.

[0253] (2) On-demand SIB1 transmission

[0254] A method to reduce energy consumption can be discussed in which the base station transmits a SIB1 for a specific cell through an on-demand SIB1 process, and does not transmit the SIB1 for that cell when the on-demand SIB1 process is not present. In existing NR systems, it was difficult to reduce energy consumption even when the base station had no data to receive or send, because it was always necessary to periodically provide a SIB1 containing system information and random access information for initial access or idle mode terminals to connect to a cell. Considering this, the base station's energy consumption can be reduced by allowing it to refrain from transmitting SIB1 and only transmit it when the on-demand SIB1 process is involved. The base station's SIB1 transmission can be triggered by the terminal transmitting an uplink signal / channel (e.g., PRACH in an NR system), and specifically, the following scenarios can be considered, but may not be limited to them.

[0255] 1) Scenario 1: As shown in FIG. 17 (a), a terminal that receives an SSB (and / or other downlink signal / channel) at cell #1 and recognizes that SIB1 is not being transmitted on cell #1 can trigger the transmission of SIB1 by transmitting a signal requesting SIB1 (for convenience, the signal is referred to as WUS, wake-up signal) based on information provided by the SSB (and / or other downlink signal / channel) and / or pre-determined information. A base station that receives the WUS can transmit a specific DL signal / channel on cell #1 in response, or transmit SIB1 on cell #1 (or without transmitting the DL signal / channel).

[0256] 2) Scenario 2: As shown in FIG. 17 (b), a terminal that receives an SSB (and / or other downlink signal / channel such as SIB1) at cell #1 and realizes that SIB1 is not being transmitted on cell #2 may attempt to camp-on through cell #2. Based on the information provided by the received SSB (and / or other downlink signal / channel such as SIB1) and / or predetermined information, the terminal may transmit a signal requesting SIB1 (i.e., WUS) onto cell #1 to trigger the transmission of SIB1 to cell #2. A base station that receives the WUS may transmit a specific DL signal / channel (on cell #1 or cell #2) in response, or transmit SIB1 to cell #1 or cell #2 (or without transmitting the DL signal / channel).

[0257] 3) Scenario 3: As in Fig. 17(c), a terminal that receives an SSB (and / or other downlink signal / channel such as SIB1) at cell #1 and realizes that SIB1 is not being transmitted on cell #2 may attempt to camp-on through cell #2. The terminal may trigger the transmission of SIB1 for cell #2 by transmitting a signal requesting SIB1 (i.e., WUS) on cell #2 based on the information provided in the received SSB (and / or other downlink signal / channel such as SIB1) and / or pre-determined information. A base station that receives the WUS may transmit a specific DL signal / channel (on cell #1 or cell #2) in response, or transmit SIB1 for cell #2 on cell #1 or cell #2 (or without transmitting the DL signal / channel).

[0258] (3) adaptation of common signal / channel transmissions

[0259] Methods to reduce energy consumption by controlling common signal / channel transmissions such as SSB, PRACH, and paging can be discussed. While completely turning off the SSB can significantly reduce the energy consumption of the base station, the absence of an SSB that performs functions such as time / frequency synchronization or RRM measurement may result in unstable operation for the corresponding cell from the terminal's perspective. Considering this, energy saving effects for the base station can be achieved by changing the transmission pattern of the SSB (e.g., transmission period, period per SSB candidate index(es), SSB candidate index(es) transmitted within one transmission period, transmission power, etc.) depending on the situation.

[0260] In the case of PRACH resources, in the case of contention-based random access, energy consumption can increase because the base station always attempts to receive from the configured PRACH resources since it is unknown when the terminal will transmit PRACH. Considering this, the energy of the base station can be saved by applying methods to adjust the amount of PRACH resources (e.g., adjusting the period of the PRACH resources, adjusting the amount of resources by pre-configuring PRACH resource set #1 and set #2 and giving instructions such as whether to turn on only one set or both sets, or providing the amount of PRACH resources corresponding to each SSB index uniformly or non-uniformly).

[0261] In the case of paging, conventionally, paging frames (PF) and / or paging occasions (PO) were distributed along the time axis within the DRX cycle (or paging cycle), and terminals attempted to receive paging at specific PF / POs derived from their ID-based formulas. From the base station's perspective, if it intended to transmit paging to multiple terminals simultaneously, it was necessary to transmit paging while frequently breaking the data. To reduce the resulting energy consumption of the base station, it is possible to consider placing the PF and / or PO for paging reception as close to the time axis as possible, or placing them using different frequency axis resources within the same timeframe.

[0262] On-demand SSB-based CSI-related operations and procedures

[0263] This disclosure proposes a measurement and reporting method utilizing two different types of SSBs. For example, the two types of SSBs are specifically as follows.

[0264] (1) Example 1: On-demand SSB on the first cell, in which transmission is initiated by a base station instruction or a terminal request.

[0265] - Type 1 SSB: This may refer to an SSB that is periodically transmitted over a first cell or a second cell. If the period, etc., for the SSB is determined / defined / set, the SSB may be transmitted continuously at that period (without on or off intervals, or without activation or deactivation). If Type 1 SSB refers to an SSB transmitted over a first cell, the first cell may be a timing reference cell. If Type 1 SSB refers to an SSB transmitted over a second cell, the second cell may be in an intra-band or inter-band carrier aggregation relationship with the first cell, and (especially in an inter-band CA environment) the second cell may be set as a timing reference cell for the first cell, or (especially in an intra-band CA environment) the second cell may be determined / defined as a timing reference cell for the first cell (e.g., any cell, PCell, or PSCell within the same timing advance group). Additionally, only the following Type 2 SSB may be transmitted over the first cell without a Type 1 SSB.

[0266] - Type 2 SSB (or on-demand SSB): This may refer to an SSB in which transmission on the first cell is activated by instructions from the base station (via RRC / MAC-CE / DCI, etc.). Alternatively, it may refer to an SSB in which transmission is activated by a request from the terminal. For the activated SSB, the SSB deactivation may be explicitly instructed through RRC / MAC-CE / DCI, etc., or the number of transmissions or transmission intervals may be set / instructed in the RRC / MAC-CE / DCI that instructs SSB activation, and the SSB may be deactivated after the number of transmissions or transmission intervals have passed, or the SSB may be deactivated after the number of transmissions or transmission intervals have passed after the SSB activation, or (if the first cell is SCell) the SSB may be deactivated when the activation for the first cell is completed (or when CSI reporting for the first cell is successfully reported), or (if the first cell is SCell) the SSB may be deactivated when the first cell is deactivated, or (if the first cell is PCell) the SSB may be deactivated after a hand-over is performed, or the SSB may be deactivated by a request from the terminal.

[0267] - In Example 1, the case where only OD (on-demand)-SSB can be transmitted and AO (always on)-SSB is not transmitted for a single cell is named Case #1, and the case where both AO-SSB and OD-SSB can be transmitted is named Case #2.

[0268] In addition, the OD-SSB of Example 1 above may be configured with one or more od-ssb-configs when SSB parameters such as those in Table 1 below can be configured within the od-ssb-config IE, or it may be configured in the form of a list containing one or more of the SSB parameters below. When multiple od-ssb-configs are configured, each od-ssb-config has an index value, and one of the index values ​​may be activated / deactivated by being indicated via RRC / MAC-CE / DCI. Alternatively, when it may be configured in the form of a list containing one or more of the SSB parameters, the OD-SSB may be activated / deactivated by being indicated via RRC / MAC-CE / DCI as to which parameter value within the list is actually applied.

[0269] - The physical cell identifier of SS / PBCH blocks is indicated by od-ssb-physCellId if provided, otherwise by the physCellId of ServingCellConfigCommon. - The indices of transmitted SS / PBCH blocks are indicated by RRC / MAC CE / DCI from among the candidate values ​​provided by od-ssb-PositionsInBurst if provided, otherwise by ssb-PositionsInBurst. - The frequency position of SS / PBCH blocks is indicated by od-absoluteFrequencySSB if provided, otherwise by absoluteFrequencySSB. - The subcarrier spacing (SCS) setting of SS / PBCH blocks is indicated by od-ssbSubcarrierSpacing if provided, otherwise by ssbSubcarrierSpacing. - The power of SS / PBCH blocks is indicated by od-ss-PBCH-BlockPower if provided, and by ss-PBCH-BlockPower otherwise. - The periodicity of SS / PBCH block transmission is indicated by RRC / MAC CE / DCI from among the candidate values ​​given by od-ssb-Periodicity if od-ssb-Periodicity is provided. - The half frame for SS / PBCH block transmission is determined based on the indication of RRC / MAC CE / DCI. SS / PBCH block transmission is performed in a frame satisfying (SFN + SFN_offset)*10 mod P = 0, where P represents the period of SS / PBCH block transmission.SFN_offset is the SFN offset indicated by RRC / MAC CE / DCI among the candidate values ​​given by od-ssb-sfn-Offset if od-ssb-sfn-Offset is provided, otherwise SFN_offset = 0. The index of the half-frame in which the SS / PBCH block is transmitted in the frame is indicated by RRC / MAC CE / DCI among the candidate values ​​given by od-ssb-halfFrameIndex if od-ssb-halfFrameIndex is provided, otherwise the index of the half-frame is 0.

[0270] (2) Example 2: A method in which one or more SSB configurations are set and an SSB corresponding to one of the SSB configurations is transmitted by a base station instruction or a request from a terminal. At this time, the SSB periodicity values ​​may differ between the different SSB configurations, and an adaptation to the SSB periodicity may be performed by changing the activated SSB configuration.

[0271] - Type 1 SSB: Among the configured SSB configurations, this can refer to the reference configuration or the configuration with the largest SSB periodicity value. The SSB corresponding to the reference configuration can be called a Type 1 SSB. If the SSB configuration corresponding to a Type 2 SSB is not activated, the SSB configuration corresponding to that Type 1 SSB can be activated. Conversely, if the SSB configuration corresponding to a Type 2 SSB (or an SSB configuration not corresponding to a Type 1 SSB) is activated, the SSB configuration corresponding to that Type 1 SSB can be deactivated. Or, if an SSB occasion configured based on a specific (reference) configuration among the configured SSB configurations (referred to as “reference SSB occasions” for convenience) becomes a subset of an SSB occasion configured based on another configuration (referred to as “extended SSB occasions” for convenience), an SSB on the reference SSB occasions (regardless of the actual activated SSB configuration) may be defined as a type 1 SSB, and in this case, a type 2 SSB may be defined as an SSB on the remaining SSB occasions among the extended SSB occasions (included in the actual activated configuration) excluding the reference SSB occasions.

[0272] - Type 2 SSB: In addition to the SSB configuration corresponding to Type 1 SSB, one or more SSB configurations for Type 2 SSB may be configured, and when the SSB configuration corresponding to Type 2 SSB is activated, all SSBs belonging to the activated SSB configuration may be defined as Type 2 SSBs. Alternatively, if SSB occasions configured based on a specific (reference) configuration among the configured SSB configurations (referred to as “reference SSB occasions” for convenience) become a subset of SSB occasions configured based on another configuration (referred to as “extended SSB occasions” for convenience), the SSBs on the reference SSB occasions may be defined as Type 1 SSBs (regardless of the actual activated SSB configuration), and in this case, Type 2 SSBs may be defined as SSBs on the remaining SSB occasions among the extended SSB occasions (included in the actual activated configuration), excluding the reference SSB occasions. One or more of the corresponding SSB configurations may be activated by a command from the base station (via RRC / MAC-CE / DCI) or by a request from the terminal.For the activated SSB configuration, the SSB may be deactivated by (i) explicitly instructed to deactivate via RRC / MAC-CE / DCI, etc., or (ii) the number of transmissions or transmission intervals are set / instructed in the RRC / MAC-CE / DCI that instructs SSB activation, and the SSB is deactivated after the number of transmissions or transmission intervals have passed, or (iii) the number of transmissions or transmission intervals are set / defined in advance, and the SSB is deactivated after the number of transmissions or transmission intervals have passed following SSB activation, or (iv) (if the first cell is SCell) the SSB is deactivated when activation for the first cell is completed (or when CSI reporting for the first cell is successfully reported), or (v) (if the first cell is SCell) the SSB is deactivated when the first cell is deactivated, or (vi) (if the first cell is PCell) the SSB is deactivated after a hand-over is performed, and / or (vii) the SSB may be deactivated by a request from the terminal.

[0273] (3) Example 3: A method in which one or more SSB configurations are set and an SSB corresponding to one of the SSB configurations can be transmitted by a base station instruction or a request from a terminal. In this case, there is an SSB (e.g., type 1 SSB) that is continuously and periodically transmitted regardless of the (de)activation of the SSB configuration(s), and an additional SSB configuration to be transmitted to the SSB can be (de)activated. At least the SSB periodicity value and / or SSB time pattern may differ between different SSB configurations, and adaptation to the SSB periodicity may be performed by changing the activated SSB configuration.

[0274] - Type 1 SSB: This may refer to an SSB corresponding to the Default SSB configuration, and continuous periodic transmission may be guaranteed regardless of the (de)activation of the SSB configuration(s) corresponding to the type 2 SSB.

[0275] - Type 2 SSB: One or more SSB configurations for Type 2 SSB may be configured. One of the one or more SSB configurations may be activated by a command from the base station (via RRC / MAC-CE / DCI) or by a request from the terminal. For the activated SSB configuration, SSB deactivation may be explicitly instructed through RRC / MAC-CE / DCI, etc., or the number of transmissions or transmission intervals may be set / instructed in the RRC / MAC-CE / DCI that instructs SSB activation, and the SSB may be deactivated after the number of transmissions or transmission intervals have passed, or there may be a pre-set / defined number of transmissions or transmission intervals, and the SSB may be deactivated after the number of transmissions or transmission intervals have passed after the SSB activation, or (if the first cell is SCell) the SSB may be deactivated when the activation for the first cell is completed (or when CSI reporting for the first cell is successfully reported), or (if the first cell is SCell) the SSB may be deactivated when the first cell is deactivated, or (if the first cell is PCell) the SSB may be deactivated after a hand-over is performed, or the SSB may be deactivated by a request from the terminal.

[0276] As in the examples above, Type 2 SSB may mean an SSB that cannot assume continuous periodic transmission.

[0277] Specifically below, we intend to propose the CSI report configuration settings and CSI report reporting methods for type 1 SSB and type 2 SSB, the CPU (CSI processing unit) determination method, and / or the CPU / CSI processing timeline determination method.

[0278] [Proposal #1] CSI report configuration settings and CSI report transmission

[0279] For any serving cell in which a Type 1 SSB and a Type 2 SSB are operating, the CSI report configuration (e.g., CSI-ReportConfig) method considered in the present invention may be one of the following two methods.

[0280] (1) Opt1: For a single CSI report configuration, only one type of SSB can be linked, either a type 1 SSB or a type 2 SSB.

[0281] (2) Opt2: Both type 1 SSB and type 2 SSB can be linked for a single CSI report configuration.

[0282] For example, when two different types of SSBs, such as the aforementioned Opt2, can be linked to a single CSI report configuration, we would like to propose a specific configuration method and a CSI reporting method.

[0283] First, I would like to propose a method for configuring CSI report settings utilizing the concept of sub-configuration introduced in Rel-18.

[0284] Table 2 is a portion of CSI-ReportConfig IE and CSI-ResourceConfig IE extracted from TS38.331 Rel.18.

[0285] [CSI-ReportConfig]CSI-ReportConfig ::= SEQUENCE {reportConfigId CSI-ReportConfigId,carrier ServCellIndexresourcesForChannelMeasurement CSI-ResourceConfigId,csi-IM-ResourcesForInterference CSI-ResourceConfigIdnzp-CSI-RS-ResourcesForInterference CSI-ResourceConfigId...csi-ReportSubConfigToAddModList-r18 SEQUENCE (SIZE (1..maxNrofCSI-ReportSubconfigPerCSI-ReportConfig-r18)) OF CSI-ReportSubConfig-r18...CSI-ReportSubConfig-r18 ::= SEQUENCE {reportSubConfigId-r18 CSI-ReportSubConfigId-r18,reportSubConfigParams-r18 CHOICE {a1-parameters SEQUENCE {codebookSubConfig-r18 CodebookConfigportSubsetIndicator-r18 CHOICE {p2 BIT STRING (SIZE (2)),p4 BIT STRING (SIZE (4)),p8 BIT STRING (SIZE (8)),p12 BIT STRING (SIZE (12)),p16 BIT STRING (SIZE (16)),p24 BIT STRING (SIZE (24)),p32 BIT STRING (SIZE (32))}non-PMI-PortIndication-r18 SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourcesPerConfig)) OF PortIndexFor8Ranks},a2-parameters SEQUENCE {nzp-CSI-RS-ResourceList-r18 SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourcesPerSet)) OF NZP-CSI-RS-ResourceIndex-r18}}powerOffset-r18 INTEGER(0..23)}[CSI-ResourceConfig]CSI-ResourceConfig ::= SEQUENCE {csi-ResourceConfigId CSI-ResourceConfigId,csi-RS-ResourceSetList CHOICE {nzp-CSI-RS-SSB SEQUENCE {nzp-CSI-RS-ResourceSetList SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig)) OF NZP-CSI-RS-ResourceSetIdcsi-SSB-ResourceSetList SEQUENCE (SIZE (1..maxNrofCSI-SSB-ResourceSetsPerConfig)) OF CSI-SSB-ResourceSetId},csi-IM-ResourceSetList SEQUENCE (SIZE (1..maxNrofCSI-IM-ResourceSetsPerConfig)) OF CSI-IM-ResourceSetId},bwp-Id BWP-Id,resourceType ENUMERATED { aperiodic, semiPersistent, periodic},...,[[csi-SSB-ResourceSetListExt-r17 CSI-SSB-ResourceSetId]].

[0286] Referring to Table 2, a single CSI report configuration is linked to a single CSI resource configuration (e.g., CSI-resourceConfig) for channel measurement purposes, and the CSI resource configuration can be linked to one or more resource set lists (e.g., csi-RS-ResourceSetList). In this case, the structure allows SSBs to be linked within each list. Specifically, SSB resources can be linked within an SSB resource list (e.g., csi-SSB-ResourceSetList) belonging to a single resource set list.

[0287] According to one embodiment, when setting up a CSI report configuration and setting up an SSB-based L1 measurement through the CSI report (e.g., when the parameter reportQuantity is set to one of 'ssb-Index-RSRP', 'ssb-Index-SINR', 'ssb-Index-RSRP-Index', or 'ssb-Index-SINR-Index'), multiple sub-configurations may be set up and an SSB type linked to each sub-configuration may be set. At this time, the method for setting the specific SSB type linked to each sub-configuration may follow at least some of the following Methods 1 to 3.

[0288] (1) Method 1: (For channel measurement purposes) one or more CSI resource configurations (e.g., CSI-resourceConfig) are linked to the corresponding CSI report configuration, and each CSI resource configuration may be linked to only one type of SSB, either a type 1 SSB or a type 2 SSB. For each sub-configuration, an index of the linked CSI resource configuration (or the parameter name of the corresponding CSI resource configuration) may be additionally set. For example, CSI resource configuration #1 may be linked to a type 1 SSB and CSI resource configuration #2 may be linked to a type 2 SSB, and CSI resource configuration #1 and #2 may be linked to the corresponding CSI report configuration (for channel measurement purposes). Additionally, (at least) two sub-configurations may be set for the corresponding CSI report configuration, and CSI resource configuration #1 may be linked to sub-configuration #0 and CSI resource configuration #2 may be linked to sub-configuration #1, thereby linking different types of SSBs to each sub-configuration. Alternatively, by linking CSI resource configurations #1 and #2 to a single sub-configuration, both types of SSBs can be linked to that single sub-configuration.

[0289] (2) Method 2: One or more SSB resource lists are linked within a single CSI resource configuration, and each SSB resource list may be linked to only one type of SSB, either a type 1 SSB or a type 2 SSB. An index of the linked SSB resource list (or the parameter name of the corresponding SSB resource list) may be additionally set for each sub-configuration. For example, SSB resource list #1 may be configured to be linked to a type 1 SSB and SSB resource list #2 may be configured to be linked to a type 2 SSB, and the CSI resource configuration linked to SSB resource lists #1 and #2 may be linked to the corresponding CSI report configuration. Additionally, two sub-configurations may be configured for the corresponding CSI report configuration, and SSB resource list #1 may be linked to sub-configuration #0 and SSB resource list #2 may be linked to sub-configuration #1, thereby linking different types of SSBs to each sub-configuration. Alternatively, by linking SSB resource lists #1 and #2 to a single sub-configuration, both types of SSBs can be linked to that single sub-configuration.

[0290] (3) Method 3: A configuration may be allowed in which a single SSB resource list belonging to a single CSI resource configuration includes not only a type 1 SSB but also a type 2 SSB. For each sub-configuration, an additional resource set index (or the parameter name of the corresponding resource set) belonging to the linked SSB resource list may be configured. For example, resource set #1 and resource set #2 belonging to the same SSB resource list may be configured, and resource set #1 may be linked to a type 1 SSB and resource set #2 may be linked to a type 2 SSB, and the CSI resource configuration linked to resource set #1 and #2 may be linked to the corresponding CSI report configuration. Additionally, two sub-configurations may be configured for the corresponding CSI report configuration, and resource set #1 may be linked to sub-configuration #0 and resource set #2 may be linked to sub-configuration #1, thereby linking different types of SSBs to each sub-configuration. Alternatively, resource sets #1 and #2 can be linked for a single sub-configuration, allowing both types of SSBs to be linked for that single sub-configuration.

[0291] The above Methods 1, 2, and 3 can be extended to a method of linking a single CSI report configuration with both types of SSBs when no sub-configuration is set within a single CSI report configuration. Specifically, when setting up a single CSI report configuration and setting up an SSB-based L1 measurement through the CSI report (e.g., when the parameter reportQuantity is set to one of 'ssb-Index-RSRP', 'ssb-Index-SINR', 'ssb-Index-RSRP-Index', or 'ssb-Index-SINR-Index'), the method of linking a single CSI report configuration with both types of SSBs may follow at least some of Methods 1A to 3A.

[0292] (1) Method 1A: (for channel measurement purposes) one or more CSI resource configurations (e.g., CSI-resourceConfig) are linked to the corresponding CSI report configuration, and each CSI resource configuration can be linked to only one type of SSB, either a type 1 SSB or a type 2 SSB. For example, CSI resource configuration #1 is configured to be linked to a type 1 SSB and CSI resource configuration #2 is configured to be linked to a type 2 SSB, and CSI resource configuration #1 and #2 can be linked to the corresponding CSI report configuration (for channel measurement purposes). Through this, both types of SSBs can be linked to a single CSI report configuration.

[0293] (2) Method 2A: One or more SSB resource lists are linked within a single CSI resource configuration, and each SSB resource list may be linked to only one type of SSB, either a type 1 SSB or a type 2 SSB. For example, SSB resource list #1 is configured to be linked to a type 1 SSB and SSB resource list #2 is configured to be linked to a type 2 SSB, and the CSI resource configuration linked to SSB resource lists #1 and #2 can be linked to the corresponding CSI report configuration. Through this, SSB resource lists #1 and #2 can be linked to a single CSI report configuration, thereby allowing both types of SSBs to be linked to a single CSI report configuration.

[0294] (3) Method 3A: A configuration may be allowed in which a single SSB resource list belonging to a single CSI resource configuration includes not only a type 1 SSB but also a type 2 SSB. For example, resource set #1 and resource set #2 belonging to the same SSB resource list may be configured such that resource set #1 is linked to a type 1 SSB and resource set #2 is linked to a type 2 SSB, and the CSI resource configuration linked to resource set #1 and #2 may be linked to the corresponding CSI report configuration. Through this, resource set #1 and #2 may be linked to a single CSI report configuration, thereby allowing both types of SSBs to be linked to a single CSI report configuration.

[0295] In at least one of the above Methods 1, 1A, 2, 2A, 3, and 3A, the CSI resource configuration linked to the type 1 SSB and the CSI resource configuration linked to the type 2 SSB may be distinguished by different associated parameter names or specific parameters within each configuration, the SSB resource list linked to the type 1 SSB and the SSB resource list linked to the type 2 SSB may be distinguished by different associated parameter names or specific parameters within each list, and the resource set linked to the type 1 SSB and the resource set linked to the type 2 SSB may be distinguished by different associated parameter names or specific parameters within each resource set.

[0296] For example, for a single CSI report configuration, CSI reporting from an actual terminal can be performed as follows depending on the reporting type:

[0297] - When Periodic CSI reporting is configured, the terminal can periodically perform CSI reporting through the configured PUCCH resource.

[0298] - When semi-persistent CSI reporting on PUCCH is configured, the terminal can periodically perform CSI reporting through the linked semi-persistent PUCCH resource when the CSI reporting is activated via MAC-CE. Additionally, (when the CSI report configuration is configured to be linked with type 1 SSB and type 2 SSB), the MAC-CE may be instructed on which report to perform, the report for type 1 SSB or the report for type 2 SSB.

[0299] - When semi-persistent CSI reporting on PUSCH is configured, the terminal can periodically perform CSI reporting through the linked semi-persistent PUSCH resource when the CSI reporting is triggered via the DCI. Additionally, (when the CSI report configuration is configured to be linked with type 1 SSB and type 2 SSB), the DCI may be instructed on which report to perform, the report for type 1 SSB or the report for type 2 SSB.

[0300] - When Aperiodic CSI reporting is configured, the terminal can perform CSI reporting through a scheduled PUSCH resource when the CSI reporting is triggered via a DCI (e.g., UL grant). Additionally, (when the CSI report configuration is configured to be linked with a type 1 SSB and a type 2 SSB), the DCI may be instructed on which report to perform, the report for the type 1 SSB or the report for the type 2 SSB.

[0301] For example, if L sub-configurations are set for a single CSI report configuration, actual terminal CSI reporting can be performed as follows depending on the reporting type:

[0302] - When Periodic CSI reporting is configured, the terminal can periodically perform CSI reporting for all L sub-configurations through the configured PUCCH resources.

[0303] - When semi-persistent CSI reporting on PUCCH is configured, the terminal can periodically perform CSI reporting for N sub-configurations among L that are activated through the corresponding MAC-CE via the linked semi-persistent PUCCH resource when the corresponding CSI reporting is activated via MAC-CE. Additionally, (when a sub-configuration configured within the corresponding CSI report configuration is configured to be linked with type 1 SSB and type 2 SSB), the MAC-CE may be instructed to perform either reporting for type 1 SSB or reporting for type 2 SSB (for each sub-configuration).

[0304] - When semi-persistent CSI reporting on PUSCH is configured, the terminal can periodically perform CSI reporting for N sub-configurations triggered through the corresponding DCI via the linked semi-persistent PUSCH resource when the corresponding CSI reporting is triggered through the DCI. Additionally, (when a sub-configuration configured within the corresponding CSI report configuration is configured to be linked with a type 1 SSB and a type 2 SSB), the DCI may be instructed to determine which report to perform between the report for the type 1 SSB and the report for the type 2 SSB (for each sub-configuration).

[0305] - When Aperiodic CSI reporting is configured, the terminal can perform CSI reporting for N sub-configurations triggered by the corresponding DCI (e.g., UL grant) through a scheduled PUSCH resource when the CSI reporting is triggered by the corresponding DCI. Additionally, (when a sub-configuration configured within the corresponding CSI report configuration is configured to be linked with a type 1 SSB and a type 2 SSB), the DCI may be instructed to perform either reporting for the type 1 SSB or reporting for the type 2 SSB (for each sub-configuration).

[0306] When the terminal performs CSI reporting through the above process, both Type 1 SSB and Type 2 SSB can be interconnected for a single CSI report configuration (by applying the above Method 1A / 2A / 3A) or for a single sub-configuration (by applying the above Method 1 / 2 / 3). In this case, as with the existing NR standard method extracted from Table 3 below, K S SSB If the value is determined, it may be ambiguous as to which of the two types of SSBs corresponds to the number of SS / PBCH block indices.

[0307] (1) Alt 1:K S SSB can be the number of SS / PBCH blocks configured within the resource set associated with the type 1 SSB. S SSB is the configured number of SS / PBCH blocks in the resource set associated with type 1 SSB]]

[0308] (2) Alt 2:K S SSB can be the number of SS / PBCH blocks configured within the resource set associated with the type 2 SSB. S SSB is the configured number of SS / PBCH blocks in the resource set associated with type 2 SSB]]

[0309] (3) Alt 3:K S SSB is the maximum value between the number of SS / PBCH blocks configured within the resource set associated with the type 1 SSB and the number of SS / PBCH blocks configured within the resource set associated with the type 2 SSB. [[K S SSBis the maximum between the configured number of SS / PBCH blocks in the resource set associated with type 1 SSB and the configured number of SS / PBCH blocks in the resource set associated with type 2 SSB]]

[0310] Table 3 is a partial excerpt from TS 38.212 v18.4.0.

[0311]

[0312]

[0313]

[0314]

[0315] Generally, considering that type 1 SSBs are transmitted continuously and periodically, the number of SS / PBCH block indices associated with type 1 SSBs may be greater than the number of SS / PBCH block indices associated with type 2 SSBs, so applying Alt 1 may be more stable. However, if measurements can be performed and reported based solely on type 2 SSBs rather than type 1 SSBs in specific situations, applying Alt 2 may be advantageous in terms of CSI payload size.

[0316] If there is no mismatch between the base station and the terminal when performing and reporting measurements based on only one of the type 1 SSB or type 2 SSB (e.g., the terminal reports which type of SSB is based via a 1-bit indicator in the CSI report, the SCell transmitting the type 2 SSB is in the activation process, the SCell transmitting the type 2 SSB is in a deactivation state, the type 2 SSB is activated and therefore only the type 2 SSB is used, or the MAC-CE / DCI activating / triggering the CSI reporting indicates which SSB, type 1 or type 2, should be used), then Alt 2 is applied; otherwise, Alt 1 may be applied. Alternatively, in this case, only Alt 1 may always be applied.

[0317] Alternatively, considering that the number of SS / PBCH block indices linked to a type 1 SSB may differ from the number of SS / PBCH block indices linked to a type 2 SSB, K based on the maximum value among them, as in Alt 3 S SSB The value can be determined.

[0318] In addition, when utilizing type 1 SSB and type 2 SSB through a single CSI report (a CSI report corresponding to a CSI report configuration) or a single CSI sub-report (a CSI report corresponding to a sub-configuration), the CSI payload can be constructed by combining the two types of SSBs according to pre-set / defined rules into a single report value (e.g., a common SSBRI / (differential) RSRP / (differential) SINR value for type 1 / 2 SSBs) or by constructing the CSI payload into individual report values ​​for each type (e.g., the SSBRI / (differential) RSRP / (differential) SINR value for type 1 SSB and the SSBRI / (differential) RSRP / (differential) SINR value for type 2 as individual values).

[0319] When the terminal performs CSI reporting through the above process, only Type 2 SSBs can be integrated for a single CSI report configuration (by applying the above Method 1A / 2A / 3A) or for a single sub-configuration (by applying the above Method 1 / 2 / 3). In this case, K S SSB The value can be determined by the number of actually transmitted SSB indices linked to / configured in the type 2 SSB activated via RRC / MAC CE / DCI (or the number of SSB indices configured by the od-ssb-PositionsInBurst parameter).

[0320] [Proposal #2] Decide CPU occupation

[0321] A CPU (CSI processing unit) refers to a unit required by a terminal to simultaneously process / update CSI reports at a specific point in time, and the maximum number of CPUs per carrier or for all carriers may be determined / limited based on the capability reported by the terminal.

[0322] As stated in Section 5.2.1.6 of the TS 38.214 standard, the number of CPUs currently occupied (=L) and the maximum number of CPUs supported by the terminal (N CPU Given ), the terminal has the number of CPUs currently processing / updating (e.g., Equation 1) and {N CPU Compare the values ​​of - L}.

[0323]

[0324] If the number of unoccupied CPUs is less than the number of CPUs currently processing / updating, the terminal may not update CSI information corresponding to some CSI reports with lower priority according to the priority of the CSI reports.

[0325] Meanwhile, as in Section 5.4 of the TS 38.214 standard document, minimum values ​​for the processing time of the terminal are also defined according to the configuration / type of the CSI report. In particular, as shown in Table 4, when configuring a single CSI report configuration and setting up an SSB-based L1 measurement through the CSI report (e.g., when the parameter reportQuantity is set to one of 'ssb-Index-RSRP', 'ssb-Index-SINR', 'ssb-Index-RSRP-Index', or 'ssb-Index-SINR-Index'), the number of CPUs is defined as 1.

[0326] Table 4 is a partial excerpt from TS 38.214 v18.4.0.

[0327] UE is N CPU It is not expected to be configured with an aperiodic CSI trigger state containing more than N reporting settings. Processing of CSI reports occupies a certain number of CPUs for a certain number of symbols as follows: CPU Reporting Settings. Processing of a CSI report occupies a number of CPUs for a number of symbols as follows:]]- (omitted)- For a CSI report with LTM-CSI-ReportConfig, or a CSI report with CSI-ReportConfig where the upper tier parameter (reportQuantity) is set to 'cri-RSRP', 'ssb-Index-RSRP', 'cri-SINR', 'ssb-Index-SINR', 'cri-RSRP-Index', 'ssb-Index-RSRP-Index', 'cri-SINR-Index', 'ssb-Index-SINR-Index', or 'none' (and in the case of a CSI-RS-ResourceSet where the upper tier parameter trs-Info is not set), O CPU =1 [[O CPU=1 for a CSI report with LTM-CSI-ReportConfig or a CSI report with CSI-ReportConfig with higher layer parameter reportQuantity set to 'cri-RSRP', 'ssb-Index-RSRP', 'cri-SINR', 'ssb-Index-SINR', 'cri-RSRP- Index', 'ssb-Index-RSRP- Index', 'cri-SINR- Index', 'ssb-Index-SINR- Index ' or 'none' (and CSI-RS-ResourceSet with higher layer parameter trs-Info not configured)]]

[0328] When a terminal performs a CSI report through the process described in [Proposal #1], if the following cases are considered, when setting an SSB-based L1 measurement through the CSI report (e.g., when the parameter reportQuantity is set to one of 'ssb-Index-RSRP', 'ssb-Index-SINR', 'ssb-Index-RSRP- Index', 'ssb-Index-SINR- Index'), the number of CPUs corresponding to the CSI report can be defined as a value greater than 1.

[0329] (1) Case A: For a single CSI report configuration, both type 1 SSB and type 2 SSB can be linked (by applying the above Method 1A / 2A / 3A).

[0330] (2) Case B: For a single sub-configuration, both type 1 SSB and type 2 SSB can be interconnected (by applying Method 1 / 2 / 3 above).

[0331] (3) Case C: For a single CSI report configuration, multiple sub-configurations are set up (by applying Method 1 / 2 / 3 above), and each sub-configuration is linked to only one type of SSB, either type 1 SSB or type 2 SSB. Even if the sub-configuration linked to the type 1 SSB and the sub-configuration linked to the type 2 SSB are both configured with a CSI sub-report.

[0332] When at least one of the above cases applies (and when the terminal actually performs measurement / reporting using both types of SSB), the CPU value corresponding to the CSI report may be increased to 2 (or a real value between 1 and 2), kept at 1, or determined to be 1 or 2 (or a real value between 1 and 2) depending on UE capability signaling and / or base station settings.

[0333] Alternatively, even if the above case is satisfied, if the actual terminal performs and reports measurements using only one of the two types of SSB, the corresponding CPU value may remain 1. For example, if a SCell transmitting a type 2 SSB is in the activation process, or a SCell transmitting a type 2 SSB is in a deactivation state, or if a rule is set / defined to use only the type 2 SSB because the type 2 SSB is activated, or if it is set / instructed via RRC / MAC-CE / DCI to use only one of the two types of SSB, then only the type 2 SSB is used for actual measurement / reporting, so the CPU value may remain 1. As another example, if the type 2 SSB is deactivated and only the type 1 SSB is used for actual measurement / reporting, the CPU value may remain 1.

[0334] Alternatively, even if the above case is satisfied, the CPU value may be kept at 1 if at least one of the following conditions is satisfied, and increased to 2 (or a real value between 1 and 2) otherwise. This is because, if the following conditions are satisfied, the terminal complexity may not increase relatively significantly even if measurement / reporting is performed using two types of SSBs.

[0335] (i) Condition 1: When the center frequencies of Type 1 SSB and Type 2 SSB are set / determined to be the same (or when the difference in center frequencies between the two SSBs is less than or equal to a specific value), said specific value may be a predefined or set value.

[0336] (ii) Condition 2: When the configured / determined downlink transmit power (or EPRE) values ​​of Type 1 SSB and Type 2 SSB are identical (or when the difference in TX power between the two SSBs is less than or equal to a specific value), said specific value may be a predefined or configured value.

[0337] (iii) Condition 3: When there is not a significant difference in SSB periodicity between Type 1 SSB and Type 2 SSB

[0338] (iv) Condition 4: When the half frame index where Type 1 SSB is transmitted and the half frame index where Type 2 SSB is transmitted are the same

[0339] (v) Condition 5: When Type 1 SSB and Type 2 SSB are included within an active DL BWP

[0340] (vi) Condition 6: When the combined pattern of Type 1 SSB and Type 2 SSB is regular. In this case, the regularity of the pattern means that when the transmission occasions of Type 1 SSB and Type 2 SSB are combined, a pattern of a constant period is formed. For example, if Type 1 SSB has a period of 20 msec and is transmitted in even index frames, and Type 2 SSB has a period of 20 msec and is transmitted in odd index frames, and both Type 1 and Type 2 SSB are transmitted in half frames of the same index (e.g., 1st half frame), then when the transmission occasions of Type 1 SSB and Type 2 SSB are combined, a constant pattern of a period of 10 msec is formed, so it can be considered a regular pattern. On the other hand, even if a type 1 SSB has a period of 20 msec and is transmitted in even index frames and a type 2 SSB has a period of 20 msec and is transmitted in odd index frames, if the type 1 SSB and the type 2 SSB are transmitted in half frames of different indices (e.g., the type 1 SSB is in the 1st half frame and the type 2 SSB is in the 2nd half frame), when the transmission occasions of the type 1 SSB and the type 2 SSB are combined, a pattern of constant intervals of 5 msec or 15 msec is not formed, so it may be considered not to be a regular pattern.

[0341] [Proposal #3] CPU / CSI Timeline Determination

[0342] Table 5 is a partial excerpt from TS 38.214 v18.4.0.

[0343]

[0344]

[0345] Figure 18 is a diagram illustrating the existing NR standard method of CPU occupancy based on Table 5. For the sake of convenience of explanation, only CSI reporting based on SSBs (without CSI-RS / CSI-IM) is considered, assuming (i) the CSI report is triggered in slot #n, (ii) the slot where the CSI reference resource is located is slot #k-4, and (iii) the CSI report is transmitted from #k. The earliest SSB resource at which CPU occupancy begins is SSB1, and the SSB0 resource prior to the CSI report trigger may be excluded. Therefore, CPU occupancy begins from the first symbol of SSB1. Meanwhile, the SSBs subject to channel measurement include SSB1 and SSB2, while SSB3, located after the CSI reference resource, is excluded from measurement. The latest SSB subject to measurement is SSB2. Meanwhile, among the symbols included in slot #k, CPU occupancy continues up to the last symbol used for the CSI report. Meanwhile, for convenience of explanation in Fig. 18, it was assumed that the CSI reference resource is located in slot #k-4, but the method for determining the slot where the CSI reference resource is located is defined in Section 5.2.2.5 of the NR standard TS38.214, and according to this, the CSI reference resource may be located in slot #k-4 or the CSI reference resource may be located in slot #k-5.

[0346] As shown in Table 5 above, the CPU occupies the portion based on SSB resource / occasion. However, for a serving cell that has a type 1 SSB and / or a type 2 SSB, it may be ambiguous which type of SSB should be used as the basis for determining the CPU occupancy portion.

[0347] When a terminal performs a CSI report through the process described in [Proposal #1], if the following cases are considered as examples, when setting an SSB-based L1 measurement through the CSI report (e.g., when the parameter reportQuantity is set to one of 'ssb-Index-RSRP', 'ssb-Index-SINR', 'ssb-Index-RSRP- Index', 'ssb-Index-SINR- Index'), the CPU occupancy interval corresponding to the CSI report can be determined based on type 1 SSB.

[0348] (1) Case A1: Only type 1 SSB is linked to a single CSI report configuration

[0349] (2) Case B1: Multiple sub-configurations are configured for a single CSI report configuration, and only type 1 SSBs are linked for all sub-configurations.

[0350] (3) Case C1: For a single CSI report configuration, multiple sub-configurations are set up (by applying Method 1 / 2 / 3 above), and each sub-configuration is linked to only one type of SSB, either type 1 SSB or type 2 SSB. However, a CSI sub-report can be configured only for the sub-configuration linked to the type 1 SSB.

[0351] When a terminal performs a CSI report through the process described in [Proposal #1], for example, if the following cases are considered, when setting an SSB-based L1 measurement through the CSI report (e.g., when the parameter reportQuantity is set to one of 'ssb-Index-RSRP', 'ssb-Index-SINR', 'ssb-Index-RSRP- Index', 'ssb-Index-SINR- Index'), the CPU occupancy interval corresponding to the CSI report can be determined based on type 2 SSB.

[0352] (1) Case A2: Only type 2 SSB is linked to a single CSI report configuration

[0353] (2) Case B2: Multiple sub-configurations are configured for a single CSI report configuration, and only Type 2 SSBs are linked for all sub-configurations.

[0354] (3) Case C2: For a single CSI report configuration, multiple sub-configurations are set (by applying Method 1 / 2 / 3 above), and each sub-configuration is linked to only one type of SSB, either type 1 SSB or type 2 SSB, but the CSI sub-report can be configured only for the sub-configuration linked to the type 2 SSB.

[0355] also,

[0356] (1) Case A3: For a single CSI report configuration, both type 1 SSB and type 2 SSB can be linked (by applying the above Method 1A / 2A / 3A).

[0357] (2) Case B3: For a single sub-configuration, both type 1 SSB and type 2 SSB can be interconnected (by applying Method 1 / 2 / 3 above).

[0358] (3) Case C3: For a single CSI report configuration, multiple sub-configurations are set up (by applying Method 1 / 2 / 3 above), and for each sub-configuration, even if only one type of SSB, either type 1 SSB or type 2 SSB, is linked, a CSI sub-report can be configured for both the sub-configuration linked to the type 1 SSB and the sub-configuration linked to the type 2 SSB.

[0359] When a terminal performs a CSI report through the process described in [Proposal #1], considering the above cases, when setting an SSB-based L1 measurement through the CSI report (e.g., when the parameter reportQuantity is set to one of 'ssb-Index-RSRP', 'ssb-Index-SINR', 'ssb-Index-RSRP-Index', or 'ssb-Index-SINR-Index'), the CPU occupancy period corresponding to the CSI report can be determined by one of the following Alts.

[0360] (1) Alt A: Type 1 / 2 Determine CPU usage based on earliest / latest SSB regardless of SSB distinction

[0361] (2) Alt B: When Type 2 SSB is activated, determine the CPU occupancy period based on the earliest / latest SSB regardless of Type 1 / 2 SSB, and when Type 2 SSB is deactivated, determine the CPU occupancy period based on Type 1 SSB.

[0362] - For example, Alt B can be applied when both types of SSBs exist and measurements are performed and reported using both types of SSBs.

[0363] (3) Alt C: Determines the CPU occupancy period based on the type 2 SSB when the type 2 SSB is activated, and determines the CPU occupancy period based on the type 1 SSB when the type 2 SSB is deactivated

[0364] - For example, Alt C can be applied when a measurement is performed and reported using only one type of SSB (i.e., type 2 SSB) even if both type 1 and type 2 SSBs exist. For example, this may be when a SCell transmitting a type 2 SSB is in the activation process, or when a rule is set / defined to use only the type 2 SSB because the type 2 SSB is activated, or when it is set / instructed via RRC / MAC-CE / DCI to use only one of the two types of SSBs.

[0365] New parameters (e.g., 'od-ssb-Index-RSRP', 'od-ssb-Index-SINR', 'od-ssb-Index-RSRP-Index', 'od-ssb-Index-SINR-Index') may be introduced to the existing reportQuantity. When these parameters are set, the terminal can consider the corresponding CSI report configuration to be connected only to type 2 SSB. In this way, when the terminal performs CSI reporting, for a CSI report in which a type 2 SSB-based L1 measurement is configured (e.g., when the parameter reportQuantity is set to one of 'od-ssb-Index-RSRP', 'od-ssb-Index-SINR', 'od-ssb-Index-RSRP-Index', 'od-ssb-Index-SINR-Index', or when only a type 2 SSB is linked to the CSI report through another method), the CPU occupancy period corresponding to the CSI report can be determined by the following method.

[0366] - When the Type 2 SSB is activated, the CPU occupancy period is determined based on the activated Type 2 SSB. If the Type 2 SSB is deactivated, CPU occupancy can be omitted. In other words, when the Type 2 SSB is deactivated, the CPU based on the CSI report with the L1 measurement set based on the Type 2 SSB can be 0.

[0367] Even if the CPU occupancy period is determined through the above methods, the CPU value may fluctuate within a single CPU occupancy period due to type 2 SSB activation or type 2 SSB deactivation. For example, (while the type 2 SSB is activated) the CPU occupancy period may be determined based on type 1 SSB and / or type 2 SSB, resulting in a CPU value of 2 (or a real value between 1 and 2). However, if the type 2 SSB is deactivated within the same period, the CPU value may change to 1 due to the type 2 SSB deactivation, or the CPU value for the corresponding CSI report within the period may remain constant at 2 (or a real value between 1 and 2) (regardless of whether the type 2 SSB is deactivated), or the terminal may not expect type 2 SSB deactivation while executing the CSI report. As another example, (while the type 2 SSB is deactivated) the CPU occupancy period may be determined based on type 1 SSB, resulting in a CPU value of 1. However, if a type 2 SSB is activated within the same interval (and does not correspond to the condition of [Proposal #2] above), the CPU value may be changed to 2 (or a real value between 1 and 2) due to the type 2 SSB activation, or the CPU value for the corresponding CSI report within the interval may be kept constant at 1 while the type 2 SSB is not utilized for measurement, or the terminal may not expect a type 2 SSB activation while executing the CSI report.

[0368] For example, if a terminal has determined a time interval during which the CPU is occupied in a first type 2 SSB activation / deactivation state, the terminal may not expect to receive network signaling that changes the first type 2 SSB activation / deactivation state to a second type 2 SSB deactivation / activation state (e.g., the opposite of the first type 2 SSB activation / deactivation state) within that time interval.

[0369] Table 6 is a partial excerpt from TS 38.214 v18.4.0.

[0370] 5.2.1.4.3 L1-RSRP Reporting For L1-RSRP computation, the UE may be configured with CSI-RS resources, SS / PBCH Block resources or both CSI-RS and SS / PBCH Block resources, when resource-wise quasi co-located with 'type C' and 'type D' when applicable. The UE may be configured with a CSI-RS resource configuration consisting of up to 16 sets of CSI-RS resources, each set may contain up to 64 resources. The total number of different CSI-RS resources across all resource sets does not exceed 128. For L1-RSRP reporting, if the upper-level parameter nrofReportedRS of CSI-ReportConfig is set to 1, or if both the upper-level parameters nrOfReportedCells and nrOfReportedRS-PerCell are set to 1, the reported L1-RSRP value is defined as a 7-bit value with a 1 dB step size in the range of [-140, -44] dBm.If the upper tier parameter nrofReportedRS is set to a value greater than 1, or if the upper tier parameter groupBasedBeamReporting is set to 'enabled', or if the upper tier parameter groupBasedBeamReporting-r17 is set, or if either the upper tier parameter nrOfReportedCells or nrOfReportedRS-PerCell is set to a value greater than 1, the UE must use a differential L1-RSRP-based reporting scheme. In this case, the largest of the measured L1-RSRP values ​​is quantized into 7-bit values ​​in 1-dB intervals within the [-140, -44] dBm range, and the differential L1-RSRP is quantized into 4-bit values. The differential L1-RSRP values ​​are calculated in 2-dB intervals based on the largest measured L1-RSRP value within the same L1-RSRP reporting instance. The mapping between the reported L1-RSRP values ​​and the measured quantity is described in [11, TS 38.133].[[For L1-RSRP reporting, if the higher layer parameter nrofReportedRS in CSI-ReportConfig is configured to be one, or if the higher layer parameters nrOfReportedCells and nrOfReportedRS-PerCell are both configured to be one, the reported L1-RSRP value is defined by a 7-bit value in the range [-140, -44] dBm with 1dB step size, if the higher layer parameter nrofReportedRS is configured to be larger than one, or if the higher layer parameter groupBasedBeamReporting is configured as 'enabled', or if the higher layer parameter groupBasedBeamReporting-r17 is configured, or if any of the higher layer parameters nrOfReportedCells and nrOfReportedRS-PerCell is configured to be larger than one, the UE shall use differential L1-RSRP based reporting, where the largest measured value of L1-RSRP is quantized to a 7-bit value in the range [-140, -44] dBm with 1dB step size, and the differential L1-RSRP is quantized to a 4-bit value.The differential L1-RSRP value is computed with a 2 dB step size with a reference to the largest measured L1-RSRP value, which is part of the same L1-RSRP reporting instance. The mapping between the reported L1-RSRP value and the measured quantity is described in [11, TS 38.133]. If the upper-level parameter groupBasedBeamReporting-r17 of CSI-ReportConfig is set, the UE must indicate the set of CSI resources where the largest L1-RSRP value was measured, and within each group, the CRI or SSBRI of the indicated set of CSI resources must be provided first. [[When the higher layer parameter groupBasedBeamReporting-r17in CSI-ReportConfig is configured, the UE shall indicate the CSI Resource Set associated with the largest measured value of L1-RSRP, and for each group, CRI or SSBRI of the indicated CSI Resource Set is present first.]] When the higher layer parameter timeRestrictionForChannelMeasurements of CSI-ReportConfig is set to "notConfigured", the UE must derive channel measurements for calculating the L1-RSRP value reported in uplink slot n based only on the SS / PBCH or NZP CSI-RS that is not delayed compared to the CSI reference resource (defined in TS 38.211 [4]) associated with the CSI resource set.[[If the higher layer parameter timeRestrictionForChannelMeasurements in CSI-ReportConfig is set to "notConfigured", the UE shall derive the channel measurements for computing L1-RSRP value reported in uplink slot n based on only the SS / PBCH or NZP CSI-RS, no later than the CSI reference resource, (defined in TS 38.211[4]) associated with the CSI resource setting.]] If the higher layer parameter timeRestrictionForChannelMeasurements in CSI-ReportConfig is set to "Configured", the UE shall derive the channel measurements for computing the L1-RSRP value reported in uplink slot n based only on the most recent SS / PBCH opportunity or NZP CSI-RS that is no later than the CSI reference resource associated with the CSI resource setting (defined in TS 38.211 [4]). [[If the higher layer parameter timeRestrictionForChannelMeasurements in CSI-ReportConfig is set to "Configured", the UE shall derive the channel measurements for computing L1-RSRP reported in uplink slot n based on only the most recent, no later than the CSI reference resource, occasion of SS / PBCH or NZP CSI-RS (defined in [4, TS 38.211]) associated with the CSI resource setting.]]<omitted>5.2.1.4.4 L1-SINR Reporting For L1-SINR calculation, for channel measurement, the UE may be configured with NZP CSI-RS resources and / or SS / PBCH block resources. For L1-SINR computation, for channel measurement the UE may be configured with NZP CSI-RS resources and / or SS / PBCH Block resources. For channel measurement, the UE may be configured with a CSI-RS resource setting consisting of up to 16 resource sets, with a total of up to 64 CSI-RS resources or up to 64 SS / PBCH Block resources. For L1-SINR reporting, if the upper-level parameter nrofReportedRS of CSI-ReportConfig is set to 1, the reported L1-SINR value It is defined as a 7-bit value with a step size of 0.5 dB in the [-23, 40] dB range. If the upper-level parameter nrofReportedRS is set to a value greater than 1, or if the upper-level parameter groupBasedBeamReporting is set to 'enabled', the UE must use differential L1-SINR-based reporting.At this time, the largest of the measured L1-SINR values ​​is quantized into 7-bit values ​​in 0.5 dB intervals within the [-23, 40] dB range, and the differential L1-SINR is quantized into 4-bit values. The differential L1-SINR values ​​are calculated in 1 dB intervals based on the largest measured L1-SINR value within the same L1-SINR reporting instance. When NZP CSI-RS is configured for channel measurements and / or interference measurements, the reported L1-SINR values ​​must not be compensated by applying the power offset given by the upper layer parameter powerControlOffsetSS or powerControlOffset. [[For L1-SINR reporting, if the higher layer parameter nrofReportedRS in CSI-ReportConfig is configured to be one, the reported L1-SINR value is defined by a 7-bit value in the range [-23, 40] dB with 0.5 dB step size, and if the higher layer parameter nrofReportedRS is configured to be larger than one, or if the higher layer parameter groupBasedBeamReporting is configured as 'enabled', the UE shall use differential L1-SINR based reporting, where the largest measured value of L1-SINR is quantized to a 7-bit value in the range [-23, 40] dB with 0.5 dB step size, and the differential L1-SINR is quantized to a 4-bit value.The differential L1-SINR is computed with a 1 dB step size with a reference to the largest measured L1-SINR value, which is part of the same L1-SINR reporting instance. When NZP CSI-RS is configured for channel measurement and / or interference measurement, the reported L1-SINR values ​​should not be compensated by the power offset(s) given by the higher layer parameter powerControOffsetSS or powerControlOffset. When one or two resource settings are configured for L1-SINR measurement: - When the higher layer parameter timeRestrictionForChannelMeasurements of CSI-ReportConfig is set to 'notConfigured', the UE must derive the channel measurement for calculating the L1-SINR value reported in uplink slot n based only on the SSB or NZP CSI-RS that is not delayed compared to the CSI reference resource (defined in TS 38.211 [4]) associated with the CSI resource setting.[[If the higher layer parameter timeRestrictionForChannelMeasurements in CSI-ReportConfig is set to 'notConfigured', the UE shall derive the channel measurements for computing L1-SINR reported in uplink slot n based on only the SSB or NZP CSI-RS, no later than the CSI reference resource, (defined in TS 38.211[4]) associated with the CSI resource setting.]]- If the higher layer parameter timeRestrictionForChannelMeasurements in CSI-ReportConfig is set to 'configured', the UE shall derive the channel measurements for computing L1-SINR reported in uplink slot n based only on the most recent SSB or NZP CSI-RS opportunity that is no later than the CSI reference resource associated with the CSI resource setting (defined in TS 38.211 [4]). measurements for computing L1-SINR reported in uplink slot n based on only the most recent, no later than the CSI reference resource, occasion of SSB or NZP CSI-RS (defined in [4, TS 38.211]) associated with the CSI resource setting.If the higher layer parameter timeRestrictionForInterferenceMeasurements in CSI-ReportConfig is set to 'notConfigured', the UE shall derive the interference measurements for computing L1-SINR reported in uplink slot n based on only the CSI-IM or NZP CSI-RS for interference measurement (defined in [4, TS 38.211]) or NZP CSI-RS for channel and interference measurement no later than the CSI reference resource associated with the CSI resource setting. If the upper-level parameter timeRestrictionForInterferenceMeasurements of CSI-ReportConfig is set to 'configured', the UE must derive the interference measurement for calculating the L1-SINR value reported in uplink slot n based on the most recent CSI-IM or NZP CSI-RS opportunity that is not later than the CSI reference resource associated with the CSI resource configuration, or based solely on the NZP CSI-RS for the channel and interference measurement (TS 38.211 [4] defined).[[If the higher layer parameter timeRestrictionForInterferenceMeasurements in CSI-ReportConfig is set to 'configured', the UE shall derive the interference measurements for computing the L1-SINR reported in uplink slot n based on the most recent, no later than the CSI reference resource, occasion of CSI-IM or NZP CSI-RS for interference measurement (defined in [4, TS 38.211]) or NZP CSI-RS for channel and interference measurement associated with the CSI resource setting.]]- When the UE is configured with a CSI-ReportConfig with the higher layer parameter reportQuantity set to 'cri-SINR-Index' or 'ssb-Index-SINR-Index', the UE must report the SSBRI / CRI and L1-SINR pairs together with an index of the UE capability value indicating the maximum number of supported SRS antenna ports. reportQuantity set to 'cri-SINR- Index' or 'ssb-Index-SINR- Index' an index of UE capability value, indicating the maximum supported number of SRS antenna ports, is reported along with the pair of SSBRI / CRI and L1-SINR.]].

[0371] When two types of SSBs are linked for a single CSI report configuration as in Case A3 / B3 / C3 above, the determination of the reference resource of the SS / PBCH actually being measured may be ambiguous depending on the setting of the timeRestrictionForChannelMeasurements parameter during L1-RSRP / SINR reporting as shown in Table 6. According to one embodiment, the reference resource of the SS / PBCH being measured can be determined by one of the following methods. Different methods may be applied depending on whether the combined pattern of Type 1 SSB and Type 2 SSB is regular; for example, if it is a regular pattern, the terminal may apply Alt A1 or Alt B1, and if it is not a regular pattern, the terminal may apply Alt C1.

[0372] (1) Alt A1: Measurement / calculation of L1-RSRP / SINR based on SS / PBCH of all types regardless of Type 1 / 2 SSB

[0373] (2) Alt B1: When Type 2 SSB is activated, measure / calculate L1-RSRP / SINR based on all types of SS / PBCH regardless of type 1 / 2 SSB, and when Type 2 SSB is deactivated, measure / calculate L1-RSRP / SINR based on type 1 SSB.

[0374] Alt B1 can be applied when both types of SSBs exist and measurements are performed and reported using both types of SSBs.

[0375] i) When Type 2 SSB is activated:

[0376] - If the higher layer parameter timeRestrictionForChannelMeasurements in CSI-ReportConfig is set to "notConfigured", the UE shall derive the channel measurements for computing L1-RSRP value reported in uplink slot n based on only the type 1 or type 2 SS / PBCH, no later than the CSI reference resource, (defined in TS 38.211[4]) associated with the CSI resource setting.

[0377] - If the higher layer parameter timeRestrictionForChannelMeasurements in CSI-ReportConfig is set to "Configured", the UE shall derive the channel measurements for computing L1-RSRP reported in uplink slot n based on only the most recent, no later than the CSI reference resource, occasion of type 1 or type 2 SS / PBCH (defined in [4, TS 38.211]) associated with the CSI resource setting.

[0378] - If the higher layer parameter timeRestrictionForChannelMeasurements in CSI-ReportConfig is set to 'notConfigured', the UE shall derive the channel measurements for computing L1-SINR reported in uplink slot n based on only the type 1 or type 2 SSB or NZP CSI-RS, no later than the CSI reference resource, (defined in TS 38.211[4]) associated with the CSI resource setting.

[0379] - If the higher layer parameter timeRestrictionForChannelMeasurements in CSI-ReportConfig is set to 'configured', the UE shall derive the channel measurements for computing L1-SINR reported in uplink slot n based on only the most recent, no later than the CSI reference resource, occasion of type 1 or type 2 SSB or NZP CSI-RS (defined in [4, TS 38.211]) associated with the CSI resource setting.

[0380] ii) When Type 2 SSB is deactivated:

[0381] - If the higher layer parameter timeRestrictionForChannelMeasurements in CSI-ReportConfig is set to "notConfigured", the UE shall derive the channel measurements for computing L1-RSRP value reported in uplink slot n based on only the type 1 SS / PBCH or NZP CSI-RS, no later than the CSI reference resource, (defined in TS 38.211[4]) associated with the CSI resource setting.

[0382] - If the higher layer parameter timeRestrictionForChannelMeasurements in CSI-ReportConfig is set to "Configured", the UE shall derive the channel measurements for computing L1-RSRP reported in uplink slot n based on only the most recent, no later than the CSI reference resource, occasion of type 1 SS / PBCH or NZP CSI-RS (defined in [4, TS 38.211]) associated with the CSI resource setting.

[0383] - If the higher layer parameter timeRestrictionForChannelMeasurements in CSI-ReportConfig is set to 'notConfigured', the UE shall derive the channel measurements for computing L1-SINR reported in uplink slot n based on only the type 1 SSB or NZP CSI-RS, no later than the CSI reference resource, (defined in TS 38.211[4]) associated with the CSI resource setting.

[0384] - If the higher layer parameter timeRestrictionForChannelMeasurements in CSI-ReportConfig is set to 'configured', the UE shall derive the channel measurements for computing L1-SINR reported in uplink slot n based on only the most recent, no later than the CSI reference resource, occasion of type 1 SSB or NZP CSI-RS (defined in [4, TS 38.211]) associated with the CSI resource setting.

[0385] (3) Alt C1: Measure / calculate L1-RSRP / SINR based on type 2 SSB when type 2 SSB is activated, and measure / calculate L1-RSRP / SINR based on type 1 SSB when type 2 SSB is deactivated

[0386] Alt C1 can be applied when a measurement is performed and reported using only one type of SSB (type 2 SSB) even if both type 1 and type 2 SSBs exist. For example, this may be when a SCell transmitting a type 2 SSB is in the activation process, or when a rule is set / defined to use only the type 2 SSB because the type 2 SSB is activated, or when it is set / instructed via RRC / MAC-CE / DCI to use only one of the two types of SSBs.

[0387] i) When Type 2 SSB is activated:

[0388] - If the higher layer parameter timeRestrictionForChannelMeasurements in CSI-ReportConfig is set to "notConfigured", the UE shall derive the channel measurements for computing L1-RSRP value reported in uplink slot n based on only the type 2 SS / PBCH, no later than the CSI reference resource, (defined in TS 38.211[4]) associated with the CSI resource setting.

[0389] - If the higher layer parameter timeRestrictionForChannelMeasurements in CSI-ReportConfig is set to "Configured", the UE shall derive the channel measurements for computing L1-RSRP reported in uplink slot n based on only the most recent, no later than the CSI reference resource, occasion of type 2 SS / PBCH (defined in [4, TS 38.211]) associated with the CSI resource setting.

[0390] - If the higher layer parameter timeRestrictionForChannelMeasurements in CSI-ReportConfig is set to 'notConfigured', the UE shall derive the channel measurements for computing L1-SINR reported in uplink slot n based on only the type 2 SSB or NZP CSI-RS, no later than the CSI reference resource, (defined in TS 38.211[4]) associated with the CSI resource setting.

[0391] - If the higher layer parameter timeRestrictionForChannelMeasurements in CSI-ReportConfig is set to 'configured', the UE shall derive the channel measurements for computing L1-SINR reported in uplink slot n based on only the most recent, no later than the CSI reference resource, occasion of type 2 SSB or NZP CSI-RS (defined in [4, TS 38.211]) associated with the CSI resource setting.

[0392] ii) When Type 2 SSB is deactivated,

[0393] - If the higher layer parameter timeRestrictionForChannelMeasurements in CSI-ReportConfig is set to "notConfigured", the UE shall derive the channel measurements for computing L1-RSRP value reported in uplink slot n based on only the type 1 SS / PBCH or NZP CSI-RS, no later than the CSI reference resource, (defined in TS 38.211[4]) associated with the CSI resource setting.

[0394] - If the higher layer parameter timeRestrictionForChannelMeasurements in CSI-ReportConfig is set to "Configured", the UE shall derive the channel measurements for computing L1-RSRP reported in uplink slot n based on only the most recent, no later than the CSI reference resource, occasion of type 1 SS / PBCH or NZP CSI-RS (defined in [4, TS 38.211]) associated with the CSI resource setting.

[0395] - If the higher layer parameter timeRestrictionForChannelMeasurements in CSI-ReportConfig is set to 'notConfigured', the UE shall derive the channel measurements for computing L1-SINR reported in uplink slot n based on only the type 1 SSB or NZP CSI-RS, no later than the CSI reference resource, (defined in TS 38.211[4]) associated with the CSI resource setting.

[0396] - If the higher layer parameter timeRestrictionForChannelMeasurements in CSI-ReportConfig is set to 'configured', the UE shall derive the channel measurements for computing L1-SINR reported in uplink slot n based on only the most recent, no later than the CSI reference resource, occasion of type 1 SSB or NZP CSI-RS (defined in [4, TS 38.211]) associated with the CSI resource setting.

[0397] Table 7 is a partial excerpt from TS 38.214 v18.4.0.

[0398]

[0399] As shown in Table 7, when a terminal performs aperiodic CSI reporting reported via PUSCH, Z' is the minimum gap between the aperiodic CSI-RS resource and PUSCH. ref It is stipulated that a value is defined, and the terminal can perform a valid CSI report only when the corresponding gap is guaranteed.

[0400] When considering a type 2 SSB that can be activated via MAC-CE or DCI instructions from a base station, the above rule needs to be defined for type 2 SSBs as well. Specifically, in cases where a triggered CSI (sub-)report is linked with a type 2 SSB as in the above Cases A2 / B2 / C2 / A3 / B3 / C3 (and where the said type 2 SSB is activated and performs measurement / reporting through it), CP follows T' after the end of the last symbol of the most recent type 2 SSB in time. proc,CSI =(Z')(2048+144) * k2 -μ * T c The next uplink symbol with its CP starting T' proc,CSI =(Z')(2048+144) * k2 -μ * T c after the end of the last symbol in time of the latest of type 2 SSB) is Z' ref It can be defined as a value.

[0401] Table 8 is a partial excerpt from TS 38.214 v18.4.0.

[0402]

[0403]

[0404] In cases where triggered CSI (sub-)reports and type 1 / 2 SSBs are all linked, as in Case A3 / B3 / C3 above (and measurements / reports are performed through both type 1 / 2 SSBs), a longer delay than the CSI computation delay defined in Table 8 above may be required. For example, when the parameter reportQuantity is set to one of 'ssb-Index-SINR' or 'ssb-Index-SINR-Index', a value greater than (Z1, Z'1) in Table 5.4-2 may be defined. As another example, when the parameter reportQuantity is set to one of 'ssb-Index-RSRP' or 'ssb-Index-RSRP-Index', a value greater than (Z3, Z'3) in Table 5.4-2 may be defined.

[0405] FIG. 19 is a diagram illustrating the operation of a base station and a terminal according to one embodiment. FIG. 19 is an embodiment of at least some of the proposals described above, and the previously described content may be referenced without further separate mention.

[0406] Referring to FIG. 19, the terminal can receive various configuration information from the base station through upper layer signaling (e.g., RRC signaling). The configuration information may include information regarding CSI reporting settings and can be configured through a method such as [Proposal #1]. The CSI reporting settings may be linked with at least one of a type 1 SSB and a type 2 SSB. For convenience, the explanation assumes that the CSI reporting settings are linked with both a type 1 SSB and a type 2 SSB.

[0407] The terminal can receive network signaling for Type 2 SSB activation (1910). The network signaling may include at least one of RRC signaling or MAC CE.

[0408] The terminal can calculate L1 measurement and CPU occupancy by utilizing both type 1 SSB and type 2 SSB based on the activation of the type 2 SSB (1915).

[0409] The terminal can transmit a first CSI report based on L1 measurements for type 1 SSB and type 2 SSB (1920).

[0410] The terminal can receive network signaling for Type 2 SSB deactivation (1925). The network signaling may include at least one of RRC signaling or MAC CE.

[0411] The terminal can calculate L1 measurement and CPU occupancy by utilizing only the type 1 SSB based on the deactivation of the type 2 SSB (1925).

[0412] The terminal can transmit a second CSI report based on an L1 measurement of a type 1 SSB (1930).

[0413] In this way, depending on whether the Type 2 SSB is activated, the terminal can calculate L1 measurement / reporting and CPU occupancy by utilizing both the Type 1 SSB and the Type 2 SSB, or calculate L1 measurement / reporting and CPU occupancy by utilizing only the Type 1 SSB.

[0414] The terminal can minimize unnecessary CPU occupancy by calculating CPU occupancy differently depending on whether Type 2 SSB is activated.

[0415] In the above description, the expressions Type 1 SSB and Type 2 SSB are used for convenience of explanation and may be referred to by other terms. For example, Type 1 SSB may be referred to as an SSB that is transmitted periodically / (semi)permanently, an AO (Always-on) SSB, or simply the 1st SSB. Type 2 SSB may be referred to as an SSB that can be activated / deactivated according to network signaling / terminal requests, an OD (on-demand) SSB, or simply the 2nd SSB. Type 2 SSB may also be transmitted periodically during the actual transmission interval when activated.

[0416] The distinction between the aforementioned proposals 1, 2, and 3 is for convenience of explanation, and each proposal may be implemented individually or in a combined form of at least some of the aforementioned proposals 1, 2, and 3.

[0417] FIG. 20 illustrates the flow of a method performed by a terminal according to one embodiment. FIG. 20 is an implementation example of at least some of the proposals described above, and the previously described content may be referenced unless otherwise separately mentioned.

[0418] Referring to FIG. 20, the terminal can receive configuration information regarding the activation / deactivation of the second SSB (synchronization signal blocks) (2005).

[0419] The terminal can receive CSI (channel state information) report settings (2010). CSI report settings can be received through higher-level signaling, such as RRC signaling.

[0420] The terminal can perform channel measurements on at least one of the first SSBs or the second SSBs that are periodically transmitted based on the above CSI report settings (2015).

[0421] The terminal can transmit a CSI report based on the above channel measurement (2020).

[0422] The above CSI reporting settings may include information regarding at least one SSB for channel measurement among the first SSBs or the second SSBs.

[0423] Based on the activation of the second SSB, the CPU (CSI processing unit) may begin to be occupied starting from the first symbol of the earliest SSB among the first SSBs and the second SSBs.

[0424] Based on the deactivation of the second SSB, the CPU (CSI processing unit) may begin to be occupied starting from the first symbol of the earliest SSB among the first SSBs.

[0425] During the time interval in which the above CPU is occupied, the terminal may not expect the activation / deactivation state of the above second SSB to change.

[0426] Based on the activation of the second SSB, the channel measurement can be performed up to the latest SSB among the first SSBs and the second SSBs that is not later than the CSI reference resource.

[0427] Based on the deactivation of the second SSB, the channel measurement can be performed up to the most recent SSB among the first SSBs that is not later than the CSI reference resource.

[0428] The above CSI reporting settings may include one or more SSB resource lists. The one or more SSB resource lists may include at least one of a first SSB resource list linked only to the first SSBs or a second SSB resource list linked only to the second SSBs.

[0429] The above CSI reporting configuration may include a plurality of sub-configurations. Among the plurality of sub-configurations, the first sub-configuration may be linked to the first SSB resource list, and the second sub-configuration may be linked to the second SSB resource list.

[0430] The above CSI reporting settings may include a list of SSB resources linked to the first SSBs and the second SSBs.

[0431] The above second SSBs may be OD (on-demand) SSBs.

[0432] The above second SSBs can be enabled or disabled based on at least one of RRC (radio resource control) signaling or MAC (medium access control) CE (control element).

[0433] The above channel measurement may be an L1 (layer 1) measurement related to SSB RSRP (reference signal received power) or SSB SINR (signal to interference and noise ratio).

[0434] The above CSI report can be transmitted via PUCCH (physical uplink control channel) or PUSCH (physical uplink shared channel).

[0435] FIG. 21 illustrates the flow of a method performed by a base station according to one embodiment. FIG. 21 is an embodiment of at least some of the proposals described above, and the previously described content may be referenced unless otherwise separately mentioned.

[0436] Referring to FIG. 21, the base station can transmit configuration information for the activation / deactivation of the second SSB (synchronization signal blocks) (2105).

[0437] The base station can transmit CSI (channel state information) report settings to the terminal (2110). The CSI report settings can be transmitted via higher-layer signaling, such as RRC signaling.

[0438] The base station can receive a CSI report from the terminal regarding channel measurement for at least one of the first SSBs or the second SSBs that are transmitted periodically (2115).

[0439] The above CSI reporting settings may include information regarding at least one SSB for channel measurement among the first SSBs or the second SSBs.

[0440] Based on the activation of the second SSB, the base station can determine that the terminal's CPU (CSI processing unit) begins to be occupied starting from the first symbol of the earliest SSB among the first SSBs and the second SSBs.

[0441] Based on the deactivation of the second SSB, the base station can determine that the terminal's CPU (CSI processing unit) begins to be occupied starting from the first symbol of the earliest SSB among the first SSBs.

[0442] During the time interval in which the above CPU is occupied, the base station may not transmit network signaling to the terminal that changes the activation / deactivation state of the above second SSB.

[0443] Based on the activation of the second SSB, the base station can determine that the channel measurement was performed up to the latest SSB among the first SSBs and the second SSBs, which is not later than the CSI reference resource.

[0444] Based on the deactivation of the second SSB, the base station can determine that the channel measurement was performed up to the most recent SSB among the first SSBs that is not later than the CSI reference resource.

[0445] The above CSI reporting settings may include one or more SSB resource lists. The one or more SSB resource lists may include at least one of a first SSB resource list linked only to the first SSBs or a second SSB resource list linked only to the second SSBs.

[0446] The above CSI reporting configuration may include a plurality of sub-configurations. Among the plurality of sub-configurations, the first sub-configuration may be linked to the first SSB resource list, and the second sub-configuration may be linked to the second SSB resource list.

[0447] The above CSI reporting settings may include a list of SSB resources linked to the first SSBs and the second SSBs.

[0448] The above second SSBs may be OD (on-demand) SSBs.

[0449] The above second SSBs can be enabled or disabled based on at least one of RRC (radio resource control) signaling or MAC (medium access control) CE (control element).

[0450] The above channel measurement may be an L1 (layer 1) measurement related to SSB RSRP (reference signal received power) or SSB SINR (signal to interference and noise ratio).

[0451] The above CSI report can be received via PUCCH (physical uplink control channel) or PUSCH (physical uplink shared channel).

[0452] The embodiments described above are combinations of the components and features of the present disclosure in a specific form. Each component or feature should be considered optional unless otherwise explicitly stated. Each component or feature may be implemented in a form not combined with other components or features. Additionally, it is possible to construct embodiments of the present disclosure by combining some components and / or features. The order of operations described in the embodiments of the present disclosure may be changed. Some components or features of one embodiment may be included in another embodiment, or may be replaced with corresponding components or features of another embodiment. It is obvious that embodiments may be constructed by combining claims that are not explicitly related in the claims, or that they may be included as new claims by amendment after filing.

[0453] It is obvious to those skilled in the art that the present disclosure may be embodied in other specific forms without departing from the features of the present disclosure. Accordingly, the foregoing detailed description should not be interpreted restrictively in all respects and should be considered illustrative. The scope of the present disclosure shall be determined by a reasonable interpretation of the appended claims, and all modifications within the equivalent scope of the present disclosure are included within the scope of the present disclosure.

[0454] The present disclosure may be used in a terminal, base station, or other equipment of a wireless mobile communication system.

Claims

1. In a method performed by a terminal, Receive configuration information regarding the activation / deactivation of the second SSB (synchronization signal blocks); Receive CSI (channel state information) report settings; Performing channel measurements on at least one of the first SSBs or the second SSBs that are periodically transmitted based on the above CSI reporting settings; and Includes transmitting a CSI report based on the above channel measurement, A method in which the above CSI reporting setting includes information for at least one SSB for channel measurement among the first SSBs or the second SSBs.

2. In Paragraph 1, A method in which, based on the activation of the second SSB, the CPU (CSI processing unit) begins to be occupied starting from the first symbol of the earliest SSB among the first SSBs and the second SSBs.

3. In Paragraph 1, A method in which, based on the deactivation of the second SSB, the CPU (CSI processing unit) begins to be occupied from the first symbol of the earliest SSB among the first SSBs.

4. In Paragraph 2 or 3, A method in which, during the time interval in which the above CPU is occupied, the terminal does not expect the activation / deactivation state of the above second SSB to change.

5. In Paragraph 1, A method in which, based on the activation of the second SSB, the channel measurement is performed up to the latest SSB among the first SSBs and the second SSBs that is not later than the CSI reference resource.

6. In Paragraph 1, A method in which, based on the deactivation of the second SSB, the channel measurement is performed up to the most recent SSB among the first SSBs that is not later than the CSI reference resource.

7. In Paragraph 1, The above CSI reporting settings include one or more SSB resource lists, and A method in which the above one or more SSB resource lists include at least one of a first SSB resource list linked only to the first SSBs or a second SSB resource list linked only to the second SSBs.

8. In Paragraph 7, The above CSI reporting configuration includes a plurality of sub-configurations, and A method in which, among the plurality of sub-settings above, the first sub-setting is linked to the first SSB resource list and the second sub-setting is linked to the second SSB resource list.

9. In Paragraph 1, A method in which the above CSI reporting settings include a list of SSB resources linked to the first SSBs and the second SSBs.

10. In Paragraph 1, The above second SSBs are OD (on-demand) SSBs, and The above second SSBs are enabled or disabled based on at least one of RRC (radio resource control) signaling or MAC (medium access control) CE (control element), and The above channel measurement is an L1 (layer 1) measurement related to SSB RSRP (reference signal received power) or SSB SINR (signal to interference and noise ratio), and A method in which the above CSI report is transmitted via PUCCH (physical uplink control channel) or PUSCH (physical uplink shared channel).

11. A computer-readable non-transitory recording medium storing a program for performing the method described in claim 1.

12. Regarding the device, At least one processor; and It includes at least one memory configured to store instructions that cause the at least one processor to perform operations by being executed by the at least one processor, and The operations of the above processor are, Receive configuration information regarding the activation / deactivation of the second SSB (synchronization signal blocks); Receive CSI (channel state information) report settings; Performing channel measurements on at least one of the first SSBs or the second SSBs that are periodically transmitted based on the above CSI reporting settings; and Includes transmitting a CSI report based on the above channel measurement, The above CSI reporting setting is a device comprising information for at least one SSB for channel measurement among the first SSBs or the second SSBs.

13. In Paragraph 12, The above device is a device that is a terminal further comprising a transceiver or a processing device configured to control the above.

14. In a method performed by a base station, Transmit configuration information for the activation / deactivation of the second SSB (synchronization signal blocks); Transmit CSI (channel state information) report settings to the terminal; and It includes receiving from the terminal a CSI report related to channel measurement for at least one of the first SSBs or the second SSBs that are periodically transmitted, and A method in which the above CSI reporting setting includes information for at least one SSB for channel measurement among the first SSBs or the second SSBs.

15. Regarding base stations, At least one processor; and It includes at least one memory configured to store instructions that cause the at least one processor to perform operations by being executed by the at least one processor, and The operations of the above processor are, Transmit configuration information for the activation / deactivation of the second SSB (synchronization signal blocks); Transmit CSI (channel state information) report settings to the terminal; and It includes receiving from the terminal a CSI report related to channel measurement for at least one of the first SSBs or the second SSBs that are periodically transmitted, and The above CSI reporting setting is a base station that includes information for at least one SSB for channel measurement among the first SSBs or the second SSBs.

Images