Method and apparatus for operation of an IAB node when multiple parent nodes are connected to a single IAB node

Abstract

The present specification proposes a method for operation to prevent resource conflicts and a method for operation of an IAB node when resource conflicts and / or timing misalignments occur in a case where a plurality of parent nodes are connected to a single IAB node.

Description

Technical Field

[0001] The present disclosure relates to wireless communications. Background Art

[0002] One potential technology to enable future cellular network deployment scenarios and applications is to support wireless backhaul and relay links. This enables flexible and high-density deployment of NR cells without the need to densify the transmission network proportionally.

[0003] It is expected that together with local deployment of massive MIMO or multi-beam systems, greater bandwidth will be available in NR compared to LTE. Therefore (e.g., mmWave spectrum) creates opportunities for the development and deployment of integrated access and backhaul links. This makes it easier to deploy dense networks of self-backhauled NR cells in a more integrated manner by establishing multiple control and data channels / procedures defined to provide access or access to terminals. Such systems are called integrated access and backhaul links (IAB). Summary of the invention

[0004] Technical Solution

[0005] The present specification proposes an operation method for preventing resource conflicts when multiple parent nodes are connected to one IAB node, and a method for operating the IAB node when resource conflicts and / or timing misalignments occur.

[0006] Beneficial Effects

[0007] According to the present specification, when a plurality of parent nodes are connected to one IAB node, communication between the IAB nodes can be efficiently performed without resource conflict, and even if resource conflict occurs, a protection symbol is set.

[0008] The effects that can be obtained through the specific examples of this specification are not limited to the effects listed above. For example, there may be various technical effects that can be understood or derived from this specification by a person of ordinary skill in the relevant field. Therefore, the specific effects of this specification are not limited to those explicitly described herein, and may include various effects that can be understood or derived from the technical characteristics of this specification. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] The following figures are created to explain specific examples of this specification. Because the names of specific devices or the names of specific signals / messages / fields described in the figures are presented by way of example, the technical features of this specification are not limited to the specific names used in the following figures.

[0010] Figure 1 The figure shows a wireless communication system to which the present disclosure can be applied.

[0011] Figure 2 is a diagram illustrating a radio protocol architecture for a user plane.

[0012] Figure 3 is a diagram showing a radio protocol architecture for a control plane.

[0013] Figure 4 Another example of a wireless communication system to which the technical features of the present disclosure can be applied is shown.

[0014] Figure 5 Diagram showing the functional division between NG-RAN and 5GC.

[0015] Figure 6 The diagram illustrates an example of a frame structure that can be applied in NR.

[0016] Figure 7 The diagram shows the time slot structure.

[0017] Figure 8 Figure CORESET.

[0018] Fig. 9 is a diagram illustrating the difference between a conventional control area and a CORESET in NT.

[0019] Fig.10 An example of a frame structure of a new radio access technology is illustrated.

[0020] Fig.11 Figure 1 shows the structure of a self-contained time slot.

[0021] Fig.12 is an abstract schematic diagram illustrating the hybrid beamforming structure from the perspective of the TXRU and physical antennas.

[0022] Fig.13 A synchronization signal and PBCH (SS / PBCH) block is shown.

[0023] Fig.14 This section explains how the UE obtains timing information.

[0024] Fig.15 An example of a system information acquisition process of a UE is shown.

[0025] Fig.16 Used to describe the random access process.

[0026] Fig.17 is a diagram for describing a power ramping counter.

[0027] Fig.18 The concept of threshold value for SS blocks used for RACH resource relation is explained.

[0028] Fig.19 is a flow chart illustrating an example of performing idle mode DRX operation.

[0029] Fig. 20 The diagram shows the DRX cycle.

[0030] Fig.21 An example of a network with an integrated access and backhaul link (IAB) is schematically illustrated.

[0031] Fig. 22 Examples of operation of the IAB system in standalone (SA) mode and non-standalone (NSA) mode are shown.

[0032] Fig.23 An example of the configuration of access and backhaul links is schematically shown.

[0033] Fig.24 Used to explain the links and relationships between IAB nodes.

[0034] Fig.25 Timing alignment case 1 is shown.

[0035] Fig.26 Timing alignment case 6 is shown.

[0036] Fig. 27 Timing alignment case 7 is shown.

[0037] Fig.28 An example is illustrated in which a plurality of component carriers are configured for an IAB node.

[0038] Fig.29 An example of scenario 1 is schematically shown.

[0039] Fig.30 An example of scenario 2 is shown.

[0040] Fig.31 An example of scenario 3 is shown.

[0041] Fig.32 and Fig.33 An example is shown in which a plurality of parent nodes are connected to one IAB node.

[0042] Fig.34 is a flowchart illustrating an operation example of the first parent DU-cell when the first parent DU-cell and the second parent DU-cell are connected to the IAB node.

[0043] Fig.35 is a flowchart of an operation example of an IAB node when multiple parent DU-cells are connected to the IAB node. Here, the IAB node may mean an MT of the IAB node.

[0044] Fig.36 An example of transmission / reception timing of each node when two parent nodes are connected to one IAB node is illustrated.

[0045] Fig.37 An example of the difference in uplink transmission timing of an IAB node relative to two parent nodes is illustrated.

[0046] Fig.38 is a flowchart of an example of a method for setting protection symbols of an IAB node according to some embodiments of the present specification.

[0047] Fig.39 An example is shown in which downlinks are configured for parent node 1 and parent node 2.

[0048] Fig.40 An example is shown in which the parent node 1 is configured for the downlink and the parent node 2 is configured for the uplink.

[0049] Fig.41 An example is shown in which the parent node 1 is configured for the uplink and the parent node 2 is configured for the downlink.

[0050] Fig.42 An example is shown in which uplinks are configured for parent node 1 and parent node 2.

[0051] Fig.43 An example is illustrated in which Alternative Scheme 2 is applied among the operating methods of the IAB node when resources conflict between two parent links.

[0052] Fig.44 is a flowchart of an example of a resource setting method for an IAB node according to some embodiments of the present specification.

[0053] Fig.45 The diagram shows a communication system 1 applied to the present specification.

[0054] Fig.46 The diagram illustrates a wireless device suitable for use with the present disclosure.

[0055] Fig.47 The diagram shows the signal processing circuit used to transmit the signal.

[0056] Fig.48 Another example of a wireless device to which the present disclosure is applied is shown.

[0057] Fig.49 The diagram shows a portable device to which the present disclosure is applied.

[0058] Fig.50 The illustration is applied to a vehicle of the present disclosure or an autonomous driving vehicle.

[0059] Fig.51 The illustration is applied to a vehicle of the present disclosure.

[0060] Fig.52 The diagram illustrates an XR device applicable to the present disclosure.

[0061] Fig.53 The figure shows a robot applied to the present disclosure.

[0062] Fig.54 The diagram illustrates an AI device applied to the present disclosure. DETAILED DESCRIPTION

[0063] In this document, "A or B" may mean "only A", "only B", or "A and B". That is, "A or B" may be interpreted as "A and / or B" in this document. For example, "A, B or C" may mean "only A", "only B", "only C", or "any combination of A, B, and C".

[0064] As used herein, a slash ( / ) or a comma (,) may mean "and / or". For example, "A / B" may mean "A and / or B". Thus, "A / B" may include "only A", "only B", or "A and B". For example, "A, B, C" may mean "A, B, or C".

[0065] As used herein, "at least one of A and B" may mean "only A", "only B", or "both A and B". In addition, as used herein, "at least one of A or B" or "at least one of A and / or B" may be equivalently interpreted as "at least one of A and B".

[0066] Furthermore, herein, “at least one of A, B, and C” may mean “only A,” “only B,” “only C,” or “any combination of A, B, and C.” Furthermore, “at least one of A, B, or C” or “at least one of A, B, and / or C” may mean “at least one of A, B, and C.”

[0067] In addition, the brackets used herein may mean "for example". For example, the expression "control information (PDCCH)" may mean that PDCCH is proposed as an example of control information. That is, the control information is not limited to PDCCH, but PDCCH is proposed as an example of control information. In addition, the expression "control information (ie, PDCCH)" may also mean that PDCCH is proposed as an example of control information.

[0068] The technical features described separately in one figure in this specification can be implemented separately or simultaneously.

[0069] Figure 1 A wireless communication system to which the present disclosure can be applied is shown. The wireless communication system may be referred to as an Evolved UMTS Terrestrial Radio Access Network (E-UTRAN) or a Long Term Evolution (LTE) / LTE-A system.

[0070] The E-UTRAN includes at least one base station (BS) 20, which provides a control plane and a user plane for a user equipment (UE) 10. The UE 10 may be fixed or mobile, and may be referred to as another term, such as a mobile station (MS), a user terminal (UT), a subscriber station (SS), a mobile terminal (MT), a wireless device, etc. The BS 20 is typically a fixed station that communicates with the UE 10, and may be referred to as another term, such as an evolved Node B (eNB), a base transceiver system (BTS), an access point, etc.

[0071] The BSs 20 are connected to each other using an X2 interface. The BSs 20 are also connected to an Evolved Packet Core (EPC) 30 using an S1 interface, more specifically, to a Mobility Management Entity (MME) via S1-MME, and to a Serving Gateway (S-GW) via S1-U.

[0072] The EPC 30 includes an MME, an S-GW, and a packet data network gateway (P-GW). The MME has access information of the UE or capability information of the UE, and such information is generally used for mobility management of the UE. The S-GW is a gateway having the E-UTRAN as an endpoint. The P-GW is a gateway having the PDN as an endpoint.

[0073] The layers of the radio interface protocol between the UE and the network can be divided into a first layer (L1), a second layer (L2), and a third layer (L3) based on the lower three layers of the open system interconnection (OSI) simulation known in the communication system. Among them, the physical (PHY) layer belonging to the first layer provides an information transfer service by using a physical channel, and the radio resource control (RRC) layer belonging to the third layer is used to control radio resources between the UE and the network. To this end, the RRC layer exchanges RRC messages between the UE and the BS.

[0074] Figure 2 is a diagram showing the wireless protocol architecture for the user plane Figure 3 is a diagram showing a wireless protocol architecture for a control plane. The user plane is a protocol stack for user data transmission. The control plane is a protocol stack for control signal transmission.

[0075] refer to Figure 2 and 3 , the PHY layer provides information transmission services to the upper layer via a physical channel. The PHY layer is connected to the medium access control (MAC) layer, which is the upper layer of the PHY layer, via a transport channel. Data is transmitted between the MAC layer and the PHY layer via the transport channel. Transport channels are classified according to how data is transmitted via a radio interface and what kind of characteristic data is transmitted.

[0076] Through the physical channel, data moves between different PHY layers, ie, PHY layers of a transmitter and a receiver. The physical channel may be modulated according to an Orthogonal Frequency Division Multiplexing (OFDM) scheme and use time and frequency as radio resources.

[0077] The functions of the MAC layer include mapping between logical channels and transport channels and multiplexing / demultiplexing of transport blocks provided by physical channels on transport channels of MAC service data units (SDUs) belonging to logical channels. The MAC layer provides services to the radio link control (RLC) layer through logical channels.

[0078] The functions of the RLC layer include concatenation, segmentation, and reassembly of RLC SDUs. In order to ensure the quality of various types of services (QoS) required by radio bearers (RBs), the RLC layer provides three types of operation modes: transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM). AM RLC provides error correction through automatic repeat request (ARQ).

[0079] The RRC layer is defined only in the control plane. The RRC layer is related to the configuration, reconfiguration, and release of radio bearers, and is responsible for control of logical channels, transport channels, and physical channels. RB means a logical path provided by the first layer (PHY layer) and the second layer (MAC layer, RLC layer, and PDCP layer) to facilitate data transmission between the UE and the network.

[0080] The functions of the Packet Data Convergence Protocol (PDCP) on the user plane include transmission and header compression of user data, and encryption. The functions of the PDCP layer on the control plane include transmission and encryption / integrity protection of control plane data.

[0081] What RB is configured means the process of defining the characteristics of the radio protocol layer and the channel in order to provide a specific service and configuring each detailed parameter and operation method. RB can be divided into two types of signaling RB (SRB) and data RB (DRB). SRB is used as a channel through which RRC messages are transmitted on the control plane, and DRB is used as a channel through which user data is transmitted on the user plane.

[0082] If an RRC connection is established between the RRC layer of the UE and the RRC layer of the E-UTRAN, the UE is in the RRC connected state. If not, the UE is in the RRC idle state.

[0083] The downlink transport channel through which data is transmitted from the network to the UE includes a broadcast channel (BCH) through which system information is transmitted and a downlink shared channel (SCH) through which user traffic or control messages are transmitted. Traffic or control messages for downlink multicast or broadcast services may be transmitted through the downlink SCH, or may be transmitted through an additional downlink multicast channel (MCH). Meanwhile, the uplink transport channel through which data is transmitted from the UE to the network includes a random access channel (RACH) through which an initial control message is transmitted and an uplink shared channel (SCH) through which user traffic or control messages are transmitted.

[0084] Logical channels placed above and mapped to the transport channels include a broadcast control channel (BCCH), a paging control channel (PCCH), a common control channel (CCCH), a multicast control channel (MCCH), and a multicast traffic channel (MTCH).

[0085] A physical channel includes several OFDM symbols in the time domain and several subcarriers in the frequency domain. A subframe includes multiple OFDM symbols in the time domain. An RB is a resource allocation unit and includes multiple OFDM symbols and multiple subcarriers. In addition, each subframe may use a specific subcarrier of a specific OFDM symbol (e.g., the first OFDM symbol) of a corresponding subframe for a physical downlink control channel (PDCCH), i.e., an L1 / L2 control channel. A transmission time interval (TTI) is a unit time for transmission. For example, a TTI may be a subframe or a time slot.

[0086] Hereinafter, new radio access technology (new RAT, NR) will be described.

[0087] As more and more communication devices require more communication capacity, improved mobile broadband communication compared to existing radio access technologies is needed. Moreover, large-scale machine type communication (MTC) that provides various services by connecting many devices and objects is one of the main issues to be considered in the next generation of communications. In addition, the design of communication systems considering reliability / delay-sensitive services / UEs is being discussed. The introduction of next generation radio access technologies considering enhanced mobile broadband communication (eMBB), massive mobile communication (mMTC), and ultra-reliable low latency communication (URLLC) is discussed. For convenience, in this disclosure, this new technology may be referred to as a new radio access technology (new RAT or NR).

[0088] Figure 4 Another example of a wireless communication system to which the present disclosure can be applied is shown.

[0089] Specifically, Figure 4The system architecture based on the 5G new radio access technology (NR) system is shown. The entities used in the 5G NR system (hereinafter referred to as "NR") can absorb Figure 1 The entities used in the NR system can be identified by the name "NG" to distinguish them from LTE.

[0090] refer to Figure 4 The wireless communication system includes one or more UEs 11, a next generation RAN (NG-RAN) and a fifth generation core network (5GC). The NG-RAN consists of at least one NG-RAN node. The NG-RAN node corresponds to Figure 5 The NG-RAN node is composed of at least one gNB 21 and / or at least one ng-eNB 22. The gNB 21 provides NR user plane and control plane protocol termination to the UE 11. The ng-eNB 22 provides E-UTRA user plane and control plane protocol termination to the UE 11.

[0091] 5GC includes access and mobility management function (AMF), user plane function (UPF) and session management function (SMF). AMF is responsible for functions such as non-access stratum (NAS) security and idle state mobility processing. AMF is an entity that includes traditional MMF functions. UPF is responsible for functions such as mobile anchoring and protocol data unit (PDU) processing. UPF is an entity that includes traditional S-GW functions. SMF is responsible for functions such as UE Internet Protocol (IP) address allocation and PDU session control.

[0092] gNB and ng-eNB are interconnected through the Xn interface. gNB and ng-eNB are also connected to 5GC through the NG interface. More specifically, gNB and ng-eNB are connected to AMF through the NG-C interface and to UPF through the NG-U interface.

[0093] Figure 5 Diagram showing the functional division between NG-RAN and 5GC.

[0094] refer to Figure 5 , gNB can provide functions such as inter-cell radio resource management (inter-cell RRM), radio bearer management (RB control), connection mobility control, radio admission control, measurement configuration and provision, dynamic resource allocation, etc. AMF can provide functions such as NAS security, idle state mobility processing, etc. UPF can provide functions such as mobility anchoring, PDU processing, etc. SMF can provide functions such as UE IP address assignment, PDU session control, etc.

[0095] Figure 6An example of a frame structure that can be applied in NR is illustrated.

[0096] refer to Figure 6 , a frame may consist of 10 milliseconds (ms) and include 10 subframes, each subframe consisting of 1 ms.

[0097] In NR, uplink and downlink transmissions can be composed of frames. The length of a radio frame is 10ms and can be defined as two 5ms half frames (HF). HF can be defined as five 1ms subframes (SF). SF can be divided into one or more time slots, and the number of time slots in a SF depends on the subcarrier spacing (SCS). Depending on the cyclic prefix (CP), each time slot includes 12 or 14 OFDM (A) symbols. When a normal CP is used, each time slot includes 14 symbols. When an extended CP is used, each time slot includes 12 symbols. Here, the symbol may include OFDM symbols (or CP-OFDM symbols) and SC-FDMA symbols (or DFT-S-OFDM symbols).

[0098] Depending on the subcarrier spacing, a subframe may include one or more time slots.

[0099] The following Table 1 illustrates subcarrier spacing configuration μ.

[0100] [Table 1]

[0101]

[0102] Table 2 below illustrates the number of time slots (N) in a frame according to the subcarrier spacing configuration μ. frame,μ slot ), the number of time slots in a subframe (N subframe,μ slot ), the number of symbols in the time slot (N slot symb )wait.

[0103] [Table 2]

[0104]

[0105] Table 3 below illustrates that the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary depending on the SCS in the case of using the extended CP.

[0106] [Table 3]

[0107] <![CDATA[SCS(15·2 μ )]]> <![CDATA[N slot symb ]]> <![CDATA[N frame,u slot ]]> <![CDATA[N subframe,u slot ]]> 60kHz(μ=2) 12 40 4

[0108] NR supports multiple parameter sets (or subcarrier spacing (SCS)) to support various 5G services. For example, if the SCS is 15kHz, a wide area of ​​the traditional cellular band can be supported. If the SCS is 30kHz / 60kHz, dense cities, lower latency and wider carrier bandwidth are supported. If the SCS is 60kHz or higher, bandwidths greater than 24.25GHz are used to overcome phase noise.

[0109] The NR frequency band can be defined as two types of frequency ranges (FR1, FR2). The value of the frequency range can be changed. For example, the frequency ranges of the two types (FR1, FR2) can be as shown in Table 4 below. For ease of explanation, among the frequency ranges used by the NR system, FR1 may mean "a range below 6 GHz", and FR2 may mean "a range above 6 GHz", and may also be referred to as millimeter wave (mmW).

[0110] [Table 4]

[0111] Frequency range specification Corresponding frequency range Subcarrier Spacing (SCS) FR1 450MHz-6000MHz 15,30,60kHz FR2 24250MHz-52600MHz 60,120,240kHz

[0112] As described above, the value of the frequency range in the NR system may be changed. For example, as shown in Table 5 below, FR1 may include a frequency band in the range of 410 MHz to 7125 MHz. That is, FR1 may include a frequency band of at least 6 GHz (or 5850, 5900, 5925 MHz, etc.). For example, the frequency band of at least 6 GHz (or 5850, 5900, 5925 MHz, etc.) included in FR1 may include an unlicensed frequency band. The unlicensed frequency band may be used for various purposes, for example, an unlicensed frequency band for vehicle-specific communications (e.g., autonomous driving).

[0113] [Table 5]

[0114] Frequency range specification Corresponding frequency range Subcarrier Spacing (SCS) FR1 410MHz-7125MHz 15,30,60kHz FR2 24250MHz-52600MHz 60,120,240kHz

[0115] In the NR system, OFDM (A) parameter sets (e.g., SCS, CP length, etc.) may be configured differently between multiple cells integrated into one UE. Therefore, the (absolute time) duration of a time resource (e.g., SF, time slot, or TTI) configured by the same number of symbols (collectively referred to as a time unit (TU) for convenience) may be configured differently between the integrated cells.

[0116] Figure 7 The diagram shows the time slot structure.

[0117] refer to Figure 7, a slot includes multiple symbols in the time domain. For example, in the case of normal CP, one slot may include 14 symbols. However, in the case of extended CP, one slot may include 12 symbols. Alternatively, in the case of normal CP, one slot may include 7 symbols. However, in the case of extended CP, one slot may include 6 symbols.

[0118] A carrier includes multiple subcarriers in the frequency domain. A resource block (RB) can be defined as multiple consecutive subcarriers (e.g., 12 subcarriers) in the frequency domain. A bandwidth part (BWP) can be defined as multiple consecutive (P)RBs in the frequency domain, and a BWP can correspond to a parameter set (e.g., SCS, CP length, etc.). A carrier can include up to N (e.g., 5) BWPs. Data communication can be performed through activated BWPs. In a resource grid, each element can be referred to as a resource element (RE) and a complex symbol can be mapped to it.

[0119] The Physical Downlink Control Channel (PDCCH) may include one or more Control Channel Elements (CCEs), as illustrated in the following table.

[0120] [Table 6]

[0121] Aggregation level Number of CCEs 1 1 2 2 4 4 8 8 16 16

[0122] That is, the PDCCH may be transmitted through resources including 1, 2, 4, 8 or 16 CCEs. Here, the CCE includes six resource element groups (REGs), and one REG includes one resource block in the frequency domain and one orthogonal frequency division multiplexing (OFDM) symbol in the time domain.

[0123] At the same time, a new unit called control resource set (CORESET) can be introduced in NR. UE can receive PDCCH in CORESET.

[0124] Figure 8 Figure CORESET.

[0125] refer to Figure 8 , CORESET includes N in the frequency domain CORESET RB The number of resource blocks and N in the time domain CORESET symb ∈{1, 2, 3} number of symbols. N can be provided by the base station through higher layer signaling CORESET RB and N CORESET symb .like Figure 8 As shown in FIG. 1 , a CORESET may include multiple CCEs (or REGs).

[0126] The UE may attempt to detect the PDCCH in units of 1, 2, 4, 8, or 16 CCEs in a CORESET. One or more CCEs for which PDCCH detection may be attempted may be referred to as PDCCH candidates.

