Method and apparatus for reporting channel state information in a wireless communication system

Abstract

A method of a terminal according to one embodiment of the present disclosure may include receiving operation mode configuration information for a first operation mode and a second operation mode from a base station; receiving resource allocation information for reporting CSI measured based on the operation mode configuration information from the base station; determining a CSI reference resource based on a preset CSI generation criterion; measuring a first CSI received from the base station based on the operation mode configuration information; confirming validity of the measured first CSI; and transmitting a CSI report to the base station reflecting valid CSI measurements based on the confirmation.

Description

[Technical Field]

[0001] TECHNICAL FIELD The present disclosure relates to wireless communication technologies, and more particularly to techniques for reporting channel conditions in wireless communication systems. [Background technology]

[0002] Radio resources in a mobile communication system can use variable transmission modes to handle a variety of situations, such as integrated access and backhaul (IAB) node operation, multiple transmission and reception point (multi-TRP) operation, and in-band or out-band full duplex communication operation.

[0003] Meanwhile, the transceiver (or base station or terminal) of the mobile communication system can operate with differences in time / frequency / space / power resources for wireless communication, such as using different numbers of antennas, antenna shapes, and transmission powers depending on each transmission mode (or according to instructions from the base station considering each transmission mode), in order to improve wireless communication quality. In 5G NR to 6G communications, there is an emerging need to dynamically change such various transmission modes in order to enhance wireless communication quality / capacity while ensuring robustness and resilience in various communication environments.

[0004] On the other hand, even in the case of a terminal to which a high proportion of uplink transmission time is allocated in the full-duplex communication system, there may be cases where it is necessary to receive downlink signals such as a downlink control channel in part of the corresponding uplink transmission section for various purposes such as cell-specific downlink reception, uplink-based channel estimation, and uplink beam change. Summary of the Invention [Problem to be solved by the invention]

[0005] In order to solve the above-mentioned needs, an object of the present disclosure is to provide a method for measuring and reporting channel state information to efficiently support dynamically variable transmission modes. [Means for solving the problem]

[0006] A method for a terminal according to the present disclosure to achieve the above object may include receiving operation mode configuration information for a first operation mode and a second operation mode from a base station; receiving resource allocation information for reporting channel state information (CSI) measured based on the operation mode configuration information from the base station; determining a CSI reference resource based on a preset CSI generation criterion; measuring a first CSI received from the base station based on the operation mode configuration information; confirming validity of the measured first CSI; and transmitting a CSI report reflecting valid CSI measurements to the base station based on the confirmation,

[0007] The valid CSI information may be a case where the operation mode when measuring the first CSI and the operation mode when reporting the CSI based on the CSI reference resource are the same.

[0008] The first operating mode may be one of sub-band full duplex (SBFD) or full-duplex (FD), and the second operating mode may be one of time-domain duplex (TDD) or frequency-domain duplex (FDD).

[0009] In the first operating mode, the first CSI may be measured on each of one or more subbands.

[0010] When reporting the CSI, if only some of the valid CSI measurements can be reported, the valid CSI measurements to be transmitted can be determined based on a predetermined priority.

[0011] The method may further include receiving first configuration information, in which at least one of a channel measurement resource (CMR) or an interference measurement resource (IMR) is configured, from the base station,

[0012] If the first configuration information indicates CMR, the first CSI may be composed of NZP (non-zero-power) CSI-reference signal (RS), and if the first configuration information indicates IMR, the first CSI may be composed of one of NZP CSI-RS or ZP (zero-power) CSI-RS.

[0013] The method may further include not reflecting invalid CSI measurements in the CSI report based on the confirmation,

[0014] The invalid CSI measurement value may be a case where the operation mode at the time of measurement of at least one of the CMR or IMR is different from the operation mode at the time of reporting the CSI based on the CSI reference resource.

[0015] At least one of the CMR or IMR may be received periodically, semi-persistently, or aperiodically, and the CSI report may be transmitted to the base station periodically, semi-persistently, or aperiodically.

[0016] The transport block size (TBS) for the CSI report may be determined based on at least one of a subband frequency resource or a time resource of an operation mode applied to the CSI reference resource.

[0017] A method of a base station according to an embodiment of the present disclosure may include transmitting operation mode configuration information for a first operation mode and a second operation mode to a terminal; transmitting resource allocation information for receiving a channel state information (CSI) report measured based on the operation mode configuration information to the terminal; transmitting a first CSI and a CSI reference resource to the terminal based on the operation mode configuration information; and receiving a CSI report from the terminal based on the resource allocation information,

[0018] The first operating mode may be one of sub-band full duplex (SBFD) or full-duplex (FD), and the second operating mode may be one of time-domain duplex (TDD) or frequency-domain duplex (TDD).

[0019] In the first operating mode, the first CSI may be transmitted on each of one or more subbands.

[0020] The method may further include transmitting first configuration information, in which at least one of a channel measurement resource (CMR) or an interference measurement resource (IMR) is configured, to the terminal,

[0021] If the first configuration information indicates CMR, each of the first CSIs may be composed of a non-zero-power (NZP) CSI-reference signal (RS), and if the first configuration information indicates IMR, each of the first CSIs may be composed of one of a non-zero-power (NZP) CSI-RS or a zero-power (ZP) CSI-RS.

[0022] At least one of the CMR or IMR may be transmitted to the terminal periodically, semi-statically, or aperiodically, and the CSI report may be received from the terminal periodically, semi-persistently, or aperiodically.

[0023] A terminal according to an embodiment of the present disclosure includes a processor, and the processor is configured to:

[0024] receiving, from a base station, operation mode setting information for a first operation mode and a second operation mode; receiving, from the base station, resource allocation information for reporting channel state information (CSI) measured based on the operation mode setting information; determining a CSI reference resource based on a predetermined CSI generation criterion; measuring a first CSI received from the base station based on the operation mode setting information; confirming validity of the measured first CSI; and causing a CSI report reflecting valid CSI measurements to be transmitted to the base station based on the confirmation,

[0025] The valid CSI information may be a case where the operation mode when measuring the first CSI and the operation mode when reporting the CSI based on the CSI reference resource are the same.

[0026] The first operating mode may be one of sub-band full duplex (SBFD) or full-duplex (FD), and the second operating mode may be one of time-domain duplex (TDD) or frequency-domain duplex (FDD).

[0027] The processor may further cause the terminal to measure the first CSI on each of one or more subbands when the terminal is in the first operating mode.

[0028] The processor may further cause the terminal to determine valid CSI measurement values ​​to transmit based on a predetermined priority when the terminal is only able to report a portion of the valid CSI measurement values ​​during the CSI reporting.

[0029] The processor may further cause the terminal to receive first configuration information, in which at least one of a channel measurement resource (CMR) or an interference measurement resource (IMR) is configured, from the base station;

[0030] If the first configuration information indicates CMR, each of the first CSIs may be composed of a non-zero-power (NZP) CSI-reference signal (RS), and if the first configuration information indicates IMR, each of the first CSIs may be composed of one of a non-zero-power (NZP) CSI-RS or a zero-power (ZP) CSI-RS.

[0031] The processor may further cause the terminal not to reflect invalid CSI measurements in the CSI report based on the confirmation;

[0032] The invalid CSI measurement may be a case where the operation mode at the time of measurement of at least one of the CRM or IMR is different from the operation mode at the time of reporting the CSI based on the CSI reference resource.

[0033] The processor may further cause the terminal to receive at least one of the CMR or IMR periodically, semi-statically, or aperiodically, and to transmit the CSI report to the base station periodically, semi-persistently, or aperiodically.

[0034] The transport block size (TBS) for the CSI report may be determined based on at least one of a subband frequency resource or a time resource of an operation mode applied to the CSI reference resource. [Effects of the Invention]

[0035] According to a method and apparatus according to an embodiment of the present disclosure, when multiple operation modes are available, resources for each mode can be configured. Furthermore, when the resources for each mode are variable, the base station provides configuration information for valid channel state reporting to the terminal, so that the terminal can report valid channel state information to the base station. Therefore, the base station can confirm accurate channel states through valid channel state reporting. Based on this, wireless communication capacity between the terminal and the base station can be effectively expanded. [Brief explanation of the drawings]

[0036] [Figure 1] FIG. 1 is a conceptual diagram illustrating one embodiment of an air interface protocol structure in a communication system. [Figure 2] 1 is a conceptual diagram illustrating one embodiment of time resources over which wireless signals are transmitted in a communication system. [Figure 3]FIG. 10 is a conceptual diagram illustrating the time difference between the reception timing of the #i-th downlink frame and the transmission timing of the #i-th uplink frame in an embodiment of a communication system. [Figure 4] 1 is a conceptual diagram illustrating one embodiment of a time / frequency resource grid for a communication system. [Figure 5] FIG. 1 is a conceptual diagram illustrating one embodiment of an SS / PBCH block of a communication system. [Figure 6] 1 is a flow chart illustrating one embodiment of a random access procedure in a communication system. [Figure 7] FIG. 1 is a conceptual diagram illustrating a first embodiment of SSB-RO interaction by RACH setup in a communication system. [Figure 8] FIG. 10 is a conceptual diagram illustrating a second embodiment of SSB-RO interaction through RACH setup in a communication system. [Figure 9] 1 is a conceptual diagram illustrating an embodiment of a QCL information transfer process through TCI state setting and indication in a communication system. [Figure 10] 1 is a conceptual diagram illustrating one embodiment of a TCI state activation / deactivation MAC CE structure in a communication system. [Figure 11] FIG. 1 is a conceptual diagram illustrating one embodiment of a TCI status indication MAC CE in a communication system. [Figure 12] FIG. 1 is a conceptual diagram showing a slot configuration according to a slot format in a communication system. [Figure 13] 1 is a flowchart illustrating an embodiment of a terminal capability reporting procedure in a communication system. [Figure 14] 1 is a block diagram illustrating an embodiment of a separation structure of a central unit (CU) and distributed units (DU) in a communication system. [Figure 15] 1 is a flowchart illustrating a first embodiment of a resource management method for an IAB node in a communication system. [Figure 16] 1 is a flowchart illustrating an embodiment of a terminal capability reporting procedure in a communication system. [Figure 17a]1 is a conceptual diagram illustrating a user plane protocol stack structure in a communication system. [Figure 17b] FIG. 1 is a conceptual diagram illustrating a control plane protocol stack structure in a communication system. [Figure 18a] 1 is a conceptual diagram illustrating a user plane protocol structure for carrier association (CA) in a base station of a communication system. [Figure 18b] 1 is a conceptual diagram illustrating a user plane protocol structure for dual connection (DC) in a base station of a communication system. [Figure 19a] FIG. 10 is a conceptual diagram for explaining a case where both the MT and DU of an IAB node are in transmission mode. [Figure 19b] FIG. 10 is a conceptual diagram for explaining a case where both the MT and DU of an IAB node are in reception mode. [Figure 19c] FIG. 10 is a conceptual diagram for explaining a case where the MT of the IAB node is in a transmission mode and the DU is in a reception mode. [Figure 19d] FIG. 10 is a conceptual diagram for explaining a case where the MT of the IAB node is in a receiving mode and the DU is in a transmitting mode. [Figure 20] 1 is a conceptual diagram illustrating a method in which a base station allocates one or more operation modes to a terminal within a resource section. [Figure 21] 1 is a conceptual diagram illustrating a method in which a base station allocates resources to a terminal using time-frequency resources according to an operation mode. [Figure 22] 1 is a conceptual diagram illustrating a method in which a base station allocates resources to a terminal according to an operation mode using frequency-slots (or symbols). [Figure 23] FIG. 10 is a conceptual diagram illustrating CSI reporting for each operation mode according to an embodiment of the present disclosure. [Figure 24] 1 is a flowchart illustrating CSI resource configuration and reporting configuration, CSI request, operation mode configuration / activation / indication, and CSI reporting according to an embodiment of the present disclosure. [Figure 25]10 is a flowchart illustrating a CSI resource configuration and reporting configuration, an operation mode configuration / activation / indication, and a CSI reporting operation depending on whether a specific condition is satisfied, according to an embodiment of the present disclosure. [Figure 26] FIG. 10 is a conceptual diagram illustrating CSI reporting in a first operation mode according to an embodiment of the present disclosure. [Figure 27] FIG. 10 is a conceptual diagram illustrating a case where CSI is reported in an environment where a first operation mode and a second operation mode coexist according to an embodiment of the present disclosure. [Figure 28] FIG. 10 is a conceptual diagram for explaining a subband CSI reporting operation according to one embodiment of the present disclosure. [Figure 29] FIG. 2 is a block diagram of a base station according to an embodiment of the present disclosure. [Figure 30] FIG. 2 is a block diagram of a terminal according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0037] While the present disclosure can be modified in various ways and can have various embodiments, specific embodiments will be illustrated in the drawings and described in detail, but it should be understood that this is not intended to limit the disclosure to the specific embodiments, and that all modifications, equivalents, and alternatives within the spirit and technical scope of the present disclosure are included.

[0038] Terms such as "first," "second," etc. may be used to describe various components, but the components should not be limited by these terms. These terms are used only to distinguish one component from another. For example, a first component may be designated as a second component, and similarly, a second component may be designated as a first component, without departing from the scope of the present disclosure. The term "and / or" includes a combination of multiple associated listed items or any of multiple associated listed items.

[0039] In this disclosure, "at least one of A and B" may mean "at least one of A or B" or "at least one of a combination of one or more of A and B." Also, in this disclosure, "one or more of A and B" may mean "one or more of A or B" or "one or more of a combination of one or more of A and B."

[0040] In this disclosure, (re)transmission may mean "transmission," "retransmission," or "transmission and retransmission," (re)configuration may mean "configuration," "reconfiguration," or "configuration and reconfiguration," (re)connection may mean "connection," "reconnection," or "connection and reconnection," and (re)connection may mean "connection," "reconnection," or "connection and reconnection."

[0041] When a component is said to be "coupled" or "connected" to another component, it should be understood that it may be directly coupled or connected to the other component, but that there may be other components in between. Conversely, when a component is said to be "directly coupled" or "directly connected" to another component, it should be understood that there are no other components in between.

[0042] The terms used in this disclosure are merely used to describe specific embodiments and are not intended to limit the present disclosure. Singular expressions include plural expressions unless the context clearly dictates otherwise. In this disclosure, terms such as "comprise" or "have" are intended to specify the presence of features, numbers, steps, operations, components, parts, or combinations thereof described in the specification, and should be understood not to preclude the possibility of the presence or addition of one or more other features, numbers, steps, operations, components, parts, or combinations thereof.

[0043] Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains. Terms as defined in commonly used dictionaries should be interpreted as having a meaning consistent with the meaning they have in the context of the relevant art, and should not be interpreted in an idealized or overly formal sense unless expressly defined in this disclosure.

[0044] Hereinafter, preferred embodiments of the present disclosure will be described in more detail with reference to the accompanying drawings. In describing the present disclosure, the same reference numerals will be used to refer to the same components in the drawings, and redundant descriptions of the same components will be omitted, in order to facilitate overall understanding.

[0045] A communication network to which an embodiment of the present disclosure is applied will now be described. The communication network to which an embodiment of the present disclosure is applied is not limited to the content described below, and the embodiment of the present disclosure may be applied to various communication networks. Here, the term "communication network" may be used interchangeably with the term "communication system." The term "communication network" may refer to a wireless communication network, and the term "communication system" may refer to a wireless communication system.

[0046] In the present disclosure, "configuring an operation (e.g., a transmission operation)" may mean that "configuration information (e.g., information elements, parameters) for the corresponding operation" and / or "information instructing the performance of the corresponding operation" is signaled. "Configuring an information element (e.g., a parameter)" may mean that the corresponding information element is signaled. In the present disclosure, the signaling may be at least one of system information (SI) signaling (e.g., transmission of a system information block (SIB) and / or a master information block (MIB)), RRC signaling (e.g., transmission of RRC parameters and / or higher layer parameters), MAC control element (CE) signaling, or PHY signaling (e.g., transmission of downlink control information (DCI), uplink control information (UCI), and / or sidelink control information (SCI)).

[0047] Throughout the specification, a network may include, for example, wireless internet such as WiFi (wireless fidelity), mobile internet such as WiBro (wireless broadband internet) or WiMax (world interoperability for microwave access), 2G mobile communication networks such as GSM (global system for mobile communication) or CDMA (code division multiple access), 3G mobile communication networks such as WCDMA (wideband code division multiple access) or CDMA2000, 3.5G mobile communication networks such as HSDPA (high speed downlink packet access) or HSUPA (high speed uplink packet access), 4G mobile communication networks such as LTE (long term evolution) networks or LTE-Advanced networks, 5G mobile communication networks, B5G mobile communication networks (6G mobile communication networks, etc.), etc.

[0048] Throughout this specification, the term "terminal" may refer to a mobile station, mobile terminal, subscriber station, portable subscriber station, user equipment, access terminal, etc., and may include all or some of the functionality of a terminal, mobile station, mobile terminal, subscriber station, portable subscriber station, user equipment, access terminal, etc.

[0049] Here, devices that can communicate with the terminal include desktop computers, laptop computers, tablet PCs, wireless phones, mobile phones, smartphones, smart watches, smart glasses, e-book readers, portable multimedia players (PMPs), portable game consoles, navigation devices, digital cameras, digital multimedia broadcasting (DMB) players, digital audio recorders, digital audio players, digital picture recorders, digital picture players, digital video recorders, digital video players, and the like.

[0050] Throughout this specification, the term "base station" may refer to an access point, radio access station, Node B, evolved Node B, base transceiver station, MMR (mobile multihop relay)-BS, etc., and may include all or some of the functions of a base station, access point, radio access station, Node B, eNodeB, base transceiver station, MMR-BS, etc.

[0051] Hereinafter, preferred embodiments of the present disclosure will be described in more detail with reference to the accompanying drawings. In describing the present disclosure, the same reference numerals will be used to refer to the same components in the drawings, and redundant descriptions of the same components will be omitted, in order to facilitate overall understanding.

[0052] In particular, the present disclosure described below may include a method for determining the transmission direction of an uplink and / or a downlink of a terminal in a full-duplex communication system.

[0053] FIG. 1 is a conceptual diagram illustrating one embodiment of a radio interface protocol architecture in a communication system.

[0054] 1, an embodiment of a radio interface protocol structure 100 of a communication system may be configured to include a radio resource control (RRC) layer 110, a medium access control (MAC) layer 120, a physical (PHY) layer 130, etc. The embodiment of the radio interface protocol structure 100 shown in FIG. 1 may correspond to various interface embodiments, such as an interface between a terminal and a base station, an interface between an IAB-node distributed unit (DU) and an IAB-node mobile terminal (MT) of an integrated access backhaul (IAB) network, an interface between an IAB-node DU and a lower node, an interface between an IAB-node MT and an upper node, and an interface between multiple terminals.

[0055] The RRC layer 110, the MAC layer 120, and the like may be arranged above the PHY layer 130 near the PHY layer 130. For example, the MAC layer 120 may be arranged above the PHY layer 130. The RRC layer 110 may be arranged above the MAC layer 120.

[0056] The MAC layer 120 may be connected to a higher layer (e.g., the RRC layer 110) through a logical channel 115. The PHY layer 130 may be connected to a higher MAC layer 120 through a transport channel 125. The PHY layer 130 may exchange control information or measurement information 150 with the RRC layer 110.

[0057] The PHY layer 130 may be referred to as "layer 1" or "L1." The MAC layer 120 may be referred to as "layer 2" or "L2." The RRC layer 110 may be referred to as "layer 3" or "L3." The RRC layer 110 and the MAC layer 120 may be referred to as "higher layers."

[0058] In this specification, "L1 signaling" may refer to signaling such as downlink control information (DCI) transmitted through a physical downlink control channel (PDCCH), which is a PHY layer 130 channel, uplink control information (UCI) transmitted through a physical uplink control channel (PUCCH), and sidelink control information (SCI) transmitted through a physical sidelink control channel (PSCCH). Similarly, in this specification, "higher layer signaling" may include L2 signaling transmitted through a MAC control element (CE), L3 signaling transmitted through RRC signaling, etc.

[0059] In particular, although omitted in Figure 1 for the sake of convenience in this disclosure, information that may be included in interfaces (e.g., F1, NG interface, etc.) between base stations or between base station components such as distributed units (DUs) and central units (CUs) may also be commonly referred to as upper layer signaling, along with L2 signaling or L3 signaling.

[0060] In communication systems that use 5G, one or more of the numerologies in Table 1 can be used for various purposes, such as inter-carrier interference (ICI) reduction due to frequency band characteristics and latency reduction due to service characteristics.

[0061] [Table 1]

[0062] Table 1 is merely an example for convenience of explanation, and examples of numerologies used in a communication system may not be limited thereto. Each numerology μ may correspond to information on subcarrier spacing (SCS) and cyclic prefix (CP). The terminal can check the numerology μ and CP value applied to the downlink bandwidth part or uplink bandwidth part based on the higher layer parameters 'subcarrierSpacing', 'cyclicPrefix', etc.

[0063] FIG. 2 is a conceptual diagram illustrating one embodiment of time resources over which wireless signals are transmitted in a communication system.

[0064] JPEG2026506518000003.jpg73161

[0065] [Table 2]

[0066] [Table 3]

[0067] In a 5G NR communication system, a frame 230 may have a length of 10 ms, and a subframe 220 may have a length of 1 ms. Each frame 230 may be divided into two half-frames having the same length, where the first half-frame (half-frame 0) may be composed of subframes 220 numbered 0 to 4, and the second half-frame (half-frame 1) may be composed of subframes 220 numbered 5 to 9. One carrier may have a set of frames for the uplink (uplink frames) and a set of frames for the downlink (downlink frames).

[0068] FIG. 3 is a conceptual diagram illustrating the time difference between the reception timing of the #i-th downlink frame and the transmission timing of the #i-th uplink frame in one embodiment of the communication system.

[0069] JPEG2026506518000006.jpg87161

[0070]

number

[0071] JPEG2026506518000008.jpg22161

[0072] FIG. 4 is a conceptual diagram illustrating one embodiment of a time / frequency resource grid for a communication system.

[0073] JPEG2026506518000009.jpg74161

[0074] JPEG2026506518000010.jpg44161

[0075] JPEG2026506518000011.jpg37161

[0076]

number

[0077]

number

[0078] Up to four downlink bandwidth portions can be configured for one UE within one component carrier (CC), and only one downlink bandwidth portion can be activated at a time. The UE cannot receive PDSCH (physical downlink shared channel), PDCCH (physical downlink control channel), CSI-RS (channel state information reference signal), etc., except for the activated bandwidth portion.

[0079] Up to four uplink bandwidth portions can be configured for one UE within one component carrier, and only one uplink bandwidth portion can be activated at a time. The UE may not transmit a physical uplink shared channel (PUSCH), a physical uplink control channel (PUCCH), a sounding reference signal (SRS), etc., other than the activated bandwidth portion.

[0080] FIG. 5 is a conceptual diagram illustrating one embodiment of a synchronization signal and physical broadcast channel block (SS / PBCH block, SSB) of a communication system.

