Method of operation of a du of a parent node in communication with a mt of an iab node in a wireless communication system and apparatus using the same

Abstract

An operation method performed by a first distributed unit (DU) of a first parent node communicating with a mobile terminal (MT) of an IAB node in a wireless communication system and an apparatus using the same are provided. The first parent node acquires first configuration information about the first DU, acquires second configuration information about a second DU of a second parent node communicating with the MT, and limits downlink transmission or uplink link reception operation of the first DU based on the first configuration information and the second configuration information if a predetermined condition is satisfied.

Description

Technical Field

[0001] The present invention relates to a method of operating a distributed unit (DU) of a parent node communicating with a mobile terminal (MT) of an IAB node in a wireless communication system, and an apparatus using the method. Background Technology

[0002] With an increasing number of communication devices requiring greater communication capacity, there is a need to improve mobile broadband communications on top of existing radio access technologies. Furthermore, massive machine-type communication (MTC), which provides various services by connecting numerous devices and objects, is one of the main issues to be considered in next-generation communications. In addition, communication system designs considering reliability / latency-sensitive services / UEs are being discussed. The introduction of next-generation radio access technologies considering enhanced mobile broadband communication (eMBB), massive MTC (mMTC), and ultra-reliable low-latency communication (URLLC) is discussed. For convenience, this new technology may be referred to in this disclosure as a new radio access technology (new RAT or NR).

[0003] In NR, massive MIMO or multi-beam may be used, and a very large amount of bandwidth is expected to be available compared to LTE. Integrated access and backhaul (IAB) nodes are also expected to be developed and deployed.

[0004] An IAB node can be a node that supports wireless connectivity to terminals, much like a repeater, based on a multi-hop wireless backhaul (connection to a parent or donor node). An IAB node can include a Distributed Unit (DU) and a Mobile Terminal (MT). Here, the DU can be the part providing connectivity to terminals or other IAB nodes, while the MT can be the part providing connectivity to a parent or donor node.

[0005] IAB nodes can support dual connectivity (DC). DC refers to the technology by which an IAB node simultaneously uses radio resources provided by multiple base stations (or parent nodes).

[0006] An IAB node, connected to two parent nodes via a dual-connection, can set different resource directions for the same resource. For example, the first parent node can set a specific resource as a downlink, while the second parent node can set the same resource as an uplink. In this case, it is necessary to define how the first parent node, the second parent node, and the IAB node should operate. Summary of the Invention

[0007] Technical issues

[0008] One object of this disclosure is to provide a method of operating a distributed unit (DU) of a parent node that communicates with a mobile terminal (MT) of an IAB node, and an apparatus for using the method.

[0009] Technical solution

[0010] In one aspect, a method of operation is provided in a wireless communication system performed by a first distributed unit (DU) of a first parent node communicating with a mobile terminal (MT) of an IAB node. The method includes: obtaining first configuration information for the first DU, obtaining second configuration information for a second DU communicating with a second parent node of the MT, and restricting downlink transmission or uplink reception of the first DU based on the first and second configuration information.

[0011] On the other hand, a first distributed unit (DU) of a first parent node is provided for communication with a mobile terminal (MT) of an IAB node. The first DU includes a transceiver, at least one memory, and at least one processor operatively coupled to the at least one memory and the transceiver. The processor is configured to: obtain first configuration information for the first DU; obtain second configuration information for a second DU for communication with a second parent node of the MT; and restrict downlink transmission or uplink reception of the first DU based on the first and second configuration information.

[0012] In another aspect, an apparatus is provided for a first distributed unit (DU) of a first parent node communicating with a mobile terminal (MT) of an IAB node. The apparatus includes at least one memory and at least one processor operatively coupled to said at least one memory. The processor is configured to: obtain first configuration information for the first DU, obtain second configuration information for a second DU communicating with a second parent node of the MT, and restrict downlink transmission or uplink reception of the first DU based on the first and second configuration information.

[0013] In another aspect, at least one computer-readable medium (CRM) is provided having instructions to be executed by at least one processor to perform operations including: obtaining first configuration information of a first distributed unit (DU) of a first parent node communicating with a mobile terminal (MT) of an IAB node, obtaining second configuration information of a second DU of a second parent node communicating with the MT, and restricting downlink transmission or uplink reception of the first DU based on the first and second configuration information.

[0014] In another aspect, a method for operating a wireless communication system is provided, the wireless communication system including a first distributed unit (DU) of a first parent node and a mobile terminal (MT) of an IAB node. The method includes: obtaining first configuration information for the first DU; obtaining second configuration information for a second DU of a second parent node for communicating with the MT; and, based on the first and second configuration information, having the MT receive signals transmitted by the first DU or have the first DU receive signals transmitted by the MT. Based on the first and second configuration information, and based on determining that the first and second DUs are configured to perform simultaneous operations on specific resources that the MT does not support, the first DU restricts operations according to the first configuration information.

[0015] Beneficial effects

[0016] When an IAB node connects to two parent nodes using the DC method, if both parent nodes are scheduled to perform concurrent operations that the IAB node does not support in a specific resource, one parent node will not operate and only the other parent node will operate. Therefore, concurrent operations that the IAB node does not support can be prevented. Attached Figure Description

[0017] Figure 1 This illustrates a wireless communication system to which this disclosure can be applied.

[0018] Figure 2 This is a diagram illustrating the wireless protocol architecture used for the user plane.

[0019] Figure 3 This is a diagram illustrating the wireless protocol architecture used for the control plane.

[0020] Figure 4 The diagram illustrates the system architecture of a next-generation radio access network (NG-RAN) using NR.

[0021] Figure 5 The diagram illustrates the functional division between NG-RAN and 5GC.

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

[0023] Figure 7 The diagram illustrates the time slot structure of an NR frame.

[0024] Figure 8 The diagram shows CORESET.

[0025] Figure 9 This is a diagram illustrating the differences between the control area in the prior art and the CORESET in NR.

[0026] Figure 10The illustration shows an example of a frame structure used for new radio access technologies.

[0027] Figure 11 The diagram illustrates the structure of a self-contained time slot.

[0028] Figure 12 The diagram illustrates the physical channel and typical signal transmission.

[0029] Figure 13 The illustration shows an example of a network with integrated access and backhaul (IAB).

[0030] Figure 14 This diagram illustrates an example of the configuration of access and backhaul links.

[0031] Figure 15 The diagram illustrates an IAB node operating in Standalone (SA) mode or Non-Standalone (NSA) mode.

[0032] Figure 16 The diagram illustrates the backhaul link and the access link.

[0033] Figure 17 The diagram illustrates the parent and child links.

[0034] Figure 18 This example demonstrates the use of multiple CCs in the MT and DU of an IAB node.

[0035] Figure 19 The diagram shows the timing alignment situation 1.

[0036] Figure 20 The diagram shows the timing alignment status 6.

[0037] Figure 21 The diagram shows the timing alignment status (7).

[0038] Figure 22 The diagram shows MT and DU in the IAB node.

[0039] Figure 23 Scenario 1 is shown in the diagram.

[0040] Figure 24 Another example is shown in which IAB MT1 is connected to two parent DUs.

[0041] Figure 25 Another example is shown in which IAB MT1 is connected to two parent DUs.

[0042] Figure 26 This shows another example of connecting IAB MT1 and two parent DUs.

[0043] Figure 27The diagram illustrates the operation performed by the first DU of the first parent node communicating with the IAB node in a wireless communication system.

[0044] Figure 28 The diagram is based on Figure 27 The detailed operation methods for the first parent node, IAB node, and second parent node are described below.

[0045] Figure 29 This example illustrates a method for determining whether the first DU of the first parent node will perform an operation based on the first configuration information.

[0046] Figure 30 This is an example of how to operate an IAB node.

[0047] Figure 31 The illustration shows an example of a wireless communication device used to implement this disclosure.

[0048] Figure 32 An example of the structure of a signal processing module is shown.

[0049] Figure 33 This shows another example of the structure of a signal processing module in a transmission device.

[0050] Figure 34 The illustration shows an example of a wireless communication device according to an embodiment of the present disclosure.

[0051] Figure 35 An example of a processor 2000 is shown.

[0052] Figure 36 An example of processor 3000 is shown.

[0053] Figure 37 Another example of a wireless device is shown.

[0054] Figure 38 Another example of a wireless device used in this specification is shown.

[0055] Figure 39 The illustration is for a handheld device used in this manual.

[0056] Figure 40 The diagram illustrates the communication system 1 used in this specification.

[0057] Figure 41 The illustrations are applicable to the vehicles or autonomous vehicles described in this manual. Detailed Implementation

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

[0059] The forward slash ( / ) or comma used in this specification may mean "and / or". For example, "A / B" may mean "A and / or B". Therefore, "A / B" may mean "A only", "B only", or "both A and B". For example, "A, B, C" may mean "A, B, or C".

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

[0061] Furthermore, in this specification, "at least one of A, B, and C" may mean "A only", "B only", "C only" or "any combination of A, B, and C". Additionally, "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".

[0062] Furthermore, the parentheses used in this specification may mean "for example". Specifically, when indicated as "Control Information (PDCCH)", it may mean that "PDCCH" is presented as an example of "Control Information". That is, "Control Information" in this specification is not limited to "PDCCH", and "PDCCH" may be presented as an example of "Control Information". In addition, when indicated as "Control Information (i.e., PDCCH)", it may also mean that "PDCCH" is presented as an example of "Control Information".

[0063] The technical features described individually in a single figure in this specification can be implemented individually or simultaneously.

[0064] Figure 1 This illustrates a wireless communication system to which this disclosure can be applied. This 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.

[0065] E-UTRAN includes at least one base station (BS) 20, which provides the control plane and user plane to user equipment (UE) 10. UE 10 can be fixed or mobile, and can be referred to by other terms such as mobile station (MS), user terminal (UT), subscriber station (SS), mobile terminal (MT), radio equipment, etc. BS 20 is typically a fixed station that communicates with UE 10, and can be referred to by other terms such as evolved Node B (eNB), base transceiver system (BTS), access point, gNB, etc.

[0066] BS 20 interconnects with each other using the X2 interface. BS 20 also connects to the evolved packet core (EPC) 30 using the S1 interface, and more specifically, connects to the Mobility Management Entity (MME) via the S1-MME, and to the Serving Gateway (S-GW) via the S1-U.

[0067] EPC 30 includes an MME, an S-GW, and a Packet Data Network Gateway (P-GW). The MME holds UE access information or UE capability information, and this information is typically used for UE mobility management. The S-GW is a gateway with an E-UTRAN as its endpoint. The P-GW is a gateway with a PDN as its endpoint.

[0068] The radio interface protocol between the UE and the network can be layered based on the lower three layers of the Open Systems Interconnection (OSI) model, which is well-known in communication systems: Layer 1 (L1), Layer 2 (L2), and Layer 3 (L3). Among these, the Physical (PHY) layer, belonging to Layer 1, provides messaging services using physical channels, while the Radio Resource Control (RRC) layer, belonging to Layer 3, controls radio resources between the UE and the network. For this purpose, the RRC layer exchanges RRC messages between the UE and the BS.

[0069] Figure 2 This is a diagram illustrating the wireless protocol architecture used for the user plane. Figure 3 This diagram illustrates the wireless protocol architecture used for the control plane. The user plane is the protocol stack used for user data transmission. The control plane is the protocol stack used for control signal transmission.

[0070] refer to Figure 2 and 3 The PHY layer provides information transmission services to higher layers (i.e., higher layers) via physical channels. The PHY layer connects to the Media Access Control (MAC) layer via a transport channel, which is the layer above the PHY layer. Data is transmitted between the MAC and PHY layers via the transport channel. Transport channels are classified according to how data is transmitted via the radio interface and what characteristics of the data are transmitted.

[0071] Through the physical channel, data moves between different PHY layers, i.e., between the PHY layers of the transmitter and receiver. The physical channel can be modulated according to an orthogonal frequency division multiplexing (OFDM) scheme and uses time and frequency as radio resources.

[0072] The functions of the MAC layer include mapping between logical channels and transport channels, and multiplexing / demultiplexing transport blocks provided on the physical channel over the transport channel of MAC Service Data Units (SDUs) that belong to the logical channel. The MAC layer provides services to the Radio Link Control (RLC) layer through the logical channel.

[0073] The RLC layer's functions include the concatenation, splitting, and reassembly of RLC SDUs. To ensure the quality of service (QoS) of various types of services requested via radio bearers (RBs), the RLC layer provides three operating modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). AM RLC provides error correction through Automatic Repeat Request (ARQ).

[0074] The RRC layer is defined only in the control plane. The RRC layer relates to the configuration, reconfiguration, and release of radio bearers, and is responsible for the control of logical channels, transport channels, and physical channels. RB refers to the logical path provided by Layer 1 (PHY layer) and Layer 2 (MAC layer, RLC layer, and PDCP layer) to facilitate data transfer between the UE and the network.

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

[0076] RB configuration refers to the process of defining the characteristics of the radio protocol layer and channel to provide a specific service and configuring each detailed parameter and operation method. RBs can be divided into two types: Signaling RBs (SRBs) and Data RBs (DRBs). SRBs are used as channels to transmit RRC messages on the control plane, while DRBs are used as channels to transmit user data on the user plane.

[0077] If an RRC connection is established between the UE's RRC layer and the E-UTRAN's RRC layer, the UE is in an RRC connected state. Otherwise, the UE is in an RRC idle state.

[0078] The downlink transport channels through which data is transmitted from the network to the UE include the Broadcast Channel (BCH) for transmitting system information and the Shared Downlink Channel (SCH) for transmitting user service or control messages. Service or control messages used for downlink multicast or broadcast services can be transmitted via the downlink SCH or via an additional downlink multicast channel (MCH). Similarly, the uplink transport channels through which data is transmitted from the UE to the network include the Random Access Channel (RACH) for transmitting initial control messages and the Shared Uplink Channel (SCH) for transmitting user service or control messages.

[0079] The logical channels placed above and mapped to the transport channel include the Broadcast Control Channel (BCCH), Paging Control Channel (PCCH), Common Control Channel (CCCH), Multicast Control Channel (MCCH), and Multicast Service Channel (MTCH).

[0080] A physical channel comprises several OFDM symbols in the time domain and several subcarriers in the frequency domain. A subframe comprises multiple OFDM symbols in the time domain. An RB (Resource Allocation Unit) is a resource allocation unit and comprises multiple OFDM symbols and multiple subcarriers. Furthermore, each subframe may use specific subcarriers of a specific OFDM symbol (e.g., the first OFDM symbol) for the Physical Downlink Control Channel (PDCCH), i.e., the L1 / L2 control channel. The Transmission Time Interval (TTI) is the unit of time used for subframe transmission.

[0081] The new radio access technologies (new RAT, NR) will be described below.

[0082] With an increasing number of communication devices requiring greater communication capacity, there is a need for improved mobile broadband communications compared to existing radio access technologies. Furthermore, massive machine-type communication (MTC), which provides various services by connecting numerous devices and objects, is one of the main issues to be considered in next-generation communications. In addition, communication system designs considering reliability / latency-sensitive services / UEs are being discussed. The introduction of next-generation radio access technologies considering enhanced mobile broadband (eMBB), massive mobile communication (mMTC), and ultra-reliable low-latency communication (URLLC) is discussed. For convenience, in this disclosure, such new technologies may be referred to as new radio access technologies (new RAT or NR).

[0083] Figure 4 The illustration shows another example of a wireless communication system that can be applied to this disclosure.

[0084] refer to Figure 4 NG-RAN may include gNBs and / or ng-eNBs that provide user plane and control plane protocol termination to the UE. Figure 4 The diagram only includes the gNB case. The gNB and eNB are connected via the Xn interface. The gNB and eNB are connected to the 5G core network (5GC) via the NG interface. More specifically, the gNB and eNB are connected to the Access and Mobility Management Function (AMF) via the NG-C interface and to the User Plane Function (UPF) via the NG-U interface.