[0127] Multiple CORESETs can be configured for a UE.

[0128] Fig. 9 is a diagram illustrating the difference between the conventional control area and the CORESET in NR.

[0129] refer to Fig. 9 , the control region 900 in a conventional wireless communication system (e.g., LTE / LTE-A) is configured on the entire system frequency band used by a base station (BS). All UEs except some (e.g., eMTC / NB-IoT UEs) that only support narrowband must be able to receive wireless signals of the entire system frequency band of the BS in order to properly receive / decode control information sent by the BS.

[0130] On the other hand, in NR, the above-mentioned CORESET is introduced. CORESET 301, 302, and 303 are radio resources for control information to be received by UE, and only a portion, not the entire system bandwidth, may be used. The BS may allocate a CORESET to each UE, and may transmit control information through the allocated CORESET. For example, in Fig. 9 In NR, the first CORESET 301 may be allocated to UE 1, the second CORESET 302 may be allocated to UE 2, and the third CORESET 303 may be allocated to UE 3. In NR, the UE may receive control information from the BS without receiving the entire system frequency band.

[0131] The CORESET may include a UE-specific CORESET for transmitting UE-specific control information and a common CORESET for transmitting control information common to all UEs.

[0132] Meanwhile, NR may require high reliability depending on the application. In this case, a target block error rate (BLER) of downlink control information (DCI) transmitted through a downlink control channel (e.g., a physical downlink control channel (PDCCH)) can be significantly reduced compared to those of conventional technologies. As an example of a method for satisfying the requirement for high reliability, it is possible to reduce the content included in the DCI and / or increase the amount of resources used for DCI transmission. Here, the resources may include at least one of resources in the time domain, resources in the frequency domain, resources in the code domain, and resources in the space domain.

[0133] In NR, the following technologies / features can be applied.

[0134] <Self-contained subframe structure>

[0135] Fig.10 An example of a frame structure of a new radio access technology is illustrated.

[0136] In NR, such as Fig.10 As shown, a structure in which a control channel and a data channel are time-division multiplexed within one TTI may be considered as a frame structure in order to minimize delay.

[0137] exist Fig.10 In the figure, the shaded area represents the downlink control region, and the black area represents the uplink control region. The remaining area can be used for downlink (DL) data transmission or uplink (UL) data transmission. This structure is characterized in that DL transmission and UL transmission are performed sequentially within one subframe, and thus DL data can be sent and UL ACK / NACK can be received within the subframe. Therefore, the time required from the occurrence of a data transmission error to data retransmission is reduced, thereby minimizing the delay in the final data transmission.

[0138] In this subframe structure where data and control are TMD, a time gap may be needed for the base station and the terminal to switch from the transmission mode to the reception mode or from the reception mode to the transmission mode. To this end, some OFDM symbols when DL switches to UL can be set as a guard period (GP) in a self-contained subframe structure.

[0139] Fig.11 Figure 1 shows the structure of a self-contained time slot.

[0140] refer to Fig.11 , can have a self-contained structure in which a time slot includes all of the DL control channel, the DL or UL data channel, the UL control channel, etc. For example, the first N symbols in the time slot can be used to send the DL control channel (hereinafter, the DL control region), and the last M symbols in the time slot can be used to send the UL control channel (hereinafter, the UL control region). N and M are both integers of 0 or greater. The resource region (hereinafter, the data region) located between the DL and UL control regions can be used for the transmission of DL data or UL data. For example, the following configuration can be considered. Each time period is listed in chronological order.

[0141] 1. DL configuration only

[0142] 2. UL configuration only

[0143] 3. Hybrid UL-DL configuration

[0144] -DL area + GP (guard period) + UL control area

[0145] -DL control area + GP + UL area

[0146] Here, the DL region may correspond to (i) a DL data region or (ii) a DL control region + a DL data region, and the UL region may correspond to (i) a UL data region or (ii) a UL data region + a UL control region.

[0147] PDCCH may be transmitted in the DL control region, and PDSCH may be transmitted in the DL data region. In the UL control region, PUCCH may be transmitted, and in the UL data region, PUSCH may be transmitted. In the PDCCH, downlink control information (DCI) may be transmitted, for example, DL data scheduling information or UL data scheduling information. In the PUCCH, uplink control information (UCI) may be transmitted, for example, ACK / NACK (positive acknowledgement / negative acknowledgement) information about DL data, channel state information (CSI) information, or scheduling request (SR). GP provides a time gap during the process of the gNB and UE transitioning from a transmission mode to a reception mode or the process of the gNB and UE transitioning from a reception mode to a transmission mode. Some symbols at the time of switching from DL to UL within a subframe may be configured as GP.

[0148] <Analog Beamforming #1>

[0149] The wavelength is shortened in millimeter waves (mmW), and therefore a large number of antenna elements can be installed in the same area. That is, the wavelength is 1 cm at 30 GHz, and therefore in a 5×5 cm panel, a total of 100 antenna elements can be installed in a two-dimensional array at intervals of 0.5λ (wavelength). Therefore, a large number of antenna elements can be used in mmW to increase beamforming (BF) gain to increase coverage or improve throughput.

[0150] In this case, if a transceiver unit (TXRU) is provided to adjust the transmission power and phase of each antenna element, independent beamforming for each frequency resource can be performed. However, installing a TXRU for all approximately 100 antenna elements reduces efficiency in terms of cost. Therefore, a method of mapping a large number of antenna elements to one TXRU and using an analog phase shifter to control the beam direction is considered. This analog beamforming is able to form only one beam direction in all frequency bands, and therefore cannot provide frequency selective beamforming.

[0151] Hybrid beamforming (BF) with B TXRUs smaller than Q antenna elements can be considered as an intermediate form of digital BF and analog BF. In this case, the number of directions of beams that can be transmitted simultaneously is limited to B, although it depends on the method of connecting the B TXRUs and the Q antenna elements.

[0152] <Analog Beamforming #2>

[0153] When multiple antennas are used in NR, hybrid beamforming, which is a combination of digital beamforming and analog beamforming, appears. Here, in analog beamforming (or RF beamforming), the RF end performs precoding (or combining), and is therefore able to achieve performance similar to that of digital beamforming while reducing the number of RF chains and the number of D / A (or A / D) converters. For convenience, the hybrid beamforming structure can be represented by N TXRUs and M physical antennas. Then, the digital beamforming for the L data layers to be sent at the transmitting end can be represented by an N by L matrix, and the converted N digital signals are converted into analog signals via the TXRU, and analog beamforming represented by an M by N matrix is ​​applied.

[0154] Fig.12 is an abstract diagram illustrating hybrid beamforming from the perspective of the TXRU and physical antennas.

[0155] exist Fig.12 In the NR system, the number of digital beams is L and the number of analog beams is N. Further, in the NR system, it is considered to support more efficient beamforming for terminals located in a specific area by designing the base station to change the analog beamforming in symbol units. In addition, when Fig.12 While N TXRUs and M RF antennas are defined as one antenna panel in NR systems, consideration is given to introducing multiple antenna panels to which mutually independent hybrid beamforming can be applied.

[0156] When the base station uses multiple analog beams as described above, the analog beam suitable for receiving signals may be different for the terminal, and therefore the following beam scanning operation is considered: at least for synchronization signals, system information and paging, the multiple analog beams to be applied in a specific subframe (SF) are scanned symbol by symbol by the base station so that all terminals can have a receiving opportunity.

[0157] Fig.13 A synchronization signal / PBCH (SS / PBCH) block is schematically illustrated.

[0158] refer to Fig.13, SS / PBCH blocks may include PSS and SSS (each of which occupies one symbol and 127 subcarriers) and PBCH (which spans three OFDM symbols and 240 subcarriers, where one symbol may include an unoccupied portion reserved for SSS in the middle). The periodicity of SS / PBCH blocks may be configured by the network, and the time position for sending SS / PBCH blocks may be determined based on the subcarrier spacing.

[0159] Polar codes may be used for PBCH. The UE may assume band-specific subcarrier spacing for SS / PBCH blocks as long as the network has not configured the UE to assume a different subcarrier spacing.

[0160] The PBCH symbol carries its frequency-multiplexed DMRS. QPSK can be used for PBCH. 1008 inherent physical layer cell IDs can be allocated.

[0161] For a half-frame with SS / PBCH blocks, the first symbol index of the candidate SS / PBCH blocks is determined according to the subcarrier spacing of the SS / PBCH blocks, which will be described later.

[0162] - Case A - Subcarrier spacing 15 kHz: The index of the first symbol of the candidate SS / PBCH block is {2,8}+14*n. For carrier frequencies less than or equal to 3 GHz, n=0,1. For carrier frequencies greater than 3 GHz and less than or equal to 6 GHz, n=0,1,2,3.

[0163] - Case B - Subcarrier spacing 30 kHz: The index of the first symbol of the candidate SS / PBCH block is {4, 8, 16, 20} + 28*n. For carrier frequencies less than or equal to 3 GHz, n = 0. For carrier frequencies greater than 3 GHz and less than or equal to 6 GHz, n = 0, 1.

[0164] - Case C - Subcarrier spacing 30 kHz: The index of the first symbol of the candidate SS / PBCH block is {2,8}+14*n. For carrier frequencies less than or equal to 3 GHz, n=0,1. For carrier frequencies greater than 3 GHz and less than or equal to 6 GHz, n=0,1,2,3.

[0165] - Case D - subcarrier spacing 120 kHz: The index of the first symbol of the candidate SS / PBCH block is {4,8,16,20}+28*n. For carrier frequencies greater than 6 GHz, n=0,1,2,3,5,6,7,8,10,11,12,13,15,16,17,18.

[0166] - Case E - subcarrier spacing 240 kHz: The index of the first symbol of the candidate SS / PBCH block is {8, 12, 16, 20, 32, 36, 40, 44} + 56*n. For carrier frequencies greater than 6 GHz, n = 0, 1, 2, 3, 5, 6, 7, 8.

[0167] The candidate SS / PBCH blocks in a half-frame are indexed in ascending order from 0 to L-1 on the time axis. The UE shall determine the 2 LSB bits for L=4 and 3 LSB bits for L>4 of the SS / PBCH block index per half-frame from a one-to-one mapping with the index of the DM-RS sequence sent in the PBCH. For L=64, the UE shall determine the 3 MSB bits of the SS / PBCH block index per half-frame from the PBCH payload bits.

[0168] Through the higher layer parameter "SSB-transmitted-SIB1", the index of the SS / PBCH block in which the UE cannot receive other signals or channels in the RE overlapping with the RE corresponding to the SS / PBCH block can be set. In addition, according to the higher layer parameter "SSB-transmitted", the index of the SS / PBCH block of each serving cell in which the UE cannot receive other signals or channels in the RE overlapping with the RE corresponding to the SS / PBCH block can be set. The setting through "SSB-transmitted" can take precedence over the setting through "SSB-transmitted-SIB1". The periodicity of half frames of the received SS / PBCH block of each serving cell can be set by the higher layer parameter "SSB-periodicityServingCell". If the UE does not set the periodicity of half frames for receiving SS / PBCH blocks, the UE should assume the periodicity of half frames. The UE can assume that the periodicity is the same for all SS / PBCH blocks in the serving cell.

[0169] Fig.14 This section explains how the UE obtains timing information.

[0170] First, the UE can obtain six-bit SFN information through the master information block (MIB) received in the PBCH. Further, the UE can obtain four-bit SFN in the PBCH transport block.

[0171] Second, the UE may obtain a one-bit half-frame indicator as part of the PBCH payload. In the case of less than 3 GHz, the half-frame indicator may be implicitly signaled as part of the PBCH DMRS with Lmax=4.

[0172] Finally, the UE can obtain the SS / PBCH block index through the DMRS sequence and the PBCH payload. That is, within a 5ms period, the UE can obtain the 3-bit LSB of the SS block index through the DMRS sequence. Moreover, the 3-bit MSB of the timing information is explicitly carried in the PBCH payload (for more than 6GHz).

[0173] In the initial cell selection, the UE may assume that the half-frame with SS / PBCH blocks occurs with a periodicity of 2 frames. When an SS / PBCH block is detected, if for FR1, k SSB ≤23, and for FR2, k SSB ≤11, the UE determines that there is a control resource set for the Type0-PDCCH common search space. If for FR1, k SSB >23, and for FR2, k SSB >11, the UE determines that there is no control resource set for the Type0-PDCCH common search space.

[0174] For a serving cell in which no SS / PBCH blocks are transmitted, the UE acquires time and frequency synchronization of the serving cell based on receiving SS / PBCH blocks on the PCell or PSCell of the cell group of the serving cell.

[0175] Hereinafter, acquisition of system information will be described.

[0176] The system information (SI) is divided into a master information block (MIB) and multiple system information blocks (SIBs), where:

[0177] -MIB is always sent on the BCH according to a period of 80 ms, repeated within 80 ms, and includes the parameters required to obtain the system information block type 1 (SIB1) from the cell;

[0178] -SIB1 is sent periodically and repeatedly on DL-SCH. SIB1 includes information about the availability and scheduling of other SIBs (e.g., periodicity or SI window size). In addition, SIB1 indicates whether the SIB (i.e., other SIBs) is broadcast periodically or provided upon request. When other SIBs are provided by request, SIB1 includes information that the UE requested the SIB;

[0179] - SIBs other than SIB1 are carried by system information (SI) messages sent on DL-SCH. Each SI message is sent within a periodic time window (called SI window);

[0180] -For PSCell and SCells, RAN provides the required SI through dedicated signaling. In any case, UE needs to obtain the MIB of PSCell in order to obtain the SFN timing of SCH (which can be different from MCG). When the relevant SI of SCell changes, RAN will release and add the relevant SCell. For PSCell, SI can only be changed by reconfiguration with sync.

[0181] Fig.15 An example of a system information acquisition process of a UE is illustrated.

[0182] refer to Fig.15 , the UE may receive the MIB from the network and may then receive SIB1. Subsequently, the UE may send a system information request to the network and, in response, may receive a system information message from the network.

[0183] The UE may apply the system information acquisition procedure to acquire access stratum (AS) and non-access stratum (NAS) information.

[0184] In RRC_IDLE and RRC_INACTIVE states, the user equipment needs to ensure valid versions of (at least) MIB, SIB1 and system information block type X (according to the relevant RAT support for mobility controlled by the UE).

[0185] In RRC_CONNECTED state, the UE needs to ensure valid versions of MIB, SIB1 and system information block type X (according to the mobility support for the relevant RAT).

[0186] The UE needs to store the relevant SI obtained from the current resident / serving cell. The version of SI acquired and stored by the UE is only valid for a certain period of time. For example, after cell reselection, after returning from out of coverage, or after an indication of a system information change, the UE can use this version of the stored SI.

[0187] Hereinafter, random access will be described.

[0188] The random access procedure of the UE can be summarized as in the following table.

[0189] [Table 7]

[0190]

[0191] Fig.16 The figure shows the random access process.

[0192] refer to Fig.16 , first, the UE may send the PRACH preamble as Msg 1 of the random access procedure via the uplink.

[0193] Two random access preamble sequences with different lengths are supported. The long sequence of length 839 is applied to the subcarrier spacing of 1.25kHz and 5kHz, and the short sequence of length 139 is applied to the subcarrier spacing of 15kHz, 30kHz, 60kHz and 120kHz. The long sequence supports unrestricted sets and restricted sets of type A and type B, while the short sequence can only support unrestricted sets.

[0194] Multiple RACH preamble formats are defined by one or more RACH OFDM symbols, different cyclic prefixes (CPs) and guard times. The PRACH preamble settings to be used are provided to the UE as system information.

[0195] If there is no response to Msg1, the UE may resend a power-ramped PRACH preamble within a specified number of times. The UE calculates the PRACH transmission power for the retransmission of the preamble based on the most recently estimated path loss and the power ramp counter. The power ramp counter does not change when the UE performs beam switching.

[0196] Fig.17 is a diagram for describing a power ramp counter.

[0197] The UE may perform power ramping for retransmission of the random access preamble based on the power ramp counter. Here, as described above, when the UE performs beam switching in PRACH retransmission, the power ramp counter does not change.

[0198] refer to Fig.17 , when the UE retransmits a random access preamble for the same beam, the UE increases the power ramp counter by 1, for example, the power ramp counter increases from 1 to 2, and from 3 to 4. However, when the beam changes, the power ramp counter does not change in PRACH retransmission.

[0199] Fig.18 The concept of the threshold of the SS block in relation to the RACH resources is illustrated.

[0200] System information informs the UE of the relationship between SS blocks and RACH resources. The threshold of SS blocks in relationship to RACH resources is based on RSRP and network configuration. The transmission or retransmission of RACH preamble is based on SS blocks that meet the threshold. Fig.18 In the example of , because SS block m exceeds the threshold of received power, a RACH preamble is sent or resent based on SS block m.

[0201] Subsequently, when the UE receives a random access response on the DL-SCH, the DL-SCH may provide timing alignment information, RA preamble ID, initial uplink grant, and temporary C-RNTI.

[0202] Based on this information, the UE can perform uplink transmission of Msg3 of the random access procedure on the UL-SCH. Msg3 may include an RRC connection request and a UE identifier.

[0203] In response, the network may send Msg4 over the downlink which may be considered as a contention resolution message. Upon receiving this, the UE may enter the RRC connected state.

[0204] <Bandwidth Part (BWP)>

[0205] In the NR system, each component carrier (CC) can support a maximum value of 400MHz. If a UE operating in such a wideband CC operates with the RF for all turned-on CCs all the time, the UE battery consumption may increase. Additionally, considering the use cases (e.g., eMBB, URLLC, mMTC, etc.) operating in a wideband CC, different frequency bands in the CC may support different parameter sets (e.g., subcarrier spacing (SCS)). Additionally, the UE may have different capabilities for the maximum bandwidth. Taking this into account, the eNB may instruct the UE to operate only in a portion of the entire bandwidth of the wideband CC, and for convenience, the portion of the bandwidth is defined as a bandwidth part (BWP). The BWP may be composed of resource blocks (RBs) that are continuous on the frequency axis and may correspond to a parameter set (e.g., subcarrier spacing, cyclic prefix (CP) length, slot / mini-slot duration, etc.).

[0206] At the same time, even within one CC, the eNB can configure multiple BWPs for the UE. For example, a BWP occupying a relatively small frequency domain can be set in the PDCCH monitoring time slot, and the PDSCH indicated by the PDCCH can be scheduled on a BWP wider than the BWP. When the UE converges on a specific BWP, some UEs can be set to other BWPs for load balancing. Additionally, considering the frequency domain inter-cell interference elimination between adjacent cells, the BWPs on both sides of the bandwidth except for some spectrum at the center of the bandwidth can be configured in the same time slot. That is, the eNB can configure at least one DL / UL BWP for a UE associated with (= associated with) a wideband CC, and activate at least one of the DL / UL BWPs configured at a specific time (through L1 signaling or MAC CE or RRC signaling), and can indicate switching to other configured DL / UL BWPs (through L1 signaling or MAC CE or RRC signaling), or can switch to the determined DL / UL BWP when the timer value expires based on a timer. Here, the activated DL / UL BWP is defined as an active DL / UL BWP. However, when the UE is in the initial access procedure or the RRC connection is not established, the UE may not receive the configuration for the DL / UL BWP. In this case, the DL / UL BWP assumed by the UE is defined as the initially active DL / UL BWP.

[0207] <Discontinuous Reception (DRX)>

[0208] Discontinuous Reception (DRX) refers to an operation mode that enables UE to reduce battery consumption and discontinuously receive downlink channels. That is, a UE configured with DRX can discontinuously receive UL signals, thereby reducing power consumption.

[0209] The DRX operation is performed within a DRX cycle indicating a period of time of periodically repeated OnDuration. The DRX cycle includes OnDuration and SleepDuration (or an opportunity for DRX). The OnDuration indicates a period of time during which the UE monitors the PDCCH to receive the PDCCH.

[0210] DRX may be performed in a radio resource control (RRC)_idle state (or mode), an RRC_inactive state (or mode), or an RRC_connected state (or mode). In the RRC_idle state and the RRC_inactive state, DRX may be used to discontinuously receive a paging signal.

[0211] -RRC_IDLE state: a state in which no radio connection (RRC connection) is established between the base station and the UE.

[0212] -RRC_Inactive state: A state in which a radio connection (RRC connection) is established between a base station and a UE but the radio connection is deactivated.

[0213] -RRC_CONNECTED STATE: A state in which a radio connection (RRC connection) is established between a base station and a UE.

[0214] DRX can be basically divided into idle mode DRX, connected DRX (C-DRX) and extended DRX.

[0215] DRX applied in an idle state may be referred to as idle mode DRX, and DRX applied in a connected state may be referred to as connected mode DRX (C-DRX).

[0216] Extended / enhanced DRX (eDRX) is a mechanism that can extend the cycle of idle mode DRX and C-DRX, and can be mainly used for (large-scale) IoT applications. In idle mode DRX, whether eDRX is allowed can be configured based on system information (e.g., SIB1). SIB1 may include an eDRX allowed parameter. The eDRX allowed parameter is a parameter indicating whether idle mode extended DRX is allowed.

[0217] <IDLE MODE DRX>

[0218] In idle mode, the UE may use DRX to reduce power consumption. A paging occasion (PO) is a subframe in which a paging radio network temporary identifier (P-RNTI) may be sent over the physical downlink control channel (PDCCH), MTC PDCCH (MPDCCH), or narrowband PDCCH (NPDCCH) (addressing paging messages for NB-IoT).

[0219] In the P-RNTI sent over MPDCCH, the PO may indicate the starting subframe of the MPDCCH repetition. In the case of the P-RNTI sent over NPDCCH, when the subframe determined based on the PO is not a valid NB-IoT downlink subframe, the PO may indicate the starting subframe of the NPDCCH repetition. Therefore, the first valid NB-IoT downlink subframe after the PO is the starting subframe of the NPDCCH repetition.

[0220] A paging frame (PF) is a radio frame that can include one or more paging occasions. When using DRX, the UE only needs to monitor one PO for each DRX cycle. A paging narrowband (PNB) is a narrowband over which the UE receives paging messages. PF, PO and PNB can be determined based on DRX parameters provided via system information.

