Method and apparatus for transmitting or receiving data with dual connectivity of iab node in wireless communication system

Abstract

The disclosure provides a method of transmitting and receiving data in a wireless communication system, performed by an integrated access and backhaul (IAB) node. The method can include receiving resource allocation information from an IAB donor node, receiving first resource scheduling information from a first parent IAB node, receiving second resource scheduling information from a second parent IAB node, transmitting data to and receiving data from at least one of the first parent IAB node, the second parent IAB node, a child IAB node, or a user equipment (UE) based on the resource allocation information, the first resource scheduling information, and the second resource scheduling information.

Description

[0001] This application is a divisional application. The parent application is an invention patent application that entered the national phase of the PCT patent application with international application number PCT / KR2021 / 006866, and the Chinese patent application number of the parent application is 202180039471.1. Technical Field

[0002] This disclosure relates to wireless communication systems, and more specifically, to methods and apparatus for transmitting and receiving data using dual connectivity of integrated access and backhaul (IAB) nodes. Background Technology

[0003] To meet the growing demand for wireless data services following the commercialization of fourth-generation (4G) communication systems, efforts have been made to develop fifth-generation (5G) or pre-5G communication systems. For this purpose, 5G or pre-5G communication systems are referred to as "beyond 4G network" communication systems or "post-Long Term Evolution (post-LTE)" systems.

[0004] To achieve high data rates, 5G communication systems are being considered for implementation in ultra-high frequency millimeter-wave (mmwave) bands (e.g., the 60 GHz band). To reduce path loss of radio waves and increase transmission distance in the ultra-high frequency band of 5G communication systems, various technologies are being investigated, such as beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive MIMO.

[0005] To improve the system network used in 5G communication systems, various technologies have been developed, such as evolved small cells, advanced small cells, cloud radio access networks (Cloud-RAN), ultra-dense networks, device-to-device communication (D2D), wireless backhaul, mobile networks, cooperative communication, cooperative multipoint (CoMP), and receive interference cancellation.

[0006] In addition, advanced coding and modulation (ACM) technologies, such as hybrid frequency shift keying (FSK), quadrature amplitude modulation (QAM) (FQAM), and sliding window superposition coding (SWSC), have been developed for 5G communication systems, as well as advanced access technologies, such as filter bank multicarrier (FBMC), non-orthogonal multiple access (NOMA), and sparse coded multiple access (SCMA).

[0007] The Internet has evolved from a human-based network of connections where humans create and consume information to the Internet of Things (IoT), where distributed elements, such as objects, exchange information with each other to process it. Internet of Everything (IoE) technology has emerged, where IoT technology is combined with technologies such as those used to process big data via connections to cloud servers. To realize IoT, various technological elements are required, such as sensing technology, wired / wireless communication and network infrastructure, service interface technology, and security technology. This has led to research in recent years on technologies related to sensor networks, machine-to-machine (M2M) communication, and machine-type communication (MTC) for connecting objects. In the IoT environment, intelligent Internet technology (IT) services can be provided to collect and analyze data obtained from connected objects, thereby creating new value in human life. Due to the existing convergence and integration of information technology (IT) with various industries, IT can be applied to a wide range of fields, such as smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, healthcare, smart appliances, and advanced medical services.

[0008] Various attempts are underway to apply 5G communication systems to IoT networks. For example, 5G communication technologies with beamforming, MIMO, and array antennas are being used to implement technologies related to sensor networks, M2M communication, and MTC. Cloud Radio Access Network (Cloud-RAN), as an application of the aforementioned big data processing technologies, can be seen as an example of the convergence of 5G communication and IoT technologies.

[0009] Recently, various studies have been conducted to utilize Integrated Access and Backhaul (IAB), thus requiring enhanced communication services in dual-connectivity environments with IAB nodes. Summary of the Invention

[0010] Technical solution

[0011] This disclosure provides a method and apparatus for effectively providing services in a mobile communication system.

[0012] More specifically, when an Integrated Access and Backhaul (IAB) communication system is in operation, where an IAB node is configured for dual connectivity with multiple parent IAB nodes at a higher level, data transmission and reception between the distributed unit (DU) of the parent IAB node and the mobile terminal (MT) of the IAB node, as well as data transmission and reception between the DU of the IAB node and the MT or access UE of the child IAB at a lower level of the IAB node, are mixed, making it difficult to satisfy the half-duplex constraint instantaneously. This disclosure provides various methods for communication while satisfying the half-duplex constraint.

[0013] Beneficial effects

[0014] According to embodiments of this disclosure, an apparatus and method for effectively providing services in a wireless communication system are provided. Attached Figure Description

[0015] Figure 1 A communication system for operating integrated access and backhaul (IAB) nodes according to an embodiment of the present disclosure is shown.

[0016] Figure 2 This is a schematic diagram illustrating each multiplexing of the access link and backhaul link in the time or frequency domain at an IAB node according to an embodiment of the present disclosure.

[0017] Figure 3 This is a diagram illustrating the multiplexing of access links and backhaul links in the time domain in an IAB communication system according to an embodiment of the present disclosure.

[0018] Figure 4 This is a diagram illustrating the multiplexing of access links and backhaul links in the frequency and spatial domains of an IAB communication system according to an embodiment of the present disclosure.

[0019] Figure 5 This is a diagram schematically illustrating the architecture of an IAB node according to an embodiment of the present disclosure.

[0020] Figure 6 This is a diagram illustrating a communication system according to an embodiment of the present disclosure.

[0021] Figure 7 This is a diagram schematically illustrating a dual-connection structure of an IAB node according to an embodiment of the present disclosure.

[0022] Figure 8 This is a diagram schematically illustrating a dual-connection structure of an IAB node according to an embodiment of the present disclosure.

[0023] Figure 9 This is a schematic diagram illustrating the environment that may occur in a dual-connection structure of an IAB node according to an embodiment of the present disclosure, based on real-time coordination.

[0024] Figure 10 This is a flowchart illustrating a method for sending and receiving data performed by an IAB node, according to embodiments of the present disclosure.

[0025] Figure 11 This is a diagram illustrating a UE device according to an embodiment of the present disclosure.

[0026] Figure 12 This is a diagram illustrating a BS device according to an embodiment of the present disclosure.

[0027] Figure 13 This is a diagram illustrating an IAB node according to an embodiment of the present disclosure. Detailed Implementation

[0028] Best mode

[0029] According to embodiments of this disclosure, a method for transmitting and receiving data in a wireless communication system, performed by an Integrated Access and Backhaul (IAB) node, may include: receiving resource allocation information from an IAB donor node; receiving first resource scheduling information from a first parent IAB node; receiving second resource scheduling information from a second parent IAB node; transmitting data to at least one of the first parent IAB node, the second parent IAB node, the child IAB node, or the user equipment (UE) based on the resource allocation information, the first resource scheduling information, and the second resource scheduling information; and receiving data from at least one of the first parent IAB node, the second parent IAB node, the child IAB node, or the user equipment (UE).

[0030] Invention Model

[0031] In the following, exemplary embodiments of the present disclosure will now be described more fully with reference to the accompanying drawings. It should be noted that the same reference numerals denote the same parts in the drawings. Furthermore, detailed descriptions of well-known functions and configurations that may obscure the present disclosure are not provided.

[0032] In the following description of the embodiments, descriptions of techniques well-known in the art and not directly related to the present disclosure are omitted. By omitting unnecessary descriptions, the essence of the present disclosure is conveyed clearly without obscuring it.

[0033] For the same reason, some components in the accompanying drawings are exaggerated, omitted, or shown schematically. Furthermore, the dimensions of each component do not precisely correspond to their actual dimensions. In each drawing, the same or corresponding components are presented with the same reference numerals.

[0034] The advantages and features of this disclosure, as well as methods of implementing it, can be more readily understood by referring to the following detailed description and accompanying drawings of embodiments of this disclosure. However, this disclosure may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concepts of this disclosure to those skilled in the art. Therefore, the scope of this disclosure is defined by the appended claims. Throughout this specification, the same reference numerals denote the same parts.

[0035] It should be understood that each block of a flowchart, and combinations of blocks within a flowchart, can be implemented by computer program instructions. Computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus, such that the instructions, which execute via the processor, generate means for performing the functions specified in the flowchart blocks. The computer program instructions can also be stored in a computer-executable or computer-readable storage medium that can direct the computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the computer-executable or computer-readable storage medium can produce an article of art including instruction means for performing the functions specified in the flowchart blocks. The computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus, thereby producing a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide operations for implementing the functions specified in the flowchart blocks.

[0036] Furthermore, each box in the flowchart can represent a module, fragment, or section of code, which includes one or more executable instructions for performing a specified logical function. It should also be noted that in some alternative implementations, the functions recorded in the boxes may occur out of order. For example, two boxes shown consecutively may actually execute substantially simultaneously, or these boxes may sometimes execute in reverse order, depending on the functions involved.

[0037] The term "...unit" as used in this embodiment refers to a software or hardware component that performs certain tasks, such as a field-programmable gate array (FPGA) or an application-specific integrated circuit (ASIC). However, the term "...unit" is not intended to be limited to software or hardware. "...unit" may be configured to reside in addressable storage media or to operate one or more processors. Therefore, "...unit" may include, for example, components such as software components, object-oriented software components, class components, and task components, processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functionality provided in components and "...units" may be combined into fewer components and "...units" or further separated into additional components and "...units". Furthermore, components and "...units" may be implemented as one or more central processing units (CPUs) in an operating device or a secure multimedia card.

[0038] In the following description, for ease of description, terms identifying access nodes, network entities, messages, interfaces between network entities, and various types of identification information are exemplified. Therefore, this disclosure is not limited to the terms described below, and other terms indicating objects with the same technical meaning may be used.

[0039] In the following text, a base station is an entity that allocates resources to terminals and can be at least one of a next-generation Node B (gNB), an evolved Node B (eNB), a Node B, a base station (BS), a radio access unit, a BS controller, or a node on a network. A terminal can include a user equipment (UE), a mobile station (MS), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing communication functions. Furthermore, the term "terminal (UE)" refers not only to mobile phones, NB-IoT devices, and sensors, but also to other wireless communication devices. Clearly, the BS and terminal are not limited to the examples provided.

