Method and apparatus for resource management in a wireless communication system

Abstract

A method of resource management performed by an integrated access and backhaul (IAB) node in a communication system, according to one of the embodiments of the present invention, can include the steps of: receiving, from a superior node of the IAB node, a first higher layer signaling signal for resource configuration of the IAB node; receiving, from the superior node of the IAB node, a second higher layer signaling signal for resource configuration of the IAB node; and determining, based on the first higher layer signaling signal and the second higher layer signaling signal, that an IAB mobile terminal (LAB-MT) and an IAB distribution unit (LAB-DU) constituting the IAB node perform communication by being multiplexed by any one of time division, frequency division, and space division.

Description

Technical Field

[0001] This disclosure relates to resource management techniques in wireless communication systems, and more specifically, to resource management techniques in wireless communication systems employing integrated access and backhaul (IAB) networks. Background Technology

[0002] With the development of information and communication technologies, various wireless communication technologies have been developed. Typical wireless communication technologies include Long Term Evolution (LTE) and New Radio (NR) as defined in the 3rd Generation Partnership Project (3GPP) standards. LTE can be one of the fourth-generation (4G) wireless communication technologies, and NR can be one of the fifth-generation (5G) wireless communication technologies.

[0003] In 5G or next-generation communication technologies, higher data rates, greater communication capacity, lower latency, and wider coverage may be required compared to previous generations. To achieve these requirements, Integrated Access and Backhaul (IAB) network technology is being researched. An IAB node constituting an IAB network can consist of two elements: a distributed unit (i.e., IAB-DU) and a mobile terminal (i.e., IAB-MT).

[0004] In an exemplary embodiment of the communication system, an IAB node can be designed based on a time division multiplexing (TDM) scheme between the IAB-DU and the IAB-MT. In an IAB node designed based on a TDM scheme between the IAB-DU and the IAB-MT, radio resources (such as time and / or frequency resources) can be allocated to the IAB-DU and / or the IAB-MT based on the TDM scheme.

[0005] On the other hand, to meet the high communication performance requirements of the communication system, the IAB node may need to be designed to support multiplexing schemes that allow simultaneous transmission rather than TDM schemes. Here, multiplexing schemes that allow simultaneous transmission can refer to frequency division multiplexing (FDM), space division multiplexing (SDM), etc. A resource management technique may be needed for effectively allocating radio resources in the IAB node, which is designed to support TDM schemes and / or multiplexing schemes that allow simultaneous transmission.

[0006] The items described as prior art are prepared to facilitate an understanding of the background art of this disclosure and may include items that are not yet known to a person of ordinary skill in the art to which the exemplary embodiments of this disclosure pertain. Summary of the Invention

[0007] Technical issues This disclosure aims to provide a method and apparatus for efficiently performing radio resource allocation for IAB nodes in a wireless communication system employing an IAB network, the IAB nodes being designed to support TDM schemes and / or multiplexing schemes that allow simultaneous transmission.

[0008] Technical solutions According to an exemplary embodiment of the present disclosure for achieving this purpose, a resource management method performed by an Integrated Access and Backhaul (IAB) node in a communication system may include: receiving a first higher-level signaling signal for resource configuration of the IAB node from a parent node of the IAB node; receiving a second higher-level signaling signal for resource configuration of the IAB node from a parent node of the IAB node; and determining, based on the first higher-level signaling signal and the second higher-level signaling signal, that an IAB mobile terminal (MT) and an IAB distributed unit (DU) constituting the IAB node are multiplexed to perform communication using one of a time-division scheme, a frequency-division scheme, and a space-division scheme.

[0009] The first higher-layer signaling signal may include at least one of information at a specific point in time in the time domain regarding the communication direction configured for IAB-MT or the communication direction configured for IAB-DU, and the communication direction may include at least one of downlink (DL), uplink (UL), variable, or a combination thereof.

[0010] The first higher-level signaling signal may include a hard / soft / unavailable (HSNA) configuration for IAB-MT at a specific point in time in the time domain, or an HSNA configuration for IAB-DU.

[0011] The second higher-level signaling may include information about the simultaneous operation (SO) scheme of IAB-DU and IAB-MT.

[0012] Information regarding simultaneous operation schemes may include one of the following: a first case where both IAB-DU and IAB-MT transmit; a second case where both IAB-DU and IAB-MT receive; a third case where IAB-DU receives and IAB-MT transmits; a fourth case where IAB-DU transmits and IAB-MT receives; a fifth case where radio resources used by IAB-DU and IAB-MT are multiplexed in a frequency division scheme; and a sixth case where radio resources used by IAB-DU and IAB-MT are multiplexed in a space division scheme.

[0013] The second higher-level signaling signal may include at least one of a hard / soft / unavailable (HSNA) configuration configured for IAB-MT or an HSNA configuration configured for IAB-DU at a specific time point in the time domain and a specific location in the frequency domain.

[0014] The resource management method may further include: after receiving a second higher-layer signaling signal, receiving at least one physical layer signaling signal from the upper-level node for resource configuration of the IAB node, wherein, in the determination, based on the first higher-layer signaling signal, the second higher-layer signaling signal, and the at least one physical layer signaling signal, IAB-MT and IAB-DU may be determined to be multiplexed to perform communication.

[0015] The at least one physical layer signaling signal may include at least one of resource configuration information configured for IAB-MT or resource configuration information configured for IAB-DU, and the resource configuration information may include information on the availability indicator (AI) of soft resources for IAB-MT or IAB-DU.

[0016] Information about AI used for soft resources may be included in a predetermined DCI format and may include information about the availability of at least one of DL soft resources, UL soft resources, variable soft resources, or simultaneous operation (SO) soft resources.

[0017] Information for AI used for soft resources may include information relating to one of the HSNA configurations included in a first higher-level signaling signal or a second higher-level signaling signal.

[0018] According to another exemplary embodiment of the present disclosure for achieving this purpose, a resource management method performed by a first communication node in a communication system may include: sending a first higher-level signaling signal for resource configuration of the IAB node to an Integrated Access and Backhaul (IAB) node, which is a subordinate node of the first communication node; and sending a second higher-level signaling signal for resource configuration of the IAB node to the IAB node, wherein the first higher-level signaling signal and the second higher-level signaling signal include information for the IAB node to control the IAB Mobile Terminal (MT) and IAB Distributed Unit (DU) constituting the IAB node to perform communication by multiplexing one of a time division scheme, a frequency division scheme, and a space division scheme.

[0019] The first higher-layer signaling signal may include at least one of information at a specific point in time in the time domain regarding the communication direction configured for IAB-MT or the communication direction configured for IAB-DU, and the communication direction may include at least one of downlink (DL), uplink (UL), variable, or a combination thereof.

[0020] The first higher-level signaling signal may include a hard / soft / unavailable (HSNA) configuration for IAB-MT at a specific point in time in the time domain, or an HSNA configuration for IAB-DU.

[0021] The second higher-level signaling may include information about the simultaneous operation (SO) scheme of IAB-DU and IAB-MT.

[0022] Information regarding simultaneous operation schemes may include one of the following: a first case where both IAB-DU and IAB-MT perform transmission; a second case where both IAB-DU and IAB-MT perform reception; a third case where IAB-DU performs reception while IAB-MT performs transmission; a fourth case where IAB-DU performs transmission and IAB-MT performs reception; a fifth case where the radio resources used by IAB-DU and IAB-MT are multiplexed in a frequency division scheme; and a sixth case where the radio resources used by IAB-DU and IAB-MT are multiplexed in a space division scheme.

[0023] The second higher-level signaling signal may include at least one of a hard / soft / unavailable (HSNA) configuration configured for IAB-MT or an HSNA configuration configured for IAB-DU at a specific time point in the time domain and a specific location in the frequency domain.

[0024] The resource management method may further include: after sending a second higher-layer signaling signal, sending at least one physical layer signaling signal to the IAB node for resource configuration of the IAB node.

[0025] The at least one physical layer signaling signal may include at least one of resource configuration information configured for IAB-MT or resource configuration information configured for IAB-DU, and the resource configuration information may include information on the availability indicator (AI) of soft resources for IAB-MT or IAB-DU.

[0026] Information about AI used for soft resources may be included in a predetermined DCI format and may include information about the availability of at least one of DL soft resources, UL soft resources, variable soft resources, or simultaneous operation (SO) soft resources.

[0027] Information for AI used for soft resources may include information related to one of the HSNA configurations included in a first higher-level signaling signal or a second higher-level signaling signal.

[0028] Beneficial effects According to exemplary embodiments of this disclosure, the IAB-MT and IAB-DU included in an IAB node can communicate with their parent and child nodes respectively according to a TDD scheme or a simultaneous operation scheme. The parent node (such as an IAB donor of the IAB node) can deliver resource configuration information (or resource indicators) indicating information about the allocated resources for each of the IAB-DU and IAB-MT to the IAB node in the form of a TDM scheme, FDM scheme, SDM scheme, etc. Signals (such as DCI, FIAP, etc.) can be extended and used for the transmission of resource configuration information (or resource indicators) delivered from the parent node of the IAB node to the IAB node. Therefore, communication efficiency through the IAB node can be improved, its coverage can be expanded, and its communication capacity can be increased. Attached Figure Description

[0029] Figure 1 This is a conceptual diagram illustrating an exemplary embodiment of a radio interface protocol structure in a communication system.

[0030] Figure 2 This is a conceptual diagram illustrating an exemplary embodiment of time resources for transmitting radio signals in a communication system.

[0031] Figure 3 This 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 exemplary embodiment of a communication system.

[0032] Figure 4 This is a conceptual diagram illustrating an exemplary embodiment of a time / frequency resource grid in a communication system.

[0033] Figure 5 This is a conceptual diagram illustrating an exemplary embodiment of a synchronization signal and physical broadcast channel (SS / PBCH) block or synchronization signal block (SSB) in a communication system.

[0034] Figure 6 This is a sequence diagram illustrating an exemplary embodiment of a random access procedure in a communication system.

[0035] Figure 7 This is a conceptual diagram illustrating a first exemplary embodiment of SSB-RO association configured according to RACH in a communication system.

[0036] Figure 8 This is a conceptual diagram illustrating a second exemplary embodiment of SSB-RO association configured according to RACH in a communication system.

[0037] Figure 9 This is a conceptual diagram illustrating an exemplary embodiment of QCL information transmission processing via TCI status configuration and indication in a communication system.

[0038] Figure 10 This is a conceptual diagram illustrating an exemplary embodiment of TCI state activation / deactivation MAC CE in a communication system.

[0039] Figure 11 This is a conceptual diagram illustrating an exemplary embodiment of a TCI status indicator MAC CE in a communication system.

[0040] Figure 12 This is a conceptual diagram illustrating the time slot configuration according to the time slot format in a communication system.

[0041] Figure 13 This is a conceptual diagram illustrating an exemplary embodiment of an IAB network in a communication system.

[0042] Figure 14 This is a block diagram illustrating an exemplary embodiment of a functional separation structure of a central unit (CU) and a distributed unit (DU) in a communication system.

[0043] Figure 15 This is a flowchart illustrating a first exemplary embodiment of a method for resource management of an IAB node in a communication system.

[0044] Figure 16 This is a sequence diagram illustrating an exemplary embodiment of the UE capability reporting process in a communication system.

[0045] Figure 17 This is a flowchart illustrating a second exemplary embodiment of a method for resource management of an IAB node in a communication system.

[0046] Figure 18 This is a conceptual diagram illustrating an exemplary embodiment of a communication node in a communication system. Detailed Implementation

[0047] Because this disclosure is subject to various modifications and has several forms, specific exemplary embodiments will be shown in the accompanying drawings and described in detail in the specific implementation. However, it should be understood that this disclosure is not intended to be limited to the specific exemplary embodiments, but rather, this disclosure will cover all modifications and alternatives falling within the spirit and scope of this disclosure.

[0048] Relational terms such as "first," "second," etc., may be used to describe various elements, but elements should not be limited by the terms. These terms are used only to distinguish one element from another. For example, without departing from the scope of this disclosure, a first component may be named a second component, and a second component may similarly be named a first component. The term "and / or" refers to any one or a combination of multiple related and described items.

[0049] In exemplary embodiments of 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". Furthermore, in exemplary embodiments of 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".

[0050] When it is said that a component is “coupled” or “connected” to another component, it should be understood that the component is directly “coupled” or “connected” to the other component, or that the other component may be disposed between them. Conversely, when it is said that a component is “directly coupled” or “directly connected” to another component, it should be understood that the other component is not disposed between them.

[0051] The terminology used in this disclosure is used only to describe particular exemplary embodiments and is not intended to limit the disclosure. Unless the context clearly specifies otherwise, singular expressions include plural expressions. In this disclosure, terms such as “comprising” or “having” are intended to indicate the presence of features, quantities, steps, operations, components, parts, or combinations thereof described in the specification; however, it should be understood that these terms do not preclude the presence or addition of one or more features, quantities, steps, operations, components, parts, or combinations thereof.

[0052] Unless otherwise defined, all terms used herein (including technical and scientific terms) shall have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains. Terms that are commonly used and already in dictionaries shall be interpreted as having a meaning that matches the context in this art. In this specification, terms are not necessarily interpreted as having a formal meaning unless explicitly defined.

[0053] A communication system based on exemplary embodiments of the present disclosure will be described. The communication system based on exemplary embodiments of the present disclosure is not limited to what is described below, and can be applied to various communication systems. Here, the term "communication system" may be used in the same sense as "communication network".

[0054] Throughout this disclosure, networks may include, for example, wireless internet (such as Wi-Fi), mobile internet (such as WiBro or WiMax), 2G mobile communication networks (such as GSM or CDMA), 3G mobile communication networks (such as WCDMA or CDMA2000), 3.5G mobile communication networks (such as HSDPA or HSUPA), 4G mobile communication networks (such as LTE or LTE-Advanced), 5G mobile communication networks, etc.

[0055] Throughout this disclosure, "terminal" may refer to a mobile station, mobile terminal, user station, portable user station, user equipment, access terminal, etc., and may include all or part of the functions of a terminal, mobile station, mobile terminal, user station, mobile user station, user equipment, access terminal, etc.

[0056] Here, desktop computers, laptops, tablet PCs, cordless phones, mobile phones, smartphones, smartwatches, smart glasses, e-book readers, portable multimedia players (PMPs), portable game consoles, navigation devices, digital cameras, digital multimedia broadcast (DMB) players, digital audio recorders, digital audio players, digital image recorders, digital image players, digital video recorders, and digital video players, etc., with communication capabilities can be used as terminals.

[0057] Throughout this specification, "base station" may refer to an access point, radio access station, Node B (NB), evolved Node B (eNB), base transceiver station, mobile multi-hop relay (MMR)-BS, etc., and may include all or part of the functions of base stations, access points, radio access stations, NBs, eNBs, base transceiver stations, MMR-BS, etc.

[0058] In the following description, preferred exemplary 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 are used for the same elements in the drawings for ease of full understanding, and repeated descriptions of the same elements are omitted.

[0059] Figure 1 This is a conceptual diagram illustrating an exemplary embodiment of a radio interface protocol structure in a communication system.

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

[0061] Near PHY layer 130, RRC layer 110 and MAC layer 120 can be positioned above PHY layer 130. For example, MAC layer 120 can be positioned above PHY layer 130. RRC layer 110 can be positioned above MAC layer 120.

[0062] MAC layer 120 can be connected to a higher layer (e.g., RRC layer 110) via logical channel 115. PHY layer 130 can be connected to the higher MAC layer 120 via transport channel 125. PHY layer 130 can send control information or measurement information 150 to RRC layer 110 and receive control information or measurement information 150 from RRC layer 110.

[0063] PHY layer 130 can be referred to as "layer 1" or "L1". MAC layer 120 can be referred to as "layer 2" or "L2". RRC layer 110 can be referred to as "layer 3" or "L3". RRC layer 110 and MAC layer 120 can be collectively referred to as "higher layers".