[0081] Referring to FIG. 5, the SS / PBCH block 500 of the communication system may be composed of a primary synchronization signal (PSS) transmitted on the middle 127 subcarriers of the first OFDM symbol, a secondary synchronization signal (SSS) transmitted on the middle 127 subcarriers of the third OFDM symbol, and a physical broadcast channel (PBCH) transmitted on the second, third, and fourth OFDM symbols. The PBCH, which occupies the widest bandwidth, may be transmitted over 20 RBs, which may be 3.6 MHz based on a 15 kHz SCS. A base station transmits one SSB using the same beam. If the number of base station antennas increases or multiple beams need to be operated, such as applying one or more analog beams for high frequency support, multiple beam operation can be supported by transmitting multiple SSBs. Here, the term "beam" may be expressed by various terms, such as transmit precoding or spatial transmission filter, in actual applications, but may be referred to as a beam to avoid ambiguity.

[0082] For example, a base station may transmit multiple SSBs 530, 540, 550, and 560 to represent multiple beams (e.g., beam #1, beam #2, beam #3, and beam #4). In this case, multiple SSBs 530, 540, 550, and 560 may be transmitted in one slot according to a predetermined pattern for each numerology. SSBs 530, 540, 550, and 560 to which different beams are applied may be included in an SS burst 520 and grouped into one set. A terminal may assume a half-frame window having a length of 5 ms when monitoring SSBs. An SS burst set 515 configured by higher layer signaling within a half frame may include one or more SS bursts 520. When performing initial access (IA), if the RRC configuration value is unknown or unavailable, the terminal may receive or measure SSBs by assuming a period of the SS burst set 510 of 20 ms. As an example, the terminal can receive SSB by referring to SSB setting information that is the same as or similar to that shown in Tables 4 and 5.

[0083] [Table 4]

[0084] [Table 5]

[0085] FIG. 6 is a flow chart illustrating one embodiment of a random access procedure in a communication system.

[0086] 6, in a random access procedure of a communication system 600, a terminal 615 may transmit a physical random access channel (PRACH) preamble, which may be referred to as Msg1, to a base station 610 (S620). Through the transmission of the PRACH preamble, a random access-radio network temporary identifier (RA-RNTI) may be determined. In this case, the RA-RNTI may be calculated using Equation 4.

[0087]

number

[0088] JPEG2026506518000017.jpg42161

[0089] Thus, before the terminal transmits the PRACH preamble to the base station, the terminal may acquire system information through PBCH reception or may have some of the following information through RRC signaling reception, etc.

[0090] -PRACH preamble format

[0091] -Time / frequency resource information for RACH (random access channel) transmission

[0092] -index to logical root sequence table

[0093] -Cyclic Shift (NCS)

[0094] - Set type (unrestricted, restricted set A, restricted set B)

[0095] Referring again to FIG. 6, in the second procedure, the base station may provide a random access response (RAR) to the terminal, which may be referred to as Msg2 (S630). Specifically, when the base station receives a PRACH preamble from the terminal in step S620, it may calculate the RA-RNTI based on equation (4) and use the RA-RNTI for scrambling to transmit DCI. The terminal may monitor the PDCCH scrambled with the RA-RNTI in an interval included in the RACH response window set in an upper layer within the Type 1 PDCCH common search space (CSS). The terminal may receive the PDCCH (or DCI transmitted from the base station over the PDCCH) and decode the received PDCCH (or DCI). If the terminal successfully decodes the PDCCH (or DCI), it may decode the PDSCH including the RAR data transmitted from the base station in step S630. If the terminal successfully decodes the RAR, the terminal can check whether the RAPID (RA preamble identifier) ​​in the RAR matches the RAPID previously assigned to the terminal.

[0096] In the third step, the terminal may transmit a PUSCH to the base station, which may be referred to as Msg3 (S640). To this end, the terminal may determine whether to apply transform precoding to PUSCH transmission (i.e., transmit using discrete Fourier transform (DFT)-s-OFDM) or not (i.e., transmit using OFDM) based on higher layer parameters (e.g., msg3-transformPrecoding). In addition, the terminal may determine the SCS to use for PUSCH transmission based on higher layer parameters (e.g., msg3-scs). In this case, the PUSCH of Msg3 may be transmitted through the serving cell from which the PRACH is transmitted.

[0097] As a fourth procedure, the base station may transmit a contention resolution message to the terminal, which may be referred to as Msg4 (S650). The terminal may start a timer to receive the contention resolution message and may monitor the PDCCH scrambled with the temporary cell-RNTI (TC-RNTI) in the Type 1 PDCCH CSS until the timer expires. If the terminal successfully decodes the PDCCH, it may decode the PDSCH including the MAC CE and set the TC-RNTI to the Cell-RNTI (C-RNTI). After successfully decoding Msg4, the terminal may report a hybrid automatic repeat request (HARQ) positive-acknowledgement (ACK) for this to the base station and may report the success or failure of the RACH procedure to the base station (S660).

[0098] The aforementioned RACH occasion (RO) may refer to time and frequency resources specified for receiving the RACH preamble, which the UE can use for PRACH transmission. As described above, in 5G NR, multiple SSBs may be associated with different beams for multi-beam operation. The UE can measure multiple SSBs and select the optimal SSB (i.e., optimal beam) using one of various methods, such as reference signal received power (RSRP), reference signal received quality (RSRQ), signal-to-noise ratio (SNR), or signal-to-noise / interference ratio (SNIR). The UE can then determine the beam (i.e., (TX) spatial filter) to use for PRACH transmission based on the beam (i.e., (RX) spatial filter) used when receiving the optimal SSB. In this case, a relationship between a specific SSB and a specific RO may be established so that the base station or network can determine which SSB (beam) the terminal has selected. Through this relationship, the base station can determine which SSB (beam) the terminal has selected based on which RO the terminal has transmitted the PRACH. For example, the relationship between the SSB and the RO may be determined by referring to the same or similar upper layer configuration as shown in Tables 6 and 7.

[0099] [Table 6]

[0100] [Table 7]

[0101] FIG. 7 is a conceptual diagram illustrating a first embodiment of SSB-RO linkage by RACH (Random Access Channel) setup in a communication system.

[0102] 7, in an SSB-RO mapping relationship according to RACH configuration, N SSBs 710-1 to 710-n that are separated from one another in time on a specific frequency band may be mapped one-to-one to N ROs 720-1 to 710-n that are separated from one another in time. For example, if the upper layer parameter msg1-FDM is set to 1 (msg1-FDM=one) and the upper layer parameter ssb-perRACH-OccasionAndCB-PreamblesPerSSB is set to 1 (ssb-perRACH-OccasionAndCB-PreamblesPerSSB=one), N different SSBs 710-1 to 710-n may be mapped one-to-one to N different ROs 720-1 to 720-n.

[0103] FIG. 8 is a conceptual diagram illustrating a second embodiment of SSB-RO interaction by RACH setup in a communication system.

[0104] 8, in an SSB-RO mapping relationship according to RACH configuration, a plurality of SSBs (810-1, 810-3, 810-5, ..., 810-(n-1)) separated from one another in time in a first frequency band may be mapped one-to-one to a plurality of ROs (820-1, 820-3, 820-5, ..., 820-(n-1)) separated from one another in time, while a plurality of SSBs (810-2, 810-4, 810-6, ..., 810-n) separated from one another in time in a second frequency band may be mapped one-to-one to a ROs (820-2, 820-4, 820-6, ..., 820-n) separated from one another in time. For example, if the upper layer parameter msg1-FDM is set to 2 (msg1-FDM=two) and the upper layer parameter ssb-perRACH-OccasionAndCB-PreamblesPerSSB is set to 2 (ssb-perRACH-OccasionAndCB-PreamblesPerSSB=two), N different SSBs (810-1 to 810-n) can be one-to-one mapped to N different ROs (820-1 to 820-n) that are arranged by frequency multiplexing in the frequency domain.

[0105] Meanwhile, the 5G NR communication system can support the DCI format shown in Table 8 based on Rel-16.

[0106] [Table 8]

[0107] The DCI may include downlink control information for one or more cells and may be associated with one RNTI. The DCI may be encoded through the following order: 1) information element multiplexing, 2) cyclic redundancy check (CRC) addition, 3) channel coding, and 4) rate matching, and decoding may also be performed taking these steps into consideration. The above description of DCI being associated with one RNTI may mean that the CRC parity bit of the corresponding DCI is scrambled with the corresponding RNTI. Referring to Table 6, some DCIs may include one or more PUSCH scheduling information for a certain cell.

[0108] As an example, the CRC of DCI format 0_1 ​​may be scrambled with C-RNTI, CS-RNTI (configured scheduling-RNTI), SP-CSI-RNTI (semi-persistent CSI RNTI), or MCS-C-RNTI (modulation coding scheme cell RNTI), and DCI format 0_1 ​​may include at least one of the following information:

[0109] □DCI format identifier (1 bit): An indicator indicating that it is a UL DCI format, and is always set to 0 in the case of DCI format 0_1.

[0110] □Carrier indicator (0 or 3 bits): An indicator that indicates the CC that the corresponding DCI schedules.

[0111] DFI flag (0 or 1 bit): Configuration Grant Downlink Feedback Information (CG-DFI) indicator.

[0112] - If DCI format 0_1 ​​is used for CG-DFI indication (DFI flag is 1), at least one of the following fields may be used:

[0113] HARQ-ACK bitmap (16 bits), where the bitmap to HARQ process index mapping order is the same as the HARQ process index mapping order, from MSB to LSB of the bitmap. For each bit in the bitmap, a value of 1 indicates ACK and a value of 0 indicates NACK.

[0114] TPC command for scheduled PUSCH (2 bits)

[0115] All remaining bits in format 0_1 ​​are set to zero

[0116] - If DCI format 0_1 ​​is not used for CG-DFI indication (no DFI flag field or DFI flag field is 0), at least one of the following fields shall be used:

[0117] □UL / SUL indicator (0 or 1 bit): This is the supplementary UL indicator.

[0118] □Bandwidth part indicator (0, 1 or 2 bits): An indicator indicating the bandwidth part to be activated among the uplink bandwidth parts configured in the terminal.

[0119] Frequency domain resource assignment: An indicator for allocating frequency domain resources.

[0120] □Time domain resource assignment: An indicator for allocating time-domain resources.

[0121] □Frequency hopping flag (0 or 1 bit): A frequency axis hopping indicator.

[0122] Modulation and coding scheme (5 bits)

[0123] New Data Indicator (NDI): An indicator that indicates whether the allocated data is new data or retransmitted data.

[0124] □Redundancy version (RV): An indicator that indicates the RV value when channel coding is applied to the allocated data.

[0125] □HARQ process number (4 bits): HARQ (hybrid automatic repeat request) process indicator assigned to the scheduled data.

[0126] □TPC command for scheduled PUSCH (2 bits): TPC indicator.

[0127] □SRS resource indicator: An aperiodic SRS resource selection indicator.

[0128] □Precoding information and number of layers: Indicator for the precoding and number of transmission layers used when transmitting PUSCH.

[0129] □Antenna ports: Indicators for the uplink antenna ports used during PUSCH transmission.

[0130] □SRS request: Indicator of whether or not Aperiodic SRS transmission is required.

[0131] □CSI request: An indicator of whether or not to report channel state information and how to report it.

[0132] □PTRS-DMRS association: An indicator showing the relationship between uplink PTRS (phase-noise tracking reference signal) antenna ports and DMRS (demodulation reference signal) antenna ports.

[0133] □DMRS sequence initialization: Indicator for the DMRS sequence initialization value during OFDM-based uplink transmission.

[0134] □UL-SCH indicator: An indicator that indicates whether the PUSCH includes an uplink shared channel (UL-SCH) (PUSCH that does not include an UL-SCH must include CSI).

[0135] □Open-loop power control parameter set indication: An indicator that indicates the open-loop power control parameter set (OPLC).

[0136] □Priority indicator: Uplink transmission priority indicator.

[0137] □Invalid symbol pattern indicator: An indicator that shows whether or not an invalid symbol pattern set in a higher layer is applied.

[0138] As yet another example, the CRC of DCI format 1_1 may be scrambled with C-RNTI, CS-RNTI, or MCS-C-RNTI, and DCI format 1_1 may include at least one of the following information:

[0139] □DCI format identifier (1 bit): An indicator indicating that it is a DL DCI format, and is always set to 1 in the case of DCI format 1_1.

[0140] □Carrier indicator (0 or 3 bits): An indicator that indicates the CC that the corresponding DCI schedules.

[0141] □Bandwidth part indicator (0, 1 or 2 bits): An indicator indicating the bandwidth part to be activated among the downlink bandwidth parts configured in the terminal.

[0142] Frequency domain resource assignment: An indicator for allocating frequency domain resources.

[0143] □Time domain resource assignment: An indicator for allocating time-domain resources.

[0144] PRB bundling size indicator: An indicator that indicates the PRB bundling type (static or dynamic) and size.

[0145] □ Rate matching indicator: An indicator that indicates the rate matching pattern set in the upper layer.

[0146] □ZP CSI-RS trigger: Aperiodic zero-power CSI-RS application indicator.

[0147] - "Modulation and coding scheme", "new data indicator", and "redundancy version" fields for transport block 1.

[0148] - "Modulation and coding scheme", "new data indicator", and "redundancy version" fields for transport block 2.

[0149] HARQ process number: This is the HARQ (hybrid automatic repeat request) process indicator assigned to the scheduled data.

[0150] □Downlink assignment index: A DAI indicator for HARQ-ACK codebook generation in TDD operation.

[0151] TPC command for scheduled PUCCH: This is the power control indicator for PUCCH transmission.

[0152] □PUCCH resource indicator: A PUCCH resource indicator that carries HARQ-ACK information for an allocated PDSCH or a defined PDSCH set.

[0153] □PDSCH-to-HARQ_feedback timing indicator: An indicator for the time axis offset between the assigned PDSCH and PUCCH transmissions.

[0154] □Antenna port(s): Antenna port indicator used for PDSCH transmission and reception.

[0155] □Transmission configuration indication: A TCI information indicator used for PDSCH transmission and reception.

[0156] □SRS request: A non-periodic SRS transmission indicator.

[0157] □DMRS sequence initialization: This is a DMRS sequence initialization value indicator used for PDSCH transmission and reception.

[0158] □Priority indicator: PDSCH reception priority indicator.

[0159] As another example, a DCI format may be used to transmit the same control information to one or more terminals. For example, the CRC of DCI format 2_3 may be scrambled with the TPC-SRS-RNTI (Transmit Power Control-Sounding Reference signal-RNTI) and may include at least one of the following information:

[0160] Block number 1, block number 2, ..., block number B: Indicators indicating the resource area to which DCI format 2_3 is applied. The start of the block is set by the upper layer parameter startingBitOfFormat2-3 or startingBitOfFormat2-3SUL-v1530.

[0161] -When a terminal in which the upper layer parameter srs-TPC-PDCCH-Group is set to type A performs uplink transmission in which there is no PUCCH and PUSCH or the SRS power control is not bound to the power control of the PUSCH, one block is configured in the upper layer and the following fields are defined for the corresponding block.

[0162] □SRS request (0 or 2 bits): Aperiodic SRS transmission indicator.

[0163] □TPC command number 1, TCP command number 2, ..., TPC command number N: These are uplink power control indicators that are applied to the UL carrier pointed to by the upper layer parameter cc-IndexInOneCC-Set.

[0164] -When a terminal with the upper layer parameter srs-TPC-PDCCH-Group set to type B performs uplink transmission without PUCCH and PUSCH or where SRS power control is not bound to PUSCH power control, one or more blocks are configured in the upper layer, and the following fields are defined for the corresponding blocks.

[0165] □SRS request (0 or 2 bits): Aperiodic SRS transmission indicator.

[0166] TPC command (2 bits)

[0167] As another example, a DCI format may be used to transmit the same control information to one or more terminals. For example, the CRC of DCI format 2_0 may be scrambled with the SFI-RNTI and used to notify information such as a slot format, a channel occupancy time (COT) duration, an available RB set, and search space set group switching. Specifically, DCI format 2_0 may include at least one of the following information:

[0168] -If the upper layer parameter slotFormatCombToAddModList is set,

[0169] □ Slot format indicator 1, slot format indicator 2, ..., slot format indicator N

[0170] -If the upper layer parameter availableRB-SetsToAddModList-r16 is set,

[0171] Available RB set indicator 1, available RB set indicator 2, ..., available RB set indicator N1

[0172] -If the upper layer parameter co-DurationsPerCellToAddModList-r16 is set,

[0173] COT duration indicator 1, COT duration indicator 2, ..., COT duration indicator N2

[0174] -If the upper level parameter searchSpaceSwitchTriggerToAddModList-r16 is set,

[0175] □ Search space set group switching flag 1, search space set group switching flag 2, ..., search space set group switching flag M

[0176] The size of DCI format 2_0 can be set to one of the values ​​up to 128 bits in the upper layer. For example, DCI format 2_5 can be used to notify the availability of soft type resources of the access backhaul integration (IAB) node. The CRC of DCI format 2_5 can be scrambled with the availability indicator-RNTI (AI-RNTI) and can include the following information:

[0177] □Availability indicator 1, availability indicator, ..., availability indicator N

[0178] In DCI format 2_5, a value smaller than or equal to 128 bits can be set in the upper layer.

[0179] The terminal may receive CORESET #0 and search space #0 configuration information that is the same as or similar to that shown in Table 9.

[0180] [Table 9]

[0181] The UE may refer to higher layer configurations that are the same as or similar to those shown in Tables 10 to 13 for cell-specific PDCCH monitoring.

[0182] [Table 10]

[0183] [Table 11]

[0184] [Table 12]

[0185] [Table 13]

[0186] The UE may refer to the same or similar higher layer configuration as shown in Table 14 for UE-specific PDCCH monitoring.

[0187] [Table 14]

[0188] The existence of one antenna port may mean that the channel experienced by a symbol transmitted through the corresponding antenna port can be estimated or inferred from the channel experienced by other symbols transmitted through the same antenna port.

[0189] Two different antenna ports are said to be quasi-colocated (QCL) when the large-scale characteristics of the channel experienced by symbols transmitted from one antenna port can be estimated or inferred from the channel experienced by symbols transmitted from the other antenna port. The large-scale characteristics of the channel can be one or more of "delay spread," "Doppler spread," "Doppler shift," "average gain," "average delay," and "spatial Rx parameters."

[0190] When the time / frequency resources of a certain signal (QCL target RS) are insufficient and the large-scale characteristics of the channel cannot be accurately measured using that signal alone, information (i.e., QCL information) on another signal (QCL reference RS) that has large-scale characteristics (i.e., sufficient time / frequency resources) that can be reused to receive the corresponding signal can be provided to the terminal to improve the terminal's channel measurement performance. In the case of an NR communication system, various types of QCLs can be supported, as follows:

[0191] QCL Type A: Includes Doppler shift, Doppler spread, average delay, and delay spread.

[0192] QCL Type B: Includes Doppler shift and Doppler spread.

[0193] QCL Type C: Includes Doppler shift and average delay.

[0194] -The QCL-type (Type) D includes {Spatial Rx parameter}.

[0195] FIG. 9 is a conceptual diagram illustrating an example of the QCL information transmission process through TCI (transmission configuration information) state setting and indication in a communication system.

[0196] JPEG2026506518000027.jpg85161

[0197] Since having the base station apply all the TCIs set in RRC in real time can greatly increase the implementation complexity of the terminal, the base station can transmit an activation message for some of the TCIs set in RRC to the terminal through L2 signaling such as MAC CE (S940). The base station can activate up to N (<M) TCIs, and the terminal may only receive a dynamic indication for the activated TCIs.

[0198] Thereafter, the base station can dynamically indicate some of the N activated TCIs to the terminal through L1 signaling such as DCI (S950). After receiving the L1 signaling, the terminal can apply the QCL information( s) indicated from the corresponding TCI at a predetermined timing and perform a reception operation for the corresponding signal or channel.

[0199] The TCI state indication steps, which are reached through 'RRC signaling step (S930)', 'MAC CE signaling step (S940)', and 'DCI signaling step (S950)' in Figure 9, may be partially omitted depending on the type of QCL target RS. For example, if the QCL target is a PDSCH DMRS and one or more TCI states are configured in the RRC, the base station may indicate the TCI state using all steps in Figure 9. However, if the QCL target is a PDSCH DMRS and a single TCI state is configured in the RRC, the MAC CE signaling step (S940) to the DCI signaling step (S950) may be omitted. Similarly, if the QCL target is a PDCCH DMRS, the DCI signaling step (S940) may be omitted. Specifically, the UE may acquire configuration information for the TCI state and QCL information by referring to RRC signaling that is the same as or similar to that shown in Table 15.

[0200] [Table 15]

[0201] The base station can instruct the terminal to activate or deactivate some of the TCI states set in the RRC through MAC CE signaling, or can apply the TCI state indicated by MAC CE to the QCL target RS. For example, the base station can use the following MAC CE signaling depending on the type of QCL target RS.

[0202] TCI state activation / deactivation MAC CE for UE-specific PDSCH DMRS

[0203] TCI status indication MAC CE for terminal-specific PDCCH DMRS

[0204] - Enhanced TCI state activation / deactivation MAC CE for UE-specific PDSCH DMRS

[0205] FIG. 10 is a conceptual diagram illustrating one embodiment of a TCI state activation / deactivation Medium Access Control (MAC) Control Element (CE) structure in a communication system.

[0206] 10, in the TCI state activation / deactivation MAC CE structure for a UE-specific PDSCH DMRS, the first octet (Oct 1) may include a COREST pool ID field 1010, a serving cell ID field 1020, and a BWP ID field 1030, and the second octet (Oct 2) to the Nth octet (Oct N) may include a field 1040 for Ti, which is a TCI state ID. The detailed meaning of each field may be as follows, and the size may be variable.

[0207] Serving cell ID: The serving cell ID to which the corresponding MAC CE is applied.

[0208] BWP ID: Bandwidth portion ID to which the corresponding MAC CE is applied. The bandwidth portion can be identified in relation to the BWP indication field in the DCI.

[0209] Ti: Indicates TCI state ID i. When this value is set to 0, it may mean that the TCI state with TCI state ID i is deactivated, and when this value is set to 1, it may mean that the TCI state with TCI state ID i is activated. The TCI states activated by 1 may be sequentially mapped to TCI indication field code points in the DCI.

[0210] -CORESET Pool ID: If the DCI scheduling the PDSCH is monitored in a CORESET that does not include the upper layer parameter coresetPoolIndex, this field may be ignored. If the DCI scheduling the PDSCH is monitored in a CORESET that includes the upper layer parameter coresetPoolIndex, the Ti indication may only be applied if the 'CORESET Pool ID value' and the 'CORESET coresetPoolIndex value' match.

[0211] FIG. 11 is a conceptual diagram illustrating an embodiment of a TCI status indication MAC CE in a communication system.

[0212] Referring to FIG. 11, the TCI status indication MAC CE structure for a UE-specific PDCCH DMRS may include a serving cell ID field 1110 and a CORESET ID field 1120 in the first octet (Oct 1), and a CORESET ID field 1130 and a TCI status ID field 1140 in the second octet (Oct 2), and the sizes thereof may be variable.

[0213] Serving cell ID: The serving cell ID to which the corresponding MAC CE is applied.

[0214] CORESET ID: Indicates the control resource set to which the corresponding MAC CE is applied. If this value is set to 0, the CORESET set through controlResourceSetZero may indicate CORESET #0.

[0215] TCI State ID: May refer to the TCI state ID indicated by the corresponding MAC CE.