[0085] Figure 5 The diagram illustrates the functional division between NG-RAN and 5GC.

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

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

[0088] refer to Figure 6 In NR, radio frames (hereinafter referred to as frames) can be used for both uplink and downlink transmissions. A frame has a length of 10 ms and can be defined as two 5 ms half-frames (half-frame, HF). A half-frame can be defined as five 1 ms subframes (subframe, SF). A subframe can be divided into one or more time slots, and the number of time slots in a subframe depends on the subcarrier spacing (SCS). Each time slot includes 12 or 14 OFDM(A) symbols depending on the cyclic prefix (CP). When using a standard CP, each time slot includes 14 symbols. When using an extended CP, each time slot includes 12 symbols. Here, symbols can include OFDM symbols (or CP-OFDM symbols) and SC-FDMA symbols (or DFT-s-OFDM symbols).

[0089] Table 1 below illustrates the subcarrier spacing configuration μ.

[0090] [Table 1]

[0091]

[0092] Table 2 below illustrates the number of time slots (N) in a frame configured with subcarrier spacing μ. frame,μ slot ), number of time slots in subframes (N) subframe,μ slot ), Number of symbols in a time slot (N) slotsymb )wait.

[0093] [Table 2]

[0094]

[0095] exist Figure 6 In the example, μ = 0, 1, 2 and 3 are exemplified.

[0096] Table 2-1 below illustrates that, when using extended CP, the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary depending on the SCS.

[0097] [Table 2-1]

[0098] μ <![CDATA[N slot symb ]]> <![CDATA[N frame,u slot ]]> <![CDATA[N subframe,u slot ]]> 2 12 40 4

[0099] In NR systems, OFDM(A) parameter sets (e.g., SCS, CP length, etc.) can be configured differently across multiple cells integrated into a single UE. Therefore, the (absolute time) duration of time resources (e.g., SF, time slots, or TTI) configured with the same number of symbols (collectively referred to as Time Units (TUs) for convenience) can be configured differently across integrated cells.

[0100] Figure 7 The diagram illustrates the time slot structure of an NR frame.

[0101] A time slot comprises multiple symbols in the time domain. For example, in the case of normal CP, a time slot may include 7 symbols. However, in the case of extended CP, a time slot may include 6 symbols. A carrier may include multiple subcarriers in the frequency domain. A resource block (RB) can be defined as multiple consecutive subcarriers in the frequency domain (e.g., 12 subcarriers). A bandwidth portion (BWP) can be defined as multiple consecutive (P)RBs in the frequency domain and may correspond to a set of parameters (e.g., SCS, CP length, etc.). A carrier may include up to N (e.g., 5) BWPs. Data communication is performed through active BWPs, and only one BWP can be activated for a UE. Each element in the resource grid is called a resource element (RE) and can be mapped to a complex symbol.

[0102] The Physical Downlink Control Channel (PDCCH) may include one or more Control Channel Elements (CCEs), as illustrated in Table 3 below.

[0103] [Table 3]

[0104] Aggregation Level CCE quantity 1 1 2 2 4 4 8 8 16 16

[0105] In other words, PDCCH can be transmitted using resources comprising 1, 2, 4, 8, or 16 CCEs. Here, a CCE comprises six Resource Element Groups (REGs), and a REG comprises a resource block in the frequency domain and an orthogonal frequency division multiplexing (OFDM) symbol in the time domain.

[0106] Monitoring refers to decoding each PDCCH candidate according to the downlink control information (DCI) format. The UE monitors (described below) a set of PDCCH candidates in one or more CORESETs on the active DL BWP of each active serving cell, wherein PDCCH monitoring is configured for each active serving cell according to the corresponding search space set.

[0107] In NR, a new element called the Control Resource Set (CORESET) can be introduced. The UE can receive the PDCCH from the CORESET.

[0108] Figure 8 The diagram shows CORESET.

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

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

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

[0112] Figure 9 This is a diagram illustrating the differences between the control area in the prior art and the CORESET in NR.

[0113] refer to Figure 9In existing wireless communication systems (e.g., LTE / LTE-A), the control area 800 is configured across the entire system frequency band used by the base station (BS). All UEs, except those supporting only narrowband signals (e.g., eMTC / NB-IoT UEs), must be able to receive radio signals across the entire system frequency band of the BS in order to properly receive / decode control information transmitted by the BS.

[0114] On the other hand, in NR, the aforementioned CORESET is introduced. CORESETs 801, 802, and 803 are radio resources used for control information to be received by the UE, and can use only a portion, rather than the entire system bandwidth in the frequency domain. The BS can allocate CORESETs to each UE and can transmit control information through the allocated CORESETs. For example, in Figure 9 In this configuration, the first CORESET 801 can be assigned to UE 1, the second CORESET 802 can be assigned to UE 2, and the third CORESET 803 can be assigned to UE 3. In NR, the UE can receive control information from the BS without having to receive the entire system frequency band.

[0115] CORESET can include UE-specific CORESET for sending UE-specific control information and public CORESET for sending control information common to all UEs.

[0116] Simultaneously, depending on the application, NR may require high reliability. In such cases, the target block error rate (BLER) of downlink control information (DCI) transmitted via a downlink control channel (e.g., physical downlink control channel (PDCCH)) can be significantly reduced compared to conventional technologies. As an example of a method to meet the requirement of 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, 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 spatial domain.

[0117] The following technologies / features can be applied in NR.

[0118] <Self-contained subframe structure>

[0119] Figure 10 The illustration shows an example of a frame structure used for new radio access technologies.

[0120] In NR, to minimize latency, such as Figure 10 As shown, a frame structure can be considered that allows control channels and data channels to be time-division multiplexed within a single TTI.

[0121] exist Figure 10In the diagram, the shaded area represents the downlink control area, and the black area represents the uplink control area. The remaining area can be used for either downlink (DL) data transmission or uplink (UL) data transmission. This structure is characterized by sequentially performing DL and UL transmissions within a subframe, thus enabling the transmission of DL data and the reception of UL ACK / NACK within that subframe. Therefore, it reduces the time required from the occurrence of a data transmission error to data retransmission, thereby minimizing latency in the final data transmission.

[0122] In this subframe structure where data and control are handled by TMD, time gaps may be needed for base stations and terminals to switch from transmit mode to receive mode or vice versa. Therefore, some OFDM symbols during the DL to UL switch can be set as guard periods (GP) in a self-contained subframe structure.

[0123] Figure 11 The diagram illustrates the structure of a self-contained time slot.

[0124] In an NR system, a timeslot includes the DL control channel, DL or UL data channel, UL control channel, etc. For example, the first N symbols in a timeslot can be used to transmit the DL control channel (hereinafter, the DL control area), and the last M symbols in the timeslot can be used to transmit the UL control channel (hereinafter, the UL control area). N and M are both integers of 0 or greater. The resource area located between the DL and UL control areas (hereinafter, the data area) can be used for the transmission of either DL or UL data. As an example, a timeslot can correspond to one of the following configurations. Each time slot is listed in chronological order.

[0125] 1. DL configuration only

[0126] 2. UL only

[0127] 3. Hybrid UL-DL configuration

[0128] -DL area + GP (protection period) + UL control area

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

[0130] DL regions: (i) DL data region, (ii) DL control region + DL data region.

[0131] UL Area: (i) UL Data Area, (ii) UL Data Area + UL Control Area. PDCCH can be transmitted in the DL Control Area, and PDSCH can be transmitted in the DL Data Area. PUCCH can be transmitted in the UL Control Area, and PUSCH can be transmitted in the UL Data Area. Downlink Control Information (DCI), such as DL data scheduling information or UL data scheduling information, can be transmitted in the PDCCH. Uplink Control Information (UCI), such as ACK / NACK (positive / negative acknowledgment) information, Channel State Information (CSI) information, or Scheduling Request (SR), can be transmitted in the PUCCH. GP provides a time gap during the transition from transmit mode to receive mode by the gNB and UE, or during the transition from receive mode to transmit mode by the gNB and UE. A portion of the symbols within a subframe corresponding to the mode transition from DL to UL can be configured as GP.

[0132] <Simulated Beamforming #1>

[0133] 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 a total of 100 antenna elements can be installed in a two-dimensional array with a spacing of 0.5λ (wavelength) in a 5×5 cm panel. Therefore, a large number of antenna elements can be used in mmW to increase beamforming (BF) gain, thereby increasing coverage or improving throughput.

[0134] In this scenario, if a transceiver unit (TXRU) is provided to adjust the transmit power and phase of each antenna element, independent beamforming for each frequency resource can be performed. However, installing TXRUs for all approximately 100 antenna elements reduces cost efficiency. Therefore, a method is considered that maps a large number of antenna elements to a single TXRU and uses analog phase shifters to control the beam direction. This analog beamforming can only form a single beam direction across all frequency bands and therefore cannot provide frequency-selective beamforming.

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

[0136] <Simulated Beamforming #2>

[0137] When multiple antennas are used in NR, hybrid beamforming, a combination of digital and analog beamforming, emerges. Here, in analog beamforming (or RF beamforming), precoding (or combination) is performed at the RF end, thus achieving performance similar to digital beamforming while reducing the number of RF chains and D / A (or A / D) converters. For convenience, the hybrid beamforming structure can be represented by N TXRUs and M physical antennas. Then, digital beamforming for the L data layers to be transmitted at the transmitter can be represented by an N x L matrix, and the converted N digital signals are converted into analog signals via TXRUs, and analog beamforming, represented by an M x N matrix, is applied.

[0138] System information for the NR system can be broadcast. In this case, analog beams belonging to different antenna panels can be transmitted simultaneously within a single symbol. A scheme is being discussed to introduce a beam RS (BRS) as a reference signal (RS) transmitted by applying a single analog beam (corresponding to a specific antenna panel) to measure the channel of each analog beam. A BRS can be defined for multiple antenna ports, and each antenna port of the BRS can correspond to a single analog beam. In this case, unlike the BRS, a synchronization signal or xPBCH can be transmitted by applying all analog beams within a group of analog beams so that it can be correctly received by any UE.

[0139] In NR, in the time domain, a synchronization signal block (SSB, or also known as synchronization signal and physical broadcast channel (SS / PBCH)) can include four OFDM symbols indexed in ascending order from 0 to 3 within the synchronization signal block, and the primary synchronization signal (PSS), secondary synchronization signal (SSS), and PBCH associated with the demodulation reference signal (DMRS) can be mapped to these symbols. As mentioned above, the synchronization signal block can also be represented by an SS / PBCH block.

[0140] In NR, since multiple synchronization signal blocks (SSBs) can be transmitted at different times, and SSBs can be used to perform initial access (IA), serving cell measurements, etc., it is preferable to transmit the SSB first when the transmission time and resources of the SSB overlap with those of other signals. For this purpose, the network can broadcast the transmission time and resource information of the SSBs, or indicate them through UE-specific RRC signaling.

[0141] In NR, transmission and reception can be performed based on beams. If the reception performance of the currently serving beam degrades, a process called beam fault recovery (BFR) can be performed to search for a new beam.

[0142] Since the BFR procedure is not intended to declare an error or failure in the link between the network and the UE, it can be assumed that the connection with the current serving cell is maintained even when the BFR procedure is performed. During the BFR procedure, measurements can be performed using different beams configured by the network (which can be represented by CSI-RS port or Synchronization Signal Block (SSB) index), and the optimal beam for the corresponding UE can be selected. The UE can perform the BFR procedure in the same way that it performs the RACH procedure associated with the beam that produces good measurement results.

[0143] The Transmission Configuration Indicator (hereinafter referred to as TCI) state will now be described. The TCI state can be configured for each CORESET of the control channel, and the parameters used to determine the RX beam for the UE can be determined based on the TCI state.

[0144] For each DL BWP of the serving cell, the UE can be configured for three or fewer CORESETs. In addition, the UE can receive the following information for each CORESET.

[0145] 1) CORESET index p (e.g., one of 0 to 11, where the index of each CORESET can be uniquely determined among the BWPs of a serving cell),

[0146] 2) PDCCH DM-RS scrambling sequence initialization values,

[0147] 3) The duration of CORESET in the time domain (which can be given in sign units),

[0148] 4) Resource block set,

[0149] 5) CCE-to-REG mapping parameters,

[0150] 6) Antenna port quasi-co-addressing (QCL) information (from a set of antenna port quasi-co-addressing provided by a higher-level parameter called "TCI-State") indicates the quasi-co-addressing (QCL) information of the DM-RS antenna ports used to receive the PDCCH in each CORESET.

[0151] 7) Indications of the presence of the Transport Configuration Indicator (TCI) field for a specific DCI format, sent by the PDCCH in CORESET, etc.

[0152] Quasi-co-located (QCL) will be described. Two antenna ports are considered quasi-co-located (QCLed) if the characteristics of the channel through which a symbol is transmitted on one antenna port can be inferred from the characteristics of the channel through which a symbol is transmitted on the other antenna port. For example, when two signals A and B are transmitted from the same transmit antenna array with the same / similar spatial filters applied, these two signals may experience the same / similar channel states. From the receiver's perspective, upon receiving one of the two signals, the other signal can be detected by using the channel characteristics of the received signal.

[0153] In this sense, when signals A and B are considered quasi-co-located (QCLed), it may mean that signals A and B experience similar channel conditions, and therefore the channel information estimated for detecting signal A is also useful for detecting signal B. In this paper, channel conditions can be defined based on, for example, Doppler shift, Doppler spread, average delay, delay spread, spatial reception parameters, etc.

[0154] The “TCI-State” parameter associates one or two downlink reference signals with the corresponding QCL type (QCL types A, B, C, and D, see Table 4).

[0155] [Table 4]

[0156] QCL type describe QCL-TypeA Doppler frequency shift, Doppler spread, average delay, delay spread QCL-TypeB Doppler frequency shift, Doppler spread QCL-TypeC Doppler shift, average delay QCL-TypeD Spatial Rx parameters

[0157] Each “TCI-State” may include parameters for configuring the QCL relationship between one or two downlink reference signals and the DM-RS port of the PDSCH (or PDDCH) or the CSI-RS port of the CSI-RS resource.

[0158] Additionally, for each DL BWP of a UE configured in a serving cell, the UE can be equipped with 10 (or fewer) search space sets. For each search space set, the UE can be equipped with at least one of the following information.

[0159] 1) Search space set index s (0≤s<40), 2) Correlation between CORESET p and search space set s, 3) PDCCH monitoring periodicity and PDCCH monitoring offset (slot unit), 4) PDCCH monitoring pattern within a slot (e.g., indicating the first symbol of CORESET in the slot used for PDCCH monitoring), 5) Number of slots in which search space set s exists, 6) Number of PDCCH candidates per CCE aggregation level, 7) Information indicating whether search space set s is a CSS or USS.

[0160] In NR, CORESET#0 can be configured via PBCH (or UE-specific signaling for handover, PSCell configuration, or BWP configuration). The search space (SS) set #0 configured by PBCH can have different monitoring offsets (e.g., slot offset, symbol offset) for each associated SSB. This may be necessary to minimize the timing of search space monitoring by the UE. Alternatively, this may be required to provide a beam-scanning control / data area capable of performing control / data transmission on a per-beam basis, enabling continuous communication with the UE even as the UE's optimal beam dynamically changes.

[0161] Figure 12 The diagram illustrates the physical channel and typical signal transmission.

[0162] refer to Figure 12 In a wireless communication system, the UE receives information from the BS via the downlink (DL) and transmits information to the BS via the uplink (UL). The information transmitted / received by the BS and UE includes data and various control information, and various physical channels exist depending on the type / purpose of the information transmitted / received by the BS and UE.