[0221] Fig.19is a flow chart illustrating an example of performing idle mode DRX operation.

[0222] refer to Fig.19 , the UE may receive idle mode DRX configuration information from the base station through higher layer signaling (eg, system information) (S21).

[0223] The UE may determine a paging frame (PF) and a paging occasion (PO) based on the idle mode DRX configuration information to monitor the PDCCH in the paging DRX cycle (S22). In this case, the DRX cycle may include an on duration and a sleep duration (or an opportunity for DRX).

[0224] The UE may monitor the PDCCH in the PO of the determined PF (S23). Here, for example, the UE monitors only one subframe (PO) for each paging DRX cycle. In addition, when the UE receives a PDCCH scrambled with the P-RNTI within the on-duration (i.e., when paging is detected), the UE may transition to a connected mode and may send and receive data to and from the base station.

[0225] <Connected Mode DRX (C-DRX)>

[0226] C-DRX refers to DRX applied in the RRC connected state. The DRX cycle of C-DRX may include a short DRX cycle and / or a long DRX cycle. Here, the short DRX cycle may be optional.

[0227] When C-DRX is configured, the UE may perform PDCCH monitoring during the on-duration. When the PDCCH is successfully detected during the PDCCH monitoring, the UE may operate (or run) the inactivity timer and may maintain the awake state. However, when the PDCCH is not successfully detected during the PDCCH monitoring, the UE may enter the sleep state after the on-duration expires.

[0228] When C-DRX is configured, the PDCCH reception timing (e.g., a time slot with a PDCCH search space) may be configured discontinuously based on the C-DRX configuration. However, when C-DRX is not configured, the PDCCH reception timing (e.g., a time slot with a PDCCH search space) may be configured continuously in the present disclosure.

[0229] On the other hand, PDCCH monitoring may be limited to a time period set as a measurement gap regardless of the C-DRX configuration.

[0230] Fig. 20 The diagram shows the DRX cycle.

[0231] refer to Fig. 20, the DRX cycle includes an "on duration" (hereinafter also referred to as "DRX on duration") and a "DRX opportunity". The DRX cycle defines a time interval in which the on duration is repeated periodically. The on duration indicates the duration for which the UE performs monitoring to receive the PDCCH. If DRX is configured, the UE performs PDCCH monitoring during the "on duration". If the PDCCH is successfully detected during the PDCCH monitoring, the UE runs an inactive timer and remains awake. On the other hand, if the PDCCH is not successfully detected during the PDCCH monitoring, the UE enters a sleep state after the "on duration" ends. Therefore, when DRX is configured, PDCCH monitoring / reception may be performed discontinuously in the time domain when performing the above / proposed process and / or method. For example, when DRX is configured, in the present disclosure, the PDCCH reception opportunity (e.g., a time slot with a PDCCH search space) may be configured discontinuously according to the DRX configuration. Otherwise, if DRX is not configured, PDCCH monitoring / reception may be performed continuously in the time domain when performing the above / proposed process and / or method. For example, when DRX is not configured, in the present disclosure, PDCCH reception opportunities (eg, time slots with PDCCH search spaces) may be continuously configured. Meanwhile, regardless of whether DRX is configured, PDCCH monitoring may be limited within the duration configured as a measurement gap.

[0232] Table 8 shows the UE process related to DRX (RRC_CONNECTED state). Referring to Table 8, DRX configuration information is received through higher layer (e.g., RRC) signaling, and whether DRX is turned on / off is controlled by the DRX command of the MAC layer. When DRX is configured, the UE may perform PDCCH monitoring discontinuously when performing the process and / or method described / proposed in the present disclosure.

[0233] [Table 8]

[0234]

[0235] MAC-CellGroupConfig may include configuration information required to configure media access control (MAC) parameters for a cell group. MAC-CellGroupConfig may also include configuration information about DRX. For example, MAC-CellGroupConfig may include the following information for defining DRX.

[0236] - Value of drx-OnDurationTimer: This defines the length of the start duration of the DRX cycle.

[0237] - Value of drx-InactivityTimer: This defines the length of the duration that the UE is in the awake state after detecting a PDCCH opportunity indicating a PDCCH for initial UL or DL ​​data.

[0238] - Value of drx-HARQ-RTT-TimerDL: This defines the length of the maximum duration after a DL initial transmission is received until a DL retransmission is received.

[0239] - Value of drx-HARQ-RTT-TimerUL: This defines the length of the maximum duration after receiving a grant for an UL initial transmission until receiving a grant for an UL retransmission.

[0240] -drx-LongCycleStartOffset: This defines the length and starting point of the DRX cycle

[0241] -drx-ShortCycle (optional): This defines the length of the short DRX cycle

[0242] Here, if any one of drx-OnDurationTimer, drx-InactivityTimer, drx-HARQ-RTT-TimerDL, and drx-HARQ-RTT-TimerUL is running, the UE performs PDCCH monitoring at each PDCCH opportunity while maintaining an awake state.

[0243] Hereinafter, an integrated access and backhaul link (IAB) will be described. Meanwhile, hereinafter, for the convenience of description, the proposed method will be described based on a new RAT (NR) system. However, the scope of the system to which the proposed method is applied can be extended to other systems besides the NR system, such as a 3GPP LTE / LTE-A system.

[0244] One of the potential technologies aimed at realizing future cellular network deployment scenarios and applications is the support for wireless backhaul and relay links, and enabling flexible and high-density deployment of NR cells without the need to densify the transmission network proportionally.

[0245] It is expected that, together with local deployment of massive MIMO or multi-beam systems, greater bandwidth will be available in NR compared to LTE (e.g., mmWave spectrum), thus creating opportunities for the development and deployment of integrated access and backhaul links. This facilitates dense networks of self-backhauled NR cells in a more integrated manner by establishing multiple control and data channels / procedures defined to provide access or access to UEs. Such systems are referred to as integrated access and backhaul links (IAB).

[0246] The following terms may be used in this disclosure.

[0247] - AC(x): Access link between node(x) and UE(s).

[0248] - BH(xy): backhaul link between node (x) and node (y).

[0249] In this case, the node may mean a donor gNB (DgNB) or a relay node (RN). Here, the DgNB or donor node may be a gNB that provides a function of supporting a backhaul to the IAB node.

[0250] In addition, in the present disclosure, for the sake of convenience of explanation, when relay node 1 and relay node 2 exist, relay node 1, which is connected to relay node 2 via a backhaul link and relays sent and received data to relay node 2, is called the parent node of relay node 2, and relay node 2 is called the child node of relay node 1.

[0251] The following figures are created to explain specific examples of this specification. Because the names of specific devices or the names of specific signals / messages / fields described in the figures are presented by way of example, the technical features of this specification are not limited to the specific names used in the following figures.

[0252] Fig.21 An example of a network with an integrated access and backhaul link (IAB) is schematically illustrated.

[0253] according to Fig.21 , a relay node (rTRP) can multiplex access and backhaul links in the time domain, frequency domain, or spatial domain (i.e., beam-based operation).

[0254] The operation of the different links can be on the same frequency or on different frequencies (also referred to as “in-band” or “out-of-band” relaying, respectively). While effective support for out-of-band relaying is important for some NR deployment scenarios, it is important to understand the requirements for in-band operation, which means close interworking with access links operating on the same frequency to accommodate duplex limitations and avoid / mitigate interference.

[0255] Additionally, operating NR systems in mmWave spectrum presents some unique challenges. It involves experiencing severe short-range blocking, which cannot be easily mitigated by current RRC-based switching mechanisms due to the larger time scale required to complete the process compared to short blocking. Overcoming short-range blocking in mmWave systems may require fast RAN-based mechanisms to switch between rTRPs, which does not necessarily need to involve the core network. The aforementioned need to mitigate short-range blocking for NR operation in mmWave spectrum, together with the need for easier deployment of self-backhauled NR cells, creates the need to develop an integrated framework that allows for fast switching of access and backhaul links. Over-the-air (OTA) coordination between rTRPs may also be considered to mitigate interference and support end-to-end path selection and optimization.

[0256] The following requirements and aspects should be addressed through the IAB for NR:

[0257] - Efficient and flexible operation of in-band and out-of-band relays in indoor and outdoor scenarios

[0258] -Multi-hop and redundant connections

[0259] - End-to-end path selection and optimization

[0260] -Supports backhaul links with high spectral efficiency

[0261] -Support for legacy NR UE

[0262] Legacy NR is designed to support half-duplex devices. Therefore, half-duplex can be supported in IAB scenarios and is worth targeting. In addition, IAB devices with full-duplex can also be considered.

[0263] Fig. 22 An example of the operation of the IAB system in standalone (SA) mode and non-standalone (NSA) mode is shown. Specifically, Fig. 22 (a) shows an example of the operation of the UE and IAB node considering NGC in SA mode, Fig. 22 (b) shows an example of the operation of the IAB node considering the NGC in SA mode and the UE considering the EPC in NSA mode, and Fig. 22 (c) shows an example of the operation of the UE and IAB node considering the EPC in the NSA mode.

[0264] The IAB node can operate in SA mode or NSA mode. When operating in NSA mode, the IAB node uses only NR links for backhaul. A UE connected to an IAB node can select an operating mode different from that of the IAB node. The UE may further be connected to a core network of a different type from the connected IAB node. In this case, (e) DECOR ((enhanced) dedicated core network) or slices may be used for CN selection. IAB nodes operating in NSA mode may be connected to the same or different eNBs. UEs operating in NSA mode may be connected to the same or different eNBs as the IAB nodes to which they are connected. Fig. 22 An example of considering NGC in SA mode and an example of considering EPC in NSA mode are shown.

[0265] In the IAB scenario, if each relay node (RN) does not have scheduling capability, the donor gNB (DgNB) will schedule the entire link between the DgNB, related relay nodes and the UE. That is, the DgNB should make scheduling decisions for all links by collecting service information from all related relay nodes, and then notify each relay node of the scheduling information.

[0266] On the other hand, when each relay node has scheduling capability, distributed scheduling can be performed. Then, immediate scheduling of uplink scheduling requests of UEs is possible, and the backhaul / access link can be used more flexibly by reflecting the surrounding traffic conditions.

[0267] Fig.23 Examples of configurations of access and backhaul links are schematically illustrated.

[0268] Fig.23 An example is shown in which a backhaul link and an access link are configured when there are DgNB and IAB relay nodes (RNs). RN(b) and RN(e) connect the backhaul link, RN(c) connects the backhaul link to RN(b), and RN(d) connects the backhaul link to RN(c).

[0269] refer to Fig.23 , DgNB receives not only the scheduling request of UE1, but also the scheduling requests of UE2 and UE3. Then, DgNB makes scheduling decisions for two backhaul links and three access links, and notifies the scheduling results. Therefore, this centralized scheduling involves scheduling delay and introduces latency problems.

[0270] On the other hand, if each relay node has scheduling capability, distributed scheduling can be performed. Then, immediate scheduling can be performed on the uplink scheduling request of the UE, and the backhaul / access link can be used more flexibly by reflecting the surrounding traffic conditions.

[0271] Fig.24 Used to explain the links and relationships between IAB nodes.

[0272] refer to Fig.24 , IAB node 1 is connected to IAB node 2 through backhaul link A. And, for backhaul link A, IAB node 1 is the parent node of IAB node 2, and IAB node 2 is the child node of IAB node 1. In addition, IAB node 2 is connected to IAB node 3 through backhaul link B. And, for backhaul link B, IAB node 2 is the parent node of IAB node 3, and IAB node 3 is the child node of IAB node 2.

[0273] Here, each IAB node can perform two functions. One is a mobile terminal (MT), which maintains a wireless backhaul connection to an upper IAB node or a donor node. And, the other is a DU (distributed unit), which provides an access connection with a UE or an MT connection with a lower IAB node.

[0274] For example, from the perspective of IAB node 2, the DU of IAB node 2 has a functional backhaul link B with the MT of IAB node 3. At the same time, the MT of IAB node 2 has a functional backhaul link A with the DU of IAB node 1. Here, the child link of the DU of IAB node 2 may refer to the backhaul link B between IAB node 2 and IAB node 3. In addition, here, the parent link of the MT of IAB node 2 may refer to the backhaul link A between IAB node 2 and IAB node 1.

[0275] Hereinafter, initial access of the IAB node will be described.

[0276] To initially establish a connection with a parent node or donor node, the IAB node may follow the same procedure as the UE's initial access procedure, including cell search, system information acquisition, and random access. SSB / CSI-RS-based RRM measurement is the starting point for IAB node discovery and measurement.

[0277] Methods to avoid SSB configuration conflicts between IAB nodes, inter-IAB node discovery procedures applying half-duplex restrictions and multi-hop topologies, including the feasibility of CSI-RS-based IAB node discovery, should be considered. Considering the cell ID used by a given IAB node, the following two cases can be considered.

[0278] - Case 1: Donor node and IAB node share the same cell ID

[0279] - Case 2: Donor node and IAB node maintain separate cell IDs

[0280] In addition, a mechanism for multiplexing RACH transmissions from UEs and RACH transmissions from IAB nodes should be further considered.

[0281] For standalone (SA) deployment, the initial IAB node discovery (Phase 1) by the MT follows the same initial access procedure as the UE, including cell search based on the same SSB available to the accessing UE, system information acquisition and random access to initially establish a connection with the parent IAB node or IAB donor.

[0282] In the case of NSA (non-standalone) deployment (from the perspective of the access / access UE), the IAB node MT follows the aforementioned phase 1 initial connection in SA deployment (from the perspective of the access UE) when performing the initial connection on the NR carrier. The SSB / RMSI period assumed by the MT for the initial connection may be longer than the 20ms assumed for Release 15 UEs of NR, and one of the candidate values ​​20ms, 40ms, 80ms and 160ms is selected.

[0283] Here, this means that the candidate parent IAB node / donor shall support NSA functionality for UEs and SA functionality for MTs on the NR carrier.

[0284] When an IAB node MT performs initial access on an LTE carrier, the Phase 2 solution can be used with parent selection of the IAB node by the MT on the NR carrier.

[0285] Hereinafter, backhaul link measurement will be described.

[0286] Measurements on multiple backhaul links for link management and path selection should be considered. In order to support half-duplex restrictions in terms of a given IAB node, the IAB supports detection and measurement of candidate backhaul links (after initial connection) using resources orthogonal to those used by accessing UEs for cell detection and measurement. In this regard, the following can be further considered.

[0287] - TDM of multiple SSBs (e.g., possibly following hop order, cell ID, etc.)

[0288] -SSB muting across IAB nodes

[0289] -SSB multiplexing for accessing UE and IAB nodes within or across half-frames

[0290] - Additional IAB node discovery signals (e.g., CSI-RS) to be TDMed with SSB transmissions

[0291] -Use non-raster SSB

[0292] - The transmission period for backhaul link detection and measurement is different compared to the period used by access UEs

[0293] Coordination mechanisms for different solutions should be further considered, including coordination mechanisms for IAB nodes for measurement times and reference signal (RS) transmission.

[0294] Improvements to SMTC and CSI-RS configurations may be considered to support RRM measurements for IAB nodes.

[0295] For the purpose of backhaul link RSRP / RSRQ RRM measurements, IAB supports both SSB-based and CSI-RS-based solutions.

[0296] After the IAB node DU is activated, the IAB inter-node discovery process needs to take into account the half-duplex limitation and multi-hop topology for the IAB nodes for inter-IAB node and donor detection (Phase 2). The following solutions are supported: SSB-based solution - uses SSB (TDM and / or FDM) that is orthogonal to the SSB used to access the UE.

[0297] Hereinafter, backhaul link management will be described.

[0298] IAB nodes support mechanisms for detecting / recovering from backhaul link failures. Enhancements to Beam Failure Recovery (BFR) and Radio Link Failure (RLF) procedures are advantageous and should be supported for NR IAB as follows.

[0299] - Improved support for interaction between beam failure recovery success indication and RLF.

[0300] - Improvements to the current beam management process for IAB nodes should be considered to speed up beam switching / coordination / recovery to avoid backhaul link disruptions.

[0301] Further, for example, when the backhaul link of the parent IAB node fails, etc., the need for an additional backhaul link status notification mechanism from the parent IAB node to the child IAB node, and the need for the corresponding IAB node operation are discussed. Solutions for avoiding RLF in the child IAB node due to the parent backhaul link failure should be supported.

[0302] Hereinafter, a mechanism for changing a path or transmission / reception in a plurality of backhaul links will be described.

[0303] Mechanisms for efficient rerouting or transmission / reception in multiple backhaul links simultaneously (e.g., multi-TRP (Tx / Rx point) operation and intra-frequency dual connectivity) should be considered.

[0304] Hereinafter, scheduling of backhaul and access links will be described.

[0305] Downlink IAB node transmissions (i.e., transmissions from an IAB node to child IAB nodes served by the IAB node on the backhaul link and transmissions from an IAB node to UEs served by the IAB node on the access link) will be scheduled by the IAB node itself. Uplink IAB transmissions (transmissions from an IAB node to its parent or donor node on the backhaul link) will be scheduled by the parent or donor node.

[0306] The following describes the multiplexing of access and backhaul links.

[0307] According to the half-duplex limitation, IAB supports TDM, FDM and SDM between access and backhaul links at the IAB node. Mechanisms for efficient TDM / FDM (frequency division multiplexing) / SDM (space division multiplexing) multiplexing of access / backhaul services across multiple hops taking into account the half-duplex limitation of the IAB node should be considered. The following solutions for different multiplexing options can be further considered.

[0308] - A mechanism for orthogonal partitioning of time slots or frequency resources between access and backhaul links across one or more hops

[0309] - Utilize different DL / UL timeslot settings for access and backhaul links

[0310] -DL and UL power control enhancements and timing requirements to allow intra-panel FDM and SDM for backhaul and access links

[0311] -Interference management including cross-link interference

[0312] Hereinafter, resource coordination will be described.

[0313] Mechanisms for scheduling coordination, resource allocation and path selection across IAB nodes / donor nodes and multiple backhaul hops should be considered. Resource coordination (frequency, time in terms of slots / slot formats, etc.) between semi-static IAB nodes (on the time scale of RRC signaling) should be supported. The following aspects can be further considered.

[0314] - Distributed or centralized coordination mechanism

[0315] - Resource granularity of the desired signal (e.g., TDD configuration pattern)

[0316] - Exchange L1 (layer-1) and / or L3 (layer-3) measurements between IAB nodes

[0317] - Exchange of topology-related information (e.g., hop order) that affects the physical layer design of the backhaul link

[0318] - Faster coordination of resources (frequency, time in terms of slots / slot formats, etc.) than semi-static coordination

[0319] Hereinafter, IAB node synchronization and timing alignment will be described.

[0320] The feasibility of over-the-air (OTA) synchronization and the impact of timing misalignment on IAB performance (e.g., the number of hops that can be supported) should be considered. Assuming that the timing requirement at the IAB nodes in overlapping coverage is 3us or less, TA-based OTA synchronization can support multi-hop IAB networks (up to 5 hops) for FR 2. TA-based OTA synchronization may not be sufficient to support multi-hop in FR1.

[0321] The next level of alignment between IAB nodes / IAB donors or within an IAB node is discussed.

[0322] -Slot level alignment

[0323] -Symbol-level alignment

[0324] - Misalignment

[0325] Mechanisms for timing alignment in multi-hop IAB networks are discussed. IAB supports TA-based synchronization between IAB nodes including multiple backhaul hops. Improvements to existing timing alignment mechanisms are discussed, including TAs required for IAB nodes to support different transmission timing alignment scenarios.

[0326] The following transmission timing alignment cases across IAB nodes and IAB donors are discussed.

[0327] - Case 1: DL transmission timing alignment across IAB nodes and IAB donors: If downlink transmission and uplink reception at the parent node are not well aligned, the child node needs additional information about the alignment to correctly set its downlink transmission timing for OTA based timing and synchronization.

[0328] - Case 2: Aligning downlink and uplink transmission timing for one IAB node.

[0329] - Case 3: Aligning downlink and uplink reception timing for one IAB node.

[0330] - Case 4: For an IAB node, when receiving using case 3 while transmitting using case 2.

[0331] - Case 5: Case 4 for backhaul link timing and Case 1 for access link timing for one IAB node in different time slots.

[0332] - Case 6: The sum of the downlink transmission timing of Case 1 and the uplink transmission timing of Case 2: The downlink transmission timing of all IAB nodes is aligned with the downlink timing of the parent IAB node or the donor; the uplink transmission timing of the IAB node can be aligned with the downlink transmission timing of the IAB node.

[0333] -Case 7: The sum of the downlink transmission timing of Case 1 and the uplink reception timing of Case 3: The downlink transmission timing of all IAB nodes is aligned with the downlink timing of the parent IAB node or the donor; the uplink reception timing of the IAB node can be aligned with the downlink reception timing of the IAB node; if the downlink transmission and uplink reception in the parent node are not well aligned, the child node needs additional information about the alignment to correctly set its downlink transmission timing for OTA-based timing and synchronization.

[0334] The impact of different situations on TDM / FDM / SDM multiplexing of parent and child links, the potential impact of incomplete timing adjustment, the overhead of the required downlink / uplink switching gaps, cross-link interference, the feasibility when an IAB node is connected to one or more parent nodes, and the impact on access UEs (especially compatibility with Release 15 UEs) are discussed.

[0335] For both access and backhaul link transmission timing alignment, case 1 is supported.

[0336] For IAB, cases 2 to 5 are not supported.

[0337] The use of case 6 for IAB nodes, if supported, should be under the control of the parent node or network.In order to align downlink transmissions between IAB nodes, the following examples of solutions have been identified.

[0338] - Alternative 1: The IAB node may have to perform parallel (always time division multiplexed) case 1 and case 6 uplink transmissions.

[0339] -Alternative 2: Signaling between the parent node and the IAB node for the time difference of the downlink transmission and uplink reception timing at the parent node to correct the potential misalignment of the downlink transmission timing at the child node: the child IAB node compares the corresponding differences of its downlink transmission timing and the backhaul reception timing; if the difference signaled by the parent node is larger than the difference measured by the child node, the child node advances its transmission timing if the transmission timing is smaller.

[0340] Here, Alternative 1 and Alternative 2 may have to maintain separate receive timing in the parent node for case 6 uplink transmissions from other child nodes.