[0216] The base station can configure spatial relation information in the UE through higher layer (e.g., RRC) signaling to indicate uplink beam information. The spatial relation information may refer to a signaling structure that specifies that the spatial domain filter value used in transmitting and receiving a reference signal (reference RS) is used as the spatial TX filter for uplink transmission of the corresponding spatially related target RS. The spatially related reference RS may be a downlink signal such as SSB or CSI-RS, and may also be configured as an uplink signal such as SRS. If the reference RS is a downlink signal, the UE can use the spatial RX filter value used to receive the corresponding reference RS as the spatial TX filter for transmitting the corresponding spatial relation target RS. If the reference RS is an uplink signal, the UE can use the spatial TX filter value used to transmit the corresponding reference RS as the spatial TX filter for transmitting the corresponding spatial relation target RS.

[0217] The signaling structure for the spatial relationship information may vary depending on the type of target RS. For example, if the target RS is an SRS, the base station may perform RRC setup for each SRS resource based on a message identical or similar to that shown in Table 16.

[0218] [Table 16]

[0219] For example, if the target RS is an SRS, the base station may perform RRC setup for each SRS resource based on a message identical or similar to that shown in Table 17.

[0220] [Table 17]

[0221] In a 5G NR communication system, one slot format may include a downlink symbol, an uplink symbol, and a flexible symbol.

[0222] FIG. 12 is a conceptual diagram showing a slot configuration according to a slot format in a communication system.

[0223] 12, in a communication system, a downlink dedicated slot 1200 may be configured such that all symbols in the slot are composed of only downlink symbols 1215 according to the slot format. As another example, an uplink dedicated slot 1205 may be configured such that all symbols in the slot are composed of only uplink symbols 1220 according to the slot format. As another example, a downlink / uplink mixed slot 1210 may be configured such that some symbols in the slot are composed of downlink symbols 1225 and some symbols are composed of uplink symbols 1235 according to the slot format. In this case, a specific symbol in the mixed slot 1210 including both uplink and downlink symbols may be set or indicated as a guard period 1230 to facilitate downlink-uplink transition, and the terminal may not perform transmission or reception during the guard period 1230.

[0224] In a 5G NR communication system, a base station can configure a 'slot format' spanning one or more slots for each serving cell in a terminal through the upper layer parameter tdd-UL-DL-ConfigurationCommon. In this case, the upper layer parameter tdd-UL-DL-ConfigurationCommon can include or refer to at least one of the following information:

[0225] JPEG2026506518000031.jpg14161

[0226] -Pattern 1: This is the first pattern.

[0227] -Pattern 2: The second pattern.

[0228] Here, pattern 1 or pattern 2 may include at least one of the following settings:

[0229] Slot setting period (dl-UL-TransmissionPeriodicity): The slot setting period P expressed in msec.

[0230] JPEG2026506518000032.jpg14161

[0231] JPEG2026506518000033.jpg15161

[0232] JPEG2026506518000034.jpg16161

[0233] JPEG2026506518000035.jpg15161

[0234] JPEG2026506518000036.jpg58161

[0235] JPEG2026506518000037.jpg49161

[0236] The base station can use the upper layer parameter tdd-UL-DL-ConfigurationDedicated to override the direction of the flexible symbols among the symbols set in the terminal by the upper layer parameter tdd-UL-DL-ConfigurationCommon based on the following information.

[0237] - Slot configuration set (slotSpecificConfigurationsToAddModList): A set of slot configurations.

[0238] - Slot Index (slotIndex): The index of the slot in the set of slot configurations.

[0239] - Symbol direction (symbols): The direction of the slot indicated by the slot index (slotIndex). If the symbol direction is all downlink (symbols=allDownlink), all symbols in the slot are downlink symbols. If the symbol direction is all uplink (symbols=allUplink), all symbols in the slot are uplink symbols. If the symbol direction is explicit (symbols=explicit), nrofDownlinkSymbols can indicate the number of downlink symbols located at the beginning of the slot, and nrofUplinkSymbols can indicate the number of uplink symbols located at the end of the slot. If nrofDownlinkSymbols or nrofUplinkSymbols is omitted, the corresponding parameter can be considered to point to a value of 0. The remaining symbols in the slot are flexible symbols.

[0240] In a 5G communication system, a base station may be able to indicate a slot format to a terminal based on L1 signaling. For example, when a terminal receives an upper layer parameter SlotFormatIndicator from a base station, the terminal may acquire configuration information for SFI-RNTI (slot format indication-RNTI). Meanwhile, when a terminal receives an upper layer parameter dci-PayloadSize from a base station, the terminal may acquire configuration information for the payload size of DCI format 2_0. In addition, the terminal may additionally receive information such as PDCCH candidate, CCE aggregation level, and search space set of CORESET monitoring DCI format 2_0 from the base station. Each slot format indication (SFI) index field in DCI format 2_0 may indicate a slot format to be applied to each slot in the slot set of DL BWP and UL BWP from the slot where the terminal detected the corresponding DCI format 2_0. In this case, the size of the slot set may be equal to or greater than the PDCCH monitoring period of DCI format 2_0. As an example, when a slot set consists of N slots, DCI format 2_0 may include N SFI index fields, and each SFI index field may indicate a slot format shown in the following Tables 18 to 20. In Table 14, "D" may represent a downlink symbol, "U" may represent an uplink symbol, and "F" may represent a flexible symbol.

[0241] [Table 18]

[0242] [Table 19]

[0243] [Table 20]

[0244] In a 5G NR communication system, the Integrated Access Backhaul (IAB) feature may enable flexible and dense wireless backhaul links for each cell without the support of a wired network.

[0245] FIG. 13 is a conceptual diagram illustrating one embodiment of an integrated access and backhaul (IAB) network in a communication system.

[0246] Referring to Figure 13, a communication system 1300 may include one or more communication nodes. The communication nodes of the communication system 1300 may constitute an IAB network. For example, the communication system 1300 may include one or more IAB nodes. Figure 13 may be seen as illustrating an embodiment in which one IAB node communicates with one or more upper nodes and one or more lower nodes. However, this is merely an example for convenience of explanation, and embodiments of the present invention are not limited thereto.

[0247] The communication system 1300 may include multiple IAB nodes. For example, the communication system 1300 may include a first IAB node 1310, one or more parent nodes 1320 corresponding to the first IAB node's 1310's upper nodes, and / or one or more child nodes 1330 corresponding to the first IAB node's 1310's lower nodes. Here, the one or more parent nodes 1320 may each be referred to as a "donor node." The IAB node 1310, the one or more parent nodes 1320, and / or the one or more child nodes 1330 may constitute an IAB network. The IAB nodes 1310, 1320, and 1330 constituting the IAB network may each function as a type of repeater configured based on a front-haul architecture. The communication system 1300 employing IAB network technology can support flexible and dense wireless backhaul links for each cell without the support of a wired network.

[0248] Each of the IAB nodes 1310, 1320, and 1330 may include an IAB-DU (distributed unit) and an IAB-MT (mobile terminal). The IAB-MT allows each IAB node to function like a terminal in communication with a higher-level node. For example, the first IAB node 1310 can communicate with the higher-level parent node 1320 through the IAB-MT. Meanwhile, the IAB-DU allows each IAB node to function like a base station or cell in communication with a lower-level node. For example, the first IAB node 1310 can communicate with the lower-level child node 1330 or terminal 1340 through the IAB-DU.

[0249] The IAB-MT of the first IAB node 1310 may be connected to the IAB-DU of the parent node 1320 via a Uu interface 1325. The IAB-DU of the first IAB node 1310 may be connected to the IAB-MT of the child node 1330 via a Uu interface 1335. The IAB-DU of the first IAB node 1310 may be connected to the terminal 1340 via a Uu interface 1345.

[0250] The IAB nodes that make up the IAB network can fully decode received signals, re-encode the decoded received signals, amplify them, and transmit them. IAB nodes can be classified as a type of regenerative relay. To this end, IAB nodes can support the control plane (CP) and user plane (UP) from the parent node to the terminal based on a protocol stack structure including L1 and L2 layers or higher.

[0251] The IAB nodes that make up the IAB network have the advantage of being able to perform various operations, including the operations of the base station and the terminal, but have the disadvantages of being relatively complex to implement and expensive to produce, and possibly requiring a relatively long delay for retransmission.

[0252] FIG. 14 is a block diagram illustrating an embodiment of a separate structure of a central unit (CU) and distributed units (DU) in a communication system.

[0253] Referring to FIG. 14, in an IAB network, a central unit (CU) and a distributed unit (DU) are separated into two hop chains of IAB nodes 1410 and 1415 connected to an IAB donor 1405. Each IAB node 1410 and 1415 and terminals 1420, 1422, and 1424 may be connected to a core network (next generation core, NGC) 1400 in a stand-alone (SA) mode. Each IAB node 1410 and 1415 may include one DU and one MT. An IAB node (e.g., 1415) may be connected to a parent IAB node 1410 or the IAB donor 1405 via an MT 1417. As another example, an IAB node (e.g., 1410) may establish an RLC channel to the MT 1417 of a child IAB node 1415 via a DU 1414. At this time, the RLC channels 1450, 1452 generated for MTs 1412, 1417 may be referred to as modified RCL* because their contents may change, such as including some additional information for IAB operation in addition to the components of the RLC channel for the terminal.

[0254] An IAB node can be connected to one or more parent IAB nodes or IAB donor DUs. In this case, an IAB node can include multiple DUs, but each DU of the IAB node can have an F1-C (1440, 1442) connection with a single IAB donor CU-CP (control plane). This means that even if an IAB node has multiple UP (user plane) connections, there should be no crosstalk in the operation of the IAB node based on a single CP connection (in other words, connected to a single IAB donor).

[0255] The IAB donor 1405 can include a DU for supporting UEs and MTs of child IAB nodes. The IAB donor 1405 can include a CU (1407) for itself and all child IAB node DUs (1409, 1414, 1419). An IAB donor can be assumed to have a single IAB donor, and the IAB donor that manages the IAB donor can be changed using a topology adaptation function. The DU of an IAB node can be connected to the IAB donor's CU through an F1 interface or modified F1 interface (modified F1, F1*) (1440, 1442). The F1*-U (user plane) can operate over RLC channels 1450, 1452 between the corresponding IAB-MT (1417, 1412) and the parent IAB node or donor DU (1414, 1409).

[0256] Hereinafter, for the sake of convenience in the present disclosure, upper layer parameters or upper layer settings may be generally referred to as including all information transmitted or set through various interfaces, such as the F1 interface (1440, 1442), the NG interface (1430, connecting the CU and NGC), and the X2 interface, without being limited to the aforementioned L2 and L3 signaling.

[0257] Although the slot format configuration and indication schemes described with reference to Figures 11 and 12 may appear to be limited to a terminal communicating with a base station, this is merely an example for convenience of explanation, and embodiments of the present invention are not limited thereto. For example, the slot format configuration and indication schemes described with reference to Figures 11 and 12 may also be applied to the IAB-DU and / or IAB-MT. For example, for each serving cell of the IAB-DU, the IAB-DU may configure slot format information for each slot in each slot set by receiving an upper layer parameter IAB-DU-Resource-Configuration. Meanwhile, the IAB-MT may receive configuration information for "slot format" for one or more slots for each serving cell from at least one upper node of the IAB-MT via an upper layer parameter tdd-UL-DL-ConfigurationDedicated-IAB-MT. If the IAB-MT receives the upper layer parameter tdd-UL-DL-ConfigurationDedicated-IAB-M, the received upper layer parameter can replace the upper layer parameter tdd-UL-DL-ConfigurationDedicated in the slot format configuration and indication method described above. Specifically, the upper layer parameter tdd-UL-DL-ConfigurationDedicated-IAB-MT can include the following information:

[0258] □IAB-MT slot configuration set (slotSpecificConfigurationsToAddModList-IAB-MT): A set of slot configurations.

[0259] □SlotIndex: The index of the slot in the set of slot configurations.

[0260] IAB-MT symbol direction (symbols-IAB-MT): The direction of the slot indicated by the slot index.

[0261] If the IAB-MT symbol directions are all downlink (symbols-IAB-MT=allDownlink), all symbols in the corresponding slot are downlink symbols.

[0262] If the IAB-MT symbol directions are all uplink (symbols-IAB-MT=allUplink), all symbols in the corresponding slot are uplink symbols.

[0263] If the IAB-MT symbol direction is explicit (symbols-IAB-MT=explicit), nrofDownlinkSymbols can indicate the number of downlink symbols located at the beginning of the slot, and nrofUplinkSymbols can indicate the number of uplink symbols located at the end of the slot. If nrofDownlinkSymbols or nrofUplinkSymbols is omitted, the corresponding parameter can be considered to point to a value of 0. The remaining symbols in the slot are flexible symbols.

[0264] If the IAB-MT symbol direction is IAB-MT explicit (symbols-IAB-MT=explicit-IAB-MT), nrofDownlinkSymbols can indicate the number of downlink symbols located at the beginning of the slot, and nrofUplinkSymbols can indicate the number of uplink symbols located at the end of the slot. If nrofDownlinkSymbols or nrofUplinkSymbols is omitted, the corresponding parameter can be considered to point to a value of 0. The remaining symbols in the slot are flexible symbols.

[0265] Like the general UE described above, the IAB-MT can also receive DCI format 2_0, through which it can receive slot format configuration information from the base station or the parent node IAB-DU. In the case of DCI format 2_0 received by the IAB-MT, the candidate values ​​of each SFI field may not be limited to the values ​​shown in Table 14. For example, the candidate values ​​of each SFI field of DCI format 2_0 received by the IAB-MT can additionally include the values ​​shown in Tables 21 and 22.

[0266] [Table 21]

[0267] [Table 22]

[0268] The IAB-MT can receive information about symbols not used by the corresponding IAB-MT for a serving cell through upper layer parameters (e.g., Provided Guard Symbols MAC CE). The IAB-MT can perform a transition between the IAB-MT and IAB-DU of the corresponding IAB node during the time interval containing the unused symbols. The corresponding base station can also signal the numerology for the symbols to the UE through upper layer parameters (e.g., Provided Guard Symbols MAC CE).

[0269] In a given IAB-DU cell, symbols within a slot can be set to one of three types: "hard," "soft," or "unavailable (or not available)."

[0270] If a downlink, uplink, or flexible symbol is configured as a hard type, the IAB-DU cell can transmit and / or receive signals using the corresponding symbol. This may mean that the hard type setting of a symbol ensures that the IAB-DU downlink, uplink, or flexible symbol setting for the corresponding symbol is reflected.

[0271] Specifically, in one embodiment of the communication system, F1AP (F1 application protocol) signaling as shown in Table 23 may be provided, through which an upper IAB node (e.g., IAB donor, parent node, core network, etc.) can configure the DU resource type of a lower IAB node (e.g., IAB node, child node). Referring to Table 16, the DU resource type information may include one HSNA slot configuration list consisting of one or more HSNA (hard, soft, not-available) slot configurations. In this case, one HSNA slot configuration list may include the maximum number of HSNA slot configurations (e.g., maxnoofHSNA). The nth HSNA slot configuration included in the HSNA slot configuration list may include information on whether the hard, soft, or not-available type is applied to each of the downlink symbol, uplink symbol, and flexible symbol of the nth slot, depending on the application period and start time of the HSNA slot configuration list.

[0272] [Table 23]

[0273] If a downlink, uplink, or flexible symbol is configured as a soft type, the corresponding IAB-DU cell can transmit and / or receive signals on the symbol if at least one of the following conditions is met:

[0274] Condition 1: The IAB-MT (co-located / associated with the corresponding IAB-DU) does not transmit or receive at the corresponding symbol.

[0275] -Condition 2: When the IAB-MT (co-located / associated with the corresponding IAB-DU) can transmit or receive using the corresponding symbol, but the transmission and reception operations of the IAB-MT are not changed by the IAB-DU's use of the corresponding symbol.

[0276] Condition 3: When the IAB-MT (co-located / associated with the corresponding IAB-DU) receives DCI format 2_5 indicating that the corresponding soft symbol is "available."

[0277] If a downlink, uplink, or flexible symbol is set to an unavailable or NA (not-available) type, the corresponding IAB-DU (cell) may not transmit or receive on the symbol.

[0278] If the IAB-DU transmits one of the following cell-specific, periodic, or semi-static signals or channels in a certain slot symbol(s), the IAB-DU can perform transmission and reception operations by assuming that the corresponding symbol(s) in the slot is the same as the hardware type regardless of the configured resource type:

[0279] - SS / PBCH block, CSS set for Type 0-PDCCH configured by SIB1 (System Information Block 1) for PDCCH configuration (PDCCH for Type 0-PDCCH CSS sets configured by pdcchConfigSIB1), periodic CSI-RS, etc.

[0280] If the IAB-DU receives one of the cell-specific, periodic, semi-static signals or channels included in the following list in the symbol(s) of a certain slot, the IAB-DU can perform transmission and reception operations by assuming that the corresponding symbol(s) in the corresponding slot are the same as those set in the hardware type regardless of the set resource type.

[0281] □PRACH, SR(scheduling request)

[0282] The following information may be set for each cell in the IAB-DU cell set:

[0283] □IAB-DU cell identifier (iabDuCellId-AI): means the identifier of the IAB-DU cell.

[0284] □AI position in DCI format (positionInDCI-AI): The position of the availability identifier (AI) index field in DCI format 2_5.

[0285] Availability Combinations: Contains a list of the following two pieces of information for availability combinations:

[0286] Resource Availability: Indicates the resource availability for soft symbols contained in one or more slots of an IAB-DU cell. The availability of soft symbols in a slot can be determined by referring to the values ​​in Table 17.

[0287] Availability Combination Identifier (availabilityCombinationId): Indicates the mapping between resource availability and the availability indicator (AI) index field in DCI format 2_5.

[0288] JPEG2026506518000044.jpg85161

[0289] [Table 24]

[0290] As described above, upper IAB nodes, including IAB donors, can instruct the use or non-use of soft symbols of lower IAB nodes based on the contents of DCI format 2_5 and Table 16. However, this function is designed under the assumption that IAB nodes operate in half duplex mode. In other words, this function is designed mainly assuming that the MT and DU of a certain IAB node operate in TDM (time division multiplexing) or TDD (time division duplexing).

[0291] In one embodiment of the communication system, F1AP signaling as shown in Table 25 may be used. Through this, an IAB node can report or transmit to an upper IAB node (e.g., an IAB donor, parent node) the multiplexing capability between the IAB-DU of the corresponding IAB node and the IAB-MT of the corresponding IAB node (or a cell configured in a co-located IAB-MT) (or a cell configured in a co-located IAB-MT). Referring to Table 18, the multiplexing information can include one IAB-MT cell list consisting of one or more IAB-MT cell information. In this case, one IAB-MT cell list can include IAB-MT cell information for the maximum number of serving cells (maxnoofServingCells). The nth IAB-MT cell information included in the IAB-MT cell list can include the ID (NR Cell Identity) information of the corresponding cell and information on whether the following four types of multiplexing are supported:

[0292] DU_RX / MT_RX Multiplexing: Indicates whether the corresponding IAB node supports simultaneous reception in DU and MT

[0293] DU_TX / MT_TX Multiplexing: Indicates whether the corresponding IAB node supports simultaneous transmission in DU and MT

[0294] DU_TX / MT_RX multiplexing: Indicates whether the corresponding IAB node can simultaneously transmit in DU and receive in MT

[0295] DU_RX / MT_TX multiplexing: Indicates whether the corresponding IAB node can simultaneously receive in DU and transmit in MT

[0296] [Table 25]

[0297] According to Table 25, an IAB node may be able to semi-statically report the DU / MT multiplexing capability or the applicability of DU / MT simultaneous operation for each cell, but the applicability of DU / MT simultaneous operation for the corresponding IAB node may be entirely up to the corresponding IAB node. An upper IAB node may not support dynamic or semi-static control of the DU / MT simultaneous operation of a lower IAB node depending on the situation.

[0298] FIG. 15 is a flowchart for explaining a first embodiment of a resource management method for an IAB node in a communication system.

[0299] 15 illustrates a first embodiment of a resource management method for an IAB node, exemplifying an operation of the IAB node to determine whether to use IAB-DU resources. However, this is merely an example for convenience of explanation, and embodiments of the present invention are not limited thereto. For example, the configurations described herein for "whether to use IAB-DU resources" may be applied in the same or similar manner to "whether to use IAB node resources," "whether to use IAB-MT resources," "whether to use DU / MT simultaneous operation resources," etc.

[0300] 15, in the order in which an IAB node determines whether to use an IAB-DU resource, the IAB node can check whether the corresponding IAB-DU resource is available and can receive at least one of upper layer IAB-MT resource configuration information and IAB-DU resource configuration information from an upper IAB node to determine whether to use the resource (S1500). For example, the upper layer IAB-MT resource configuration information can include D / U / F (downlink / uplink / flexible) slot and symbol configuration information for an IAB-MT cell (or a set of cells). As another example, the upper layer IAB-DU resource configuration information can include D / U / F (downlink / uplink / flexible) slot and symbol configuration information for an IAB-DU cell (or a set of cells).

[0301] The upper layer IAB-DU resource configuration information may include information on the type (hard, soft, not-available) of IAB-DU resources configured by the upper IAB node. The upper layer IAB-DU resource configuration information may include some or all of cell-specific / semi-static downlink signals and channels, such as SSB configured in the cell (or set of cells) configured for the IAB-DU, a CSS set for type 0-PDCCH configured by the SIB1 for PDCCH configuration, and CSI-RS. The upper layer IAB-DU resource configuration information may include some or all of cell-specific / semi-static uplink signals and channels, such as PRACH and SR configured in the cell (or set of cells) configured for the IAB-DU.

[0302] In addition to the above-described upper layer configuration, the IAB node may receive at least one of a physical layer (L1 signaling) IAB-MT resource indicator and an IAB-DU resource indicator from an upper IAB node (S1510). For example, the physical layer IAB-MT resource indicator may be DCI format 2_0, which includes a slot format indicator for a cell (or a set of cells) configured for IAB-MT. For another example, the physical layer IAB-DU resource indicator may be DCI format 2_5, which includes an IAB-DU soft resource availability indicator (AI).

[0303] Finally, the IAB node can make a final decision on whether to use the IAB-DU resource (S1520) based on the upper layer signal (S1500) and L1 signaling (S1510) information.

[0304] On the other hand, it may generally be impossible to force all terminals to implement the same features. UE capability reports can enable expensive terminals to implement a large number of features with high performance, while inexpensive terminals can implement a small number of features with low performance. In this way, UE capability reports can ensure terminal implementation flexibility for various situations and can report the relevant information to the network, allowing the base station to set each function within the limits supported by each terminal. It may be promised that all terminals must implement a specific function, in which case the UE capability report for the corresponding function may be omitted.

[0305] A terminal may be able to report different terminal capability values ​​for a single function for each frequency band or duplex scheme. For example, a terminal may report to a base station that it supports a particular function for frequency range 1 (FR1), which means a band below 6 GHz, but does not support the function for frequency range 2 (FR2), which means a band above 6 GHz. As another example, a terminal may report to a base station that it supports a particular function in time division duplexing (TDD), but does not support the function in frequency division duplexing (FDD).

[0306] If the terminal performs a terminal capability report, the base station must respect (obey) the contents of the terminal capability report when configuring, indicating, or scheduling the terminal. This means that if the base station instructs the terminal to perform configuration, indication, or scheduling that contradicts the terminal capability report, the terminal can ignore it.

[0307] FIG. 16 is a flowchart illustrating an embodiment of a terminal capability reporting procedure in a communication system.