[0163] When a UE is powered on again after a power outage or enters a new cell, it performs an initial cell search operation, such as adjusting synchronization with the BS (S11). To do this, the UE receives the primary synchronization channel (PSCH) and secondary synchronization channel (SSCH) from the BS to adjust synchronization with the BS and obtains information such as the cell identifier (ID). Additionally, the UE can receive the physical broadcast channel (PBCH) from the BS to obtain broadcast information within the cell. Furthermore, the UE can receive a downlink reference signal (DL RS) during the initial cell search step to identify the downlink channel state.

[0164] Upon completion of the initial cell search, the UE can receive the Physical Downlink Control Channel (PDCCH) and its corresponding Physical Downlink Control Channel (PDSCH) to obtain more specific system information (S12).

[0165] Subsequently, the UE can perform a random access procedure to complete access to the BS (S13-S16). Specifically, the UE can transmit a preamble via the Physical Random Access Channel (PRACH) (S13), and can receive a Random Access Response (RAR) for the preamble via the PDCCH and its corresponding PDSCH (S14). Afterward, the UE can transmit the Physical Uplink Shared Channel (PUSCH) using the scheduling information in the RAR (S15), and can perform a contention resolution procedure similar to that of the PDCCH and its corresponding PDSCH (S16).

[0166] After executing the above process, as a typical uplink / downlink signal transmission procedure, the UE can perform PDCCH / PDSCH reception (S17) and PUSCH / Physical Uplink Control Channel (PUCCH) transmission (S18). The control information sent by the UE to the BS is called uplink control information (UCI). UCI includes Hybrid Automatic Repeat Request (HARQ) acknowledgment (ACK) / negative ACK (NACK), scheduling request (SR), channel state information (CSI), etc. CSI includes channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), etc. Usually, UCI is sent via PUCCH. However, when control information and data need to be sent simultaneously, UCI can be sent via PUSCH. In addition, the UE can send UCI aperiodically via PUSCH according to network requests / instructions.

[0167] To achieve reasonable battery consumption when configuring bandwidth adaptive (BA), in the active serving cell, only one uplink BWP and one downlink BWP, or only one downlink / uplink BWP pair, can be activated at a time for each uplink carrier, and all other BWPs configured in the UE are deactivated. In the deactivated BWPs, the UE does not monitor the PDCCH and does not perform transmissions on the PUCCH, PRACH, and UL-SCH.

[0168] For BA, the UE's RX and TX bandwidths are not necessarily as wide as the cell's bandwidth and can be adjusted. That is, commands can be used to change the bandwidth (e.g., to save power, reducing it during low-activity periods), move its position in the frequency domain (e.g., to increase scheduling flexibility), and change the subcarrier spacing (e.g., to allow different services). A subset of the cell's entire bandwidth is called the Bandwidth Part (BWP), and BA is obtained by configuring the BWP for the UE and informing the UE of the currently active BWP within the configured BWP. When BA is configured, the UE only needs to monitor the PDCCH on one active BWP. That is, it does not need to monitor the PDCCH on the entire downlink frequency of the cell. A BWP inactivity timer (independent of the aforementioned DRX inactivity timer) is used to switch the active BWP to the default BWP. That is, the timer restarts when the PDCCH is successfully decoded and switches to the default BWP when the timer expires.

[0169] The Integrated Access and Backhaul (IAB) will be described below. For ease of description, the proposed method will be based on the new RAT (NR) system. However, the scope of systems applying the proposed method can be extended to systems other than NR systems, such as 3GPP LTE / LTE-A systems.

[0170] One of the potential technologies aimed at enabling future cellular network deployment scenarios and applications is support for wireless backhaul and relay links, which enables flexible and high-density deployment of NR cells without proportionally increasing the density of the transmission network.

[0171] With the local deployment of massive MIMO or multi-beam systems, larger bandwidths (e.g., millimeter-wave spectrum) in NR compared to LTE are expected to become available, thus creating an opportunity for the development and deployment of integrated access and backhaul links. By establishing multiple control and data channels / procedures defined to provide access to or through the UE, this makes it easier to build dense networks of NR cells from backhaul in a more integrated manner. Such a system is called Integrated Access and Backhaul (IAB).

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

[0173] -AC(x): The access link between node (x) and UE(s).

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

[0175] In this context, a node can refer to either a donor gNB (DgNB) or a relay node (RN). Here, the DgNB or donor node can be a gNB that provides backhaul functionality to the IAB node.

[0176] Furthermore, in this disclosure, for ease 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 the sent and received data to relay node 2, is referred to as the parent node of relay node 2, and relay node 2 is referred to as the child node of relay node 1.

[0177] The technical features described individually in one of the accompanying drawings of this specification can be implemented individually or simultaneously.

[0178] The following figures are created to illustrate specific examples of this specification. Because the names of specific devices or 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.

[0179] Figure 13 The illustration shows an example of a network with integrated access and backhaul (IAB).

[0180] according to Figure 13 Relay nodes (rTRPs) can multiplex access and backhaul links in the time, frequency, or spatial domains (i.e., beam-based operation).

[0181] Different links can operate on the same frequency or different frequencies (also referred to as "in-band" or "out-of-band" trunks, respectively). For some NR deployment scenarios, effective support for out-of-band trunks may be important. Close interoperability with access links operating on the same frequency to accommodate duplex constraints and avoid / mitigate interference is also crucial.

[0182] Furthermore, operating NR systems in the millimeter-wave spectrum can present problems such as severe short-range congestion, which current RRC-based handover mechanisms cannot easily mitigate. Overcoming short-range congestion in millimeter-wave systems may require a fast RAN-based mechanism for handover between rTRPs that do not necessarily need to include the core network. It may also be necessary to develop an integrated framework that allows for rapid handover via access and backhaul links. Over-the-air (OTA) coordination between rTRPs could also be considered to mitigate interference and support end-to-end path selection and optimization.

[0183] It may be necessary to address the following requirements related to IAB in NR.

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

[0185] Multi-hop and redundant connections

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

[0187] - Supports backhaul links with high spectral efficiency

[0188] - Supports legacy NR UEs

[0189] Legacy NR is designed to support half-duplex devices. Therefore, half-duplex support is a worthwhile target in IAB scenarios. Additionally, IAB devices with full-duplex capabilities can also be considered.

[0190] In an IAB scenario, if each relay node (RN) lacks scheduling capabilities, the donor gNB (DgNB) must schedule the entire link between the DgNB, relevant relay nodes, and the UE. In other words, the DgNB should collect service information from all relevant relay nodes, make scheduling decisions for all links, and then notify each relay node of the scheduling information.

[0191] On the other hand, when each relay node has scheduling capabilities, distributed scheduling can be performed. Then, real-time scheduling of the UE's uplink scheduling request is possible, and backhaul / access links can be used more flexibly by reflecting the surrounding service conditions.

[0192] Figure 14 This diagram illustrates a configuration example for access and backhaul links.

[0193] Figure 14 The diagram illustrates an example of configuring backhaul and access links when DgNB and IAB relay nodes (RNs) are present. DgNB, relay node 1, and relay node 2 are connected to the backhaul link, and UEs 1, 2, and 3 are connected to DgNB, relay node 1, and relay node 2 in sequence via access links.

[0194] DgNB can make scheduling decisions for two backhaul links and three access links, and notify the scheduling results. This centralized scheduling may include scheduling delays and cause latency issues.

[0195] If each relay node has scheduling capabilities, distributed scheduling can be performed. Then, uplink scheduling requests from UEs can be scheduled in real time, and backhaul / access links can be used more flexibly by reflecting the surrounding service conditions.

[0196] Figure 15 The diagram shows the IAB node operating in standalone (SA) mode or non-standalone (NSA) mode.

[0197] Figure 15 (a) The illustration shows that both the UE and the IAB node are operating in SA mode associated with NGC, and Figure 15 (b) The diagram shows the UE operating in NSA mode related to the EPC, while the IAB node operates in SA mode related to the NGC. Figure 15 (c) The illustration shows that both the UE and the IAB node are operating in NSA mode related to the EPC.

[0198] In other words, an IAB node can operate in either SA or NSA mode. In NSA mode, the IAB node uses only the NR link for backhaul. A UE connected to an IAB node can choose a different operating mode than the IAB node itself. A UE can also connect to a different type of core network than the connected IAB node. An IAB node operating in NSA mode can connect to the same or different eNBs. A UE operating in an NSA node can connect to the same or different eNBs as the connected IAB node.

[0199] Figure 16 The diagram illustrates the backhaul link and the access link.

[0200] refer to Figure 16Links between a donor node (which can be called a parent node) and IAB nodes, or links between IAB nodes, are called backhaul links. Conversely, links between a donor node and a UE, or links between an IAB node and a UE, are called access links. Specifically, the link between the MT of an IAB node and the DU of its parent node, or the link between the DU of an IAB node and the MT of its child node, is called a backhaul link, and the link between the DU of an IAB node and the UE can be called an access link.

[0201] For communication with the parent node, the IAB node can be provided with an MT configuration, which indicates link direction information regarding the backhaul link between the parent node and itself. Furthermore, for communication with the child node, the IAB node can be provided with a DU configuration, which notifies the child node / access UE of the link direction and link availability information of the access link between itself and the child node / access UE.

[0202] In existing IAB nodes, DU and MT perform TDM operations using different time resources. However, future communication systems may require resource multiplexing between DU and MT, such as SDM / FDM and full-duplex (FD), to achieve efficient resource management.

[0203] Figure 17 The diagram illustrates the parent and child links.

[0204] refer to Figure 17 The link between an IAB node (specifically, an IAB MT) and its parent node (specifically, a parent DU) is called a parent link, and the link between an IAB node (specifically, an IAB DU) and its child node (specifically, a child MT) is called a child link. A parent link can be a backhaul link as mentioned above, and a child link can be either a backhaul link or an access link, depending on what the child node is. That is, if the child node is an IAB node, it is likely a backhaul link, and if the child node is a UE, it is likely an access link. TDM operations between parent and child links have been discussed previously, and SDM / FDM and FD operations are currently being discussed.

[0205] From the perspective of the DU of the IAB node, there are multiple types of time resources for sub-links, such as downlink (DL), uplink (UL), and flexible (F).

[0206] Each downlink, uplink, and flexible time resource in a DU sublink can be a hard, soft, or unavailable (NA) resource. Here, an unavailable resource means that the resource is not used for communication on the DU sublink. Hard resources mean that they are always available for communication on the DU sublink. Whether a soft resource can be used for communication in a DU sublink (availability) can be explicitly and / or implicitly controlled by the parent node.

[0207] In the present disclosure, the configuration of the link (resource) direction (DL / UL / F) and link (resource) availability (hard / soft / NA) of the time resources of the DU sub - link can be referred to as "DU configuration". This configuration can be used for efficient multiplexing and interference handling between IAB nodes. For example, the above - mentioned configuration can be used to indicate which link among the parent link and the sub - link the time resources are valid for. It can be used to coordinate interference between sub - nodes. Considering this aspect, the DU configuration may be more effective when configured semi - statically and specifically for IAB nodes.

[0208] The availability of soft resources can be dynamically configured through implicit / explicit signals based on the physical layer (L1). Hereinafter, "IA" can mean that the DU resources are explicitly or implicitly indicated as available, and "INA" can mean that the DU resources are explicitly or implicitly indicated as unavailable. The dynamic L1 - based signaling can indicate whether the DU soft resources are "IA" or "INA".

[0209] From the perspective of the DU, the soft resources can be in the IA (indicated as available) state or the non - IA state. In this case, the non - IA state can be interpreted as the INA (indicated as unavailable) state. Whether the soft resources are IA can be indicated by AI (Availability Indicator) information, and the AI information can be indicated from the parent node to the IAB node through AI - DCI. The following DCI format 2_5 is an example of AI - DCI.

[0210] <DCI format 2_5>

[0211] DCI format 2_5 is a DCI format for notifying the availability of soft resources. The following information can be sent together with the CRC scrambled by the AI - RNTI through DCI format 2_5.

[0212] Availability Indicator 1, Availability Indicator 2,..., Availability Indicator N.

[0213] The size of DCI format 2_5 with the CRC scrambled by the AI - RNTI can be configured by the higher layer up to 128 bits.

[0214] Similar to the SFI configuration of the access link, the IAB node MT can have three types of time resources for the parent link: downlink (DL), uplink (UL), and flexible (F).

[0215] Due to reasons such as in - node interference, slot / symbol boundary misalignment, power sharing, etc., the DU and MT present in the same IAB node (or co - located) cannot operate simultaneously and may operate in TDM.