[0040] For ease of description, the terms and names defined in the 3GPP LTE standard are used in this disclosure. However, this disclosure is not limited to these terms and names and can be applied equivalently to systems conforming to other standards.

[0041] Based on communication standards such as High-Speed ​​Packet Access (HSPA), Long Term Evolution (LTE) or Evolved Universal Terrestrial Radio Access (E-UTRA), LTE Advanced (LTE-A), 3GPP's LTE-Pro, High-Rate Packet Data (HRPD), 3GPP2's Ultra Mobile Broadband (UMB), and IEEE's 802.16e, wireless communication systems that initially provided voice-based services are being developed into broadband wireless communication systems that provide high-speed and high-quality packet data services.

[0042] As a representative example of a broadband wireless communication system, the LTE system employs Orthogonal Frequency Division Multiplexing (OFDM) for the downlink (DL) and Single-Carrier Frequency Division Multiple Access (SC-FDMA) for the uplink (UL). UL refers to the radio link used to transmit data or control signals from a terminal (e.g., UE or MS) to a base station (e.g., eNB or BS), and DL refers to the radio link used to transmit data or control signals from the base station to the terminal. These various access schemes identify each user's data or control information in such a way that the time-frequency resources used to carry each user's data or control information are allocated and managed to ensure they do not overlap, i.e., to achieve orthogonality.

[0043] As a post-LTE communication system, i.e., a 5G (or New Radio (NR)) communication system, it needs to support services that can freely reflect and simultaneously meet the diverse needs of users, service providers, and others. Services considered for 5G systems include enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low latency communications (URLLC) services.

[0044] eMBB aims to provide higher data rates than those supported by traditional LTE, LTE-A, or LTE-Pro. For example, in a 5G communication system, eMBB should be able to provide a peak data rate of 20Gbps in DL at a BS and 10Gbps in UL. Furthermore, 5G communication systems must simultaneously provide both the UE's peak data rate and the increased user-aware data rate. To meet this requirement, improved transmit / receive technologies, including improved multiple-input multiple-output (MIMO) transmission techniques, are needed. Moreover, the data rates required in 5G communication systems can be met by using a frequency bandwidth wider than 20MHz in the 3GHz to 6GHz or 6GHz or more bands, rather than by using a maximum of 20MHz to transmit signals in the 2GHz band as in LTE.