[0308] Referring to Figure 16, in the UE capability reporting procedure, if the UE is in RRC connected mode (UE in RRC_CONNECTED), the base station can transmit a UE capability report request signal to the UE through the upper layer parameter UECapabilityEnquiry (1600). At this time, the network can only refer to UE capability reports after AS (access stratum) security activation and can not retransmit or report UE capability reports before AS security activation to the core network (CN). The UE that receives the UE capability report request signaling can compile UE capability information through a specific procedure and report the UE capability information to the base station through a UE capability information (for example, UECapabilityInformation) signal (1610).

[0309] The specific procedure for generating the UE capability information signal may include a procedure for generating at least one of a list of bands or band combinations (BC) supported by the UE (supportedBandCombinationList), feature set information (FS) related to feature sets supported by the UE, or feature set combinations (FSC) related to combinations of feature sets supported by the UE. For example, when a base station requests a UE capability report from the UE to obtain information on bands or band combinations supported by the UE, the UE may report which bands it supports for each radio access technology (RAT). To this end, the base station may set the RAT-Type in a UE RAT capability report request signal (e.g., UE-CapabilityRAT-Request) included in a UE RAT capability report request list signal (e.g., ue-CapabilityRAT-RequestList), which is an upper layer message, to one of "nr," "eutra-nr," "eutra," or "eutra-fdd." This may mean that the base station can request a terminal capability report for one or more RATs or RAT combinations from the terminal. In this case, the terminal can perform a request-specific response to a supported band list for multiple RATs or RAT combinations. As an example, if the RAT-type is set to 'nr', the terminal can include a list of bands or band combinations to which NR-DC can be applied in the terminal capability report. As another example, if the RAT-type is set to 'eutra-nr', the terminal can include a list of bands or band combinations to which MR-DC (multi-RAT DC) can be applied, such as EN-DC, NGEN-DC, and NE-DC, in the terminal capability report. In addition, when the base station requests a terminal capability report, it can provide the terminal with a band list that the terminal determines whether to support via the upper layer parameter frequencyBandListFilter.The terminal can determine candidate band combinations for the bands included in the upper layer parameter frequencyBandListFilter by considering the 'predefined RAT types that can be supported for each band', 'RAT-type information requested by the base station', etc., and can include this in the terminal capability report.

[0310] 17a and 17b are conceptual diagrams for explaining a first embodiment of a user plane protocol stack structure and a control plane protocol stack structure in a communication system.

[0311] 17a and 17b, a radio interface protocol stack or radio interface protocol stack structure 1700, 1750 may be defined in a wireless connection section between communication nodes. For example, the radio interface protocol stack may be divided into a vertically configured physical layer, a data link layer, a network layer, etc.

[0312] The air interface protocol stack may be divided into a user plane protocol stack 1700 and a control plane protocol stack 1750. Here, the control plane may be a plane for transmitting control signals. The control signals may be referred to as signaling signals. The user plane may be a plane for transmitting user data.

[0313] 17a, the communication system may include a terminal 1710 and a base station 1720. The terminal 1710 may be referred to as a user equipment (UE). The base station 1720 may correspond to an eNB, a gNB, etc. The terminal 1710 and the base station 1720 may transmit and receive data signals between each other based on the user plane protocol stack structure 1700 shown in FIG.

[0314] In the user plane air interface protocol stack structure 1700 of the communication system, the terminal 1710 and the base station 1720 may include PHY layers 1711, 1721 included in L1, MAC layers 1712, 1722 included in L2, RLC (radio link control) layers 1713, 1723 and PDCP (packet data convergence protocol) layers 1714, 1724, SDAP (service data adaptation protocol) layers 1715, 1725 included in L3, etc.

[0315] 17b, the communication system may include a terminal 1760 and a base station 1770. The terminal 1760 and the base station 1770 may transmit and receive control signals to and from each other based on the control plane protocol stack structure 1750 shown in FIG.

[0316] In the control plane protocol stack structure 1750 of the communication system, the terminal 1760 and the base station 1770 may include PHY layers 1761, 1771 included in L1, MAC layers 1762, 1772 included in L2, RLC layers 1763, 1773 and PDCP layers 1764, 1774, RRC layers 1765, 1775 included in L3, etc.

[0317] The communication system may further include an Access and Management Mobility Function (AMF) 1780. In the control plane protocol stack structure 1750, the terminal 1760 and the AMF 1780 may include non-access stratum (NAS) layers 1766, 1786. The base station 1770 may not include a NAS layer. In other words, in the control plane protocol stack structure 1750, the NAS layer of the base station 1770 may be transparent.

[0318] The 5G communication system can provide technologies for improving wireless coverage and / or reducing network construction costs. For example, the 5G communication system can provide IAB (integrated access and backhaul) technology that provides wireless backhaul / fronthaul that can coexist with the wireless access network, and repeater technology that covers terminating areas at low cost.

[0319] In a 5G NR communication system, it may be possible to support flexible and dense wireless backhaul links for each cell without the support of a wired network through the integrated access backhaul (IAB) feature. In addition, the protocol structures of Figures 17a and 17b can be appropriately modified and applied to suit the situation when carrier aggregation (CA) or dual connectivity (DC) is applied.

[0320] Figure 18a is a conceptual diagram for explaining a user plane protocol structure for carrier association (CA) in a base station of a communication system, and Figure 18b is a conceptual diagram for explaining a user plane protocol structure for dual connection (DC) in a base station of a communication system.

[0321] 18a and 18b, radio interface protocol stacks or radio interface protocol stack structures 1800 and 1850 may be defined in a wireless connection section between communication nodes. For example, a user plane protocol stack structure 1800 for carrier aggregation (CA) may be defined in a wireless connection section between communication nodes. Alternatively, a user plane protocol stack structure 1850 for dual connectivity (DC) may be defined in a wireless connection section between communication nodes.

[0322] 18a, the communication system may include a base station 1820. The base station 1820 may correspond to an eNB, a gNB, etc. The base station 1800 employing CA may operate two or more PHY layers 1821-1 and 1821-2 to transmit and receive data to two or more component carriers (CCs). In this case, the PHY layers 1821-1 and 1821-2 may be connected to a single MAC layer 1822 by an independent hybrid automatic repeat request (HARQ) entity for each CC (or serving cell).

[0323] For connections at higher layers such as RLC (1823), PDCP (1824), and SDAP (1825), please refer to the descriptions of Figures 17a and 17b. This is because CA assumes support for multiple carriers at a single transmission point. When CA is operated at multiple transmission points, the base station 1800 requires a backhaul with a latency of 0 ms between transmission points for a single MAC entity.

[0324] Referring to FIG. 18b, the communication system may include a master cell group (MCG) 1870 and a secondary cell group (SCG) 1880. The cells or base stations of the MCG 1870 and SCG 1880 may establish DC with lower nodes such as terminals based on a user plane protocol stack structure 1850 for DC. In the user plane air interface protocol stack structure 1850 for DC, the cell or base station of the MCG 1870 may include a PHY layer 1871 included in L1, a MAC layer 1872 included in L2, an RLC layer 1873 and a PDCP layer 1874, an SDAP layer 1875 included in L3, etc. Meanwhile, the cell or base station of the SCG 1880 may include a PHY layer 1881 included in L1, a MAC layer 1882 and an RLC layer 1883 included in L2.

[0325] A base station applying DC can use two or more transmission nodes 1870, 1880 to transmit and receive on two or more component carriers. In this case, the transmission node can be configured as a first node (master node, master gNB, MgNB) 1870 that leads the 5GC connection and a second node (secondary node, secondary gNB, MgNB) 1880 that supports the 5GC auxiliary connection.

[0326] The first node 1870 and the remaining nodes 1880 may also be referred to as MeNB to SeNB when applying multi-RAT DC such as LTE-NR or NR-LTE. In the case of DC, a backhaul structure with a delay time greater than 0 (e.g., 3 ms) is assumed, so unlike CA, the MgNB 1870 and SgNB 1880 support separate RLC layers 1873, 1883, separate MAC layers 1872, 1882, and separate PHY layers 1871, 1881.

[0327] As an example, this means that data separated for the MeNB 1870 and the SeNB 1880 can be scheduled independently of each other in the PDCP layer 1874. In the above description, sharing layers above PDCP with each other when operating a DC (i.e., using layers above PDCP as a single entity when operating a DC) is an example of DC operation, and in actual application, DC and CA are not mutually exclusive and can be applied simultaneously.

[0328] As another example, the MgNB 1870 can configure a cell group consisting of one or more CCs, which can be named a master cell group (MCG). Similarly, the SgNB 1880 can configure a cell group consisting of one or more CCs, which can be named a secondary cell group (SCG). In this case, multiple CCs within one cell group (i.e., within an MCG or SCG) can be operated according to the CA protocol architecture described above.

[0329] One embodiment of a communication system supporting 5G wireless communication can support various DC types, such as:

[0330] □EN-DC (EUTRA-NR DC): A DC in which the MCG is configured with E-UTRA (Evolved Universal Terrestrial Radio Access, 4G) and the SCG is configured with NR (new radio, 5G). Here, the control plane of the MCG can be configured through the 4G core (EPC, Evolved Packet Core).

[0331] NGEN-DC (Next Generation-RAN E-UTRA-NR DC): DC in which the MCG is configured with E-UTRA and the SCG is configured with NR. In this case, the control plane of the MCG can be configured through the 5G core (NG, next generation core).

[0332] □NE-DC (NR-EUTRA DC): A DC in which the MCG is composed of NR and the SCG is composed of E-UTRA.

[0333] □NR-DC (NR DC): DC in which both MCG and SCG are composed of NR.

[0334] The base station can perform DC-related configuration on the terminal (UE, MT, etc.) using one or more upper layer parameters. For example, the upper layer parameters used by the base station for DC-related configuration can include at least some of CellGroupConfig, SpCellConfig, ReconfigurationWithSync, and SCellConfig. The upper layer parameter CellGroupConfig may be the same as or similar to those shown in Tables 26 and 27.

[0335] [Table 26]

[0336] [Table 27]

[0337] Meanwhile, the upper layer parameters SpCellConfig may be the same as or similar to those shown in Table 28.

[0338] [Table 28]

[0339] Meanwhile, the upper layer parameter ReconfigurationWithSync may be the same as or similar to that shown in Table 29.

[0340] [Table 29]

[0341] Meanwhile, the upper layer parameter SCellConfig may be the same as or similar to that shown in Table 30.

[0342] [Table 30]

[0343] Meanwhile, cell-specific configuration of a serving cell configured as an SpCell to SCell within an MCG or SCG can be performed with reference to the upper layer parameter ServingCellConfigCommon. The upper layer parameter ServingCellConfigCommon can be the same as or similar to those shown in Table 31.

[0344] [Table 31]

[0345] Meanwhile, UE-specific configuration or cell-specific configuration of a serving cell configured as an SpCell to SCell in an MCG or SCG may be performed with reference to the higher layer parameter ServingCellConfig, which may be the same as or similar to those shown in Tables 32 and 33.

[0346] [Table 32]

[0347] [Table 33]

[0348] Meanwhile, cell-specific configuration of a serving cell configured as an SpCell to SCell in an MCG or SCG can be performed with reference to the higher layer parameter ServingCellConfig. The higher layer parameter ServingCellConfig can be the same as or similar to the following:

[0349] DC or CA can be defined within a specific frequency resource. DC or CA can operate within a band (4G band or 5G band) including one or more component carriers (CC). DC or CA operating within a band can be referred to as "intra-band DC" or "intra-band CA." On the other hand, DC or CA can be applied across one or more bands or across a band combination consisting of one or more bands. DC or CA applied across one or more bands or band bundles can be referred to as "inter-band" DC or "inter-band CA."

[0350] Alternatively, DC or CA may operate within one CC. DC or CA operating within one CC can be referred to as "intra-carrier" DC or "intra-carrier CA." Alternatively, DC or CA may be applied across one or more CCs. DC or CA applied across one or more CCs can be referred to as "inter-carrier" DC or "inter-carrier CA."

[0351] On the other hand, DC or CA may operate within one FR (frequency range). DC or CA applied within one FR can be referred to as "intra-FR" DC or "intra-FR CA". On the other hand, DC or CA can be applied across one or more FRs. For example, some cell groups or CCs can be configured to exist in FR1, and the remaining cell groups or CCs can be configured to exist in FR2. DC or CA can be applied across one or more FRs. DC or CA can be referred to as "inter-FR" DC or "inter-FR CA".

[0352] Intra-FR DC / CA, inter-FR DC / CA, intra-band DC / CA, inter-band DC / CA, intra-carrier DC / CA, inter-carrier DC / CA, etc. may be set depending on how far or close the frequency axis distance is between two or more CCs or serving cells simultaneously supported by the UE. The hardware of a communication node such as a UE or a base station may be implemented differently depending on which combination of DC / CA should be supported. Hereinafter, an embodiment of an implementation method of the hardware of a communication node will be described using an implementation method for supporting intra-band CA or inter-band CA, etc., as an example. However, this is merely an example for convenience of explanation, and embodiments of the present invention are not limited thereto.

[0353] In all the embodiments of the present disclosure described below, for convenience of explanation, six types of DU / MT simultaneous operation types are defined as follows: Here, the simultaneously operating DU and MT can be assumed to be co-located (included in one IAB node or can be considered as one IAB node).

[0354] (1) Case A (DU / MT all transmit): Case A may be a case where the IAB-DU and IAB-MT transmit simultaneously at the same time (symbol). In other words, the IAB-DU transmits a downlink signal and the IAB-MT transmits an uplink signal.

[0355] (2) Case B (DU / MT all receive): Case B may be a case where the IAB-DU and IAB-MT receive simultaneously at the same time (symbol). In other words, the IAB-DU receives an uplink signal and the IAB-MT receives a downlink signal.

[0356] (3) Case C (Case CL: DU receive / MT transmit): Case C is a case where the IAB-DU receives and the IAB-MT transmits at the same time (symbol). In other words, the IAB-DU receives an uplink signal and the IAB-MT transmits an uplink signal.

[0357] (4) Case D (DU transmission / MT reception): Case D is a case where the IAB-DU transmits and the IAB-MT receives at the same time (symbol). In other words, the IAB-DU transmits downlink signals and the IAB-MT receives downlink signals.

[0358] (5) Case E (DU / MT FDM required): Case E may be the case where the time-frequency resources of the IAB-DU and the IAB-MT must be frequency division multiplexed (FDM) when the DU / MT operate simultaneously. Case E may be necessary when the interference control capabilities of the DU or MT are relatively limited.

[0359] (6) Case F (DU / MT SDM required): Case F may be the case where the time-frequency resources of the IAB-DU and the IAB-MT must be spatially multiplexed (SDM) when the DU / MT operate simultaneously. Case E may be supported when the interference control capabilities of the DU or MT are relatively good.

[0360] An IAB node (or IAB-DU to IAB-MT) according to an embodiment of the present disclosure can support at least one of six types, Case A to Case F. The IAB node according to an embodiment of the present disclosure can report information related to the supported simultaneous operation type or type combination to an upper IAB node (e.g., IAB donor) or core network (e.g., CU). The example in Table 16 above can be seen as an example of this. Furthermore, the upper IAB node or CU can instruct the IAB node that reported the supported simultaneous operation type or type combination to apply which simultaneous operation type or type combination to which time-frequency resource. This instruction can be set through upper layer signaling or dynamically instructed through L1 / L2 signaling.

[0361] Figure 19a is a conceptual diagram to explain the case where the MT and DU of the IAB node are both in transmission mode, Figure 19b is a conceptual diagram to explain the case where the MT and DU of the IAB node are both in reception mode, Figure 19c is a conceptual diagram to explain the case where the MT of the IAB node is in transmission mode and the DU is in reception mode, and Figure 19d is a conceptual diagram to explain the case where the MT of the IAB node is in reception mode and the DU is in transmission mode.

[0362] 19a to 19d, it is assumed that the IAB node supports four modes of operation among the six cases described above: Case A (1900), Case B (1905), Case C (1910), and Case D (1920).

[0363] First, referring to case A (1900) in Figure 19a, this is a case where both the MT and the DU are in transmit mode. Here, MT may refer to IAB-MT, and DU may refer to IAB-DU. Therefore, this may be a situation where the DU in Figure 19a transmits a downlink signal, and the MT transmits an uplink signal. As illustrated in Figure 19a, since the DU transmits a downlink signal, it can perform downlink transmission with a higher transmit power than the MT transmitting an uplink signal. In Figure 19a, the strength of the transmit power is indicated by the thickness of the arrow. Therefore, this may be a case where the DU has a higher transmit power.

[0364] Referring to case B (1905) in Figure 19b, both MT and DU are in receive mode. Here, MT may refer to IAB-MT, and DU may refer to IAB-DU. Therefore, in Figure 19b, the DU receives an uplink signal and the MT receives a downlink signal. In Figure 19b, the received power strength is indicated by the thickness of the arrow, but the difference in the received signal strength may be large or the same.

[0365] Referring to case C (1910) in Figure 19c, the MT is in the transmit mode and the DU is in the receive mode. Here, MT may refer to IAB-MT, and DU may refer to IAB-DU. Therefore, in Figure 19c, the DU receives an uplink signal and the MT transmits an uplink signal. In Figure 19c, the strength of the received power is also indicated by the thickness of the arrow. As illustrated in Figure 19c, the transmit power of the MT may be greater than the receive power of the DU.

[0366] Referring to case D (1910) in Figure 19d, the MT is in the receiving mode and the DU is in the transmitting mode. Here, MT may refer to IAB-MT, and DU may refer to IAB-DU. Therefore, this is a situation in which the DU in Figure 19d transmits a downlink signal and the MT receives a downlink signal. In Figure 19d, the strength of the received power is also indicated by the thickness of the arrow. As illustrated in Figure 19d, this may be the case where the transmission power of the DU is greater than the reception power of the MT.

[0367] In the situations of Figures 19a to 19d, the IAB node may need to measure and report uplink-downlink interference (CLI) due to DU / MT transmission and reception operations. For example, when the IAB node operates in Case A (1900), the MT can transmit (uplink, as a signal is transmitted from the MT to the DU) and the DU can transmit (downlink, as a signal is transmitted from the DU to the MT or UE) simultaneously. Therefore, CLI may occur due to such simultaneous operations. In this case, since both the DU and MT are transmitting, measurement of CLI can be performed by any one of the DU, MT, or UE located in a different location.

[0368] On the other hand, when the IAB node operates in case B (1905), the MT receives (downlink as a signal is transmitted from the DU to the MT) and the DU receives (uplink as a signal is transmitted from the MT or UE to the DU) simultaneously, which causes CLI (1920). At this time, the CLI of the interference (1920) that the uplink signal received by the DU causes to the MT receiving the downlink signal requires standard support for measurement and reporting.

[0369] 5G NR systems are likely to experience UL-DL interference (CLI) due to dynamic TDD, full duplex, IAB DU / MT simultaneous operation, etc. Therefore, CLI measurement and reporting functions must be supported to prevent performance degradation due to CLI.

[0370] Among the 5G NR standards, Rel-16 NR supports two CLI measurement methods as follows:

[0371] 1) CLI-received signal strength indicator (CLI-RSSI) measurement

[0372] 2) SRS-reference signal received power (SRS-RSRP) measurement

[0373] In both of the above methods, layer 3 (L3) filtering is applied, and measurement and reporting can be performed based on time / frequency resources according to the detailed settings in Tables 25 and 26 below. In addition, reporting of measurement values ​​supports event-triggered and periodic reporting, and measurement and reporting can be applied when operating NR multiple cells such as CA / DC.

[0374] Table 34 shows an example of setting parameters related to SRS-RSRP measurements.

[0375] [Table 34]

[0376] Table 35 shows an example of setting parameters related to CLI-RSSI measurement.

[0377] [Table 35]

[0378] The 3GPP TS38.473 standard provides F1 application protocol (F1AP) signaling as shown in Table 33 below.

[0379] Through the F1AP illustrated in Table 33, the gNB-DU can report / transmit information to be considered when mitigating CLI to the gNB-CU (or the gNB-CU can report / transmit to the gNB-DU, or the gNB-DU can report / transmit to another gNB-DU). Here, CLI mitigation can include CLI measurement / reporting and subsequent implementation.

[0380] Here, the information to be considered when reducing the CLI can be conveyed by the "intended TDD DL-UL configuration", which can include information such as SCS, CP, and TDD UL-DL slot configuration.

[0381] [Table 36]

[0382] Referring to Table 33, "Intended TDD DL-UL Configuration" can include DL / UL symbol information for one or more slots, in other words, a slot configuration list including TDD DL-UL pattern information. If a slot includes both DL and UL symbols, whether the DL symbols from the beginning of the slot and the previous symbols from the end of the slot are UL symbols can be indicated through the parameters "Number of DL Symbols" and "Number of UL Symbols," respectively.

[0383] Meanwhile, the TS38.473 standard among the 3GPP standards can provide F1AP signaling as shown in Tables 37 and 38 below, through which an IAB node can transmit resource configuration information (gNB-DU cell resource configuration) for the cell(s) supported by the gNB-DU of the corresponding IAB node to an upper IAB node (e.g., IAB donor, parent node, gNB-CU) or a neighboring IAB node. In other words, an IAB node can report / transmit information on TDD / FDD resource parameters for each activated cell to an upper IAB node or a neighboring IAB node through F1AP signaling.

[0384] [Table 37]

[0385] [Table 38]

[0386] Referring to Tables 37 and 38, the resource allocation information can include DUF (downlink / uplink / flexible) configuration information for one or more slot lists that are repeated at a specific period (DUF transmission periodicity). In this case, 'maxnoofDUFSlots' in Table 28 is the maximum number of slots within 10 ms and can be defined as 320, and 'maxnoofHSNASlots' is the maximum number of H / S / NA slots within 160 ms and can be defined as 5120.

[0387] The number of downlink symbols and the number of uplink symbols in one slot can be set by the parameters 'Number of Downlink Symbols' and 'Number of Uplink Symbols', respectively. In addition, if the permutation parameter is set to 'DFU', downlink symbols can be placed at the beginning of the slot and uplink symbols can be placed at the end of the slot. Conversely, if the permutation parameter is set to 'UFD', uplink symbols can be placed at the beginning of the slot and downlink symbols can be placed at the end of the slot. Refer to Table 30 for other parameters and detailed setting values.

[0388] The 3GPP Rel-17 standard specifies that the HSNA slot configuration in Table 30 can be extended to the frequency domain to support simultaneous operation of the IAB-DU and IAB-MT. In other words, the 3GPP Rel-17 standard specifies that the HSNA slot configuration can be extended to the frequency domain so that the IAB-DU resources and IAB-MT resources can support not only TDM but also FDM or SDM. A base station or upper node can configure or indicate one or more RB sets or RB set groups to which a frequency-domain HSNA configuration is applied. In addition, the base station or upper node can indicate to the IAB-MT of the lower node whether one or more frequency-domain soft resources are available for one or more RB sets and / or RB set groups within a specific time resource. This indication can be indicated to the IAB-MT of the lower node via an availability indicator in an extended form in DCI format 2_5.

[0389] At this time, when the IAB-node receives DCI format 2_5, it can use the RB set, RB set group and / or slot that the availability indicator indicates as available as the IAB-DU resource of the corresponding IAB-node.