[0216] On the other hand, SDM / FDM multiplexing can be used between DU and MT. This is applicable, for example, when DU and MT use different panels and the interference between panels is minimal. In this case, DU and MT existing in the same (or co-located) IAB node can simultaneously transmit (DU transmits, MT transmits) or receive (DU receives, MT receives). (DU and MT cannot simultaneously perform transmit and receive (DU transmits, MT receives) or receive and transmit (DU receives, MT transmits) respectively.

[0217] Alternatively, full-duplex (FD) can be used between the DU and MT. This is suitable, for example, in situations where interference between the DU and MT is minimal, such as when the frequency regions of the DU and MT are geographically distant. In this case, the DU and MT, located in the same (or co-located) IAB node, can freely transmit and receive simultaneously. The DU and MT can transmit or receive simultaneously, and they can also perform simultaneous transmission and reception or separate transmission and reception.

[0218] The MT and DU of the IAB node can be configured with multiple component carriers (CCs) (meaning multiple CCs can be used). In this case, different CCs can operate in the same or different frequency regions, or they can use the same or different panels.

[0219] Figure 18 This example demonstrates the use of multiple CCs in the MT and DU of an IAB node.

[0220] refer to Figure 18 The MT and DU of an IAB node can use multiple component carriers (CC) (or it can be expressed that the MT and DU of an IAB node consist of multiple CCs).

[0221] In this scenario, different CCs can operate in the same or different frequency regions, or they can use the same or different panels. For example, such as Figure 18 As shown, each of the three CCs can exist in MT and DU of the IAB node. The three CCs in MT are called MT-CC1, MT-CC2 and MT-CC3, respectively, and the three CCs in DU are called DU-CC1, DU-CC2 and DU-CC3, respectively.

[0222] In this scenario, a multiplexing scheme among TDM, SDM / FDM, and FD can be applied between a specific CC of the MT and a specific CC of the DU. For example, when specific MT-CCs and DU-CCs are located in different inter-band frequency regions, FD can be applied between the corresponding MT-CCs and DU-CCs.

[0223] On the other hand, TDM schemes can be applied between MT-CC and DU-CC located in the same frequency region. For example, in Figure 18 In this configuration, MT-CC1, MT-CC2, DU-CC1, and DU-CC2 operate at center frequency f1, while MT-CC3 and DU-CC3 operate at center frequency f2. f1 and f2 can be located between each other's bands. In this case, MT-CC1 (or MT-CC2) can operate with DU-CC1 and DU-CC2 in TDM mode, but with DU-CC3 in FD mode. Conversely, from MT-CC3's perspective, it operates with DU-CC1 and DU-CC2 in FD mode, but with DU-CC3 in TDM mode.

[0224] On the other hand, even within the same CC, different multiplexing schemes can be applied between MT and DU. For example, multiple sections can exist within the CC of MT and / or DU. This section can refer, for example, to a link transmitted via antennas with the same center frequency but different physical locations or different panels. Alternatively, this section can refer, for example, to a link with the same center frequency but transmitted via different BWPs. In this case, for example, when two sections exist in DU-CC1, the multiplexing type operating with a particular MT-CC or a particular section within a particular MT-CC may be different for each section. The following disclosure describes the situation where the multiplexing type applied to each pair of MT CC and DU CC may be different, and this disclosure can be extended and applied even when MT and DU are divided into multiple sections and the multiplexing types applied to the CC and sections of each pair of MT and the CC and sections of DU may not be the same.

[0225] In the context of this disclosure, DU-CC can be interpreted as a replacement of DU cells.

[0226] The following are some possible methods for Tx / Rx timing alignment of IAB nodes in an IAB environment.

[0227] Case 1: Alignment of DL transmission timing between IAB nodes and IAB donors.

[0228] Scenario 2: DL and UL transmission timings are aligned within the IAB node.

[0229] Case 3: The timing of DL and UL reception is aligned within the IAB node.

[0230] Case 4: Within the IAB node, Case 2 is used for transmission, and Case 3 is used for reception.

[0231] Case 5: In different time slots within the IAB node, Case 1 is used for access link timing, and Case 4 is used for backhaul link timing.

[0232] Case 6: Use the DL transmission timing from Case 1 and the UL transmission timing from Case 2.

[0233] Case 7: Use the DL transmission timing from Case 1 and the UL transmission timing from Case 3.

[0234] The following text will describe some situations in the case of timed alignment in more detail.

[0235] Timed alignment case 1 (hereinafter referred to as case 1).

[0236] Figure 19 The diagram shows the timing alignment situation 1.

[0237] refer to Figure 19 In Case 1, the DL transmission (Tx) timing is aligned between the IAB node and the IAB donor (represented by the CU). That is, the DL Tx timing of the DU between IAB nodes is aligned, and this is the timing alignment method used by IAB nodes in version 16.

[0238] If DL Tx and UL Rx are not properly aligned in the parent node, the child node may require additional alignment information to correctly set the DL Tx timing. MT Tx timing can be expressed as "MT Rx timing - TA", while DU Tx timing can be expressed as "MT Rx timing - TA / 2 - T_delta". The T_delta value can be obtained from the parent node.

[0239] Timed alignment scenario 6 (hereinafter referred to as scenario 6)

[0240] Figure 20 The diagram shows the timing alignment status 6.

[0241] refer to Figure 20 Case 6 is when the DL transmission timing of all IAB nodes is consistent with the DL timing of the parent IAB node (CU) or donor. The UL transmission timing of the IAB node can be aligned with the DL transmission timing of the IAB node. That is, the MT UL Tx timing and DU DL Tx timing of the IAB node are aligned.

[0242] Because the UL Tx timing of the MT is fixed, the ULRx timing of its receiving parent DU delays the propagation delay of both the parent DU and the MT compared to the MT's UL Tx timing. The UL Rx timing of the MT varies depending on the child MT that transmits the UL. When an IAB node uses timing alignment case 6, the parent node's UL Rx timing differs from the existing one. Therefore, if an IAB node wants to use timing alignment case 6, the parent node also needs to know the corresponding information.

[0243] Timed alignment status 7.

[0244] Figure 21 The diagram shows the timing alignment status (7).

[0245] refer to Figure 21 In Case 7, the DL transmission timing of all IAB nodes is consistent with the DL timing of the parent IAB node or donor. The UL receive timing of the IAB nodes can be consistent with the DL receive timing of the IAB nodes. If the DL Tx and ULRx are not well aligned in the parent node, additional information on alignment may be required for the child nodes to correctly set the DL Tx timing. Case 7 is a scheme for aligning the MT DL Rx timing and DU UL Rx timing of the IAB nodes.

[0246] From the MT's perspective, the transmit / receive timing is the same as that of the existing IAB node (version 16 IAB node), and the UL Rx timing of the DU can be aligned with the MT's DL Rx timing. The IAB node needs to adjust the TA of the sub-MT so that the sub-MT transmits the UL signal according to the IAB node's UL Rx timing.

[0247] Compared to the existing timing alignment method (Case 1), this timing alignment method may not reveal differences in the standard operation of IAB nodes. Therefore, timing alignment case 7 can be replaced / interpreted as timing alignment case 1.

[0248] In this disclosure, timing alignment can refer to slot-level alignment or symbol-level alignment.

[0249] This disclosure will be described below.

[0250] First, we will describe DAPS-HO (Dual Active Protocol Stack-based Switching).

[0251] DAPS handover (hereinafter referred to as DAPS) can be called the handover process, which is used to maintain the connection with the source gNB until the source cell (source gNB) releases the connection after receiving the RRC message (HO command) for handover and successfully randomly accessing the target cell (target gNB).

[0252] From the perspective of UE functionality, DAPS typically has the following characteristics.

[0253] In terms of transmission operations, 1) a common sequence number (SN), 2) separate header compression for the source cell and the destination cell, and 3) separate encryption for the source cell and the destination cell.

[0254] In terms of receiving operations, 1) separate decryption of source and target cells, 2) separate header decompression of source and target cells, 3) common PDCP reordering, 4) sequential delivery and duplicate detection, and 5) common buffer management.

[0255] Generally, the network and UE have the same procedures and functions for both transmit and receive operations. The difference may lie in whether these functions are co-located. In the network, all functions except DL PDCP SN allocation and UL PDCP reordering are deployed separately and are not performed 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.

[0256] On the UE side, all functions, including SN allocation and PDCP reordering, are deployed together. Therefore, all DAPS functions 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 or destination eNB can be used.

[0257] UE RF / baseband requirements.

[0258] To minimize interruptions, regardless of whether the UE is SAPS or DAPS, it may be necessary to continue data transmission / reception with the source cell while performing a random access procedure to the target cell. This is only possible if the UE supports simultaneous transmission and reception with two cells. In most cases, this works on UEs with dual Rx / dual Tx chains. More restrictions can be imposed on UEs with dual Rx / single Tx RF chains or single Rx / single Tx RF chains. Furthermore, to effectively utilize baseband and RF resources, it may be necessary to partition the UE's capabilities. Because tuning the UE's baseband and RF resources is not as straightforward in the case of SAPS, additional interruptions and UE complexity may occur.

[0259] For UEs with dual Rx / single Tx RF chains, in order to support simultaneous UL data transmission to the source eNB and UL RACH transmission to the target eNB, simultaneous transmission can be supported if certain requirements are met (e.g., if the bandwidth of the source cell is greater than the bandwidth of the target cell, and the Tx power difference between the two cells is within a certain limit).

[0260] Otherwise, some type of UL TDM mode would be required, which could increase downtime and UL handover complexity. However, this UE option offers flexibility in terms of hardware and power efficiency for different UE implementation styles (especially for lower-level devices that cannot perform UL CA and / or UL MIMO).

[0261] For UEs with a single Rx / single Tx RF chain, simultaneous transmission / reception can still be supported if certain requirements are met, such as the source cell's bandwidth being greater than the target cell's bandwidth and the Tx / Rx power difference between the two cells being within certain limits. Otherwise, both DL and UL require TDM design, which adds additional complexity to both the UE and network sides. Furthermore, both DL and UL require RF chain handover, which increases HO interruption time and handover complexity.

[0262] If the UE indicates the capability of Dual Active Protocol Stack (DAPS HO), the source MCG and target MCG can be provided to the UE. The UE can determine the transmission power of the MCG and the transmission power of the SCG for each frequency range.

[0263] UE transmissions may overlap in the target cell and the source cell. For example, 1) when the carrier frequencies of the target MCG and the source MCG are in-frequency and in-band, and the time resources overlap, 2) when the carrier frequencies of the target MCG and the source MCG are not in-frequency and in-band, UE transmissions may overlap in overlapping time resources and overlapping frequency resources.

[0264] In the case of DAPS HO operation within the frequency range, the UE can anticipate that the active DL BWP and active UL BWP of the target cell are in the active DL BWP and active UL BWP of the source cell, respectively.

[0265] The UE can provide the ability to monitor the maximum number of PDCCH candidates per time slot for the target MCG and the maximum number of PDCCH candidates per time slot for the source MCG.

[0266] For PRACH transmissions, the IAB node MT determines the frame containing the PRACH timing and the subframes within that frame. The IAB node MT determines the association period for mapping SS / PBCH blocks to PRACH timings based on the PRACH configuration period, according to the table below. The association pattern period includes one or more association periods and is determined such that the pattern between the PRACH timing and the SS / PBCH block repeats at most once every 640 milliseconds. PRACH timings within a PRACH slot can be enabled or disabled depending on conditions.

[0267] The table below illustrates the mapping between the PRACH configuration cycle of the MT of the IAB node and the SS / PBCH blocks.

[0268] [Table 5]

[0269]

[0270] If the IAB node provides the value T from the serving cell delta IAB nodes can be in (NTA +N TA，offset )·T c / 2+T delta When >0, it is assumed that (N) TA +N TA，offset )·T c / 2+T delta This is the time difference between the DU transmission of the signal from the serving cell and the MT reception of the signal at the IAB node. The IAB node can use this time difference to determine the DU transmission time.

[0271] The slot format for IAB node DU or IAB node MT includes downlink symbols, uplink symbols, and flexible symbols.

[0272] For each serving cell of an IAB node's DU, the IAB node's DU can be provided with "IAB-DU-Resource-Configuration". "IAB-DU-Resource-Configuration" can provide instructions on the time slot format for multiple time slots.

[0273] If the IAB node MT is provided with "tdd-UL-DL-ConfigDedicated-IAB-MT", then the parameter "tdd-UL-DL-ConfigDedicated-IAB-MT" only overrides the flexible sign on the number of slots provided by "TDD-UL-DL-ConfigurationCommon".

[0274] “tdd-UL-DL-ConfigDedicated-IAB-MT” can provide the following information.

[0275] 1) The slot configuration set by “slotSpecificConfigurationsToAddModList-IAB-MT”; 2) For each slot configuration in the slot configuration set, the slot index provided by “slotIndex”; for the symbol set of the slot via “symbols”, if “symbol” is “allDownlink”, all symbols in the slot are downlinks; if “symbols” is “allUplink”, all symbols in the slot are uplinks; and if “symbol” is “explicit”, “nrofDownlinkSymbols” provides the number of the first downlink symbol in the slot, and “nrofUplinkSymbols” provides the number of the last uplink symbol in the slot. If “nrofDownlinkSymbols” is not provided, it may mean that there is no first downlink symbol in the slot, and if “nrofUplinkSymbols” is not provided, it may mean that there is no last uplink symbol in the slot. The remaining symbols in the slot are flexible symbols.

[0276] If "symbols" is "explicit-IAB-MT", then "nrofUplinkSymbols" provides the number of the first uplink symbol in the time slot, while "nrofDownlinkSymbols" provides the number of the last downlink symbol in the time slot. If "nrofUplinkSymbols" is not provided, it may mean that there is no first uplink symbol in the time slot, and if "nrofDownlinkSymbols" is not provided, it may mean that there is no last downlink symbol in the time slot. The remaining symbols in the time slot are flexible.

[0277] The slot format of the DU of an IAB node or the MT of an IAB node can include downlink symbols, uplink symbols, and flexible symbols. Slot format information can refer to information indicating whether each symbol is a downlink symbol, uplink symbol, or flexible symbol.

[0278] For each slot with a corresponding index provided by "slotIndex", the MT of the IAB node can apply the format provided by the corresponding "symbols". The MT of the IAB node is provided with a list of slot format combinations applicable to a serving cell through "SlotFormatCombinationsPerCell-IAB-MT", and the configuration of DCI format 2_0 for monitoring the slot format combination can be provided by "SlotFormatIndicator-IAB-MT". The SFI field of DCI format 2_0 can indicate to the MT of the IAB node one of the slot formats in the following table.

[0279] The table below illustrates the time slot format in a normal CP.

[0280] [Table 6]

[0281]

[0282] The number of unused symbols of an IAB node's MT can be provided to the MT via "guard-SymbolsProvided". Within these symbols, the IAB node can perform transformations between the MT and DU. The SCS configuration for the number of symbols can be provided by "guardSymbol-SCS".

[0283] The symbols in the time slots of the DU serving cell of an IAB node can be set to hard, soft, or unavailable type. When downlink, uplink, or flexible symbols are configured as hard, the DU serving cell of an IAB node can perform transmit, receive, or "transmit or receive" operations on the corresponding symbols, respectively.

[0284] If the downlink, uplink, or flexible symbol is configured as soft, the DU (DU serving cell) of the IAB node can only perform transmit, receive, or “transmit or receive” operations on the respective symbol under the following conditions.

[0285] 1) For IAB node MT, the ability of IAB node DU to send or receive in soft symbols is equivalent to configuring soft symbols as unavailable. 2) IAB node DU detects DCI format 2_5 with AI index field values ​​indicating that soft symbols can be used for sending or receiving.

[0286] In other words, when the downlink, uplink, or flexible symbol is configured as a soft symbol, the IAB node DU can transmit, receive, or transmit or receive within the symbol, respectively, only if:

[0287] 1) If the MT of the IAB node does not transmit or receive in the corresponding symbol, 2) When the MT of the IAB node transmits / receives in the corresponding symbol, and the transmission / reception of the MT of the IAB node does not change because the DU of the IAB node uses the corresponding symbol, 3) Where the MT of the IAB node detects the case of DCI format 2_5 with an AI index field value indicating the availability of soft symbols, etc.

[0288] If a symbol is configured to be unavailable, the DU of the IAB node will not send or receive in that symbol.

[0289] When the DU of an IAB node transmits SS / PBCH blocks or periodic CSI-RS in a time slot symbol or receives PRACH or SR in a symbol, the symbol is equivalent to being configured as hard.

[0290] Information about AI-RNTI and the payload size in DCI format 2_5 can be provided to the IAB node. Additionally, a search space set configuration for monitoring the PDCCH can be provided.

[0291] The following information can be provided to the DU of the IAB node: 1) the ID of the serving cell of the DU of the IAB node, 2) the location of the Availability Indication (AI) index field in DCI format 2_5, and 3) the availability combination set. Each availability combination within the availability combination set may contain the following information: i) information indicating the availability of soft symbols in one or more slots of the serving cell of the DU of the IAB node, and ii) information related to the mapping between the corresponding AI index field value in DCI format 2_5 and the soft symbol availability combination.

[0292] The random access preamble can be sent only in the time resources provided by the higher layer parameter (prach-ConfigurationIndex) and can be configured differently depending on FR1 or FR2 and the spectrum type.

[0293] Based on this discussion, we will now consider the case where a specific IAB node is connected to two parent nodes and the links to these two parent nodes use the same or adjacent frequency regions. In this case, to prevent cross-link interference due to the different DL / UL directions of the two links, it is proposed to operate the DL / UL directions of the two links in the same way.

[0294] Due to intra-node interference, time slot / symbol boundary misalignment, power sharing, etc., DU and MT existing in the same IAB node (or co-located) cannot operate simultaneously and may operate as TDM.

[0295] On the other hand, SDM / FDM multiplexing can be used between DU and MT. For example, this is applicable when DU and MT use different panels and the interference between the panels is minimal. In this case, DU and MT existing in the same IAB node (or quasi-co-located) can transmit or receive simultaneously, and it is not possible for each of DU and MT to perform transmission and reception separately or simultaneously.

[0296] Alternatively, full-duplex (FD) can be used between the DU and MT. This is suitable, for example, when interference between the DU and MT is minimal, such as when the frequency regions in which the DU operates are far apart from the frequency regions in which the MT operates. In this case, the DU and MT, existing in the same (or co-located) IAB node, can freely transmit and receive simultaneously. The DU and MT can transmit or receive simultaneously, and can also transmit and receive simultaneously, or receive and transmit simultaneously.

[0297] The MT and DU of an IAB node can consist of multiple component carriers (CCs). In this case, different CCs can operate in the same or different frequency regions, or can use the same or different panels.

[0298] Figure 22 The diagram shows MT and DU in the IAB node.

[0299] refer to Figure 22 Each of the MT and DU in the IAB node can have three CCs. The three CCs in the MT are called MT-CC1, MT-CC2, and MT-CC3, respectively. In the case of the DU, the CCs are replaced by cells and are called DU-cell1, DU-cell2, and DU-cell3.

[0300] In this scenario, a multiplexing scheme among TDM, SDM / FDM, and FD can be applied between specific MT-CCs and specific DU cells. For example, when specific MT-CCs and DU cells are located in different inter-band frequency regions, FD can be applied between the corresponding MT-CCs and DU cells. On the other hand, the TDM scheme can be applied between MT-CCs and DU-CCs located in the same frequency region.