[0341] In case 7, by introducing TDM between child IAB nodes / Release 16 UEs supporting valid negative TA and new TA values ​​and child IAB nodes / UEs not supporting new TA values, it is compatible for Release 15 UEs. To achieve alignment between downlink and uplink within an IAB node, the following examples of solutions are identified.

[0342] -Alternative 1: Introduce negative initial time alignment (TA) to be applied to the child nodes of the IAB node applying case 7 timing.

[0343] -Alternative 2: In the IAB node, positive TA is applied, which implements symbol alignment instead of time slot alignment between downlink reception and uplink reception.

[0344] - Alternative 3: Signalling of a relative offset of the most recent TA value to be applied to the child nodes of the IAB node clocked by case 7 to achieve efficient negative TA.

[0345] - In addition to OTA synchronization, other technologies such as GNSS and PTP can also be used to obtain synchronization between IAB nodes.

[0346] In the following, cross-link interference measurement and management will be described.

[0347] The impact of cross-link interference (CLI) on access and backhaul links (including across multiple hops) will be considered. In addition, interference measurement and management solutions should be considered.

[0348] In the following, CLI mitigation techniques will be described.

[0349] CLI mitigation techniques including advanced receiver and transmitter coordination should be considered and prioritized in terms of complexity and performance. CLI mitigation techniques should be able to manage the following IAB-to-node interference scenarios.

[0350] - Case 1: The victim IAB node receives in the downlink through its MT, and the interfering IAB node transmits in the uplink through its MT.

[0351] - Case 2: The victim IAB node receives in downlink through its MT, and the interfering IAB node transmits in downlink through its DU.

[0352] - Case 3: The victim IAB node receives in uplink through its DU, and the interfering IAB node transmits in uplink through its MT.

[0353] - Case 4: The victim IAB node receives in uplink through its DU, and the interfering IAB node transmits in downlink through its DU.

[0354] Given FDM / SDM reception between access and backhaul links at an IAB node, the interference experienced at the IAB node should be further considered.

[0355] Hereinafter, spectrum efficiency enhancement will be described.

[0356] Support for 1024 Quadrature Amplitude Modulation (QAM) for the backhaul link should be considered.

[0357] Hereinafter, DAPS-HO (Dual Active Protocol Stack-based Handover) will be described.

[0358] From the perspective of UE functions, DAPS generally has the following characteristics:

[0359] 1)Transmission operation:

[0360] - Public SN

[0361] - Separate header compression for source and target cells

[0362] - Separate encryption for source and target cells

[0363] 2) Receiving operation:

[0364] - Separate decryption of source and target cells

[0365] - Separate header decompression for source and target cells

[0366] - Common PDCP reordering

[0367] - Sequential delivery and duplicate detection

[0368] - Common buffer management

[0369] Typically, the network side and the UE have common transmission and reception processes and functions. The only difference is whether these functions are co-located. On the network side, all functions except DL PDCP SN allocation and UL PDCP reordering do not co-exist and are performed separately by the source eNB or the target eNB. Therefore, it is assumed that the two PDCP entities are located in the source eNB and the target eNB respectively.

[0370] On the UE side, all functions including SN allocation and PDCP reordering are co-located. Therefore, all functions of DAPS can be modeled as a single PDCP entity on the UE side. For a single UL data transmission, only header compression and security processing of the source eNB or target eNB are used.

[0371] Hereinafter, RF / baseband requirements of UE for DAPS-HO will be described.

[0372] To minimize the interruption, whether it is SAPS or DAPS, the UE needs to continue to send / receive data with the source cell when performing a random access procedure to the target cell. This is only possible if the UE supports simultaneous transmission / reception for two cells. According to the RAN4 response LS, in most cases, it works for UEs with dual Rx / dual Tx chains, and more restrictions should be imposed on UEs with dual Rx / single Tx RF chains or with single Rx / single Tx RF chains. In addition, in order to effectively use baseband and RF resources, there is also a request for UE capability segmentation. For SAPS, UE baseband and RF resource tuning is not very simple, resulting in additional interruption and complexity for the UE.

[0373] For UEs with dual Rx / single Tx RF chains, in order to simultaneously support uplink data transmission to the source eNB and uplink RACH to the target eNB, if some requirements can be met, for example, if the bandwidth of the source cell is larger than the bandwidth of the target cell, if the transmit power difference between the two cells is within certain limits, simultaneous transmission can still be supported. Otherwise, some kind of uplink TDM pattern is required, which will add additional downtime and complexity to the uplink switching. However, this UE option provides flexibility for various UE implementation types in terms of hardware and power efficiency (in particular, UEs where low-layer devices, uplink CA and / or uplink MIMO are not possible). From a standard perspective, these types of UEs should at least be supported as another option.

[0374] For UEs with a single Rx / single Tx RF chain, simultaneous transmission / reception can still be supported if some requirements can be met, for example, if the bandwidth of the source cell is larger than the bandwidth of the target cell and the transmit / receive power difference of the two cells is within a certain limit. Otherwise, TDM design is required for both downlink and uplink, which adds additional complexity to both the UE and network side. In addition, RF link switching is required for both downlink and uplink, which increases HO downtime and switching complexity.

[0375] In general, solutions should be designed for all types of UE capabilities rather than limiting the solution to just one type of capability. Therefore, solutions that support both Dual Rx / Dual Tx as a baseline and Dual Rx / Single Tx and Single Rx / Single Tx as alternative options should be considered.

[0376] If the UE indicates DAPS-HO capability, the source Master Cell Group (MCG) and the target MCG may be provided to the UE.

[0377] If a primary cell group (MCG) and a secondary cell group (SCG) using NR radio access in FR1 and / or FR2 are configured for a UE, the UE is configured with a maximum power P for transmission on the MCG via p-DAPS-FR1 and / or p-DAPS-FR2. MCG , is configured with a maximum power P for transmission over the SCG via p-DAPS-FR1 and / or p-DAPS-FR2 SCG The inter-CG power sharing mode is set by UplinkPowerSharingDAPS-HO-mode of FR1 and / or UplinkPowerSharingDAPS-HO-mode of FR2. The UE determines the transmission power on the MCG and the transmission power on the SCG for each frequency range.

[0378] If the UE indicates UplinkPowerSharingDAPS-HO=Semistatic-mode1 and if UplinkPowerSharingDAPS-HO-mode=Semi-static-mode1 is provided, the UE regards the target MCG as the MCG and the source MCG as the SCG to determine the transmission power for the target MCG or the source MCG for UplinkPowerSharingDAPS-HO=Semi-static-mode1.

[0379] If the UE indicates UplinkPowerSharingDAPS-HO=Semistatic-mode2 and is provided with UplinkPowerSharingDAPS-HO-mode=Semi-static-mode2, the UE regards the target MCG as the MCG and the source MCG as the SCG to determine the transmission power for the target MCG or the source MCG for UplinkPowerSharingDAPS-HO=Semi-static-mode2.

[0380] If the UE indicates UplinkPowerSharingDAPS-HO=Dynamic and is provided with UplinkPowerSharingDAPS-HO-mode=Dynamic, the UE regards the target MCG as the MCG and the source MCG as the SCG to determine the transmission power for the target MCG or the source MCG for UplinkPowerSharingDAPS-HO=Dynamic.

[0381] If UplinkPowerSharingDAPS-HO is not provided for the UE and the UE transmissions on the target cell and the source cell overlap, the UE transmits only on the target cell.

[0382] If the carrier frequencies used for the target MCG and the source MCG are intra-frequency and intra-band when UE transmissions on the target cell and the source cell overlap in time resources, if the carrier frequencies of the target MCG and the source MCG are not within the frequency (intra-frequency) but within the frequency band (intra-band) when UE transmissions on the target cell and the source cell overlap in time resources and frequency resources, the UE transmissions on the target cell and the source cell overlap.

[0383] For intra-frequency DAPS-HO operation, the UE expects the active downlink BWP and active uplink BWP on the target cell to be within the active downlink BWP and active uplink BWP on the source cell, respectively.

[0384] The UE may provide pdcch-BlindDetectionMCG1-UE to indicate the monitoring of N with the target MCG. target cells The maximum number of PDCCH candidates per time slot corresponding to the downlink cells can be set, and pdcch-BlindDetectionMCG2-UE can be provided to indicate monitoring of N source cells If a UE is provided with a search space set for both a target MCG and a source MCG, the UE is not expected to have a USS set in any time slot that does not have a PDCCH candidate assigned for monitoring both the target MCG and the source MCG.

[0385] Hereinafter, the proposals of the present disclosure will be described in more detail.

[0386] The following figures are created to illustrate specific examples of this specification. Since the names of specific devices or the names of specific signals / messages / fields described in the figures are presented by example, the technical features of this specification are not limited to the specific names used in the following figures. In addition, the methods / configurations proposed in this specification can be combined in various ways.

[0387] The existing IAB node performs TDM operation, in which the IAB node DU and the IAB node MT operate through different time resources. On the other hand, it may be necessary to perform resource multiplexing between the IAB node DU and the IAB node MT, such as SDM / FDM and full duplex (FD), for efficient resource management. Fig.24As shown in, the link between IAB node 2 (MT of IAB node 2) and the parent node of IAB node 2 (DU of IAB node 1) is called a parent link, and the link between IAB node 2 (DU of IAB node 2) and the child node of IAB node 2 (MT of IAB node 3) can be called a child link. At this time, in addition to the TDM operation between the parent link and the child link, SDM / FDM and FD operations are also discussed.

[0388] refer to Figure 25 to Figure 27 , the following three examples of alignment of transmission / reception timing of IAB nodes that can be considered in an IAB environment will be described. Fig.25 Showing timing alignment case 1, Fig.26 Showing the timing alignment case 6, Fig. 27 Timing alignment case 7 is shown.

[0389] - Timing alignment case 1: DL transmission timing alignment across IAB nodes and IAB donors This is a method in which downlink transmission timing of DUs between IAB nodes is aligned.

[0390] Referring to timing alignment case 1, if downlink transmission and uplink reception are not well aligned in the parent node, the child node needs additional information about the alignment to properly set its downlink transmission timing for OTA-based timing and synchronization. The MT transmission timing can be expressed as (MT reception timing - TA (timing advance)), and the DU transmission timing can be expressed as (MT reception timing - TA / 2 - T Δ ). Here, T can be obtained from the parent node Δ value.

[0391] - Timing alignment case 6: DL transmission timing for all IAB nodes is aligned with the DL timing of the parent IAB node or donor. The UL transmission timing of the IAB node may be aligned with the DL transmission timing of the IAB node.

[0392] Referring to timing alignment case 6, the uplink transmission timing of the MT for the IAB node and the downlink transmission timing of the DU for the IAB node are aligned. Since the uplink transmission timing of the MT of the IAB node is fixed, the uplink reception timing of the DU of the parent node receiving this is delayed by the propagation delay between the DU of the parent node and the MT of the IAB node compared to the uplink transmission timing of the MT of the IAB node. If the IAB node uses timing alignment case 6, since the uplink reception timing of the parent node is different from the existing uplink reception timing, if the IAB node wants to use timing alignment case 6, the parent node also needs to know this information.

[0393] - Timing alignment case 7: The downlink transmission timing of all IAB nodes is aligned with the downlink timing of the parent IAB node or the donor. The uplink reception timing of the IAB node can be aligned with the downlink reception timing of the IAB node.

[0394] Referring to timing alignment case 7, if the downlink transmission and uplink reception are not well aligned in the parent node, additional information about the alignment is required in order to properly configure the child node for its own downlink transmission timing for OTA-based timing and synchronization. This is a scheme in which the MT downlink reception timing of the IAB node and the DU uplink reception timing of the IAB node are aligned. From the MT perspective, the send / receive timing is the same as the send / receive timing of the existing IAB node or the version 16 IAB node, and the uplink reception timing of the DU of the IAB node can be aligned with the downlink reception timing of the MT of the IAB node. The IAB node can adjust the TA of the MT of the child node so that the MT of the child node sends an uplink signal according to its uplink reception timing. Therefore, when compared with timing alignment case 1, this timing alignment method may not reveal the differences in the operation of the IAB node according to the specification. Therefore, the timing alignment case 7 described in this article can be replaced / interpreted as timing alignment case 1.

[0395] Meanwhile, in this specification, timing alignment may mean slot unit alignment or symbol unit alignment.

[0396] Due to reasons such as intra-node interference, slot / symbol boundary misalignment, and power sharing, the IAB node DU and IAB node MT existing in the same IAB node or being co-located cannot operate simultaneously and cannot operate through TDM.

[0397] On the other hand, multiplexing of SDM / FDM can be used between the DU of the IAB node and the MT of the IAB node. This is applicable, for example, when the DU of the IAB node and the MT of the IAB node use different panels, so the interference between the panels is small. In this case, the DU of the IAB node and the MT of the IAB node that exist or coexist in the same IAB node can transmit or receive at the same time, and it is impossible for the DU of the IAB node and the MT of the IAB node to perform transmission and reception or reception and transmission at the same time, respectively.

[0398] Alternatively, full duplex (FD) may be used between the DU of the IAB node and the MT of the IAB node. For example, this is when there is little interference influence between the DU of the IAB node and the MT of the IAB node, such as when the frequency domain in which the DU of the IAB node operates and the frequency domain in which the MT of the IAB node operates are far apart. In this case, the DU of the IAB node and the MT of the IAB node that exist or coexist in the same IAB node can freely transmit and receive at the same time. The DU of the IAB node and the MT of the IAB node can transmit or receive at the same time, and it is also possible that the DU of the IAB node and the MT of the IAB node respectively perform transmission and reception or reception and transmission at the same time.

[0399] Fig.28 An example is illustrated in which a plurality of component carriers are configured for an IAB node.

[0400] The MT of the IAB node and the DU of the IAB node may consist of multiple component carriers (CCs). In this case, different CCs may operate in the same or different frequency regions, or may use the same or different panels. For example, Fig.28 As shown in , there may be three CCs for each MT and DU in the IAB node. Fig.28 In the example, the three CCs existing for the MT of the IAB node may be named MT-CC1, MT-CC2, and MT-CC3, respectively. In the case of DU, CC may be replaced by cell and may be called DU-cell1, DU-cell2, and DU-cell3.

[0401] In this case, one of TDM, SDM / FDM, and FD may be applied between a specific CC of the IAB node MT and a specific cell of the DU of the IAB node. For example, when a specific MT-CC and a DU-cell are located in different inter-band frequency regions, FD may be applied between the corresponding MT-CC and DU-cell. On the other hand, the TDM scheme may be applied between an MT-CC and a DU-CC located in the same frequency domain. Fig.28 In the embodiment, MT-CC1, MT-CC2, DU-cell 1 and DU-cell 2 use f1 as the center frequency, MT-CC3 and DU-cell 3 use f2 as the center frequency, and f1 and f2 can be located in an inter-band relationship with each other. In this case, from the standpoint of MT-CC1 or MT-CC2, it operates with DU-cell 1 and DU-cell 2 in TDM, but operates with DU-cell 3 in FD. On the other hand, from the standpoint of MT-CC3, it operates with DU-cell 1 and DU-cell 2 in FD, but can operate with DU-cell 3 in TDM.

[0402] On the other hand, different multiplexing schemes between MT and DU can be applied even within the same CC. For example, multiple parts may exist in MT-CC and / or DU-cell. For example, such a part may mean a link transmitted through an antenna having the same center frequency but different physical positions or different panels. Alternatively, for example, the part may mean a link having the same center frequency but transmitted through different bandwidth parts (BWP). In this case, for example, when there are two parts in DU-cell 1, the multiplexing type operating with a specific MT-CC or a specific part within a specific MT-CC may be different for each part. The case where the multiplexing type of each pair of cells of the CC of the MT of the IAB node and the DU of the IAB node may be different will be described later. However, it can also be extended to and applied to the case where the MT of the IAB node and the DU of the IAB node are divided into multiple parts, and the multiplexing type of the CC and part of the MT of each pair of IAB nodes and the cell and part of the DU of the IAB node may be different.

[0403] It can be considered that one IAB node is connected to two or more parent nodes. In this case, the MT of the IAB node can be connected to the DUs of two parent nodes using a dual connectivity (DC) method. The IAB node may have redundant routes to the IAB donor centralized unit (CU). For IAB nodes operating in SA mode, NR DC can be used to enable routing redundancy in the BH by allowing the IAB-MT to have concurrent backhaul (BH) radio link control (RLC) channels with two parent nodes. The parent node may need to be connected to the same IAB donor CU-CP (control plane), which controls the establishment and release of redundant routes through two parent nodes. Together with the IAB-donor CU, the parent node can acquire the roles of the master node and auxiliary node of the IAB-MT. The NR DC framework (e.g., MCG / SCG related processes) can be used to establish a dual radio link with the parent node.

[0404] As one of the methods in which the IAB MT is connected to the DUs of two parent nodes, the following scenario may be considered.

[0405] - Scenario 1: Multiple parent DU connections using different MT-CCs with adjacent carrier frequencies Fig.29 An example of scenario 1 is schematically shown.

[0406] The MT of the IAB node can use different MT-CCs to establish connections with DUs of multiple parent nodes (hereinafter referred to as parent DUs). That is, one MT-CC establishes a connection with one parent DU-cell, and the corresponding parent DU-cells may exist in different parent DUs. Fig.29As shown in , MT-CC1 and MT-CC2 exist in the MT of the IAB node, MT-CC1 is connected to DU-cell 1 in the parent DU1, and MT-CC2 can be connected to DU-cell 4 in the parent DU2. In this case, from the perspective of the MT of the IAB node, the link between one MT-CC and one DU-cell can be called a parent link. In this case, the link between MT-CC1 and DU-cell 1 and the link between MT-CC2 and DU-cell 4 become different parent links.

[0407] In this way, in order to establish connections with DU-cells in different parent DUs using different MT-CCs, the existing DC method can be used. In this case, when the MT of the IAB node is connected to two parent DU-cells using different MT-CCs, one parent DU-cell may belong to the MCG and the other parent DU-cell may belong to the SCG.

[0408] It can be assumed that each MT-CC of the MT of the IAB node has an independent RF chain. Therefore, each MT-CC can perform transmission / reception operations independently and simultaneously. Each MT-CC can set and manage transmission / reception timing based on the parent DU-cell connected to it.

[0409] In scenario 1, consider that the MT-CCs connected to different parent DUs in the above scenario operate on different carrier frequencies. Fig.29 In the example, the link between MT-CC1 and DU-cell 1 and the link between MT-CC2 and DU-cell 4 may have different carrier frequencies. Fig.29 In the example, the link between MT-CC1 and DU-cell 1 has a carrier frequency of f1, while the link between MT-CC2 and DU-cell 4 has a carrier frequency of f3. In this case, the carrier frequency regions operating between the two parent links may be adjacent. In this case, cross-link interference may occur when the parent links operate in different downlink / uplink directions. In this scenario, the adjacent carrier frequency regions between the two parent links may cause cross-link interference to the extent that it affects performance.

[0410] - Scenario 2: Multiple parent DU connections using different MT-CCs with the same carrier frequency Fig.30 An example of scenario 2 is shown.

[0411] The MT of the IAB node can use different MT-CCs to establish connections with multiple parent DUs. That is, one MT-CC establishes a connection with one parent DU-cell, and the corresponding parent DU-cells may exist in different parent DUs. Fig.30In the example, MT-CC1 and MT-CC2 exist in the MT of the IAB node, MT-CC1 is connected to DU-cell 1 in the parent DU1, and MT-CC2 can be connected to DU-cell 3 in the parent DU2. In this case, from the perspective of the MT of the IAB node, the link between one MT-CC and one DU-cell can be called a parent link. In this case, the link between MT-CC1 and DU-cell 1 and the link between MT-CC2 and DU-cell 3 become different parent links.

[0412] In this way, in order to establish connections with DU-cells in different parent DUs using different MT-CCs, the existing DC method can be used. In this case, when the MT of the IAB node is connected to two parent DU-cells through different MT-CCs, one parent DU-cell may belong to the MCG and the other parent DU-cell may belong to the SCG.

[0413] It can be assumed that each MT-CC of the MT of the IAB node has an independent RF chain. Therefore, each MT-CC can perform transmission / reception operations independently and simultaneously. Each MT-CC can set and manage transmission / reception timing based on the parent DU-cell connected to it.

[0414] In the situation described in Scenario 2 above, consider that MT-CCs connected to different parent DUs operate on the same carrier frequency. Fig.30 In the example, consider the case where the links between MT-CC1 and DU-cell 1 and between MT-CC2 and DU-cell 3 have the same carrier frequency. That is, in this scenario, it means that different MT-CCs in the MT of the IAB node can operate on the same carrier frequency, and it means that multiple MT-CCs can exist in the same frequency region. Fig.30 , the link between MT-CC1 and DU-cell 1 has a carrier frequency of f1, and the link between MT-CC2 and DU-cell 3 also has a carrier frequency of f1. In this case, cross-link interference may occur when the parent links operate in different downlink / uplink directions. In addition, interference may occur when the resources used to send actual downlink signals / channels to two MT-CCs overlap each other. Even in the case of uplink, when the uplink signals / channels sent by two MT-CCs overlap, the uplink signals / channels sent to a specific parent DU may act as interference to other parent DUs.

[0415] - Scenario 3: Connecting multiple parent DUs using a single MT-CC

[0416] Fig.31 An example of scenario 3 is shown.

[0417] The MT of the IAB node can use one MT-CC to establish connections with multiple parent DUs. That is, one MT-CC can establish connections with multiple parent DU-cells, and the corresponding parent DU-cells can exist in different parent DUs. Fig.31 In the example, MT-CC1 exists in the MT of the IAB node, and MT-CC1 can be connected to DU-cell 1 in the parent DU1 and DU-cell 4 in the parent DU2. In this case, from the perspective of the MT of the IAB node, the link between one MT-CC and one DU-cell can be called a parent link. In this case, the link between MT-CC1 and DU-cell 1 and the link between MT-CC1 and DU-cell 4 become different parent links. Fig.31 In the example, the link between MT-CC1 and DU-cell 1 has a carrier frequency of f1, and the link between MT-CC1 and DU-cell 3 also has a carrier frequency of f1.

[0418] - Scenario 3-1: Multiple parent DU connections with multiple RF modules