[0064] In this disclosure, "L1 signaling" refers to signaling such as downlink control information (DCI) transmitted on the physical downlink control channel (PDCCH), uplink control information (UCI) transmitted on the physical uplink control channel (PUCCH), and sidelink control information (SCI) transmitted on the physical sidelink control channel (PSCCH), which are channels of PHY layer 130. Similarly, in this disclosure, "higher layer signaling" may include L2 signaling transmitted via MAC control elements (CE), L3 signaling transmitted via RRC signaling, etc. Although for ease of description... Figure 1 Information omitted in the text but which may be included in the interfaces between base stations or between base station components (such as the interfaces between distributed units (DU) and central units (CU)) (e.g., F1, next-generation (NG) interfaces, etc.) may also be collectively referred to as higher-level signaling and L2 or L3 signaling.

[0065] In communication systems that utilize 5G communication technologies, one or more parameter sets from Table 1 can be used for various purposes, such as reducing inter-carrier interference (ICI) based on frequency band characteristics, reducing latency based on service characteristics, etc.

[0066] [Table 1]

[0067] Table 1 is merely an example for ease of description, and exemplary embodiments of parameter sets used in a communication system are not limited thereto. Each parameter set It can be configured with subcarrier spacing (SCS). This corresponds to the information in the cyclic prefix (CP). The terminal can identify the parameter set applied to the downlink bandwidth portion (BWP) or the uplink BWP based on higher-level parameters (such as subcarrierSpacing and / or cyclicPrefix). And CP value.

[0068] Figure 2 This is a conceptual diagram illustrating an exemplary embodiment of time resources for transmitting radio signals in a communication system.

[0069] Reference Figure 2 It can include one or more ( ) Frame 230 of the subframe, including one or more ( Subframe 220 of the time slot and including 14 ( The OFDM symbol time slot 210 represents the time resource for transmitting radio signals in the communication system 200. In this case, according to the configured parameter set, as , and The values ​​can be used according to Table 2 below in the case of normal CP, and according to Table 3 below in the case of extended CP. OFDM symbols included in a time slot can be classified as "downlink", "flexible" or "uplink" by higher layer signaling or a combination of higher layer signaling and L1 signaling.

[0070] [Table 2]

[0071] [Table 3]

[0072] In a 5G NR communication system, frame 230 may have a length of 10 ms, and subframe 220 may have a length of 1 ms. Each frame 230 may be divided into two half-frames of equal length, and the first half-frame (i.e., half-frame 0) may consist of subframes #0 to #4, and the second half-frame (i.e., half-frame 1) may consist of subframes #5 to #9. A carrier may include a set of frames for the uplink (i.e., uplink frames) and a set of frames for the downlink (i.e., downlink frames).

[0073] Figure 3 This 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 exemplary embodiment of a communication system.

[0074] Reference Figure 3 The time difference between the reception timing of the i-th downlink frame 300 and the transmission timing of the i-th uplink frame 310 can be T. TA 320. Therefore, the terminal can receive the downlink frame #i 300 earlier than the receiving timing. TA The uplink frame #i 310 is sent starting at time T. TA This can be referred to as timing advance or timing adjustment of TA. The base station can instruct the terminal to change the TA via higher-layer signaling or L1 signaling. TA The value, and the terminal can be configured to be defined as Applying T in this way TA In the case of 5G NR, It can be defined as , It can be defined as , It can be defined as , It can be a value set by L3 signaling, and It can be determined by the value indicated by L2 signaling in Equation 1 below. A definite value.

[0075] [Equation 1]

[0076] Here, about and The description may be an example of a specific situation, and various other options may exist, but in order not to obscure the main point of the description, not all possible situations may be listed in this disclosure.

[0077] Figure 4 This is a conceptual diagram illustrating an exemplary embodiment of a time / frequency resource grid in a communication system.

[0078] Reference Figure 4 The time / frequency resource grid 400 of the communication system can have Subcarriers and One OFDM. A resource grid can be defined for each parameter set and each carrier. In this case, It can refer to the location of a Common Resource Block (CRB) indicated by higher-level signaling. It can refer to the number of resource blocks (RBs) starting from the CRB, which is the carrier bandwidth. and / or The parameter set μ can have different values ​​for each link direction (e.g., uplink, downlink, or sidelink) or for each parameter set μ. Here, the parameter set μ can be referred to by other terms (such as SCS configuration) if necessary.

[0079] Each element in the resource grid configured for antenna port p and SCS μ can be referred to as a resource element (RE) 420, and can be configured for each location. It is uniquely defined. In this case, It can be a frequency axis index, and It can indicate the position of a symbol on the timeline. Can be used with physical channels or signal complex values. The physical resources correspond to this. An RB 410 can be defined as a continuous frequency axis. Subcarriers.

[0080] 5G NR communication systems have introduced the concept of BWP (Block Window) to reduce the high implementation complexity and power consumption of terminals caused by the wider carrier bandwidth compared to 3G / 4G communication systems. A BWP can be composed of consecutive CRBs (Carrier Routers), with the starting RB position of the BWP... and the number of RBs that make up BWP Equations 2 and 3 can be satisfied.

[0081] [Equation 2]

[0082] [Equation 3]

[0083] The terminal can be configured with up to four downlink BWPs within a component carrier (CC), and only one downlink BWP can be activated at a time. The terminal may not receive the Physical Downlink Shared Channel (PDSCH), Physical Downlink Control Channel (PDCCH), Channel State Information Reference Signal (CSI-RS), etc., other than the activated BWP.

[0084] The terminal can be configured with up to four uplink BWPs within a single CC, and only one uplink BWP can be activated at a time. The terminal can transmit Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), Sound Reference Signal (SRS), etc., without using the activated BWPs.

[0085] Figure 5 This is a conceptual diagram illustrating an exemplary embodiment of a synchronization signal and physical broadcast channel (SS / PBCH) block or synchronization signal block (SSB) in a communication system.

[0086] Reference Figure 5 The SS / PBCH block 500 of the communication system can be configured with a primary synchronization signal (PSS) transmitted in 127 subcarriers in the middle of the first OFDM symbol, a secondary synchronization signal (SSS) transmitted in 127 subcarriers in the middle of the third OFDM symbol, and a physical broadcast channel (PBCH) transmitted in the second, third, and fourth OFDM symbols. The PBCH occupying the widest bandwidth can be transmitted on 20 RBs, which can be 3.6MHz based on a 15kHz SCS. The base station transmits one SSB by applying the same beam. When 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), the base station can support multi-beam operation by transmitting multiple SSBs. Here, when applied in practice, the term "beam" can be represented by various terms (such as transport precoding or spatial transmission (TX) filters). However, for the sake of not obscuring the main points of the description, "beam" is used as a uniform term below.

[0087] 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, beam #4). In this case, it is possible to transmit one or more SSBs within a time slot according to a pattern predetermined for each parameter set. SSBs 530, 540, 550, and 560 applying different beams can be bundled into a set by including them in an SS burst 520. The terminal may assume a half-frame window of 5ms length when monitoring SSBs. The SS burst set 515 configured by higher-layer signaling within the half-frame may include one or more SS bursts 520. If the RRC configuration value is unknown or unavailable when performing Initial Access (IA), the terminal may assume that the periodicity of the SS burst set 510 is 20ms when receiving or measuring SSBs. As an example, the terminal may receive one or more SSBs with reference to the following SSB configuration information.

[0088]

[0089]

[0090] Figure 6 This is a sequence diagram illustrating an exemplary embodiment of a random access procedure in a communication system.

[0091] Reference Figure 6During the random access process of communication system 600, terminal 615 may send a Physical Random Access Channel (PRACH) preamble, which may be referred to as "Msg1" (S620). Through the transmission of the PRACH preamble, the Random Access Radio Network Temporary Identifier (RA-RNTI) can be determined. In this case, RA-RNTI can be calculated using Equation 4.

[0092] [Equation 4] RA-RNTI = 1 + s_id + 14 × t_id + 14 × 80 × f_id + 14 × 80 × 8 ×ul_carrier_id In Equation 4, s_id can be the index of the first OFDM symbol of the corresponding PRACH timing (e.g., 0 ≤ s_id < 14), t_id can be the index of the first slot of the PRACH timing within the system frame (e.g., 0 ≤ t_id < 80), f_id can be the index of the PRACH timing in the time domain (e.g., 0 ≤ f_id < 8), and ul_carrier_id can be a value based on the uplink carrier type used for preamble transmission (e.g., 0 indicates a regular uplink carrier, 1 indicates a supplementary uplink carrier).

[0093] Before the terminal sends the PRACH preamble, the terminal may have at least a portion of the following information by receiving system information from the base station or receiving RRC signaling from the base station on the PBCH.

[0094] -PRACH leading format -Time / frequency resource information used for RACH transmission - Index of the logical root sequence table - Circular shift NCS - Collection types (unrestricted set A, restricted set B) Refer again Figure 6As a second process, the base station may provide the terminal with a Random Access Response (RAR), which may be referred to as "Msg2" (S630). Specifically, when the base station receives the PRACH preamble from the terminal in step S620, the base station may calculate the RA-RNTI based on Equation 4 and may transmit the DCI by using the RA-RNTI for scrambling. The terminal may monitor the PDCCH scrambled with the RA-RNTI in the time period included in the RACH response window configured by the higher layer in the Type 1 PDCCH Common Search Space (CSS). The terminal may receive the PDCCH (or the DCI transmitted from the base station via the PDCCH) and may decode the PDCCH (or DCI). If the terminal successfully decodes the PDCCH (or DCI), then in step S630, the terminal may decode the PDSCH including the RAR transmitted from the base station. If the terminal successfully decodes the RAR, the terminal may identify whether the RA preamble identifier (RAPID) in the RAR matches the RAPID pre-assigned to the terminal.

[0095] As a third process, the terminal may send a PUSCH (S640) to the base station, which may be referred to as "Msg3". For this purpose, the terminal may determine, based on higher-layer parameters (e.g., msg3-transformPrecoding), whether to apply transform precoding to the PUSCH transmission (i.e., whether to apply Discrete Fourier Transform (DFT)-s-OFDM-based transmission or OFDM-based transmission). Furthermore, the terminal may determine the SCS (Section Classification Class) to be used for the PUSCH transmission based on higher-layer parameters (e.g., msg3-scs). In this case, the Msg3 PUSCH can be transmitted via the serving cell to which the PRACH has already been sent.

[0096] As the fourth step, the base station may send a contention resolution message, referred to as "Msg4," to the terminal (S650). The terminal may start a timer for receiving the contention resolution message and may monitor the PDCCH scrambled with a 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 corresponding 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 acknowledgment (ACK) to the base station and may also report whether the RACH procedure was successful (S660).

[0097] RACH timing (RO) can refer to the time and frequency resources specified for receiving the RACH preamble, and the terminal can use the RO for PRACH transmission. As mentioned above, in 5G NR, multiple SSBs can be associated with different beams used for multi-beam operation, and the terminal can measure multiple SSBs and select the optimal SSB (i.e., the optimal beam) based on one of various schemes such as Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Signal-to-Noise Ratio (SNR), Signal-to-Noise Ratio (SNIR), etc. Subsequently, the terminal can determine the beam (i.e., the TX spatial filter) to be used for PRACH transmission based on the beam used when receiving the optimal SSB (i.e., the RX spatial filter). In this case, to allow the base station or network to know which SSB (i.e., beam) the terminal has selected, a relationship between (one or more) SSBs and (one or more) ROs can be established. Through this relationship, the base station can know the SSB (i.e., beam) selected by the terminal based on the RO of the PRACH that the terminal has transmitted. For example, the relationship between (one or more) SSBs and (one or more) ROs can be determined with reference to the following higher-level configuration.

[0098]

[0099]

[0100] Figure 7 This is a conceptual diagram illustrating a first exemplary embodiment of SSB-RO association configured according to RACH in a communication system.

[0101] Reference Figure 7 In the SSB-RO mapping relationship configured according to RACH, N SSBs 710-1 to 710-n with separate time resources in a certain frequency band can be mapped to ROs 720-1 to 720-n with separate time resources on a one-to-one basis. For example, if the higher-level parameter msg1-FDM is set to 1 (i.e., msg1-FDM=1) and the higher-level parameter ssb-perRACH-OccasionAndCB-PreamblesPerSSB is set to 1 (i.e., ssb-perRACH-OccasionAndCB-PreamblesPerSSB=1), then N different SSBs 710-1 to 710-n can be mapped to N different ROs 720-1 to 720-n on a one-to-one basis.

[0102] Figure 8 This is a conceptual diagram illustrating a second exemplary embodiment of SSB-RO association configured according to RACH in a communication system.

[0103] Reference Figure 8 In the SSB-RO association configured according to RACH, SSBs 810-1, 810-3, 810-5, ..., and 810-(n-1) that are time-different in the first frequency band can be associated with ROs 820-1, 820-3, 820-5, ..., and 810-(n-1) that are time-different in the first frequency band in a one-to-one scheme. Similarly, SSBs 810-2, 810-4, 810-6, ..., and 810-n that are time-different in the second frequency band can be associated with ROs 820-2, 820-4, 820-6, ..., and 810-n that are time-different in the second frequency band in a one-to-one scheme. In this case, higher-level frequency division parameters (e.g., ...) msg1-FDM ) can be set to 2 (e.g., msg1-FDM =2), and time-division higher-level parameters (e.g., ssb-perRACH- OccasionAndCB-PreamblesPerSSB ) can be set to 2 (e.g., ssb-perRACH-OccasionAndCB- PreamblesPerSSB =2). Thus, N different SSBs 810-1 to 810-n can be associated with N different ROs 820-1 to 820-n by occupying two bandwidths.

[0104] In addition, the 5G NR communication system can support the DCI format shown in Table 4 based on version 16.

[0105] [Table 4]

[0106] A DCI may include downlink control information for one or more cells and may be associated with an RNTI. A DCI may be encoded in the following order: 1) information element multiplexing, 2) cyclic redundancy check (CRC) addition, 3) channel coding, and 4) rate matching, and decoding may also take into account the above steps being performed. In the above description, "a DCI is associated with an RNTI" may mean that the CRC parity bits of the DCI are scrambled using the RNTI. Referring to Table 6, some DCIs may include scheduling information for one or more PUSCHs for a given cell.

[0107] For example, the CRC of DCI format 0_1 ​​can be scrambled using C-RNTI, configured schedule-RNTI (CS-RNTI), semi-persistent CSIRNTI (SP-CSI-RNTI), or modulation and coding scheme cell RNTI (MCS-C-RNTI). DCI format 0_1 ​​may include at least one of the following information.

[0108] □ Identifier for DCI format (1 bit): Indicator for UL DCI format, which is always set to 0 in the case of DCI format 0_1.

[0109] □ Carrier indicator (0 or 3 bits): Indicator indicating the CC scheduled by the corresponding DCI.

[0110] □DFI flag (0 or 1 bit): Configured Authorized Downlink Feedback Information (CG-DFI) indicator.

[0111] - If DCI format 0_1 ​​is used for the CG-DFI indication (when the DFI flag is set to 1), then at least one of the following fields may be used: □ HARQ-ACK bitmap (16 bits), in which the HARQ process indices are mapped in ascending order from the MSB to the LSB of the bitmap. For each bit in the bitmap, a value of 1 indicates ACK, and a value of 0 indicates NACK.

[0112] □ TPC command (2 bits) for PUSCH used for scheduling.

[0113] □ In DCI format 0_1, all remaining bits are set to zero.

[0114] - If DCI format 0_1 ​​is not used for CG-DFI indication (when there is no DFI flag field or the DFI flag field is set to 0), then at least one of the following fields may be used: □UL / SUL indicator (0 or 1 bit): Supplemental UL indicator.

[0115] □ Bandwidth Part Indicator (0, 1, or 2 bits): Indicator that indicates the BWP to be activated in the uplink BWP configured for the terminal.

[0116] □ Frequency Domain Resource Allocation: An indicator used to allocate frequency domain resources.

[0117] □ Time-domain resource allocation: An indicator used to allocate time-domain resources.

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

[0119] □ Modulation and coding scheme (5 bits).

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

[0121] □ Redundancy Version (RV): An indicator of the RV value when channel coding is applied to the allocated data.

[0122] □ HARQ process number (4 bits): An indicator that will be assigned to the HARQ process that will handle the scheduling data.

[0123] □ TPC command (2 bits) for PUSCH used for scheduling: TPC indicator.

[0124] □SRS Resource Indicator: Aperiodic SRS resource selection indicator.

[0125] □ Precoding information and layer number: Indicators that indicate precoding and the number of transport layers to be used in PUSCH transmission.

[0126] □ Antenna Port: Indicator for the uplink antenna port used for PUSCH transmission.