[0301] For example, MT-CC1, MT-CC2, DU-cell 1, and DU-cell 2 use f1 as their center frequency, while MT-CC3 and DU-cell 3 use f2 as their center frequency, and f1 and f2 can be located between each other's frequency bands. In this case, at the location of MT-CC1 (or MT-CC2), it operates via TDM with DU-cell 1 and DU-cell 2, but can operate via FD with DU-cell 3. On the other hand, from the perspective of MT-CC3, it operates via FD with DU-cell 1 and DU-cell 2, but can operate via TDM with DU-cell 3.

[0302] Different multiplexing schemes between MT and DU can even be applied within the same CC. For example, multiple parts can exist in an MT-CC and / or DU-cell. Such parts may refer, for example, to links transmitting through antennas with the same center frequency but in different physical locations or on different panels.

[0303] Alternatively, "part" can refer to, for example, links that have the same center frequency but transmit through different bandwidth portions (BWPs). In this case, for example, when there are two portions in DU-cell 1, the multiplexing type operating with a specific MT-CC or a specific portion within a specific MT-CC may be different for each portion. The following disclosure describes the case where the multiplexing type applied to each pair of MTCC and DU cells can be different. However, even when MT and DU are divided into multiple portions and the multiplexing type applied to each pair of CCs and portions of the MT and cells and portions of the DU may be different, the following disclosure can be extended and applied.

[0304] An IAB node can be considered to be connected to two or more parent nodes. In this case, the IAB MT can use a dual-connection (DC) scheme to connect to two parent DUs.

[0305] IAB nodes can have redundant routes to the IAB donor CU. For IAB nodes operating in SA mode, the new radio (NR) DC can enable path redundancy in BH by allowing the IAB-MT to have concurrent BH RLC channels with two parent nodes. The two parent nodes may have to connect to the same IAB donor CU-CP that controls the establishment and release of redundant paths. The parent node, together with the IAB donor CU, can act as both the primary and secondary node of the IAB-MT. NR DC frameworks (e.g., MCG / SCG related procedures) can be used to configure dual radio links with the parent nodes.

[0306] The following scenario can be considered by connecting the IAB MT to two parent DUs.

[0307] Scenario 1. Using different MT-CCs with adjacent carrier frequencies to connect to multiple parent DUs.

[0308] IAB MT can establish connections with multiple parent DUs using different MT-CCs. That is, one MT-CC establishes a connection with one parent DU-cell, and the corresponding parent DU-cell may exist in different parent DUs.

[0309] Figure 23 Scenario 1 is shown in the diagram.

[0310] refer to Figure 23 In IAB MT1, there are MT-CC1 and MT-CC2. MT-CC1 is connected to DU-cell 1 in parent DU1, and MT-CC2 is connected to DU-cell 4 in parent DU2. From the perspective of IAB MT1, the link between an MT-CC1 and a DU-cell is referred to as a parent link. However, the link between MT-CC1 and DU-cell 1 and the link between MT-CC2 and DU-cell 4 are considered different parent links.

[0311] Thus, to establish connections with DU-cells in different parent DUs using different MT-CCs, the existing dual connectivity (DC) method can be used. In this case, when the IAB MT is connected to two parent DU-cells using different MT-CCs, one parent DU-cell belongs to the primary cell group (MCG), while the remaining parent DU-cells may belong to the secondary cell group (SCG).

[0312] It can be assumed that each MT-CC of the IAB MT has an independent RF chain. Therefore, each MT-CC can perform Tx / Rx operations independently and simultaneously. Each MT-CC can set and manage Tx / Rx timing based on its connected parent DU-cell.

[0313] In scenario 1, it is assumed that MT-CCs connected to different parent DUs operate on different carrier frequencies under the aforementioned conditions. That is, in Figure 23 In this scenario, the links between MT-CC1 and DU-cell 1, and between MT-CC2 and DU-cell 4, have different carrier frequencies. The link between MT-CC1 and DU-cell 1 can have a carrier frequency of f1, while the link between MT-CC2 and DU-cell 4 can have a carrier frequency of f3. In this case, the carrier frequency regions operating in the two parent links may be adjacent. If the parent links operate in different D / U directions, cross-link interference may occur. In this scenario, we consider the case where the carrier frequency regions between the two parent links are adjacent to each other and cross-link interference occurs to the extent that it affects performance.

[0314] IAB MT can establish connections with multiple parent DUs using different MT-CCs. That is, one MT-CC establishes a connection with one parent DU-cell, and the parent DU-cell may exist in different parent DUs.

[0315] Figure 24 Another example is shown in which IAB MT1 is connected to two parent DUs.

[0316] refer to Figure 24 In IAB MT1, there are MT-CC1 and MT-CC2. MT-CC1 is connected to DU-cell 1 in parent DU1, and MT-CC2 is connected to DU-cell 3 in parent DU2. From the perspective of IAB MT1, the link between an MT-CC1 and a DU-cell can be considered a parent link. However, in this case, the link between MT-CC1 and DU-cell 1 and the link between MT-CC2 and DU-cell 3 are considered different parent links.

[0317] Thus, in order to establish connections with DU cells in different parent DUs using different MT-CCs, existing dual connectivity schemes can be used. In this case, when connecting the IAB MT 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.

[0318] Each MT-CC in an IAB MT can have an independent RF chain. Therefore, each MT-CC can perform Tx / Rx operations independently and simultaneously. Each MT-CC can set and manage Tx / Rx timing based on its connected parent DU-cell.

[0319] In scenario 2, consider MT-CCs connected to different parent DUs operating on the same carrier frequency under the aforementioned conditions. That is, consider... Figure 24 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.

[0320] In this scenario, this means that different MT-CCs in the IAB MT can operate at the same carrier frequency, and it also means that multiple MT-CCs can exist in the same frequency region. Figure 24In this scenario, the link between MT-CC1 and DU-cell 1 can have a carrier frequency of f1, and the link between MT-CC2 and DU-cell 3 can also have a carrier frequency of f1. In this case, cross-link interference may occur when the parent links operate in different D / U directions. Furthermore, when the resources for transmitting actual DL signals / channels through the two MT-CCs overlap, they may act as mutual interference. Even in the case of UL, when the UL signals / channels transmitted by the two MT-CCs overlap, the UL signals / channels transmitted to a particular parent DU may act as interference to other parent DUs.

[0321] Figure 25 This shows another example of connecting IAB MT1 and two parent DUs.

[0322] refer to Figure 25 IAB MT1 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.

[0323] like Figure 25 As shown, MT-CC1 exists in IAB MT1, and MT-CC1 can connect to DU-cell 1 in parent DU1 and DU-cell 3 in parent DU2. From the perspective of IAB MT1, it is assumed that the link between an MT-CC1 and a DU-cell is a parent link. In this case, the link between MT-CC1 and DU-cell 1 and the link between MT-CC1 and DU-cell 3 become different parent links. The link between MT-CC1 and DU-cell 1 can have a carrier frequency of f1, and the link between MT-CC1 and DU-cell 3 can also have a carrier frequency of f1.

[0324] Scenario 3-1. Multiple parent DUs with multiple RF modules connected

[0325] An MT-CC in an IAB MT can have multiple RF chains. For example, an MT-CC can use two RF modules to communicate with different parent DUs on the same carrier frequency. In this case, there is only one MT-CC, but the MT-CC supports independent RF modules and can establish connections with multiple parent DUs simultaneously. Therefore, the MT-CC can independently and simultaneously perform Tx / Rx operations on multiple parent DUs. Each RF module of the MT-CC can set and manage Tx / Rx timing based on the parent DU-cell it is connected to. In this case, cross-link interference may occur when the parent links operate in different D / U directions. Furthermore, when the resources of actual DL signals / channels transmitted through two parent links overlap, they may act as interference to each other. Even in the case of UL, when UL signals / channels transmitted through two parent links overlap, the UL signals / channels sent to a particular parent DU may act as interference to other parent DUs.

[0326] Scenario 3-2. Multiple parent DU connections with a single RF module

[0327] An MT-CC in an IAB MT can have one RF chain. Therefore, an MT-CC may not be able to simultaneously transmit and receive via two parent links operating at different Tx / Rx timings. Furthermore, simultaneous transmission and reception via two parent links operating in different analog beam directions is not possible. Therefore, the MT-CC must use different time resources to operate on different parent links. In this case, the MT-CC can independently set and manage the Tx / Rx timing for each parent DU connected to it.

[0328] Scenario 4. DAPS HO (Switching based on dual-activity protocol stack)

[0329] DAPS HO was introduced to enhance UE mobility. This DAPS HO can also be applied to IAB MT. When applying DAPS HO, the MCG currently connected to the UE becomes the source MCG, and the MCG to be switched to becomes the target MCG. In this case, the UE can use the same carrier frequency to connect to both the source and target MCG simultaneously. The DAPS HO scheme can also be used when IAB MT establishes connections with multiple parent DUs using the same carrier frequency. In this case, two parent DUs can be connected by using one parent DU as the source MCG and the other as the target MCG.

[0330] The present disclosure is based on configuring and operating two parent DUs as MCG and SCG, respectively. However, it can include DAPS HO operations as MCG and SCG having MCG and SCG as source MCG and target MCG (or target MCG and source MCG), respectively. In this case, the MCG and SCG mentioned in this disclosure can be interpreted by replacing them with source MCG and target MCG (or target MCG and source MCG), respectively.

[0331] In the following description, the contents of this disclosure are assumed to be in an in-band environment, but can also be applied in an out-of-band environment. Furthermore, the contents of this disclosure are described with reference to an environment in which the donor base station (donor gNB: DgNB), relay node (RN), and UE are performing half-duplex operation, but can be applied to an environment in which the donor base station, relay node (RN), and / or UE are performing full-duplex operation.

[0332] In this disclosure, the scenario where the same IAB MT is connected to different parent DUs is considered. Considering the scenarios 1, 2 and 3 mentioned above, one MT-CC in the IAB MT is connected to a specific DU-cell in two different parent DUs, or different MT-CCs in the IAB MT may be connected to specific DU-cells in two different parent DUs respectively.

[0333] When different MT-CCs in an IAB MT are connected to specific DU cells in two different parent DUs, the two parent links operate in adjacent frequency regions (with carrier frequencies) as in Scenario 1, or they can operate in the same frequency region (with carrier frequencies) as in Scenario 2.

[0334] In scenario 3, when an MT-CC connects to a specific DU cell in two different parent DUs, the MT-CC operating via connection to the first parent DU is designated MT-CC-A, and the MT-CC operating via connection to the second parent DU is designated MT-CC-B. For example, an MT-CC may have two RF modules and can be divided into MT-CC-A and MT-CC-B based on these RF modules. In this case, MT-CC-A becomes the RF module of the MT-CC operating via connection to the first parent DU, and MT-CC-B becomes the RF module of the MT-CC operating via connection to the second parent DU. Alternatively, for example, the MT-CC can operate by dividing into two time zones and can be divided into MT-CC-A and MT-CC-B based on the operating time zone. In this case, the MT-CC operating via connection to the first parent DU in time zone 1 is designated MT-CC-A, and the MT-CC operating via connection to the second parent DU in time zone 2 can be designated MT-CC-B. In this disclosure, for convenience, MT-CC-A and MT-CC-B are interpreted and described as different MT-CCs. That is, in this disclosure, two different MT-CCs in IAB MT can refer to MT-CC-A and MT-CC-B in the same MT-CC (i.e., separate RF modules or time resources).

[0335] Figure 26 This shows another example of connecting IAB MT1 and two parent DUs.

[0336] refer to Figure 26 IAB MT1 consists of MT-CC1 and MT-CC2. Parent DU1 and parent DU2 are independent DUs within the IAB node and can connect to the same donor node / CU. MT-CC1 can connect to DU-cell 1 in parent DU1, while MT-CC2 can connect to DU-cell 4 in parent DU2. In this configuration, the link between MT-CC1 and DU-cell 1, and the link between MT-CC2 and DU-cell 4, can operate in the same or adjacent frequency regions. From the perspective of IAB MT1, the link between MT-CC1 and DU-cell 1 can be referred to as parent link 1, and the link between MT-CC2 and DU-cell 4 can be referred to as parent link 2.

[0337] In this scenario, if the DL / UL directions of parent link 1 and parent link 2 differ in terms of resources at a given time, cross-link interference may occur between the two parent links, thus degrading performance. Therefore, the DL / UL directions of the two parent links should be aligned simultaneously.

[0338] For DL / UL direction alignment between two parent links from the perspective of IAB-MT1, when the DL / UL directions of the parent links are not aligned, it is necessary to restrict the DL or UL operations of a specific parent link. In this invention, for ease of explanation, the two parent IAB DUs of IABMT1 are divided into V-DU-cells (victim DU-cells) and A-DU-cells (infringing DU-cells). In this case, considering the DL / UL operations of the V-DU-cell, the A-DU-cell performs operations that restrict its DL / UL operations (i.e., DL / UL alignment technique).

[0339] exist Figure 26 For example, parent IAB DU1 becomes V-DU-cell, and parent IAB DU2 becomes A-DU-cell. For convenience, the MT-CC in IAB MT1 connected to the V-DU-cell (i.e., MT-CC1) is called V-MT-CC, and for the same reason, the MT-CC connected to the A-DU-cell (i.e., MT-CC2) is called A-MT-CC. Furthermore, from the perspective of IAB MT, the link between V-MT-CC and V-DU-cell is called the V-parent link, and the link between A-MT-CC and A-DU-cell is called the A-parent link.

[0340] In this disclosure, the scenario where parent DU1 and parent DU2 are connected to the same donor node / CU is considered and described. However, the contents of this disclosure can also be applied when connected to different donor nodes / CUs.

[0341] Configuration of AV-DU and A-DU cells

[0342] When an IAB MT connects to two parent DU cells (= parent IAB DU cells), and these two parent DU cells belong to different parent DUs, these two parent DU cells can be either a V-DU-cell and an A-DU-cell or an A-DU-cell and a V-DU-cell. In this case, the method for determining whether a specific parent DU cell is a V-DU-cell or an A-DU-cell can be as follows.

[0343] Method aV-DU-cell can be the parent DU-cell of the MCG (Carrier Group) within two CGs (Carrier Groups) belonging to IAB MT. A-DU-cell becomes the parent DU-cell of the SCG within two CGs belonging to IAB MT.

[0344] Method bV-DU-cell can be the parent DU-cell of an SCG (Carrier Group) within two CGs (Carrier Groups) belonging to IAB MT. A-DU-cell becomes the parent DU-cell of an MCG within two CGs belonging to IAB MT.

[0345] Method cV-DU-cells and A-DU-cells can be determined through specific configuration / signaling. For example, a parent DU-cell can be explicitly or implicitly configured as an A-DU-cell from the donor node / CU of the parent node DU-cell. Alternatively, IABMT can explicitly or implicitly indicate that it is an A-DU-cell. For example, a parent node DU-cell can be determined to be an A-DU-cell as follows.

[0346] 1. It can be explicitly configured as an A-DU cell.

[0347] 2. It can determine that it is an A-DU cell by receiving the configuration used to perform DL / UL alignment technology.

[0348] 3. By setting / receiving information about the V-DU cell, V-MT-CC, and / or V-parent link to be considered for performing DL / UL alignment, it can be determined that it is an A-DU cell and should perform DL / UL alignment. In this case, "information about the A-DU cell to be considered for performing DL / UL alignment" may include, for example, all or part of the following: a) D / U / F resource configuration information in the DU configuration of the V-DU cell, b) H / S / NA resource configuration information in the DU configuration of the V-DU cell, c) MT configuration information (i.e., D / U / F resource configuration information) of the V-MT-CC.

[0349] B. Methods for performing DL / UL alignment between two parent links