[0419] One MT-CC in the MT of the IAB node can have multiple RF chains. That is, one MT-CC is able to support different parent DUs on the same carrier frequency by using two RF modules. In this case, the MT-CC is one, but by supporting independent RF modules, it is possible to establish connections with multiple parent DUs at the same time. Therefore, the MT-CC can perform transmit / receive operations independently and simultaneously for multiple parent DUs. Each RF module of the MT-CC is capable of setting and managing transmit / receive timing based on the parent DU-cell connected to it. In this case, cross-link interference may occur when the parent link operates in different downlink / uplink directions. In addition, interference may occur when the resources used to send actual downlink signals / channels through two parent links overlap with each other. Even in the case of the uplink, when the uplink signals / channels sent through the two parent links overlap, the uplink signals / channels sent to a specific parent DU may also act as interference to other parent DUs.

[0420] - Scenario 3-2: Multiple Parent DUs connected with a single RF module

[0421] One MT-CC in the MT of the IAB node may have one RF chain. Therefore, the MT-CC may not be able to simultaneously transmit / receive through two parent links operating at different transmit / receive timings. In addition, simultaneous transmission and reception cannot be performed through two parent links operating in different analog beam directions. Therefore, the MT-CC must use different time resources to perform operations on different parent links. In this case, the MT-CC needs to independently set and manage the transmit / receive timing for each parent DU connected to it.

[0422] -Scenario 4: DAPS-HO (handover based on dual-active protocol stack)

[0423] DAPS HO is introduced to enhance the mobility of UE. This DAPS HO can also be applied to the MT of the IAB node. When DAPS HO is applied, when the MCG to which the UE is currently connected is called the source MCG and the MCG to be switched is called the target MCG, the UE can be connected to the source MCG and the target MCG at the same time using the same carrier frequency. The DAPS HO scheme can be used when the MT of the IAB node establishes connections with multiple parent DUs using the same carrier frequency. In this case, one parent DU can be the source MCG and the other parent DU can be the target MCG to establish connections to the two parent DUs.

[0424] The contents proposed in this specification are based on operating with two parent DUs set as MCG and SCG respectively. However, it can include operating as DAPS HO, where MCG and SCG act as source MCG and target MCG (or target MCG and source MCG), respectively. In this case, the MCG and SCG mentioned in this specification can be interpreted by replacing them with source MCG and target MCG (or target MCG and source MCG), respectively.

[0425] The contents proposed in this specification describe the contents assuming an in-band environment, but can also be applied in an out-of-band environment. In addition, the contents proposed in this specification are described considering an environment in which a donor gNB (donor gNB: DgNB), a relay node (RN), and a UE perform half-duplex operation, and it can even be applied in an environment in which the DgNB, RN, and / or UE perform full-duplex operation.

[0426] In this specification, the case where MTs of the same IAB node are connected to different parent nodes is considered. Considering the cases such as the above scenarios 1, 2, 3, and 4, one MT-CC in the MTs of the IAB node is connected to a specific DU-cell in two different parent nodes, or different MT-CCs in the MTs of the IAB node may be connected to specific DU-cells in two different parent nodes, respectively. In this case, one parent node may mean one carrier group (CG).

[0427] Fig.32 and Fig.33 An example is shown in which a plurality of parent nodes are connected to one IAB node.

[0428] In combination with these scenarios, this manual considers Fig.32 and 33 The situation shown in . The IAB node is simultaneously connected to the parent DU-cell 1 present in the parent node 1 and the parent DU-cell 2 present in the parent node 2. In this case, the link between the IAB node and the parent DU-cell 1 is called the parent link 1, and the link between the IAB node and the parent DU-cell 2 is called the parent link 2. The parent link 1 and the parent link 2 can operate through frequency resources having an intra-frequency relationship. That is, the parent DU-cell 1 and the parent DU-cell 2 can operate through frequency resources having an intra-frequency relationship. At this time, from the perspective of the IAB node, the parent link 1 and the parent link 2 can be connected through different MT-CCs, such as Fig.32 That is, the link with parent DU-cell 1 can be connected through MT-CC1, and the link with parent DU-cell 2 can be connected through MT-CC2. Alternatively, parent link 1 and parent link 2 can be connected through the same MT-CC, such as Fig.33 That is, both parent DU-cell 1 and parent DU-cell 2 can be connected through MT-CC1.

[0429] In this case, depending on the situation, the IAB node may simultaneously or non-simultaneously perform reception through the parent link 1 and reception through the parent link 2. The IAB node may also simultaneously or non-simultaneously perform transmission through the parent link 1 and transmission through the parent link 2 depending on the situation. The reason / situation in which simultaneous transmission / reception cannot be performed may be, for example, as follows.

[0430] (Case 1) Whether simultaneous transmission / reception is possible may vary depending on the number of Tx / Rx chains that the MT of the IAB node uses for transmission / reception with two parent DUs.

[0431] Whether simultaneous transmission / reception is possible may vary depending on the number of transmission / reception chains that the MT of the IAB node uses for transmission / reception with two parent DUs. For example, if it has two Tx chains, simultaneous transmission is possible for two parent DUs, but if it has only one Tx chain, Tx is possible for only one parent DU in a specific time resource.

[0432] The number of Tx / Rx chains that the MT of the IAB node uses for transmission / reception with two parent DUs may vary depending on the number of Tx / Rx chains that the MT of the IAB node has.

[0433] Alternatively, when carrier aggregation (CA) / dual connectivity (DC) is performed, the number of Tx / Rx chains that can be used in a specific CC or in a specific frequency resource may vary according to the number of CCs configured or activated for the MT of the IAB node.

[0434] (Case 2) Whether simultaneous transmission / reception is possible may vary depending on the transmission / reception method performed by the MT of the IAB node.

[0435] Even if the MT of the IAB node performs transmission / reception with two parent DUs using the same number of Tx / Rx chains, whether simultaneous transmission / reception is possible may vary depending on a transmission / reception method applied by the MT of the IAB node.

[0436] For example, even if transmission is performed for two parent DUs using a single Tx chain, whether simultaneous transmission is possible may vary depending on the following factors.

[0437] - When the analog beam directions are different (or the QCL (quasi co-location) information is different), simultaneous transmission may not be possible.

[0438] - If the transmission timing difference between two parent links is larger than a certain value, simultaneous transmission may not be possible.

[0439] - If the transmission power difference between two parent links is larger than a certain value, simultaneous transmission may not be possible.

[0440] Alternatively, for example, when there are two parent DUs, it is possible to consider dynamic switching between 2-layer transmission for one parent DU and 1-layer simultaneous transmission for two parent DUs using 2 Tx / Rx chains. In this case, whether simultaneous transmission is possible may vary depending on the operation method.

[0441] First, as described above, when the MT of the IAB node is connected to two parent nodes, that is, when it is connected to two parent DU-cells belonging to different CGs, consider a situation where simultaneous transmission and / or simultaneous reception on the two parent links is impossible. In this case, the transmission / reception operation of the MT of the IAB node on the two parent links is proposed below.

[0442] The following description will be described assuming that there are two parent nodes, parent DU-cells and / or parent links, but may be extended / applied to more than two parent nodes.

[0443] First, a method of operating a parent DU cell to prevent a collision of transmission / reception resources between two parent links will be described.

[0444] When the MT of the IAB node cannot simultaneously perform downlink reception from two parent DU-cells or simultaneously perform uplink transmission, each of the two parent DU-cells needs to operate so that downlink reception or uplink transmission is not performed on the same resources for the MT of the IAB node. That is, only one parent DU-cell may have to perform transmission / reception with the MT of the IAB node in the same time resources. To this end, the following operations / methods are proposed. Only one of the following methods may be applied or multiple methods may be applied together. By the following method, when a specific parent DU-cell does not transmit / receive with the MT of the IAB node in a specific resource, scheduling may not be performed so that the MT of the IAB node performs transmission / reception with itself in the corresponding resource.

[0445] (Method 1-1) A parent DU cell to be operated is determined based on resource availability information of the parent DU cell.

[0446] Here, the resource availability information indicates whether a specific resource (e.g., a DU resource of a parent DU cell) is a hard resource, a soft resource, or an unavailable (NA) resource. Here, a hard (H) resource may mean a time resource that is always available for a DU sublink, and a soft (S) resource may mean a time resource in which the availability of the time resource for the DU sublink is explicitly or implicitly controlled by the parent node, respectively.

[0447] Fig.34 is a flowchart illustrating an operation example of the first parent DU-cell when the first parent DU-cell and the second parent DU-cell are connected to the IAB node.

[0448] refer to Fig.34 , the first parent DU-cell receives DU configuration information of the second parent DU-cell (S3410). Here, the DU configuration information may include information on availability of resources configured for the parent DU cell.

[0449] Thereafter, the first parent DU-cell determines whether transmission / reception with the IAB node in a specific resource is possible based on its DU configuration information and the DU configuration information of the second parent DU-cell (S3420).

[0450] Thereafter, when the first parent DU cell determines that transmission / reception with the IAB node in the specific resources is possible, the first parent DU cell performs transmission / reception with the IAB node in the specific resources (S3430).

[0451] That is, assuming that the parent DU-cells of the MTs connected to the same IAB node are the first parent DU-cell (or parent DU-cell 1) and the second parent DU-cell (or parent DU-cell 2), respectively, the parent DU-cell 1 can determine whether transmission / reception with the MT of the IAB node in a specific resource is possible while considering the resource availability information included in its DU configuration information and the resource availability information included in the DU configuration information of the parent DU-cell 2.

[0452] To this end, the parent DU-cell 1 may receive DU configuration information of the parent DU-cell 2 or availability information of resources included in the DU configuration information.

[0453] Meanwhile, according to the resource availability information of the parent DU-cell 1 and the DU configuration information or resource availability information of the parent DU-cell 2 for specific time resources, the parent DU-cell 1 may operate as follows.

[0454] a) When the resource availability information of the parent DU-cell 1 is not available (NA), the parent DU-cell 1 may not perform transmission / reception with the MT of the IAB node.

[0455] b) When the resource availability information of the parent DU-cell 1 is hard or soft and the resource availability information of the parent DU-cell 2 is NA, the parent DU-cell 1 may perform transmission / reception with the MT of the IAB node.

[0456] c) When the resource availability information of the parent DU-cell 1 is hard and the resource availability information of the parent DU-cell 2 is soft, the operation of the parent DU-cell 1 may be prioritized (Alternative 1), which is set to use the corresponding resources deterministically. Therefore, the parent DU-cell 1 may perform transmission / reception with the MT of the IAB node. Alternatively, (Alternative 2) the parent DU-cell configured to have priority among the two parent DU-cells may perform transmission / reception with the MT of the IAB node. The parent DU-cell with priority may be determined as in method 1-2 described later. If the parent DU-cell 1 has priority according to the priority determination method, the parent DU-cell 1 may perform transmission / reception with the MT of the IAB node. Otherwise, the parent DU-cell 1 may not perform transmission / reception with the MT of the IAB node. Alternatively, (Alternative 3) the parent DU cell configured to operate on the corresponding resources through TDM resource configuration may perform transmission / reception with the MT of the IAB node. The TDM resource configuration may be configured as in method 1-3 described later. If the parent DU-cell 1 is configured to operate in the corresponding resources through the corresponding TDM resource configuration, the parent DU-cell 1 can perform transmission / reception with the MT of the IAB node. Otherwise, the parent DU-cell 1 may not perform transmission / reception with the MT of the IAB node. Alternatively, (Alternative 4) both parent DU cells can perform transmission / reception with the MT of the IAB node. Therefore, the parent DU-cell 1 can perform transmission / reception with the MT of the IAB node. In this case, in addition, when a transmission / reception resource conflict occurs between two parent links to be described later, the MT of the IAB node can perform transmission / reception on only one parent link by the method proposed in the operation method of the MT of the IAB node.

[0457] d) When the resource availability information of the parent DU-cell 1 is soft and the resource availability information of the parent DU-cell 2 is hard, (Alternative 1) the operation of the parent DU-cell 2 set to use the corresponding resources for certainty may be given priority. Therefore, the parent DU-cell 1 may not perform transmission / reception with the MT of the IAB node. Alternatively, (Alternative 2) the parent DU-cell configured to have priority among the two parent DU-cells may perform transmission / reception with the MT of the IAB node. The parent DU-cell with priority may be determined as in method 1-2 described later. If the parent DU-cell 1 has priority according to the priority determination method, the parent DU-cell 1 may perform transmission / reception with the MT of the IAB node. Otherwise, the parent DU-cell 1 may not perform transmission / reception with the MT of the IAB node. Alternatively, (Alternative 3) the parent DU cell configured to operate on the corresponding resources through TDM resource configuration may perform transmission / reception with the MT of the IAB node. The TDM resource configuration may be configured as in method 1-3 described later. If the parent DU-cell 1 is configured to operate in the corresponding resources through the corresponding TDM resource configuration, the parent DU-cell 1 can perform transmission / reception with the MT of the IAB node. Otherwise, the parent DU-cell 1 may not perform transmission / reception with the MT of the IAB node. Alternatively, (Alternative 4) both parent DU cells can perform transmission / reception with the MT of the IAB node. Therefore, the parent DU-cell 1 can perform transmission / reception with the MT of the IAB node. In this case, when the transmission / reception resources conflict between the two parent links that will be further described later, the MT of the IAB node can perform transmission / reception on only one parent link according to the method proposed in the operation method of the MT of the IAB node.

[0458] e) When the resource availability information of the parent DU-cell 1 is hard and the resource availability information of the parent DU-cell 2 is hard, (Alternative 1) the parent DU-cell configured to have priority among the two parent DU-cells can perform transmission / reception with the MT of the IAB node. The parent DU-cell with priority can be determined as in method 1-2 described later. If the parent DU-cell 1 has priority according to the priority determination method, the parent DU-cell 1 can perform transmission / reception with the MT of the IAB node. Otherwise, the parent DU-cell 1 may not perform transmission / reception with the MT of the IAB node. Alternatively, (Alternative 2) the parent DU cell configured to operate on the corresponding resources through TDM resource configuration can perform transmission / reception with the MT of the IAB node. The TDM resource configuration can be configured as in method 1-3 described later. If the parent DU-cell 1 is configured to operate in the corresponding resources through the corresponding TDM resource configuration, the parent DU-cell 1 can perform transmission / reception with the MT of the IAB node. Otherwise, the parent DU-cell 1 may not perform transmission / reception with the MT of the IAB node. Alternatively, (Alternative 3) both parent DU cells may perform transmission / reception with the MT of the IAB node. Therefore, the parent DU-cell 1 may perform transmission / reception with the MT of the IAB node. In this case, when transmission / reception resources conflict between two parent links described later, the MT of the IAB node may perform transmission / reception on only one parent link according to the method proposed in the operation method of the MT of the IAB node.

[0459] f) When the resource availability information of the parent DU-cell 1 is soft and the configuration information of the parent DU-cell 2 is soft, (Alternative 1) the parent DU-cell configured to have priority among the two parent DU-cells can perform transmission / reception with the MT of the IAB node. The parent DU-cell with priority can be determined as in method 1-2 described later. If the parent DU-cell 1 has priority according to the priority determination method, the parent DU-cell 1 can perform transmission / reception with the MT of the IAB node. Otherwise, the parent DU-cell 1 may not perform transmission / reception with the MT of the IAB node. Alternatively, (Alternative 2) the parent DU cell configured to operate on the corresponding resources through TDM resource configuration can perform transmission / reception with the MT of the IAB node. The TDM resource configuration can be configured as in method 1-3 described later. If the parent DU-cell 1 is configured to operate in the corresponding resources through the corresponding TDM resource configuration, the parent DU-cell 1 can perform transmission / reception with the MT of the IAB node. Otherwise, the parent DU-cell 1 may not perform transmission / reception with the MT of the IAB node. Alternatively, (Alternative 3) two parent DU cells may perform transmission / reception with the MT of the IAB node. Therefore, the parent DU-cell 1 may perform transmission / reception with the MT of the IAB node. In this case, when the transmission / reception resources conflict between the two parent links described later, the MT of the IAB node may perform transmission / reception on only one parent link according to the method proposed in the operation method of the MT of the IAB node.

[0460] The foregoing has been written from the perspective of parent DU-cell 1, and similarly, parent DU-cell 2 is also able to determine whether transmission / reception with the MT of the IAB node is possible in specific resources in consideration of the resource availability information of parent DU-cell 2 and the resource availability information of parent DU-cell 1.

[0461] (Method 1-2) A parent DU-cell to be operated is determined based on the priority setting of the parent DU-cells.

[0462] Assuming that the two parent DU-cells of the MT connected to the same IAB node are parent DU-cell 1 and parent DU-cell 2, each parent DU-cell can determine whether transmission / reception with the MT of the IAB node is possible in a specific resource by a method of determining priority. In this case, a parent DU-cell with priority (or with a relatively high priority) can perform transmission / reception with the MT of the IAB node, and a parent DU-cell without priority (or with a relatively low priority) cannot perform transmission / reception with the MT of the IAB node. In this case, the specific method of determining priority may be as follows.

[0463] (Alternative 1) When two parent DU-cells are in a DC relationship from the perspective of the MT of the IAB node, (Alternative 1-a) the parent DU-cell belonging to the MCG may have priority (or a relatively high priority). Alternatively, (Alternative 1-b) the parent DU-cell belonging to the SCG may have priority (or a relatively high priority).

[0464] (Alternative 2) When two parent DU cells are in a DAPS-HO relationship from the perspective of the MT of the IAB node, (Alternative 2-a) the parent DU cell belonging to the source MCG has priority (or a relatively high priority). Alternatively, (Alternative 2-b) the parent DU cell belonging to the target MCG may have priority (or a relatively high priority).

[0465] (Alternative 3) Information of the parent DU cell with priority may be configurable information. For example, each parent DU-cell may receive information about which parent DU-cell has priority from the donor node / CU.

[0466] (Method 1-3) The parent DU-cell is determined through TDM resource configuration.

[0467] Assuming that the parent DU-cells of the MTs connected to the same IAB node are parent DU-cell 1 and parent DU-cell 2, respectively, the information of the parent DU-cell with priority (or relatively high priority) may vary according to time resources. In this case, the parent DU-cell with priority (or relatively high priority) may perform transmission / reception with the MT of the IAB node, and the parent DU-cell without priority (or with relatively low priority) may not perform transmission / reception with the MT of the IAB node.

[0468] Information about the parent DU cell with priority according to time resources can be configured by the donor node / CU. Alternatively, the parent DU-cell with priority can be changed according to a predetermined rule (for example, the parent DU-cell with priority in the even-numbered time slot and the odd-numbered time slot is different according to the time slot index).

[0469] In the foregoing, the fact that a specific parent DU-cell does not operate or does not perform transmission and reception with the MT of the IAB node may mean that the resource availability of the corresponding parent DU-cell is maintained as set, but the parent DU-cell does not perform transmission / reception with the MT of the IAB node. Alternatively, the fact that a specific parent DU-cell does not operate or does not perform transmission / reception with the MT of the IAB node can be interpreted as an NA operation configured in the corresponding resource or as a soft resource operation that is not configured as an available resource.

[0470] Typically, if a specific parent DU-cell determines whether its operation is possible using the above method, whether the corresponding operation is possible is also applied to transmission / reception with all its own sub-links (i.e., UEs and / or MTs connected to all child nodes of the corresponding parent DU cell). That is, according to the determination of whether the operation is possible, transmission / reception may or may not be performed for all sub-links of the parent DU-cell.

[0471] Alternatively, if a specific parent DU cell determines whether its operation is possible, whether the corresponding operation is possible may be applied only to transmission / reception with a specific sub-link (i.e., MT and / or UE connected to a specific sub-node of the corresponding parent DU-cell). In this case, the information referred to by the specific parent DU-cell in determining whether its own operation is possible (e.g., DU configuration or resource availability information of another parent DU-cell, TDM information, and priority-related information about the parent DU-cell, etc.) can be configured in a sub-link-specific (i.e., MT-specific and / or UE-specific in the sub-node) manner.

[0472] Next, an operation method of the MT of the IAB node when resources conflict between two parent links will be described.

[0473] Fig.35 is a flowchart of an operation example of an IAB node when multiple parent DU-cells are connected to the IAB node. Here, the IAB node may mean an MT of the IAB node.

[0474] refer to Fig.35 , the IAB node determines whether it is configured to simultaneously perform downlink reception from a plurality of parent DU-cells or simultaneously perform uplink transmission to a plurality of parent DU-cells (S3510).

[0475] Thereafter, the IAB node selects one of a plurality of parent DU cells (S3520).

[0476] Thereafter, the IAB node performs downlink reception or uplink transmission with the selected parent DU cell (S3530).

[0477] When the MT of the IAB node cannot perform downlink reception from two parent DU-cells or uplink transmission at the same time, each of the two parent DU-cells should use the above method and not perform downlink reception or uplink transmission for the MT of the IAB node under the same time resources.

[0478] However, inevitably, the MT of the IAB node may be configured / scheduled to simultaneously perform downlink reception from two parent DU-cells or simultaneously perform uplink transmission.

[0479] In this case, the MT of the IAB node may perform downlink reception or uplink transmission only for one parent DU-cell, and may not perform downlink reception or uplink transmission for another parent DU-cell. Hereinafter, a method for determining a parent DU-cell for performing downlink reception or uplink transmission is proposed. For example, in Fig.35 In the step (S3520) of selecting one of multiple parent DU-cells, the IAB node may apply at least one of the following methods.

[0480] (Method 2-1) Set available resources for each parent link.

[0481] When the MT of the IAB node is configured / scheduled for uplink transmission to two parent DU-cells or downlink reception from two parent DU-cells in a specific time resource, the MT of the IAB node can determine the parent DU-cell to which the MT of the IAB node will transmit / receive by receiving resource information operable for each parent link. To this end, the MT of the IAB node can receive information about time resources that can be used for operations on the corresponding parent link of each parent link. Typically, this setting can be set by RRC signaling from the donor node / CU. When the IAB node is configured / scheduled for transmission / reception of a specific parent DU-cell, the corresponding transmission / reception can be performed when the resources on which the corresponding transmission / reception is performed are set to resources available in the corresponding parent link. If the IAB node is configured / scheduled for transmission / reception of two parent DU-cells in a specific time resource, and the corresponding time resource is set to a resource that can be used for two parent links, the following operations can be performed.