[0390] Meanwhile, the 3GPP Rel-17 standard introduced the following additional functions to support the use of IAB-DU resources and IAB-MT resources in FDM or SDM in addition to TDM when the IAB-DU and IAB-MT operate simultaneously: For example, a transmission timing adjustment method, FDM through frequency axis resource allocation, additional PDSCH power adjustment (DL Tx power adjustment) other than PDSCH power setting through higher layer parameters (powerControlOffset), and desired uplink PSD (power spectral density) reporting. The details of these functions are summarized as follows:

[0391] The gNB determines the desired Timing Advance (TA) setting and provides it to the UE / IAB-MT, which uses the provided TA to determine the uplink transmission timing relative to the downlink reception timing observed by the UE / IAB-MT.

[0392] An IAB node can support additional modes for uplink timing.

[0393] The IAB-MT determines the uplink transmission timing using the provided TA and the provided additional offset, facilitating IAB-MT receive x / IAB-DU receive multiplexing of the upper node.

[0394] The IAB-MT aligns its uplink transmission timing with the IAB-DU downlink transmission timing to facilitate IAB-MT transmission / IAB-DU transmission multiplexing.

[0395] The IAB node uplink timing mode is indicated by the upper node through the MAC-CE.

[0396] If the IAB-DU and IAB-MT of an IAB node are subject to half-duplex constraints, correct transmission / reception on one side cannot be guaranteed while the other side is transmitting / receiving, and vice versa. For example, when they are located and operating on the same frequency. If an IAB node supports enhanced frequency or spatial multiplexing capabilities, additional multiplexing modes may be supported. For example, IAB-MT receive / IAB-DU receive, IAB-MT transmit / IAB-DU transmit, IAB-MT receive / IAB-DU transmit, or IAB-MT transmit / IAB-DU receive may be supported. An IAB node can report duplex constraints between the IAB-MT and IAB-DU via F1AP. An IAB node can indicate via F1AP whether FDM is required for enhanced multiplexing.

[0397] The IAB-DU or IAB-donor-DU scheduler adheres to the gNB-DU resource configuration received via the F1AP, which defines the use of scheduling resources to account for the duplication constraints described above.

[0398] The resource configuration assigns hard, soft or unavailable attributes to each symbol of each DU cell.

[0399] Hard-configured symbols allow transmission / reception, while unavailable symbols prevent scheduling except in special cases. For soft-configured symbols, scheduling can occur conditionally based on an explicit availability indication from the upper node via DCI type 2_5 or an implicit availability decision from the IAB node. The implicit availability decision is made by the IAB node based on whether the IAB-DU's operation affects the co-located IAB-MT.

[0400] Resource configurations may be shared among neighboring IAB nodes and IAB donors to facilitate interference management, dual connectivity, and enhanced multiplexing.

[0401] To facilitate transitions from IAB-MT to IAB-DU operation and vice versa, guard symbols can be used to overcome potentially misaligned symbol boundaries between the IAB-MT and IAB-DU domains (e.g., the IAB-MT receiving boundary is not aligned with the IAB-DU transmitting boundary). Specifically, an IAB node can indicate to its parent node the number of guard symbols it desires, while the parent node can indicate to the IAB node the number of guard symbols actually provided for a particular transition.

[0402] An IAB node that supports enhanced multiplexing functions, i.e., IAB-MT receive / IAB-DU receive, IAB-MT transmit / IAB-DU transmit, IAB-MT receive / IAB-DU transmit, and IAB-MT transmit / IAB-DU receive, can provide upper node information via MAC-CE to facilitate scheduling of enhanced multiplexing operations by the IAB node, particularly as follows:

[0403] -IAB-MT transmit / receive (Tx / Rx) beams are recommended.

[0404] -Desired IAB-MT transmission PSD range,

[0405] - IAB-DU transmit power adjustment of the desired upper node;

[0406] -IAB-MT uplink transmission timing mode is required.

[0407] Accordingly, the parent node may provide MAC-CE information to the IAB node to facilitate improved multiplexing at the IAB node and / or parent node:

[0408] - Limited IAB-DU Tx beam,

[0409] - Actual upper node IAB-DU Tx power adjustment,

[0410] -IAB-MT uplink transmission timing mode.

[0411] Meanwhile, in 5G NR, a base station (or relay station such as an IAB node) can be controlled to report channel state information (CSI) to a terminal (UE, user equipment) or mobile terminal (MT) using specific time / frequency resources. Hereinafter, for convenience of explanation, a relay station having general base station functions such as an eNB or gNB, or a relay station having some or all of the base station functions such as an IAB node (IAB-DU, IAB-MT) or repeater, will be referred to as a relay station. Also, for convenience of explanation, various types of terminals, such as a user equipment (UE) consisting of a mobile equipment (ME) and a UMTS subscriber identity module (USIM), a mobile equipment (ME) consisting of a mobile terminal (MT) and terminal equipment (TE), or an MT including a mobile communication function unit, will be referred to as a terminal.

[0412] The CSI may be composed of some or all of a channel quality indicator (CQI), a precoding matrix indicator (PMI), a CSI-RS resource indicator (CRI), a SS / PBCH block resource indicator (SSBRI), a layer indicator (LI), a rank indicator (RI), a layer-1 reference resource received power (L1-RSRP), and a layer-1 signal-to-noise and interference ratio (L1-SINR). The UE can receive, from a higher layer of the base station, a trigger configuration (e.g., CSI-AperiodicTriggerStateList or CSI-SemiPersistentOnPUSCH-TriggerStateList) including N (N is 1 or more) reporting configurations (CSI-ReportConfig Reporting Settings), M (M is 1 or more) resource configurations (CSI-ResourceConfig Resource Settings) and a list of one or more trigger states for CSI reporting.

[0413] Each reporting configuration CSI-ReportConfig can be configured with some or all of the higher layer parameters shown in Tables 39 to 41 below.

[0414] [Table 39]

[0415] [Table 40]

[0416] [Table 41]

[0417] Each resource configuration CSI-ResourceConfig can be configured with some or all of the higher layer parameters shown in Tables 42 to 44 below.

[0418] [Table 42]

[0419] [Table 43]

[0420] [Table 44]

[0421] The trigger configuration (CSI-AperiodicTriggerStateList or CSI-SemiPersistentOnPUSCH-TriggerStateList) can be configured with some or all of the higher layer parameters such as those in Tables 45 and 46 below.

[0422] [Table 45]

[0423] [Table 46]

[0424] In 5G NR, the base station can configure the terminal to derive the CQI according to one of Tables 47 to 50.

[0425] [Table 47]

[0426] [Table 48]

[0427] [Table 49]

[0428] [Table 50]

[0429] In this case, a combination of a modulation scheme and a transport block size that satisfies the following conditions corresponds to one of the CQI indexes in Tables 47 to 50:

[0430] Condition 1: The combination is indicated for PDSCH transmission within a CSI reference resource;

[0431] Condition 2: The modulation scheme is indicated by the CQI index,

[0432] ●Condition 3: When the combination of the transport block size and modulation method is applied to the reference resource, the effective channel code rate calculated based on this is closest to the code rate indicated by the CQI index.In this case, if two or more combinations of transport block size and modulation method are calculated to be closest to the code rate indicated by the CQI index, only the combination consisting of the smallest transport block size among the combinations is valid.

[0433] If the upper layer parameter timeRestrictionForChannelMeasurements is set to notConfigured in a certain reporting configuration and no time-domain measurement restriction is applied to the channel measurement resource (CMR) of the corresponding reporting configuration, when performing channel measurement for calculating the CSI value to be reported in uplink slot n, the UE shall only consider and guide the NZP CSI-RS (non-zero power CSI-RS) resource(s) that are located at the same time as or before the CSI reference resource among the NZP CSI-RS (non-zero power CSI-RS) resources included in the CMR.

[0434] If the upper layer parameter timeRestrictionForChannelMeasurements is set to Configured in a certain reporting configuration and time domain measurement restrictions are applied to the CMR of the corresponding reporting configuration, when performing channel measurement for calculating the CSI value to be reported in uplink slot n, the UE shall only consider and guide the most recent NZP CSI-RS resource (the most recent occasion) that is located at the same time as or earlier than the CSI reference resource among the NZP CSI-RS (non-zero power CSI-RS) resources (occasions) included in the CMR.

[0435] If the upper layer parameter timeRestrictionForInterferenceMeasurements is set to notConfigured in a reporting configuration and no time domain measurement restriction is applied to the interference measurement resource (IMR) of the corresponding reporting configuration, when performing interference measurement for calculating the CSI value to be reported in uplink slot n, the UE shall only consider and guide the resource(s) located at the same time as or before the CSI reference resource among the CSI-IM and / or non-zero power CSI-RS (NZP CSI-RS) resources included in the IMR.

[0436] If the upper layer parameter timeRestrictionForInterferenceMeasurements is set to Configured in a certain reporting configuration and a time domain measurement restriction is applied to the IMR of the corresponding reporting configuration, when performing interference measurement for calculating the CSI value to be reported in uplink slot n, the UE shall only consider and guide the most recent resource (the most recent occasion) that is located at the same time as or earlier than the CSI reference resource among the CSI-IM and / or NZP CSI-RS (non-zero power CSI-RS) resources included in the IMR.

[0437] For a serving cell, the CSI reference resource may be defined as follows:

[0438] ●In the frequency axis, the CSI reference resource is defined as the downlink PRB group of the band related to the corresponding CSI to be derived.

[0439] JPEG2026506518000072.jpg158161

[0440] A slot that satisfies the following conditions in a serving cell is considered a valid downlink slot:

[0441] Condition 1: Contains at least one D (downlink) or F (flexible) symbol set in a higher layer,

[0442] ●Condition 2: A slot that is not included in the measurement gap set for the device in question.

[0443] If there is no valid downlink slot for the CSI reference resource of the CSI reporting configuration in a serving cell, the CSI report for the corresponding serving cell in uplink slot n' is omitted.

[0444] When configured to report CQI, the terminal assumes the following items for the purpose of deriving the corresponding CQI and the associated RI and PMI within the corresponding CSI reference resource:

[0445] ●Item 1: The first two OFDM symbols are used for control signal transmission.

[0446] Item 2: The number of symbols for PDSCH and DMRS is 12.

[0447] ●Item 3: The same BWP, subcarrier spacing, and CP length as set for PDSCH reception.

[0448] ● Item 4: The same bandwidth as configured for CQI reporting.

[0449] ●Item 5: There is no RE usage for SSB, NZP CSI-RS, or ZP CSI-RS.

[0450] ●Item 6: Redundancy version 0.

[0451] ● Item 7: The ratio between PDSCH EPRE and CSI-RS EPRE follows the higher layer configuration (Pc, powerControlOffset) value.

[0452] ● Item 8: Refer to the maxLength parameter and dmrs-AdditionalPosition setting in the DMRS-DownlinkConfig setting for the DMRS pattern.

[0453] ● Item 9: There is no DMRS in the PDSCH symbol.

[0454] ●Item 10: Assume that the PRB bundling size is 2 PRB.

[0455] ●Item 11: The PDSCH signals transmitted on PDSCH antenna ports [1000, ..., 1000+v-1] for v layers satisfy the relationship of the following equation 5 with the signals transmitted on CSI-RS antenna ports [3000, ..., 3000+P-1].

[0456]

number

[0457] Here, W(i) is the precoding matrix pointed to by the PMI, and P is the number of CSI-RS ports in the CSI-RS resource.

[0458] JPEG2026506518000074.jpg154161

[0459]

number

[0460] Each CSI report has a priority value according to the following rule (lower value has higher priority). When two different CSI reports collide and the two different CSI reports are combined into one CSI report by the base station configuration, or when one of the two CSI reports is selected, the priority value can be referenced to adjust the CSI content to fit the CSI payload, or one of the two CSI reports can be selected.

[0461] JPEG2026506518000076.jpg15161

[0462] y=0 for aperiodic CSI reporting transmitted via PUSCH, y=1 for semi-persistent CSI reporting transmitted via PUSCH, y=2 for semi-persistent CSI reporting transmitted via PUCCH, and y=3 for periodic CSI reporting transmitted via PUCCH;

[0463] k=0 for CSI reports carrying L1-RSRP or L1-SINR, and k=1 for CSI reports not carrying L1-RSRP or L1-SINR;

[0464] c is the serving cell index and N cells is the value of the upper layer parameter maxNrofServingCells;

[0465] s is the reportConfigID and is the value of the upper layer parameter maxNrofCSI-ReportConfigurations.

[0466] JPEG2026506518000077.jpg14161

[0467] Two CSI reports are said to collide if the time occupancy of the physical channels scheduled to carry the CSI reports overlaps by at least one OFDM symbol and are transmitted on the same carrier. When a UE is configured to transmit two colliding CSI reports,

[0468] If the y values ​​differ between two CSI reports, the following rules apply except when one of the y values ​​is 2 and the other is 3 (for CSI reports transmitted via PUSCH, as explained in clause 5.2.3; for CSI reports transmitted via PUCCH, as explained in clause 5.2.4):

[0469] JPEG2026506518000078.jpg9161

[0470] ● Otherwise, the two CSI reports are multiplexed or one of the two is dropped according to the priority value, as described in clause 9.2.5.2 of [TS 38.213].

[0471] If the semi-persistent CSI report transmitted over the PUSCH overlaps in time with the PUSCH data transmission in one or more symbols on the same carrier, and 2、1 d is a PUSCH carrying semi-permanent CSI reports and d is a PUSCH associated with data transmission. 2、1 The earliest symbol of such a PUSCH channel after the last symbol of the DCI scheduling the PUSCH is N2+d 2、1 If the CSI report starts later than the symbol, then the CSI report is not transmitted by the UE, otherwise this is an error case if certain requirements are not met.

[0472] If the UE transmits a first PUSCH including a semi-persistent CSI report and a second PUSCH including the UL-SCH and the first PUSCH transmission overlaps in time with the second PUSCH transmission, the UE transmits the second PUSCH without transmitting the first PUSCH. The UE expects that the first and second PUSCH transmissions will satisfy the timing conditions for the overlapping PUSCH transmissions if at least one of the first or second PUSCH transmissions responds to DCI format detection by the UE.

[0473] JPEG2026506518000079.jpg57161

[0474] The number of CPUs required for each CSI report is as follows:

[0475] CSI reporting processing involves multiple CPUs being dedicated to multiple symbols, as follows:

[0476] In the case of a CSI report with a CSI-ReportConfig with the upper layer parameter reportQuantity set to "none" and a CSI-RS-ResourceSet with the upper layer parameter trs-Info configured, CPU =0

[0477] For CSI reports with a CSI-ReportConfig with the higher layer parameter reportQuantity set to "cri-RSRP", "ssb-Index-RSRP", "cri-SINR", "ssb-Index-SINR" or "none" (and a CSI-RS-ResourceSet with the higher layer parameter trs-Info not configured). CPU =1

[0478] ● In case of CSI reporting using CSI-ReportConfig with upper layer parameter ReportQuantity set to "cri-RI-PMI-CQI", "cri-RI-i1", "cri-RI-i1-CQI", "cri-RI-CQI" or "cri-RI-LI-PMI-CQI",

[0479] JPEG2026506518000080.jpg48161

[0480] When the CSI-ReportConfig is configured with codebookType set to 'typeI-SinglePanel' and the corresponding CSI-RS resource set for channel measurement is configured with two resource groups and N resource pairs, CPU = 2N + M, where M is defined in Section 5.2.1.4.2]

[0481] ● If not, O CPU =K s , where K s is the number of CSI-RS resources in the CSI-RS resource set for channel measurement.

[0482] For CSI reporting with CSI-ReportConfig where the upper layer parameter ReportQuantity is not set to "none", the CPU is occupied relative to the number of OFDM symbols as follows:

[0483] ●Periodic or semi-permanent CSI reporting (excluding initial semi-permanent CSI reporting for PUSCH after PDCCH that triggers the report) occupies the CPU(s) from the first symbol of the earliest of each CSI-RS / CSI-IM / SSB resource for channel or interference measurement, until the last symbol of the configured PUSCH / PUCCH that transmits the report, in each recent CSI-RS / CSI-IM / SSB opportunity that is not later than the corresponding CSI reference resource.

[0484] Aperiodic CSI reporting occupies the CPU from the first symbol after the PDCCH that triggers the CSI report to the last symbol of the reserved PUSCH that carries the report. If a PDCCH candidate is associated with the search space set configured by searchSpaceLinking, the PDCCH candidate that ends later in time of the two linked PDCCH candidates is used to determine the CPU occupation period.

[0485] After the PDCCH trigger, the initial semi-persistent CSI report for the PUSCH occupies the CPU(s) from the first symbol after the PDCCH to the last symbol of the reserved PUSCH transmitting the report. If a PDCCH candidate is associated with the search space set configured by searchSpaceLinking, the PDCCH candidate that ends later in time of the two linked PDCCH candidates is used to determine the CPU occupation period.

[0486] For CSI reporting with a CSI-ReportConfig with the higher layer parameter reportQuantity set to "none" and a CSI-RS-ResourceSet with the higher layer parameter trs-Info not configured, the CPU is occupied relative to the number of OFDM symbols as follows:

[0487] ●Semi-persistent CSI reporting (excluding initial semi-persistent CSI reporting for PUSCH after PDCCH that triggers reporting) occupies the CPU(s) from the first symbol of the earliest symbol among each transmission time of periodic or semi-persistent CSI-RS / SSB resources for channel measurement for L1-RSRP calculation, and from the last symbol of the latest resource among CSI-RS / SSB resources for channel measurement for L1-RSRP calculation in each transmission situation until Z3' symbols.

[0488] Aperiodic CSI reporting occupies the CPU from the first symbol to the last symbol after the PDCCH that triggers the CSI report, between Z3 symbols after the first symbol after the PDCCH that triggers the CSI report and Z3' symbols after the last symbol of the most recent resource among each CSI-RS / SSB resource for channel measurement for L1-RSRP calculation.