[0350] When an IAB MT connects to two parent DU-cells belonging to different parent DUs, cross-link interference between the two parent links may occur and cause performance degradation if the DL / UL directions of the two parent links differ in terms of resources at a given time. Therefore, the DL / UL directions of the two parent links should be aligned simultaneously.

[0351] The following section presents a method for aligning the DL / UL directions between two parent links when the IAB MT is connected to different parent DUs. In this case, one of the following methods can be applied, or a combination of several methods can be used.

[0352] Method a. A method based on DU H / S / NA configuration.

[0353] Each DU-cell is configured with H (hard) / S (soft) / NA (unavailable, unusable) information of DU resources through DU configuration (this can be called attribute information). In this case, considering the H / S / NA configuration information of the V-DU-cell, the A-DU-cell can restrict its DL / UL operation.

[0354] To perform this operation, the A-DU cell needs to know the H / S / NA configuration information of the V-DU cell. To do this, the A-DU cell can receive information related to the V-DU cell's H / S / NA configuration from the donor node / CU. Specifically, this information can be as follows.

[0355] 1. Set / share V-DU-cell's hard, soft, and unavailable (NA) resource information (attribute information).

[0356] 2. Configure / share NA resource information for V-DU cells.

[0357] When a DU cell receives the above configuration, it identifies itself as an A-DU cell that restricts DL / UL operations for DL / UL alignment, and can perform DL / UL alignment operations. At this point, from the perspective of the corresponding A-DU cell, the DU cell considering DL / UL alignment becomes a V-DU cell.

[0358] Specifically, the A-DU cell can perform the following operations for DL / UL alignment.

[0359] Method a-1.

[0360] In method a-1, one parent DU-cell becomes a V-DU-cell, and the other parent DU-cell becomes an A-DU-cell. The V-DU-cell is not restricted from DL / UL operations because the A-DU-cell is not, while the V-DU-cell results in only the A-DU-cell potentially being restricted from DL / UL operations. The A-DU-cell can operate in the resources where it intends to perform transmit / receive operations as follows.

[0361] Because A-DU cells do not perform transmit / receive operations in NA resources, A-DU cells do not need to perform operations that restrict their UL / DL for DL / UL alignment.

[0362] Regarding resources where a V-DU cell is configured as an NA, an A-DU cell does not perform operations that restrict its own DL / UL for DL / UL alignment.

[0363] The A-DU cell performs restricted DL / UL operations by using i) method b or c below, which are set to hard resources for the V-DU cell. Alternatively, ii) it can perform its own DL / UL operations without considering the V-DU cell. In this case, method d below can be used together.

[0364] The A-DU cell performs restricted DL / UL operations by using i) method b or method c below, which are configured as soft resources for the V-DU cell. Alternatively, ii) it can perform its own DL / UL operations without considering the V-DU cell. In this case, method d below can be used together.

[0365] Method a-2.

[0366] In method a-2, each of the two parent DU-cells considers itself an A-DU-cell and the other a V-DU-cell. That is, assuming the two parent DU-cells are DU-cell 1 and DU-cell 2, DU-cell 1 determines it is an A-DU-cell and DU-cell 2 is a V-DU-cell and performs DL / UL alignment operations. DU-cell 2 can determine it is an A-DU-cell and DU-cell 1 is a V-DU-cell, and can also perform DL / UL alignment operations. In this case, it can operate as follows.

[0367] Because A-DU cells do not perform transmit / receive operations in NA resources, A-DU cells do not need to perform operations that restrict their UL / DL for DL / UL alignment.

[0368] Regarding resources where V-DU-cells are configured as NA, A-DU-cells do not perform operations that restrict their own UL / DL for DL / UL alignment.

[0369] For resources that are set to hard and V-DU-cells are set to soft, A-DU-cells do not perform operations that restrict their own UL / DL for DL / UL alignment.

[0370] For resources where the A-DU cell is configured as soft and the V-DU cell is configured as hard, i) the A-DU cell performs restricted DL / UL operations using method b or method c below. Alternatively, ii) it can perform its own DL / UL operations without considering the V-DU cell. In this case, method d below can be used together.

[0371] For resources where both A-DU cells and V-DU cells are configured as hard, i) the A-DU cell performs restricted DL / UL operations using method b or method c below. Alternatively, ii) it can perform its own DL / UL operations without considering the V-DU cell. In this case, method d below can be used together.

[0372] For resources where both A-DU cells and V-DU cells are configured as soft, i) the A-DU cell performs restricted DL / UL operations using method b or method c below. Alternatively, ii) it can perform its own DL / UL operations without considering the V-DU cell. In this case, method d below can be used together.

[0373] Method b. A method based on DU D / U / F configuration (time slot format information).

[0374] Each DU-cell receives D / U / F information (time slot format information, the same below) of DU resources through DU configuration. In this case, the A-DU-cell can consider the D / U / F configuration information of the V-DU-cell to limit its DL / UL operation.

[0375] To perform this operation, the A-DU cell needs to know the D / U / F configuration information of the V-DU cell. For this purpose, the A-DU cell can receive the D / U / F configuration information of the V-DU cell from the donor node / CU.

[0376] Upon receiving the above configuration, the DU cell can identify itself as an A-DU cell that needs to restrict DL / UL operations for DL / UL alignment, and can perform the operations for DL / UL alignment. At this time, from the perspective of the corresponding A-DU cell, the DU cell that the A-DU cell considers for DL / UL alignment becomes a V-DU cell.

[0377] Typically, DL / UL alignment operations can be applied only to resources capable of transmitting / receiving both A-DU-cells and V-DU-cells (or having the potential to perform transmission / reception). For example, DL / UL alignment operations can be applied to resources where neither A-DU-cells nor V-DU-cells are set to NA.

[0378] Specifically, the A-DU cell can perform the following operations for DL / UL alignment.

[0379] For a UL resource configured for a V-DU cell, the A-DU cell does not perform a DL operation when the resource is configured for a DL resource for an A-DU cell or when the A-DU cell needs to perform a DL operation.

[0380] For resources configured for DL ​​in V-DU cells, A-DU cells do not perform UL operations when the resource is configured as a UL resource in A-DU cells or when A-DU cells need to perform UL operations.

[0381] For a flexible (F) resource configured for a V-DU-cell, i) when the resource is configured as a DL resource for an A-DU-cell or when the A-DU-cell needs to perform a DL operation, the A-DU-cell does not perform a DL operation. And, when the resource is configured as a UL resource for an A-DU-cell or when the A-DU-cell needs to perform a UL operation, the A-DU-cell does not perform a UL operation. Or ii) it can perform its own DL / UL operation without considering the V-DU-cell. In this case, method d below can be used together.

[0382] Figure 27 The diagram illustrates the operation performed by the first DU of the first parent node communicating with the IAB node in a wireless communication system.

[0383] refer to Figure 27 The first parent node obtains the first configuration information for the first DU (S271), and obtains the second configuration information of the second DU of the second parent node communicating with the MT (S272).

[0384] The first configuration information may include at least one of the following: time slot format information indicating whether a specific resource is used for a downlink symbol, uplink symbol, or flexible symbol of the first DU, and attribute information indicating whether the specific resource is configured as hard, soft, or unavailable (NA) for the first DU.

[0385] The second configuration information may include at least one of the following: time slot format information indicating whether a specific resource is used for a downlink symbol, uplink symbol, or flexible symbol of the second DU, and attribute information indicating whether the specific resource is configured as hard, soft, or unavailable (NA) for the second DU.

[0386] The first parent node restricts the downlink transmission or uplink reception operations of the first DU based on the first configuration information and the second configuration information (S273).

[0387] For example, if it is determined that the first DU and the second DU are configured to perform simultaneous operations that are not supported by the MT of the IAB node in a specific resource, the first DU can restrict the operation according to the first configuration information.

[0388] More specifically, when the second DU is configured as hard or soft for a specific resource, the first DU can restrict operations on that specific resource according to the first configuration information. For example, when the second DU is configured as an uplink symbol for a specific resource and the first DU is configured as a downlink symbol for the specific resource, the first DU can restrict operations on that specific resource according to the first configuration information (i.e., not perform downlink transmission on the specific resource). When the second DU is configured as a downlink symbol for a specific resource and the first DU is configured as an uplink symbol for the specific resource, the first DU can restrict operations on that specific resource according to the first configuration information (i.e., not perform uplink reception on the specific resource). When the second DU is configured as a flexible symbol for a specific resource and the first DU is configured as either a downlink symbol or an uplink symbol for the specific resource, the first DU can restrict operations on that specific resource according to the first configuration information (i.e., not perform downlink transmission or uplink reception on the specific resource).

[0389] This method can be considered a combination of method a and method b mentioned above.

[0390] Figure 28 The diagram is based on Figure 27 The detailed operation methods for the first parent node, IAB node, and second parent node are described below.

[0391] refer to Figure 28 The first parent node includes the first DU. The first parent node obtains the first configuration information of the first DU (S281). For example, the first parent node can receive the time slot format information and attribute information of the first DU from its donor node or centralized unit (CU).

[0392] The first parent node obtains the second configuration information of the second DU (S282). For example, the first parent node can receive the time slot format information and attribute information of the second DU from its donor node or CU.

[0393] When the simultaneous operation supported by the MT of the IAB node is configured in the first resource, the first parent node (specifically, the first DU) performs the operation according to the first configuration information (S283).

[0394] The second parent node (specifically, the second DU) performs operations on the first resource based on the second configuration information (S284).

[0395] For example, when the second DU of the second parent node is configured as a downlink in terms of resource direction and as hard in terms of attributes according to the second configuration information, if the first DU of the first parent node is configured as a downlink in terms of resource direction according to the first configuration information, then because this is a simultaneous operation supported by MT, the operation according to the first configuration information (i.e., downlink transmission) is performed.

[0396] The second parent node (specifically, the second DU) performs the operation based on the second configuration information on the second resource (S285). When the MT of the IAB node is configured in the second resource to not support simultaneous operation, the first parent node (specifically, the first DU) does not perform the operation based on the first configuration information and imposes restrictions (S286).

[0397] For example, when the second resource is set as uplink in terms of resource direction and hard in terms of attribute for the second DU of the second parent node according to the second configuration information, if the second resource is configured as downlink in terms of resource direction for the first DU of the first parent node according to the first configuration information, then because this is a simultaneous operation not supported by MT, the operation according to the first configuration information is restricted, that is, downlink transmission (i.e., downlink transmission is not performed).

[0398] Figure 29 This example illustrates a method for determining whether the first DU of the first parent node will perform an operation based on the first configuration information.

[0399] refer to Figure 29 The first DU of the first parent node determines whether a specific resource is set as a hard resource or a soft resource for the second DU of the second parent node (S291). The first DU can determine this based on the second configuration information of the second DU.

[0400] If a specific resource is set to NA for the second DU, the first DU does not restrict operations based on the first configuration information (S292).

[0401] On the other hand, if a specific resource is set to hard or soft for the second DU, the first DU can determine whether to restrict operations based on the first configuration information based on the direction (D / U / F) of configuring the specific resource for the second DU and the direction (D / U / F) of configuring the specific resource for the first DU (S293).

[0402] For example, when a specific resource of the second DU is set to soft in terms of attributes and set to an uplink symbol in terms of resource direction, if a specific resource of the first DU is configured as a downlink symbol, the first DU can restrict operations in the specific resource according to the first configuration information (i.e., not perform downlink transmissions in the specific resource).

[0403] As another example, when a specific resource of the second DU is set to hard in terms of attributes and set to a downlink symbol in terms of resource direction, if a specific resource of the first DU is configured to an uplink symbol, the first DU can restrict operations in the specific resource according to the first configuration information (i.e., not perform uplink reception in the specific resource).

[0404] As another example, when a specific resource of the second DU is set to hard in terms of attributes and flexible in terms of resource direction, if a specific resource of the first DU is configured as a downlink symbol or an uplink symbol, the first DU can restrict operations in the specific resource according to the first configuration information (i.e., not perform downlink transmission or uplink reception in the specific resource).

[0405] Method c. Method based on MTD / U / F configuration

[0406] Each MT-CC receives D / U / F information of MT resources through MT configuration. In this case, the A-DU-cell can consider the MT D / U / F configuration information of the V-MT-CC to limit its DL / UL operation.

[0407] To perform this operation, the A-DU-cell needs to know the MT D / U / F configuration information of the V-MT-CC. For this purpose, the A-DU-cell can receive MT D / U / F configuration-related information of the V-MT-CC from the donor node / CU. Alternatively, the A-DU-cell can receive information related to the MT D / U / F configuration of the V-MT-CC from the A-MT-CC.

[0408] Upon receiving the above configuration, the DU-cell can identify itself as an A-DU-cell that needs to restrict DL / UL operations for DL / UL alignment, and can perform the DL / UL alignment operation. At this point, from the perspective of the A-DU-cell, the MT-CC that the A-DU-cell considers for DL / UL alignment becomes the V-MT-CC. The parent DU-cell connected to the V-MT-CC becomes the V-DU-cell.

[0409] Typically, the operation for DL / UL alignment can be applied only to resources where both A-DU-cells and V-DU-cells can transmit / receive, or resources where both A-DU-cells and V-DU-cells can perform transmission / reception. For example, the operation for DL / UL alignment can be applied to resources where neither A-DU-cells nor V-DU-cells are set to NA.

[0410] Specifically, the A-DU cell can perform DL / UL alignment as follows.

[0411] Regarding V-MT-CC being configured as a UL resource, when A-DU-cell is configured as a DL resource or requires DL operation, A-DU-cell will not perform DL operation.

[0412] Regarding V-MT-CC being configured as a DL resource, when A-DU-cell is configured as a UL resource or requires UL operation, A-DU-cell does not perform UL operation.

[0413] Regarding V-MT-CC being configured as a F (flexible) resource, when the A-DU-cell is configured as a DL resource or requires DL operation, the A-DU-cell does not perform DL operation. And when the A-DU-cell is configured as a UL resource or requires UL operation, the A-DU-cell does not perform UL operation. Alternatively, ii) it can perform its own DL / UL operation without considering V-MT-CC. In this case, method d below can be used together.

[0414] Method d. Priority-based method

[0415] An IAB MT can connect to two parent DU-cells via two MT-CCs, and these two parent DU-cells can belong to different parent DUs. In this case, when the two MT-CCs are configured or scheduled to perform DL reception and DU transmission (or UL transmission and DL reception) respectively in the same resource (same time resource), each MT-CC can operate as follows.

[0416] Method d-1. A-MT-CC does not operate, while V-MT-CC performs the scheduled send / receive operation.

[0417] Method d-2.V-MT-CC does not operate, while A-MT-CC performs the scheduled send / receive operation.

[0418] Method d-3. Regardless of the operation of the MT-CC, a DL signal will be transmitted. Therefore, the MT-CC scheduled for DL ​​reception performs DL reception, while the MT-CC scheduled for UL transmission does not perform UL transmission.

[0419] For example, the following process enables two MT-CCs and two parent node DU-cells to determine and perform operations when the DL / UL directions do not match.

[0420] 1) The parent DU-cell uses the H / S / NA resource information of other parent DU-cells based on IAB MT to determine the resources that can operate without restrictions and the resources that may need to be restricted.

[0421] 2) For resources that may need to be restricted by 1), the parent DU cell determines the resources that can be transmitted / received on it and the resources that cannot be transmitted / received on it based on the D / U / F resource information of other parent DU cells of IAB MT.

[0422] 3) When it is necessary to perform DL and UL or UL and DL operations separately through two parent links (in the case of scheduling), the two MT-CCs in IABMT determine whether their own transmission / reception is possible based on their DL / UL operations and / or whether they are A-MT-CC / V-MT-CC.

[0423] Figure 30 This is an example of how to operate an IAB node.

[0424] Identify whether each of the two parent DU cells connected to the IAB MT is a V-DU-cell or an A-DU-cell (S101). The specific identification method has been described in "Configuration of AV-DU Cells and A-DU Cells". For example, as mentioned above, the parent DU cell itself can be explicitly or implicitly configured as an A-DU-cell from the donor node / CU of the parent DU cell.