[0127] □SRS Request: An indicator that suggests whether to send an aperiodic SRS.

[0128] □CSI Request: An indicator that indicates whether and how channel status information should be reported.

[0129] □PTRS-DMRS Association: An indicator that shows the relationship between the uplink phase noise tracking reference signal (PTRS) antenna port and the demodulation reference signal (DMRS) antenna port.

[0130] □DMRS Sequence Initialization: An indicator for DMRS sequence initialization values ​​during OFDM-based uplink transmission.

[0131] □ UL-SCH Indicator: An indicator that indicates whether the uplink shared channel (UL-SCH) is included in the PUSCH (a PUSCH that does not include UL-SCH needs to include CSI).

[0132] □ Open-loop power control parameter set indication: An indicator that indicates a set of open-loop power control (OPLC) parameters.

[0133] □ Priority Indicator: Uplink transmission priority indicator.

[0134] □ Invalid Symbol Mode Indicator: Indicates whether an invalid symbol mode configured by a higher layer is applied.

[0135] As another example, the CRC of DCI format 1_1 can be scrambled using C-RNTI, CS-RNTI or MCS-C-RNTI, and DCI format 1_1 may include at least one of the following information.

[0136] □ Identifier for DCI format (1 bit): Indicator for DL ​​DCI format, which is always set to 1 in the case of DCI format 1_1.

[0137] □ Carrier indicator (0 or 3 bits): Indicator indicating the CC scheduled by the corresponding DCI.

[0138] □ Bandwidth Part Indicator (0, 1, or 2 bits): Indicator indicating which BWP will be activated in the downlink BWP configured for the terminal.

[0139] □ Frequency Domain Resource Allocation: An indicator used to allocate frequency domain resources.

[0140] □ Time-domain resource allocation: An indicator used to allocate time-domain resources.

[0141] □PRB Bundle Size Indicator: An indicator that indicates the type (i.e., static or dynamic) and size of the PRB bundle.

[0142] □ Rate Matching Indicator: An indicator that indicates the rate matching mode configured by a higher layer.

[0143] □ZP CSI-RS trigger: An indicator for applying non-periodic zero power (ZP) CSI-RS.

[0144] □ The "Modulation and Coding Scheme", "New Data Indicator", and "Redundancy Version" fields are used for transport block 1.

[0145] □ Used for the "Modulation and Coding Scheme", "New Data Indicator" and "Redundant Version" fields of transport block 2.

[0146] □ HARQ Process ID: An indicator that will be assigned to the HARQ process that will handle the scheduling data.

[0147] □ Downlink Allocation Index: A DAI indicator used in TDD operations for generating the HARQ-ACK codebook.

[0148] □ TPC commands for scheduling PUCCH: Power control indicator for PUCCH transmission.

[0149] □PUCCH Resource Indicator: An indicator for the PUCCH resource used to send HARQ-ACK messages for an allocated PDSCH or a predefined set of PDSCHs.

[0150] □PDSCH-to-HARQ_feedback timing indicator: An indicator that shows the time axis offset between the assigned PDSCH and PUCCH.

[0151] □ (one or more) Antenna ports: Indicators of the antenna ports that will be used for PDSCH transmission / reception.

[0152] □ Transmission Configuration Indicator: An indicator that indicates the Transmission Configuration Information (TCI) to be used for PDSCH transmission and reception.

[0153] □SRS Request: An indicator that suggests whether to send an aperiodic SRS.

[0154] □ DMRS Sequence Initialization: An indicator for the DMRS sequence initialization value used for PDSCH transmission and reception.

[0155] □ Priority Indicator: PDSCH Receive Priority Indicator.

[0156] As another example, certain DCI formats can be used to deliver the same control information to one or more terminals. For example, the CRC of DCI format 2_3 can be scrambled using Transmit Power Control-Probe Reference Signal-RNTI (TPC-SRS-RNTI) and can include at least one of the following information.

[0157] □ Block No. 1, Block No. 2, ..., Block No. B: Indicators for resource regions using DCI format 2_3. The beginning of the block is defined by higher-level parameters. startingBitOfFormat2-3 or startingBitOfFormat2-3SUL-v1530 Configuration.

[0158] -When higher-level parameters srs-TPC-PDCCH-Group When a terminal set to Type A performs an uplink transmission without PUCCH and PUSCH or an uplink transmission where SRS power control is not associated with PUSCH power control, a block is configured by a higher layer, and the following fields are defined for that block.

[0159] □SRS Request (0 or 2 bits): Aperiodic SRS transmission indicator.

[0160] □ TPC command number 1, TPC command number 2, ..., TPC command number N: Indicates that the command will be applied by higher-level parameters. cc- IndexInOneCC-Set An indicator for uplink power control of the indicated UL carrier.

[0161] -When higher-level parameters srs-TPC-PDCCH-Group When a terminal set to type B performs an uplink transmission without PUCCH and PUSCH or an uplink transmission where SRS power control is not associated with PUSCH power control, one or more blocks can be configured by a higher layer, and the following fields are defined for each block.

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

[0163] □TPC command (2 bits).

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

[0165] -When higher-level parameters slotFormatCombToAddModList When configured, □Slot format indicator 1, slot format indicator 2, ..., slot format indicator N.

[0166] -When higher-level parameters availableRB-SetsToAddModList-r16 When configured, □ Available RB set indicator 1, available RB set indicator 2, ..., available RB set indicator N1.

[0167] -When higher-level parameters co-DurationsPerCellToAddModList-r16 When configured, □COT duration indicator 1, COT duration indicator 2, ..., COT duration indicator N2.

[0168] -When higher-level parameters searchSpaceSwitchTriggerToAddModList-r16 When configured, □ Search space group switching flag 1, search space group switching flag 2, ..., search space group switching flag M.

[0169] The size of DCI format 2_0 can be set by higher-layer signaling to one of 0 to 128 bits. For example, DCI format 2_5 can be used to notify IAB nodes of the availability of soft-type resources. The CRC of DCI format 2_5 can be scrambled with the availability indicator -RNTI (AI-RNTI) and can include the following information.

[0170] □ Availability indicator 1, availability indicator 2, ..., and availability indicator N.

[0171] The size of DCI format 2_5, a value less than or equal to 128 bits, can be set by higher-level signaling. The terminal can receive the following configuration information for CORESET#0 and search space#0.

[0172]

[0173] The terminal can refer to the following higher-level configurations for cell-specific PDCCH monitoring.

[0174]

[0175]

[0176]

[0177] The terminal can refer to the following higher-level configurations for UE-specific PDCCH monitoring.

[0178]

[0179] The existence of an antenna port can mean that the channel experienced by a symbol transmitted through the corresponding antenna port can be estimated or inferred from the channel experienced by another symbol transmitted through the same antenna port.

[0180] "Two different antenna ports are quasi-co-located (QCL)" can mean a situation where the large-scale characteristics of the channel experienced by a symbol transmitted through one antenna port can be estimated or inferred from the channel experienced by a symbol transmitted through the other antenna port. The large-scale characteristics of the channel can refer to at least one of "delay spread", "Doppler spread", "Doppler shift", "average gain", "average delay", and "spatial Rx parameter".

[0181] When time / frequency resources are insufficient for a signal (e.g., the QCL target RS) and the large-scale characteristics of the channel cannot be accurately measured using only the corresponding signal, information about another signal (e.g., a QCL reference RS with sufficient time / frequency resources) that can be repeatedly used to receive the corresponding signal (i.e., the QCL target RS) (i.e., QCL information) can be provided to the terminal to improve the terminal's channel measurement performance. NR communication systems can support various QCL types as follows.

[0182] -QCL-Type A: Includes {Doppler frequency shift, Doppler spread, average delay, delay spread}.

[0183] -QCL-Type B: Includes {Doppler frequency shift, Doppler spread}.

[0184] -QCL-Type C: Includes {Doppler shift, average delay}.

[0185] -QCL type D: includes {space Rx parameter}.

[0186] Figure 9 This is a conceptual diagram illustrating an exemplary embodiment of QCL information transmission processing via TCI status configuration and indication in a communication system.

[0187] Reference Figure 9In process 900 of transmitting QCL information through TCI state configuration and indication in a communication system, the base station may configure at most M TCI states for the terminal through higher-layer (i.e., RRC) signaling according to the UE capability report and the maximum value defined in the technical specification (e.g., 4, 8, 64, or 128 depending on the frequency band) (S930). In this case, each TCI state configuration 910 may include information about a signal or channel (i.e., QCL reference 915) that provides large-scale channel characteristics for a signal or channel that is a reference TCI (i.e., QCL target 920). One TCI state configuration 910 may include up to two references (i.e., qcl-Type 1 and qcl-Type 2), where the first reference can be one of QCL-Type A, QCL-Type B and QCL-Type C (i.e., qcl-Type 1∈{QCL-Type A, QCL-Type B, QCL-Type C}), and the second reference can be QCL-Type D if present (i.e., qcl-Type 2 = QCL-Type D).

[0188] Allowing the base station to use all TCI configured through RRC signaling in real time may greatly increase the implementation complexity of the terminal. The base station may transmit an activation message for some of the TCI configured through RRC signaling to the terminal through L2 signaling (such as MAC CE) (S940). The base station can activate a maximum of N (<M) TCI, and the terminal can receive dynamic indications only for activated TCI.

[0189] Thereafter, the base station may dynamically indicate some of the activated N TCI to the terminal through L1 signaling (such as DCI) (S950). The terminal may apply the QCL information indicated by the corresponding TCI at a predetermined timing after receiving the L1 signaling, and may perform a reception operation on a signal or channel.

[0190] Depending on the type of the QCL target RS, Figure 9 the TCI state indication steps of "RRC signaling (S930)", "MAC CE signaling (S940)" and "DCI signaling (S950)" may be partially omitted. For example, when the QCL target is PDSCH DMRS and one or more TCI states are configured through RRC signaling, the base station may use Figure 9 all of the above steps to indicate the TCI state. However, when the QCL target is PDSCH DMRS and a single TCI state is configured through RRC signaling, the MAC CE signaling (S940) and DCI signaling step (S950) may be omitted. Similarly, when the QCL target is PDCCH DMRS, the DCI signaling step S940 may be omitted. Specifically, the terminal may refer to RRC signaling to obtain configuration information and QCL information for the TCI state as follows.

[0191]

[0192] The base station can instruct the terminal to activate or deactivate some of the TCI states configured by RRC signaling via MAC CE signaling, or it can instruct the terminal to apply the TCI states 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 the QCL target RS.

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

[0194] - TCI status indication MAC CE for UE-specific PDCCH DMRS.

[0195] - TCI state activation / deactivation MAC CE for enhanced UE-specific PDSCH DMRS.

[0196] Figure 10 This is a conceptual diagram illustrating an exemplary embodiment of TCI state activation / deactivation MAC CE in a communication system.

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

[0198] -Serving Cell ID: The serving cell ID of the application MAC CE.

[0199] -BWP ID: The BWP ID of the MAC CE application, which indicates the BWP associated with the BWP indicator field within the DCI.

[0200] -Ti: Indicates TCI state ID i. When this value is set to 0, it means that the TCI state with TCI state ID i is deactivated, while when this value is set to 1, it means that the TCI state with TCI state ID i is activated. TCI states activated by 1 can be sequentially mapped to TCI indicator field code points within the DCI.

[0201] -CORESET pool ID: If the DCI for scheduling PDSCH does not include higher-level parameters. coresetPoolIndexIf the CORESET is monitored, this field can be ignored. If the DCI scheduling PDSCH includes higher-level parameters... coresetPoolIndex If monitored in the CORESET, then only if the value of the CORESET pool ID matches the value of the CORESET. coresetPoolIndex The Ti indicator can only be applied when the value matches.

[0202] Figure 11 This is a conceptual diagram illustrating an exemplary embodiment of a TCI status indicator MAC CE in a communication system.

[0203] Reference Figure 11 The first octet (Oct 1) in the TCI status activation / deactivation MAC CE for UE-specific PDSCH DMRS may include the serving cell ID field 1110 and the CORESET ID field 1120, and the second octet (Oct 2) may include the CORESET ID field 1130 and the TCI status ID field 1140. Its size may be variable.

[0204] -Serving Cell ID: The serving cell ID of the MAC CE corresponding to the application.

[0205] -CORESET ID: Indicates the CORESET of the applied MAC CE. If this value is set to 0, then... controlResourceSetZero The configured CORESET can be CORESET#0.

[0206] -TCI Status ID: Refers to the TCI status ID indicated by the corresponding MAC CE.

[0207] The base station can configure spatial relationship information to the terminal via higher-level (e.g., RRC) signaling to indicate uplink beam information. Spatial relationship information can refer to the signaling structure used to apply spatial domain filters for transmission and reception of the reference RS to the spatial TX filter for uplink transmission of the target RS according to the corresponding spatial relationship. The spatial reference RS can be a downlink signal (such as an SSB or CSI-RS) and can also be an uplink signal (such as an SRS). If the reference RS is a downlink signal, the terminal can use the spatial RX filter value used for receiving the reference RS as the spatial TX filter value used for transmitting the target RS, according to the spatial relationship. If the reference RS is an uplink signal, the terminal can use the spatial TX filter value used for transmitting the reference RS as the spatial TX filter value used for transmitting the target RS, according to the spatial relationship.

[0208] The signaling structure used for spatial relationship information can vary depending on the type of the target RS. For example, when the target RS is an SRS, the base station can perform RRC configuration for each SRS resource based on the following message.

[0209]

[0210] For example, when the target RS is an SRS, the base station can perform RRC configuration for each SRS resource as follows.

[0211]

[0212] Furthermore, it is often impossible to force all terminals to implement the same features. UE capability reporting allows expensive terminals to implement a large number of features with high performance, and low-cost terminals to implement a small number of features with low performance. UE capability reporting ensures the degree of freedom for terminal implementation in various situations, and when capability information is reported to the network, the base station can configure each function within the limits supported by each terminal. Some functions can be committed to being mandatory for all terminal implementations, and in this case, UE capability reporting for mandatory functions may be omitted.

[0213] A terminal may perform different UE capability reports for a single function for each frequency band or for each duplex scheme. For example, a terminal may support a specific function for frequency range 1 (FR1) (meaning a frequency band below 6 GHz), but may report to the base station that it does not support a specific function for frequency range 2 (FR2) (meaning a frequency band above 6 GHz). As another example, a terminal may report to the base station that it supports a specific function in TDD scheme but does not support a specific function in FDD scheme.

[0214] When a terminal executes a UE capability report, the base station should follow (and should not violate) the content of the UE capability report when performing configuration, instruction, or scheduling on the terminal. If the base station instructs the terminal to perform configuration, instruction, or scheduling that contradicts the UE capability report, the terminal may ignore it.

[0215] In a 5G NR communication system, the time slot format may include one or more downlink symbols, one or more uplink symbols, and / or one or more variable symbols.

[0216] Figure 12 This is a conceptual diagram illustrating the time slot configuration according to the time slot format in a communication system.

[0217] Reference Figure 12In a time slot configuration based on a time slot format in a communication system, a downlink-dedicated time slot 1200 can be a time slot in which all symbols within the time slot are configured only as downlink symbols 1215 according to the time slot format. As another example, an uplink-dedicated time slot 1205 can be a time slot in which all symbols within the time slot are configured only as uplink symbols 1220 according to the time slot format. As yet another example, in a mixed downlink / uplink time slot 1210, some symbols within the time slot can be configured as downlink symbols 1225, while some symbols within the time slot can be configured as uplink symbols 1235, depending on the time slot format. In this case, specific symbols in the mixed time slot 1210, which includes both uplink and downlink symbols, can be configured or indicated as a protection period 1230 for downlink-uplink switching, and the terminal can refrain from transmitting / receiving during the protection period 1230.

[0218] In a 5G NR communication system, the base station can configure a "time slot format" for the terminal on one or more time slots for each serving cell via the higher-layer parameter tdd-UL-DL-ConfigurationCommon. In this case, the higher-layer parameter tdd-UL-DL-ConfigurationCommon may include or refer to at least one of the following information.

[0219] - Reference subcarrier spacing: Reference parameter set -Mode 1: First mode.

[0220] -Mode 2: Second mode.

[0221] Here, mode 1 or mode 2 may include at least one of the following configurations.