[0489] where (Z3, Z3') are defined in Table 5.4-2.

[0490] In any slot, the UE is not expected to have more active CSI-RS ports or active CSI-RS resources of active BWPs than those reported in the capabilities. NZP CSI-RS resources are activated for a period defined as follows: For aperiodic CSI-RS, it starts from the end of the PDCCH containing a request and ends at the end of the reserved PUSCH containing a report related to this aperiodic CSI-RS. If a PDCCH candidate is associated with the search space set configured in searchSpaceLinking, the PDCCH candidate that ends later in time is used to determine the NZP CSI-RS resource activation period. For semi-persistent CSI-RS, it starts from the time an activation command is applied and ends when a deactivation command is applied. It starts when periodic CSI-RS starts and ends when the periodic CSI-RS configuration is deactivated. If a CSI-RS resource is referenced N times by one or more CSI reporting configurations, the CSI-RS resource and the CSI-RS ports within the CSI-RS resource are calculated N times. For a CSI-RS resource set for channel measurement consisting of two resource groups and N resource pairs, if one of the M CSI-RS resources references a CSI-RS resource X times, where M is defined in Section 5.2.1.4.2 and / or one or two resource pairs, the CSI-RS resource and the CSI-RS port within the CSI-RS resource are calculated X times.

[0491] As described above, the CSI reported in uplink slot n may be derived by assuming (or considering) various factors including the following elements as specific values, and in the following description of the present disclosure, elements assumed by the UE when generating CSI are referred to as CSI components. The following are examples of CSI components, and in actual application, the CSI components are not limited thereto and may include various other elements provided in the present disclosure.

[0492] Frequency and time axis positions of CSI reference resources

[0493] ●Position of valid downlink slots

[0494] ●CMR / IMR transmission / measurement location (whether minimum delay requirements are met, etc.)

[0495] Priority between each CSI

[0496] Number of CPUs used for each CSI calculation, maximum number of CPUs supported by the device, number of CPUs currently occupied, whether CSI reporting is instructed / activated, whether multi-TRP CSI calculation is enabled

[0497] ●Downlink power control setting value (egpowerControlOffset)

[0498] ●DRX (discontinuous reception) settings, etc.

[0499] Radio resources in a mobile communication system can use variable transmission modes to handle various situations, such as integrated access and backhaul (IAB) node operation, multiple transmission and reception point (multi-TRP) operation, and in-band or out-band full duplex communication operation. Meanwhile, a transceiver (or base station or terminal) in the mobile communication system can operate with differences in time, frequency, space, and power resources for wireless communication, such as using different numbers of antennas, antenna shapes, and transmission power according to each transmission mode (or according to instructions from the base station considering each transmission mode) to improve wireless communication quality. 5G NR to 6G communications require the ability to dynamically switch between these various transmission modes to enhance wireless communication quality and capacity while ensuring robustness and resilience in various communication environments. In this case, there is a high probability that the various transmission modes will use different values ​​for the aforementioned "factors included in CSI derivation" for each mode, which may lead to inconsistencies between operations such as "semi-static CSI measurement / reporting (e.g., periodic CSI-RS or periodic CSI report) and dynamic transmission mode change or activation (e.g., dynamic operation mode indication / activation)," which may degrade CSI reporting performance.

[0500] The present disclosure provides a method for measuring and reporting channel state information to efficiently support dynamically variable transmission modes. By using one of the methods provided in the present disclosure, a base station and a terminal can perform various operations, such as determining the validity of a channel state report by referring to a transmission mode change time and a channel / interference measurement time, determining the priority of the corresponding channel state report, and determining the amount of (computational) resources of the terminal required for the corresponding channel state report, thereby improving wireless communication quality.

[0501] Although the subject of application of the method provided in the following disclosure has been described as a base station or a terminal, this is for convenience of explanation, and when applied to future beyond 5G or 6G mobile communication technologies, it is not limited to this and may be replaced with wireless communication between similar other devices, for example, a base station may be (upper node) IAB-DU, repeater-DU, or repeater-RU (remote unit, RF unit), and a terminal may be replaced with user equipment (UE), mobile equipment (ME), mobile terminal (MT), (lower node) IAB-MT, or repeater-MT, and may be extended and applied in a similar manner.

[0502] As an example, when the contents of the present disclosure are applied to an IAB network, the operation of "a base station configuring a higher layer to a terminal through RRC or MAC CE signaling" can be replaced with the operation of "a CU or an upper node IAB-DU (or a certain IAB-node) configuring a higher layer to a lower node IAB-MT (or a neighboring IAB-node) through F1AP signaling."

[0503] As another example, when the present disclosure is applied to an IAB network, the operation of "a terminal reporting to a base station through a PUSCH or PUCCH" can be replaced with the operation of "an IAB-MT of a lower node (or an IAB-MT of a certain IAB-node) reporting to a CU or an IAB-DU of an upper node (or an IAB-DU of a neighboring IAB-node) through a PUSCH or PUCCH." Specific examples of various other possible operations will be omitted to avoid obscuring the gist of the description.

[0504] First embodiment: Method for determining operation mode for CSI reporting

[0505] In the first embodiment, when a base station allocates one or more operation modes to a terminal within a specific resource interval, a method for determining an operation mode to be assumed when inducing / generating / calculating CSI reporting for the corresponding resource will be described in detail.

[0506] In the embodiments described below, the base station may be replaced by a CU or an upper node, and the terminal may be replaced by a lower node or an IAB-MT of an IAB-node. A specific resource interval may include one or a combination of time resources, frequency resources, spatial resources, and code resources. For example, a specific combination such as a time-frequency resource interval may be possible. Assigning an operation mode may be understood as configuring an operation mode, activating an operation mode, indicating an operation mode, etc. For example, configuring an operation mode may be performed through RRC. As another example, activating an operation mode may be performed through MAC CE. As yet another example, indicating an operation mode may be performed through DCI and / or MAC CE. A method for determining an operation mode may also be provided through a combination of RRC, MAC CE, and DCI.

[0507] FIG. 20 is a conceptual diagram illustrating a method in which a base station allocates one or more operation modes to a terminal within a resource interval.

[0508] Referring to FIG. 20, a base station can allocate specific resources to operation mode A (2000). In other words, the base station can allocate specific time / frequency / space / code resources 2000 to operation mode A. Operation mode A can be a basic mode and can be "committed to have the highest priority." Because operation mode A is a basic mode, it can be applied independently of any one of configuration, activation, or instruction. Also, because operation mode A is a basic mode, it can be a default mode and can fall back to other modes. Furthermore, the resources allocated to operation mode A can be at least one or a combination of two or more of time / frequency / space / code resources.

[0509] As illustrated in Fig. 20, operation mode B may be a mode that uses a portion of the resources in operation mode A, and operation mode C may also be a mode that uses a portion of the resources in operation mode A. Some of the resources in operation mode B and operation mode C may overlap as shown by reference numeral 2015. The remaining resources in operation mode B and operation mode C excluding the overlapping resources as shown by reference numeral 2015 are shown as an example where the remaining resources in operation mode B and operation mode C are mutually prime.

[0510] A base station can assign operation mode B as an additional operation mode in addition to operation mode A according to its capabilities. Also, a base station can assign operation mode C as an additional operation mode in addition to operation mode A according to its capabilities. For example, a base station can assign only operation mode A, or it can assign operation mode A and additionally assign operation mode B. As another example, a base station can assign operation mode A and additionally assign operation mode C. As yet another example, a base station can assign operation mode A, additionally assign operation mode B, and also assign operation mode C. The order of assignment of operation modes B and C, excluding operation mode A, which is the basic mode, can be simultaneous or sequential.

[0511] As explained above, when two or three modes of operation are allocated, there may be overlapping resources available for use in the two or three modes.

[0512] For example, if operating mode A and operating mode B are assigned, the overlapping resources may be resources 2005 for operating mode B. As another example, if operating mode A and operating mode C are assigned, the overlapping resources may be resources 2010 for operating mode C. As yet another example, if operating mode A, operating mode B, and operating mode C are all assigned, there may be overlapping resources 2015 for all three modes.

[0513] The mode change may be performed by dynamically changing the operation mode applied to a specific resource by the MAC CE and / or DCI. The operation modes described in the present disclosure may take various forms.

[0514] For example, the types of operation modes may be classified according to the applied IAB DU / MT multiplexing mode. Here, the multiplexing mode may include at least one of TDM, FDM, and SDM. For another example, the types of operation modes may be classified according to the IAB FDM resource configuration (whether or not the frequency domain HSNA configuration is applied). For yet another example, the types of operation modes may be classified according to the frequency or time resource configuration for duplex improvement. Here, the frequency or time resource configuration may be expressed as XDD, which may include FDD, TDD, subband full-duplex (SBFD), and full-duplex (FD). Here, FD may include in-band full-duplex.

[0515] As yet another example, the types of operation modes may be classified according to whether or not a downlink transmit power adjustment (DL TX power adjustment) setting is applied. As yet another example, the types of operation modes may be classified according to whether or not a restricted / desired DU / MT beam setting is applied. As yet another example, the types of operation modes may be classified according to whether or not a UL PSD range setting is applied. As yet another example, the types of operation modes may be classified according to whether or not a case #1 / #6 / #7 timing setting is applied. As yet another example, the types of operation modes may be classified according to whether or not they are included in a slot list indicated by one of the IAB MAC CEs.

[0516] Although various types of operation modes have been described above, and only one independent type of operation mode has been described, two or more types of operation modes may be combined and classified.

[0517] Meanwhile, the types of operation modes and resources corresponding to the operation modes described above can be provided to the UE through higher layer signaling.

[0518] FIG. 21 is a conceptual diagram illustrating a method in which a base station allocates resources to a terminal according to an operation mode using time-frequency resources.

[0519] Referring to FIG. 21, the horizontal axis represents time and the vertical axis represents frequency. Although FIG. 21 illustrates both slots and symbols, for convenience of explanation, only slots will be used in the following description. However, slots may be understood as a plurality of symbols. On the time axis of FIG. 21, a first time region in which only downlink (DL) slots are transmitted may be arranged, followed by a second time region in which only uplink (UL) slots are transmitted, and then a third time region in which mixed downlink and uplink slots are transmitted. In the third time region, mixed downlink and uplink slots may be divided into downlink slots and uplink slots according to frequency. FIG. 21 illustrates an example in which the first to third time regions are repeated twice. For convenience of explanation, the repeated time regions will be referred to as the fourth, fifth, and sixth time regions, respectively, starting from the third time region.

[0520] A base station can set a specific time period to operate in a time-domain duplex (TDD) mode 2100. In this case, the TDD mode is assumed to be operation mode A described in FIG. 20. In the TDD mode 2100, which is operation mode A, resources in the first, second, fourth, and fifth time domains can be allocated.

[0521] The third and sixth time domains can operate in an improved duplex mode 2110. In the following description, the improved duplex mode will be referred to as operation mode B. The improved duplex mode 2110 can include various cases such as flexible duplex modes including XDD (FDD, TDD, and subband full-duplex) and FD mode.

[0522] Since the base station uses the improved duplex mode 2110, it can allocate downlink slots or symbols to a specific terminal (group) using a specific frequency resource (group) in the same time interval, for example, the third time region or the sixth time region, and allocate uplink slots or symbols to other terminals (groups) using other frequency resources (groups) in the same time interval. As a specific example, the base station can allocate downlink slots or symbols to terminal group A in the third time region and allocate downlink slots or symbols to terminal group B in the third time region. Terminal group A can include at least one terminal, and terminal group B can include at least one terminal not included in terminal group A.

[0523] As described above, in order to allocate individual resources to different terminals in the same resource region according to operation modes, the base station may allocate resources semi-statically to each terminal or each terminal group based on higher layer signaling (e.g., F1AP, RRC, or MAC CE). As another example, the base station may dynamically allocate resources to each terminal or each terminal group based on layer 2 (L2) signaling (e.g., MAC CE) or layer 1 (L1) signaling (e.g., DCI).

[0524] In this case, each operation mode may be associated with a set of CSI components (elements that a UE must assume when generating CSI) with different values. In this case, the base station needs to receive separate CSI reports for resource intervals 2100 and 2110 to improve wireless transmission efficiency.

[0525] In the event that the resource allocation characteristics of the CSI measurement and reporting, e.g., periodic CSI reporting based on periodic CMR / IMR measurements, do not match the resource allocation characteristics of the operation mode, e.g., dynamic operation mode resource allocation. As another example, the resource allocation / change timing of the CSI measurement and reporting, e.g., CSI measurement / reporting configuration is configured in slot n, and the resource allocation / change timing of the operation mode, e.g., operation mode resources are allocated in slot n+N, may not match. In such a case, the terminal or base station needs to determine which CSI component (set) the CSI report is associated with.

[0526] Meanwhile, the types of operation modes and resources corresponding to the operation modes described above can be provided to the UE through higher layer signaling.

[0527] FIG. 22 is a conceptual diagram illustrating a method in which a base station allocates resources to a terminal according to an operation mode by using frequencies-slots (or symbols).

[0528] Referring to Figure 22, the horizontal axis represents time based on downlink (DL) slots or symbols, and the vertical axis represents frequency. For convenience of explanation, slots will be used in the description of Figure 22. However, as illustrated in Figure 22, a slot can be understood as a number of symbols.

[0529] On the slot-based time axis of Figure 22, a first slot region for IAB-DU operation may be arranged, followed by a second slot region for IAB-MT operation, and then a third slot region where IAB-DU operation and IAB-MT operation are mixed. In the third slot region, IAB-DU operation and IAB-MT operation may be separated by frequency and resources may be allocated. Figure 22 illustrates an example in which the first to third slot regions are repeated twice. For convenience of explanation, the repeated slot regions will be referred to as the fourth, fifth, and sixth slot regions, starting from the third slot region.

[0530] A base station can perform operation between IAB-DU operation and IAB-MT operation in time division multiplexing (TDM) mode. For example, the first and second slot regions and the fourth and fifth slot regions can be used when operating in TDD mode between IAB-DU operation and IAB-MT operation. Therefore, the first and second slot regions and the fourth and fifth slot regions can be time-frequency resources 2200 for TDM operation. In FIG. 22, TDM operation is assumed to be operation mode A. Operation mode A can be configured by time-domain HSNA configuration.

[0531] On the other hand, the third and sixth slot regions can operate in non-TDM mode. For example, IAB-DU and IAB-MT operations in the third and sixth slot regions can be frequency division multiplexed (FDM), respectively. Furthermore, IAB-DU and IAB-MT operations in the third and sixth slot regions can be spatial division multiplexed (SDM), respectively. The operation mode of the third and sixth slot regions is thus assumed to be operation mode B. Operation mode B can be configured by frequency-domain HSNA configuration. The resources for operation mode B can be time-frequency resources 2210 for FDM / SDM operation.

[0532] Based on the above description, time-frequency resources for IAB-DU operation may be allocated in the first and fourth slot regions where TDM operation is performed, and time-frequency resources 2200 for IAB-MT operation may be allocated in the second and sixth slot regions. Also, time-frequency resources 2210 corresponding to FDM or SDM may be allocated in the third and sixth slot regions for IAB-DU and IAB-MT operation.

[0533] Meanwhile, the operation mode may be divided into sub-operation modes according to other related functions, which will be explained in detail with examples as follows.

[0534] 1) Resource A allocated to TDM mode can be classified into operation mode A-1 in association with Pc set by a higher layer. Here, it can be said that the PDSCH EPRE in resource A is induced by the powerControlOffset described above.

[0535] 2) Resource B allocated to FDM mode can be classified into operation mode B-1 in relation to the provided or desired downlink transmit power adjustment (DL Tx power adjustment) MAC CE B. Here, the PDSCH EPRE in resource B can be derived by additionally considering the value indicated by MAC CE B in addition to the CSI-RS / PDSCH power ratio according to the powerControlOffset described above.

[0536] 3) Resources C allocated to FDM mode can be classified into operation mode B-2 in relation to the provided or desired downlink transmit power adjustment (DL Tx power adjustment) MAC CE C. Here, the PDSCH EPRE in resource C can be derived by additionally considering the value indicated by MAC CE C in addition to the CSI-RS / PDSCH power ratio according to the powerControlOffset described above.

[0537] If resource B assigned to the FDM mode is a resource associated with IAB-DU operation, then resource C assigned to the FDM mode may be a resource associated with IAB-MT operation. Conversely, if resource B assigned to the FDM mode is a resource associated with IAB-MT operation, then resource C assigned to the FDM mode may be a resource associated with IAB-DU operation.

[0538] The resources for the above-described operation modes may be allocated semi-statically based on higher layer signaling (e.g., F1AP, RRC, or MAC CE). As another example, the resources for the above-described operation modes may be allocated dynamically based on layer 2 (L2) signaling (e.g., MAC CE) or layer 1 (L1) signaling (e.g., DCI).

[0539] In this case, each operation mode may be associated with a set of CSI components (elements that a UE must assume when generating CSI) with different values. In this case, the base station needs to receive separate CSI reports for each resource interval 2200, 2210 to improve wireless transmission efficiency.

[0540] If the resource allocation characteristics of the CSI measurement and reporting do not match the resource allocation characteristics of the operating mode, or if the resource allocation / change time of the CSI measurement and reporting does not match the resource allocation / change time of the operating mode, the UE (or base station) needs to determine which CSI component (set) the CSI report relates to. Here, the resource allocation characteristics can be, for example, periodic CSI reporting based on periodic CMR / IMR measurements, and the resource allocation characteristics of the operating mode can be, for example, dynamic operating mode resource allocation.

[0541] Furthermore, to consider an example in which the resource allocation / change time for CSI measurement and reporting does not match the resource allocation / change time for the operation mode, the CSI measurement / reporting configuration may be set in slot n, and the resource allocation / change time for the operation mode may be, for example, when the operation mode resource is allocated in slot n+N.

[0542] As another example, as in the example described in FIG. 20, there may be cases where two or more different operation modes are simultaneously assigned to a specific resource (e.g., 2015). Specifically, this may be the case where a specific slot list and RB set (or RB set group) are configured as a time-domain soft resource in 3GPP Standard Rel-16 and a frequency-domain soft resource in 3GPP Standard Rel-17. The operation mode for the corresponding time-frequency resource may be dynamically changed by DCI format 2_5. In such cases, the UE (or base station) needs to determine which CSI component (set) the CSI report relates to.

[0543] The operation modes described above can be combined with other different operation modes. In other words, the operation modes described with reference to Figures 20 to 22 can be combined to form new operation modes.

[0544] As an example, in Figure 20, operation mode A can be defined as a TDM operation mode of IAB-DU / IAB-MT based on the time-domain HSNA configuration, and operation mode B can be defined as a combination of an FDM (or SDM) operation mode of IAB-DU / IAB-MT based on the frequency-domain HSNA configuration and a downlink power adjustment operation mode based on the provided downlink transmit power adjustment (DL Tx power adjustment) MAC CE. The examples of Figures 21 to 22 can also be extended in a similar manner.

[0545] FIG. 23 is a conceptual diagram illustrating CSI reporting for each operation mode according to an embodiment of the present disclosure.

[0546] 23, the horizontal axis represents time and the vertical axis represents frequency, and FIG. 23 illustrates a case where different operation modes are set in different time sequences.

[0547] Referring to FIG. 23 in chronological order, the operational mode changes in the following order: a first time region in which operational mode A (2300) is activated, a second time region in which operational mode B (2310) is activated, a third time region in which operational mode A (2320) is activated again, and a fourth time region in which operational mode C (2330) is activated.

[0548] As shown in Figure 23, to change the operation mode, the base station can set / activate / instruct one or more operation modes 2300, 2310, 2320, and 2330 to the terminal. In this case, the resources for which each operation mode 2300, 2310, 2320, and 2330 is set (or activated or instructed) can be the same or different. For example, it can be seen that the time resources are different from each other in Figure 23. It can also be seen that the frequency resources are the same in Figure 23.

[0549] 23, after the CMR and / or IMR 2306 is transmitted for a time set in operation mode A (2300), CSI reference resources 2304 are allocated and resources for CSI reporting 2302 are allocated. Also, an example is shown in which a CMR and / or IMR 2316 is additionally transmitted for a time set in operation mode A (2300).

[0550] This illustrates a case where CSI reference resources 2314 are allocated for a time set in operation mode B (2310), and then CSI reporting resources 2312 are allocated. This illustrates a case where CMRs and / or IMRs 2306 not labeled with reference symbols are subsequently transmitted, and CSI reference resources and CSI reporting resources are allocated.

[0551] This illustrates an example in which a CMR and / or IMR without a reference code is first transmitted for a time period set in the second operating mode A (2320), and then CSI reference resources and CSI reporting resources are allocated and a CMR and / or IMR 2336 is transmitted.

[0552] Finally, the example shows a case where CSI reference resources 2334 and CSI reports 2332 are allocated for the time set in operation mode C (2330), and CMRs and / or IMRs not designated by reference symbols are allocated, and CSI reference resources and CSI report resources are allocated.

[0553] As described above, the transmission / monitoring / measurement locations of channel estimation resources for specific CSI reports 2302, 2312, 2332, e.g., CMRs and / or IMRs 2306, 2316, 2336, and the locations of CSI reference resources 2304, 2314, 2334 for the corresponding CSI reports, may occupy different resources assigned to different operation modes. In other words, the operation mode associated with the channel estimation resources may not match the operation mode associated with the CSI reference resources.

[0554] Let us consider this in more detail. When the operation mode A (2300) associated with the CMR and / or IMR 2306 resource matches the operation mode A (2300) associated with the CSI reference resource 2304, the CSI report 2302 resource based on the corresponding resource 2306, 2304 is a value based on the CSI component according to operation mode A (2300), and there is no ambiguity.

[0555] On the other hand, if the CMR and / or IMR 2316 resources and the operational mode A (2300) and operational mode A (2320) associated with the CMR and / or IMR 2336 do not match with the operational mode B (2310) and operational mode C (2330) associated with the CSI reference resources 2314, 2334, it may be unclear whether the CSI report 2312, 2332 resources based on the corresponding resources 2316, 2336, 2314, 2334 are derived from values ​​derived from CSI components in the first operational mode A (2300), the second operational mode A (23-20), the operational mode B (2310), or the operational mode C (2330).

[0556] Such unclear characteristics can be problematic, particularly when the terminal monitors or receives activation / indication signaling for an operation mode change, e.g., from operation mode A (2300) to operation mode B (2310) and / or from operation mode A (2320) to operation mode C (2330), after the terminal begins to occupy one or more CPUs for CSI calculation after monitoring channel estimation resources 2316, 2336.

[0557] To solve this problem, the base station and the terminal can eliminate ambiguity in the assumption of the CSI component by, for example, "determining the operation mode assumed for CSI derivation," "limiting the target frequency band of CSI derivation (frequency band of CSI reference resource)," or "limiting the channel estimation resource (time interval or frequency band of CMR and / or IMR resource) referenced for CSI derivation," based on at least one of the following methods:

[0558] A specific example of this method is as follows: The terminal described below can be understood as any one of a UE, an IAB-MT, or a repeater-MT.

[0559] Method #1: The UE may generate CSI by taking into account the operation mode applied to the CSI reference resource of a specific CSI report. The operation mode applied to the CSI reference resource may be defined as one of the following cases:

[0560] "Operation mode set through higher layer signaling (SIB, RRC or F1AP) in the same (overlapping) slot (or symbol) as the corresponding CSI reference resource,"

[0561] An operation mode activated or indicated through higher layer signaling (MAC CE) in the same (overlapping) slot (or symbol) as the corresponding CSI reference resource;

[0562] The operation mode is activated or indicated through higher layer signaling (MAC CE) in the same (overlapping) slot (or symbol) as the corresponding CSI reference resource, and the higher layer signaling (MAC CE) is received a specific time before the same slot (or symbol), for example, a predetermined number of slots or symbols such as a minimum delay time Z', or a separately set or indicated number of slots or symbols.

[0563] "Operation mode indicated through L1 signaling (DCI) in the same (overlapping) slot (or symbol) as the corresponding CSI reference resource,"

[0564] The operation mode is indicated through L1 signaling (DCI) in the same (overlapping) slot (or symbol) as the corresponding CSI reference resource, and the L1 signaling (DCI) is received a specific time before the same slot (or symbol), for example, a predetermined number of slots or symbols, such as a minimum delay time Z', or a separately set or indicated number of slots or symbols.

[0565] In this case, if one of the conditions in the above-mentioned cases 3) or 4) is not satisfied, it may be possible to assume a default operation mode for the corresponding CSI reference resource. An example of a case where one of the conditions in the cases 3) or 4) is not satisfied may be when signaling activating or indicating a specific operation mode is not received before a specific time point from the CSI reference resource slot (or symbol).

[0566] The default operating mode can be one of the following modes:

[0567] a. "The operating mode used when receiving cell-specific or group-specific downlink signals (e.g., MIB (PBCH), SIB, CSI-RS, or CORESET 0, etc.)";

[0568] b. "The operating mode used when transmitting cell-specific or group-specific uplink signals (e.g., PRACH, SRS, etc.)";

[0569] c. "Operation mode set through separate upper layer parameters";

[0570] d. "Operation modes assumed for CSI reporting defined in 3GPP Rel-15"

[0571] ●Method #2: The base station may separately configure or instruct the UE to consider the operation mode(s) when deriving (calculating) CSI for a specific CSI report. If a certain CSI report is associated with multiple operation modes, the UE may derive CSI by considering the operation mode with the highest priority. For specific examples of priority determination, please refer to other embodiments of the present disclosure. The UE may be configured to assume a default operation mode when deriving CSI for a CSI report that is not associated with a separate configuration or instruction. Since the default operation mode is the same as the modes used in Method #1, repeated description will be omitted.

[0572] Method #3: The base station may configure or instruct the terminal to perform CSI reporting including multiple CSI values ​​taking multiple operation modes into consideration. For example, if N operation modes to be considered for a specific CSI report are configured or instructed, the terminal may report CSI consisting of pairs of N CSI values ​​(CRI, RI, PMI, CQI, RSRP, etc.). In this case, the N CSI pairs for the N operation modes may be understood as a serving cell including the corresponding CSI being expanded into N virtual serving cells. The stacking order of the N CSI pairs for the N operation modes may be determined by the priority of the N operation modes or by the order in which the N operation modes are configured / instructed.

[0573] Here, the stacking order may be a criterion when some CSI must be dropped due to insufficient PUCCH or PUSCH payload for CSI reporting. As another example, when two different operation modes are configured or indicated for a specific CSI report, the UE may report the CQI difference between the first operation mode and the second operation mode using a (sub-band) differential CQI. The first operation mode is not separately configured or indicated, but may be implicitly determined by one of the examples of the default operation mode in Method #1 above.

[0574] ●Method #4: If the CMR and / or IMR associated with a certain CSI report use different time resources (different symbols, different slots, different symbols / slots separated by more than N, etc.) associated with different operating modes, the terminal may omit or ignore the corresponding CSI report.

[0575] As another example, if the CMR, IMR, and CSI reference resource associated with a certain CSI report use different time resources (different symbols, different slots, different symbols / slots separated by more than N, etc.) associated with different operating modes, the terminal may omit or ignore the corresponding CSI report.

[0576] This can omit CSI reporting that has ambiguity related to the operation mode, thereby reducing the UE burden and uplink load for CSI reporting.

[0577] ●Method #5: If the CMR and / or IMR associated with a certain CSI report use different frequency resources (different RBs, different RB sets / RB set groups, different RBs / RB sets / RB set groups separated by more than N, etc.) associated with different operating modes, the terminal may omit or ignore the corresponding CSI report.

[0578] As another example, if the CMR, IMR, and CSI reference resource associated with a certain CSI report use different frequency resources (different RBs, different RB sets / RB set groups, different RBs / RB sets / RB set groups separated by more than N, etc.) associated with different operating modes, the terminal may omit or ignore the corresponding CSI report.

[0579] This can omit CSI reporting that has ambiguity related to the operation mode, thereby reducing the UE burden and uplink load for CSI reporting.

[0580] Method #6: If the CMR and / or IMR associated with a certain CSI report use different time resources associated with different operation modes, the UE may omit or ignore the CSI report. Here, if the CMR and / or IMR associated with a certain CSI report use different time resources associated with different operation modes, this may be one of the following cases.

[0581] a. When included in different IAB (or repeater) time resource settings,

[0582] b. The CMR is set in a slot included in the slot list indicated by the provided DL TX power adjustment MAC CE, and the IMR is set in a slot not included in the slot list.

[0583] c. When the CMR is set in a slot not included in the slot list indicated by the provided DL TX power adjustment MAC CE, and the IMR is set in a slot included in the slot list.

[0584] As another example, if the CMR, IMR, and CSI reference resource associated with a certain CSI report use different time resources associated with different operation modes, the UE may omit or ignore the corresponding CSI report. Here, the case where the CMR, IMR, and CSI reference resource associated with a certain CSI report use different time resources associated with different operation modes may be one of the following cases.

[0585] a. When included in different IAB (or repeater) time resource settings,

[0586] b. The CMR and / or IMR are set in slots included in the slot list indicated by the provided DL TX power adjustment MAC CE, and the CSI reference resource is set in a slot not included in the slot list.