[0425] Within a specific time resource, the A-DU-cell determines whether the transmission directions in the two parent links between the IAB MT and each parent DU cell are different (S102). When the transmission directions in the two parent links are different, the A-DU-cell can restrict its DL / UL operation based on the configuration information of the V-DU-cell (S103). Specific examples of operation restrictions have already been described in "B. Method for Performing DL / UL Alignment Between Two Parent Links".

[0426] Figure 31 The illustration shows a wireless device applicable to this instruction manual.

[0427] refer to Figure 31 The first wireless device 100 and the second wireless device 200 can transmit radio signals via various RATs (e.g., LTE and NR).

[0428] The first wireless device 100 may include one or more processors 102 and one or more memories 104, and further includes one or more transceivers 106 and / or one or more antennas 108. The processor 102 may control the memory 104 and / or the transceiver 106 and may be configured to implement the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. For example, the processor 102 may process information in the memory 104 to generate a first information / signal, and then transmit a radio signal including the first information / signal via the transceiver 106. Furthermore, the processor 102 may receive a radio signal including a second information / signal via the transceiver 106, and then store the information obtained by processing the second information / signal in the memory 104. The memory 104 may be connected to the processor 102 and may store various information relating to the operation of the processor 102. For example, the memory 104 may store software code, including commands for performing some or all of the processes controlled by the processor 102 or for performing the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. Here, processor 102 and memory 104 may be part of a communication modem / circuit / chip designed to implement RAT (e.g., LTE or NR). Transceiver 106 may be connected to processor 102 and transmit and / or receive radio signals via one or more antennas 108. Transceiver 106 may include a transmitter and / or a receiver. Transceiver 106 may be used interchangeably with a radio frequency (RF) unit. In this specification, wireless device may refer to a communication modem / circuit / chip.

[0429] The second wireless device 200 may include one or more processors 202 and one or more memories 204, and further includes one or more transceivers 206 and / or one or more antennas 208. The processor 202 can control the memory 204 and / or the transceiver 206 to be configured to implement the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. For example, the processor 202 may process information in the memory 204 to generate a third message / signal, and then transmit a radio signal including the third message / signal via the transceiver 206. Furthermore, the processor 202 may receive a radio signal including a fourth message / signal via the transceiver 206, and then store the information obtained from processing the fourth message / 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 commands for performing some or all of the processes controlled by the processor 202 or for performing the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. Here, processor 202 and memory 204 may be part of a communication modem / circuit / chip designed to implement RAT (e.g., LTE or NR). Transceiver 206 may be connected to processor 202 and transmit and / or receive radio signals via one or more antennas 208. Transceiver 206 may include a transmitter and / or a receiver. Transceiver 206 may be used interchangeably with an RF unit. In this specification, wireless device may refer to a communication modem / circuit / chip.

[0430] The hardware elements of wireless devices 100 and 200 will be described in more detail below. One or more protocol layers may be implemented by, but are not limited to, one or more processors 102 and 202. For example, one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, and SDAP). One or more processors 102 and 202 may generate one or more Protocol Data Units (PDUs) and / or one or more Service Data Units (SDUs) according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. One or more processors 102 and 202 may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. One or more processors 102 and 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document, and provide the generated signals to one or more transceivers 106 and 206. One or more processors 102 and 202 may receive signals (e.g., baseband signals) from one or more transceivers 106 and 206 and acquire PDUs, SDUs, messages, control information, data, or information in accordance with the descriptions, functions, procedures, suggestions, methods, and / or operation flowcharts disclosed in this document.

[0431] One or more processors 102 and 202 may be referred to as a controller, microcontroller, microprocessor, or microcomputer. One or more processors 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more application-specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), or one or more field-programmable gate arrays (FPGAs) may be included in one or more processors 102 and 202.

[0432] One or more processors 102 and 202 may be implemented using at least one computer-readable medium (CRM) including instructions to be executed by at least one processor.

[0433] That is, at least one computer-readable medium (CRM) having instructions to be executed by at least one processor to perform operations includes obtaining first configuration information of a first distributed unit (DU) of a first parent node for communicating with a mobile terminal (MT) of an IAB node, obtaining second configuration information of a second DU of a second parent node for communicating with the MT, and restricting downlink transmission or uplink reception operations of the first DU based on the first and second configuration information.

[0434] The descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed herein can be implemented using firmware or software, and the firmware or software can be configured to include modules, processes, functions, etc. Firmware or software configured to perform the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed herein can be included in at least one processor 102 and 202 or can be stored in at least one memory 104 and 204 and can be executed by at least one processor 102 and 202. The descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed herein can be implemented using firmware or software in the form of code, instructions, and / or instruction sets.

[0435] 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 combinations thereof. At least one memory 104 and 204 may be arranged internally and / or externally to at least one processor 102 and 202. Furthermore, 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.

[0436] At least one transceiver 106 and 206 can transmit user data, control information, radio signals / channels, etc., as mentioned in the methods and / or operation flowcharts disclosed herein, to at least one different device. At least one transceiver 106 and 206 can receive user data, control information, radio signals / channels, etc., as mentioned in the descriptions, functions, processes, proposals, methods, and / or operation flowcharts 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 transmit and receive radio signals. For example, at least one processor 102 and 202 can control at least one transceiver 106 and 206 to transmit user data, control information, or radio signals to at least one different device. Furthermore, 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 transmit or receive user data, control information, radio signals / channels, etc., as described herein in the description, function, process, proposal, method, and / or operation flowcharts, via at least one antenna 108 and 208. In this document, at least one antenna may be multiple physical antennas or multiple 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 for processing 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. For this purpose, at least one transceiver 106 and 206 may include (analog) oscillators and / or filters.

[0437] Figure 32 An example of the structure of a signal processing module is shown. Here, signal processing can be performed... Figure 31 It is executed in processors 102 and 202.

[0438] refer to Figure 32 The transmitting device (e.g., processor, processor and memory, or processor and transceiver) in the UE or BS may include a scrambler 301, a modulator 302, a layer mapper 303, an antenna port mapper 304, a resource block mapper 305, and a signal generator 306.

[0439] The transmitting device can transmit one or more codewords. The encoded bits in each codeword are scrambled by a corresponding scrambler 301 and transmitted over the physical channel. The codeword can be referred to as a data string and can be equivalent to a transport block as a data block provided by the MAC layer.

[0440] The scrambling bits are modulated into complex-valued modulation symbols by the corresponding modulator 302. Modulator 302 can modulate the scrambling bits according to a modulation scheme to arrange complex-valued modulation symbols representing positions on the signal constellation. The modulation scheme is unrestricted and can use m-PSK (M-Phase Shift Keying) or m-QAM (M-Quadrature Amplitude Modulation) to modulate the coded data. The modulator can be referred to as a modulation mapper.

[0441] Complex-valued modulation symbols can be mapped to one or more transmission layers by layer mapper 303. Complex-valued modulation symbols on each layer can be mapped by antenna port mapper 304 for transmission on antenna ports.

[0442] Each resource block mapper 305 can map the complex-valued modulation symbols for each antenna port to the appropriate resource elements in the virtual resource blocks allocated for transmission. The resource block mapper can map virtual resource blocks to physical resource blocks according to an appropriate mapping scheme. The resource block mapper 305 can assign the complex-valued modulation symbols for each antenna port to the appropriate subcarriers and multiplex the complex-valued modulation symbols according to the user.

[0443] Signal generator 306 can modulate complex-valued modulation symbols (i.e., antenna-specific symbols) for each antenna port according to a specific modulation scheme (e.g., OFDM (Orthogonal Frequency Division Multiplexing)) to generate complex-valued time-domain OFDM symbol signals. The signal generator can perform an IFFT (Inverse Fast Fourier Transform) on the antenna-specific symbols and can insert a CP (Cyclic Prefix) into the time-domain symbols that have already undergone the IFFT. The OFDM symbols undergo digital-to-analog conversion and up-conversion before being transmitted to the receiving device through each transmit antenna. The signal generator may include an IFFT module, a CP insertion unit, a digital-to-analog converter (DAC), and an up-converter.

[0444] Figure 33 This is another example diagram illustrating the structure of a signal processing module in a transmitting device. Here, signal processing can be performed in the processor of the UE / BS, such as... Figure 31 Processors 102 and 202.

[0445] refer to Figure 33 The transmitting device (e.g., processor, processor and memory, or processor and transceiver) in the UE or BS may include a scrambler 401, a modulator 402, a layer mapper 403, a precoder 404, a resource block mapper 405, and a signal generator 406.

[0446] The transmitting device can scramble the encoded bits in the codeword using the corresponding scrambler 401, and then transmit the scrambled encoded bits through the physical channel.

[0447] The scrambling bits are modulated into complex-valued modulation symbols by the corresponding modulator 402. The modulator can modulate the scrambling bits according to a predetermined modulation scheme to arrange complex-valued modulation symbols representing the positions on the signal constellation. The modulation scheme is unrestricted and can use pi / 2-BPSK (pi / 2-binary phase shift keying), m-PSK (m-phase shift keying), or m-QAM (m-quadrature amplitude modulation) to modulate the coded data.

[0448] Complex-valued modulation symbols can be mapped to one or more transport layers by layer mapper 403.

[0449] Complex-valued modulation symbols on each layer can be pre-encoded by pre-encoder 404 for transmission at the antenna ports. Here, the pre-encoder can perform transform precoding on the complex-valued modulation symbols, followed by precoding. Alternatively, the pre-encoder can perform precoding without performing transform precoding. Pre-encoder 404 can use multiple transmission antennas to process the complex-valued modulation symbols according to MIMO, outputting antenna-specific symbols and assigning them to the corresponding resource block mapper 405. The output z of pre-encoder 404 can be obtained by multiplying the output y of layer mapper 403 by an N×M precoding matrix W. Here, N is the number of antenna ports and M is the number of layers.

[0450] Each resource block mapper 405 maps the complex-valued modulation symbol for each antenna port to the appropriate resource element in the virtual resource block allocated for transmission.

[0451] Resource block mapper 405 can assign complex-valued modulation symbols to appropriate subcarriers and multiplex complex-valued modulation symbols according to users.

[0452] Signal generator 406 can modulate complex-valued modulation symbols according to a specific modulation scheme (e.g., OFDM) to generate complex-valued time-domain OFDM symbol signals. Signal generator 406 can perform IFFT (Inverse Fast Fourier Transform) on antenna-specific symbols and can insert a CP (Cyclic Prefix) into the time-domain symbols that have already undergone IFFT. The OFDM symbols undergo digital-to-analog conversion and up-conversion before being transmitted to the receiving device through each transmit antenna. Signal generator 406 may include an IFFT module, a CP insertion unit, a digital-to-analog converter (DAC), and an up-converter.

[0453] The signal processing of a receiving device can be the reverse of that of a transmitting device. Specifically, the processor of the transmitting device decodes and demodulates the RF signals received through the antenna ports of the transceiver. The receiving device may include multiple receiving antennas, and the signals received through the receiving antennas are recovered into baseband signals, then multiplexed and demodulated according to MIMO to recover the data string intended to be transmitted by the transmitting device. The receiving device may include a signal recovery unit to recover the received signals into baseband signals, a multiplexer for combining and multiplexing the received signals, and a channel demodulator for demodulating the multiplexed signal string into corresponding codewords. The signal recovery unit, multiplexer, and channel demodulator may be configured as integrated modules or independent modules for performing their functions. More specifically, the signal recovery unit may include an analog-to-digital converter (ADC) for converting analog signals into digital signals, a CP removal unit for removing CP from digital signals, a FET module for applying FFT (Fast Fourier Transform) to the CP-removed signal to output frequency domain symbols, and a resource element demapper / equalizer for recovering the frequency domain symbols into antenna-specific symbols. Antenna-specific symbols are recovered to the transport layer by the multiplexer, and the transport layer is recovered to the codewords intended to be transmitted by the transmitting device by the channel demodulator.

[0454] Figure 34 The illustration shows an example of a wireless communication device according to an embodiment of this disclosure.

[0455] refer to Figure 34 The wireless communication device, for example, the UE, may include at least one of the following: a processor 2310 such as a digital signal processor (DSP) or microprocessor; a transceiver 2335; a power management module 2305; an antenna 2340; a battery 2355; a display 2315; a keypad 2320; a global positioning system (GPS) chip 2360; a sensor 2365; a memory 2330; a subscriber identification module (SIM) card 2325; a speaker 2345; and a microphone 2350. Multiple antennas and multiple processors may be provided.

[0456] The processor 2310 is capable of implementing the functions, processes and methods described in this specification. Figure 34 The processor 2310 in the middle can be Figure 31 Processors 102 and 202 in the middle.

[0457] The memory 2330 is connected to the processor 2310 and stores information related to the operation of the processor. The memory can be located inside or outside the processor and can be connected to the processor via various technologies such as wired and wireless connections. Figure 34 The memory 2330 in the memory can be Figure 31 The memory in the memory is 104 and 204.

[0458] Users can use various techniques, such as pressing buttons on keypad 2320 or activating sound using microphone 2350, to input various types of information, such as phone numbers. Processor 2310 can receive and process user information and perform appropriate functions, such as making a call using the entered phone number. In some scenarios, data can be retrieved from SIM card 2325 or memory 2330 to perform appropriate functions. In some scenarios, for user convenience, processor 2310 can display various types of information and data on display 2315.

[0459] Transceiver 2335 is connected to processor 2310 and transmits and / or receives RF signals. The processor can control the transceiver to initiate communication or transmit RF signals comprising various types of information or data such as voice communication data. The transceiver includes a transmitter and a receiver for transmitting and receiving RF signals. Antenna 2340 facilitates the transmission and reception of RF signals. In some embodiments, when the transceiver receives an RF signal, it can forward the signal and convert it to a baseband frequency for processing by the processor. The signal can be processed using various techniques, such as converting it into audible or readable information to be output through speaker 2345. Figure 34 The transceiver in the middle can be Figure 31 The transceivers in the middle are 106 and 206.

[0460] Although Figure 34 As not shown in the diagram, various components such as a camera and a Universal Serial Bus (USB) port may be additionally included in the UE. For example, the camera may be connected to the processor 2310.

[0461] Figure 34 This is an implementation example of a UE, and the implementation examples disclosed herein are not limited to this. The UE does not need to inherently include... Figure 34 All components are shown. That is to say, some components, such as the keyboard 2320, GPS chip 2360, sensor 2365, and SIM card 2325, may not be required. In this case, they may not be included in the UE.

[0462] Figure 35 An example of a processor 2000 is shown.

[0463] refer to Figure 35 The processor 2000 may be included in the first parent node, and may include a monitoring unit 2010 and a transceiver 2020. The processor 2000 may execute reference... Figures 22 to 28The described method. For example, processor 2000 can obtain first configuration information of the first DU and second configuration information of the second DU communicating with the second parent node of the MT through monitoring unit 2010. Furthermore, based on the first and second configuration information, transceiver 2020 can restrict downlink transmission or uplink reception operations of the first DU. Processor 2000 may be... Figure 31 Examples of processors 102 and 202.

[0464] Figure 36 An example of processor 3000 is shown.

[0465] refer to Figure 36 The processor 3000 may be included in a donor node or CU connected to a first parent node and a second parent node, and may include a control information / data encoding / decoding module 3010 and a transmit / receive module 3020. The processor 3000 can perform reference... Figures 22 to 28 The method described. For example, processor 3000 generates first configuration information for a first DU of a first parent node through control information / data encoding / decoding module 3010, and generates second configuration information for a second DU of a second parent node communicating with the MT of the IAB node. The first and second configuration information can be sent to the first parent node through sending / receiving module 3020. Processor 3000 can be... Figure 31 Examples of processors 102 and 202.

[0466] Figure 37 Another example of a wireless device is shown.