[0482] (Alternative a) It may operate based on methods 2 to 4 described later.

[0483] (Alternative b) It can operate based on method 2-2 described later.

[0484] (Method 2-2) Determine the transmission and reception with priority (or relatively high priority)

[0485] When the MT of the IAB node is configured / scheduled for uplink transmission to two parent DU cells or downlink reception from two parent DU cells in a specific time resource, transmission and reception with priority or relatively high priority can be preferentially performed. In this case, when the MT of the IAB node is configured / scheduled for uplink transmission to two parent DU-cells or downlink reception from two parent DU-cells, the MT of the IAB node may only perform transmission / reception with priority (or relatively high priority), and may not perform transmission / reception without priority (or relatively low priority). In this case, transmission and reception with priority (or relatively high priority) can be determined as follows.

[0486] (Alternative a) Determined according to the transmission timing of the scheduling DCI for the corresponding downlink / uplink transmission.

[0487] (Alternative scheme a-1) Transmission / reception of scheduling DCI for corresponding downlink / uplink transmission transmitted earlier has priority (relatively high).

[0488] (Alternative a-2) Transmission / reception of scheduling DCI for corresponding downlink / uplink transmission sent later has a (relatively high) priority.

[0489] (Alternative b) Determined according to the time resources of the corresponding downlink / uplink transmission.

[0490] (Alternative b-1) The time resource for performing the corresponding downlink / uplink transmission, the transmission / reception of which starts earlier, has a (relatively higher) priority.

[0491] (Alternative b-2) Transmission / reception in which the time resources for performing the corresponding downlink / uplink transmission start later has a (relatively higher) priority.

[0492] (Alternative solution c) If the two parent DU cells are in a DC relationship from the perspective of the MT of the IAB node, then (Alternative solution c-1) the transmission / reception of the parent DU cell belonging to the MCG has a (relatively high) priority. Alternatively, (Alternative solution c-2) the transmission / reception of the parent DU cell belonging to the SCG has a (relatively high) priority.

[0493] (Alternative d) When two parent DU-cells are in a DAPS-HO relationship from the perspective of the MT of the IAB node, (Alternative d-1) the transmission / reception of the parent DU-cell belonging to the source MCG has a (relatively higher) priority. Alternatively, (Alternative d-2) the transmission / reception of the parent DU-cell belonging to the target MCG has a (relatively higher) priority.

[0494] (Alternative e) Information about a parent DU-cell with a (relatively high) priority may be configured. For example, the MT of the IAB node may receive information about which parent DU-cell has a (relatively high) priority from the donor / CU. In this case, transmission / reception of the parent DU-cell with a (relatively high) priority may be transmission / reception with a (relatively high) priority.

[0495] (Method 2-3) The parent DU-cell to be operated is determined through TDM resource configuration.

[0496] When the MT of the IAB node is configured / scheduled for uplink transmission to two parent DU-cells or downlink reception from two parent DU-cells in a specific time resource, the parent DU-cell may be determined to perform uplink transmission or downlink reception differently according to the time resource. That is, information about the parent DU-cell having a (relatively high) priority for MT transmission / reception of the IAB node may vary according to the time resource. In this case, when the MT of the IAB node is configured / scheduled for uplink transmission to two parent DU-cells or downlink reception from two parent DU-cells, the MT of the IAB node performs transmission / reception configured / scheduled with the parent DU-cell having a (relatively high) priority, and may not perform transmission / reception configured / scheduled with the parent DU-cell not having a (relatively high) priority.

[0497] To this end, information about a parent DU cell having a (relatively high) priority for transmission and reception according to time resources may be configured from the donor node / CU. Alternatively, the parent DU-cell having a (relatively high) priority may be changed according to a predetermined rule (e.g., determining that the parent DU-cell having a (relatively high) priority in an even-numbered time slot and an odd-numbered time slot is different according to a time slot index).

[0498] (Method 2-4) The MT of the IAB node determines a parent DU-cell to be operated arbitrarily.

[0499] When the MT of the IAB node is configured / scheduled for uplink transmission to or downlink reception from two parent DU-cells in a specific time resource, the MT of the IAB node can perform one transmission or reception selected at random.

[0500] Hereinafter, the timing misalignment between parent links will be described.

[0501] When a UE is connected to two eNBs through DC (dual connectivity) in an existing LTE environment, the difference between the maximum transmission / reception timing of MCG and SCG considered from the UE's perspective is 33us based on a synchronous DC scenario and 500us based on an asynchronous DC scenario.

[0502] In the case of EN-DC in the NR environment, the maximum uplink transmission timing difference in the asynchronous inter-band EN-DC scenario is as follows.

[0503] [Table 9]

[0504]

[0505] Here, for EN-DC in the E-UTRA FDD-NR FDD band, if the standard or the like defines the requirements in advance and this table is applicable, there may not be a scenario of 120kHz PCell.

[0506] On the other hand, the maximum uplink transmission timing difference in the EN-DC case in the synchronization band is as follows.

[0507] [Table 10]

[0508]

[0509] Here, when the UL subcarrier spacing for data in PSCell is 15kHz, it does not apply to UEs that indicate the capability of supporting only a single UL timing (using signaling ul-TimingAlignmentEUTRA-NR). For this reason, the UE assumes a single UL timing for E-UTRA and NR cells.

[0510] Furthermore, in the case of Table 10 above, if the transmission timing difference exceeds the cyclic prefix length of the UL subcarrier spacing for PSCell data, NR UE Tx EVM degradation is expected for symbols overlapping with LTE subframe boundaries.

[0511] On the other hand, in the IAB environment, a synchronous deployment is assumed in which the downlink transmission timing between IAB nodes is aligned. However, despite being a synchronous environment, when an IAB node is connected to two parent nodes, the difference in uplink transmission timing for the two parent nodes may be greater than in a traditional synchronous DC environment.

[0512] Fig.36 An example of transmission / reception timing of each node when two parent nodes are connected to one IAB node is illustrated.

[0513] This phenomenon may occur, for example, when the DU reception timing between parent nodes is set differently due to different timing alignment methods applied between nodes. Fig.36 As shown in , the IAB node is connected to a parent node 1 and a parent node 2, and the parent node 1 and the parent node 2 can be connected to the wireless backhaul directly or through a connection with another node. That is, the parent node 1 and the parent node 2 are connected through a non-ideal backhaul. Here, in the case of the parent node 1, the uplink reception timing of the DU can be set by applying the timing alignment case 1. On the other hand, in the case of the parent node 2, the DU reception timing can be set to be the same as its own MT reception timing by applying the timing alignment case 7. In this case, the IAB node sets the uplink transmission timing for each parent node using the timing advance (TA) value set according to the DU reception timing of each parent node. Fig.36 In the embodiment, the IAB node sets the transmission timing of uplink transmission 1 (UL Tx 1) according to the timing of uplink reception 1 (UL Rx 1) of the parent node 1, and sets the transmission timing of uplink transmission 2 (UL Tx 2) according to the uplink reception 2 (UL Rx) of the parent node 2. In this case, the UL Tx 1 transmission timing and the UL Tx 2 transmission timing may have a difference greater than that in the case where the UL transmission timing is performed according to the same DU reception timing between the existing parent nodes.

[0514] As another example, the IAB node may apply timing alignment case 1 when transmitting / receiving with parent node 1, but may apply timing alignment case 6 when transmitting / receiving with parent node 2. In this case, when transmitting / receiving with parent node 1, the MT transmission timing of the IAB node may be set to be in advance by the TA value set from parent node 1 (according to the DU reception timing of parent node 1). On the other hand, the IAB node may set the MT transmission timing to be the same as its DU transmission timing during transmission / reception with parent node 2. Also in this case, the difference in uplink transmission timing of the IAB node relative to the two parent nodes may have a larger range than before.

[0515] Because the DU transmission timing between the parent nodes is synchronized, the difference in the MT reception timing of the two parent links is affected by the difference in the propagation delay with the two parent nodes. This may be similar to the situation in the existing DC. However, the difference in the MT transmission timing of the two parent nodes may be affected by the timing alignment method applied to the parent node and the IAB node and the propagation delay with the two parent nodes. In this case, the uplink transmission timing difference may be greater than the timing difference in the existing synchronous DC scenario.

[0516] Hereinafter, non-simultaneous transmission / reception of two parent links will be described.

[0517] When the IAB node is connected to two parent nodes, the frequency resources connected to the two parent nodes can use the same channel (same frequency) or adjacent channels (intra-frequency and intra-band). In this case, the connection with the two parent nodes can use, for example, the DC method or the DAPS-HO method.

[0518] When two parent nodes are connected using the same or different frequency resources within the frequency band, it can be assumed that a single RF chain is used. That is, the IAB node can use the same transmission RF chain to perform uplink transmission to parent node 1 and uplink transmission to parent node 2. In this case, if the difference in uplink transmission timing to the two parent nodes is equal to or greater than a certain value, simultaneous uplink transmission to the two parent nodes may not be performed, and only non-simultaneous uplink transmission may need to be used. This means that the IAB node should perform uplink transmission to the two parent nodes in a TDM method.

[0519] In the case of downlink, the IAB node can perform downlink reception for parent node 1 and downlink reception for parent node 2 using the same reception RF chain. In this case, if the difference in downlink reception timing to the two parent nodes is equal to or greater than a certain value, simultaneous downlink reception from the two parent nodes cannot be performed, and only non-simultaneous downlink reception can be performed. This means that the IAB node should perform downlink reception for the two parent nodes in a TDM manner.

[0520] Hereinafter, the transmission / reception timing misalignment of two parent links will be described.

[0521] When the IAB node performs transmission and / or reception operations to two parent nodes non-simultaneously, in order for the IAB node to perform transmission / reception from one parent node and transmission / reception to another parent node, it may need to perform a transmission / reception switching operation. When the IAB node transmits / receives with one parent node and then transmits / receives with another parent node, due to the switching of the transmission / reception operation and the misalignment between the transmission / reception timing with the two parent nodes, a protection time may be required when transmitting / receiving with the two parent nodes.

[0522] Fig.37 An example of the difference in uplink transmission timing of an IAB node relative to two parent nodes is illustrated.

[0523] refer to Fig.36 , the transmission / reception timing of the IAB node relative to the two parent nodes is misaligned. Therefore, for example, when uplink transmission is performed to parent node 2 until symbol #n and uplink transmission is performed to parent node 1 from symbol #n+1, a resource conflict problem may occur because there is a difference in the uplink transmission timing to the two parent nodes. Fig.37The example shows the uplink transmission timing to parent node 1 and the uplink transmission timing to parent node 2 from the perspective of the IAB node. When the IAB node performs uplink transmission to parent node 2 in time slot #n and performs uplink transmission to parent node 2 in time slot #n+1, due to the misalignment of the two uplink transmission timings, overlap occurs in the uplink transmission to the two parent nodes. In this case, the IAB node cannot perform uplink transmission simultaneously in the overlapping resources. This timing misalignment problem occurs not only in uplink transmission to two parent nodes, but may also occur when the transmission directions to parent node 1 and parent node 2 are downlink and downlink, uplink and downlink, and / or downlink and uplink, respectively.

[0524] Meanwhile, in the present specification, a parent node may refer to a parent DU-cell belonging to the parent node.

[0525] Hereinafter, a method of operating a parent node to prevent a conflict of transmission / reception resources between two parent links will be described.

[0526] As described above, when the IAB node switches the parent node that performs transmission / reception, a resource overlap problem may occur. In this case, each parent node needs to know information about overlapping resources so that it can determine information about resources that cannot be transmitted / received with the IAB node due to the resource overlap problem. To this end, the parent node and the IAB node may have to share information about resources that cannot be transmitted / received with the IAB node due to the resource overlap problem.

[0527] Therefore, the protection symbol report / configuration related to the operation method of the parent node for preventing the conflict of the transmission / reception resources between the two parent links will be described. Here, the protection symbol can be a time resource in which the IAB node does not communicate with another IAB node or a time resource in which the IAB node connected to multiple parent nodes performs a switch from the first parent node to the second parent node.

[0528] Because the IAB node knows the transmit / receive timing to each parent node, it is able to know information about resources that cannot be used due to resource overlap between the parent links of the two parent nodes. The IAB node can report information about the "number of required protection symbols" to the parent node and / or CU (or donor node) based on the degree of timing misalignment between the two parent links.

[0529] In this case, the IAB node and each parent node of the IAB node may determine the number of guard symbols applied when the IAB node switches the parent node that performs transmission / reception as follows.

[0530] (Method 3-1) The IAB node may determine that the number of protection symbols reported to the parent node and / or CU (or donor node) is the number of protection symbols it uses. In this case, each parent node of the IAB node may determine that the number of necessary protection symbols reported by the IAB node is the number of protection symbols used by the IAB node.

[0531] (Method 3-2) The IAB node may be configured with the number of protection symbols from the CU (or donor node) through RRC signaling and / or F1-AP (Application Protocol) signaling. To this end, the CU (or donor node) may set the number of protection symbols applied to the IAB node based on the number of necessary protection symbols reported by the IAB node or independently. In addition, each parent node (or DU of the parent node) of the IAB node may also be notified of the number of protection symbols applied to the IAB node.

[0532] In this case, the information about the number of guard symbols reported by the IAB node (or configured by the IAB node and / or the parent node) may be in the form of guard symbol related information to be described later.

[0533] Fig.38 is a flowchart of an example of a method for setting protection symbols of an IAB node according to some embodiments of the present specification.

[0534] refer to Fig.38 , the IAB node determines overlapping resources between a first link with a first parent node and a second parent link with a second parent node (S3810).

[0535] Thereafter, the IAB node reports information related to the number of guard symbols required by the IAB node to at least one of the first parent node and the second parent node (S3820).

[0536] Thereafter, when switching from communication with the first parent node to communication with the second parent node, the IAB node operates based on the reported number of guard symbols (S3830).

[0537] Hereinafter, protection symbol related information related to a method of operating a parent node to prevent a collision of transmission / reception resources between two parent links will be described.

[0538] The number of the above-mentioned protection symbols may have different values ​​depending on the situation when the IAB node switches the parent node that performs transmission / reception. Fig.36In the example of , both the downlink reception timing and the uplink transmission timing of the two parent links of the IAB node can have different timings. When the IAB node performs switching for the parent node that performs transmission / reception, the number of required protection symbols can vary according to the downlink reception / uplink transmission operation before the switching and the downlink reception / uplink transmission operation after the switching. That is, the number of protection symbols can vary according to the following switching situations.

[0539] - Switch from downlink reception to downlink reception

[0540] - Switch from downlink reception to uplink transmission

[0541] -Switch from uplink transmission to downlink reception

[0542] -Switch from uplink transmission to downlink transmission

[0543] In this case, the number of guard symbols may be defined for only some combinations among all combinations of DL / UL directions between the parent node 1 and the parent node 2. For example, assuming that the difference between the downlink reception timings to the two parent nodes is always less than a predetermined value, when switching from downlink reception to downlink reception, switching may be performed without separate guard symbols. In view of this situation, guard symbols may be set only for the remaining switching cases except for the case of switching from downlink reception to downlink reception.

[0544] In this case, if the number of guard symbols is not set for a specific switching situation, the number of guard symbols may be assumed to be zero.

[0545] In addition, when the IAB node is connected to parent node 1 and parent node 2, the number of protection symbols may be different depending on whether switching from parent node 1 to parent node 2 or switching from parent node 2 to parent node 1 is performed for the DL / UL direction of specific parent node 1 and parent node 2 (i.e., depending on the switching direction between parent node 1 and parent node 2).

[0546] Fig.39 An example of configuring downlinks for parent node 1 and parent node 2 is shown. Fig.40 An example is shown in which parent node 1 is configured with a downlink and parent node 2 is configured with an uplink. Fig.41 An example is shown in which parent node 1 is configured with an uplink and parent node 2 is configured with a downlink. Fig.42 An example of configuring uplinks for parent node 1 and parent node 2 is shown.

[0547] exist Figures 39 to 42 In the example, based on Fig.36The downlink reception timing and uplink transmission timing of two parent links of the IAB node shown in FIG. 1 show the resource overlap type according to each switching situation. Figures 39 to 42 It shows the case where the parent node 1 and the parent node 2 have resource directions of downlink and downlink, downlink and uplink, uplink and downlink, and uplink and uplink, respectively. Figures 39 to 42 (a) shows the case of switching from parent node 1 to parent node 2, and Figures 39 to 42 (b) shows the case of switching from parent node 2 to parent node 1. It can be seen that the number of overlapping resources is based on Figures 39 to 42 There are a total of 8 switching situations.

[0548] Therefore, the protection symbols used by the IAB node when switching between two parent nodes can be defined for the following switching situations: Different definitions can be made according to the switching direction between parent node 1 and parent node 2 and the DL / UL direction between parent node 1 and parent node 2.

[0549] Hereinafter, the positions of guard symbols related to an operation method of a parent node for preventing a collision of transmission / reception resources between two parent links will be described.

[0550] In order to determine the transmission / reception resources with the IAB node considering the protection symbols applied by the IAB node when switching the parent node, it is necessary to know when the IAB node switches the parent node. However, each parent node of the IAB node does not know the scheduling information of each other for the IAB node. Therefore, when the IAB node dynamically performs the switching of the parent node according to the DL / UL scheduling of each parent node, the parent node cannot determine the switching time of the IAB node and the location of the protection symbol application.

[0551] When the parent node knows the parent node switching time of the IAB node, the protection symbol application time of the IAB node can be determined. To this end, it is assumed that the parent node can determine the following by a method such as a setting from the CU / donor node, such as the time resource for the IAB node to send / receive with the parent node and / or the time resource for sending / receiving with another parent node, or the time when the IAB node performs switching to another parent node when performing transmission / reception with the parent node, and / or the time point when switching to the parent node when performing transmission / reception with another parent node.

[0552] When the IAB node switches the parent node to be transmitted / received from parent node 1 to parent node 2, or when the parent node to be transmitted / received switches from parent node 2 to parent node 1, the IAB node and each parent node can determine that the protection symbol of the IAB node is generated at the following position.

[0553] (Alternative 1) The position of the protection symbol may be determined according to the direction in which the IAB node performs switching between parent nodes.

[0554] (Alternative 1-a) A specific parent node may determine that the IAB node uses x symbols located before switching from itself to another parent node as protection symbols. That is, when the IAB node transmits / receives to / from parent node 1 until symbol #n and transmits / receives to / from parent node 2 from symbol #n+1, the IAB node and each parent node determine that the IAB node uses x symbols before symbol #n as protection symbols.

[0555] (Alternative 1-b) A specific parent node can determine that the IAB node uses n symbols located after switching from another parent node to itself as protection symbols. When the IAB node transmits / receives to / from parent node 1 until symbol #n, and transmits / receives to / from parent node 2 from symbol #n+1, the IAB node and each parent node can determine that n symbols after symbol #n+1 are used as protection symbols.

[0556] (Alternative 2) When the IAB node is connected to two parent nodes using DC, the position of the protection symbol can be determined according to whether the parent node is an MCG / SCG.

[0557] (Alternative 2-a) If a specific parent node is an MCG, it can be determined that the IAB node uses the x symbols located before switching from the specific parent node to another parent node as protection symbols. In addition, when the specific parent node is an MCG, it can be determined that the IAB node uses the n symbols located after switching from another parent node to the specific parent node as protection symbols. That is, when the IAB node performs switching of the sending / receiving parent node, the IAB node and each parent node can determine that the x symbols or n symbols operating with the MCG parent node will be used as protection symbols. As an example, when the IAB node performs sending / receiving with the parent node 1 until symbol #n and sends / receives with the parent node 2 from symbol #n+1, if the parent node 1 is an MCG, it is determined that the x symbols before symbol #n are used as protection symbols, and if the parent node 2 is an MCG, it can be determined that the n symbols after symbol #n+1 are used as protection symbols.

[0558] (Alternative 2-b) If a specific parent node is an SCG, it can be determined that the IAB node uses the x symbols located before switching from the specific parent node to another parent node as protection symbols. In addition, if the specific parent node is an SCG, it can be determined that the IAB node uses the n symbols located after switching from another parent node to the specific parent node as protection symbols. That is, when the IAB node performs switching of the sending / receiving parent node, the IAB node and each parent node can determine that the x symbols or n symbols operating with the SCG parent node will be used as protection symbols. As an example, when the IAB node performs sending / receiving with the parent node 1 until symbol #n and sends / receives with the parent node 2 from symbol #n+1, if the parent node 1 is an SCG, it is determined that the x symbols before symbol #n are used as protection symbols, and if the parent node 2 is an SCG, it can be determined that the n symbols after symbol l#n+1 are used as protection symbols.

[0559] (Alternative 3) When the IAB node is connected to two parent nodes using DAPS / DAPS-HO, the position of the protection symbol may be determined according to whether the parent node is a source MCG / target MCG.

[0560] (Alternative 3-a) When a specific parent node is a source MCG, it can be determined that the IAB node uses the x symbols located before switching from the specific parent node to another parent node as protection symbols. In addition, when the specific parent node is a source MCG, it can be determined that the n symbols located after the IAB node performs switching from another parent node to the specific parent node are used as protection symbols. That is, when the IAB node performs switching of the sending / receiving parent node, the IAB node and each parent node can determine that the x symbols or n symbols operating with the MCG parent node are used as protection symbols. When the IAB node sends / receives to / from parent node 1 until symbol #n and sends / receives to / from parent node 2 from symbol #n+1, if parent node 1 is a source MCG, it is determined that the x symbols before symbol #n are used as protection symbols, and if parent node 2 is a source MCG, it is determined that the n symbols after symbol #n+1 are used as protection symbols.

[0561] (Alternative 3-b) When a specific parent node is a target MCG, it can be determined that the IAB node uses the x symbols located before switching from the specific parent node to another parent node as protection symbols. In addition, if the specific parent node is a target MCG, it can be determined that the IAB node uses the n symbols located after switching from another parent node to the specific parent node as protection symbols. That is, when the IAB node performs switching of the sending / receiving parent node, the IAB node and each parent node can determine that the x symbols operating with the SCG parent node will be used as protection symbols. As an example, when the IAB node performs sending / receiving with the parent node 1 until symbol #n and sends / receives with the parent node 2 from symbol #n+1, if the parent node 1 is the target MCG, it is determined that the x symbols or n symbols before symbol #n are used as protection symbols, and if the parent node 2 is the target MCG, it can be determined that the n symbols after symbol #n+1 are used as protection symbols.