[0587] c. The CMR and / or IMR are set in a slot not included in the slot list indicated by the provided DL TX power adjustment MAC CE, and the CSI reference resource is set in a slot included in the slot list.

[0588] Through the above example, CSI reporting with ambiguity related to the operation mode can be omitted, thereby reducing the UE burden and uplink load for CSI reporting.

[0589] Method #7: If the CM and / or IMR associated with a certain CSI report use different frequency resources associated with different operation modes, the UE may omit or ignore the CSI report. Here, if the CM and / or IMR associated with a certain CSI report use different frequency resources associated with different operation modes, this may be one of the following cases:

[0590] a. When included in different IAB (or repeater) frequency resource configurations

[0591] b. When CMR is set in an RB set / RB set group included in the frequency domain H / S / NA setting, and IMR is set in an RB not included in the RB set / RB TPXM group

[0592] c. When CMR is set in an RB set / RB set group that is not included in the frequency domain H / S / NA setting, and IMR is set in an RB that is included in the RB set / RB TPXM group.

[0593] Method #8: When the CMR and / or IMR associated with a certain CSI report use different time / frequency resources associated with different operation modes, the UE may perform CSI derivation (calculation) based on the operation mode of the CMR (e.g., whether DL TX power adjustment is applied) (i.e., the operation mode of the IMR resource may override the operation mode of the CMR resource). Similarly, when the CMR and / or IMR associated with a certain CSI report use different time / frequency resources associated with different operation modes, the UE may perform CSI derivation (calculation) based on the operation mode of the IMR (e.g., whether DL TX power adjustment is applied) (i.e., the operation mode of the IMR resource may override the operation mode of the CMR resource). Similarly, when the CMR, IMR, and CSI reference resource associated with a certain CSI report use different time / frequency resources associated with different operation modes, the UE may perform CSI derivation (calculation) based on the operation mode (e.g., whether DL TX transmission adjustment is applied) of the resource with the highest priority (e.g., the CSI reference resource) (i.e., the operation mode of the CMR / IMR resource may be overridden by the operation mode of the CSI reference resource). This allows the UE to resolve ambiguity during CSI derivation (calculation) and improve the accuracy of CSI reporting.

[0594] ●Method #9: If there is an operating mode associated with a certain CSI report, the UE can consider only the frequency resources allocated to (or associated with) the corresponding operating mode when deriving (calculating) the wideband CQI. In other words, when calculating the CQI, only the frequency resources associated with the corresponding operating mode can be considered in determining the TBS. This allows the UE to resolve ambiguity during CSI derivation (calculation) and improve the accuracy of CSI reporting.

[0595] If there are multiple frequency resource configuration values ​​for a certain operation mode at the same time, it may be possible to derive (calculate) the CSI for the frequency resource with the narrowest bandwidth, i.e., the smallest TBS. The opposite is also possible. For example, if there are multiple frequency resource configuration values ​​for a certain operation mode at the same time, it may be possible to derive (calculate) the CSI for the frequency resource with the widest bandwidth, i.e., the largest TBS. An example of a case where there are multiple frequency resource configuration values ​​for a certain operation mode at the same time may be when there is an RB set group for FDM H / S resource configuration for multiple RB sets / eIAB.

[0596] Similarly, if there are multiple frequency resource setting values ​​for a certain operating mode at the same time (e.g., if there are multiple RB sets / RB set groups for FDM H / S resource configuration for RB eIAB), the base station can induce (calculate) CSI for the terminal based on a certain frequency resource setting or set it through separate signaling.

[0597] ● Method #10: If multiple operating modes exist (based on configuration or instruction) at the same time, the terminal may be promised or configured / instructed to report the CSI with the lowest MCS (or modulation scheme, code rate, efficiency) among the multiple CSIs induced for the multiple operating modes. As another example, the terminal may be promised or configured / instructed to report the CSI with the highest MCS (or modulation scheme, code rate, efficiency) among the multiple CSIs induced for the multiple operating modes.

[0598] In one embodiment, the CSI may include an indicator for the assumed operation mode when the corresponding CSI is derived, which allows the UE to resolve ambiguity during CSI derivation (calculation) and improve the accuracy of CSI reporting.

[0599] Method #11: If an operation mode associated with a certain CSI report exists, the UE may be promised or configured / instructed to exclude CMR and / or IMR that are not transmitted in the time / frequency resources associated with the corresponding operation mode when calculating CSI. This allows the UE to resolve ambiguity during CSI derivation (calculation) and improve the accuracy of CSI reporting.

[0600] The UE may be promised or configured / instructed to apply the same one of Methods #1 to #11 to the CSI-RS group for the multi-TRP. For example, if different methods are configured / instructed, they may be unified according to a specific criterion or guaranteed to be set / instructed to the same value.

[0601] Similarly, a terminal may be promised or configured / instructed to apply different methods to different CSI-RS groups.

[0602] The above-described methods #1 to #11 may be restricted to be applied only when IMR is set to NZP CSI-RS, because in the case of CSI-IM-based IMR, the operation mode applied to the interfering signal based on the ZP CSI-RS configuration is implicitly reflected.

[0603] In the above-described methods #1 to #11, the frequency resource (or time resource) region assumed when generating CSI for CSI reporting related to a certain operation mode may be one of the following:

[0604] This may refer to the resources configured in the DU / RU (e.g., IAB-DU) of a node (e.g., IAB node) including the CSI generating entity (e.g., IAB-MT) for the operating mode. The configured resources here may be, for example, FDM HSNA resources allocated by the frequency domain IAB-DU-Resource-Configuration-H / S / NA-Config setting of 3GPP Rel-17 or FDM soft resources indicated as available / not available by DCI format 2_5.

[0605] It may refer to resources (e.g., MT-CC) allocated to a CSI generator (e.g., IAB-MT) for an operation mode, excluding the portion overlapping with the resources configured in the DU / RU (e.g., IAB-DU) of the node (e.g., IAB node) including the CSI generator (e.g., IAB-MT). The configured resources here may be, for example, FDM HSNA resources allocated by the frequency domain IAB-DU-Resource-Configuration-H / S / NA-Config configuration of 3GPP Rel-17 or FDM soft resources indicated as available / not available by DCI format 2_5.

[0606] ●It may refer to resources (e.g., MT-CC) allocated to a CSI generator (e.g., IAB-MT) that the CSI generator can utilize for downlink reception operations (or uplink transmission operations) in its operating mode.

[0607] It may refer to resources configured in the DU / RU (e.g., parent node of IAB-DU) of the parent / upper node (e.g., IAB parent node, donor node, CU) of the node including the CSI generator for the operation mode. Here, the configured resources may be, for example, FDM HSNA resources allocated by the frequency domain IAB-DU-Resource-Configuration-H / S / NA-Config setting of 3GPP Rel-17 or FDM soft resources indicated as available / not available by DCI format 2_5.

[0608] A region allocated through a separate, independent configuration, instruction, or report, for example, may be a frequency (time) resource region configured or instructed by a base station, upper node, or neighboring node, or a frequency (time) resource region reported directly or indirectly by a terminal (e.g., IAB-MT, repeater-MT) to an upper node, neighboring node, or base station through signaling such as DCI, MAC CE, RRC, and / or F1AP. A direct example may be when explicitly reporting a frequency (time) region used / referenced by a CSI report related to a certain operation mode. An indirect example may be when the IAB-MT reports the operation mode of a specific frequency (time) resource as, for example, TDM (fallback) mode or FDM mode through MAC CE, and the frequency (time) resource is identified as an IAB-MT frequency (time) resource available for use in the corresponding mode.

[0609] When generating CSI for a CSI report related to a certain operation mode, the UE may determine the TB size based on a frequency resource (or time resource) region according to one of the above-defined contents. As an example, this may mean that when generating wideband CSI for a CSI report related to a certain operation mode (not the entire band in which PDSCH transmission is possible within CC to BWP represented by the corresponding CSI report), the UE must generate CSI (CRI, RI, LI, PMI, CQI, etc.) values ​​that represent only a frequency resource (or time resource) region according to one of the above-defined contents.

[0610] As another example, when generating subband CSI for CSI reporting related to a certain operation mode, it may mean that CSI (CRI, RI, LI, PMI, CQI, etc.) values ​​for frequency resource (or time resource) regions associated with one of the contents defined above (see (a)) should be generated and reported, and CSI for other frequency resource (or time resource) regions should not be reported (or omitted) or meaningless (garbage) values ​​should be reported.

[0611] As an example, improvements such as those in Table 51 below can be considered.

[0612] [Table 51]

[0613] Based on the above, the specifications can be improved as shown in Table 52 below, with the portions highlighted in bold.

[0614] [Table 52]

[0615] In the method described above, the upper layer (F1AP / RRC / MAC CE) configuration or instruction (DCI) for the (candidate) value(s) of the interval N (symbol / slot / RB / RB set / RB set group, etc.) between time / frequency resources can be considered not only in the downlink (upper node -> lower node) direction, but also in the uplink (lower node -> upper node) direction or horizontal (neighbor node -> neighbor node) direction.

[0616] The terminal can perform a UE (IAB-MT or repeater-MT) capability report indicating whether or not it supports one of the above-mentioned methods #1 to #11, including information on the (candidate) value(s) of the interval N between time / frequency resources (symbol / slot / RB / RB set / RB set group, etc.).

[0617] FIG. 24 is a flowchart illustrating CSI resource configuration and reporting configuration, CSI request, operation mode configuration / activation / indication, and corresponding CSI reporting according to one embodiment of the present disclosure.

[0618] Referring to FIG. 24, in step 2420, a base station 2400 performs CSI reporting configuration and resource configuration for an operation mode set A consisting of one or more operation modes on a terminal 2410, and can request a CSI report based on the configuration.

[0619] Separately, in step 2430, base station 2400 can allocate specific resources to operation mode set B, which is composed of one or more operation modes, and notify (configure / activate / instruct) this to terminal 2410.

[0620] In step 2440, the terminal 2410 can derive (calculate) only CSI corresponding to an operation mode belonging to the intersection of operation mode set A and operation mode set B for a certain CSI reference resource and report it to the base station (2440).

[0621] This allows the terminal 2410 to reduce the CSI calculation burden, and the base station 2400 or the network to minimize uplink resource occupation for CSI reporting.

[0622] FIG. 25 is a flowchart illustrating a CSI resource configuration and reporting configuration, an operation mode configuration / activation / indication, and a CSI reporting operation depending on whether a specific condition is satisfied, according to one embodiment of the present disclosure.

[0623] Referring to FIG. 25, in step 2500, the terminal receives CSI reporting configuration and resource configuration including CMR and / or IMR configuration information from the base station, and may additionally receive activation or indication information for the CSI.

[0624] In step 2505, the terminal may receive configuration, activation, and instruction information for one or more operation modes for a particular resource from the base station.

[0625] In step 2510, the UE can perform the CSI report only if the "occasion of operation mode setting, activation, and indication signaling" and the "occasion of CMR and / or IMR resource" for the CSI report all satisfy the conditions of the above-mentioned methods #1 to #11. On the other hand, if the "occasion of operation mode setting, activation, and indication signaling" and the "occasion of CMR and / or IMR resource" for the CSI report all do not satisfy any of the conditions of the above-mentioned methods #1 to #11, the UE can omit the CSI report.

[0626] This allows the terminal to reduce the CSI induction (calculation) burden, and the base station or network to minimize uplink resource occupation for CSI reporting.

[0627] Second Example: CPU Occupancy Calculation Method Considering Operation Mode

[0628] In a second embodiment of the present disclosure, a CPU occupation management / calculation method that takes into account various operation modes will be examined in detail.

[0629] JPEG2026506518000083.jpg29161

[0630] JPEG2026506518000084.jpg49161

[0631] When the UE performs CSI reporting taking into account multiple operation modes through separate upper layer signaling (F1AP, RRC, MAC CE) or L1 signaling (DCI), the BS may configure / instruct the UE to initialize the pre-occupied CPU in consideration of the UE's complexity. Here, initialization may mean, for example, setting the CPU occupancy rate before the currently newly derived (calculated) CSI to '0 (zero)'.

[0632] Third embodiment: CSI reference resource / available DL slot determination method taking into account operation mode

[0633] In a third embodiment of the present disclosure, a method for determining CSI reference resources / available DL slots taking into account various operation modes will be examined in detail.

[0634] In one embodiment of the present disclosure, the UE may be guaranteed to derive (calculate) CSI for each operation mode after receiving at least one CMR and / or IMR for the corresponding operation mode. For example, the UE may be guaranteed to receive at least one CMR / IMR after applying a specific operation mode and perform CSI reporting associated therewith. In this case, the point in time after the specific operation mode may be, for example, a point in time after applying a provided DL transmission power adjustment or receiving a provided DL transmission power adjustment MAC CE. If the above conditions are not met, the UE may omit CSI reporting.

[0635] As another example, the UE may be guaranteed to receive at least one CMR / IMR from a CSI reference resource for CSI reporting in a specific operation mode before a specific time point and perform CSI reporting. Here, the specific time point may be, for example, n slots before the CSI reference resource to which the provided DL TX transmission adjustment is applied. If the above condition is not met, the UE may omit CSI reporting.

[0636] In one embodiment of the present disclosure, the UE may be guaranteed not to consider a separate operation mode during DRX configuration (DRX period). For example, the UE may be guaranteed not to perform CSI reporting taking into account DL TX transmission adjustments provided during the DRX period.

[0637] In one embodiment of the present disclosure, the UE may be configured not to consider a corresponding slot as a valid slot if the operation mode applied to the CSI reference resource and the operation mode associated with the corresponding CSI report setting are different from each other. For example, the UE (or IAB-MT) may not consider a corresponding slot as a valid slot if the IAB-DU / -MT simultaneous operation mode (or multiplexing mode (e.g., TDM / FDM / SDM)) applied to a certain slot is different from the simultaneous operation mode setting (or multiplexing mode) value associated with the CSI report setting.

[0638] The frequency resources allocated to the following 1) to 3) may have different values:

[0639] 1) PDSCH allocated frequency resources;

[0640] 2) Frequency resources configured in the CSI reporting band (e.g., wideband CSI, subband CSI),

[0641] 3) Frequency resources allocated to a specific operating mode (e.g., 3GPP Rel-17 frequency domain HSNA configuration for an RB set to an RB set group or frequency resource configuration for XDD to FD, etc.)

[0642] The base station can configure which of these criteria the terminal will use to derive CSI. In this case, the frequency resources configured for the CSI reporting candidate band in 2) can be a list of one or more RB sets to RB set groups, and the base station can configure / select one or more of these RB sets or RB set groups to actually derive CSI.

[0643] ●Various frequency resource configurations / allocations may have different priorities, and when a terminal derives a certain CSI, it may derive the CSI for the frequency resource with the highest priority at that time (e.g., based on the slot of the CSI reference resource).

[0644] For example, assumption 2) may have a higher priority than assumption 3) for resources on which cell-specific information such as SIB is transmitted.

[0645] As another example, if an operation mode indicator (e.g., DCI format 2_5 or a provided DL Tx transmit power adjustment MAC CE) indicates a specific operation mode, assumption 3) may have a higher priority than assumption 2).Here, an example of a case where an operation mode indicator indicates a specific operation mode may be when 3GPP Rel-17 indicates that AI is available for a frequency domain soft resource and indicates a specific PDSCH EPRE adjustment value other than 0 for the corresponding resource.

[0646] Example 4:

[0647] In a fourth embodiment of the present disclosure, details are considered to provide a method for selecting a CMR and an IMR and generating and reporting a CSI in consideration of various operation modes.

[0648] FIG. 26 is a conceptual diagram illustrating CSI reporting in a first operation mode according to an embodiment of the present disclosure.

[0649] 26, the horizontal axis represents time, and the vertical axis represents frequency. Therefore, a specific resource, such as a symbol or a slot, can be allocated to a terminal by a base station according to frequency and time resources. The specific symbol or slot may be allocated a resource for CSI measurement according to the present disclosure, and may also be a resource for CSI reporting.

[0650] The base station may configure / assign at least one CMR and / or IMR for channel or interference measurement to the terminal as exemplified by reference numerals 2600, 2620, and 2630. In addition, the base station may configure / assign to the terminal uplink resources (PUSCH to PUCCH) for reporting CSI generated based on channel or interference measurement as exemplified by reference numeral 2610. At this time, the terminal may determine CSI reference resources 2605 and 2625 serving as a reference for CSI generation according to the above-described method. The terminal may determine a transport block size (TBS) based on the number of REs that can be transmitted for data in a slot determined by the CSI reference resource 2625 according to one of the above-described rules, and use the determined TBS for CSI derivation.

[0651] In the example of Figure 26, the time during which a certain CSI report occupies one or more CPUs can be defined as the time from the first OFDM symbol occupied by the most recent CMR and / or IMR resource prior to the CSI reference resource of the corresponding CSI report to the last OFDM symbol occupied by the uplink channel including the corresponding CSI report. Here, the uplink channel can be either a PUSCH or a PUCCH. In addition, the number of CMRs and / or IMRs reflected in CSI generation can be limited to the most recent CMR or the most recent IMR according to the time-domain measurement restriction setting (2620). In this case, the time-domain measurement restriction setting can be an upper layer parameter such as timeRestrictionForChannelMeasurements or timeRestrictionForInterferenceMeasurements.

[0652] As another example, the number of CMRs and / or IMRs reflected when generating CSI may be limited to the most recent one CMR or the most recent one IMR if there are no previously valid CMRs and / or IMRs (2620). As yet another example, the number of CMRs and / or IMRs reflected when generating CSI may include the most recent one CMR and its previous CMR or the most recent one IMR and its previous IMR, depending on the time-domain measurement restriction setting described above (2630).

[0653] For example, when a terminal measures a CMR set based on a periodic NZP CSI-RS or a semi-persistent NZP CSI-RS and generates CSI to which timeRestrictionForChannelMeasurements does not apply, it can use the (weighted) average value of the channel measured at two or more valid NZP CSI-RS transmission points.

[0654] Similarly, when the UE measures the IMR set based on periodic NZP CSI-IM or quasi-static NZP CSI-IM and generates CSI to which timeRestrictionForInterferenceMeasurements does not apply, it can use the (weighted) average value of the interference measured at two or more valid NZP CSI-RS transmission points.

[0655] FIG. 27 is a conceptual diagram illustrating a case where CSI is reported in an environment where the first operation mode and the second operation mode coexist according to an embodiment of the present disclosure.

[0656] Referring to Figure 27, the horizontal axis represents time and the vertical axis represents frequency. Figure 27 illustrates an example divided into four time intervals to explain the coexistence of two operating modes. The four time intervals can be divided into a first time interval 2720 using the subband full-duplex (SBFD) scheme, a second time interval 2722 using the TDD scheme, a third time interval 2724 also using the SBFD scheme, and a fourth time interval 2726 using the TDD scheme. In the following description, each time interval 2720, 2722, 2724, and 2726 will be described using the same reference numerals depending on the scheme used. For example, since the first and third time intervals use SBFD, they will be described as SBFD 2720 and SDFD 2724. Similarly, since the second and fourth time intervals use TDD, they will be described as TDD 2722 and TDD 2726. Therefore, in the following description, SBFD2720 may refer to the first time period, which may mean the time period in which the SBFD method is set as the operation mode.

[0657] SBFD 2720, TDD 2722, SBFD 2724, and TDD 2726 may respectively transmit CMR / IMR (CSI-RS, CSI-IM) 2720, CSI reference resource 2705, and CSI report 2710 on the uplink, for example, PUSCH or PUSCH.

[0658] Then, among SBFD 2720, TDD 2722, SBFD 2724, and TDD 2726, the frequency may be divided into DL subband 2750, UL subband 2752, and DL subband 2754 only in SBFD 2720 and SBFD 2724. In this case, UL subband 2752 may include a guard band as illustrated in the drawing.

[0659] Although Figure 27 illustrates SBFD and TDD as two operation modes, this is not limiting. For example, in one embodiment of the present disclosure, the first operation mode may be one of duplex modes such as TDD or FDD, and the second operation mode may be one of advanced duplex modes such as SBFD, FD (full-duplex), or IAB DU / MT simultaneous operation mode. In the example of Figure 27, the first operation mode is assumed to be TDD (2722, 2726) and the second operation mode is assumed to be SBFD (2720, 2724), but these may be replaced or changed by any one of the first and second operation modes. As described above, the second operation mode may include at least one downlink subband (DL subband) 2750, 2754 and uplink subband (UL subband) 2752, and the uplink subband 2752 may include a guard band. As another example, the guard band may be configured / allocated separately.

[0660] The CSI reporting operation will be examined in more detail with reference to FIG.

[0661] The base station can configure / assign at least one CMR / IMR 2700 for channel or interference measurement to the terminal. The base station can also configure / assign a PUSCH or PSCCH 2710 as an uplink resource for reporting CSI generated based on channel or interference measurement to the terminal. At this time, the terminal can determine a CSI reference resource 2705 serving as a reference for CSI generation according to the above-mentioned method. The terminal can determine a TBS based on the number of REs that can be transmitted for data according to one of the above-mentioned rules in the slot determined by the CSI reference resource 2705, and use the TBS for CSI derivation.

[0662] In the example of Figure 27, it is assumed that the operation mode assumed in a certain CSI report is determined by the operation mode configured / assigned / instructed at the time of overlap with the CSI reference resource of the corresponding CSI report. In actual application, this is not limited to this, and various methods of the above-mentioned embodiments 1 to 3 can be applied, and the following content can also be appropriately modified and applied accordingly.

[0663] In the example of Figure 27, in the case of a CSI report that references a CSI reference resource present in the first operation mode (TDD) period 2722 (2734), the TBS can be determined taking into account the frequency (time) resources for the first operation mode (2734). In this case, if the CMR and / or IMR associated with the CSI report are measured in a time period to which the same operation mode (first operation mode - TDD) is assigned, they can be determined as valid CMRs to valid IMRs (2732). On the other hand, the CMRs and IMRs associated with the CSI report are measured in a time period to which a different operation mode (second operation mode - SBFD) is assigned, they can be determined as invalid CMRs to invalid IMRs (2730).

[0664] For example, the terminal may be promised / constrained not to reflect measurements in invalid CMRs and / or IMRs when generating CSI, thereby improving the accuracy of the corresponding CSI report.

[0665] As another example, the base station can set the measurement values ​​in the CMR to IMR that are not valid for the UE not to be reflected when generating CSI through upper layer parameters or can instruct through physical layer signaling, thereby improving the accuracy of the corresponding CSI report.

[0666] As another example, the UE may report to the base station that measurements at invalid CMRs to IMRs should not be reflected when generating CSI, allowing the base station to predict the accuracy of the corresponding CSI report.

[0667] In the above example, even if the operation mode of the CMR to IMR and the operation mode of the CSI reference resource are the same (e.g., all exist within the second operation mode (SBFD) interval), if the direction allocated to some frequency resources of the CMR and / or IMR differs from the direction allocated to some frequency resources of the CSI reference resource, the UE (or base station) may determine that different operation modes are allocated to the CMR to IMR and the CSI reference resource. Here, an example of the direction allocated to some frequency resources of the CMR and / or IMR may be when PRB#1 in the SBFD interval occupied by the CMR is allocated as a DL subband. Also, an example of the direction allocated to some frequency resources of the CSI reference resource may be when PRB#1 in the SBFD interval occupied by the CSI reference resource is allocated as a UL subband or a guard band.