[0045] Furthermore, mMTC is considered to support application services such as IoT in 5G communication systems. To effectively deliver IoT, mMTC may need to support a large number of terminals in a cell, improve terminal coverage, improve battery life, and reduce terminal costs. Because IoT connects to various sensors and devices to provide communication functions, mMTC should be able to support a large number of terminals in a cell (e.g., 1,000,000 terminals / km). 2 Furthermore, because mMTC-enabled terminals may be located in shadow areas not covered by the cell (e.g., a building's basement), they may require wider coverage than other services provided by 5G communication systems due to the nature of the service. mMTC-enabled terminals should be configured as low-cost devices and may require a very long battery life of 10 to 15 years, as frequent battery replacements are difficult.

[0046] Finally, URLLC refers to cellular-based wireless communication services used for mission-critical purposes. Examples include services for remotely controlled robots or machines, industrial automation, drones, remote healthcare, and emergency alerts. Therefore, URLLC should provide communication with very low latency and very high reliability. For example, services supporting URLLC should have an air interface latency of less than 0.5 milliseconds and a packet error rate of 10-1. -5Or even smaller. Therefore, for services that support URLLC, 5G systems should provide shorter transmission time intervals (TTIs) than other services, and can also be designed to allocate wide resources in the frequency band to ensure the reliability of the communication link.

[0047] The three 5G services—eMBB, URLLC, and mMTC—can be multiplexed and transmitted within a single system. Here, to meet different service requirements, services can use different transmit / receive schemes and parameters.

[0048] Although LTE, LTE-A, LTE Pro, or 5G (or NR, next-generation mobile communications) systems are mentioned as examples in the following description, embodiments of this disclosure can also be applied to other communication systems with similar technical backgrounds or channel types. Furthermore, embodiments of this disclosure can be applied to other communication systems with partial modifications, based on the determination of those skilled in the art, without significantly departing from the scope of this disclosure. In 5G, when a BS transmits or receives data from a UE in a frequency band equal to or greater than 6 GHz, particularly in the millimeter wave (millimeter wave) band, coverage may be limited due to propagation path attenuation. Coverage limitations can be addressed by densely arranging multiple relays (or relay nodes) in the propagation path between the BS and the UE; however, the significant cost of installing optical cables to connect the backhaul between the relays can be a problem. Therefore, instead of installing optical cables between relays, broadband radio frequency resources available for millimeter waves can be used to transmit or receive backhaul data between relays, thus solving the cost problem of installing optical cables and making more efficient use of the millimeter wave band.

[0049] The technology of using millimeter waves to send or receive backhaul data from the BS and ultimately to send or receive access data to the UE via multiple relays as described above is called Integrated Access and Backhaul (IAB). In this context, the relay nodes that send or receive data to the BS using wireless backhaul are called IAB nodes. Here, the BS includes a Central Unit (CU) and Distributed Units (DUs), and the IAB node includes DUs and Mobile Terminals (MTs). The CU can control the DUs connected to all IAB nodes via multi-hop connections to the BS.

[0050] IAB nodes can use different frequency bands or the same frequency band to receive backhaul data from the BS and send access data to the UE, and to receive access data from the UE and send backhaul data to the BS. When using the same frequency band, the IAB node is momentarily constrained by half-duplex. Therefore, as a method to reduce the transmission and reception latency caused by the half-duplex constraint of the IAB node, the IAB node can perform frequency division multiplexing (FDM) and / or space division multiplexing (SDM) on the backhaul data (downlink (DL) data from the parent IAB node's DU to the IAB node's MT and uplink (UL) data from the child IAB node's MT to the IAB node's DU) and access data from the UE (UL data from the UE to the IAB node) during reception.

[0051] Furthermore, the IAB node used for transmission can perform FDM and / or SDM on backhaul data (UL data from the MT of the IAB node to the DU of the parent IAB node and DL data from the DU of the IAB node to the MT of the child IAB node) and access data to the UE (DL data from the IAB node to the UE). Here, when an IAB node is configured to be dual-connected to multiple parent IAB nodes at a higher layer, data transmission and reception between the DU of the parent IAB node and the MT of the IAB node, as well as data transmission and reception between the DU of the IAB node and the MT of the child IAB at a lower layer or between the IAB node and the access UE, are mixed, making it difficult to instantaneously meet the half-duplex constraint. This disclosure provides a method by which an IAB node can operate in an environment where data transmission and reception are mixed to meet the half-duplex constraint. Embodiments of this disclosure will now be described with reference to the accompanying drawings.

[0052] Figure 1 A communication system for operating an IAB node according to an embodiment of the present disclosure is shown.

[0053] exist Figure 1In this disclosure, gNB 101 is a public BS (e.g., an eNB or gNB), and gNB 101 is referred to as gNB, eNB, BS, donor BS, or donor IAB. IAB node #1 111 and IAB node #2 121 are IAB nodes used to perform backhaul link transmission and reception in the millimeter-wave band. UE 1 102 transmits access data to and receives access data from gNB 101 via access link 103. IAB node #1 111 transmits backhaul data to and receives backhaul data from gNB 101 via backhaul link 104. UE 2 112 transmits access data to and receives access data from IAB node #1 111 via access link 113. IAB node #2 121 sends backhaul data to IAB node #1 111 via backhaul link 114 and receives backhaul data from IAB node #1 111. Therefore, IAB node #1 111 is a higher-level IAB node than IAB node #2 121 and is referred to as the parent IAB node, and IAB node #2 121 is a lower-level IAB node than IAB node #1 111 and is referred to as the child IAB node. UE 3 122 sends access data to IAB node #2 121 via access link 123 and receives access data from IAB node #2 121.

[0054] The measurements performed by the UE on the IAB node or donor gNB will now be described.

[0055] UE 2 112 or UE 3 122 may require coordination between the donor gNB and the IAB node to perform measurements on neighboring donor gNBs or neighboring donor IAB nodes that are not serving IAB nodes. That is, the donor gNB can match measurement resources for IAB nodes with an even-numbered hop order or for IAB nodes with an odd-numbered hop order, thereby minimizing resource waste when the UE performs measurements on neighboring IAB nodes or IAB BSs. The UE can receive higher-layer signals from the serving IAB node or BS for configuring the Synchronization Signal Block (SSB) / Physical Broadcast Channel (PBCH) or for measuring neighboring IAB nodes using Channel State Information Reference Signals (CSI-RS). When the UE is configured to perform measurements on neighboring BSs via SSB / PBCH, the UE can be configured to have at least two SSB / PBCH Measurement Timing Configurations (SMTCs) for each frequency of measurement resources for IAB nodes with an even-numbered hop order or for each frequency of measurement resources for IAB nodes with an odd-numbered hop order. Upon receiving this configuration, the UE can perform measurements on IAB nodes with an even-numbered hop order in one SMTC and on IAB nodes with an odd-numbered hop order in another SMTC.

[0056] Next, the measurements of the IAB node performed by another IAB node or the donor gNB will be described.

[0057] Coordination between the donor gNB and the IAB node may be necessary for an IAB node to perform measurements on another neighboring donor gNB or another neighboring IAB node. That is, the donor gNB can be matched with measurement resources for IAB nodes with an even-numbered hop order, or with measurement resources for IAB nodes with an odd-numbered hop order, thereby minimizing the waste of resources for an IAB node to perform measurements on neighboring IAB nodes or IAB BSs. An IAB node can receive higher-layer signals for the configuration of the SSB / PBCH for measuring neighboring IAB nodes from the serving IAB node or BS, or CSI-RS for measuring neighboring IAB nodes. When an IAB node is configured to perform measurements on a neighboring BS via the SSB / PBCH, the IAB node can be configured to have at least two SMTCs per frequency for the measurement resources of IAB nodes with an even-numbered hop order, or at least two SMTCs for the measurement resources of IAB nodes with an odd-numbered hop order. After receiving the configuration, an IAB node can perform measurements on IAB nodes with an even-numbered hop order in one SMTC and on IAB nodes with an odd-numbered hop order in another SMTC.

[0058] In the IAB technology proposed in this disclosure, reference will now be made to Figure 2 , Figure 3 and Figure 4 Describe in detail the multiplexing of backhaul links between BS and IAB nodes or between IAB nodes and access links between BS and UE or between IAB nodes and UE in radio resources.

[0059] Figure 2 This is a schematic diagram illustrating the multiplexing of access links and backhaul links at an IAB node according to an embodiment of this disclosure. Figure 2 The upper part shows the time-domain multiplexing of the access link and backhaul link at the IAB node. Figure 2 The lower part shows the frequency domain multiplexing of the access link and backhaul link at the IAB node.

[0060] exist Figure 2In the radio resource 201 shown above, the backhaul link 203 between the access links 202 between the gNB and the IAB node, or between the IAB node and the UE, is time-domain multiplexed (TDM). Therefore, in the time domain where the gNB or IAB node sends data to and receives data from the UE, data transmission and reception between the gNB and the IAB node are not performed, and in the time domain where data transmission and reception between the gNB and the IAB node are performed, the gNB or IAB node does not send data to or receive data from the UE.

[0061] Next, in Figure 2 In the radio resource 211 shown below, the backhaul link 213 between the gNB and IAB nodes or between IAB nodes, and the access link 212 between the gNB and the UE or between the IAB node and the UE, are FDMed. Therefore, in the time domain where the gNB or IAB node sends data to and receives data from the UE, it is possible to send and receive data between the gNB and the IAB node; however, due to the half-duplex constraint of the IAB node, only unidirectional data transmission is possible. That is, in the time domain where the IAB node receives data from the UE, the IAB node can receive backhaul data only from another IAB node or gNB. Furthermore, in the time domain where the IAB node sends data to the UE, the IAB node can only send backhaul data to another IAB node or gNB.

[0062] Despite the combination Figure 2 Only TDM and FDM are described, but spatial domain multiplexing (SMD) of access and backhaul links in the spatial domain is also possible. Therefore, access and backhaul links can be transmitted and received simultaneously via SDM. However, even with SDM, data transmission in the same direction is only possible under the half-duplex constraint of the IAB node, as... Figure 2 The lower part utilizes FDM. That is, in the time domain where the IAB node receives data from the UE, the IAB node can receive backhaul data only from another IAB node or gNB. Furthermore, in the time domain where the IAB node transmits data to the UE, the IAB node can only transmit backhaul data to another IAB node or gNB.

[0063] When an IAB node performs initial access to a gNB or higher-level IAB node, it sends the capability for multiplexing schemes to the gNB or higher-level IAB node via the IAB node, and then receives configuration information from the gNB or higher-level IAB node via system information or radio resource control (RRC) signals, or receives configuration information from the gNB or higher-level IAB node via the backhaul link after initial access. It can configure the use of multiplexing schemes such as TDM, FDM and SDM.

[0064] Figure 3This is a diagram illustrating the multiplexing of access links and backhaul links in the time domain in an IAB communication system according to an embodiment of the present disclosure.

[0065] exist Figure 3 The upper part illustrates the communication process between IAB node 302 and its parent node 301, child IAB node 303, and UE 304. The links between the nodes are explained in more detail, with parent node 301 on the backhaul DL link L. P，DL (311) sends a backhaul DL signal to IAB node 302, and IAB node 302 sends a backhaul UL link L P，UL (312) Sends a return UL signal to parent node 301. IAB node 302 accesses DL link L A，DL (316) sends an access DL signal to UE 304, and UE 304 accesses the UL link L. A，UL (315) Sends an access UL signal to IAB node 302. IAB node 302 sends an access UL signal to the backhaul DL link L. C，DL The IAB sub-node 303 sends a backhaul DL signal (313), and the IAB sub-node 303 on the backhaul UL link L C，UL The middle node sends a backhaul UL signal (314) to IAB node 302. In the above symbols, P refers to the backhaul link to the parent node, A refers to the access link to the UE, and C refers to the backhaul link to the child node.

[0066] These link relationships are described relative to IAB node 302, and from the perspective of IAB child node 303, the parent node is IAB node 302, and IAB child node 303 may have another IAB child node at a lower level. Furthermore, from the perspective of parent node 301, the child node is IAB node 302, and parent node 301 may have another IAB parent node at a higher level.

[0067] The aforementioned signals include data and control information, channels for transmitting data and control information, reference signals required for decoding data and control information, or reference signals used for calculating channel information.

[0068] exist Figure 3 The lower part illustrates the process for multiplexing all links in the time domain. In the accompanying figures, the backhaul DL links are arranged in chronological order. P，DL 311. Backhaul DL link L C，DL 313. Access DL link L A，DL 316. Access UL Link L A，UL 315. Backhaul UL Link L C，UL 314 and backhaul UL link L P，UL312 is reused. The order of links provided in the attached diagram is an example, but any order can be applied equivalently.

[0069] The links are multiplexed sequentially in the time domain. Therefore, it is obvious that the multiplexing scheme requires the longest time to send signals from the parent node 301 to the child IAB node, and even to the UE, via IAB node 302. Therefore, in order to reduce the time delay of finally sending signals from the parent node 301 to the UE, a method of simultaneously multiplexing the backhaul link or the backhaul link and the access link in the frequency domain or spatial domain and sending the results simultaneously can be considered.

[0070] Figure 4 This is a diagram illustrating the multiplexing of access links and backhaul links in the frequency and spatial domains of an IAB communication system according to an embodiment of the present disclosure.

[0071] refer to Figure 4 The following will describe a method for reducing time latency by multiplexing backhaul links or backhaul and access links in the frequency or spatial domain.

[0072] First, similar to Figure 3 ,exist Figure 4 The upper part illustrates the communication process between IAB node 402 and its parent node 401, child IAB node 403, and UE 404. The links between the nodes are explained in more detail, with parent node 401 on the backhaul DL link L. P，DL (411) sends a backhaul DL signal to IAB node 402, and IAB node 402 sends a backhaul UL link L P，UL (412) Sends a return UL signal to parent node 401. IAB node 402 accesses DL link L A，DL (416) sends an access DL signal to UE 404, and UE 404 accesses the UL link L. A，UL (415) Sends an access UL signal to IAB node 402. IAB node 402 sends an access UL signal to the backhaul DL link L. C，DL (413) sends a backhaul DL signal to the child IAB node 403, and the IAB child node 403 sends a backhaul UL link L C，UL (414) sends a backhaul UL signal to IAB node 402. In the above symbols, P refers to the backhaul link to the parent node, A refers to the access link to the UE, and C refers to the backhaul link to the child node.

[0073] These link relationships are described relative to IAB node 402, and from the perspective of IAB child node 403, the parent node is IAB node 402, and IAB child node 403 may have another IAB child node at a lower level. Furthermore, from the perspective of parent node 401, the child node is IAB node 402, and parent node 401 may have another IAB parent node at a higher level.

[0074] The aforementioned signals include data and control information, channels for transmitting data and control information, reference signals required for decoding data and control information, or reference signals used for calculating channel information.

[0075] Next, in Figure 4 The lower part shows a scheme for multiplexing the above links in the frequency domain or spatial domain.

[0076] As mentioned above, IAB nodes are subject to half-duplex constraints instantaneously, thus limiting the signals that can be multiplexed in the frequency or spatial domains. For example, considering the half-duplex constraint of IAB node 402, the link that can be multiplexed in the time domain for transmissions that can be performed by the IAB node is the backhaul UL link L. P，UL 412. Backhaul DL link L C，DL 413. Access DL link L A，DL 416, etc. Therefore, when links are multiplexed in the frequency or spatial domain, IAB node 402 can transmit all links in the same time domain as in 421. Furthermore, the link that can be multiplexed in the time domain where IAB nodes can perform reception is the backhaul DL link L. P，DL 411, Backhaul UL Link L C，UL 414. Access UL Link L A，UL 415, etc. Therefore, when links are multiplexed in the frequency or spatial domain, IAB node 402 can receive all links in the same time domain as 422.

[0077] The link multiplexing shown in the attached figure is an example, and two of the three links multiplexed in the frequency or spatial domain can be multiplexed.

[0078] The structure of the IAB node will now be described.

[0079] For 5G, various forms of Base Station (BS) architectures have been studied, which are optimized for service requirements to support a wide range of services or a large number of machine-to-machine communication devices, such as massive transmission, low latency, and high reliability, while reducing capital expenditure (CAPEX) for installing the communication network. In 4G LTE, to reduce CAPEX and effectively handle interference control, the Cloud Radio Access Network (C-RAN) architecture has been commercialized. In this architecture, the data processor and radio transceiver (or Remote Radio Head (RRH)) in the BS are separated, with the data processor centrally located for processing and the radio transceivers located at the cell level. In the C-RAN architecture, when the BS data processor sends baseband digital IQ data to the radio transceiver, a common public radio interface (CPRI) standard optical link is typically used. Large data volumes are required when data is sent to the radio transceiver. For example, a transmission rate of 614.4 Mbps is needed to send 10 MHz of Internet Protocol (IP) data, and a transmission rate of 1.2 Gbps is needed to send 20 MHz of IP data. Therefore, 5G RAN architectures are designed by dividing the BS (gNB) into CU and DU to accommodate various structures, thereby reducing the heavy load on optical links, and functional splitting is applied to the CU and DU. 3GPP is standardizing many different functional splitting options for the CU and DU. Functional splitting options involve splitting inter-protocol layers or intra-protocol layers into functions, and there are a total of 8 options from Option 1 to Option 8, with Options 2 and 7 being considered first in the current 5G BS architecture. Option 2 has the RRC and Packet Data Convergence Protocol (PDCP) layers located in the CU and the Radio Link Control (RLC), Medium Access Control (MAC), Physical (PHY), and Radio Frequency (RF) layers located in the DU. Option 7 has RRC, PDCP, RLC, MAC, and higher PHY layers located in the CU, and lower PHY layers located in the DU. This functional splitting allows for flexible architectures that separate and migrate NR network protocols between the CU and DU. This architecture leads to flexible hardware implementation, provides cost-effective solutions, and the separation between CU and DU allows for load management and real-time performance optimization adjustments, enables Network Functions Virtualization (NFV) / Software-Defined Networking (SDN), and the configurable function splitting can have the advantage of being applicable to a variety of applications (variable latency in transmission).

[0080] Now refer to Figure 5 This describes the architecture of IAB nodes considering functional decomposition. Figure 5 This is a diagram schematically illustrating the architecture of an IAB node according to an embodiment of the present disclosure.

[0081] exist Figure 5In this architecture, gNB 501 includes CU and DU, and each IAB node includes MT and DU. MT is used to send data to and receive data from the parent node via the backhaul link, and DU is used to send data to and receive data from the child node via the backhaul link. Figure 5 In this configuration, IAB node #1 502 is wirelessly connected to gNB 501 via a single hop, and IAB node #2 503 is wirelessly connected to gNB 501 via IAB node #502 via two hops.

[0082] like Figure 5 As shown, the CU of gNB 501 controls not only the DU of gNB 501, but also all DUs wirelessly connected to gNB 501 (i.e., IAB node #1 502 and IAB node #2 503 (511 and 512)). The CU can allocate radio resources to the DUs, enabling the DUs to send and receive data from the MTs of the IAB nodes at lower layers of the DU. Radio resource allocation on the DUs can be performed using the F1 Application Protocol (F1AP) interface and by transmitting system information, higher-layer signals, or physical signals. Here, radio resources can be configured using DL time resources, UL time resources, flexible time resources, etc.

[0083] The configuration of radio resources will now be described in detail based on IAB Node #2 503. DL time resources are resources for the DU of IAB Node #2 503 to transmit DL control / data and signals to the MT of a lower-level IAB node (not shown). UL time resources are resources for the DU of IAB Node #2 503 to receive UL control / data and signals from the MT of a lower-level IAB node. Flexible time resources are resources that can be used by the DU of IAB Node #2 503 as either DL time resources or UL time resources, and how to use flexible time resources can be indicated to the MT of the lower-level IAB node via the DL control signal of the DU of IAB Node #2 503. Upon receiving a DL control signal, the MT determines whether the flexible time resource is for DL ​​time resources or UL time resources. When no DL control signal is received, the MT does not perform transmit or receive operations. That is, the MT does not monitor or decode the DL control channel on the resource or measure the signals on the resource. You can indicate two different types (or three different types, including time resources that are always unavailable) of time resources from the CU to the DU: DL time resources, UL time resources, and flexible time resources.

[0084] - The first type is the soft type, where the CU can use F1AP (the interface between the CU and DU) to configure the DU of IAB node #2 503 to utilize soft-type DL time resources, UL time resources, or flexible time resources. In this case, for the configured soft-type resource, the parent IAB node (or the DU of the parent IAB node) of IAB node #2 502 and IAB node #2 503 can explicitly (e.g., by using DCI format) or implicitly indicate to IAB node #2 503 and child IAB node (or the DU of the child IAB node) whether the resource is available. That is, when a specific resource is indicated to be available, the DU of IAB node #2 503 can use that resource to send and receive data to and from the MT of the lower IAB node. In other words, the DU of IAB node #2 503 can use the resource to perform transmission when the resource is a DL resource, or to perform reception when the resource is a UL resource. When a specific resource is indicated to be unavailable, IAB node #2 503 may not use that resource for sending and receiving data to and from lower IAB nodes' MTs. In other words, the DU of IA node #2 503 cannot use the resource for sending or receiving.

[0085] The method of indicating the availability of soft-type resources using a DCI format will now be described in more detail. The DCI format in the embodiments may include an availability indicator to indicate the availability of one or more consecutive UL, DL, or flexible symbols.

[0086] IAB node #2 503 can receive information in advance from the CU or parent IAB node (e.g., IAB node #1 502) regarding at least one of the following via higher-layer signals: the location of an availability indicator indicating the availability of IAB node #2 in DCI format; a table indicating the availability of time resources corresponding to multiple time slots; or a mapping between the availability indicator and the cell ID of the DU of IAB node #2 503, in order to receive DCI format. The value (or indicator) indicating the availability of consecutive UL symbols, DL symbols, or flexible symbols in a time slot, and the meaning of the value (or indicator), can be represented as shown in Table 1 below.

[0087] [Table 1]

[0088] When an availability indicator is indicated from the parent IAB node to IAB node #2 503 in DCI format and IAB node #2 503 receives the indicator, the following method can be considered as follows: through this method, the DU of IAB node #2 503 interprets the relationship between the DL, UL, or flexible time resources configured by the CU for the IAB DU and the availability.

[0089] The first method is one in which the IAB DU anticipates that the number of availability indicators included in the availability indicator in the DCI format corresponds to the number of soft-type time slots including consecutive symbols configured by the CU. According to this method, the IAB DU can determine that availability is applied only to time slots including soft types.

[0090] The second approach is that the number of availability indicators included in the availability indicator in the DCI format by the IAB DU corresponds to the number of all time slots configured by the CU, i.e., the number of all time slots with hard / soft / unavailable (NA) types. In this embodiment, the IAB DU can determine that availability is applied only to time slots with soft types, and availability is not applied to time slots with hard or NA types that do not have soft types.

[0091] In both the first and second methods, the IAB DU can be expected to indicate a value corresponding to a DL resource, UL resource, or flexible resource. For example, when only a DL soft resource or a DL hard resource exists in a time slot, the IAB DU can also be expected to indicate only the value 1 in Table 1 above. Therefore, values ​​in the table that indicate the availability of UL soft resources may not be expected.

[0092] Alternatively, the IAB DU can determine that, for a flexible resource configured at least by the CU, it can indicate whether a DL or UL resource is available, in addition to a value indicating the availability of the flexible resource. For example, for a flexible soft resource or a flexible hard resource, the DU of an IAB node can be expected to indicate a value of 1 or 2 instead of the value 4 in Table 1. In this case, the DU of IAB node #2 can determine whether the flexible resource can be used as a UL or DL ​​based on an indication from the parent IAB rather than the determination of IAB node #2 itself.

[0093] Alternatively, the IAB DU may anticipate a value of 0 in the table above even for any hard / soft or NA resource configured by the CU. In this case, the IAB DU determines that a hard / soft resource already configured by the CU is unavailable, and that resource is considered unavailable for the DU of IAB node #2, which transmits or receives data with the MT of a lower-level IAB node, as in the case of resource types that are always unavailable as configured by the CU, until indicated as available in a later DCI format. When the resource is again indicated as available by the DCI format, the DU of IAB node #2 can use the resource configured by the CU or received in the DCI format.

[0094] - The second type is hard type, and the resource is always available between DU and MT. That is, regardless of the transmit or receive operation of the MT of IA node #2503, the DU of IAB node #2503 can perform transmit when the resource is a DL time resource and can perform receive when the resource is a UL resource. When the resource is a flexible resource, the IAB DU can determine whether to perform transmit or receive (corresponding to the DCI format, which indicates to the MT of the lower IAB node whether the flexible resource is a DL resource or a UL resource).

[0095] - The third type is the type that is always unused or always unavailable, and the DU of IAB node #2 can send data to and receive data from the MT without using resources.

[0096] When the DU receives DL time resources, UL time resources, flexible time resources, or reserved time resources from the CU in a higher-layer signal, it receives all of the above types together.

[0097] Next, the DU of gNB 501 is a common BS, and the DU controls the MT of IAB node #1 502 for scheduling data transmission or reception (521). The DU of IAB #1 502 is a common BS, and the DU controls the MT of IAB node #2 503 for scheduling data transmission or reception (522).

[0098] The DU can indicate the radio resources for data transmission and reception to and from the MT of the lower IAB node based on the radio resources allocated from the CU. The configuration of radio resources can be sent to the MT via system information, higher-layer signals, or physical signals. Here, radio resources can be configured using DL time resources, UL time resources, flexible time resources, reserved time resources, etc. DL time resources are resources used by the DU to transmit DL control / data and signals to the MT of the lower IAB node. UL time resources are resources used by the DU to receive UL control / data and signals from the MT of the lower IAB node. Flexible time resources are resources that can be used by the DU as either DL or UL time resources, and how to use flexible time resources can be indicated to the MT of the lower IAB by the DU's DL control signal. Upon receiving a DL control signal, the MT determines whether the flexible time resource is used for DL ​​or UL time resources. When no DL control signal is received, the MT does not perform transmit or receive operations. That is, the MT does not monitor or decode the DL control channel on the resource or measure the signals on the resource.

[0099] The DL control signal, as a combination of higher-level signals and physical signals, is signaled to the MT, and the MT can determine the time slot format in a specific time slot by receiving this signal notification. The time slot format is essentially formed by starting with a DL symbol, having a flexible symbol in the middle, and ending with a UL symbol (i.e., a structure with DFU order). When using only the time slot format, the DU of an IAB node may be able to perform a DL transmission at the beginning of a time slot, but the MT of an IAB node configured by its parent IAB with the same time slot format (i.e., DFU structure) cannot simultaneously perform a UL transmission (corresponding to time slot format indices 0 to 55 in Table 2 below). Therefore, a time slot format formed by starting with a UL symbol, having flexible symbols in the middle and at the end of the DL symbol, can be defined in Table 2 below (corresponding to time slot format indices 56 to 96 in Table 2 below). The time slot formats defined in Table 2 below can be sent to the MT using the DL control signal and can be configured by the CU for the DU using F1AP.

[0100] [Table 2]

[0101] The reserved time resources are resources on which the DU cannot send data to or receive data from a lower-level MT, so the MT does not perform send or receive operations on the resource. In other words, the MT does not monitor or decode the DL control channel on the resource or measure the signals on the resource.

[0102] Therefore, the MT in an IAB node is controlled by the DU in a higher-level IAB node to receive scheduling for data transmission or reception, and the DU in the same IAB node is controlled by the CU of the gNB 501. In other words, the MT and DU in an IAB are controlled by different entities and therefore may not be coordinated in real time.

[0103] Next, Figure 6 This is a diagram illustrating a communication system according to an embodiment of the present disclosure. Although Figure 6 An example of a system configured by combining a BS using the new radio access technology and an LTE / LTE-A BS is shown, but systems configured by combining BS using the new radio access technology may also exist.

[0104] Reference Figure 6Smaller BSs 603, 605, and 607 with relatively small coverage areas 604, 606, and 608 can be deployed within the coverage area 602 of the macro BS 601. Typically, the macro BS 601 is capable of transmitting signals at a higher transmit power than the smaller BSs 603, 605, or 607, making the coverage area 602 of the macro BS 601 larger than the coverage areas 604, 606, or 608 of the smaller BSs 603, 605, or 607. Figure 6 In the examples, macro BS refers to an LTE / LTE-A system operating in a relatively lower frequency band, while small BS 603, 605, or 607 refers to a system that uses a new radio access technology (NR or 5G) operating in a relatively higher frequency band.

[0105] Macro BS 601 and small BSs 603, 605, and 607 can be interconnected, and a certain degree of return delay may exist depending on the connection status. Therefore, it may be undesirable to exchange information that is susceptible to transmission delays between macro BS 601 and small BSs 603, 605, or 607.

[0106] although Figure 6 The examples illustrate carrier aggregation between macro BS 601 and small BS 603, 605, or 607, but this disclosure is not limited thereto and can be equivalently applied to carrier aggregation between BSs located at different geological locations. For example, in some embodiments, it can be equivalently applied to carrier aggregation between macro BSs located at different locations or between small BSs located at different locations. Moreover, there is no limitation on the number of carriers. Alternatively, the invention can be applied to carrier aggregation in macro BS 601 and carrier aggregation in small BS 603, 605, or 607.

[0107] Reference Figure 6 Macro BS 601 can use frequency f1 for DL ​​signal transmission, while small BSs 603, 605, or 607 can use frequency f2 for DL ​​signal transmission. In this configuration, macro BS 601 can transmit data or control information to a specific UE 609 on frequency f1, and small BSs 603, 605, or 607 can transmit data or control information to UE 609 on frequency f2. Through the aforementioned carrier aggregation, BSs employing new radio access technologies supporting high-frequency to ultra-high-frequency bands can provide ultra-high-speed data services and ultra-low latency services. Furthermore, together with BSs, BSs employing LTE / LTE-A technology in relatively low-frequency bands can support reliable UE mobility.

[0108] Figure 6The configuration shown can be applied not only to DL carrier aggregation but also to UL carrier aggregation. For example, UE 609 can send data or control information to macro BS 601 at frequency f1' for UL signal transmission. Furthermore, UE 609 can send data or control information to small BSs 603, 605, or 607 at frequency f2' for UL signal transmission. f1' can correspond to f1, and f2' can correspond to f2. UL signal transmission from the UE to the macro and small BSs can be performed at different times or at one time. In either case, due to the physical constraints of the power amplifiers in the UE and the propagation constraints on the UE's output power, the total UL transmit power of the UE must remain equal to or less than a certain threshold within a random time period.

[0109] Through such Figure 6 In the environment shown, the operation of UE609, which connects to macro BS 601 and small BS 603, 605, or 607 to perform communication, is called dual connectivity (DC). When the UE performs dual connectivity, the following three configurations are possible.

[0110] According to the first configuration, after the UE performs initial access to the macro BS 601 operating as an LTE / LTE-A system, the UE receives configuration information for data transmission and reception of the macro BS 601 via a higher-layer signal (system or RRC signal). Then, the UE receives configuration information for data transmission and reception of the micro BS 603, 605, or 607 operating as an NR system via the higher-layer signal (system or RRC signal) of the macro BS 601, and the UE performs random access to the micro BS 603, 605, or 607, thus having a dual-connectivity state, where the UE can transmit and receive data to and from both the macro BS 601 and the micro BS 603, 605, or 607. Here, the macro BS 601 operating as an LTE / LTE-A system is included in the primary cell group (MCG), and the micro BS 603, 605, or 607 operating as an NR system is included in the secondary cell group (SCG). When a UE is in dual connectivity, this can be represented as a UE configured with an MCG using E-UTRA radio access (or LTE / LTE-A) and an SCG using NR radio access. Alternatively, the UE can be represented as a UE configured with NR E-UTRA dual connectivity (NE-DC).

[0111] According to the second configuration, after the UE performs initial access to small BS 603, 605, or 607 operating as an NR system, the UE receives configuration information for data transmission and reception regarding small BS 603, 605, or 607 via a higher-layer signal (system or RRC signal). Then, the UE receives configuration information for data transmission and reception regarding macro BS 601 operating as an LTE / LTE system via the small BS 603, 605, or 607 via the higher-layer signal (system or RRC signal), and performs random access to macro BS 601, thus achieving a dual-connectivity state, where the UE can transmit and receive data to and from both macro BS 601 and small BS 603, 605, or 607. Here, small BS 603, 605, or 607 operating as an NR system are included in the MCG, and macro BS 601 operating as an LTE system is included in the SCG. When a UE is in dual connectivity, this can be represented as the UE being configured with an MCG using NR radio access and an SCG using E-UTRA radio access (or LTE / LTE-A). Alternatively, the UE can be represented as being configured with NR E-UTRA dual connectivity (NE-DC).

[0112] According to the third configuration, after the UE performs initial access to a first BS 601, 603, 605, or 607 operating as an NR system, the UE receives configuration information for data transmission and reception regarding the first BS via a higher-layer signal (system or RRC signal). Then, the UE receives configuration information for data transmission and reception regarding a second BS 601, 603, 605, or 607 operating as an NR system from the first BS via a higher-layer signal (system or RRC signal), and performs random access to the second BS, thus having a dual-connectivity state, where the UE can transmit and receive data to and from both the first and second BSs. Here, the first BS operating as an NR system is included in the MCG, and the second BS, also operating as an NR system, is included in the SCG. When the UE is in a dual-connectivity state, this can be represented as the UE being configured with both an MCG using NR radio access and an SCG using NR radio access. Alternatively, the UE can be represented as being configured with NR dual-connectivity (NN-DC).

[0113] In the above description, the dual connectivity configuration is described for a specific UE 609; however, the dual connectivity configuration can also be applied to IAB node 614. The dual connectivity configuration and access procedure of UE 609 described above can also be applied to the dual connectivity of IAB node 614. Therefore, IAB node 614 can perform dual connectivity to different parent IAB nodes 611 and 612 by applying the dual connectivity procedure and method of UE 609. These different parent IAB nodes 611 and 612 are connected to different donor BSs 601 and 607 via wireless backhaul (615), or to different parent IAB nodes 612 and 613, which are both connected to a donor BS 601 via wireless backhaul (616). Reference Figure 7 and Figure 8 The dual-connection structure of the IAB node will now be described in detail.

[0114] First, refer to Figure 7 The structure in which IAB nodes perform dual connections to different parent IAB nodes connected to a donor BS via wireless backhaul will now be described.

[0115] Figure 7 This is a diagram schematically illustrating a dual-connection structure of an IAB node according to an embodiment of the present disclosure. Figure 7 The dual-connection structure of the IAB node in this disclosure takes into account the functional decomposition described above.

[0116] exist Figure 7 In the gNB 701, there are CU and DU, and each IAB node includes MT and DU. MT is used to send data to and receive data from the parent node via the backhaul link, and DU is used to send data to and receive data from the child node via the backhaul link. Figure 7 In this configuration, parent IAB node #1 702 is wirelessly connected to gNB 701 (711) with one hop, and parent IAB node #2 703 is wirelessly connected to gNB 701 (712) with one hop. IAB node #1 704 performs dual connectivity to different parent IAB nodes #1 702 and #2 703, and is wirelessly connected to gNB 701 via different parent IAB nodes with two hops.

[0117] Despite Figure 7Not shown, but the CU of gNB 701 controls not only the DU of gNB 701, but also the DUs of all IAB nodes, namely the parent IAB node #1 702, parent IAB node #2 703, and IAB node #1 704 wirelessly connected to gNB 701. The CU can allocate radio resources to the DUs, enabling the DUs to send data to and receive data from the MTs of the IAB nodes at lower layers of the DUs. The allocation of radio resources can be performed by sending system information, higher-layer signals, or physical signals to the DUs using the F1AP interface. Here, the IAB nodes of the DUs that have received radio resources use the resources to send DL control / data and signals or UL control / data and signals to the MTs of lower-layer child IAB nodes, and to receive DL control / data and signals from the MTs of lower-layer child IAB nodes, based on resource configurations configured with DL time resources, UL time resources, flexible time resources, resource type, availability, etc., and instructions from the DUs of higher-layer parent IAB nodes.

[0118] exist Figure 7 In this configuration, IAB node #1 704 is dual-connected to two different parent IAB nodes, #1 702 and #2 703, and both parent IAB nodes #1 702 and #2 703 are connected to a donor BS 701 via wireless backhaul. Therefore, the MT in IAB node #1 704 is controlled by each DU in the higher-level parent IAB nodes 702 or 703 to receive scheduling for data transmission and reception, and the DU in IAB node #1 704 must act as the BS for data transmission and reception with respect to the lower-level IAB nodes and the UE, making it possible that the MT and DU are not coordinated in real time.

[0119] Next, refer to Figure 8 Now, a structure will be described in which an IAB node performs dual connections to different parent IAB nodes that are connected to different donor BSs via wireless backhaul.

[0120] Figure 8 This is a diagram schematically illustrating a dual-connection structure of an IAB node according to an embodiment of the present disclosure. Figure 8 The dual-connection structure of the IAB node in this disclosure takes into account the functional decomposition described above.

[0121] exist Figure 8 In this context, gNB #1 801 includes a CU and a DU, and each IAB node includes an MT for sending and receiving data from the parent node via a backhaul link and a DU for sending and receiving data from the child node via a backhaul link. Figure 8In this configuration, parent IAB node #1 803 is wirelessly connected to gNB #1 801 via a single hop (811), while parent IAB node #2 804 is wirelessly connected to gNB #2 802 via a single hop (812). IAB node #1 805 performs dual connectivity to both parent IAB node #1 803 and parent IAB node #2 804, and is wirelessly connected to both gNB #1 801 and gNB #2 802 via two different parent IAB nodes.

[0122] Despite Figure 8 Not shown in the diagram, but the CU of gNB #1 801 can control not only the DU of gNB #1 801, but also the DUs of any lower IAB node (i.e., parent IAB node #1 803) wirelessly connected to gNB #1 801, and the CU of gNB #2 802 can control not only the DU of gNB #2 804, but also the DUs of any lower IAB node (i.e., parent IAB node #2 804) wirelessly connected to gNB #2 802. The DU of IAB node #1 805 wirelessly connected to gNB #1 801 and gNB #2 802 can be controlled by the CU of the gNB included in the MCG (e.g., gNB #1).

[0123] The CU can allocate radio resources to the DU, enabling the DU to send and receive data from the MT of the IAB node at a lower layer of the DU. The allocation of radio resources can be performed by sending system information, higher-layer signals, or physical signals to the DU using the F1AP interface. Here, the IAB node of the DU that has received radio resources uses the resources, configured with DL time resources, UL time resources, flexible time resources, resource type, availability, etc., and as instructed by the DU of the higher parent IAB node, to send DL control / data and signals or UL control / data and signals to the MT of the lower child IAB node, and to receive DL control / data and signals from the MT of the lower child IAB node.

[0124] exist Figure 8 In this configuration, IAB node #1 805 is dual-connected to different parent IAB nodes #1 803 and #2 804, and parent IAB nodes #1 803 and #2 804 are respectively connected to different donor BSs 801 and 802 via wireless backhaul. Therefore, since the MT in IAB node #1 805 is controlled at a higher layer by the DU in parent IAB nodes 803 or 804 to receive scheduling for data transmission and reception, and the DU in IAB node #1 805 must act as a BS for data transmission and reception with respect to lower-level IAB nodes and the UE, the MT and DU can not be as separate as in the previous configuration. Figure 7In a dual-connection structure, it is coordinated in real time. (Refer to...) Figure 9 Describe these details.

[0125] Figure 9 This is a diagram schematically illustrating the environment that may occur in a dual-connection structure of an IAB node according to an embodiment of the present disclosure.

[0126] Figure 9 It is shown according to the reference Figure 7 and Figure 8 The description pertains to the case where IAB node #1 904 is wirelessly connected to different parent IAB nodes via dual connectivity (e.g., where IAB node #1 904 is wirelessly connected to parent IAB node #1 902 (913) and wirelessly connected to parent IAB node #2 903 (916)), wherein the parent IAB node indicates the MT and gNB CU of IAB node #1 904. Figure 5 , Figure 7 and Figure 8 The resources described in, as in Figure 7 and Figure 8 The instructions specify the resource allocation for the DU of IAB node #1.

[0127] Here, as in Figure 9 In 915 and 916, the MT of IAB node #1 904 can perform DL reception or UL transmission according to the configuration and instructions from parent IAB node #1 902 or parent IAB node #2 903, and as in Figure 9 In 917, the DU of IAB node #1 904 can perform UL reception or DL ​​transmission according to the configuration and instructions of the MT of the lower IAB node.

[0128] The MT of IAB node #1 904 determines the time resource as a DL time resource, a UL time resource, or a flexible time resource based on the configuration and instructions from the DU of parent IAB node #1 902. Furthermore, the MT of IAB node #1 904 determines the time resource as a DL time resource, a UL time resource, or a flexible time resource based on the configuration and instructions from the DU of parent IAB node #2 903. Additionally, the DU of IAB node #1 904 determines the time resource as a DL time resource, a UL time resource, or a flexible time resource according to the configuration from the CU, and determines the resource as hard (H), soft (S), or unavailable (NA) based on its type.

[0129] Subsequently, when the time resource is determined to be a DL time resource according to the scheduling from parent IAB node #1 902 or parent IAB node #2 903, the MT of IAB node #1 904 can receive DL control / data channels and reference signals. When the time resource is determined to be a UL time resource, the MT of IAB node #1 904 can transmit UL control / data channels and reference signals, and can receive DL control / data channels and reference signals or transmit UL control / data channels and reference signals according to instructions. This applies when the time resource is determined to be a flexible time resource. On the other hand, although in Figure 9 Not shown, but the DU of IAB node #1 904 can determine the time resource as DL time resource, UL time resource, or flexible time resource according to the MT instruction from the CU to the lower IAB node, and transmit UL control / data channel and reference signal, and therefore can receive UL control / data channel and reference signal, or can transmit DL control / data channel and reference signal. Therefore, according to the instructions and determinations of the parent IAB node and the configuration from the CU, each of the MT and DU of IAB node #1 904 must determine and perform the transmission and reception of the time resource, and in this case, it is possible that the half-duplex constraint of the IAB node cannot be satisfied. This will now be described in detail as an example. Figure 9 Situations 1, 2, and 3.

[0130] In Case 1, the MT of IAB node #1 904 can determine the time resource as DL time resource according to the instruction from the DU of parent IAB node #1 902, in order to receive DL control / data channels and reference signals. Simultaneously, the MT of IAB node #1 904 can determine the time resource as UL time resource according to the instruction from the DU of parent IAB node #2 903, in order to transmit UL control / data channels and reference signals. At the same time, the DU of IAB node #1 904 can determine the time resource as UL time resource for receiving UL control / data channels and reference signals. Therefore, the half-duplex constraint cannot be satisfied when the MT of IAB node #1 904 must perform reception and transmission relative to different parent IAB nodes and the DU must perform reception.

[0131] In scenario 2, the MT of IAB node #1 904 can determine the time resource as DL time resource according to the instruction from the DU of parent IAB node #1 902 to receive DL control / data channels and reference signals. Simultaneously, the MT of IAB node #1 904 can determine the time resource as UL time resource according to the instruction from the DU of parent IAB node #2 903 to transmit UL control / data channels and reference signals. At the same time, the DU of IAB node #1 904 can determine the time resource as DL time resource to transmit DL control / data channels and reference signals. Therefore, the half-duplex constraint cannot be satisfied when the MT of IAB node #1 904 must perform reception and transmission relative to different parent IAB nodes and the DU must perform transmission.

[0132] In scenario 3, the MT of IAB node #1 904 can determine the time resource as UL time resource according to the instruction from the DU of parent IAB node #1 902 in order to transmit UL control / data channels and reference signals. Simultaneously, the MT of IAB node #1 904 can determine the time resource as DL time resource according to the instruction from the DU of parent IAB node #2 903 in order to receive DL control / data channels and reference signals. Conversely, the DU of IAB node #1 904 can determine the time resource as DL time resource to transmit DL control / data channels and reference signals. Therefore, the half-duplex constraint cannot be satisfied when the MT of IAB node #1 904 must perform transmission and reception relative to different parent IAB nodes and the DU must perform transmission (or reception).

[0133] This disclosure provides an embodiment of a method for simultaneously transmitting and receiving data in the backhaul link while satisfying the half-duplex constraint of the IAB node when the transmission and reception of the MT conflicts with the transmission and reception of the DU in the IAB node.

[0134] [Implementation Plan 1]

[0135] In Example 1, a scenario is assumed where the transmission and reception of DUs and the transmission and reception of MTs of IAB node #1 904 may conflict with each other when following configuration from the CU, instructions or scheduling from parent IAB node #1 902, or when connected to parent IAB node #2 903 via dual connectivity. In Example 1, the procedure for IAB node #1 904 can be determined based on whether the resource type of the DU of IAB node #1 904 is hard, soft, or unavailable (NA).

[0136] When the resource type of the DU of IAB node #1 904 is hard, the DU of IAB node #1 904 can perform both sending and receiving, regardless of the sending and receiving of the MT of IAB node #1 904. That is, when the time resource of the DU of IAB node #1 904 is DL, the DU of IAB node #1 904 can perform sending; when the time resource of the DU of IAB node #1 904 is UL, the DU of IAB node #1 904 can perform receiving; and when the time resource of the DU of IAB node #1 904 is flexible, the DU of IAB node #1 904 can perform either sending or receiving. In this case, sending or receiving from the MT of IAB node #1 904 can only be done from the scheduling of the parent IAB node corresponding to the sending or receiving direction of the DU of IAB node #1 904 (i.e., satisfying the half-duplex constraint). For example, when the DU of IAB node #1 904 performs a transmission, the MT of IAB node #1 904 can perform a UL transmission according to the instruction from the parent IAB node scheduled for UL. Therefore, when the MT of IAB node #1 904 is scheduled for DL, it cannot follow the instruction from the parent IAB node, and the MT of IAB node #1 904 cannot receive DL transmissions.

[0137] When the resource type of the DU of IAB node #1 904 is soft, the DU of IAB node #1 904 can perform transmission or reception when at least one of the following conditions 1, 2, or 3 satisfies the half-duplex constraint. That is, when at least one of conditions 1, 2, or 3 is satisfied, the DU of IAB node #1 904 can perform transmission when its time resources are used for DL, can perform reception when its time resources are used for UL, and can perform transmission or reception when its time resources are flexible.

[0138] (Condition 1) The MT of IAB node #1 904 does not perform transmission or reception simultaneously with the transmission or reception of DU. In other words, Condition 1 corresponds to the case where there is no scheduling of transmission or reception from the parent IAB node while DU is transmitting or receiving.

[0139] (Condition 2) Because the transmission or reception direction of the DU of IAB node #1 904 corresponds to the transmission or reception direction of the MT of IAB node #1 904, the half-duplex constraint can be maintained, ensuring that the transmission or reception direction of the DU of IAB node #1 904 does not affect the transmission or reception of the MT of IAB node #1 904. In this case, for example, for the transmission or reception direction of the MT of IAB node #1 904, the transmission or reception direction scheduled or indicated by the parent IAB node included in the MCG can be considered first, and then when there is no scheduling or indication of data transmission or reception from the parent IAB node included in the MCG, the transmission or reception direction scheduled or indicated by the parent IAB node included in the SCG can be considered.

[0140] (Condition 3) The MT of IAB node #1 904 receives an indication from at least one parent IAB node that soft resources are available for the DU of IAB node #1 904.

[0141] When the resource type of the DU of IAB node #1 904 is NA (unavailable) for the half-duplex constraint, the DU of IAB node #1 904 does not perform transmission or reception. In this case, if scheduling conflicts occur between parent IAB nodes, the MT of IAB node #1 904 can prioritize the scheduling from parent IAB nodes included in the MCG. That is, the MT of IAB node #1 904 can perform transmission or reception according to the scheduling from parent IAB nodes included in the MCG, and can ignore the scheduling from the SCG when the scheduling from parent IAB nodes included in the SCG does not satisfy the half-duplex constraint.

[0142] When the DU of IAB node #1 904 sends SS / PBCH blocks, sends PDCCH for SIB1 transmission, sends periodic CSI-RS, or receives PRACH or SR on time resources (i.e., time resources where the transmission and reception of the DU and the transmission and reception of the MT of IAB node #1 904 may conflict with each other), if the resource type of the DU of IAB node #1 904 is hard, IAB node #1 904 can execute the procedures of IAB node #1 904 regardless of the resource type configured for the DU of IAB node #1 904.

[0143] [Implementation Plan 2]

[0144] In Example 2, a scenario is assumed where the transmission and reception of the DU and the transmission and reception of the MT of IAB node #1 904 may conflict when following configuration from the CU, instructions or scheduling from parent IAB node #1 902, or when connected to parent IAB node #2 903 via dual connectivity. In Example 2, based on the direction of the DU resources of IAB node #1 904, the process for IAB node #1 904 can be determined according to whether the DU resources are used for UL, DL, or flexible. For example, when the direction of the DU resources of IAB node #1 904 is DL, the MT of IAB node #1 904 can execute instructions only from the parent IAB node scheduled by the UL to satisfy the half-duplex constraint. Therefore, the MT of IAB node #1 904 can ignore scheduling from parent IAB nodes that cannot satisfy the half-duplex constraint.

[0145] [Example 3]

[0146] In Example 3, a scenario is assumed where, when following configuration from the CU or instructions or scheduling from parent IAB node #1 902, or connected to parent IAB node #2 903 via dual connectivity to IAB node #1 904, the transmission and reception of DU and the transmission and reception of MT of IAB node #1 904 may conflict with each other. In Example 3, based on the direction of resources or scheduling from the parent IAB node of the MCG that belongs to the scheduling of MT of IAB node #1 904, i.e., according to the scheduling or resource configuration and instructions from the parent IAB node belonging to the MCG, the process for IAB node #1 904 can be determined based on whether the MT resources are used for UL, DL, or flexibly. For example, the MT of IAB node #1 904 can perform DL reception to satisfy half-duplex constraints when the direction of the resource scheduled by the parent IAB node included in the MCG is DL, and can receive data from the parent IAB node included in the SCG only when the direction of the resource is DL. For DL, in this case, the DU of IAB node #1 904 can perform only UL reception. For example, when the direction of the resource scheduled by the parent IAB node in the MCG is UL, the MT of IAB node #1 904 can perform UL transmission to satisfy half-duplex constraints, and can transmit data from the parent IAB node included in the SCG only when the direction of the resource is UL. In this case, the DU of IAB node #1 904 can perform only DL transmission. In other words, the MT of IAB node #1 904 can ignore scheduling from the parent IAB node included in the SCG that cannot satisfy the half-duplex constraint.

[0147] [Implementation Plan 4]

[0148] In Example 4, we assume a situation where the transmission and reception of the MT of IAB node #1904 may conflict with each other when following the configuration from the CU or the instructions or schedules from parent IAB node #2 903, which is connected to IAB node #1 904 via dual connectivity. In this case, we assume that the DU of IAB node #1 904 does not perform transmission or reception. When the schedules received from the parent IAB node conflict with each other, the MT of IAB node #1 904 can prioritize the schedules from the parent IAB node included in the MCG. That is, the MT of IAB node #1 904 can perform transmission or reception according to the schedules from the parent IAB node included in the MCG, and can ignore the schedules from the SCG when the schedules from the parent IAB node included in the SCG do not satisfy the half-duplex constraint.

[0149] One or more embodiments may be combined and used, and may be applied to some or all of this disclosure.

[0150] Figure 10 This is a flowchart describing a method for sending and receiving data performed by an IAB node according to embodiments of the present disclosure.

[0151] Reference Figure 10 In operation 1010, the IAB node according to an embodiment of the present disclosure can receive resource allocation information from the IAB donor node.

[0152] In operation 1020, an IAB node according to an embodiment of the present disclosure may receive first resource scheduling information from a first parent IAB node.

[0153] In operation 1030, an IAB node according to an embodiment of the present disclosure may receive second resource scheduling information from a second parent IAB node.

[0154] In operation 1040, an IAB node according to an embodiment of the present disclosure can send data to at least one of a first parent IAB node, a second parent IAB node, a child IAB node, or a UE (e.g., a UE in a cell) based on resource allocation information, first resource scheduling information, and second resource scheduling information, and receive data from at least one of the first parent IAB node, the second parent IAB node, the child IAB node, or a UE (e.g., a UE in a cell).

[0155] In order to implement the embodiments of this disclosure, Figure 11 and Figure 12 The transmitter, receiver, and controller of the UE and BS are shown respectively. Furthermore, Figure 13 The apparatus for an IAB node is shown. Figures 11 to 13The present invention illustrates a method for a BS (donor BS) to perform backhaul link transmission or reception with an IAB node on millimeter waves, and a method for a UE to perform access link transmission or reception with an IAB node when transmitting or receiving backhaul links or access links via an IAB node in a 5G communication system corresponding to an embodiment of the present disclosure. In order to perform the methods, the transmitter, receiver and processor of each of the BS, UE and IAB node may be operated according to the embodiments.

[0156] Figure 11 This is a block diagram illustrating the internal structure of a UE according to an embodiment of the present disclosure. (Refer to...) Figure 11 The UE may include a UE controller 1101, a UE receiver 1102, and a UE transmitter 1103. Although not shown, the UE may also include memory. However, the components of the UE are not limited to these. Figure 11 The example shown is illustrated. For instance, the UE may include more or fewer components than those described above. Furthermore, the UE controller 1101, UE receiver 1102, and UE transmitter 1103 may be implemented in a single chip.

[0157] UE controller 1101 can control a series of processes to enable the UE to operate according to embodiments of the present disclosure. For example, UE controller 1101 according to embodiments of the present disclosure can control access link transmission or reception differently relative to the IAB node. UE controller 1101 can control UE receiver 1102 and UE transmitter 1103 to receive and transmit information. Furthermore, UE controller 1101 may include one or more processors.

[0158] In embodiments of this disclosure, the UE receiver 1102 and the UE transmitter 1103 can be collectively referred to as a transceiver. The transceiver can transmit signals to and receive signals from the BS. Signals may include control information and data. For this purpose, the transceiver may include an RF transmitter for up-converting and amplifying the frequency of the signal to be transmitted, and an RF receiver for low-noise amplification and down-converting the frequency of the signal to be received. Furthermore, the transceiver can receive signals on a wireless channel and output those signals to the UE controller 1101, and can also transmit signals output from the UE controller 1101 on the wireless channel.

[0159] A memory (not shown) may store programs and data required for the operation of the UE. Additionally, the memory may store control information or data included in signals received by the UE. The memory may include storage media such as read-only memory (ROM), random access memory (RAM), hard disk, optical disc ROM (CD-ROM), and digital multifunction disc (DVD), or a combination of storage media. Furthermore, the memory may not exist separately but may be included within the UE controller 1101. Moreover, the UE controller 1101 can control components of the UE by executing programs stored in the memory.

[0160] Figure 12 This is a block diagram illustrating the internal structure of a BS according to an embodiment of the present disclosure. (Refer to...) Figure 12 The BS may include a BS controller 1201, a BS receiver 1202, and a BS transmitter 1203. Although not shown, the BS may also include a memory. However, the components of the BS are not limited to these. Figure 12 The example shown. For example, the BS may include more or fewer components than those described above. Furthermore, the BS controller 1201, BS receiver 1202, and BS transmitter 1203 may be implemented in a single chip.

[0161] The BS controller 1201 can control a series of processes to enable the BS to operate according to embodiments of the present disclosure. For example, it can control backhaul link transmission or reception and access link transmission or reception with respect to IAB nodes according to embodiments of the present disclosure. The BS controller 1201 can control the BS receiver 1202 and the BS transmitter 1203 to receive and transmit information. Furthermore, the BS controller 1201 may include one or more processors.

[0162] In embodiments of this disclosure, the BS receiver 1202 and the BS transmitter 1203 can be collectively referred to as a transceiver. The transceiver can transmit signals to and receive signals from the UE. Signals may include control information and data. For this purpose, the transceiver may include an RF transmitter for up-converting and amplifying the frequency of the signal to be transmitted, and an RF receiver for low-noise amplification and down-converting the frequency of the signal to be received. Furthermore, the transceiver can receive signals on a wireless channel and output those signals to the BS controller 1201, and can also transmit signals output from the BS controller 1201 on the wireless channel.

[0163] A memory (not shown) may store programs and data required for the operation of the BS. Furthermore, the memory may store control information or data included in signals received by the BS. The memory may include storage media such as ROM, RAM, hard disk, CD-ROM, and DVD, or a combination of storage media. Moreover, the memory may not exist separately but may be included within the BS controller 1201. Furthermore, the BS controller 1201 can control the components of the BS by executing programs stored in the memory.

[0164] Figure 13 This is a block diagram illustrating the internal structure of an IAB node according to an embodiment of the present disclosure. Figure 13 As shown, an IAB node may include a BS function controller 1301, a BS function receiver 1302, and a BS function transmitter 1303 for transmitting or receiving signals to lower-level IAB nodes via a backhaul link. Furthermore, an IAB node may include a UE function controller 1311, a UE function receiver 1312, and a UE function transmitter 1313, etc., for initial access to higher-level IAB nodes and donor BS, for transmitting or receiving higher-layer signals before transmitting or receiving signals via a backhaul link, and for transmitting or receiving signals to higher-level IAB nodes and donor BS via a backhaul link. Although not shown, an IAB node may also include memory. However, the components of an IAB node are not limited to these. Figure 13 The example shown. For instance, an IAB node may include more or fewer components than those described above. Furthermore, Figure 13 Each component shown can be implemented as a single chip. Furthermore, each of the BS function controller 1301 and the UE function controller 1311 of the IAB node can include one or more processors.

[0165] The BS function controller 1301 of the IAB node can control a series of processes to enable the IAB node to operate according to embodiments of the present disclosure, and can, for example, perform the functions of the IAB node's DU as described above. For example, the BS function controller 1301 can differently control backhaul link transmission or reception with respect to lower IAB nodes and access link transmission or reception with the UE. In embodiments of the present disclosure, the BS function receiver 1302 and the BS function transmitter 1303 can be collectively referred to as transceivers. The transceivers can transmit and receive signals to and from lower IAB nodes and the UE. Signals may include control information and data. For this purpose, the transceivers may include an RF transmitter for up-converting and amplifying the frequency of the signal to be transmitted, and an RF receiver for low-noise amplification and down-converting the frequency of the signal to be received. Furthermore, the transceivers can receive signals on a wireless channel and can output those signals to the BS function controller 1301, and can also transmit signals output from the BS function controller 1301 on a wireless channel.

[0166] According to the embodiments of this disclosure described above, the UE function controller 1311 of the IAB node can control a series of processes for lower IAB nodes to operate as a UE for data transmission and reception with respect to the donor BS or higher IAB nodes, and can, for example, perform the MT functions of the IAB node as described above. For example, according to embodiments of this disclosure, the UE function controller 1311 can control backhaul link transmission or reception with respect to the donor BS and higher IAB nodes differently. In embodiments of this disclosure, the UE function receiver 1312 and the UE function transmitter 1313 can be collectively referred to as transceivers. The transceivers can transmit signals to and receive signals from the donor BS and higher IAB nodes. The signals may include control information and data. For this purpose, the transceivers may include an RF transmitter for up-converting and amplifying the frequency of the signal to be transmitted, and an RF receiver for low-noise amplification and down-converting the frequency of the signal to be received. In addition, the transceiver can receive signals on the wireless channel and output the signals to the UE function controller 1311, and can also transmit signals output from the UE function controller 1311 on the wireless channel.

[0167] A memory (not shown) may store programs and data required for the operation of the IAB node. Additionally, the memory may store control information or data included in signals received by the IAB node. The memory may include storage media such as ROM, RAM, hard disk, CD-ROM, and DVD, or a combination of storage media. Furthermore, the memory may not exist alone, but may be included in the BS function controller 1301 and / or the UE function controller 1311 of the IAB node. Moreover, the BS function controller 1301 and / or the UE function controller 1311 of the IAB node can control the components of the IAB node by executing programs stored in the memory.

[0168] At the same time, including Figure 13 The BS function controller 1301 and UE function controller 1311 of the IAB node can be integrated to implement an IAB node controller. In this case, the IAB node controller can control the functions of DU and MT in the IAB node.

[0169] The methods according to embodiments of this disclosure as described in the claims or specification can be implemented in hardware, software, or a combination of hardware and software.

[0170] When implemented as software, a computer-readable storage medium may be provided for storing one or more programs (e.g., software modules). The one or more programs stored in the computer-readable storage medium are configured to be executed by one or more processors in an electronic device. The one or more programs include instructions that instruct the electronic device to perform a method according to an embodiment of this disclosure as described in the claims or specification.

[0171] The program (e.g., a software module or software) can be stored in non-volatile memory, including RAM or flash memory, ROM, electrically erasable programmable read-only memory (EEPROM), disk storage devices, CD-ROMs, DVDs, other optical storage devices, or magnetic tape cartridges. Alternatively, the program can be stored in a memory that includes some or all of the above-described storage media. Furthermore, multiple such memories may be included.

[0172] Furthermore, the program can be stored in an attachable storage device accessible via any or a combination of communication networks such as the Internet, intranet, local area network (LAN), wide area network (WLAN), and storage area network (SAN). Such a storage device can be connected via an external port to an apparatus executing embodiments of this disclosure. Additionally, a separate storage device on a communication network can be connected to an electronic device executing embodiments of this disclosure.

[0173] In the above embodiments of this disclosure, components included in this disclosure are represented in a singular or plural form according to the embodiments. However, for ease of description, a singular or plural form is suitably chosen, and this disclosure is not limited thereto. Therefore, components expressed in a plural form may also be configured as a single component, and components expressed in a singular form may also be configured as a plural component. Furthermore, the embodiments of this disclosure described with reference to this specification and accompanying drawings are merely specific examples for ease of description and understanding of this disclosure, and are not intended to limit the scope of this disclosure. That is, those skilled in the art will understand that other modifications based on this disclosure are feasible. Moreover, embodiments can be combined when necessary. For example, parts of the methods provided in this disclosure can be combined with each other to enable the BS and UE to operate. Furthermore, embodiments of this disclosure can be applied to other communication systems, and various modifications based on the technical concepts of the embodiments are feasible.

Claims

1. A method performed by an Integrated Access and Backhaul (IAB) node in a wireless communication system, the method comprising: Receive the first scheduling information for flexible time resources from the first parent IAB node associated with the primary cell group (MCG); Receive second scheduling information for flexible time resources from the second parent IAB node associated with the subcell group SCG; Based on the first scheduling information and the second scheduling information, identify whether simultaneous transmission and reception in the MCG and the SCG are scheduled for resources configured with flexible time resources; and Based on the identification that simultaneous transmission and reception in the MCG and SCG are scheduled for the resource and that the IAB node cannot transmit and receive simultaneously, the operation is performed according to the first scheduling information for the resource.

2. The method according to claim 1, wherein, The operation based on the first scheduling information includes: Based on the direction of the resources used for data transmission and reception between the first parent IAB node and the IAB node, it is determined whether to transmit or receive data between the second parent IAB node and the IAB node.

3. The method according to claim 1, wherein, The operation based on the first scheduling information includes: Based on the first scheduling information, determine whether to send or receive data between the sub-IAB node or the user equipment (UE) and the IAB node; and Based on the determination, data is sent or received with the sub-IAB node or the UE.

4. The method according to claim 3, wherein, Based on the first scheduling information, determining whether to send or receive data between the sub-IAB node or the user equipment (UE) and the IAB node includes: Based on the direction of the resources used for data transmission and reception between the first parent IAB node and the IAB node, it is determined whether to transmit or receive data between the child IAB node or between the UE and the IAB node.

5. The method according to claim 1, wherein, The operation based on the first scheduling information includes: Based on the resource type of the resources used for data transmission and reception between the sub-IAB node or user equipment (UE) and the IAB node, it is determined whether to transmit or receive data between the second parent IAB node and the IAB node.

6. The method according to claim 1, wherein, When the direction of the resources used for data transmission and reception between the first parent IAB node and the IAB node is for downlink, the operation based on the first scheduling information includes: When the direction of the resources configured for data transmission and reception between the second parent IAB node and the IAB node is for downlink, it is determined that data will be received from the second parent IAB node; and When the direction of the resources configured for data transmission and reception between a sub-IAB node or a user equipment (UE) and the IAB node is for uplink, it is determined that data will be received from the sub-IAB node or the UE.

7. The method according to claim 1, wherein, When the direction of the resources used for data transmission and reception between the first parent IAB node and the IAB node is for uplink, the operation based on the first scheduling information includes: When the direction of the resources configured for data transmission and reception between the second parent IAB node and the IAB node is for uplink, it is determined that data will be transmitted to the second parent IAB node; and When the direction of the resources configured for data transmission and reception between the sub-IAB node or the user equipment (UE) and the IAB node is for downlink, it is determined that data will be transmitted to the sub-IAB node or the UE.

8. The method according to claim 1, wherein, Performing operations based on the first scheduling information includes one of the following: The IAB node sends data to the second parent IAB node based on the second scheduling information. The IAB node receives data from the second parent IAB node based on the second scheduling information, or The second scheduling information is ignored by the IAB node.

9. An integrated access and backhaul (IAB) node for transmitting and receiving data in a wireless communication system, the IAB node comprising: transceiver; as well as At least one processor is configured as follows: Receive the first scheduling information for flexible time resources from the first parent IAB node associated with the primary cell group (MCG); Receive second scheduling information for flexible time resources from the second parent IAB node associated with the subcell group SCG; Based on the first scheduling information and the second scheduling information, identify whether simultaneous transmission and reception in the MCG and the SCG are scheduled for resources configured with flexible time resources; and Based on the identification that simultaneous transmission and reception in the MCG and SCG are scheduled for the resource and that the IAB node cannot transmit and receive simultaneously, the operation is performed according to the first scheduling information for the resource.

10. The IAB node according to claim 9, wherein, The at least one processor is further configured to: determine whether to send or receive data between the second parent IAB node and the IAB node based on the direction of resources used for data transmission and reception between the first parent IAB node and the IAB node.

11. The IAB node according to claim 9, wherein, The at least one processor is further configured to: Based on the first scheduling information, determine whether to send or receive data between the sub-IAB node or the user equipment (UE) and the IAB node; and Based on the determination, data is sent or received with the sub-IAB node or the UE.

12. The IAB node according to claim 11, wherein, The at least one processor is further configured to: determine whether to send or receive data between the child IAB node or between the UE and the IAB node, based on the direction of resources used for data transmission and reception between the first parent IAB node and the IAB node.

13. The IAB node according to claim 11, wherein, The at least one processor is further configured to: determine whether to send or receive data between the second parent IAB node and the IAB node based on the resource type of the resources used for data transmission and reception between the sub-IAB node or user equipment (UE) and the IAB node.

14. The IAB node according to claim 9, wherein, When the direction of the resources used for data transmission and reception between the first parent IAB node and the IAB node is for downlink, the at least one processor is further configured to: When the direction of the resources configured for data transmission and reception between the second parent IAB node and the IAB node is for downlink, it is determined that data will be received from the second parent IAB node. as well as When the direction of the resources configured for data transmission and reception between a sub-IAB node or a user equipment (UE) and the IAB node is for uplink, it is determined that data will be received from the sub-IAB node or the UE.

15. The IAB node according to claim 9, wherein, When the direction of the resources used for data transmission and reception between the first parent IAB node and the IAB node is for uplink, the at least one processor is further configured to: When the direction of the resources configured for data transmission and reception between the second parent IAB node and the IAB node is for uplink, it is determined that data will be sent to the second parent IAB node. as well as When the direction of the resources configured for data transmission and reception between the sub-IAB node or the user equipment (UE) and the IAB node is for downlink, it is determined that data will be transmitted to the sub-IAB node or the UE.

Images