[0562] (Alternative 4) The position of the guard symbol may be determined according to the downlink / uplink transmission direction. When the IAB node switches the parent node that performs transmission / reception, the position of the guard symbol may be determined based on the transmission / reception direction with the IAB node.

[0563] (Alternative 4-a) When the IAB node switches the parent node that performs transmission / reception, the IAB node and each parent node can determine that x symbols of the parent node with uplink resources are used as protection symbols. When the IAB node performs transmission / reception with the parent node 1 through the uplink resources until symbol #n, and transmits / receives with the parent node 2 from symbol #n+1, it can be determined that the x symbols before symbol #n are used as protection symbols. For example, when the IAB node performs transmission / reception with the parent node 1 until symbol #n, and transmits / receives with the parent node 2 through the uplink resources from symbol #n+1, it can be determined that the x symbols after symbol #n+1 are used as protection symbols.

[0564] For example, when the IAB node switches the parent node that performs transmission and reception, if transmission and reception are performed with the parent node through downlink resources before the switching, and transmission / reception is also performed with the parent node through downlink resources after the switching, from the perspective of the IAB node, it can be assumed that the downlink reception timing difference between the two parent nodes is not large, and no protection symbol is generated. Alternatively, it can be assumed that the IAB node does not generate protection symbols because simultaneous reception is possible in the case of downlink reception with two parent nodes. Alternatively, in this case, the method of alternative 4-b described later can be applied.

[0565] For example, when the IAB node switches the parent node that performs transmission and reception, if transmission and reception are performed with the parent node through uplink resources before the switch, and transmission / reception is also performed with the parent node through uplink resources after the switch, considering that the two parent nodes do not know each other's downlink / uplink transmission direction information, both parent nodes can generate protection symbols in the operating resources between themselves and the IAB node. For example, when the IAB node performs transmission / reception with parent node 1 through uplink resources until symbol #n, and performs uplink operation with parent node 2 from symbol #n+1, parent node 1 determines that x1 symbols before symbol #n are used as protection symbols, and parent node 2 can determine that x2 symbols after symbol #n+1 are used as protection symbols. Here, x1 and x2 can be the same or different from each other. Alternatively, in this case, the method of alternative 4-b described later can be applied.

[0566] (Alternative 4-b) Considering the case where two parent nodes are able to know each other's downlink / uplink transmission direction information, the following operation may be performed.

[0567] For example, when the IAB node performs transmission / reception with the parent node through uplink resources before the switching of the parent node, and performs transmission / reception with the parent node through uplink resources after the switching, it can be determined that the IAB node and each parent node will not generate protection symbols in the transmission / reception resources with the two parent nodes. In this case, each parent node can operate without considering the separate protection symbols. When the uplink transmission resources between the two parent nodes conflict, the IAB node can operate according to the operation method of the IAB node when the resources conflict between the two parent nodes, which will be described later.

[0568] In another example, when the IAB node performs transmission / reception with the parent node through uplink resources before switching of the parent node and also performs transmission / reception with the parent node through uplink resources after switching, and / or when performing transmission / reception with the parent node through downlink resources before switching and also performs transmission / reception with the parent node through downlink resources after switching, the IAB node and each parent node can use the methods of alternatives 1 to 3 above to determine the generation position of the protection symbol.

[0569] In this case, the number of protection symbols may be determined as suggested in the protection symbol reporting / configuration described above.

[0570] Hereinafter, a method of operating an IAB node when resources conflict between two parent links will be described.

[0571] When an IAB node is connected to two parent nodes and does not perform downlink reception and / or uplink transmission simultaneously with the two parent nodes, each parent node generates a protection symbol when the IAB node performs a switching of the parent node using one of the methods proposed in this specification, which can prevent the IAB node from having a resource overlap problem due to the misalignment of the transmission / reception timing with the two parent nodes. However, if the switching of the parent node of the IAB node is dynamically changed or the parent node cannot know the switching time of the parent node of the IAB node, etc., from the perspective of the IAB node, a problem in which the transmission and reception resources to the two parent nodes overlap may occur. Therefore, in the following, the operation of the IAB node is proposed when two transmissions / receptions in which the IAB node cannot perform simultaneous transmission / reception operations from two parent nodes are configured / scheduled in overlapping resources.

[0572] When an IAB node is connected and operated with two parent nodes, even if the transmit / receive resources of the two parent nodes are set / scheduled by different symbol resources, e.g. Fig.37 and 39 to Fig.42 As shown in , resource overlap may also occur due to the misalignment of the transmission / reception timing of the two parent nodes. In this case, the IAB node can solve the problem by only performing one of the two transmissions / receptions and not performing the other transmission / reception. In the following, a specific method for this is proposed.

[0573] (Alternative 1) When the IAB node switches from parent node 1 to parent node 2 to the parent node to be transmitted / received, if there is a conflict with the transmission / reception resources of the two parent nodes, (Alternative 1-a) the IAB node may not perform transmission / reception for the parent node 2 set / scheduled after the parent node is switched. Alternatively, (Alternative 1-b) the IAB node may not perform transmission / reception with respect to the parent node 1 set / scheduled before the switching of the parent node. Alternatively, (Alternative 1-c) the IAB node selects any transmission / reception among the transmission / reception for the two parent nodes, and may not perform the selected transmission / reception.

[0574] In the above description, not performing transmission / reception may mean discarding the entire transmission / reception of a corresponding channel / signal or puncturing the corresponding channel / signal in a symbol where a collision occurs.

[0575] (Alternative 2) When the IAB node switches from parent node 1 to parent node 2 to the parent node to be transmitted / received, if there is a conflict in the transmission / reception resources with the two parent nodes and one of the transmission / reception to / from the two parent nodes is uplink, the IAB node can perform downlink reception without performing uplink transmission during the transmission / reception to the two parent nodes.

[0576] In the above description, not performing transmission / reception may mean discarding the entire transmission / reception of a corresponding channel / signal, or puncturing the corresponding channel / signal in a symbol where a collision occurs.

[0577] In this case, when the transmission and reception to both parent nodes are all downlink or all uplink, the method of alternative 1 may be used.

[0578] Fig.43 An example is illustrated in which Alternative Scheme 2 is applied in the operation method of the IAB node when resources conflict between two parent links.

[0579] refer to Fig.43 , the IAB node may switch to communicate with the second parent node while communicating with the first parent node. In this case, a conflict situation may occur in which the resources allocated to the first parent link with the first parent node overlap with the resources allocated to the second parent link with the second parent node and the transmission directions are different. For example, Fig.43 As shown in , in the overlapping resources, the resources allocated to the first parent link may be uplink resources, and the resources allocated to the second parent link may be downlink resources. In this case, the IAB node does not perform uplink transmission on the overlapping resources (i.e., only punctures the corresponding channel / signal in the overlapping symbols, or the uplink transmission of the entire corresponding channel / signal that overlaps is discarded), and can perform downlink reception.

[0580] Fig.44 is a flowchart of an example of a resource setting method of an IAB node according to some embodiments of the present specification.

[0581] refer to Fig.44 , the IAB node performs an initial access process with the first parent node and the second parent node (S4410). Here, the initial access process can refer to Fig.16 process.

[0582] Thereafter, the IAB node sends report information to the first parent node and the second parent node (S4420). Here, the report information may indicate overlapping resources between a first parent link with the first parent node and a second parent link with the second parent node.

[0583] Thereafter, the IAB node receives protection symbol information (S4430). Here, the protection symbol information may inform protection symbols configured to the IAB node.

[0584] Thereafter, the IAB node performs switching from communication based on the first parent link to communication based on the second parent link based on the protection symbol information (S4440).

[0585] The claims in this specification can be combined in various ways. For example, the technical features of the method claims of the specification can be combined to be implemented or executed in a device, and the technical features of the device claims can be combined to be implemented or executed in a method. Furthermore, the technical features of the method claims and the technical features of the device claims can be combined to be implemented or executed in a device, and the technical features of the method claims and the technical features of the device claims can be combined to be implemented or executed in a method.

[0586] The method proposed in this specification can be performed by an IAB node. In addition, the method proposed in this specification can also be performed by at least one computer-readable medium, which includes instructions based on execution by at least one processor. The method proposed in this specification can also be performed by a device configured to control an IAB node. The device includes one or more processors and one or more memories operably coupled by the one or more processors and storing instructions, wherein the one or more processors execute the instructions to perform the method proposed herein. In addition, it is obvious that according to the method proposed in this specification, the operation of another IAB node corresponding to the operation performed by the IAB node can be considered.

[0587] Hereinafter, an example of a communication system to which the present disclosure is applied is described.

[0588] The various descriptions, functions, processes, proposals, methods and / or operational flowcharts disclosed herein may be applied to, but are not limited to, various fields requiring wireless communication / connection between devices (e.g., 5G).

[0589] In the following, specific examples are illustrated with reference to the accompanying drawings. In the following drawings / descriptions, unless otherwise specified, the same reference numerals may refer to the same or corresponding hardware blocks, software blocks or functional blocks.

[0590] Fig.45 A communication system 1 applied to the present disclosure is illustrated.

[0591] refer to Fig.45, the communication system 1 applied to the present disclosure includes a wireless device, a base station and a network. Here, the wireless device refers to a device that performs communication using a wireless access technology (e.g., 5G NR (New RAT), LTE (Long Term Evolution)), and may be referred to as a communication / wireless / 5G device. Although not limited to this, the wireless device may include a robot 100a, a vehicle 100b-1, 100b-2, an extended reality (XR) device 100c, a handheld device 100d and a home appliance 100e, an Internet of Things (IoT) device 100f and an AI device / server 400. For example, a vehicle may include a vehicle equipped with a wireless communication function, an autonomous driving vehicle, a vehicle capable of performing inter-vehicle communication, and the like. Here, the vehicle may include an unmanned aerial vehicle (UAV) (e.g., a drone). The XR device includes an AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) device, and it can be implemented in the form of a head-mounted device (HMD), a head-up display (HUD) set in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance, a digital signage, a vehicle, a robot, and the like. Portable devices may include smart phones, smart pads, wearable devices (e.g., smart watches, smart glasses), computers (e.g., laptop computers), etc. Home appliances may include televisions, refrigerators, washing machines, etc. IoT devices may include sensors, smart meters, etc. For example, base stations and networks may be implemented as wireless devices, and a specific wireless device 200a may operate as a base station / network node for other wireless devices.

[0592] Here, the wireless communication technology implemented in the wireless device of the present specification may include narrowband Internet of Things for low power communication as well as LTE, NR and 6G. In this case, for example, NB-IoT technology may be an example of low power wide area network (LPWAN) technology. In addition, it can be implemented in standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above names. Additionally or alternatively, the wireless communication technology implemented in the wireless device of the present specification may perform communication based on LTE-M technology. In this case, as an example, LTE-M technology may be an example of LPWAN technology and may be referred to as various names such as enhanced machine type communication (eMTC). For example, LTE-M technology may be implemented in at least one of various standards, such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-bandwidth limited), 5) LTE-MTC, 6) LTE machine type communication, and / or 7) LTE M, and is not limited to the above names. Additionally or alternatively, in consideration of low power communication, the wireless communication technology implemented in the wireless device of the present specification may include at least one of ZigBee, Bluetooth, and a low power wide area network (LPWAN), and is not limited to the above names. For example, ZigBee technology can create a PAN (Personal Area Network) related to small / low power digital communication based on various standards such as IEEE 802.15.4, and can be referred to by various names.

[0593] The wireless devices 100a to 100f may be connected to the network 300 through the base station 200. Artificial intelligence (AI) technology may be applied to the wireless devices 100a to 100f, and the wireless devices 100a to 100f may be connected to the AI ​​server 400 through the network 300. The network 300 may be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. The wireless devices 100a to 100f may communicate with each other via the base station 200 / network 300, and may also perform direct communication (e.g., sidelink communication) with each other without going through the base station / network. For example, the vehicles 100b-1 and 100b-2 may perform direct communication (e.g., vehicle-to-vehicle (V2V) / vehicle-to-everything (V2X) communication). In addition, an IoT device (e.g., a sensor) may communicate directly with another IoT device (e.g., a sensor) or another wireless device 100a to 100f.

[0594] Wireless communication / connection 150a, 150b and 150c can be established between wireless devices 100a to 100f and base station 200 and between base stations 200. Here, wireless communication / connection can be established through various radio access technologies (e.g., 5G NR), such as uplink / downlink communication 150a, sidelink communication 150b (or D2D communication) and inter-base station communication 150c (e.g., relay or integrated access backhaul (IAB)). Wireless devices and base stations / wireless devices and base stations can send / receive radio signals to each other through wireless communication / connection 150a, 150b and 150c. For example, wireless communication / connection 150a, 150b and 150c can send / receive signals through various physical channels. To this end, various configuration information setting processes, various signal processing processes (e.g., channel coding / decoding, modulation / demodulation, resource mapping / demapping, etc.) and at least some of the resource allocation processes can be performed based on various proposals of the present disclosure.

[0595] Fig.46 A wireless device that may be suitable for use with the present disclosure is illustrated.

[0596] refer to Fig.46 , the first wireless device 100 and the second wireless device 200 can send and receive wireless signals through various wireless access technologies (e.g., LTE, NR). Here, {first wireless device 100, second wireless device 200} may correspond to Fig.45 {wireless device 100x, base station 200} and / or {wireless device 100x, wireless device 100x}.

[0597] The first wireless device 100 includes at least one processor 102 and at least one memory 104, and may further include at least one transceiver 106 and / or at least one antenna 108. The processor 102 may be configured to control the memory 104 and / or the transceiver 106 and implement the description, functions, processes, proposals, methods and / or operation flowcharts disclosed herein. For example, the processor 102 may process the information in the memory 104 to generate first information / signals, and then may transmit a radio signal including the first information / signals through the transceiver 106. In addition, the processor 102 may receive a radio signal including second information / signals through the transceiver 106, and may store information obtained from signal processing of the second information / signals in the memory 104. The memory 104 may be connected to the processor 102 and may store various information related to the operation of the processor 102. For example, the memory 104 may store software code including instructions for executing some or all of the processes controlled by the processor 102 or executing the description, functions, processes, proposals, methods and / or operation flowcharts disclosed herein. Here, the processor 102 and the memory 104 may be part of a communication modem / circuit / chip designed to implement a radio communication technology (e.g., LTE or NR). The transceiver 106 may be connected to the processor 102 and may send and / or receive radio signals via at least one antenna 108. The transceiver 106 may include a transmitter and / or a receiver. The transceiver 106 may be replaced by a radio frequency (RF) unit. In the present disclosure, a wireless device may refer to a communication modem / circuit / chip.

[0598] The second wireless device 200 includes at least one processor 202 and at least one memory 204, and may further include at least one transceiver 206 and / or at least one antenna 208. The processor 202 may be configured to control the memory 204 and / or the transceiver 206 and implement the description, function, process, proposal, method and / or operation flowchart disclosed herein. For example, the processor 202 may process the information in the memory 204 to generate a third information / signal, and then transmit a radio signal including the third information / signal through the transceiver 206. In addition, the processor 202 may receive a radio signal including a fourth information / signal through the transceiver 206, and may store information obtained from signal processing of the fourth information / signal in the memory 204. The memory 204 may be connected to the processor 202 and may store various information related to the operation of the processor 202. For example, the memory 204 may store software code including instructions for executing some or all of the processes controlled by the processor 202 or executing the description, function, process, proposal, method and / or operation flowchart disclosed herein. Here, the processor 202 and the memory 204 may be part of a communication modem / circuit / chip designed to implement a radio communication technology (e.g., LTE or NR). The transceiver 206 may be connected to the processor 202 and may send and / or receive radio signals via at least one antenna 208. The transceiver 206 may include a transmitter and / or a receiver. The transceiver 206 may be replaced by an RF unit. In the present disclosure, a wireless device may refer to a communication modem / circuit / chip.

[0599] In the following, the hardware elements of the wireless devices 100 and 200 are described in detail. At least one protocol layer may be implemented by at least one processor 102 and 202, but is not limited thereto. For example, at least one processor 102 and 202 may implement at least one layer (e.g., a functional layer such as PHY, MAC, RLC, PDCP, RRC, and SDAP layers). At least one processor 102 and 202 may generate at least one protocol data unit (PDU) and / or at least one service data unit (SDU) according to the description, function, process, proposal, method, and / or operation flowchart disclosed herein. At least one processor 102 and 202 may generate a message, control information, data, or information according to the description, function, process, proposal, method, and / or operation flowchart disclosed herein. At least one processor 102 and 202 may generate a signal (e.g., a baseband signal) including a PDU, SDU, message, control information, data, or information according to the function, process, proposal, and / or method disclosed herein, and may provide a signal to at least one transceiver 106 and 206. At least one processor 102 and 202 may receive a signal (e.g., a baseband signal) from at least one transceiver 106 and 206 and may obtain a PDU, SDU, message, control information, data, or information according to the description, functions, processes, proposals, methods, and / or operational flow charts disclosed herein.

[0600] At least one processor 102 and 202 may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. At least one processor 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof. For example, at least one application-specific integrated circuit (ASIC), at least one digital signal processor (DSP), at least one digital signal processing device (DSPD), at least one programmable logic device (PLD), or at least one field programmable gate array (FPGA) may be included in at least one processor 102 and 202. The description, function, process, proposal, method, and / or operation flowchart disclosed herein may be implemented using firmware or software, and the firmware or software may be configured to include modules, processes, functions, etc. Firmware or software configured to execute the description, function, process, proposal, method, and / or operation flowchart disclosed herein may be included in at least one processor 102 and 202 or may be stored in at least one memory 104 and 204 and may be executed by at least one processor 102 and 202. The description, function, process, proposal, method, and / or operation flowchart disclosed herein may be implemented in the form of code, instructions, and / or instruction sets using firmware or software.

[0601] At least one memory 104 and 204 may be connected to at least one processor 102 and 202 and may store various forms of data, signals, messages, information, programs, codes, instructions and / or commands. At least one memory 104 and 204 may be configured as ROM, RAM, EPROM, flash memory, hard disk drive, register, cache memory, computer-readable storage medium and / or a combination thereof. At least one memory 104 and 204 may be arranged inside and / or outside of at least one processor 102 and 202. In addition, at least one memory 104 and 204 may be connected to at least one processor 102 and 202 via various technologies such as wired or wireless connections.

[0602] At least one transceiver 106 and 206 can send user data, control information, radio signals / channels, etc. mentioned in the method and / or operation flow chart disclosed herein to at least different devices. At least one transceiver 106 and 206 can receive user data, control information, radio signals / channels, etc. mentioned in the description, function, process, proposal, method and / or operation flow chart disclosed herein from at least one different device. For example, at least one transceiver 106 and 206 can be connected to at least one processor 102 and 202 and can send and receive radio signals. For example, at least one processor 102 and 202 can control at least one transceiver 106 and 206 to send user data, control information or radio signals to at least one different device. In addition, at least one processor 102 and 202 can control at least one transceiver 106 and 206 to receive user data, control information or radio signals from at least one different device. At least one transceiver 106 and 206 may be connected to at least one antenna 108 and 208 and may be configured to send or receive user data, control information, radio signals / channels, etc. mentioned in the description, functions, processes, proposals, methods and / or operation flow charts disclosed herein through at least one antenna 108 and 208. In this document, at least one antenna may be a plurality of physical antennas or may be a plurality of logical antennas (e.g., antenna ports). At least one transceiver 106 and 206 may convert received radio signals / channels from RF band signals to baseband signals so as to process received user data, control information, radio signals / channels, etc. using at least one processor 102 and 202. At least one transceiver 106 and 206 may convert user data, control information, radio signals / channels, etc. processed using at least one processor 102 and 202 from baseband signals to RF bad signals. To this end, at least one transceiver 106 and 206 may include an (analog) oscillator and / or a filter.

[0603] Fig.47 A signal processing circuit for transmitting a signal is illustrated.

[0604] refer to Fig.47 The signal processing circuit 1000 includes a scrambler 1010, a modulator 1020, a layer mapper 1030, a precoder 1040, a resource mapper 1050, and a signal generator 1060. Fig.46 The processors 102 and 202 and / or the transceivers 106 and 206 execute Fig.47 The operations / functions of, but not limited to, Fig.47 The hardware components can be found in Fig.46 102 and 202 and / or the transceivers 106 and 206. For example, the scrambler 1010 to the signal generator 1060 may be implemented in Fig.46 In addition, the scrambler 1010 to resource mapper 1050 may be implemented in the processor 102 and 202. Fig.46 is implemented in processors 102 and 202, and Fig.46 The signal generator 1060 may be implemented in the transceivers 106 and 206 of the present invention.

[0605] Codewords can be passed Fig.47 The signal processing circuit 1000 is converted into a wireless signal. Here, the codeword is a coded bit sequence of an information block. The information block may include a transport block (e.g., a UL-SCH transport block or a DL-SCH transport block). The wireless signal may be transmitted through various physical channels (e.g., PUSCH or PDSCH).

[0606] Specifically, the codeword can be converted into a scrambled bit sequence by the scrambler 1010. The scrambling sequence for scrambling is generated based on an initialization value, and the initialization value may include ID information about the wireless device. The scrambled bit sequence can be modulated into a modulation symbol sequence by the modulator 1020. The modulation scheme may include pi / 2-binary phase shift keying (pi / 2-BPSK), m-phase shift keying (m-PSK), m-quadrature amplitude modulation (m-QAM), etc. The complex modulation symbol sequence can be mapped to at least one transmission layer by the layer mapper 1030. The modulation symbol of each transmission layer can be mapped to the corresponding antenna port (precoding) by the precoder 1040. The output z from the precoder 1040 can be obtained by multiplying the output y from the layer mapper 1030 by the precoding matrix W of N*M, where N is the number of antenna ports and M is the number of transmission layers. Here, the precoder 1040 can perform precoding after performing transform precoding (e.g., DFT transform) on the complex modulation symbol. Alternatively, the precoder 1040 may perform precoding without performing transform precoding.