[0668] When determining the validity of a certain CMR and / or IMR using the above-described method, if the time interval between the start of a certain operation mode period 2724 and the CSI reference resource 2762 is short (for example, if the two times are in the same slot), the most recent valid CMR and / or IMR will be in the same previous operation mode period 2720. As a result, the corresponding CSI report may occupy the CPU for a very long time (2760). This may significantly hinder the CPU usage efficiency of the terminal and may also mean that the accuracy of the corresponding CSI report may be reduced. Therefore, the terminal may omit / drop a certain CSI report using one of the following methods:

[0669] Method 4A-1: The base station sets a threshold in the terminal through an upper layer parameter, and the terminal can omit the CSI report if the CPU occupancy time of the CSI report for a specific operation mode is longer than the threshold. Here, the threshold may be set for each operation mode considering that the required accuracy of the CSI report may differ for each operation mode. As another example, the threshold may be set for each CSI report. As yet another example, the threshold may be set for each CMR and / or IMR resource. In this case, the setting may be a frequency range, for example, FR1, FR2, FR2-1, FR2-2, etc., as proposed in 3GPP, or may be BWP, CC, band, or band combination. In other words, system operation flexibility can be ensured by being limited to a specific frequency resource group. As a result, system operation flexibility can be increased by being set for a specific frequency resource group.

[0670] Method 4A-2: If the CPU occupancy time of a CSI report for a specific operation mode is longer than a predetermined threshold, the UE may omit the corresponding CSI report. The threshold may be set for each operation mode or for each CSI report type, considering that the required accuracy of CSI reporting may differ for each operation mode. Here, the CSI report type may refer to periodic, quasi-static, or aperiodic CSI reporting.

[0671] As another example, a threshold value may be set for each CMR and / or IMR resource type, taking into account that the required accuracy of CSI reporting may differ for each operation mode, where the type of CMR and / or IMR resource may mean periodic, quasi-static, aperiodic NZP CSI-RS and / or CSI-IM.

[0672] In the above example, the frequency range may be FR1, FR2, FR2-1, FR2-2, etc., as proposed by 3GPP, or may be BWP, CC, a band, or a band combination. In other words, it is possible to ensure system operation flexibility by being limited to a specific frequency resource group. This can result in an increase in system operation flexibility by being set for each specific frequency resource group.

[0673] Method 4A-3: The terminal reports a preferred threshold to the base station and can determine the threshold to be actually applied based on the reported threshold or a threshold separately set by the base station. Thereafter, if the CPU occupancy time of the CSI report for a specific operation mode is longer than the actually applied threshold, the terminal can omit the corresponding CSI report. The threshold reported by the terminal can be reported for each operation mode, taking into account that the accuracy of the CSI report required for each operation mode may differ. For example, the threshold reported by the terminal can be reported for each CSI report type, taking into account that the accuracy of the CSI report required for each operation mode may differ. Here, the type of CSI reporting can be periodic, quasi-static, or aperiodic CSI reporting.

[0674] As another example, the threshold value reported by the UE may be reported for each CMR and / or IMR resource type, taking into consideration that the required CSI accuracy may differ for each operation mode, where the CMR and / or IMR resource type may be static, quasi-static, aperiodic NZP CSI-RS and / or CSI-IM.

[0675] In addition, in each of the above examples, the frequency range of the CSI report may be FR1, FR2, FR2-1, FR2-2, etc., as proposed by 3GPP, or may be BWP, CC, band, or band combination. In other words, it is possible to ensure system operation flexibility by being limited to a specific frequency resource group. This can result in an increase in system operation flexibility by being set for each specific frequency resource group.

[0676] In the above-described methods 4A-1 to 4A-3, "when the CPU occupation time of a CSI report for a specific operation mode is longer than a critical value" is an example for convenience of explanation, and when actually applied, it may be changed to other similar conditions / definitions such as "the interval between the CMR and / or IMR associated with a certain CSI report and the CSI reference resource of the corresponding CSI report (and the first symbol of the associated CMR and / or IMR)" or "the interval between the CMR~IMR associated with a certain CSI report and the most recent CMR~IMR before the CSI reference resource of the corresponding CSI report (and the first symbol of the associated CMR~IMR)."

[0677] As another example of FIG. 27, in the case of a CSI report that references a CSI reference resource 2744 existing in a second operation mode period (SBFD) 2724, a TBS may be determined taking into account frequency (time) resources for the second operation mode (2744). In this case, if the CMR and / or IMR associated with the CSI report are measured in a time period to which the same operation mode (second operation mode - SBFD) is assigned, they may be determined as valid CMRs and / or valid IMRs (2742). Conversely, the CMR and / or IMR associated with the CSI report are measured in a time period to which a different operation mode (first operation mode - TDD) is assigned, they may be determined as invalid CMRs or invalid IMRs (2740).

[0678] In the above example, even when the operation mode of the CMR and / or IMR and the operation mode of the CSI reference resource are the same, for example, when both are in the second operation mode (SBFD) period, if the direction allocated to some frequency resources of the CMR and / or IMR and the direction allocated to some frequency resources of the CSI reference resource are different from each other, it can be determined that different operation modes are allocated to the CMR and / or IMR and the CSI reference resource. Here, the direction allocated to some frequency resources of the CMR and / or IMR may be, for example, when PRB#1 in the SBFD period occupied by the CMR is allocated as a DL subband, and the direction allocated to some frequency resources of the CSI reference resource may be, for example, when PRB#1 in the SBFD period occupied by the CSI reference resource is allocated as a UL subband or a guard band.

[0679] In the above example, when the CSI reference resource of a certain CSI report exists in the second operation mode section (2744), some or all of the frequency resources of the valid CMR and / or IMR 2742 for the second operation mode associated with the CSI report may not be entirely included in the DL subband (2750 or 2754) allocated for the second operation mode. This can be understood as a case where, when the CSI reference resource of a certain CSI report exists in the second operation mode section (2744), some or all of the frequency resources of the valid CMR and / or IMR 2742 for the second operation mode associated with the CSI report overlap with the UL subband or guard band 2752 allocated for the second operation mode. In this case, the UE may apply one of the following methods to "frequency resources of the valid CMR and / or IMR 2742 that are not entirely included in the DL subband (2750 or 2754) allocated for the second operation mode":

[0680] Method 4B-1: The UE is promised / constrained not to generate CSI based on time domain channel measurements for CMRs and / or IMRs that satisfy the above conditions. This is because the time domain channel measurements include channel characteristics for the entire frequency resource occupied by the corresponding CMRs and / or IMRs.

[0681] ●Method 4B-2: The terminal may be promised or configured by higher layer parameters to exclude RE, RB, or subband measurements that are not included in the SBFD DL subband among REs, RBs, or subbands occupied by NZP CSI-RS and / or CSI-IM (e.g., referring to an NZP CSI-RS RB set / group configured in 4-RB units) when generating CSI.

[0682] ●Method 4B-3: The terminal may be promised or configured by higher layer parameters to exclude RE, RB, or subband measurements that fall within the SBFD UL subband or guard band among RE, RB, or subband occupied by NZP CSI-RS and / or CSI-IM (e.g., referring to an NZP CSI-RS RB set / group configured in 4-RB units) when generating CSI.

[0683] ● Method 4B-4: The UE may be promised or configured by a higher layer parameter to drop / omit CSI reports based on measurements of NZP CSI-RS and / or CSI-IM REs, RBs, or subbands (e.g., NZP CSI-RS RB sets / groups configured in 4-RB units) that are not included in the SBFD DL subband. Here, the omitted CSI reports may be limited to subband CSI reports that include the corresponding REs, RBs, or subbands, or all CSI reports related to the corresponding time point (e.g., wideband CSI + subband CSI).

[0684] ● Method 4B-5: The UE may be promised or configured by a higher layer parameter to drop / omit CSI reports based on measurements of NZP CSI-RS and / or CSI-IM REs, RBs, or subbands (e.g., NZP CSI-RS RB sets / groups configured in units of 4 RBs) included in the SBFD UL subband or guard band. Here, the omitted CSI reports may be limited to subband CSI reports including the corresponding REs, RBs, or subbands, or all CSI reports related to the corresponding time point (e.g., wideband CSI + subband CSI).

[0685] For a given dual mode of operation, for measurement / reference resources related to CSI reporting, the UE shall apply at least one of the following:

[0686] Option 1-1 (related to option 1): If a CSI-RS / CSI-IM does not have the same duplex mode configured for the associated CSI report, the CSI generation of the corresponding CSI report shall not be considered.

[0687] Option 1-2 (combined with Option 1): CSI-RS / CSI-IM RE / RB / subbands that overlap with uplink subbands or guard bands for SBFD shall not be considered for CSI generation of CSI reports configured for downlink subbands for SBFD.

[0688] Option 2-1 (combined with Option 2): A CSI-RS / CSI-IM that does not have the same duplex mode as the duplex mode for the CSI reference resource of the associated CSI report is not considered in generating the CSI for the corresponding CSI report.

[0689] Option 2-2 (combined with Option 2): CSI-RS / CSI-IM RE / RB / subbands that overlap with uplink subbands for SBFD or guard bands are not considered for CSI generation of CSI reference resources in downlink subbands for SBFD.

[0690] When actually implementing a base station and / or terminal (IAB-node, IAB-DU, IAB-MT, repeater, repeater-RU, repeater-MT), the above-described embodiments are not necessarily mutually exclusive, and various combinations of embodiments may be considered. For example, the operation mode for CSI derivation (calculation) may be determined according to the first embodiment of the present disclosure, and valid slots and / or CSI reference slots may be determined according to the third embodiment.

[0691] Fifth Example: CPU Occupancy Time Calculation Method Considering SBFD Subbands

[0692] In a fifth embodiment of the present disclosure, a method for managing / calculating CPU occupancy of a terminal when one or more subbands are configured / allocated within the same time resource for a specific operation mode such as subband non-overlapping full duplex (SBFD) is provided. Hereinafter, a method for calculating CPU occupancy time taking SBFD subbands into consideration will be described in detail with reference to the attached drawings.

[0693] FIG. 28 is a conceptual diagram illustrating a subband CSI reporting operation according to an embodiment of the present disclosure.

[0694] Referring to Figure 28, an example is shown in which a base station configures one or more downlink (DL) subbands within a certain time resource interval for a specific operating mode such as SBFD (subband non-overlapping full duplex) for a specific terminal.

[0695] In order to acquire CSI for DL ​​subbands, the base station may configure CSI-RS, CSI-IM, and CSI reporting including two or more DL subbands for the terminal, which means that the frequency resource configuration of CSI-RS, CSI-IM, and CSI reporting overlaps with two or more of the allocated DL subbands.

[0696] In this case, in one embodiment, the CPU occupied by the CSI report is not affected by the number of overlapping DL subbands (N) and may be determined to be K (K≧1) according to the CPU occupation method described above. As another example, the CPU occupied by the CSI report may be determined to occupy a number of CPUs greater than K, such as "N*K," taking into consideration not only the K (K≧1) value according to the CPU occupation method described above but also the number of overlapping DL bands (N). In this case, the condition for occupying a number of CPUs greater than K may be determined in one of the following ways.

[0697] 1) It may be implicitly determined depending on whether the base station is enabled to report different CSI components to the terminal for each DL subband, where the CSI components may be, for example, CQI, PMI, RI, etc.

[0698] 2) It can be explicitly determined by separate higher layer signaling set by the base station.

[0699] 3) It may be explicitly determined by a separate indicator included in the CSI reporting instruction of the base station, where the CSI reporting instruction may be, for example, aperiodic CSI reporting.

[0700] The base station may configure the UE with SI-RS, CSI-IM, and / or CSI reporting for each DL subband to acquire CSI for the DL subband. This may refer to a case where the frequency resource configuration of CSI-RS, CSI-IM, and / or CSI reporting is included in only one of the allocated DL subbands. In this case, according to one embodiment of the present disclosure, the CPU occupied by the individual CSI reporting is not affected by the number of overlapping DL subbands (N) and may be set to K (K≧1) according to the above-mentioned CPU occupancy method. In other words, the CPU occupancy for a corresponding operation mode at a corresponding time may be the sum of the CPU numbers occupied by the CSI reporting for each subband.

[0701] JPEG2026506518000085.jpg36161

[0702] Rule 1: CSI of a subband including a frequency resource with a lower index (e.g., PRB or RBG index) has higher priority than CSI of a subband including a frequency resource with a higher index. The opposite is also possible. For example, CSI of a subband including a frequency resource with a higher index has higher priority than CSI of a subband including a frequency resource with a lower index.

[0703] Rule 2: In the case of CSI reporting for two or more subbands for a specific mode (e.g., SBFD, etc.), the priority according to reportConfigID is not applied, and the CSI including the CQI with the lower (or higher) index among the corresponding CSIs has the higher priority. Here, not applying the priority according to reportConfigID means not applying the s factor in Equation 7 below.

[0704]

number

[0705] Rule 3: In the case of CSI reports for two or more subbands for the same mode (e.g., SBFD), they are assumed to have the same priority, and when one of them is dropped, all remaining reports are also dropped.

[0706] FIG. 29 is a block diagram of a base station according to an embodiment of the present disclosure.

[0707] 29, the base station may include a processing unit 2900, a base station transmitting unit 2905, and a base station receiving unit 2910. The configuration in Fig. 29 is illustrated as one example, and the base station may further include additional components according to the embodiment of the present disclosure or the intention of the operator.

[0708] For example, the base station may further include a memory, although not illustrated in Figure 29. The base station may also include a wired / wireless interface for connecting to an external device. The base station may also include an interface for allowing an operator to check the operation of the base station. In addition to the above-described configurations, additional configurations may be included according to the needs of the operator or manufacturer.

[0709] The base station processing unit 2900 can determine and process the overall operation of the base station according to the embodiments of the present disclosure described above. For example, it can determine an operation mode or control transmission of information related to the determined operation mode to the terminal via higher layer signaling or physical layer signaling. If the base station processing unit 2900 has additional memory, it can control storage of corresponding information in the memory. The base station processing unit 2900 can control not only the transmission operation of the base station transmitter 2905 but also the reception operation of the base station receiver 2910. In particular, the base station processing unit 2900 can set / instruct CSI and operation mode and process CSI reported by the terminal according to at least one of the methods of FIGS. 24 to 27.

[0710] The base station transmitter 2905 can transmit data received from the base station processor 2900 to the downlink under the control of the base station processor 2900. The base station receiver 2910 can receive an uplink channel / signal under the control of the base station processor 2900 and provide it to the base station processor 2900.

[0711] FIG. 30 is a block diagram of a terminal according to an embodiment of the present disclosure.

[0712] 30, the terminal may include a terminal processing unit 3000, a terminal transmitting unit 3005, and a terminal receiving unit 3010. The configuration of Fig. 30 is illustrated as one example, and the terminal may further include additional components according to the embodiment of the present disclosure or the intention of the operator.

[0713] For example, the terminal may further include a memory, although not illustrated in FIG. 30. The terminal may also include a wired / wireless interface for connecting to an external device. The terminal may also include an interface that allows a user or operator to check the operation of the terminal. In addition to the above-described configurations, additional configurations may be included according to the needs of a user, business operator, or manufacturer.

[0714] The terminal processing unit 3000 may perform overall operation determination and processing of the terminal according to the embodiments of the present disclosure described above. For example, the terminal processing unit 3000 may control uplink transmission and / or downlink reception according to at least one of the operation modes described in the present disclosure. The terminal processing unit 3000 may also control reception of operation mode-related information from the base station through higher layer signaling or physical layer signaling. If the terminal processing unit 3000 has additional memory, it may also control storage of corresponding information in the memory. The terminal processing unit 3000 may control not only the transmission operation of the terminal transmitter 3005 but also the reception operation of the terminal receiver 3010. In particular, the terminal processing unit 3000 may generate CSI according to at least one of the methods of FIGS. 24 to 27 based on the CSI and operation mode setting / instruction of the base station, and report the CSI to the base station.

[0715] The terminal transmitter 3005 can transmit data received from the terminal processor 3000 to the uplink under the control of the terminal processor 3000. The terminal receiver 3010 can receive a downlink channel / signal under the control of the terminal processor 2900 and provide it to the terminal processor 3000.

[0716] The operations of the methods according to the embodiments of the present disclosure may be embodied as a computer-readable program or code stored in a computer-readable recording medium. The computer-readable recording medium includes all types of storage devices that store information that can be read by a computer system. The computer-readable recording medium may also be distributed across computer systems connected to a network, so that the computer-readable program or code may be stored and executed in a distributed manner.

[0717] Additionally, the computer-readable recording medium may include a hardware device specially configured to store and execute program instructions, such as a ROM, RAM, flash memory, etc. The program instructions may include not only machine language code, such as that produced by a compiler, but also high-level language code that can be executed by a computer using an interpreter, etc.

[0718] Although some aspects of the present disclosure have been described in the context of an apparatus, they may also be described in terms of a corresponding method, where a block or apparatus corresponds to a method step or feature of a method step. Similarly, aspects described in the context of a method may also be described in terms of a corresponding block or item or feature of a corresponding apparatus. Some or all of the method steps may be performed by (or using) a hardware device, such as, for example, a microprocessor, a programmable computer, or electronic circuitry. In some embodiments, at least one or more of the most significant method steps may be performed by such a device.

[0719] In some embodiments, a programmable logic device (e.g., a field programmable gate array) may be used to perform some or all of the functions of the methods described herein. In some embodiments, a field programmable gate array may operate in conjunction with a microprocessor to perform one of the methods described herein. In general, it is preferred that the methods be performed by some hardware device.

[0720] Although the present disclosure has been described above with reference to preferred embodiments, it will be understood by those skilled in the art that various modifications and variations of the present disclosure may be made without departing from the spirit and scope of the present disclosure as set forth in the following claims.

Claims

1. In a terminal method, receiving operation mode setting information for a first operation mode and a second operation mode from a base station; receiving, from the base station, resource allocation information for reporting channel state information (CSI) measured based on the operation mode configuration information; determining a CSI reference resource based on a preset CSI generation criterion; measuring first CSI received from the base station based on the operation mode setting information; confirming the validity of the measured first CSI; and transmitting a CSI report reflecting valid CSI measurements to the base station based on the confirmation; The valid CSI information is the case where an operation mode when measuring the first CSI and an operation mode when reporting CSI based on the CSI reference resource are the same.

2. The first operating mode is one of sub-band full duplex (SBFD) or full-duplex (FD); and The method of claim 1, wherein the second operation mode is one of a time-domain duplex (TDD) and a frequency-domain duplex (FDD) scheme.

3. The method of claim 2 , wherein, when in the first operating mode, the first CSI is measured in each of one or more subbands.

4. The method of claim 3, wherein, when reporting the CSI, if only some of the valid CSI measurements can be reported, valid CSI measurements to be transmitted are determined based on a predetermined priority.

5. The method further includes receiving first configuration information, in which at least one of a channel measurement resource (CMR) or an interference measurement resource (IMR) is configured, from the base station; If the first configuration information indicates CMR, the first CSI is composed of a non-zero-power (NZP) CSI-reference signal (RS), and The method of claim 1, wherein when the first configuration information is IMR, the first CSI is configured as one of NZP CSI-RS or ZP (zero-power) CSI-RS.

6. The method further includes not reflecting invalid CSI measurements in the CSI report based on the confirmation; The method of claim 5, wherein the invalid CSI measurement value is determined when an operation mode at the time of measurement of at least one of the CMR or IMR differs from an operation mode at the time of reporting the CSI based on the CSI reference resource.

7. At least one of the CMR or IMR is received periodically, semi-persistently, or aperiodically; and The method of claim 5, wherein the CSI report is transmitted to the base station periodically, semi-statically, or aperiodically.

8. The method of claim 1, wherein a transport block size (TBS) for the CSI report is determined based on at least one of a subband frequency resource or a time resource of an operation mode applied to the CSI reference resource.

9. In a base station method, transmitting operation mode setting information for the first operation mode and the second operation mode to the terminal; transmitting, to the terminal, resource allocation information for receiving a channel state information (CSI) report measured based on the operation mode configuration information; transmitting first CSI and CSI reference resources to the terminal based on the operation mode setting information; and receiving a CSI report from the terminal based on the resource allocation information; The first operating mode is one of sub-band full duplex (SBFD) or full-duplex (FD); and The second operation mode is one of a time-domain duplex (TDD) or a frequency-domain duplex (TDD) scheme.

10. The method of claim 9, wherein, in the first operating mode, the first CSI is transmitted on each of one or more subbands.

11. The method further includes transmitting first configuration information, in which at least one of a channel measurement resource (CMR) or an interference measurement resource (IMR) is configured, to the terminal; If the first configuration information indicates CMR, the first CSI is composed of a non-zero-power (NZP) CSI-reference signal (RS), and The method of claim 9, wherein when the first configuration information indicates IMR, the first CSI is configured as one of NZP CSI-RS or ZP (zero-power) CSI-RS.

12. At least one of the CMR or IMR is transmitted to the terminal periodically, semi-statically, or aperiodically; and The method of claim 11, wherein the CSI report is received from the terminal periodically, semi-statically, or aperiodically.

13. On the device, a processor, The processor is configured to: receiving operation mode setting information for a first operation mode and a second operation mode from a base station; receiving, from the base station, resource allocation information for reporting channel state information (CSI) measured based on the operation mode configuration information; Determine a CSI reference resource based on a preset CSI generation criterion; measuring first CSI received from the base station based on the operation mode setting information; confirming the validity of the measured first CSI; and causing the base station to transmit a CSI report reflecting valid CSI measurements based on the confirmation; The valid CSI information is when the operation mode when measuring the first CSI and the operation mode when reporting the CSI based on the CSI reference resource are the same.

14. The first operating mode is one of sub-band full duplex (SBFD) or full-duplex (FD); and The terminal of claim 13, wherein the second operation mode is one of a time-domain duplex (TDD) and a frequency-domain duplex (FDD) scheme.

15. The processor is configured to: The terminal of claim 14 , wherein when in the first operating mode, the first CSI further causes measurements to be taken on each of one or more subbands.

16. The processor is configured to: The terminal of claim 15, further causing the terminal to determine valid CSI measurement values ​​to be transmitted based on a predetermined priority when only a portion of the valid CSI measurement values ​​can be reported during the CSI reporting.

17. The processor is configured to: further causing the base station to receive first configuration information in which at least one of a channel measurement resource (CMR) or an interference measurement resource (IMR) is configured; If the first configuration information indicates CMR, the first CSI is composed of a non-zero-power (NZP) CSI-reference signal (RS), and The terminal of claim 13, wherein when the first configuration information indicates IMR, the first CSI is configured as one of NZP CSI-RS or ZP (zero-power) CSI-RS.

18. The processor is configured to: further causing invalid CSI measurements based on the confirmation not to be reflected in the CSI report; The terminal of claim 17, wherein the invalid CSI measurement value is determined when an operation mode at the time of measurement of at least one of the CRM or IMR differs from an operation mode at the time of reporting the CSI based on the CSI reference resource.

19. The processor is configured to: At least one of the CMR or IMR is received periodically, semi-persistently, or aperiodically; and The terminal of claim 17, further causing the CSI report to be transmitted to the base station periodically, semi-persistently, or aperiodically.

20. The terminal of claim 13, wherein a transport block size (TBS) for the CSI report is determined based on at least one of a subband frequency resource or a time resource of an operation mode applied to the CSI reference resource.

Images