[0467] refer to Figure 37 The wireless device may include one or more processors 102 and 202, one or more memories 104 and 204, one or more transceivers 106 and 206, and one or more antennas 108 and 208.

[0468] Figure 37 The examples of wireless devices described in the text are different. Figure 37 The wireless examples described herein differ in that processors 102 and 202 and memories 104 and 204 are in Figure 31 The memory is separate, however, memories 104 and 204 are included. Figure 37 In the examples of processors 102 and 202, that is, the processor and memory can form a chipset.

[0469] Figure 38 Another example of a wireless device used in this specification is shown. Wireless devices can be implemented in various forms depending on the use case / service.

[0470] refer to Figure 38Wireless devices 100 and 200 can correspond to Figure 37 The wireless devices 100 and 200 can be configured with various elements, components, units / parts, and / or modules. For example, each of the wireless devices 100 and 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 communication circuitry 112 and a transceiver 114. For example, communication circuitry 112 may include one or more processors 102 and 202 and / or one or more memories 104 and 204. For example, transceiver 114 may include... Figure 37 One or more transceivers 106 and 206 and / or one or more antennas 108 and 208 are included. Control unit 120 is electrically connected to communication unit 110, memory 130, and add-on components 140 and controls the overall operation of the wireless device. For example, control unit 120 can control the electrical / mechanical operation of the wireless device based on programs / code / commands / information stored in memory unit 130. Furthermore, control unit 120 can transmit information stored in memory unit to an external (e.g., other communication device) 130 via wireless / wired interface through communication unit 110, or store information received from an external (e.g., other communication device) via wireless / wired interface in memory unit 130 via communication unit 110.

[0471] The additional component 140 can be configured differently depending on the type of wireless device. For example, the additional component 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 can be, but is not limited to, a robot ( Figure 40 100a), vehicles ( Figure 40 100b-1 and 100b-2), XR equipment ( Figure 40 100c), handheld devices ( Figure 40 100d), home appliances ( Figure 40 100e), IoT devices ( Figure 40 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 ( Figure 40 400), BS ( Figure 40 It can be implemented in the form of 200 (network nodes, etc.). Depending on the use case / service, wireless devices can be used in mobile or fixed locations.

[0472] exist Figure 38In wireless devices 100 and 200, the various elements, components, units / parts, and / or modules can be interconnected via a wired interface, or at least a portion thereof can be wirelessly connected via communication unit 110. For example, in each of wireless devices 100 and 200, control unit 120 and communication unit 110 can be wired connected, and control unit 120 and first units (e.g., 130 and 140) can be wirelessly connected via communication unit 110. Furthermore, each element, component, unit / part, and / or module within wireless devices 100 and 200 may further include one or more elements. For example, control unit 120 may be configured as a collection of one or more processors. For example, control unit 120 may be configured as a collection of communication control processors, application processors, electronic control units (ECUs), graphics processing units, and memory control processors. As another example, memory 130 may be configured as random access memory (RAM), dynamic RAM (DRAM), read-only memory (ROM), flash memory, volatile memory, non-volatile memory, and / or combinations thereof.

[0473] Figure 39 The illustrations refer to handheld devices used in this specification. Handheld devices may include smartphones, smartpads, wearable devices (e.g., smartwatches or smart glasses), or portable computers (e.g., laptops). Handheld devices may be referred to as mobile stations (MS), user terminals (UT), mobile user stations (MSS), user stations (SS), advanced mobile stations (AMS), or wireless terminals (WT).

[0474] refer to Figure 39 The handheld device 100 may include an antenna unit 108, a communication unit 110, a control unit 120, a memory unit 130, a power supply unit 140a, an interface unit 140b, and an I / O unit 140c. The antenna unit 108 may be configured as part of the communication unit 110. Blocks 110 to 130 / 140a to 140c respectively correspond to... Figure 38 Blocks 110 to 130 / 140.

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

[0476] For example, in data communication, input / output unit 140c can acquire information / signals input from the user (e.g., touch, text, voice, image, and video), and the acquired information / signals can be stored in storage unit 130. Communication unit 110 can convert the information / signals stored in storage unit into radio signals, and can directly transmit the converted radio signals to different wireless devices or base stations. Furthermore, communication unit 110 can receive radio signals from different wireless devices or base stations, and can reconstruct the received radio signals into the original information / signals. The reconstructed information / signals can be stored in storage unit 130, and can then be output in various forms (e.g., text, voice, image, video, and haptic forms) through input / output unit 140c.

[0477] Figure 40 The diagram illustrates the communication system 1 used in this specification.

[0478] refer to Figure 40The communication system 1 used in this specification includes wireless devices, base stations (BS), and networks. Here, a wireless device refers to a device that performs communication using radio access technology (RAT) (e.g., 5G New RAT (NR) or Long Term Evolution (LTE)) and may be referred to as a communication / radio / 5G device. Wireless devices may include, but are not limited to, robots 100a, vehicles 100b-1 and 100b-2, extended reality (XR) devices 100c, handheld devices 100d, home appliances 100e, Internet of Things (IoT) devices 100f, and artificial intelligence (AI) devices / servers 400. For example, vehicles may include vehicles with wireless communication capabilities, autonomous vehicles, and vehicles capable of performing communication between vehicles. Here, vehicles may include unmanned aerial vehicles (UAVs) (e.g., drones). XR devices may include augmented reality (AR) / virtual reality (VR) / mixed reality (MR) devices and may be implemented in the form of head-mounted displays (HMDs), head-up displays (HUDs) installed in vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signage, vehicles, robots, etc. Handheld devices may include smartphones, smart tablets, wearable devices (e.g., smartwatches or smart glasses), and computers (e.g., laptops). Home appliances may include televisions, refrigerators, and washing machines. IoT devices may include sensors and smart meters. For example, the BS and network can be implemented as wireless devices, and a particular wireless device 200a can operate as a BS / network node relative to other wireless devices.

[0479] Wireless devices 100a to 100f can connect to network 300 via BS 200. AI technology can be applied to wireless devices 100a to 100f, and wireless devices 100a to 100f can connect to AI server 400 via network 300. Network 300 can be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. Although wireless devices 100a to 100f can communicate with each other via BS 200 / network 300, wireless devices 100a to 100f can also perform direct communication with each other without going through the BS / network (e.g., sidelink communication). For example, vehicles 100b-1 and 100b-2 can perform direct communication (e.g., vehicle-to-vehicle (V2V) / vehicle-to-everything (V2X) communication). In addition, IoT devices (e.g., sensors) can perform direct communication with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.

[0480] Wireless communication / connections 150a, 150b, or 150c can be established between wireless devices 100a to 100f / BS 200 or between BS 200 and BS 200. In this document, wireless communication / connections can be established via various RATs (e.g., 5G NR), such as uplink / downlink communication 150a, sidelink communication 150b (or D2D communication), or inter-BS communication (e.g., relay, Integrated Access Backhaul (IAB)). Wireless devices and BS / wireless devices can transmit / receive radio signals to / from each other via wireless communication / connections 150a and 150b. For example, wireless communication / connections 150a and 150b can transmit / receive signals via various physical channels. To this end, at least a portion of various configuration information configuration processes, various signal processing processes (e.g., channel coding / decoding, modulation / demodulation, and resource mapping / demapping), and resource allocation processes for transmitting / receiving radio signals can be performed based on various proposals of this disclosure.

[0481] Meanwhile, NR supports multiple parameter sets (or multiple subcarrier spacing (SCS) ranges) to support a variety of 5G services. For example, when the SCS is 15kHz, it supports wide-area coverage of traditional cellular bands; when the SCS is 30kHz / 60kHz, it supports dense urban areas, low latency, and wider carrier bandwidth; when the SCS is 60kHz or higher, it supports bandwidths greater than 24.25GHz to overcome phase noise.

[0482] NR bands can be defined as frequency ranges of two types (FR1 and FR2). The values ​​of the frequency ranges can be changed. For example, the frequency ranges of the two types (FR1 and FR2) can be as shown in Table 7. For ease of description, FR1 for the frequency range used in NR systems can refer to "the range below 6 GHz", and FR2 can refer to "the range above 6 GHz" and can be referred to as millimeter wave (mmW).

[0483] [Table 7]

[0484] Frequency range specification Corresponding frequency range Subcarrier spacing FR1 450MHz–6000MHz 15, 30, 60kHz FR2 24250MHz–52600MHz 60, 120, 240kHz

[0485] As mentioned above, the frequency range of the NR system can be changed. For example, FR1 can include a band from 410MHz to 7125MHz, as shown in Table 8. That is, FR1 can include a frequency band of 6GHz (or 5850, 5900, 5925MHz, etc.) or larger. For example, the 6GHz (or 5850, 5900, 5925MHz, etc.) or larger frequency band included in FR1 can include unlicensed bands. Unlicensed bands can be used for various purposes, such as for vehicle communications (e.g., autonomous driving).

[0486] [Table 8]

[0487]

[0488] Figure 41 The illustrations are applicable to the vehicles or autonomous vehicles described in this manual. Vehicles or autonomous vehicles can be mobile robots, cars, trains, manned / unmanned aerial vehicles (AVs), ships, etc.

[0489] refer to Figure 41 The vehicle or autonomous vehicle 100 may include an antenna unit 108, a communication unit 110, a control unit 120, a drive unit 140a, a power supply unit 140b, a sensor unit 140c, and an autonomous driving unit 140d. The antenna unit 108 may be configured as part of the communication unit 110. Blocks 110 / 130 / 140a to 140d correspond to... Figure 41 Blocks 110 / 130 / 140.

[0490] Communication unit 110 can send and receive signals (e.g., data, control signals, etc.) to and from various vehicles, base stations (e.g., base stations, roadside units, etc.), and servers. Control unit 120 can control the components of the vehicle or autonomous vehicle 100 to perform various operations. Control unit 120 may include electronic control unit (ECU). Drive unit 140a enables the vehicle or autonomous vehicle 100 to move on the ground. Drive unit 140a may include an engine, electric motor, powertrain, wheels, brakes, steering mechanism, etc. Power supply unit 140b supplies power to the vehicle or autonomous vehicle 100 and may include wired / wireless charging circuitry, battery, etc. Sensor unit 140c can acquire vehicle status, environmental information, user information, etc. Sensor unit 140c may include inertial measurement unit (IMU) sensors, collision sensors, wheel sensors, speed sensors, tilt sensors, weight sensors, heading sensors, position modules, front / rear vision sensors, battery sensors, fuel sensors, tire sensors, steering sensors, temperature sensors, humidity sensors, ultrasonic sensors, illuminance sensors, pedal position sensors, etc. The autonomous driving unit 140d can implement technologies for maintaining the driving lane, technologies for automatically adjusting speed such as adaptive cruise control, technologies for autonomous driving along a set route, technologies for automatically setting a route and driving when the set destination is reached, etc.

[0491] For example, communication unit 110 can receive map data, traffic condition data, etc., from an external server. Autonomous driving unit 140d can generate autonomous driving routes and driving plans based on the acquired data. Control unit 120 can control drive unit 140a to move the vehicle or autonomous vehicle 100 along the autonomous driving route according to the driving plan (e.g., speed / direction control). During autonomous driving, communication unit 110 can periodically or intermittently obtain updated traffic condition data from an external server and can obtain surrounding traffic condition data from nearby vehicles. Furthermore, during autonomous driving, sensor unit 140c can acquire vehicle condition and environmental information. Autonomous driving unit 140d can update the autonomous driving route and driving plan based on newly acquired data / information. Communication unit 110 can transmit information about vehicle location, autonomous driving route, driving plan, etc., to an external server. The external server can use AI technology, etc., to predict traffic condition data in advance based on information collected from the vehicle or autonomous vehicle, and can provide the predicted traffic condition data to the vehicle or autonomous vehicle.

[0492] The claims disclosed in this specification can be combined in various ways. For example, the technical features in the method claims of this specification can be combined to implement or perform in an apparatus, and the technical features in the apparatus claims of this specification can be combined to implement or perform in a method. Furthermore, the technical features in the method claims and apparatus claims of this specification can be combined to implement or perform in an apparatus.

Claims

1. An operation method performed by an Integrated Access Backhaul (IAB) node, wherein the IAB node includes an IAB-Distributed Unit (DU) and an IAB-Mobile Terminal (MT), the method comprising: Connect the IAB-MT to the first parent node - DU cell of the first parent DU included in the primary cell group MCG; as well as The IAB-MT is connected to the second parent node - DU cell of the second parent DU included in the secondary cell group SCG; Each of the first parent DU and the second parent DU includes two DU cells. Wherein, the first parent node-DU cell is the victim DU cell and the second parent node-DU cell is the infringing DU cell. Specifically, the IAB-MT is connected to the first parent node-DU cell using a first MT-component carrier CC, and the IAB-MT is connected to the second parent node-DU cell using a second MT-CC. Wherein, based on i), the IAB-MT is scheduled to transmit and receive simultaneously in the same time resources of the first MT-CC and the second MT-CC, the IAB-MT performs DL reception in the MT-CC scheduled for downlink DL reception in the first MT-CC and the second MT-CC, and skips UL transmission in the MT-CC scheduled for uplink UL transmission in the first MT-CC and the second MT-CC.

2. An integrated access backhaul IAB node (100), the IAB node (100) comprising an IAB-Distributed Unit (DU) and an IAB-Mobile Terminal (MT), the IAB node comprising: At least one transceiver (106); At least one memory (104); as well as At least one processor (102), said at least one processor (102) being operatively coupled to said at least one memory (104) and said at least one transceiver (106), wherein said at least one memory (104) stores instructions that, based on execution by said at least one processor (102), cause said at least one processor (102) to perform operations including: The IAB-MT is connected to the first parent node of the first parent DU cell, which is included in the primary cell group (MCG); and The IAB-MT is connected to the second parent node - DU cell of the second parent DU included in the secondary cell group SCG; Each of the first parent DU and the second parent DU includes two DU cells. Wherein, the first parent node-DU cell is the victim DU cell and the second parent node-DU cell is the infringing DU cell. Specifically, the IAB-MT is connected to the first parent node-DU cell using a first MT-component carrier CC, and the IAB-MT is connected to the second parent node-DU cell using a second MT-CC. Wherein, based on i), the IAB-MT is scheduled to transmit and receive simultaneously in the same time resources of the first MT-CC and the second MT-CC, the IAB-MT performs DL reception in the MT-CC scheduled for downlink DL reception in the first MT-CC and the second MT-CC, and skips UL transmission in the MT-CC scheduled for uplink UL transmission in the first MT-CC and the second MT-CC.

3. An apparatus for integrating an access backhaul IAB node (100), the IAB node (100) comprising an IAB-Distributed Unit (DU) and an IAB-Mobile Terminal (MT), the apparatus comprising: At least one memory (104); as well as At least one processor (102), said at least one processor being operatively coupled to said at least one memory (104), The at least one memory (104) stores instructions, which, based on execution by the at least one processor (102), cause the at least one processor (102) to perform operations including: The IAB-MT is connected to the first parent node of the first parent DU cell, which is included in the primary cell group (MCG); and The IAB-MT is connected to the second parent node - DU cell of the second parent DU included in the secondary cell group SCG. Each of the first parent DU and the second parent DU includes two DU cells. Wherein, the first parent node-DU cell is the victim DU cell and the second parent node-DU cell is the infringing DU cell. Specifically, the IAB-MT is connected to the first parent node-DU cell using a first MT-component carrier CC, and the IAB-MT is connected to the second parent node-DU cell using a second MT-CC. Wherein, based on i), the IAB-MT is scheduled to transmit and receive simultaneously in the same time resources of the first MT-CC and the second MT-CC, the IAB-MT performs DL reception in the MT-CC scheduled for downlink DL reception in the first MT-CC and the second MT-CC, and skips UL transmission in the MT-CC scheduled for uplink UL transmission in the first MT-CC and the second MT-CC.

Images