[0607] The resource mapper 1050 may map the modulation symbols of each antenna port to time-frequency resources. The time-frequency resources may include multiple symbols (e.g., CP-OFDMA symbols or DFT-s-OFDMA symbols) in the time domain and may include multiple subcarriers in the frequency domain. The signal generator 1060 may generate a radio signal from the mapped modulation symbols, and the generated radio signal may be sent to another device through each antenna. To this end, the signal generator 1060 may include an inverse fast Fourier transform (IFFT) module, a cyclic prefix (CP) inserter, a digital-to-analog converter (DAC), a frequency uplink converter, etc.

[0608] The signal processing process of the received signal in the wireless device can be configured as follows Fig.47 For example, a wireless device (e.g., Fig.46 100 or 200 in ) can receive a wireless signal from the outside through an antenna port / transmitter. The received wireless signal can be converted into a baseband signal by a signal restorer. To this end, the signal restorer may include a frequency downlink converter, an analog-to-digital converter (ADC), a CP canceller, and a fast Fourier transform (FFT) module. Thereafter, the baseband signal can be restored to a codeword through a resource demapper process, a post-coding process, a demodulation process, and a descrambling process. The codeword can be restored to the original information block by decoding. Therefore, a signal processing circuit (not shown) for receiving a signal may include a signal restorer, a resource demapper, a post-encoder, a demodulator, a descrambler, and a decoder.

[0609] Fig.48 Another example of a wireless device applied to the present disclosure is shown. The wireless device can be implemented in various forms according to the usage example / service (refer to Fig.45 ).

[0610] refer to Fig.48 , the wireless device (100, 200) may correspond to Fig.46 The wireless device (100, 200) may be configured by various elements, components, units / parts and / or modules. For example, each of the wireless devices (100, 200) may include a communication unit (110), a control unit (120), a memory unit (130) and an additional component (140). The communication unit may include a communication circuit (112) and a transceiver (114). For example, the communication circuit (112) may include Fig.46 One or more processors (102, 202) and / or one or more memories (104, 204) of the present invention. For example, the transceiver (114) may include Fig.46The control unit (120) is electrically connected to the communication unit (110), the memory (130) and the additional components (140) and controls the overall operation of the wireless device. For example, the control unit (120) can control the electrical / mechanical operation of the wireless device based on the program / code / instruction / information stored in the storage unit (130). The control unit (120) can send the information stored in the storage unit (130) to the outside (e.g., other communication devices) via the communication unit (110) through the wireless / wired interface or store the information received from the outside (e.g., other communication devices) via the communication unit (110) through the wireless / wired interface in the storage unit (130).

[0611] The additional components (140) may be configured differently depending on the type of wireless device. For example, the additional components (140) may include at least one of a power supply unit / battery, an input / output (I / O) unit, a drive unit, and a computing unit. The wireless device may be used in, but not limited to, a robot ( Fig.45 100a), vehicles ( Fig.45 100b-1, 100b-2), XR devices ( Fig.45 100c), handheld devices ( Fig.45 100d), household appliances ( Fig.45 100e), IoT devices ( Fig.45 100f), digital broadcast UE, holographic equipment, public safety equipment, MTC equipment, medical equipment, fintech equipment (or financial equipment), security equipment, climate / environmental equipment, AI servers / equipment ( Fig.45 400), BS( Fig.45 200), network nodes, etc. Depending on the use case / service, the wireless device can be used in a mobile or fixed location.

[0612] exist Fig.48In the wireless device (100, 200), the various elements, components, units / parts and / or modules in the wireless device (100, 200) can be connected to each other through a wired interface, or at least a part of them can be wirelessly connected through the communication unit (110). For example, in each of the wireless devices (100, 200), the control unit (120) and the communication unit (110) can be connected by wire, and the control unit (120) and the first unit (e.g., 130, 140) can be wirelessly connected through the communication unit (110). Each element, component, unit / part and / or module in the wireless device (100, 200) can further include one or more elements. For example, the control unit (120) can be configured by a collection of one or more processors. As an example, the control unit (120) can be configured by a collection of a communication control processor, an application processor, an electronic control unit (ECU), a graphics processing unit and a memory control processor. As another example, the memory (130) may be composed of random access memory (RAM), dynamic RAM (DRAM), read only memory (ROM), flash memory, volatile memory, nonvolatile memory, and / or a combination thereof.

[0613] Hereinafter, the implementation will be described in detail with reference to the accompanying drawings. Fig.48 .

[0614] Fig.49 Portable devices applied to the present disclosure are illustrated. Portable devices may include smart phones, smart tablets, wearable devices (e.g., smart watches or smart glasses), portable computers (e.g., laptops), etc. Portable devices may be referred to as mobile stations (MS), user terminals (UTs), mobile subscriber stations (MSSs), subscriber stations (SSs), advanced mobile stations (AMSs), or wireless terminals (WTs).

[0615] refer to Fig.49 , the portable device may include an antenna unit 108, a communication unit 110, a control unit 120, a memory unit 130, a power supply unit 140a-49, an interface unit 140b-49, and an input / output unit 140c-49. The antenna unit 108 may be configured as a part of the communication unit 110. Blocks 110 to 130 / 140a-49 to 140c-49 correspond to Fig.48 Blocks 110 to 130 / 140.

[0616] The communication unit 110 may send and receive signals (e.g., data, control signals, etc.) to and from other wireless devices and base stations. The control unit 120 may control various components of the handheld device to perform various operations. The control unit 120 may include an application processor (AP). The storage unit 130 may store data / parameters / programs / codes / commands required to drive the handheld device. In addition, the storage unit 130 may store input / output data / information. The power supply unit 140a-49 supplies power to the handheld device 100 and may include a wired / wireless charging circuit, a battery, etc. The interface unit 140b-49 may support the connection between the handheld device 100 and different external devices. The interface unit 140b-49 may include various ports (e.g., audio input / output ports and video input / output ports) for connecting to external devices. The input / output unit 140c-49 may receive or output image information / signals, audio information / signals, data and / or information input from a user. The input / output unit 140c-49 may include a camera, a microphone, a user input unit, a display unit 140d-49, a speaker, and / or a haptic module.

[0617] For example, in data communication, the input / output unit 140c-49 can obtain information / signals (e.g., touch, text, voice, image, and video) input from the user, and the obtained information / signals can be stored in the storage unit 130. The communication unit 110 can convert the information / signals stored in the storage unit into radio signals, and can directly send the converted radio signals to different wireless devices or base stations. In addition, the communication unit 110 can receive radio signals from different wireless devices or base stations, and can reconstruct the received radio signals into original information / signals. The reconstructed information / signals can be stored in the storage unit 130, and can then be output in various forms (e.g., text, voice, image, video, and tactile forms) through the input / output unit 140c-49.

[0618] Fig.50 The vehicle or autonomous vehicle applied to the present disclosure is illustrated. The vehicle or autonomous vehicle can be implemented as a mobile robot, a vehicle, a train, an aircraft (AV), a ship, etc.

[0619] refer to Fig.50 , the vehicle or autonomous vehicle 100-50 includes an antenna unit 108, a communication unit 110, a control unit 120, a drive unit 140a-50, a power supply unit 140b-50, a sensor unit 140c-50 and an autonomous driving unit 140d-50. The antenna unit 108 may be configured as a part of the communication unit 110. The blocks 110 / 130 / 140a-50 to 140d-50 correspond to Fig.48 Block 110 / 130 / 140.

[0620] The communication unit 110 can send and receive signals (e.g., data, control signals, etc.) to and from, for example, different vehicles, base stations (e.g., base stations, road-side units, etc.), and servers. The control unit 120 can control the elements of the vehicle or autonomous driving vehicle 100-50 to perform various operations. The control unit 120 may include an electronic control unit (ECU). The drive unit 140a-50 can enable the vehicle or autonomous driving vehicle 100-50 to travel on the ground. The drive unit 140a-50 may include an engine, a motor, a powertrain, wheels, brakes, a steering device, etc. The power supply unit 140b-50 supplies power to the vehicle or autonomous driving vehicle 100-50 and may include a wired / wireless charging circuit, a battery, etc. The sensor unit 140c-50 can obtain vehicle conditions, environmental information, user information, etc. The sensor units 140c-50 may include an inertial measurement unit (IMU) sensor, a collision sensor, a wheel sensor, a speed sensor, a tilt sensor, a weight sensor, a heading sensor, a position module, a vehicle front / rear vision sensor, a battery sensor, a fuel sensor, a tire sensor, a steering sensor, a temperature sensor, a humidity sensor, an ultrasonic sensor, an illumination sensor, a pedal position sensor, etc. The autonomous driving unit 140d-50 may implement a technology for maintaining a driving lane, a technology for automatically adjusting a speed such as an adaptive cruise control, a technology for autonomous driving along a set route, a technology for automatically setting a route and driving when setting to arrive at a destination, etc.

[0621] For example, the communication unit 110 may receive map data, traffic condition data, etc. from an external server. The autonomous driving unit 140d-50 may generate an autonomous driving route and a driving plan based on the obtained data. The control unit 120 may control the drive unit 140a-50 to move the vehicle or the autonomous driving vehicle 100-50 along the autonomous driving route according to the driving plan (e.g., speed / direction control). During autonomous driving, the communication unit 110 may obtain updated traffic condition data from an external server irregularly / regularly, and may obtain surrounding traffic condition data from neighboring vehicles. In addition, during autonomous driving, the sensor unit 140c-50 may obtain vehicle conditions and environmental information. The autonomous driving unit 140d-50 may update the autonomous driving route and driving plan based on the newly obtained data / information. The communication unit 110 may send information about the vehicle position, autonomous driving route, driving plan, etc. to an external server. The external server may use AI technology, etc. to predict traffic condition data in advance based on information collected from the vehicle or autonomous driving vehicle, and may provide the predicted traffic condition data to the vehicle or autonomous driving vehicle.

[0622] Fig.51The vehicle applied to the present disclosure is illustrated. The vehicle can also be implemented as a transportation vehicle, a train, an airplane, and a ship.

[0623] refer to Fig.51 , the vehicle 100-51 may include a communication unit 110, a control unit 120, a storage unit 130, an input / output unit 140-51, and a position measurement unit 140b-51. Here, blocks 110 to 130 / 140a-51 to 140d-51 correspond to Fig.48 Blocks 110 to 130 / 140.

[0624] The communication unit 110 can send / receive signals (e.g., data, control signals, etc.) with other vehicles or external devices such as base stations. The control unit 120 can control the components of the vehicle 100-51 to perform various operations. The storage unit 130 can store data / parameters / programs / codes / commands that support various functions of the vehicle 100-51. The input / output unit 140a-51 can output AR / VR objects based on the information in the storage unit 130. The input / output unit 140a-51 may include a HUD. The positioning unit 140b-51 can obtain the location information of the vehicle 100-51. The location information may include the absolute location information of the vehicle 100-51, the location information within the driving route, the acceleration information, the location information with the neighboring vehicles, etc. The positioning unit 140b-51 may include a GPS and various sensors.

[0625] For example, the communication unit 110 of the vehicle 100-51 may receive map information, traffic information, etc. from an external server and store it in the memory unit 130. The positioning unit 140b-51 may obtain the vehicle location information through GPS and various sensors and store it in the storage unit 130. The control unit 120 may generate a virtual object based on the map information, traffic information, vehicle location information, etc., and the input / output unit 140a-51 may display the generated virtual object on the windows (1410 and 1420) in the vehicle. In addition, the control unit 120 may determine whether the vehicle 100-51 is operating normally within the driving route based on the vehicle location information. When the vehicle 100-51 deviates abnormally from the driving route, the control unit 120 may display a warning on the windshield of the vehicle through the input / output unit 140a-51. In addition, the control unit 120 may broadcast a warning message about driving abnormality to surrounding vehicles through the communication unit 110. Depending on the situation, the control unit 120 may send the vehicle's location information and information about driving / vehicle abnormality to relevant organizations through the communication unit 110.

[0626] Fig.52The XR device applied to the present disclosure is illustrated. The XR device can be implemented as an HMD, a head-up display (HUD) provided in a vehicle, a TV, a smartphone, a computer, a wearable device, a home appliance, a digital signage, a vehicle, a robot, etc.

[0627] refer to Fig.52 , the XR device 100a-52 may include a communication unit 110, a control unit 120, a storage unit 130, an input / output unit 140a-52, a sensor unit 140b-52, and a power supply unit 140c-52. Here, blocks 110 to 130 / 140a-52 to 140c-52 correspond to Fig.48 Blocks 110 to 130 / 140.

[0628] The communication unit 110 may send / receive signals (e.g., media data, control signals, etc.) to / from an external device such as another wireless device, a portable device, or a media server. The media data may include images, images, sounds, etc. The control unit 120 may control the components of the XR device 100a-52 to perform various operations. For example, the control unit 120 may be configured to control and / or perform processes such as video / image acquisition, (video / image) encoding, and metadata generation and processing. The storage unit 130 may store data / parameters / programs / codes / commands necessary to drive the XR device 100a-52 / create an XR object. The input / output unit 140a-52 may obtain control information, data, etc. from the outside, and may output the generated XR object. The input / output unit 140a-52 may include a camera, a microphone, a user input unit, a display unit, a speaker, and / or a tactile module. The sensor unit 140b-52 may obtain the XR device status, surrounding environment information, user information, etc. The sensor unit 140b-52 may include a proximity sensor, an illumination sensor, an acceleration sensor, a magnetic sensor, a gyroscope sensor, an inertial sensor, an RGB sensor, an IR sensor, a fingerprint recognition sensor, an ultrasonic sensor, an optical sensor, a microphone, and / or a radar. The power supply unit 140c-52 supplies power to the XR device 100a-52 and may include a wired / wireless charging circuit, a battery, and the like.

[0629] For example, the storage unit 130 of the XR device 100a-52 may include information (e.g., data, etc.) required for generating an XR object (e.g., an AR / VR / MR object). The input / output unit 140a-52 may obtain a command to operate the XR device 100a-52 from the user, and the control unit 120 may drive the XR device 100a-52 according to the user's drive command. For example, when the user wants to watch a movie or news through the XR device 100a-52, the control unit 120 sends content request information to another device (e.g., the mobile device 100b-52) through the communication unit 130 or may send it to a media server. The communication unit 130 may download / stream content such as movies and news from another device (e.g., the portable device 100b-52) or a media server to the storage unit 130. The control unit 120 controls and / or performs processes such as video / image acquisition, (video / image) encoding, and metadata generation / processing of content, and acquires through the input / output units 140a-52 / sensor units 140b-52. The XR object can be generated / output based on information about a surrounding space or a real object.

[0630] In addition, the XR device 100a-52 is wirelessly connected to the portable device 100b-52 through the communication unit 110, and the operation of the XR device 100a-52 can be controlled by the portable device 100b-52. For example, the portable device 100b-52 can be used as a controller of the XR device 100a-52. To this end, the XR device 100a-52 can obtain the 3D position information of the portable device 100b-52, and then generate and output the XR object corresponding to the portable device 100b-52.

[0631] Fig.53 The robot applied to the present disclosure is illustrated. Depending on the purpose or field of use, the robot can be classified into industrial, medical, household, military, etc.

[0632] refer to Fig.53 , the robot 100-53 may include a communication unit 110, a control unit 120, a storage unit 130, an input / output unit 140a-53, a sensor unit 140b-53, and a drive unit 140c-53. Here, blocks 110 to 130 / 140a-53 to 140d-53 correspond to Fig.48 Blocks 110 to 130 / 140.

[0633] The communication unit 110 may send / receive signals (e.g., driving information, control signals, etc.) to / from external devices such as other wireless devices, other robots, or control servers. The control unit 120 may perform various operations by controlling the components of the robot 100-53. The storage unit 130 may store data / parameters / programs / codes / commands that support various functions of the robot 100-53. The input / output unit 140a-53 may obtain information from the outside of the robot 100-53 and may output the information to the outside of the robot 100-53. The input / output unit 140a-53 includes a camera, a microphone, a user input unit, a display unit, a speaker, and / or a tactile module. The sensor unit 140b-53 may obtain internal information, surrounding environment information, user information, etc. of the robot 100-53. The sensor unit 140b-53 may include a proximity sensor, an illumination sensor, an acceleration sensor, a magnetic sensor, a gyroscope sensor, an inertial sensor, an IR sensor, a fingerprint recognition sensor, an ultrasonic sensor, an optical sensor, a microphone, a radar, and the like. The drive unit 140c-53 can perform various physical operations, such as moving the robot joints. In addition, the drive unit 140c-53 can make the robot 100-53 walk on the ground or fly in the air. The drive unit 140c-53 may include an actuator, a motor, a wheel, a brake, a propeller, etc.

[0634] Fig.54 The AI ​​device applied to the present disclosure is illustrated. The AI ​​device can be implemented as a fixed device or a mobile device, such as a TV, a projector, a smart phone, a PC, a laptop, a digital broadcast UE, a tablet, a wearable device, a set-top box (STB), a radio, a washing machine, a refrigerator, a digital signage, a robot, a vehicle, etc.

[0635] refer to Fig.54 , the AI ​​device 100-54 may include a communication unit 110, a control unit 120, a memory unit 130, an input / output unit 140a / 140b-54, a learning processor unit 140c-54, and a sensor unit. Blocks 110 to 130 / 140a-54 to 140d-54 correspond to Fig.48 Blocks 110 to 130 / 140.

[0636] The communication unit 110 can use wired / wireless communication technology to communicate with another AI device or an AI server (e.g., Fig.45 To this end, the communication unit 110 may send information in the storage unit 130 to the external device, or may transmit a signal received from the external device to the storage unit 130.

[0637] The control unit 120 may determine at least one executable operation of the AI ​​device 100-54 based on information determined or generated using a data analysis algorithm or a machine learning algorithm. In addition, the control unit 120 may perform the determined operation by controlling the components of the AI ​​device 100-54. For example, the control unit 120 may request, search, receive, or utilize data from the learning processor unit 140c-54 or the memory unit 130, and may control the components of the AI ​​device 100-54 to perform a predicted operation in at least one of the executable operations or operations determined to be desirable. In addition, the control unit 120 may collect historical information including the operation content of the AI ​​device 100-54 or the user's feedback on the operation, and store the collected information in the storage unit 130 or the learning processor unit 140c-54 or send the information to a storage unit such as an AI server ( Fig.45 The collected historical information can be used to update the learning model.

[0638] The storage unit 130 may store data for supporting various functions of the AI ​​devices 100-54. For example, the storage unit 130 may store data obtained from the input units 140a-54, data obtained from the communication unit 110, output data from the learning processor unit 140c-54, and data obtained from the sensing unit 140. In addition, the storage unit 130 may store control information and / or software codes required for the operation / execution of the control unit 120.

[0639] The input units 140a-54 may obtain various types of data from outside the AI ​​device 100. For example, the input units 140a-54 may obtain learning data for model learning and input data to which the learning model is applied. The input units 140a-54 may include a camera, a microphone, and / or a user input unit. The output units 140b-54 may generate visual, auditory, or tactile outputs. The output units 140b-54 may include a display unit, a speaker, and / or a tactile module. The sensing unit 140 may use various sensors to obtain at least one of internal information about the AI ​​device 100-54, environmental information about the AI ​​device 100-54, and user information. The sensing unit 140 may include a proximity sensor, an illumination sensor, an acceleration sensor, a magnetic sensor, a gyroscope sensor, an inertial sensor, an RGB sensor, an IR sensor, a fingerprint sensor, an ultrasonic sensor, an optical sensor, a microphone, and / or a radar.

[0640] The learning processor unit 140c-54 may train a model configured as an artificial neural network using training data. The learning processor unit 140c-54 may perform AI processing together with a learning processor unit of an AI server. The learning processor unit 140c-54 may process information received from an external device through the communication unit 110 and / or information stored in the memory unit 130. In addition, an output value of the learning processor unit 140c-54 may be sent to an external device through the communication unit 110 and / or may be stored in the memory unit 130.

Claims

1. A method for operating a first parent distributed unit DU in an integrated access and backhaul IAB system, the method comprising: Receive DU resource configuration information of the second parent DU (S3410); as well as determining whether transmission or reception with the IAB node in a specific resource is possible based on the DU configuration information of the second parent DU (S3420), The DU configuration information of the second parent DU includes information about availability of resources configured for the second parent DU, The information about the availability of the resource configured for the second parent DU informs whether the specific resource is a hard resource, a soft resource or an unavailable NA resource, and Wherein, based on i) the mobile terminal IAB-MT of the IAB node is configured with the first parent DU included in the main cell group MCG and the second parent DU included in the secondary cell group SCG, ii) the IAB-MT cannot transmit and receive at the same time, iii) the IAB-MT will transmit and receive on the first parent DU and the second parent DU at the same time, and iv) specific time resources configured by both the first parent DU and the second parent DU, the operation of the IAB-MT is performed based on the scheduling of the first parent DU included in the MCG.

2. The method according to claim 1, wherein: The first parent DU communicates with the IAB-MT.

3. The method according to claim 2, wherein: The second parent DU communicates with the IAB-MT.

4. The method according to claim 3, wherein: Based on the DU configuration for the first parent DU and the DU configuration for the second parent DU, it is determined whether the first parent DU can communicate with the IAB-MT in the specific resource.

5. A wireless device, comprising: at least one memory (104), the at least one memory (104) storing instructions; at least one transceiver (106); as well as At least one processor (102), the at least one processor (102) coupled to the at least one memory (104) and the at least one transceiver (106), wherein the at least one memory (104) stores instructions to enable the at least one processor (102) to perform operations, the operations comprising: receiving DU resource configuration information of a second parent DU (S3410); and determining whether transmission or reception with the IAB node in a specific resource is possible based on the DU configuration information of the second parent DU (S3420), The DU configuration information of the second parent DU includes information about availability of resources configured for the second parent DU, The information about the availability of the resource configured for the second parent DU informs whether the specific resource is a hard resource, a soft resource or an unavailable NA resource, and Wherein, based on i) the mobile terminal IAB-MT of the IAB node is configured with a first parent DU included in a main cell group MCG and a second parent DU included in a secondary cell group SCG, ii) the IAB-MT cannot transmit and receive at the same time, iii) the IAB-MT will transmit and receive on the first parent DU and the second parent DU at the same time, and iv) specific time resources configured by both the first parent DU and the second parent DU, the operation of the IAB-MT is performed based on the scheduling of the first parent DU included in the MCG.

Images