[0222] -Time slot configuration periodicity (i.e., dl-UL-TransmissionPeriodicity : The periodicity P of the time slot configuration expressed in milliseconds (msec).

[0223] - The number of dedicated downlink time slots (i.e., nrofDownlinkSlots ): The number of time slots consisting only of downlink symbols .

[0224] - The number of downlink symbols (i.e., nrofDownlinkSymbols ): Number of downlink symbols .

[0225] - The number of dedicated uplink time slots (i.e., nrofUplinkSlots ): The number of time slots consisting only of uplink symbols .

[0226] - The number of uplink symbols (i.e., nrofUplinkSymbols ): Number of uplink symbols .

[0227] The time slot configuration periodicity P milliseconds in the first mode may include Each time slot, and in this case, can follow a parameter set. Additionally, in In the gap of time, the first A time slot may consist of only downlink symbols, and finally... A time slot may consist of only uplink symbols. In this case, the first... After the time slot This symbol can be a downlink symbol. Additionally, at the end... Before the time slot The symbol can be an uplink symbol. The remaining symbols not designated as downlink or uplink symbols in this mode (i.e., The symbol can be a variable symbol.

[0228] If the second mode is configured and the time slot configuration period of the second mode is The time slot configuration with a combination of the first and second modes is periodic. Milliseconds may include the first One time slot and the second Each time slot. In this case, the position and number of downlink symbols, uplink symbols, and variable symbols in the second mode can be configured based on the configuration information of the second mode, with reference to the description of the first mode. Additionally, when the second mode is configured, the terminal can assume... It is the divisor of 20 milliseconds.

[0229] The base station can use higher-layer parameters (e.g., based on the following information) tdd-UL-DL- ConfigurationDedicated To cover through higher-level parameters (e.g., tdd-UL-DL- ConfigurationCommon The direction of (one or more) variable symbols in the configured symbols.

[0230] -Time slot configuration set (i.e., slotSpecificConfigurationsToAddModList ): A set of time slot configurations.

[0231] -Time slot index (i.e., slotIndex ): The index of the time slots included in the set of time slot configurations.

[0232] -Sign direction (i.e., symbols ): by time slot index (i.e., slotIndexThe symbol direction is indicated by `symbols = allDownlink`. If all symbols are in downlink direction (`symbols = allUplink`), then all symbols in the corresponding time slot are downlink symbols. If all symbols are in uplink direction (`symbols = allUplink`), then all symbols in the corresponding time slot are uplink symbols. If the symbol direction is explicit (`symbols = explicit`), then... nrofDownlinkSymbols It can indicate the number of downlink symbols located in the first part of the corresponding time slot, and nrofUplinkSymbols This indicates the number of uplink symbols located in the last part of the corresponding time slot. If nrofDownlinkSymbols or nrofUplinkSymbols If omitted, the corresponding parameter can be considered as an indicator value of 0. The remaining symbols in the time slot become variable symbols.

[0233] In 5G communication systems, base stations can indicate time slot formats to terminals based on L1 signaling. For example, when a terminal receives higher-level parameters from the base station... SlotFormatIndicator At this time, the terminal can obtain the configuration information of the Time Slot Format Indicator - RNTI (i.e., SFI-RNTI). Additionally, when the terminal receives higher-layer parameters from the base station... dci-PayloadSize At this time, the terminal can obtain configuration information on the payload size of DCI format 2_0. Additionally, the terminal can receive information from the base station regarding one or more PDCCH candidates, CCE aggregation levels, and one or more search space sets for monitoring the CORESET of DCI format 2_0. Each slot format indication (SFI) index field in DCI format 2_0 can indicate the slot format to be applied to each slot in the slot set of DL BWPs and UL BWPs from which the terminal has detected a slot corresponding to DCI format 2_0. In this case, the size of the slot set can be equal to or greater than the PDCCH monitoring periodicity of DCI format 2_0. For example, when the slot set consists of N slots, DCI format 2_0 can include N SFI index fields, and each SFI index field can indicate the format value in Table 5 below. In Table 5, "D" can refer to a downlink symbol, "U" can refer to an uplink symbol, and "F" can refer to a variable symbol.

[0234] [Table 5]

[0235]

[0236] In 5G NR communication systems, it is possible to support flexible and dense wireless backhaul links for each cell through the IAB feature, without supporting wired networks.

[0237] Figure 13This is a conceptual diagram illustrating an exemplary embodiment of an IAB network in a communication system.

[0238] Reference Figure 13 The communication system 1300 may include one or more communication nodes. The communication nodes of the communication system 1300 may form an IAB network. For example, the communication system 1300 may include one or more IAB nodes. Figure 13 An exemplary embodiment of an IAB node communicating with one or more superior nodes and one or more subordinate nodes is shown. However, this is merely an example for ease of description, and the exemplary embodiments of this disclosure are not limited thereto.

[0239] 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 superior nodes of the first IAB node 1310, and / or one or more child nodes corresponding to the subordinate nodes of the first IAB node 1310. Here, each of the one or more parent nodes 1320 may be referred to as a "donor node". The IAB node 1310, one or more parent nodes 1320 and / or one or more child nodes 1330 may constitute an IAB network. Each of the IAB nodes 1310, 1320 and 1330 constituting the IAB network may be used as a repeater based on a fronthaul architecture configuration. In the communication system 1300 applying IAB network technology, flexible and dense wireless backhaul links for each cell can be supported without wired network support.

[0240] Each of IAB nodes 1310, 1320, and 1330 may include an IAB-DU and an IAB-MT. The IAB-MT allows each IAB node to function as a terminal communicating with a superior node. For example, the first IAB node 1310 can communicate with its superior parent node 1320 via the IAB-MT. Conversely, the IAB-DU allows each IAB node to function as a base station or cell communicating with subordinate nodes. For example, the first IAB node 1310 can communicate with its subordinate child node 1330 or terminal 1340 via the IAB-DU.

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

[0242] After the IAB nodes forming the IAB network fully decode the received signal, they can re-encode the decoded signal, amplify it, and transmit it. IAB nodes can be classified as a type of regenerative relay. To this end, IAB nodes can support both the control plane (CP) and user plane (UP) from the parent node to the terminal, based on a protocol stack architecture including L1 and L2 layers or higher.

[0243] IAB nodes that make up an IAB network have the advantage of being able to perform a variety of operations, including acting as base stations and terminals. On the other hand, the disadvantages of IAB nodes are their relatively high implementation complexity and production cost, and the potentially relatively large latency required for retransmission.

[0244] Figure 14 This is a block diagram illustrating an exemplary embodiment of a functional separation structure of a central unit (CU) and a distributed unit (DU) in a communication system.

[0245] Reference Figure 14 In the CU-DU functional separation architecture of the IAB network, IAB nodes 1410 and 1415 in the two-hop chain are connected to IAB donor 1405, and each of IAB nodes 1410 and 1415, as well as terminals 1420, 1422, and 1424, can be connected to the Next Generation Core (NGC) 1400 in standalone (SA) mode. IAB nodes 1410 and 1415 may each include a DU and a MT. An IAB node (e.g., 1415) may be connected to its parent IAB node 1410 or IAB donor 1405 via MT 1417. As another example, an IAB node (e.g., 1410) may establish an RLC channel with the MT 1417 of its child IAB node 1415 via DU 1414. In this case, in addition to the existing components of the RLC channel used for the terminal, the RLC channels 1450 and 1452 established for MT 1412 and 1417 may additionally include some information for IAB operation. Therefore, RLC channels 1450 and 1452 can be collectively referred to as "modified RLC". (RLC) )".

[0246] An IAB node can be connected to one or more parent IAB nodes or IAB donor DUs. In this case, an IAB node may include multiple DUs, but each DU of the IAB node may have an F1-C connection 1440 or 1442 to a single IAB donor CU-CP. Even if an IAB node has multiple UP connections, the IAB node can operate based on a single CP connection (i.e., an IAB node can operate by being connected to a single IAB donor), thus preventing confusion in the operation of the IAB node.

[0247] IAB donor 1405 may include a DU for supporting the MT of the terminal and child IAB nodes. IAB donor 1405 may include a CU 1407 for DUs 1409, 1414, and 1419 for itself and all child IAB nodes. It can be assumed that an IAB donor has a single IAB donor, and the IAB donor managing the corresponding IAB donor can be changed through topology adaptation functionality. The DU of an IAB node can be accessed via the F1 interface or a modified F1 interface (modified F1, F1...). (e.g., 1440, 1442) are connected to the CU of the corresponding IAB donor. F1 - The user plane (U) can operate on RLC channels 1450 and 1452 between the corresponding IAB-MT 1417 and 1412 and the parent IAB node or donor's DU 1414 and 1409.

[0248] In the following description, for ease of description, higher-level parameters or higher-level configurations in this disclosure may not be limited to the L2 and L3 signaling described above, and may collectively include information sent or configured through F1 interfaces 1440 and 1442, NG interface 1430 for connecting the CU to the NGC, and X2 interface, etc.

[0249] Although it may look like a reference Figure 11 and Figure 12 The described time slot format configuration and indication methods are limited to terminals communicating with base stations, but this is merely an example for ease of description, and exemplary embodiments of this disclosure are not limited thereto. For example, refer to Figure 11 and Figure 12 The described slot format configuration and indication methods can be similarly applied to the cases of IAB-DU and / or IAB-MT. For example, for each serving cell of IAB-DU, IAB-DU can receive higher-layer parameters for IAB-DU resource configuration (e.g., IAB-DU-Resource-Configuration This allows configuring the slot format in each slot set. On the other hand, IAB-MT can configure it via higher-level parameters. tdd-UL-DL-ConfigurationDedicated-IAB-MT The IAB-MT receives configuration information for the "slot format" on one or more slots for each serving cell from at least one parent node. This configuration information is obtained when the IAB-MT receives higher-layer parameters. tdd-UL-DL-ConfigurationDedicated-IAB-MT At that time, the received higher-level parameters can replace the higher-level parameters in the above-described time slot format configuration and indication methods. tdd-UL-DL- Configuration Dedicated d. Specifically, higher-level parameters tdd-UL-DL-ConfigurationDedicated-IAB- MT This may include the following information.

[0250] IAB-MT slot configuration set (i.e., slotSpecificConfigurationsToAddModList-IAB-MT ): A set of time slot configurations.

[0251] Time slot index (i.e., slotIndex ): The index of a time slot included in the set of time slot configurations.

[0252] IAB-MT symbol direction (i.e., symbols-IAB-MT ): The direction of the time slot indicated by the time slot index.

[0253] If the IAB-MT symbols are all in the downlink direction ( symbols-IAB-MT= allDownlink If ), then all symbols within the corresponding time slot are downlink symbols.

[0254] If the IAB-MT symbols are all in the uplink direction ( symbols-IAB-MT = allUplink If ), then all symbols within the corresponding time slot are uplink symbols.

[0255] If the IAB-MT symbol direction is explicit ( symbols-IAB-MT = explicit ),but nrofDownlinkSymbols It can indicate the number of downlink symbols located in the first part of the time slot, and nrofUplinkSymbols This indicates the number of uplink symbols located in the last part of the corresponding time slot. If nrofDownlinkSymbols or nrofUplinkSymbols If omitted, the corresponding parameter can be considered as an indicator value of 0. The remaining symbols in the time slot become variable symbols.

[0256] If the IAB-MT sign direction is explicit ( symbols-IAB-MT = explicit-IAB-MT ),but nrofDownlinkSymbols It can indicate the number of downlink symbols located in the first part of the time slot, and nrofUplinkSymbols This indicates the number of uplink symbols located in the last part of the corresponding time slot. If nrofDownlinkSymbols or nrofUplinkSymbols If omitted, the corresponding parameter can be considered as an indicator value of 0. The remaining symbols in the time slot become variable symbols.

[0257] Similar to the ordinary terminal described above, the IAB-MT can also receive DCI format 2_0, and through this, it can receive the time slot format configuration information from the base station of the parent node's IAB-DU. When DCI format 2_0 is received by the IAB-MT, the candidate values ​​for each SFI field are not limited to those shown in Table 5. For example, the candidate values ​​for each SFI field of DCI format 2_0 received by the IAB-MT may also include those shown in Table 6.

[0258] [Table 6]

[0259]

[0260] IAB-MT can be configured through higher-level parameters (e.g., Provided Guard Symbols The MAC CE is used to receive information about symbols that will not be used by IAB-MT for a serving cell. IAB-MT can perform a transition (i.e., operation change) between IAB-MT and IAB-DU at the IAB node during a time period that includes symbols not used by IAB-MT. The base station can obtain this information through higher-level parameters (e.g., Provided Guard Symbols MAC CE sends a set of parameters for symbols to the terminal using signals.

[0261] In a cell of an IAB-DU, the symbols within a time slot can be configured as one of three types: "hard", "soft", and "unusable (or unavailable)" (HSNA).

[0262] If a downlink, uplink, or variable symbol is configured as hard-type, the cell of the IAB-DU can perform signal transmission and / or reception operations in the corresponding symbol. This may mean that the fact that a symbol is configured as hard-type guarantees a reflection of the downlink, uplink, or variable symbol configuration for the corresponding IAB-DU.

[0263] Specifically, in an exemplary embodiment of the communication system, F1 Application Protocol (F1AP) signaling as shown in Table 7 can be provided, and higher-level IAB nodes (e.g., IAB donors, parent nodes, core networks, etc.) can configure the DU resource types of lower-level IAB nodes (e.g., IAB nodes, child nodes). Referring to Table 7, the DU resource type information may include a list of HSNA time slot configurations consisting of one or more HSNA time slot configurations. In this case, a list of HSNA time slot configurations may include information based on the maximum number of HSNAs (e.g., ...). maxnoofHSNA The HSNA slot configuration of the nth slot, included in the HSNA slot configuration list, may include information about the application periodicity and start time of the application of hard type, soft type, or unavailable type to each of the downlink symbols, uplink symbols, and variable symbols in the nth slot.

[0264] [Table 7]

[0265] If a downlink, uplink, or variable symbol is configured as soft type, the IAB-DU cell can perform signal transmission and reception operations in the symbol when at least one of the following conditions is met.

[0266] -Condition 1: IAB-MT (corresponding to / associated with IAB-DU) does not perform transmission or reception in the corresponding symbol.

[0267] -Condition 2: The IAB-MT (corresponding to / associated with the IAB-DU) can perform transmission or reception in the corresponding symbol, but the transmission / reception operation of the IAB-MT will not be changed by the use of a symbol at the IAB-DU.

[0268] -Condition 3: The IAB-MT (corresponding to / associated with IAB-DU) receiver indicates that the corresponding soft symbol is "available" in DCI format 2_5.

[0269] If a downlink, uplink, or variable symbol is configured as "unavailable (or unusable (NA)) type", then the IAB-DU (i.e., the cell) cannot perform transmission or reception in the symbol.

[0270] If the IAB-DU transmits one of the cell-specific, periodic, or semi-static signals or channels included in the following list in one or more symbols of a time slot, the IAB-DU can perform transmit / receive operations by assuming that one or more corresponding symbols in the corresponding time slot are configured as hard-type, regardless of the configured resource type.

[0271] -SS / PBCH block, CSS set of type 0-PDCCH configured by System Information Block 1 (SIB1) for PDCCH configuration (i.e., for configuration by...) pdcchConfigSIB1 Configuration types include 0-PDCCH (PDCCH of CSS sets), periodic CSI-RS, etc.

[0272] If the IAB-DU receives a cell-specific, periodic, or semi-static signal or channel from one or more symbols in a specific time slot, the IAB-DU can perform a transmit / receive operation by assuming that one or more corresponding symbols in the corresponding time slot are configured as hard-type, regardless of the configured resource type.

[0273] PRACH, Scheduling Request (SR) - The following information can be configured for each cell in the IAB-DU cell set.

[0274] IAB-DU cell identifier (i.e., iabDuCellId-AI ): Identifier of IAB-DU cell AI location within the DCI format (i.e., positionInDCI-AI ): The location of the Availability Identifier (AI) index field in DCI format 2_5.

[0275] Availability combination (i.e., availabilityCombinations ): This includes a list of the following two pieces of information used for availability combinations.

[0276] -Resource availability (i.e., resourceAvailability ): Indicates the resource availability for soft symbols included in one or more time slots of an IAB-DU cell. The availability of soft symbols within a time slot can be determined by referring to the values ​​in Table 17.

[0277] -Availability combination identifier (i.e., availabilityCombinationId ): Indicates resource availability (i.e., resourceAvailability The mapping between AI index fields in DCI format 2_5 and the AI ​​index field in DCI format 2_5.

[0278] As described above, in DCI format 2_5, an AI index field can indicate to the IAB-DU the availability of soft symbols included in each slot of a certain slot set. In this case, the slot set can start from the earliest slot of the IAB-DU that overlaps with the slot of the corresponding DCI format 2_5 detected by IAB-MT on the time axis. Furthermore, the size of the slot set can be greater than or equal to the size of the slots from higher-level parameters. Search Space The given PDCCH monitoring periodicity is in DCI format 2_5. The AI ​​index field in DCI format 2_5 may include... Bits, and can be mapped to one of the values ​​in Table 17. In this case, the maximum value of the AI ​​index (i.e., maxAIindex ) can refer to the provided availability combination identifier (i.e., availabilityCombinationID The maximum value in ). Table 8 indicates the mapping between resource availability values ​​and soft symbol types within a time slot.

[0279] [Table 8]

[0280] As described above, the superior IAB node, including the IAB donor, can instruct the subordinate IAB node whether to use soft symbols based on the contents of DCI format 2_5 and Table 17. On the other hand, such functionality can assume that the IAB nodes are designed to operate in half-duplex mode. In other words, such functionality can primarily assume that the MT and DU of the IAB node are designed to operate in time-division multiplexing (TDM) or time-division duplex (TDD) schemes.

[0281] In an exemplary embodiment of the communication system, F1AP signaling as shown in Table 18 can be used. Through this, an IAB node can report or deliver multiplexing information about the multiplexing capabilities between its IAB-DU (or gNB-DU cell) and its IAB-MT (or cells configured in co-located IAB-MTs) to a superior IAB node (e.g., an IAB donor or parent node). Referring to Table 18, the multiplexing information may include a list of IAB-MT cells consisting of information about one or more IAB-MT cells. In this case, an IAB-MT cell list can be based on the maximum number of serving cells (i.e., maxnoofServingCells This includes IAB-MT cell information. The nth IAB-MT cell information included in the IAB-MT cell list may include the NR cell identifier (ID) information of the corresponding cell and information on whether the following four types of multiplexing are supported.

[0282] -DU_RX / MT_RX Multiplexing: Notifies the IAB node whether simultaneous reception in DU and MT is supported. -DU_TX / MT_TX multiplexing: Notifies the IAB node whether simultaneous transmission in DU and MT is supported. -DU_TX / MT_RX multiplexing: Notifies the IAB node whether it can simultaneously perform transmission in DU and reception in MT. -DU_RX / MT_TX multiplexing: Notifies the IAB node whether it can simultaneously perform reception in DU and transmission in MT. [Table 9]

[0283] Figure 15 This is a flowchart illustrating a first exemplary embodiment of a method for resource management of IAB nodes in a communication system.

[0284] Figure 15 This illustration shows a first exemplary embodiment of a method for resource management of an IAB node, exemplified by determining whether to use IAB-DU resources on the basis of an IAB node. However, this is merely an example for ease of description, and the exemplary embodiments of this disclosure are not limited thereto. For instance, the configuration described in this disclosure for "whether to use IAB-DU resources" can also be similarly or identically applied to "whether to use IAB node resources," "whether to use IAB-MT resources," "whether to use DU / MT resources simultaneously," etc.

[0285] Reference Figure 15In accordance with the order in which the IAB-DU resources of an IAB node are determined for use, an IAB node can identify whether the corresponding IAB-DU resources are available, and in order to determine whether to use the IAB-DU resources, it can receive at least one of higher-layer IAB-MT resource configuration information and higher-layer IAB-DU resource configuration information from the superior IAB node (S1500). As an example, the higher-layer IAB-MT resource configuration information may include time slot configuration (i.e., downlink / uplink / variable (DUF)) information and symbol configuration information for the cell (or cell group) used for IAB-MT. As another example, the higher-layer IAB-DU resource configuration information may include time slot configuration (i.e., downlink / uplink / variable (DUF)) information and symbol configuration information for the cell (or cell group) used for IAB-DU.

[0286] Higher-level IAB-DU resource configuration information may include information on the type (i.e., hard, soft, or unavailable) of IAB-DU resources configured by the superior IAB node. Higher-level IAB-DU resource configuration information may include some or all of the cell-specific / semi-static downlink signals and channels (such as one or more SSBs, type 0-PDCCH CSS sets configured by SIB1 for PDCCH configuration, CSI-RS, etc.) configured in the cell (or cell group) assigned to the IAB-DU. Higher-level IAB-DU resource configuration information may include some or all of the cell-specific / semi-static uplink signals and channels (such as PRACH, SR, etc.) configured in the cell (or cell group) assigned to the IAB-DU.

[0287] In addition to the higher-level configurations described above, the IAB node can also receive at least one of the physical layer (L1 signaling) IAB-MT resource indicator and the physical layer IAB-DU resource indicator from the superior IAB node (S1510). As an example, the physical layer IAB-MT resource indicator may be DCI format 2_0, including a time slot format indicator for the cell (or set of cells) configured for the IAB-MT. As another example, the physical layer IAB-DU resource indicator may be DCI format 2_5, including the soft resource AI of the IAB-DU.

[0288] Finally, the IAB node can determine whether to use IAB-DU resources based on higher-layer signaling (S1500) and L1 signaling (S1510) (S1520).

[0289] Figure 16 This is a sequence diagram illustrating an exemplary embodiment of the UE capability reporting process in a communication system.

[0290] Reference Figure 16During the UE capability reporting process, when the terminal is in RRC connected mode (i.e., RRC_CONNECTED state), the base station can use higher-level parameters. UECapabilityEnquiry A UE capability report request signal is sent to the terminal (S1600). In this case, the network can refer only to the UE capability report after the access stratum (AS) security is activated, and can refrain from retransmitting or reporting the UE capability report to the core network (CN) before AS security is activated. Upon receiving the UE capability report request signal, the terminal can compile the UE capability information according to a specific procedure and send it via the UE capability information signal (e.g., UECapabilityInformation It reports this to the base station (S1610).

[0291] The specific process for compiling UE capability information signals may include generating a list of one or more frequency bands or combinations of one or more frequency bands (BCs) supported by the terminal. supportedBandCombinationList This involves at least one of the following: feature set (FS) information related to a feature set supported by the terminal, or feature set combination (FSC) information related to a combination of feature sets supported by the terminal. For example, when a base station requests a UE capability report from a terminal to obtain information about the frequency bands(s) or combinations(s) of frequency bands(s) supported by the terminal, the terminal may report which frequency band(s) it supports for each radio access technology (RAT). To this end, the base station may include a UE RAT capability report request list signal (e.g., [missing information]) in a higher-level message. ue- CapabilityRAT-RequestList UE RAT capability report request signal in ) (e.g., UE-CapabilityRAT- Request The RAT-type in the UE capability report is set to one of "nr", "eutra-nr", "eutra", and "eutra-fdd". This means that the base station can request a UE capability report from the terminal for one or more RATs or RAT combinations, and in this case, the terminal can respond to each request for a list of supported frequency bands for multiple RATs or RAT combinations. For example, if the RAT-type is set to "nr", the terminal can include a list of frequency bands or frequency band combinations for which NR-DC can be applied in the UE capability report. As another example, if the RAT-type is set to "eutra-nr", the terminal can include a list of frequency bands or frequency band combinations applicable to multiple RAT DCs (MR-DCs) (such as EN-DC, NGEN-DC, NE-DC, etc.) in the UE capability report. Additionally, when the base station requests a UE capability report, it can use higher-level parameters... frequencyBandListFilter Provide the terminal with a list of frequency bands for the terminal to determine whether support is provided. This applies to parameters included in higher layers. frequencyBandListFilterIn the frequency bands, the terminal can determine the candidate frequency band combination by considering "the pre-defined RAT type supported for each frequency band" and "information about the RAT type requested by the base station", and can include the candidate frequency band combination in the UE capability report.

[0292] In 5G communication systems, base stations can provide information related to the transmission power between each downlink channel and signal, aiming to improve the accuracy of channel or signal reception and quality measurement at the terminal while reducing implementation complexity. This transmission power information can explicitly indicate the transmission power value of a particular signal or channel, or implicitly represent the ratio between the transmission powers of two different channels and signals.

[0293] Reference Figures 9 to 16 Any of the UE capability reports described in the references can be executed between the terminal and the base station. Additionally, similar to the reference... Figure 13 The relationship between the IAB node or IAB-MT and its superior node, as described, corresponds to the relationship between a terminal and a base station. The IAB node or IAB-MT can refer to... Figures 9 to 16 Any of the described UE capability reports are sent to the superior node. Furthermore, the relationship between the IAB node or IAB-DU and the subordinate node can correspond to the relationship between the base station and the terminal. The IAB node or IAB-DU can receive references from the subordinate node. Figures 9 to 16 Any of the described UE capability reports. IAB nodes can perform communication with higher or lower nodes based on UE capability reports sent and received by higher or lower nodes.

[0294] In an exemplary embodiment of the communication system, the IAB node can be designed based on a time division multiplexing (TDM) scheme between the IAB-DU and IAB-MT. Here, the time slot format of the IAB-MT cell used for communication between the IAB node and the upper-level node or for uplink communication can be statically configured or dynamically indicated. The time slot format of the IAB-DU cell used for communication between the IAB node and the lower-level node or for downlink communication can be statically configured or dynamically indicated. The downlink, uplink, or variable symbol type of the IAB-DU cell can be configured as any of hard (H)-type, soft (S)-type, and unavailable (NA)-type. Whether the S-type symbol of the IAB-DU cell is used can be dynamically indicated.

[0295] On the other hand, in exemplary embodiments of the communication system, IAB nodes may be designed to support multiplexing schemes that allow simultaneous transmissions rather than TDM schemes. Multiplexing schemes that allow simultaneous transmissions may refer to frequency division multiplexing (FDM) or space division multiplexing (SDM) schemes. In other words, IAB nodes may be designed to support simultaneous operation (SO) of IAB-MT and IAB-DU. To maximize communication capacity or reduce implementation complexity in IAB nodes designed to support simultaneous operation of IAB-MT and IAB-DU, different configuration and indication schemes may be required compared to those used in IAB nodes designed to support the aforementioned TDM schemes.

[0296] In an exemplary embodiment of an IAB node designed to support the simultaneous operation of IAB-MT and IAB-DU, IAB-MT and IAB-DU may operate based on any of the following simultaneous operation schemes A through F.

[0297] - Case A (DU Tx / MT Tx): At the same time point (symbol), IAB-DU performs downlink transmission and IAB-MT performs uplink transmission.

[0298] - Case B (DU Rx / MT Rx): At the same time point (symbol), IAB-DU performs uplink reception and IAB-MT performs downlink reception.

[0299] - Case C (DU Rx / MT Tx): At the same time point (symbol), IAB-DU performs uplink reception and IAB-MT performs uplink transmission.

[0300] - Case D (DU Tx / MT Rx): At the same time point (symbol), IAB-DU performs downlink transmission and IAB-MT performs downlink reception.

[0301] - Case E (DU / MT FDM required): For simultaneous operation of IAB-DU and IAB-MT, the radio resources of IAB-DU and IAB-MT should be frequency division multiplexed (FDM).

[0302] - Case F (DU / MT SDM required): For simultaneous operation of IAB-DU and IAB-MT, the radio resources of IAB-DU and IAB-MT should be spatially multiplexed (SDM).

[0303] IAB-DU and IAB-MT operating simultaneously based on any one of conditions A through F can be included in a single IAB node, or can be considered to constitute a single IAB node. In other words, IAB-DU and IAB-MT operating simultaneously based on any one of conditions A through F can be considered to be co-located. Here, condition E can be applied when the interference control capability of IAB-DU and / or IAB-MT is relatively limited, and condition F can be applied when the interference control capability of IAB-DU and / or IAB-MT is relatively superior.

[0304] In an exemplary embodiment of the communication system, the IAB node (or IAB-DU and IAB-MT) can support at least one of the four simultaneous operation schemes from A to D. The IAB node (or IAB-DU and IAB-MT) can report information about one or more simultaneous operation schemes supported by the IAB node to its parent node. Optionally, the IAB node (or IAB-DU and IAB-MT) can report information about one or more combinations of multiple simultaneous operation schemes supported by the IAB node to its parent node. Here, "parent node of the IAB node" can correspond to a parent IAB node, an IAB donor node, a parent node, a central unit (CU), a core network, etc. Therefore, the reporting can be performed in the same or similar manner as shown in Table 9.

[0305] In another exemplary embodiment of the communication system, the IAB node (or IAB-DU and IAB-MT) may support at least one or more of the six simultaneous operation schemes from conditions A to F. The IAB node (or IAB-DU and IAB-MT) may report information about one or more simultaneous operation schemes supported by the IAB node to the superior node. Optionally, the IAB node (or IAB-DU and IAB-MT) may report information about one or more combinations of multiple simultaneous operation schemes supported by the IAB node to the superior node. Therefore, reporting may be performed in the same or similar manner as shown in Table 10.

[0306] [Table 10]

[0307] In addition to the elements constituting the report according to Table 9, the report according to Table 10 may also include elements corresponding to situations E and F above.

[0308] In the following text, “case A,” “case B,” “case C,” “case D,” “case E,” and “case F” in this disclosure may refer to cases A through F, respectively. In this disclosure, the term “HSNA type” may refer to at least one of the H-type, S-type, or NA-type configured for a time slot or symbol constituting a time resource, and the term “HSNA time slot configuration” may refer to a message or signal used to configure an HSNA type for each time slot (or symbol).

[0309] [First exemplary embodiment of the communication system] In a first exemplary embodiment of the communication system, an extended configuration for IAB node resource management operations for simultaneous DU / MT operations is proposed, based on HSNA time slot configuration and L1 signaling (e.g., DCI formats 2-5, etc.) for one or more S symbols.

[0310] In a first exemplary embodiment of the communication system, as shown in Table 7, the HSNA timeslot configuration is extended from the same or similar HSNA timeslot configurations. For example, in a first exemplary embodiment of the communication system, timeslot configurations (or lists of timeslot configurations) for (semi-)static configuration and dynamic indication for simultaneous DU / MT operation can be added to the HSNA timeslot configurations shown in Table 7. This may mean that, in addition to existing HSNA timeslot configurations, the “HSNA timeslot configuration for simultaneous operation” or the “list of HSNA timeslot configurations for simultaneous operation” can be configured independently. Hereinafter, in the first exemplary embodiment of the communication system, “HSNA configuration for simultaneous operation” may refer to the aforementioned “HSNA timeslot configuration for simultaneous operation” or “list of HSNA timeslot configurations for simultaneous operation”.

[0311] Depending on the HSNA configuration used for simultaneous operation, various applications can be possible based on the high degree of flexibility in the configuration. For example, in an exemplary embodiment of the communication system, simultaneous operation may only be applied to downlink H-type symbols. A "static configuration of the simultaneous DU / MT operation scheme" for statically configuring the simultaneous operation scheme for DU and MT may include at least one type among H-type, S-type, and NA-type. Here, H-type may mean that operation according to one of conditions A to D (or conditions A to F) can be applied, regardless of L1 signaling. NA-type may mean that simultaneous DU / MT operation is impossible, regardless of signaling. S-type may mean that whether simultaneous DU / MT operation is performed can be indicated by L1 signaling. Table 11 shows a first exemplary embodiment of the static configuration of the simultaneous operation scheme for DU / MT.

[0312] [Table 11]

[0313] Referring to Table 11, the parent node of an IAB node (or the IAB-DU and / or IAB-MT constituting the IAB node) can configure HSNA values ​​to the IAB node. Specifically, for each time slot (or symbol, subframe, frame, etc.) within a predetermined time slot set (or symbol set, subframe set, frame set, etc.), the parent node can configure one or more HSNA values ​​(i.e., simultaneous operation HSNA values) to the IAB node for the simultaneous operation scheme shown in Table 11. Here, the parent node can refer to or consider information about the simultaneous operation capabilities of the DU / MT reported by the IAB node based on the signaling shown in Table 9. In other words, simultaneous operation HSNA values ​​that violate the simultaneous operation capabilities reported by the IAB node will not be configured for each IAB node. Optionally, when a simultaneous operation HSNA value that violates the simultaneous operation capabilities reported by the IAB node is configured, the IAB node can ignore the configured simultaneous operation HSNA value. In Table 11, the rows corresponding to each case do not necessarily have to be independent, and the combination of simultaneous operation schemes may change depending on the situation.

[0314] Table 12 shows a second exemplary embodiment of the static configuration of the simultaneous operation scheme of DU / MT.

[0315] [Table 12]

[0316] Referring to Table 12, the parent node of the IAB node (or the IAB-DU and / or IAB-MT constituting the IAB node) can configure the HSNA value for each time slot to the IAB node based on the information in the "HSNA Simultaneous Operation" row of Table 12. Here, the parent node can refer to or consider the information reported from the IAB node regarding the simultaneous operation capability of the DU / MT based on the signaling shown in Table 9. Here, the meaning of the "HSNA Simultaneous Operation" row can be committed between the IAB node and the parent node through capability reporting performed in the same or different manner as in Table 9.

[0317] Table 13 shows a third exemplary embodiment of the static configuration of the DU / MT simultaneous operation scheme.

[0318] [Table 13]

[0319] Referring to Table 13, the static configuration of the DU / MT simultaneous operation scheme can be configured such that the "HSNA simultaneous operation" row described in Table 12 is included in the "HSNA slot configuration item".

[0320] Table 14 shows a fourth exemplary embodiment of the static configuration of the DU / MT simultaneous operation scheme.

[0321] [Table 14]

[0322] Referring to Table 14, the static configuration of the DU / MT simultaneous operation scheme can be configured such that the rows corresponding to the various cases described in Table 11 are included in the "HSNA slot configuration items".

[0323] The HSNA time slot configuration can be extended in the same or similar manner as the methods described in any of the reference tables 11 to 14. In this case, the IAB node (or the IAB-DU and / or IAB-MT constituting the IAB node) can ultimately determine whether to perform simultaneous transmission in the simultaneous operation S-type resources based on predetermined signaling (e.g., L1 signaling, etc.). Here, the signaling can correspond to the DCI format 2_5 received by the IAB node or IAB-MT from the superior node. Here, the mapping between the AI ​​index field values ​​of DCI format 2_5 and the availability of S-type symbols within the time slot can be extended from those shown in Table 8 to those shown in Table 15. For this purpose, in an exemplary embodiment of the communication system, the payload of each AI index field of DCI format 2_5 can be extended from 3 bits to 4 bits.

[0324] [Table 15]

[0325]

[0326] Referring to Table 15, in an exemplary embodiment of the communication system, the upper-level IAB node may indicate information according to values ​​0 to 7 of Table 15 (i.e., information regarding whether the IAB-DU can use D / U / F soft symbols based on DU / MT TDM operation) and information according to values ​​8 to 14 of Table 15 (i.e., information regarding whether SO soft symbols can be used based on DU / MT FDM or SDM operation). Here, the information according to values ​​0 to 7 of Table 15 may be the same as or similar to the information according to Table 8. The IAB node may need a criterion for determining whether to follow the mapping in Table 8 or the mapping in Table 15. For example, when the IAB node receives a configuration according to one of Tables 11 to 14, it may be considered that the IAB node is implicitly instructed to follow the mapping in Table 15. Alternatively, a separate higher-level parameter explicitly indicating whether the IAB node follows the mapping in Table 8 or the mapping in Table 15 may be introduced.

[0327] In exemplary embodiments of the communication system, the values ​​8 to 14 in Table 15 are merely examples of a scheme for conveniently describing the availability indication of soft symbols in exemplary embodiments of the communication system, and the exemplary embodiments of this disclosure are not limited thereto. For example, in another exemplary embodiment of the communication system, some omissions, additions, or changes may be made to the values ​​8 to 14 in Table 15.

[0328] In an exemplary embodiment of the communication system, the HSNA time slot configuration scheme described with reference to Tables 11 to 14 and the AI ​​mapping extension scheme described with reference to Table 15 do not need to be mutually exclusive and can be applied simultaneously as appropriate. In an exemplary embodiment of the communication system, based on the simultaneous operation capability report of the IAB node (or the IAB-DU and / or IAB-MT constituting the IAB node) described with reference to Table 8, the exemplary embodiments described with reference to Tables 11 to 15 can be applied, in a limited manner, to cells capable of performing simultaneous operation.

[0329] Figure 17 This is a flowchart illustrating a second exemplary embodiment of a resource management method for an IAB node in a communication system.

[0330] Figure 17 This illustration shows a second exemplary embodiment of a resource management method for an IAB node, using the operation of an IAB node determining whether IAB-DU resources are used as an example. However, this is merely an example for ease of description, and the exemplary embodiments of this disclosure are not limited thereto. For example, the configuration described in this disclosure for "whether IAB-DU resources are used" can be applied in the same or similar way to "whether IAB-node resources are used," "whether IAB-MT resources are used," "whether resources are used for simultaneous DU / MT operation," etc.

[0331] Reference Figure 17 To identify whether IAB-DU resources are available and determine whether to use them, an IAB node can receive at least one of the following: first higher-level IAB-MT resource configuration information and first higher-level IAB-DU resource configuration information from its parent node (S1710). Here, "parent node of the IAB node" can correspond to a parent IAB node, an IAB donor node, a parent node, a central unit (CU), or a core network.

[0332] In an exemplary embodiment of the communication system, the first higher-layer IAB-MT resource configuration information may include the configuration of D / U / F time slots and symbols for a cell (or set of cells) configured to the IAB-MT. The first higher-layer IAB-MT resource configuration information may include information regarding cell-specific / semi-static downlink signals and channels (such as SSBs, etc.) configured in the cell (or set of cells) configured to the IAB-MT. pdcchConfigSIB1 Information configured for the PDCCH, CSI-RS, etc. of the type 0-PDCCH CSS set. First higher-layer IAB-MT resource configuration information may include all or some of the information about cell-specific / semi-static uplink signals and channels (e.g., PRACH, SR, etc.) configured in the cell (or set of cells) configured for the IAB-MT.

[0333] In another exemplary embodiment of the communication system, the first higher-level IAB-DU resource configuration information may include the configuration of D / U / F time slots and symbols for the cell (or set of cells) configured to the IAB-DU. The first higher-level IAB-DU resource configuration information may include HSNA type information of the IAB-DU resources configured by the superior IAB node. The first higher-level IAB-DU resource configuration information may include information about cell-specific / semi-static downlink signals and channels (such as SSBs, etc.) configured in the cell (or set of cells) configured to the IAB-DU. pdcchConfigSIB1 Information configured for the type 0-PDCCH CSS set (such as PDCCH, CSI-RS, etc.). First higher-layer IAB-DU resource configuration information may include all or some of the cell-specific / semi-static uplink signals and channels (such as PRACH, SR, etc.) configured in the cell (or set of cells) to which the IAB-DU is configured.

[0334] After step S1710, the IAB node can identify whether simultaneous DU / MT operations are feasible in a specific time / frequency resource. The IAB node can receive at least one of the second higher-level IAB-MT resource configuration information and the second higher-level IAB-DU resource configuration information from the parent node in order to determine whether to apply the simultaneous operation (S1720).

[0335] In an exemplary embodiment of the communication system, the second higher-layer IAB-MT resource configuration information may be the same as or similar to the configuration information in Tables 11 to 13. The second higher-layer IAB-MT resource configuration information may include configurations regarding whether a simultaneous operation scheme is applied to a cell, cell group (MCG or SCG), bandwidth portion (BWP), or a specific frequency resource configured for an independent configuration assigned to the IAB-MT, or configurations for simultaneous transmit / receive resource types. For this purpose, the second higher-layer IAB-MT resource configuration information may include all or some of the cell-specific / semi-static downlink signals and channels (such as SSB, PDCCH configured by pdcchConfigSIB1 for the Type 0-PDCCH CSS set, CSI-RS, etc.) configured in the cell (or cell set) assigned to the IAB-MT. The second higher-layer IAB-MT resource configuration information may include all or some of the cell-specific / semi-static uplink signals and channels (e.g., PRACH, SR, etc.) configured in the cell (or cell set) assigned to the IAB-MT.

[0336] In another exemplary embodiment of the communication system, the second higher-level IAB-DU resource configuration information may include information on the type (e.g., H, S, or NA) of the DU / MT simultaneous operation resources configured from the upper-level node. For example, the second higher-level IAB-DU resource configuration information may be the same as or similar to the configuration information in Tables 11 to 13. The second higher-level IAB-DU resource configuration information may include configuration regarding whether to apply the simultaneous operation scheme to specific frequency resources of a cell, cell group (MCG or SCG), BWP, or an independent configuration assigned to the IAB-DU, or configuration for the type of simultaneous transmit / receive resource. The second higher-level IAB-DU resource configuration information may include information on cell-specific / semi-static downlink signals and channels (such as SSB, etc.) configured in the cell (or cell set) assigned to the IAB-DU. pdcchConfigSIB1 Information configured for the PDCCH, CSI-RS, etc. of the type 0-PDCCH CSS set. Second higher-layer IAB-DU resource configuration information may include information about all or some of the cell-specific / semi-static uplink signals and channels (e.g., PRACH, SR, etc.) configured in the cell (or set of cells) configured to the IAB-DU.

[0337] Following step S1720, in addition to the higher-level configuration described above, the IAB node may also receive at least one of a first physical layer (e.g., L1 signaling) IAB-MT resource indicator and a first physical layer IAB-DU resource indicator from its parent node (S1730). As an example, the first physical layer IAB-MT resource indicator may be DCI format 2_0, including a slot format indicator for configuring the cell (or set of cells) to the IAB-MT. As another example, the first physical layer IAB-DU resource indicator may be DCI format 2_5, including the soft resource AI of the IAB-DU.

[0338] Following step S1730, the IAB node may receive at least one of a second physical layer (e.g., L1 signaling) IAB-MT resource indicator and a second physical layer IAB-DU resource indicator from its parent node (S1740). As an example, the second physical layer IAB-MT resource indicator may be a DCI format 2_X defined as including a simultaneous operation AI for a cell (or set of cells) configured for the IAB-MT. This may mean that the IAB-MT can determine whether to perform simultaneous DU / MT operation according to the new soft symbol availability mapping rules shown in Table 15. Similarly, the second physical layer IAB-DU resource indicator may be a DCI format 2_X defined as including a DU / MT simultaneous operation soft resource AI for the IAB-DU (or, a specific frequency resource (such as a cell, cell group, BWP, etc.) configured to the IAB-DU). This may mean that the IAB-DU can determine whether to perform simultaneous DU / MT operation according to the new soft symbol availability mapping rules shown in Table 15.

[0339] The IAB node may determine whether to use IAB-DU resources (1750) based on the higher-layer signaling information in steps S1710 and S1720 and / or the physical layer (L1) signaling information in steps S1730 and S1740.

[0340] [Second exemplary embodiment of the communication system] In a second exemplary embodiment of the communication system, configurations related to the extension of HSNA time slot configuration and L1 signaling for S-type symbols (e.g., DCI formats 2-5, etc.) are proposed, as well as IAB node resource management operations for simultaneous DU / MT operations based on additional configurations that allow simultaneous operation for each frequency resource.

[0341] In a second exemplary embodiment of the communication system, simultaneous DU / MT operation is permitted based on the HSNA time slot configuration described with reference to Table 7, etc. For this purpose, a semi-static configuration or dynamically indicated cell configuration (or cell configuration list) for simultaneous DU / MT operation can be configured separately. In other words, in addition to the HSNA time slot configuration, the "HSNA cell configuration for simultaneous operation" or the "HSNA cell configuration list for simultaneous operation" can be configured independently. The "cell configuration" or "cell configuration list" is merely an example for ease of description, and the exemplary embodiments of this disclosure are not limited thereto. In an exemplary embodiment of the communication system, the "cell" in the HSNA cell configuration for simultaneous operation or the HSNA cell configuration list for simultaneous operation can be replaced by other frequency resources (such as "cell group," "BWP," other "configured RBs," etc.). Hereinafter, in the second exemplary embodiment of the communication system, "HSNA configuration for simultaneous operation" may refer to the aforementioned "HSNA cell configuration for simultaneous operation" or "HSNA cell configuration list for simultaneous operation."

[0342] Depending on the HSNA configuration used for simultaneous operation, various applications can be possible due to the high degree of flexibility in the configuration. For example, in an exemplary embodiment of the communication system, the simultaneous operation scheme may be applied only to downlink H-type symbols. The "static configuration of the DU / MT simultaneous operation scheme" used for statically configuring the DU / MT simultaneous operation scheme may include at least one of H-type, S-type, and NA-type.

[0343] Table 16 shows a fifth exemplary embodiment of the static configuration of the DU / MT simultaneous operation scheme.

[0344] [Table 16]

[0345]

[0346] Here, a specific relationship can be defined between the HSNA configuration according to Table 7, etc., and the HSNA configuration for simultaneous operation according to Table 16. For example, only when according to... Figure 7 The higher-level HSNA configuration and its L1 signaling (i.e., the first L1 signaling) and according to Figure 16 An IAB node can only be committed to simultaneous operation when both the higher-level HSNA configuration and its L1 signaling (i.e., the second L1 signaling) indicate that the corresponding resources are available.

[0347] Table 17 shows a sixth exemplary embodiment of the static configuration of the DU / MT simultaneous operation scheme.

[0348] [Table 17]

[0349] Referring to Table 17, the parent node of the IAB node (or the IAB-DU and / or IAB-MT constituting the IAB node) can configure the HSNA value for each time slot to the IAB node based on the information in the "HSNA Simultaneous Operation" row of Table 17. Here, the parent node can refer to or consider the information reported from the IAB node regarding the simultaneous operation capability of the DU / MT based on the signaling shown in Table 9. Here, the meaning of the "HSNA Simultaneous Operation" row can be committed between the IAB node and the parent node through capability reporting performed in the same or different manner as in Table 9.

[0350] The operation according to the second exemplary embodiment of the communication system can be compared with reference to Figure 17 The operations described are the same or similar.

[0351] [Third exemplary embodiment of the communication system] In a third exemplary embodiment of the communication system, in addition to HSNA time slot configuration and / or L1 signaling for S-type symbols (e.g., DCI formats 2-5, etc.), a configuration related to IAB node resource management operations for simultaneous DU / MT operations based on a configuration regarding whether simultaneous operation for each frequency resource is allowed is proposed.

[0352] In a third exemplary embodiment of the communication system, in addition to the HSNA time slot configuration described with reference to Table 7, simultaneous DU / MT operation can also be allowed based on a separately defined cell configuration (or cell configuration list). Specifically, the semi-static configuration or dynamically indicated cell configuration (or cell configuration list) for simultaneous DU / MT operation can be configured separately. In other words, the "HSNA cell configuration for simultaneous operation" or the "HSNA cell configuration list for simultaneous operation" can be configured independently, in addition to the HSNA time slot configuration. The "cell configuration" or "cell configuration list" is merely an example for ease of description, and the exemplary embodiments of this disclosure are not limited thereto. In the exemplary embodiments of the communication system, the "cell" in the HSNA cell configuration for simultaneous operation or the HSNA cell configuration list for simultaneous operation can be replaced by other frequency resources (such as "cell group", "BWP", other "configured RB", etc.). In the following, in the third exemplary embodiment of the communication system, "HSNA configuration for simultaneous operation" may refer to the aforementioned "HSNA cell configuration for simultaneous operation" or "HSNA cell configuration list for simultaneous operation".

[0353] Depending on the HSNA configuration used for simultaneous operation, various applications can be possible based on the high degree of flexibility in the configuration. For example, in an exemplary embodiment of the communication system, the simultaneous operation scheme may be applied only to downlink H-type symbols. The "static configuration of the DU / MT simultaneous operation scheme" used for statically configuring the DU / MT simultaneous operation scheme may include at least one of H-type, S-type, and NA-type.

[0354] Additionally, to indicate the HSNA configuration for simultaneous DU / MT operation for each independent frequency resource and whether simultaneous operation soft symbols are used accordingly, a new DCI format (e.g., DCI format 2_Y) or a new RNTI (e.g., FreqAI-RNTI) can be defined. IAB nodes can use the newly defined DCI format or RNTI to identify whether a relevant DCI indicates the availability of simultaneous operation soft symbols based on Table 8, etc., or indicates the availability of simultaneous operation soft symbols based on a third exemplary embodiment of the communication system. As an example, an IAB node can determine whether a relevant DCI indicates AI for soft symbols in the time domain or AI for soft symbols in the frequency domain based on which RNTI is scrambled by the CRC of the DCI. For example, if the CRC is scrambled by AI-RNTI, it can be determined that the relevant DCI indicates AI for soft symbols in the time domain, and if the CRC is scrambled by FreqAI-RNTI, it can indicate that the relevant DCI indicates AI for soft symbols in the frequency domain.

[0355] Table 18 shows a seventh exemplary embodiment of the static configuration of the DU / MT simultaneous operation scheme.

[0356] [Table 18]

[0357] Referring to Table 18, an IAB node (or IAB DU or IAB MT) can receive HSNA configurations for one or more of the simultaneous operation schemes (i.e., cases A through D), which are defined for the configured frequency resource elements (e.g., cells in the examples of Table 18). In this case, the parent IAB node or core network configuring this may need to refer to (comply with) the simultaneous operation capability reports of the IAB node's DU / MT as shown in Table 9. This can be understood as the IAB node not expecting simultaneous operation HSNA configuration values ​​to violate the simultaneous operation capabilities reported by the IAB node. That is, the IAB node can ignore simultaneous operation HSNA configuration values ​​that violate the simultaneous operation capability reports. The IAB node can identify the time resources available for IAB-DU and the frequency resources for simultaneous DU / MT operation by referring to the time domain (e.g., time slot) HSNA configurations in Table 7 and the frequency domain (e.g., cell) HSNA configurations in Table 18.

[0358] Table 19 shows an eighth exemplary embodiment of the static configuration of the DU / MT simultaneous operation scheme.

[0359] [Table 19]

[0360] Referring to Table 19, the static configuration of the DU / MT simultaneous operation scheme can be configured such that the row corresponding to the situation described in Table 11 is included in the "HSNA slot configuration item".

[0361] The operation according to the third exemplary embodiment of the communication system can be compared with reference to Figure 17 The operations described are the same or similar.

[0362] [Fourth exemplary embodiment of the communication system] In a fourth exemplary embodiment of the communication system, a configuration related to the granularity of simultaneous operation is proposed.

[0363] In a fourth exemplary embodiment of the communication system, simultaneous DU / MT operation can be configured and guided for each of the IAB-DU and IAB-MT cells. Optionally, a configuration for simultaneous DU / MT operation (or a configuration regarding whether simultaneous DU / MT operation is possible) can be configured for each cell group (e.g., MCG, SCG, etc.) including IAB-DU and / or IAB-MT. Optionally, a configuration for simultaneous DU / MT operation (or a configuration regarding whether simultaneous DU / MT operation is possible) can be configured for each BWP of IAB-DU and / or IAB-MT. Optionally, a configuration for simultaneous DU / MT operation (or a configuration regarding whether simultaneous DU / MT operation is possible) can be configured for each RB set / group including one or more individually configured or committed RBs.

[0364] Furthermore, IAB-DU and IAB-MT can be configured to have different implementation complexities, use different transmission powers, or have different frequency resource processing capabilities. For example, IAB-DU and IAB-MT can have different maximum numbers of CA / DC cells. Considering the implementation differences between IAB-DU and IAB-MT, the configurations related to simultaneous DU / MT operation can have different granularities for IAB-DU and IAB-MT. The parent node of the IAB node can send signaling related to the simultaneous operation configurations with different granularities for IAB-DU and IAB-MT to the IAB node's IAB-DU and / or IAB-MT.

[0365] In an exemplary embodiment of the communication system, the parent node of the IAB node may configure simultaneous DU / MT operation for each cell for the IAB-DU constituting the IAB node, and configure simultaneous DU / MT operation for each BWP for the IAB-MT constituting the IAB node. For example, the interference handling capability of the IAB-MT may be relatively limited compared to the interference handling capability of the IAB-DU, therefore the simultaneous DU / MT operation for the IAB-MT can be configured in more detail than the simultaneous DU / MT operation for the IAB-DU. However, this is merely an example for ease of description, and the exemplary embodiments of this disclosure are not limited thereto. For example, in another exemplary embodiment of the communication system, the different units applied to the IAB-DU and IAB-MT respectively can be combined in many more different ways.

[0366] [Fifth Exemplary Embodiment of the Communication System] In a fifth exemplary embodiment of the communication system, a configuration related to cell-specific signals and channels is proposed.

[0367] In a fifth exemplary embodiment of the communication system, the IAB-DU can transmit and receive signals, assuming that the symbol type that does not affect the signal transmission / reception direction of the IAB-MT, or the symbol type of the transmitted / received cell-specific / semi-static signals or channels, is type H. Here, the cell-specific / semi-static signals or channels may follow the description above, such as SSB, PDCCH for the type 0-PDCCH CSS set configured by pdcchConfigSIB1, CSI-RS, PRACH, SR, etc.

[0368] Here, the aforementioned IAB-DU and / or IAB-MT operations can be extended to IAB nodes capable of performing simultaneous DU / MT operations. For example, for an IAB node that has already reported its execution capability based on one or more of the above scenarios A to D (or A to F), the corresponding IAB node's IAB-MT can be configured to transmit and receive signals even when transmitting and receiving cell-specific / semi-static signals or channel symbols during IAB-DU transmission and reception.

[0369] [Sixth Exemplary Embodiment of the Communication System] In the sixth exemplary embodiment of the communication system, additional configurations for implementing the first to fifth exemplary embodiments of the communication system are proposed.

[0370] In an exemplary embodiment of the communication system, to limit the PDCCH reception complexity of the terminal, the maximum number of blind decoding (BD) and control channel elements (CCE) that the terminal needs to decode within a specific time period can be configured or defined. For example, when the number of configured CA or DC cells is 4 or less, the terminal can assume the total number of BD / CCEs by multiplying a predetermined maximum number of BD / CCEs for each cell by the number of configured cells. However, when the number of configured CA or DC cells is greater than 5, PDCCH reception can be performed by dividing the maximum number of BD / CCEs that the terminal can handle (as reported by the terminal) by the number of configured cells. This has the effect of preventing the PDCCH detection complexity from increasing beyond a predetermined value when performing CA and / or DC using a large number of cells.

[0371] Furthermore, according to the first to fifth exemplary embodiments of the communication system, it can be assumed that simultaneous DU / MT operation is not allowed in some cells configured for IAB-MT, and simultaneous DU / MT operation is allowed in the remaining cells. In this case, since the control channel capacity required for the cells where simultaneous DU / MT operation is allowed may be larger, it is possible to commit to the number of BD / CCEs distributed by assuming that simultaneous DU / MT operation is not allowed in one cell and simultaneous DU / MT operation is allowed in two or more cells (e.g., 1.5 or 2 cells).

[0372] [Seventh Exemplary Embodiment of the Communication System] In a seventh exemplary embodiment of the communication system, a configuration related to the HSNA time slot configuration and the extension of DCI formats 2-5 for implementing one or more of the first to third exemplary embodiments of the above-described communication system is proposed.

[0373] In the first to third exemplary embodiments, methods have been provided for configuring IAB node resources for simultaneous DU / MT operations by extending the traditional type configuration for time resources (HSNA slot configuration) and L1 signaling for soft symbols (i.e., DCI formats 2-5). The following details may be referenced when applying the above methods.

[0374] As an example of extending the conventional type configuration for time resources (HSNA slot configuration, see Table 7), a semi-static configuration and a dynamically indicated slot configuration (or slot configuration list) for simultaneous DU / MT operation can be added. This may mean that, in addition to the HSNA slot configuration, a "list of HSNA slot configurations for simultaneous operation" or "HSNA slot configuration for simultaneous operation" can be independently configured for simultaneous DU / MT operation. In this case, the terms "list of HSNA slot configurations for simultaneous operation" or "HSNA slot configuration for simultaneous operation" are merely examples for ease of description, and the exemplary embodiments of this disclosure are not limited thereto. For example, various schemes can be applied, such as a conventional HSNA slot configuration being configured as a first configuration, and a second or more HSNA slot configurations for simultaneous operation being additionally configured for a cell (or CC or carrier). Each of the aforementioned second or more HSNA slot configurations may include configuration information of the configured frequency resources (BWP, configured RBs, RB groups, etc.) applied within a cell (or CC or carrier). In the following description, for ease of description, this may be referred to as "HSNA configuration for simultaneous operation". The HSNA configuration for simultaneous operation, independent of the regular HSNA configuration, can be implemented with a high degree of flexibility in configuration depending on the situation (e.g., simultaneous operation is only applied to downlink H-type symbols, etc.). Such an exemplary embodiment (i.e., applying simultaneous operation only to downlink H-type symbols) can be an operation under the assumption that the IAB node can easily manage interference caused by simultaneous operation in downlink H-type symbols of the IAB-DU, but not easily in downlink S-type or NA-type resources. Details and various operations according to this will be described below. The static configuration of simultaneous DU / MT operation may include at least one of the following: 1) H-type means that at least one operation in cases A to D can be applied, regardless of L1 signaling; 2) NA-type means that simultaneous DU / MT operation is not possible, regardless of L1 signaling; or 3) Soft-type means that simultaneous DU / MT operation is indicated by L1 signaling.

[0375] [Eighth Exemplary Embodiment of the Communication System] In the eighth exemplary embodiment of the communication system, a configuration related to the resource type configuration method and / or signaling method for implementing one or more of the first to seventh exemplary embodiments of the communication system described above is proposed.

[0376] In the eighth exemplary embodiment, other examples are provided for applying the above-described type of configuration (HSNA slot configuration and / or HSNA slot configuration for simultaneous operation) to time-frequency resources and L1 signaling for soft symbols (i.e., DCI format 2_5).

[0377] As described above, an IAB node can be configured with 1) a time resource type configuration (HSNA slot configuration, HSNA configuration #1) for a certain DU cell, and 2) a time-frequency resource type configuration (HSNA cell configuration for simultaneous operation, HSNA configuration #2) for a specific set of RBs within a certain DU cell.

[0378] If an IAB node (i.e., IAB DU) is configured with only one of HSNA configuration #1 and HSNA configuration #2 for a specific OFDM symbol, then the IAB node (i.e., IAB DU) can apply the received HSNA configuration to the corresponding OFDM symbol.

[0379] If an IAB node (i.e., an IAB DU) is configured with both HSNA configuration #1 and HSNA configuration #2 for a specific OFDM symbol, the IAB node (i.e., the IAB DU) can select one HSNA configuration according to a specific rule and apply the selected HSNA configuration to the OFDM symbol. This specific rule can be explicitly configured through independent higher-level parameters, or defined implicitly by whether one or more parameters configured for simultaneous DU / MT operation are configured.

[0380] Here, "implicitly determined rules" may consider at least one of the following: 1) whether the IAB node performs a (capability) report on whether it supports simultaneous DU / MT transmit / receive operations (for each time / frequency resource), 2) whether the DU and MT DU directions conflict, 3) whether the IAB-DU or MT transmit timing adjustment (or specific timing adjustment value / timing mode) is applied, or 4) semi-static / cell-specific signal configuration (or whether HSNA resources conflict accordingly).

[0381] The second HSNA configuration (i.e., HSNA configuration #2) can have different values ​​for downlink (D), variable (F), and uplink (U) symbols within a time slot. For example, a D symbol within a time slot can be assigned HSNA configuration value #2-1, an F symbol within a time slot can be assigned HSNA configuration value #2-2, and a U symbol within a time slot can be assigned HSNA configuration value #2-3. HSNA configuration values ​​#2-1, #2-2, and #2-3 can include HSNA configurations for the same frequency resources (e.g., RB sets, RB groups (RBGs), precoded resource block groups (PRBs), BWPs, or sets thereof) or HSNA configurations for different or partially shared frequency resources (within a DU cell or a pair of {DU cells, MTCC}).

[0382] The second HSNA configuration (i.e., HSNA configuration #2) provides an HSNA configuration for time-frequency resources assuming a specific SCS. The specific SCS can be determined by independent higher-layer parameters, or based on the SCS of the cell (i.e., DU cell, MT CC, a pair of {DU cells, MT CC}) or BWP that includes the corresponding HSNA configuration #2. If HSNA configuration #2 is applied to time-frequency resources of an SCS different from the specific SCS, the IAB nodes (IAB DU, IAB MT) can appropriately adjust the time-frequency resources for which HSNA configuration #2 is applied based on the relationships between the aforementioned parameter sets.

[0383] If the DFU symbol direction determined by the DFU configuration within the second HSNA configuration (HSNA configuration #2) according to SCS #1 (i.e., symbol direction #1) differs from the DFU configuration determined by a different SCS #2 (e.g., ... tdd-UL-DL-ConfigurationCommon , tdd-UL-DL-ConfigurationDedicated , tdd-UL-DL-ConfigurationDedicated-IAB-MT If a conflict exists between the DFU symbol direction (i.e., symbol direction #2) determined by a directive (e.g., DCI format 2_0) or an indication (e.g., DCI format 2_0), the corresponding IAB node can select a DFU symbol direction according to a specific rule. This specific rule can be configured as one of two rules via an independent parameter. As another example, the aforementioned specific rule could be a rule that pre-commits to prioritizing the selection of a specific symbol direction. For example, considering that in many cases symbol direction #2 is cell-specific (via...) tdd-UL-DL-ConfigurationCommon If the DFU symbol direction is configured or indicated specifically (e.g., via DCI format 2_0, etc.), the DFU symbol direction may be committed to be determined based on symbol direction #2.

[0384] To indicate whether to use soft symbols or time / frequency resources according to HSNA configuration #1 and HSNA configuration #2 via DCI format 2_5, six types of resources can be defined as follows.

[0385] Type #1 resource: DL soft symbol configured by HSNA configuration #1 Type #2 resource: Variable soft symbol configured by HSNA configuration #1 Type #3 resource: UL soft symbol configured by HSNA Configuration #1 Type #4 resource: DL soft (time / frequency / beam) resource configured by HSNA configuration #2. Type #5 resource: Variable soft (time / frequency / beam) resource configured by HSNA configuration #2. Type #6 resource: UL soft (time / frequency / beam) resource configured by HSNA configuration #2. The definitions of types #1 to #6 above are merely examples for ease of description, and the exemplary embodiments of this disclosure are not limited thereto. For example, in an exemplary embodiment of a communication system, not all times, frequencies, and beams are specified in types #4 to #6, but some time-frequency resources or some beams may be specified.

[0386] Table 20 illustrates a first exemplary embodiment of the mapping relationship between the availability indicator (AI) index field values ​​of the aforementioned resource types #1 to #6 and the availability of soft resources.

[0387] [Table 20]

[0388] The mapping relationships shown in Table 20 may include those shown in Table 8, etc. Therefore, in an exemplary embodiment of the communication system, the payload of each AI index field in DCI format 2_5 can be extended from 3 bits to 4 bits. According to Table 20, the upper-level IAB node can indicate not only regular operations (i.e., whether the operation of D / U / F soft symbols of IAB-DU based on DU / MT TDM operations) using values ​​0 to 7, but also whether the operation of soft symbols based on DU / MT TDM or SDM operations is used simultaneously using values ​​8 to 14. The operation corresponding to values ​​8 to 14 in Table 20 is characterized in that, in addition to indicating the operation indicated by values ​​1 to 7 (i.e., whether the soft symbol / resource according to HSNA configuration #1 is used), it also indicates whether the soft symbol / resource according to HSNA configuration #2, which overlaps with the soft symbol / resource according to HSNA configuration #1, is used. In this scenario, the IAB node might need criteria to determine whether to follow the mapping in Table 8 or Table 20, and therefore the IAB node could implicitly follow the mapping in Table 8 based on whether HSNA configuration #2 has been received, reported information about whether simultaneous DU / MT operations are possible or preferred, etc. Alternatively, higher-level parameters explicitly indicating whether to follow the mapping in Table 8 or Table 20 can be introduced. It should be noted that in Table 20, the order of values ​​and their meaning are not critical factors, and some values ​​can be changed or omitted in practice.

[0389] As another method to support the mapping between AI index field values ​​based on resource type and the availability of the corresponding soft resources, the aforementioned DCI format 2_5 can be extended. The CRC of the extended DCI format 2_5 can be scrambled using AI-RNTI, and DCI format 2_5 can include the following information.

[0390] In this case, AI 1-X may use the soft symbols / resources configured by HSNA configuration #1 according to the mapping indication in Table 8, and AI 2-X may use the soft symbols / resources configured by HSNA configuration #2 according to the mapping indication in Mapping Table 21.

[0391] In addition, Table 21 shows a second embodiment of the mapping relationship between the AI ​​index field values ​​of the aforementioned resource types #1 to #6 and the availability of soft resources.

[0392] [Table 21]

[0393] Referring to Table 21, the parent node of the IAB node can indicate to the IAB node, based on a DCI format 2_5, whether to immediately use soft symbols / resources according to HSNA configuration #1 and HSNA configuration #2. The size of the extended DCI format 2_5 can be configured via higher-level parameters to have a different value than that of the regular DCI format 2_5 (e.g., up to 128 bits).

[0394] Table 22 illustrates a third exemplary embodiment of the mapping relationship between the AI ​​index field values ​​of the aforementioned resource types #1 to #6 and the availability of soft resources.

[0395] [Table 22]

[0396] Referring to Table 22, the new mapping extends the payload of each AI index field in DCI format 2_5 from 3 bits to 4 bits to include the regular mapping in Table 8. According to Table 22, the upper-level IAB node can indicate not only regular operation (i.e., whether to use D / U / F soft symbols of IAB-DU based on DU / MT TDM operation) using values ​​0 to 7, but also whether to use simultaneous operation soft symbols based on DU / MT FDM or SDM operation using values ​​8 to 15. In addition to the operation indicated by values ​​1 to 7 (i.e., whether to use soft symbols / resources according to HSNA configuration #1), the operation corresponding to values ​​8 to 14 in Table 22 can indicate whether to use soft symbols / resources according to HSNA configuration #2. That is, it can be understood that when the operation corresponding to values ​​8 to 14 in Table 22 is indicated, the lower-level IAB node is instructed to stop DU / MT TDM operation and perform simultaneous DU / MT operation (FDM / SDM operation). In this case, the IAB node may need a criterion to determine whether to follow the mapping in Table 8 or the mapping in Table 20. For example, an IAB node may implicitly follow the mapping in Table 8 based on whether HSNA configuration #2 is received or information regarding whether simultaneous DU / MT operation is possible or preferred. Alternatively, higher-level parameters that explicitly indicate whether an IAB node follows the mapping in Table 8 or Table 21 may be introduced. It should be noted that in Table 22, the order of the values ​​and their meaning are not important factors, and some values ​​may be changed or omitted in practice.

[0397] On the other hand, higher-level IAB nodes may need to indicate whether the AI ​​(AI) regarding whether simultaneous operation is supported or preferred (i.e., information about which of cases A through F are supported or preferred, and information about whether power control, beam management, resource configuration, and / or protection symbols / bands are required) is violated, as reported by lower-level IAB nodes (i.e., IAB DU, IAB MT). For example, a violation can be understood as a soft symbol / resource indicated by the higher-level node as available including cases reported / indicated as not being preferred time / frequency / spatial (beam) resources for simultaneous DU / MT operation.

[0398] If the AI ​​indicated by the superior IAB node via DCI format 2_5 violates the information reported / indicated by the subordinate IAB node (IAB DU, IABMT) regarding whether simultaneous operation is supported or preferred (i.e., information regarding which of cases A to F are supported or preferred, and information regarding whether power control, beam management, resource configuration, and / or protection symbols / bands are required), the subordinate IAB node may choose at least one of a variety of solutions, such as 1) ignoring the AI ​​indication, 2) prioritizing operation based on information regarding whether simultaneous operation is supported or preferred, or 3) ensuring that it can freely choose according to the implementation of the subordinate IAB node.

[0399] For the coexistence of IAB nodes and terminals supporting simultaneous DU / MT operations, in addition to the exemplary embodiments described above, the following methods may also be considered. As an example, a DU or MT within an IAB node may be configured to exclude the application of simultaneous operation configurations (such as FDM and SDM) within a certain portion of a time slot (e.g., the first N symbols of the time slot) to ensure control channel transmission bandwidth for legacy terminals. As another example, a DU or MT within an IAB node may be guaranteed or configured not to perform simultaneous DU / MT operations in the N symbols before and after a cell-specific or semi-specific signal / channel.

[0400] The “first HSNA timeslot configuration” can be understood as being applied to a DU cell, and the “second or more HSNA timeslot configurations” can be configured for 1) each MT including the IAB node of the corresponding DU, 2) each MT cell including the IAB node of the corresponding DU, or 3) each beam of the corresponding DU.

[0401] The IAB node may update the capability report to the CU or parent node. This is understood to mean that the IAB node can overlay information about whether simultaneous transmission and reception of DU / MTs included in one or more MTs within the IAB node is possible, information previously reported by the IAB node to the CU or parent node. The IAB node can then update information about whether TDM, FDM, or SDM is supported or preferred in a given time resource. In this case, to match the understanding of the CU, parent node, and IAB node regarding when the IAB capability report value is applied, it may be necessary to define the application timing of the IAB capability report. As an example, the content of the corresponding IAB capability report may be committed to or configured to be applied after a specific time elapsed (e.g., N symbols, N time slots, N ms, etc.) from the time of receipt of the ACK for the F1AP used for the IAB capability report, or it may be committed to or configured to be applied after a specific time elapsed (e.g., N symbols, N time slots, N ms, etc.) from the time of transmission of the F1AP including the IAB capability report.

[0402] To support the aforementioned simultaneous DU / MT transmit / receive operations for each frequency resource, the multiplexing information report of the IAB node can be updated to include information about specific frequency resources within an MT cell (CC) (i.e., the multiplexing information can be expanded to include specific frequency resources within the cell) or to include information about specific time resources (i.e., the multiplexing information can be expanded to restrict from which time point it is applied). Based on this, the CU or parent node can identify whether TDM / FDM / SDM is applicable between the resources of the access link and the resources of the backhaul link. In this case, the aforementioned time resource information can be defined as a supportable multiplexing (TDM / FDM / SDM) pattern repeated in units of several OFDM symbols, time slots, or ms (e.g., a TDM / FDM / SDM pattern repeated every 10 time slots, such as "TTFFTTSSFF").

[0403] The configurations described in the first to eighth exemplary embodiments of the communication system are not necessarily mutually exclusive, and the configurations proposed in multiple exemplary embodiments can be combined and applied. For example, an IAB node can be implemented such that the resource management method according to the first exemplary embodiment and the BD / CCE distribution method according to the sixth exemplary embodiment can be applied simultaneously. As another example, an IAB node can be implemented such that the frequency domain DU / MT simultaneous operation configuration method according to one of the first to third exemplary embodiments and the simultaneous operation unit determination method according to the fourth exemplary embodiment can be applied simultaneously. The IAB node can report information to the superior node about which features or functions according to the first to eighth exemplary embodiments are implemented or not implemented. Based on this, the superior node can instruct the IAB node to perform what operation based on L1 signaling or higher-level signaling.

[0404] Figure 18 This is a block diagram illustrating an exemplary embodiment of a communication node constituting a communication system.

[0405] Reference Figure 18 The communication node 1800 may include at least one processor 1810, a memory 1820, and a transceiver 1830 connected to a network for performing communication. Furthermore, the communication node 1800 may also include an input interface device 1840, an output interface device 1850, a storage device 1860, etc. The corresponding components included in the communication node 1800 can communicate with each other as if connected via a bus 1870.

[0406] However, each component included in the communication node 1800 may be connected to the processor 1810 via a separate interface or a separate bus instead of the common bus 1870. For example, the processor 1810 may be connected via a dedicated interface to at least one of the memory 1820, transceiver 1830, input interface device 1840, output interface device 1850, and storage device 1860.

[0407] Processor 1810 can execute a program stored in at least one of memory 1820 and storage device 1860. Processor 1810 may refer to a central processing unit (CPU), a graphics processing unit (GPU), or a dedicated processor that executes methods according to embodiments of the present disclosure thereon. Each of memory 1820 and storage device 1860 may be constituted by at least one of volatile storage medium and non-volatile storage medium. For example, memory 1820 may include at least one of read-only memory (ROM) and random access memory (RAM).

[0408] Communication node 1800 can be configured with reference Figures 1 to 17 The exemplary embodiment of the described communication system corresponds to any of the communication nodes. In the exemplary embodiment of the communication system, communication node 1800 may correspond to an IAB node. For example, communication node 1800 may perform operations related to references Figures 13 to 17 The operations described for the IAB nodes are the same or similar. The processor 1810 of the communication node 1800 can execute instructions for communicating with the upper or lower level nodes of the IAB node.

[0409] On the other hand, communication node 1800 can correspond to IAB-DU. For example, communication node 1800 can execute and reference... Figures 13 to 17The operation of the described IAB-DU is the same as or similar to that described. The processor 1810 of communication node 1800 controls the radio signal transmission and reception operations of the transceiver 1830 of the IAB-DU, which includes a transmitter and a receiver. The processor 1810 of communication node 1800 determines whether communication node 1800 can use resources and performs communication with other communication nodes based on the determination result.

[0410] On the other hand, communication node 1800 can correspond to IAB-MT. For example, communication node 1800 can execute and reference... Figures 13 to 17 The operation described is the same as or similar to that of the IAB-MT. The processor 1810 of communication node 1800 controls the radio signal transmission and reception operations of the transceiver 1830 of the IAB-MT, which includes a transmitter and a receiver. The processor 1810 of communication node 1800 determines whether communication node 1800 can use resources and performs communication with other communication nodes based on the determination result.

[0411] According to exemplary embodiments of this disclosure, the IAB-MT and IAB-DU included in an IAB node can communicate with their parent and child nodes respectively according to a TDD scheme or a simultaneous operation scheme. The parent node (such as an IAB donor of the IAB node) can deliver resource configuration information (or resource indicators) indicating the allocated resources for each of the IAB-DU and IAB-MT to the IAB node in the form of a TDM scheme, FDM scheme, SDM scheme, etc. Signals (such as DCI, FIAP, etc.) can be extended and used for the transmission of resource configuration information (or resource indicators) delivered from the parent node of the IAB node to the IAB node. Therefore, communication efficiency through the IAB node can be improved, its coverage can be expanded, and its communication capacity can be increased.

[0412] However, the effects that can be achieved by the resource management method and apparatus in the wireless communication system according to the exemplary embodiments of the present disclosure are not limited to the effects described above, and those skilled in the art to which this disclosure pertains can clearly understand other effects not mentioned based on the configurations described in this disclosure.

[0413] Exemplary embodiments of this disclosure can be implemented as program instructions executable by various computers and recorded on a computer-readable medium. The computer-readable medium may include program instructions, data files, data structures, or combinations thereof. The program instructions recorded on the computer-readable medium may be specifically designed and configured for this disclosure, or may be known and available to those skilled in the art of computer software.

[0414] Examples of computer-readable media may include hardware devices (such as ROM, RAM, and flash memory) specifically configured to store and execute program instructions. Examples of program instructions include machine code generated, for example, by a compiler, and high-level language code that can be executed by a computer using an interpreter. The aforementioned exemplary hardware devices may be configured to operate as at least one software module to perform embodiments of this disclosure, and vice versa.

[0415] While embodiments of the present disclosure and their advantages have been described in detail, it should be understood that various changes, substitutions and alterations may be made herein without departing from the scope of the disclosure.

Claims

1. A resource management method performed by an Integrated Access and Backhaul (IAB) node in a communication system, the resource management method comprising: Based on at least one higher-level signaling signal received from the parent node of the IAB node, first information for resource configuration of the IAB node is obtained. Based on at least one higher-level signaling signal received from the superior node, second information for resource configuration of the IAB node is obtained. Receive at least one physical layer signaling signal for resource configuration of the IAB node from the superior node; as well as Based on the first information, the second information, and the at least one physical layer signaling signal, the multiplexed communication of the IAB mobile terminal MT and the IAB distributed unit DU constituting the IAB node is determined. In the determination process, the IAB node determines whether frequency division multiplexing is applied to the multiplexed communication of IAB-MT and IAB-DU. The first information includes at least one of information in the time domain regarding the communication direction configured for IAB-MT and information regarding the communication direction configured for IAB-DU, and the communication direction includes at least one of downlink DL, uplink UL, variable, and combinations thereof. The second piece of information includes: information about the simultaneous operation SO scheme of IAB-DU and IAB-MT, and The at least one physical layer signaling signal includes information related to the availability indicator (AI) of soft resources used for IAB-MT or IAB-DU.

2. The resource management method according to claim 1, wherein, The first information includes at least one of the hard / soft / unavailable HSNA configuration configured for IAB-MT in the time domain and the HSNA configuration configured for IAB-DU.

3. The resource management method according to claim 1, wherein, Information regarding the simultaneous operation scheme includes at least one of the following: Both IAB-DU and IAB-MT execute the first case of transmission; Both IAB-DU and IAB-MT perform the second case of reception; The third case involves IAB-DU performing reception and IAB-MT performing transmission; The fourth case involves IAB-DU performing transmission and IAB-MT performing reception; as well as The fifth case is that radio resources used by IAB-DU and IAB-MT are reused in a frequency division scheme.

4. The resource management method according to claim 1, wherein, The first information includes at least one of the HSNA configuration configured for IAB-MT and the HSNA configuration configured for IAB-DU in the frequency domain.

5. The resource management method according to claim 1, wherein, Information related to AI used for soft resources includes: information on the availability of at least one of DL soft resources, UL soft resources, variable soft resources, and concurrently operating SO soft resources.

6. The resource management method according to claim 1, wherein, Information related to AI for soft resources includes: information related to the HSNA configuration included in the first information, which is configured for at least one of IAB-MT and IAB-DU in the frequency domain.

7. A resource management method executed by a first communication node in a communication system, the resource management method comprising: Generate at least one higher-level signaling signal including first and second information for resource configuration of the IAB node for integrated access and backhaul, wherein the IAB node is a subordinate node of the first communication node. Send at least one higher-layer signaling signal to the IAB node; Send at least one physical layer signaling signal to the IAB node for resource configuration of the IAB node; and Communication with the IAB node is performed based on multiplexed communication determined by the IAB node based on the first information, the second information, and the at least one physical layer signaling signal. The multiplexed communication is based on the multiplexed communication of the IAB mobile terminal (MT) and the IAB distributed unit (DU) constituting the IAB node. Furthermore, based on the first information, the second information, and the at least one physical layer signaling signal, it is determined whether frequency division multiplexing is applied to the multiplexed communication between the IAB-MT and the IAB-DU. The first information includes at least one of information in the time domain regarding the communication direction configured for IAB-MT and information regarding the communication direction configured for IAB-DU, and the communication direction includes at least one of downlink DL, uplink UL, variable, and combinations thereof. The second piece of information includes: information about the simultaneous operation SO scheme of IAB-DU and IAB-MT, and The at least one physical layer signaling signal includes information related to the availability indicator (AI) of soft resources used for IAB-MT or IAB-DU.

8. The resource management method according to claim 7, wherein, The first information includes at least one of the hard / soft / unavailable HSNA configuration configured for IAB-MT in the time domain and the HSNA configuration configured for IAB-DU.

9. The resource management method according to claim 7, wherein, Information regarding the simultaneous operation scheme includes at least one of the following: Both IAB-DU and IAB-MT execute the first case of transmission; Both IAB-DU and IAB-MT perform the second case of reception; The third case involves IAB-DU performing reception and IAB-MT performing transmission; The fourth case involves IAB-DU performing transmission and IAB-MT performing reception; as well as The fifth case is that radio resources used by IAB-DU and IAB-MT are reused in a frequency division scheme.

10. The resource management method according to claim 7, wherein, The first information includes at least one of the HSNA configuration configured for IAB-MT and the HSNA configuration configured for IAB-DU in the frequency domain.

11. The resource management method according to claim 7, wherein, Information related to AI used for soft resources includes: information on the availability of at least one of DL soft resources, UL soft resources, variable soft resources, and concurrently operating SO soft resources.

12. The resource management method according to claim 7, wherein, Information related to AI for soft resources includes: information related to the HSNA configuration included in the first information, which is configured for at least one of IAB-MT and IAB-DU in the frequency domain.

Images