KR20220017817A - Apparatus and method for improved cell selection and failure handling process on integrated access and backhaul system in wireless communication systems - Google Patents

Abstract

The present disclosure relates to an apparatus and a method for improved cell selection and a failure handling process on an integrated access and backhaul system in a wireless communication system, capable of effectively providing a service in a mobile communication system. According to an embodiment of the present disclosure, a communication method of an integrated access backhaul (IAB) node in a wireless communication system includes receiving an RRC reconfiguration message from an IAB donor central unit (CU), identifying failure case information and excluded cell information included in the RRC reconfiguration message, and performing cell selection based on the identified information when detecting a radio link failure (RLF) in connection with a parent node or receiving a recovery failure notification from the parent node.

Description

Apparatus and method for improved cell selection and failure handling process on integrated access and backhaul system in wireless communication systems

The present disclosure relates to a wireless communication system, and more particularly, to a cell selection improvement method and a failure handling method for a backhaul access hole combining system.

Efforts are being made to develop an improved 5G communication system or pre-5G communication system to meet the explosively increasing demand for wireless data traffic due to the commercialization of 4G communication systems and the increase in multimedia services. For this reason, the 5G communication system or the pre-5G communication system is called a system after the 4G network (Beyond 4G Network) communication system or the LTE system after (Post LTE). In order to achieve a high data rate, the 5G communication system is being considered for implementation in a very high frequency (mmWave) band (eg, such as a 60 gigabyte (60 GHz) band). In order to alleviate the path loss of radio waves and increase the propagation distance of radio waves in the ultra-high frequency band, in the 5G communication system, beamforming, massive MIMO, full dimensional MIMO, FD-MIMO ), array antenna, analog beam-forming, and large scale antenna technologies are being discussed.

In addition, in order to improve the network performance of the system, in the 5G communication system, an evolved small cell, an advanced small cell, a cloud radio access network (cloud RAN), an ultra-dense network (ultra-dense network) ), Device to Device communication (D2D), wireless backhaul, moving network, cooperative communication, Coordinated Multi-Points (CoMP), and reception interference cancellation ) and other technologies are being developed. In addition, in the 5G system, the advanced coding modulation (ACM) methods FQAM (Hybrid FSK and QAM Modulation) and SWSC (Sliding Window Superposition Coding), and advanced access technologies FBMC (Filter Bank Multi Carrier), NOMA (non orthogonal multiple access), and sparse code multiple access (SCMA) are being developed.

On the other hand, the Internet is evolving from a human-centered connection network where humans create and consume information to an Internet of Things (IoT) network that exchanges and processes information between distributed components such as objects. Internet of Everything (IoE) technology, which combines big data processing technology through connection with cloud servers, etc. with IoT technology, is also emerging. In order to implement IoT, technology elements such as sensing technology, wired and wireless communication and network infrastructure, service interface technology, and security technology are required. , M2M), and MTC (Machine Type Communication) are being studied. In the IoT environment, an intelligent IT (Internet Technology) service that collects and analyzes data generated from connected objects and creates new values in human life can be provided. IoT is a field of smart home, smart building, smart city, smart car or connected car, smart grid, health care, smart home appliance, advanced medical service, etc. can be applied to

Accordingly, various attempts are being made to apply the 5G communication system to the IoT network. For example, in technologies such as sensor network, machine to machine (M2M), and machine type communication (MTC), 5G communication technology is implemented by techniques such as beam forming, MIMO, and array antenna. there will be The application of cloud radio access network (cloud RAN) as the big data processing technology described above can be said to be an example of convergence of 5G technology and IoT technology.

As various services can be provided according to the above-mentioned and the development of wireless communication systems, a method for effectively providing these services is required.

The present disclosure proposes a method of recovering a disconnected connection through a method for excluding selection to a specific cell according to the topology during operation for cell selection when an IAB node (Integrated Access Backhauled node) experiences a radio connection failure. . In addition, when the connection between IAB nodes fails, a method is proposed so that the lower node can perform handover quickly through the transmission of the failure indicator from the IAB node to the lower node.

The disclosed embodiment is intended to provide an apparatus and method for effectively providing a service in a mobile communication system.

Based on the re-determined overall topology information upon access and handover of the IAB node, the IAB donor CU (Central Unit) or IAB donor node can transmit information about the cell to be excluded when selecting the cell to each IAB node. When the IAB node receives the information transmitted by the IAB donor CU or the IAB donor node and needs to perform cell selection due to a connection problem, additional connection failure can be prevented in advance by excluding the cell corresponding to the information.

In addition, when the radio connection fails, the IAB node immediately informs the lower-level terminal of the radio connection failure, so that the lower-level terminal can immediately handover to another parent terminal. By enabling the lower-level terminal to immediately handover to another parent terminal, data that is delayed during the connection failure recovery time or data that may be finally lost can be protected.

According to the disclosed embodiment, by providing cell information to be excluded from cell selection in case of connection failure between IAB nodes, connection to the wrong cell is prevented during reconnection after connection failure, thereby enabling rapid failure recovery, as another idea, By transmitting the connection failure indicator to the lower node, a method for the lower node to perform handover quickly is provided, thereby preventing traffic loss of the access terminal of the lower node.

1 is a diagram illustrating a structure of an LTE system according to an embodiment of the present disclosure.
2 is a diagram illustrating a radio protocol structure of an LTE system according to an embodiment of the present disclosure.
3 is a diagram illustrating a structure of a next-generation mobile communication system according to an embodiment of the present disclosure.
4 is a diagram illustrating a radio protocol structure of a next-generation mobile communication system according to an embodiment of the present disclosure.
5 is a block diagram illustrating an internal structure of a terminal according to an embodiment of the present disclosure.
6 is a block diagram illustrating a configuration of a base station according to an embodiment of the present disclosure.
7 illustrates topology information according to an embodiment of the present disclosure.
8 is a flowchart illustrating a method for receiving cell exclusion information after an IAB node first accesses according to an embodiment of the present disclosure.
9 is a flowchart illustrating an operation method of an IAB node attempting initial access according to an embodiment of the present disclosure.
10 is a flowchart of a method for the donor CU to update excluded cell information of each IAB node when the IAB node establishes an RRC connection with the donor CU again after a HO (hand over) or reestablishment operation according to an embodiment of the present disclosure; shows
11 is a flowchart illustrating a cell exclusion operation of an IAB node in a terminal failure situation according to an embodiment of the present disclosure.
12 shows an example of a topology according to an embodiment of the present disclosure.
13 is a diagram for explaining an operation between a general IAB node and an access terminal.
14 is a diagram for explaining an operation between an IAB node and an access terminal according to an embodiment of the present disclosure.

Advantages and features of the present disclosure, and a method for achieving them will become apparent with reference to the embodiments described below in detail in conjunction with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below, but may be implemented in various different forms, and only the present embodiments allow the disclosure of the present disclosure to be complete, and common knowledge in the technical field to which the present disclosure belongs It is provided to fully inform the possessor of the scope of the invention, and the present disclosure is only defined by the scope of the claims. Like reference numerals refer to like elements throughout.

At this time, it will be understood that each block of the flowchart diagrams and combinations of the flowchart diagrams may be performed by computer program instructions. These computer program instructions may be embodied in a processor of a general purpose computer, special purpose computer, or other programmable data processing equipment, such that the instructions performed by the processor of the computer or other programmable data processing equipment are not described in the flowchart block(s). It creates a means to perform functions. These computer program instructions may also be stored in a computer-usable or computer-readable memory that may direct a computer or other programmable data processing equipment to implement a function in a particular manner, and thus the computer-usable or computer-readable memory. It is also possible that the instructions stored in the flow chart block(s) produce an article of manufacture containing instruction means for performing the function described in the flowchart block(s). The computer program instructions may also be mounted on a computer or other programmable data processing equipment, such that a series of operational steps are performed on the computer or other programmable data processing equipment to create a computer-executed process to create a computer or other programmable data processing equipment. It is also possible that instructions for performing the processing equipment provide steps for performing the functions described in the flowchart block(s).

Additionally, each block may represent a module, segment, or portion of code that includes one or more executable instructions for executing specified logical function(s). It should also be noted that in some alternative implementations it is also possible for the functions recited in blocks to occur out of order. For example, two blocks shown one after another may in fact be performed substantially simultaneously, or it is possible that the blocks are sometimes performed in the reverse order according to the corresponding function.

At this time, the term '~ unit' used in this embodiment means software or hardware components such as FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit), and '~ unit' performs certain roles do. However, '-part' is not limited to software or hardware. '~' may be configured to reside on an addressable storage medium or may be configured to refresh one or more processors. Accordingly, as an example, '~' indicates components such as software components, object-oriented software components, class components, and task components, and processes, functions, properties, and procedures. , subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables. The functions provided in the components and '~ units' may be combined into a smaller number of components and '~ units' or further separated into additional components and '~ units'. In addition, components and '~ units' may be implemented to play one or more CPUs in a device or secure multimedia card. Also, in an embodiment, '~ unit' may include one or more processors.

In the following description of the present disclosure, if it is determined that a detailed description of a related well-known function or configuration may unnecessarily obscure the subject matter of the present disclosure, the detailed description thereof will be omitted. Hereinafter, an embodiment of the present disclosure will be described with reference to the accompanying drawings.

A term for identifying an access node used in the following description, a term referring to network entities, a term referring to messages, a term referring to an interface between network objects, and various identification information Reference terms and the like are exemplified for convenience of description. Accordingly, the present disclosure is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used.

For convenience of description, the present disclosure uses terms and names defined in the 3rd Generation Partnership Project Long Term Evolution (3GPP LTE) standard. However, the present disclosure is not limited by the terms and names, and may be equally applied to systems conforming to other standards. In the present disclosure, eNB may be used interchangeably with gNB for convenience of description. That is, a base station described as an eNB may represent a gNB. Also, the term terminal may refer to mobile phones, NB-IoT devices, sensors, as well as other wireless communication devices.

Hereinafter, the base station, as a subject performing resource allocation of the terminal, may be at least one of gNode B, eNode B, Node B, a base station (BS), a radio access unit, a base station controller, or a node on a network. The terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smart phone, a computer, or a multimedia system capable of performing a communication function. Of course, it is not limited to the above example.

In particular, the present disclosure is applicable to 3GPP NR (5th generation mobile communication standard). In addition, the present disclosure provides intelligent services (eg, smart home, smart building, smart city, smart car or connected car, healthcare, digital education, retail business, security and safety-related services based on 5G communication technology and IoT-related technology) etc.) can be applied. In the present invention, eNB may be used interchangeably with gNB for convenience of description. That is, a base station described as an eNB may represent a gNB. Also, the term terminal may refer to mobile phones, NB-IoT devices, sensors, as well as other wireless communication devices.

A wireless communication system, for example, 3GPP's HSPA (High Speed Packet Access), LTE (Long Term Evolution or E-UTRA (Evolved Universal Terrestrial Radio Access)), LTE-Advanced (LTE-A), LTE-Pro, 3GPP2 HRPD (High Rate Packet Data), UMB (Ultra Mobile Broadband), and IEEE 802.16e, such as communication standards such as broadband wireless broadband wireless providing high-speed, high-quality packet data service It is evolving into a communication system.

As a representative example of a broadband wireless communication system, in an LTE system, an Orthogonal Frequency Division Multiplexing (OFDM) scheme is employed in a downlink (DL; DownLink), and Single Carrier Frequency Division Multiple Access (SC-FDMA) in an uplink (UL). ) method is used. Uplink refers to a radio link in which a terminal (UE; User Equipment or MS; Mobile Station) transmits data or control signals to a base station (eNode B or BS; A radio link that transmits signals. The multiple access method as described above divides the data or control information of each user by allocating and operating the time-frequency resources to which data or control information is to be transmitted for each user so that they do not overlap each other, that is, orthogonality is established. .

As a future communication system after LTE, that is, the 5G communication system must be able to freely reflect various requirements of users and service providers, so services that simultaneously satisfy various requirements must be supported. Services considered for the 5G communication system include Enhanced Mobile BroadBand (eMBB), massive Machine Type Communication (mMTC), and Ultra Reliability Low Latency Communication (URLLC). There is this.

According to some embodiments, the eMBB may aim to provide a data transfer rate that is more improved than the data transfer rate supported by the existing LTE, LTE-A, or LTE-Pro. For example, in the 5G communication system, the eMBB must be able to provide a maximum data rate of 20 Gbps in the downlink and a maximum data rate of 10 Gbps in the uplink from the viewpoint of one base station. In addition, the 5G communication system may have to provide the maximum transmission speed and at the same time provide the increased user perceived data rate of the terminal. In order to satisfy such a requirement, in the 5G communication system, it may be required to improve various transmission/reception technologies, including a more advanced multi-antenna (MIMO) transmission technology. In addition, while transmitting signals using a maximum of 20 MHz transmission bandwidth in the 2 GHz band currently used by LTE, the 5G communication system uses a wider frequency bandwidth than 20 MHz in the frequency band of 3 to 6 GHz or 6 GHz or more. Data transfer speed can be satisfied.

At the same time, mMTC is being considered to support application services such as the Internet of Things (IoT) in the 5G communication system. In order to efficiently provide the Internet of Things, mMTC may require large-scale terminal access support, improved terminal coverage, improved battery life, and reduced terminal cost within a cell. Since the Internet of Things is attached to various sensors and various devices to provide communication functions, it must be able to support a large number of terminals (eg, 1,000,000 terminals/km2) within a cell. In addition, since the terminal supporting mMTC is highly likely to be located in a shaded area that the cell cannot cover, such as the basement of a building, due to the characteristics of the service, wider coverage may be required compared to other services provided by the 5G communication system. A terminal supporting mMTC must be composed of a low-cost terminal, and since it is difficult to frequently exchange the battery of the terminal, a very long battery life time such as 10 to 15 years may be required.

Lastly, in the case of URLLC, as a cellular-based wireless communication service used for a specific purpose (mission-critical), remote control for a robot or machine, industrial automation, It may be used for a service used in an unmanned aerial vehicle, remote health care, emergency alert, and the like. Therefore, the communication provided by URLLC may have to provide very low latency (ultra-low latency) and very high reliability (ultra-reliability). For example, a service supporting URLLC must satisfy an air interface latency of less than 0.5 milliseconds, and at the same time may have a requirement of a packet error rate of 10-5 or less. Therefore, for a service supporting URLLC, the 5G system must provide a smaller Transmit Time Interval (TTI) than other services, and at the same time, it is a design that must allocate wide resources in the frequency band to secure the reliability of the communication link. items may be required.

The three services considered in the above-described 5G communication system, ie, eMBB, URLLC, and mMTC, may be multiplexed and transmitted in one system. In this case, different transmission/reception techniques and transmission/reception parameters may be used between services to satisfy different requirements of each service. However, the aforementioned mMTC, URLLC, and eMBB are only examples of different service types, and the service types to which the present disclosure is applied are not limited to the above-described examples.

In addition, the embodiment of the present disclosure will be described below using LTE, LTE-A, LTE Pro, or 5G (or NR, next-generation mobile communication) system as an example, but the present disclosure also applies to other communication systems having a similar technical background or channel type An embodiment of can be applied. In addition, the embodiments of the present disclosure may be applied to other communication systems through some modifications within a range that does not significantly depart from the scope of the present disclosure as judged by a person having skilled technical knowledge.

Hereinafter, the operating principle of the present invention will be described in detail with reference to the accompanying drawings. In the following description of the present invention, if it is determined that a detailed description of a known function or configuration related to the present invention may unnecessarily obscure the gist of the present invention, the detailed description thereof will be omitted. And, the terms to be described later are terms defined in consideration of functions in the present invention, which may vary according to intentions or customs of users and operators. Therefore, the definition should be made based on the content throughout this specification.

1 is a diagram illustrating the structure of an existing LTE system.

1, as shown, the radio access network of the LTE system is a next-generation base station (Evolved Node B, hereinafter ENB, Node B or base station) (1-05, 1-10, 1-15, 1-20) and It may be composed of a Mobility Management Entity (MME) (1-25) and an S-GW (1-30, Serving-Gateway). User equipment (hereinafter referred to as UE or terminal) 1-35 may access an external network through ENBs 1-05 to 1-20 and S-GW 1-30.

In FIG. 1 , ENBs 1-05 to 1-20 may correspond to existing Node Bs of the UMTS system. ENB is connected to the UE (1-35) through a radio channel and can perform a more complex role than the existing Node B. In the LTE system, all user traffic including real-time services such as VoIP (Voice over IP) through the Internet protocol may be serviced through a shared channel. Accordingly, there is a need for an apparatus for scheduling by collecting status information such as buffer status, available transmission power status, and channel status of UEs, and the ENBs 1-05 to 1-20 can handle this. One ENB can usually control multiple cells. For example, in order to implement a transmission rate of 100 Mbps, the LTE system may use, for example, Orthogonal Frequency Division Multiplexing (OFDM) as a radio access technology in a 20 MHz bandwidth. In addition, an Adaptive Modulation & Coding (AMC) method for determining a modulation scheme and a channel coding rate according to the channel state of the terminal may be applied. The S-GW 1-30 is a device that provides a data bearer, and may create or remove a data bearer according to the control of the MME 1-25. The MME is a device in charge of various control functions as well as a mobility management function for the terminal, and can be connected to a plurality of base stations.

2 is a diagram illustrating a radio protocol structure of an LTE system according to an embodiment of the present disclosure.

2, the radio protocol of the LTE system is packet data convergence protocol (PDCP) (2-05, 2-40), radio link control (RLC) ( 2-10, 2-35) and Medium Access Control (MAC) (2-15, 2-30). The PDCP may be in charge of operations such as IP header compression/restore. The main functions of PDCP can be summarized as follows.

- Header compression and decompression: ROHC (Robust Header Compression) only)

- Transfer of user data

- In-sequence delivery of upper layer PDUs (Protocol Data Units) at PDCP (Packet Data Convergence Protocol) re-establishment procedure for RLC (Radio Link Control) AM (Acknowledged Mode))

- Order reordering function (For split bearers in DC (Dual Connectivity) (only support for RLC AM): PDCP PDU routing for transmission and PDCP PDU reordering for reception)

- Duplicate detection of lower layer SDUs at PDCP re-establishment procedure for RLC AM

- Retransmission function (Retransmission of PDCP SDUs at handover and, for split bearers in DC, of PDCP PDUs at PDCP data-recovery procedure, for RLC AM)

- Ciphering and deciphering

- Timer-based SDU discard in uplink.

The radio link control (RLC) 2-10, 2-35 may perform an automatic repeat request (ARQ) operation by reconfiguring a PDCP packet data unit (PDU) to an appropriate size. . The main functions of RLC can be summarized as follows.

- Data transfer function (Transfer of upper layer PDUs)

- ARQ function (Error Correction through ARQ (only for AM data transfer))

- Concatenation, segmentation and reassembly of RLC SDUs (only for UM and AM data transfer)

- Re-segmentation of RLC data PDUs (only for AM data transfer)

- Reordering of RLC data PDUs (only for UM and AM data transfer)

- Duplicate detection (only for UM and AM data transfer)

- Protocol error detection (only for AM data transfer)

- RLC SDU (Service Data Unit) delete function (RLC SDU discard(only for UM (Unacknowledged mode) and AM data transfer))

- RLC re-establishment function (RLC re-establishment)

The MACs 1b-15 and 1b-30 are connected to several RLC layer devices configured in one terminal, and may perform operations of multiplexing RLC PDUs to MAC PDUs and demultiplexing RLC PDUs from MAC PDUs. The main functions of MAC can be summarized as follows.

- Mapping function (Mapping between logical channels and transport channels)

- Multiplexing/demultiplexing of MAC SDUs belonging to one or different logical channels into/from transport blocks (TB) delivered to/from the physical layer on transport channels)

- Scheduling information reporting function (Scheduling information reporting)

- HARQ (Hybrid Automatic Repeat Request) function (Error correction through HARQ)

- Priority handling between logical channels of one UE

- Priority handling between UEs by means of dynamic scheduling

- MBMS (Multimedia Broadcast and Multicast Service) service identification function (MBMS service identification)

- Transport format selection

- Padding function

The physical layer (2-20, 2-25) channel-codes and modulates upper layer data, makes OFDM symbols and transmits them over a radio channel, or demodulates and channel-decodes OFDM symbols received through the radio channel and transmits them to higher layers action can be made.

3 is a diagram illustrating a structure of a next-generation mobile communication system according to an embodiment of the present disclosure.

Referring to FIG. 3 , the radio access network of the next-generation mobile communication system (hereinafter referred to as NR or 5G) includes a next-generation base station (New Radio Node B, hereinafter, NR gNB or NR base station) 3-10 and a next-generation radio core network (New Radio Core). Network, NR CN) (3-05). Next-generation radio user equipment (New Radio User Equipment, NR UE or terminal) 3-15 may access an external network through NR gNB 3-10 and NR CN 3-05.

In FIG. 3 , the NR gNBs 3-10 may correspond to an Evolved Node B (eNB) of the existing LTE system. The NR gNB is connected to the NR UE 3-15 through a radio channel and can provide a service superior to that of the existing Node B. In the next-generation mobile communication system, all user traffic may be serviced through a shared channel. Accordingly, there is a need for an apparatus for scheduling by collecting status information such as buffer status, available transmission power status, and channel status of UEs, and the NR NB 3-10 can handle this. One NR gNB can control multiple cells. In the next-generation mobile communication system, a bandwidth greater than or equal to the current maximum bandwidth may be applied to implement ultra-high-speed data transmission compared to current LTE. In addition, beamforming technology may be additionally grafted by using Orthogonal Frequency Division Multiplexing (OFDM) as a radio access technology. In addition, an adaptive modulation & coding (AMC) scheme for determining a modulation scheme and a channel coding rate according to the channel state of the terminal may be applied. The NR CN (3-05) may perform functions such as mobility support, bearer setup, QoS setup, and the like. The NR CN is a device in charge of various control functions as well as a mobility management function for the terminal, and can be connected to a plurality of base stations. In addition, the next-generation mobile communication system may be linked with the existing LTE system, and the NR CN may be connected to the MME 3-25 through a network interface. The MME may be connected to the existing base station eNB (3-30).

4 is a diagram illustrating a radio protocol structure of a next-generation mobile communication system according to an embodiment of the present disclosure. .

4, the radio protocol of the next-generation mobile communication system is NR Service Data Adaptation Protocol (SDAP) (4-01, 4-45), NR PDCP (4-05, 4-40), NR RLC (4-10, 4-35), NR MAC (4-15, 4-30), and NR PHY (4-20, 4-25).

The main function of the NR SDAP (4-01, 4-45) may include some of the following functions.

- Transfer of user plane data

- Mapping between a QoS flow and a DRB for both DL (Down Link) and UL (Up Link)

- Marking QoS flow ID in both DL and UL packets for uplink and downlink

- A function of mapping a reflective QoS flow to a data bearer for uplink SDAP PDUs (reflective QoS flow to DRB mapping for the UL SDAP PDUs).

With respect to the SDAP layer device, the UE uses the header of the SDAP layer device for each PDCP layer device or for each bearer or for each logical channel by a radio resource control (RRC) message received from the base station. You can set whether to use the device's function or not. When SDAP header is set, Non-Access Stratum (NAS) QoS (Quality of Service) reflection setting 1-bit indicator (NAS reflective QoS) of SDAP header and Access Stratum (AS) QoS reflection setting 1 By using a bit indicator (AS reflective QoS), it is possible to instruct the UE to update or reconfigure mapping information for uplink and downlink QoS flows and data bearers. The SDAP header may include QoS flow ID information indicating QoS. The QoS information may be used as data processing priority, scheduling information, etc. to support a smooth service.

The main function of the NR PDCP (4-05, 4-40) may include some of the following functions.

- Header compression and decompression (ROHC only)

- Transfer of user data

- In-sequence delivery of upper layer PDUs

- Out-of-sequence delivery of upper layer PDUs

- Order reordering function (PDCP PDU reordering for reception)

- Duplicate detection of lower layer SDUs

- Retransmission of PDCP SDUs

- Ciphering and deciphering

- Timer-based SDU discard in uplink.

In the above description, the reordering function of the NR PDCP device may refer to a function of reordering PDCP PDUs received from a lower layer in order based on a PDCP sequence number (SN). The reordering function of the NR PDCP device may include a function of delivering data to a higher layer in the rearranged order, or may include a function of directly passing data without considering the order, and may be lost by reordering It may include a function of recording the PDCP PDUs that have been deleted, and may include a function of reporting a status on the lost PDCP PDUs to the transmitting side, and may include a function of requesting retransmission for the lost PDCP PDUs. have.

The main function of the NR RLC (4-10, 4-35) may include some of the following functions.

- Data transfer function (Transfer of upper layer PDUs)

- In-sequence delivery of upper layer PDUs

- Out-of-sequence delivery of upper layer PDUs

- ARQ function (Error Correction through ARQ)

- Concatenation, segmentation and reassembly of RLC SDUs

- Re-segmentation of RLC data PDUs

- Reordering of RLC data PDUs

- Duplicate detection

- Protocol error detection

- RLC SDU discard function (RLC SDU discard)

- RLC re-establishment function (RLC re-establishment)

In the above description, in-sequence delivery of the NR RLC device may refer to a function of sequentially delivering RLC SDUs received from a lower layer to a higher layer. When one RLC SDU is originally divided into several RLC SDUs and received, the in-sequence delivery function of the NR RLC device may include a function of reassembling it and delivering it.

In-sequence delivery of the NR RLC device may include a function of rearranging received RLC PDUs based on an RLC sequence number (SN) or a PDCP sequence number (SN), and may be lost by rearranging the order It may include a function of recording the lost RLC PDUs, a function of reporting a status on the lost RLC PDUs to the transmitting side, and a function of requesting retransmission of the lost RLC PDUs. have.

In-sequence delivery of the NR RLC device may include a function of sequentially delivering only RLC SDUs before the lost RLC SDU to a higher layer when there is a lost RLC SDU.

The in-sequence delivery function of the NR RLC device may include a function of sequentially delivering all RLC SDUs received before the timer starts to a higher layer if a predetermined timer expires even if there are lost RLC SDUs. have.

In-sequence delivery of the NR RLC device may include a function of sequentially delivering all received RLC SDUs to a higher layer if a predetermined timer expires even if there are lost RLC SDUs.

The NR RLC device may process RLC PDUs in the order in which they are received and deliver them to the NR PDCP device regardless of the sequence number (Out-of sequence delivery).

When the NR RLC device receives a segment, it may receive segments stored in the buffer or to be received later, reconstruct it into one complete RLC PDU, and then deliver it to the NR PDCP device.

The NR RLC layer may not include a concatenation function, and may perform a concatenation function in the NR MAC layer or may be replaced with a multiplexing function of the NR MAC layer.

In the above description, out-of-sequence delivery of the NR RLC device may refer to a function of directly delivering RLC SDUs received from a lower layer to a higher layer regardless of order. The out-of-sequence delivery function of the NR RLC device may include a function of reassembling and delivering when one original RLC SDU is divided into several RLC SDUs and received. Out-of-sequence delivery of the NR RLC device may include a function of storing the RLC SN or PDCP SN (Sequence Number) of the received RLC PDUs, sorting the order, and recording the lost RLC PDUs. can

The NR MACs 4-15 and 4-30 may be connected to several NR RLC layer devices configured in one terminal, and the main function of the NR MAC may include some of the following functions.

- Mapping function (Mapping between logical channels and transport channels)

- Multiplexing/demultiplexing of MAC SDUs

- Scheduling information reporting function (Scheduling information reporting)

- HARQ function (Error correction through HARQ)

- Priority handling between logical channels of one UE

- Priority handling between UEs by means of dynamic scheduling

- MBMS service identification

- Transport format selection

- Padding function

The NR PHY layer (4-20, 4-25) channel-codes and modulates upper layer data, creates an OFDM symbol and transmits it to a radio channel, or demodulates and channel-decodes an OFDM symbol received through the radio channel to the upper layer. You can perform a forwarding action.

5 is a block diagram illustrating an internal structure of a terminal according to an embodiment of the present disclosure.

Referring to the drawings, the terminal includes a radio frequency (RF) processing unit 5-10, a baseband processing unit 5-20, a storage unit 5-30, and a control unit 5-40. .

The RF processing unit 5-10 performs a function for transmitting and receiving a signal through a wireless channel, such as band conversion and amplification of the signal. That is, the RF processing unit 5-10 up-converts the baseband signal provided from the baseband processing unit 5-20 into an RF band signal, transmits it through the antenna, and converts the RF band signal received through the antenna to the baseband. down-convert to a signal. For example, the RF processing unit 5-10 may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a digital to analog converter (DAC), an analog to digital converter (ADC), etc. can In FIG. 5 , only one antenna is shown, but the terminal may include a plurality of antennas. In addition, the RF processing unit 5-10 may include a plurality of RF chains. Furthermore, the RF processing unit 5-10 may perform beamforming. For beamforming, the RF processing unit 5-10 may adjust the phase and magnitude of each of signals transmitted and received through a plurality of antennas or antenna elements. In addition, the RF processing unit 5-10 may perform MIMO, and may receive multiple layers when performing the MIMO operation.

The baseband processing unit 5-20 performs a function of converting between a baseband signal and a bit stream according to the physical layer standard of the system. For example, when transmitting data, the baseband processing unit 5-20 generates complex symbols by encoding and modulating the transmitted bit stream. Also, upon data reception, the baseband processing unit 5-20 restores the received bit stream by demodulating and decoding the baseband signal provided from the RF processing unit 5-10. For example, in the case of orthogonal frequency division multiplexing (OFDM), when transmitting data, the baseband processing unit 5-20 encodes and modulates a transmission bit stream to generate complex symbols, and maps the complex symbols to subcarriers. After that, OFDM symbols are constructed through inverse fast Fourier transform (IFFT) operation and cyclic prefix (CP) insertion. In addition, upon data reception, the baseband processing unit 5-20 divides the baseband signal provided from the RF processing unit 5-10 into OFDM symbol units, and a signal mapped to subcarriers through fast Fourier transform (FFT). After restoring the bits, the received bit stream is restored through demodulation and decoding.

The baseband processing unit 5-20 and the RF processing unit 5-10 transmit and receive signals as described above. Accordingly, the baseband processing unit 5-20 and the RF processing unit 5-10 may be referred to as a transmitter, a receiver, a transceiver, or a communication unit. Furthermore, at least one of the baseband processing unit 5-20 and the RF processing unit 5-10 may include a plurality of communication modules to support a plurality of different wireless access technologies. In addition, at least one of the baseband processing unit 5-20 and the RF processing unit 5-10 may include different communication modules to process signals of different frequency bands. For example, different wireless access technologies may include a wireless LAN (eg, IEEE 802.11), a cellular network (eg, LTE), and the like. In addition, the different frequency bands may include a super high frequency (SHF) (eg, 2.NRHz, NRhz) band and a millimeter wave (eg, 60GHz) band.

The storage unit 5-30 stores data such as a basic program, an application program, and setting information for the operation of the terminal. In particular, the storage unit 5-30 may store information related to a second access node that performs wireless communication using a second wireless access technology. In addition, the storage unit 5-30 provides the stored data according to the request of the control unit 5-40.

The controller 5-40 controls overall operations of the terminal. For example, the control unit 5-40 transmits and receives signals through the baseband processing unit 5-20 and the RF processing unit 5-10. In addition, the control unit 5-40 writes and reads data in the storage unit 5-40. To this end, the controller 5-40 may include at least one processor. For example, the controller 5-40 may include a communication processor (CP) that controls for communication and an application processor (AP) that controls an upper layer such as an application program.

6 is a block diagram illustrating a configuration of a base station according to an embodiment of the present disclosure.

6, the base station includes an RF processing unit 6-10, a baseband processing unit 6-20, a communication unit 6-30, a storage unit 6-40, and a control unit 6-50. is composed by

The RF processing unit 6-10 performs a function for transmitting and receiving a signal through a wireless channel, such as band conversion and amplification of the signal. That is, the RF processing unit 6-10 up-converts the baseband signal provided from the baseband processing unit 6-20 into an RF band signal, transmits it through the antenna, and converts the RF band signal received through the antenna to the baseband. down-convert to a signal. For example, the RF processing unit 6-10 may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, and the like. Although only one antenna is shown in FIG. 6 , the first access node may include a plurality of antennas. In addition, the RF processing unit 6-10 may include a plurality of RF chains. Furthermore, the RF processing unit 6-10 may perform beamforming. For beamforming, the RF processing unit 6-10 may adjust the phase and magnitude of each of signals transmitted and received through a plurality of antennas or antenna elements. The RF processing unit may perform a downlink MIMO operation by transmitting one or more layers.

The baseband processing unit 6-20 performs a function of converting a baseband signal and a bit stream according to the physical layer standard of the first radio access technology. For example, when transmitting data, the baseband processing unit 6-20 generates complex symbols by encoding and modulating the transmitted bit stream. Also, upon data reception, the baseband processing unit 6-20 restores the received bit stream by demodulating and decoding the baseband signal provided from the RF processing unit 6-10. For example, in the case of OFDM, when transmitting data, the baseband processing unit 6-20 generates complex symbols by encoding and modulating the transmission bit stream, maps the complex symbols to subcarriers, and performs IFFT operation and OFDM symbols are configured through CP insertion. In addition, upon data reception, the baseband processing unit 6-20 divides the baseband signal provided from the RF processing unit 6-10 into OFDM symbol units, and restores signals mapped to subcarriers through FFT operation. , to restore the received bit stream through demodulation and decoding. The baseband processing unit 6-20 and the RF processing unit 6-10 transmit and receive signals as described above. Accordingly, the baseband processing unit 6-20 and the RF processing unit 6-10 may be referred to as a transmitter, a receiver, a transceiver, a communication unit, or a wireless communication unit.

The backhaul communication unit 6-30 provides an interface for performing communication with other nodes in the network. That is, the backhaul communication unit 6-30 converts a bit string transmitted from the main base station to another node, for example, an auxiliary base station, a core network, etc. into a physical signal, and converts a physical signal received from another node into a bit string do.

The storage unit 6-40 stores data such as a basic program, an application program, and setting information for the operation of the main station. In particular, the storage unit 6-40 may store information on a bearer assigned to an accessed terminal, a measurement result reported from the accessed terminal, and the like. Also, the storage unit 6-40 may store information serving as a criterion for determining whether to provide or stop multiple connections to the terminal. In addition, the storage unit 6-40 provides the stored data according to the request of the control unit 6-50.

The control unit 6-50 controls overall operations of the main station. For example, the control unit 6-50 transmits and receives signals through the baseband processing unit 6-20 and the RF processing unit 6-10 or through the backhaul communication unit 6-30. In addition, the control unit 6-50 writes and reads data in the storage unit 6-40. To this end, the controller 6-50 may include at least one processor.

7 illustrates topology information according to an embodiment of the present disclosure.

Each IAB node is connected to an IAB donor node, and there is an IAB donor CU inside the IAB donor node, so each IAB node is also connected to the IAB donor CU. In the example of FIG. 7 , IAB node 2 may detect a Radio Link Failure (RLF) in connection with IAB node 1 which is a parent node. After detecting the RLF, the IAB node 2 may perform an RRC reestablishment operation. IAB node 2 may transmit a recovery failure notification to IAB node 3 and IAB node 4, which are lower nodes of IAB node 2, when the RRC reestablishment operation fails.

8 is a flowchart illustrating a method for receiving cell exclusion information after an IAB node first accesses according to an embodiment of the present disclosure.

Referring to FIG. 8 , a new IAB node 3 may select an IAB node 2 to be a parent node and perform a random access process with the IAB node 2 . After performing the random access procedure, IAB node 3 may obtain an uplink grant (UL grant) and transmit the RRCsetup request to the IAB donor CU. The RRC message may be transmitted by being encapsulated in a backhaul RLC channel through the parent node. The donor CU may transmit an RRC setup message to the IAB node 3 in the RRC layer. IAB node 3 receiving the RRC setup message transmits an RRCsetupcomplet message, so that the donor CU and the new IAB node 3 may establish an RRC connection. Thereafter, the Donor CU through the RRCReconfiguration message (a), BAP configuration (BAP (Backhaul Adaptation Protocol) configuration) information (eg, BAP address of IAB node 3, default UL BH RLC CH, default UL routing id for non -UP traffic, non-default BH RLC CH config) can be transmitted. Upon receiving the BAP configuration information, IAB node 3 may establish a BAP and apply the given configuration information. Using the given configuration information, the DU (Distributed Unit) of the IAB node 3 may request the F1 establishment to the Donor CU. Upon receiving this information, the Donor CU may establish an F1 interface by transmitting F1 establishment related configuration information. In the F1 setup request message, served cell information that the DU can operate (eg, NR CGI (Cell Global Identity) for each cell, NR PCI (Physical Cell ID), TAC (Tracking Area Code), served PLMN (Public Land) Mobile Network), Frequency Division Duplex (FDD)/Time Division Duplex (TDD) configuration information and, in each case, frequency information, measurement time configuration information, etc.) may be included. Based on the served cell information, the Donor CU may attach information of cells to be activated to the F1 setup response message and deliver it to the IAB node 3, which is an access IAB node. The information of cells to be activated may include, for example, CGI, PCI, and system information of the cell to be activated, and available PLMN (PLMN) information. Accordingly, the DU may activate a cell indicated by CGI and PCI, and the DU may broadcast system information provided by the CU to the cell. Through this process, the donor CU may acquire information of a cell actually operated in the DU of the access IAB (eg, IAB node 3 of FIG. 8 ).

Additionally, after the F1 interface is established, the donor CU may additionally update DU information of the newly accessed IAB node through the F1 interface. Among the F1 messages, a DU configuration update message may be used. Upon receiving the DU configuration update message, the donor CU may determine and deliver the updated DU configuration information to be finally used to the DU that sent the message. In this process, served cells may be additionally added, modified, or configuration information of served cells may be changed.

Based on the DU information, the donor CU may always manage the latest DU information. Based on the topology of the IAB nodes connected to the donor CU based on the latest DU information, cell information to be excluded when selecting the cell of the IAB node may be delivered to each IAB node managed by the donor CU. Cell information to be excluded when selecting a cell may include the following.

The case where the connection between IAB nodes fails may include the following cases.

- When the IAB node detects RLF in the link with the parent node

- When the IAB node receives a recovery failure notification from the parent node

Information on cells excluded for each failure case may include the following information.

- NR ARFCN (Absolute Radio Frequency Channel Number): information on the frequency in which the excluded cell exists

- PCI: physical cell id of the excluded cell

The excluded cell information may be for multiple cells. Excluded cell information mentioned below may mean an indicator in each failure case and list information of NR ARFCN and PCI bundles associated therewith.

As an example, when the IAB node detects an RLF, cell information excluded from the IAB node may be a lower IAB node (ie, a child IAB node) of the IAB node that detected the RLF. As another example, when the IAB node receives the RLF recovery failure notification from the parent node, the excluded cell information is not only its own child IAB node (child IAB node), but also the parent node that has transmitted the RLF recovery failure notification and its parent node It can also include child nodes of The excluded cell information may be determined by the donor CU in consideration of the overall topology and the relative position/signal strength.

As an example, excluded cell information may be transmitted from the donor CU through an RRCReconfiguration (b) message or a corresponding RRC message. As another example, the excluded cell information can be delivered to each IAB node through a message on the F1-AP (Application Protocol). As another example, the child nodes of each IAB node may directly transmit cell information to the parent node. When the child nodes of each IAB node directly transmit cell information to the parent node, a BAP layer signal may be used. In this case, only cell exclusion to child nodes can be performed.

The IAB nodes that have received the message including the excluded cell information detect RLF in the link with the parent node or receive an RLF recovery failure notification from the parent node, Cell information may be used to select a cell other than the excluded cell, and an RRCreestablishment operation may be performed.

9 is a flowchart illustrating an operation method of an IAB node attempting initial access according to an embodiment of the present disclosure.

The IAB MT (Mobile Termination) establishes an RRC connection with the Donor CU.

The CU may allocate BAP configuration information and an IP address used for the corresponding IAB node DU through the RRCreconfiguration message, and the IAB node may acquire at least one of the BAP configuration information and the allocated IP address.

The IAB node may set up a BAP entity (setup) and establish a (default) BH RLC channel ((default) BH RLC CH). The IAB node may request the F1 setup request from the CU by using the information obtained from the CU.

The CU may receive the F1 setup request and transmit an F1 setup response message to confirm the configuration information on the serving cell of the DU to the DU. F1 establishment can be completed through the above process.

Additionally, when the DU requests an update of the DU configuration information, there may be a process for the CU to confirm.

After the donor CU recognizes the DU configuration information of the first connected IAB node, the donor CU receives failure case information (eg, RLF detection, RLF recovery failure notification) through the RRC reconfiguration message. case), and cell information (NR ARFCN (Absolute Radio Frequency Channel Number), PCI) excluded in each case may be delivered to each IAB node. In this case, the same information may be delivered through the F1-AP message.

IAB nodes that have received information from the donor CU may detect RLF or receive RLF recovery failure notification, and in each case, may perform cell selection while excluding each cell based on excluded cell information. .

For example, IAB nodes, using the RRC message received from the donor CU, when detecting RLF or receiving a recovery failure notification from the parent node, information on cells to be excluded from each cell selection can receive

IAB nodes, when detecting RLF or receiving a recovery notification failure from a parent node, check whether the cause is RLF detection or receipt of a recovery notification failure notification, and exclude a cell according to each case from the received cell exclusion information It can be used for the purpose of Additionally, in the above process, in the case of recovery notification failure, information on the cell in which the parent node detected the RLF, ie, ARFCN and PCI, may be added to the recovery failure notification and delivered to the child IAB node. The child node may additionally exclude the delivered RLF-detected cell from cell selection, in addition to excluded cell information, if necessary.

During the cell selection operation, the IAB node may exclude a corresponding cell based on the cell exclusion information received in the above-described step. When the IAB node reads SSB (Synchronization Signal Block) and performs measurement, ARFCN (Absolute Radio Frequency Channel Number) information where SSB is located and PCI (Physical layer Cell ID) information included in SSB are previously received. If the excluded cell information matches, another cell may be selected without performing an additional cell selection process of reading SIB1 of the corresponding cell.

10 is a diagram illustrating a method for the donor CU to update excluded cell information of each IAB node when the IAB node makes RRC connection with the donor CU again after a HO (hand over) or reestablishment operation according to an embodiment of the present disclosure; Show the flow chart.

Compared to the initial access process illustrated in FIG. 9 , a process in which the IAB MT receives a HO command or performs RRC Connection Re-establishment (RRE) may be added. After that, the process of the donor CU recognizing the BAP establishment, BAP establishment, F1 establishment, and DU configuration information corresponds to the description described above with reference to FIG. 9 , and thus a redundant description will be omitted.

11 is a flowchart illustrating a cell exclusion operation of an IAB node in a terminal failure situation according to an embodiment of the present disclosure.

IAB node 2 (11-5) may be RRC-connected to the IAB donor CU through the cell of the IAB node 1 (11-10) (11-20). IAB node 2 (11-5) may receive the cell exclusion information through the system information (11-25) or through the RRC dedicated message (11-30). When failure occurs while in the connected state, IAB node 2 may perform RRC re-establishment using the given cell exclusion information (11-35). Failure situations, for example, may include failure situations recognized at the RRC level, such as radio link failure, RLC failure, reconfiguration failure, integrity check failure, handover failure. In addition, the case where the IAB node receives the RLF recovery failure notification from the parent IAB node may also be included in the failure situation.

As a sub-operation of the re-establishment operation, the IAB node 2 ( 11-5 ) may perform cell selection ( 11-40 ). According to the existing method for cell selection, when the IAB node 2 (11-5) uses stored information, the information of the previously given carrier frequency, the cell information stored by the previously given measurement control, and the existing If the cell found using at least one of the detected cell information passes a suitability check, the IAB node 2 11-5 may select the corresponding cell.

In the present disclosure, the above-mentioned cell exclusion information has already been delivered through an RRC dedicated message or a System Information Block (SIB) and/or a Master Information Block (MIB) message, and the information of the cell is IAB node 2 (11-5) It is assumed to be stored in IAB node 2 (11-5), based on the transmitted cell information, if the cell selected according to the existing cell selection operation is a cell corresponding to the cell exclusion information, the cell may be excluded. Criteria for determining whether the cell corresponds to whether the cell is selected due to a failure condition included in the cell exclusion information and whether the frequency information and physical cell identity (PCI) among the cell exclusion information associated with the failure condition are the same may be a criterion. When the cell selected according to the existing cell selection operation is the same as the cells corresponding to the cell exclusion information, the IAB node 2 (11-5) may reselect other cells excluding the cell selected according to the existing cell selection operation.

IAB node 2 (11-5), after going through the cell exclusion process, can find the selected cell again (11-40). IAB node 2 (11-5) can read the cell selection information of the SIB and / or MIB of the selected cell (11-15) again (11-45). IAB node 2 (11-5) may perform a suitability check (suitability check) (11-50). The IAB node 2 (11-5) may perform a suitability check (11-50) using the values in the SIB from the cell (11-15) after cell exclusion (11-50). If the conformance check is passed, the IAB node 2 (11-5) may perform synchronization (synchronization) with the corresponding cell (11-15) (11-60). IAB node 2 (11-5) may transmit an RRC connection re-establishment request (11-60). The selected cell 11-15 may check whether it has a terminal context, and if so, may transmit a re-establishment message to the RRC connection IAB node 2 11-5 (11-65). IAB node 2 (11-5) may transmit an RRC connection re-establishment complete message in response to the RRC connection re-establishment message (11-70).

QrxlevIABcell QqualIABcell information may not be included in the cell selection parameter received from the system information received from the cell 11-15 selected by the IAB node 2 11-5 in steps 11-45. If the cell selection parameter does not include QrxlevIABcell QqualIABcell information, IAB node 2(11-5) evaluates the cell selection criteria using the existing cell selection factors when performing the conformance check, and performs the conformance check. can If QrxlevIABcell QqualIABcell information is included in the system information received by the IAB node 2 11-5 in steps 11-45, the IAB node 2 11-5 performs a conformance check using the received information. can do.

As another embodiment, if the IAB node receives an RLF detection or RLF recovery failure notification from the parent IAB node, the IAB node receiving the RLF detection or RLF recovery failure notification mutes the iab-support indicator in SIB1 in the DU. can In this case, the IAB MT performing cell selection in the vicinity reads the corresponding SIB1, knows that there is no iab-support, and cannot select a cell with the corresponding cell. That is, cell selection to the corresponding cell may be barred. In the following description, "RLF detection indication" may have the same meaning as the indicator "RLF recovery".

In this regard, specifically, when any IAB node detects the RLF, if the CG (Cell Group) for each link is not distinguished, or the corresponding IAB node may perform the MCG (Master Cell Group) failure information procedure. If there is, the following operations are possible.

- When an IAB node detects (or declares) RLF for a link with one parent node and there is an available link with another parent node (that is, when the link with another parent node is not in RLF or in radio bearer suspension) ) Do not deliver RLF detection indication to child nodes.

- When the IAB node detects RLF for a link with one parent node and there is no link available with another parent node (that is, if there is a link with another parent node, it is RLF, RLF recovery state, or radio bearer suspension state, or When the RRCReestablishment procedure is started), an RLF detection indication may be delivered to the child node.

If the CG is classified for each link, and the IAB node cannot perform the MCG failure information procedure, the following operation is possible.

- In the state in which the IAB node is set up with dual connection, when RLF is detected for the SCG (Secondary Cell Group) link, and when the MCG link is not in the RLF situation or radio bearer suspension situation, the RLF detection indication is not delivered to the child node.

- When the IAB node detects RLF for the MCG link in a state in which dual connection is established (or when the RRCReestablishment procedure is started), the RLF detection indication may be delivered to the child node regardless of the state of the SCG link.

- When the IAB node detects the RLF for the MCG link in the single connection setup state (or the SCG configuration is not set), the RLF detection indication may be delivered to the child node.

In this regard, the IAB node that delivered the RLF detection indication to the child node may deliver the RLF recovery success indication to the child IAB node that delivered the existing RLF detection indication in the following case.

- When the RLF recovery operation is successful in a single connection situation, that is, RRC Reestablishment is successful (eg, the RRCReestablishmentComplete message is successfully transmitted to a new target cell), or If the RRCReconfigurationComplete message is successfully sent to the new target cell, given the attemptCHO configuration.

When the RLF detection indication is delivered to the child node in the dual connection situation by oneself (eg, the IAB node that has written and delivered the RLF detection indication), the RRC Reestablishment procedure is successfully completed (when the atemptCHO setting is not given to itself), Or when transmitting RRCReconfigurationComplete to the newly selected cell (when the atemptCHO setting is given to itself)

The child IAB node receiving the RLF detection indication may mutate the iab-support indication that was being transmitted through SIB1 in cells being served by the DU of the child IAB node. That is, the child IAB node may not transmit an iab-support indication.

Specifically, if CG is not distinguished, the IAB node that has received the RLF detection indication is,

- Case a: If there is a link with another parent node other than the link on which the RLF detection indication has been received, and there is no problem in the link with the other parent node, iab transmitted in SIB1 of the cells being served by the DU of the IAB node that has received the RLF detection indication You can mutate the -support directive. In this case, the IAB node performing cell selection in the vicinity, including the IAB node that has delivered the RLF detection indication, cannot select the cell of the muted IAB DU.

- Case b: If there is a link with another parent node other than the link on which the RLF detection indication has been received, and there is no problem in the link with another parent node, the iab-support indication broadcast in SIB1 of the cells being served in the DU is broadcast or maintained. can In this case, the IAB node performing cell selection in the vicinity including the IAB node that has delivered the RLF detection indication may select a cell being served in the DU of this IAB node due to the broadcast indicator.

- Case c: If there is a problem in the link with another parent node other than the link on which the RLF detection indication has been received or there is no link with another parent node, the iab-support indication broadcast in SIB1 of the cells being served in the DU can be muted. In this case, the IAB node performing cell selection in the vicinity, including the IAB node that has delivered the RLF detection indication, cannot select the cell of the muted IAB DU.

In the case of CG classification, the IAB node receiving the RLF detection indication is,

- Case a: If the link on which the RLF detection indication is received is SCG, the iab-support indication transmitted in SIB1 of the cells being served in the DU may be muted. In this case, the IAB node performing cell selection in the vicinity, including the IAB node that has delivered the RLF detection indication, cannot select the cells of the muted IAB DU.

- Case b: If the link receiving the RLF detection indication is SCG, the iab-support indication transmitted in SIB1 of the cells being served in the DU may be broadcast or maintained. In this case, the IAB node performing cell selection in the vicinity including the IAB node that has delivered the RLF detection indication may select the cell of the DU of this IAB node due to the broadcast indicator.

- Case c: If the link receiving the RLF detection indication is MCG,

■ If the IAB node that has received this RLF detection indication is in a DC configuration state, if the MCG failure information procedure is possible, and the SCG link is not in RLF or radio bearer suspension state,

◆ The iab-support indication transmitted in SIB1 of the cells being served by the DU of the IAB node that has received the RLF detection indication may be broadcast or maintained.

■ Except for the above conditions,

◆ It is possible to muting the iab-support indication transmitted in SIB1 of the cells being served in the DU of the IAB node that has received the RLF detection indication.

According to at least one operation described above, when the iab-support indication transmitted in SIB1 of the DU is muted, the IAB node must maintain the muting until it receives the RLF recovered indication from the parent node that has received the RLF detection indication. If the IAB node receives RLF recovery failure (or RLF notification indicator) from the parent node that received the RLF detection indication before receiving the RLF recovered indication, it may maintain muting or re-broadcast the iab-support indication.

The RLF detection indication / RLF recovered indication, etc. may be delivered using a BAP control plane signal or MAC CE.

Only one of case a and case b in the process of muting the IAB-support indication in the DU is possible. In case a, the parent IAB node that has delivered the RLF detection indication may perform cell selection and connection setup as a child node again to the child node that has received the RLF detection indication according to the result of cell selection.

As another embodiment of muting the IAB-support indication (or IAB-support bit), when receiving the RLF recovery failure notification from the parent IAb node, the IAB node receiving the RLF recovery failure notification is the IAB broadcast in SIB1 -support indication (or, IAB-support bit) can be muting.

According to an embodiment of the present disclosure, when an IAB node detects an RLF, it transmits an RLF detection notification to a child node of the node, and the child node receiving the notification may perform a mobility operation.

12 shows an example of a topology according to an embodiment of the present disclosure.

IAB node 1, parent node, and child node may be connected to the IAB donor CU by multiple hops. When the parent node is connected to IAB node 1 by a single connection and RLF is detected, RLF detection notification may be delivered to the child node. A child node that has received the RLF detection notification may move to find another cell (eg, a cell in another IAB node).

13 is a diagram for explaining an operation between a general IAB node and an access terminal.

When the parent IAB node detects RLF and performs recovery, if recovery finally fails, the parent IAB node may deliver an RLF recovery failure notification to the child IAB node. Upon receiving the RLF recovery failure notification, the child IAB node performs the RLF recovery operation by itself. The DU part of the child node may perform various UL/DL data transmission/reception and may operate variously depending on implementation after receiving a notification.

14 is a diagram for explaining an operation between an IAB node and an access terminal according to an embodiment of the present disclosure.

When the parent IAB node detects the RLF, the parent IAB node may transmit an RLF detection notification signal to the child node. The following information may be added to the RLF detection notification signal.

Information included in RLF detection notification:

- RLF type: RLF type is information on the cause of RLF

- Type of link where RLF occurred (eg, MCG (Master Cell Group) / SCG (Secondary Cell Group))

- Information on the operation used for RLF recovery in the IAB node that has detected the RLF (eg, only RRCreestablishment, attemptCHO, MCGFailureInformation, SCGFailureInformation, or a combination of the above operations and RRE.)

- RLF detected cell/node information (eg, node's BAP address, cell's PCI/frequency)

- timer: When the timer expires, the IAB node may perform a specific mobility procedure. The mobility procedure will be described later.

The RLF detection notification message may be transmitted as a control PDU of the BAP layer. However, it may also be transmitted as an RRC message through the donor CU.

The child IAB node receiving the RLF detection notification may perform the following operation.

[When RLF detection notification is received]

BAP layer:

If there is only a connection with the parent IAB node that has delivered the RLF detection notification on the routing entry of the BAP (or if there is no possible path other than the routing entry through the parent IAB node), the child IAB node is the RLF The UL BAP PDU may be stored in a buffer without transmitting the UL BAP PDU to the parent IAB node that has transmitted the detection notification. And the child IAB node can associate the buffered data with the BAP address of the parent node.

If another path exists, the child IAB node can rerouting and transmit the BAP PDU to the backup path so that it can go to another parent node. The child IAB node may rerouting the BAP PDU to be delivered to the parent IAB node by using a backup path in routing.

RRC layer:

The child IAB node may perform the mobility procedure. The child IAB node can perform a mobility operation using a predefined operation because the RRC connection with the donor CU is disconnected.

The child IAB node may perform one of the following operations.

- Add conditional SCG (Secondary Cell Group)

- Conditional Hand Over (CHO)

- If a candidate cell is selected after cell selection, conditional handover to the candidate cell

- Perform cell selection only

For each of the above-described operations, the following sub-operations may be required.

An operation required for conditional SCG addition according to an embodiment is as follows.

The donor CU may transmit condition information for adding SCG and SCG configuration information to the IAB node in advance in the connected state.

Conditions for adding SCG may include measurement configuration information based on A3/A4/A5 for the target pscell and a condition that an RLF detection notification is received.

The donor CU may request SCG configuration information from the target parent IAB node, receive SCG configuration information, and deliver it to the child IAB node.

The IAB node, which has received the SCG configuration information and the condition for adding the SCG, evaluates the condition, adds a cell of the SCG corresponding to the given SCG configuration when the condition is satisfied, and can start transmitting and receiving data to the cell. .

Conditional handover:

In the connected state, the donor CU may transmit target cell configuration information for handover to the target candidate cell and condition information for selecting the target cell in advance to the IAB node.

As a condition for selecting a target cell, the donor CU may deliver a measurement id associated with a report type based on A4 to ensure the connection quality of the target pcell, and other “RLF detection notification received from the parent IAB node” You can pass an directive to use as a condition.

In particular, the measurement id may be associated with a specific candidate target cell, and is also associated with target cell configuration information of the specific candidate target cell.

When condition information for selecting a target cell and target cell configuration information are received in advance, the child IAB node may perform measurement based on the measurement id, which is condition information of the candidate target cell. During measurement, if a cell satisfying the measurement condition of the candidate target cell is found in a situation where an RLF detection notification is received, the child IAB node may perform handover to one of the target cells satisfying the condition.

attemptCHO:

The child IAB node may receive and store target cell configuration information for conditional handover in a connected state.

When RLF detection notification is received from the parent node, the child IAB node performs cell selection, and if the selected cell is one of the target cells for conditional handover given in advance, handover is performed using the configuration information of the target cell. can be done

Perform cell selection only:

When RLF detection is received from the parent node, the child IAB node may select a specific cell by performing cell selection. After receiving the RLF recovery failure notification, the child IAB node may perform the remaining operations of RRC reestablishment with the selected cell.

The above-described operations and timer operations may be linked.

If there is a timer value included in the RLF detection notification, the child IAB node may start the timer from the time when the RLF detection notification is received. When the timer expires, the child IAB node may perform one of the given mobility operations. If the child IAB node receives an RLF success notification from the parent IAB node before the timer expires, it may resume operation with the existing parent IAB node without performing mobility operations. In this case, the BAP may transmit the previously buffered UL BAP PDUs to the recovered parent IAB node, and the RRC may stop the timer in operation.

In addition, when the child IAB node determines that the ingress link that has previously received the RLF detection notification is unavailable, and receives the RLF recovery success notification, it recognizes the corresponding ingress link as available and performs an available link (or next hop) for routing operation. As such, the corresponding ingress link can be reflected.

OPT2. According to an embodiment, if there is no other path other than the path through the parent IAB node, the child IAB node may perform one of the following operations.

- Use conditional SCG addition

- Conditional handover (CHO): to one of preconfigured CHO candidates which has higher than A4 threshold(no serving cell condition, no A3)

- attempt CHO

- Perform only cell selection except the current serving cell without any further HO without additional handover

Selection of the above-described option may be determined or fixed according to information received in the RLF detection notification.

OPT3. If a timer is given in the RLF detection notification, when the timer expires, the mobility solution in OPT2 may be triggered.

[If the operation of the child IAB node ends first before receiving a success notification from the parent node]

BAP:

If there are buffered UL BAP PDUs, the child IAB node may transmit the buffered UL BAP PDUs to the new parent node in the BAP and resume communication.

RRC:

The child IAB node can additionally apply BAP establishment and configuration. The child IAB node may follow the handover procedure and additional BAP/IP address configuration (follow HO procedure and further BAP/IP address configuration).

Criteria for the parent IAB node to determine recovery success may include at least one of the following criteria. At least one of the following criteria may be required to define recovery success.

- Reception of RRCreestablishment

- Transmission of RRCreestablishmentComplete

- RRCreconfiguration received after RRC reestablishment

- Successful transmission of RRCreconfigurationComplete to the target cell after conditional handover (receiving ack feedback of RRCreconfigurationComplete)

- attemptCHO success (ACK feedback of RRCreconfigurationcomplete)

- For MCGFailureInformation, HO complete

- For SCGFailureInformation, HO complete

- After the RRC operation (or in the middle of operation), receive (newly) BAP configuration through RRC or F1-AP

- After receiving the BAP setting, an IAB IP address is assigned

Additionally, the following information may be further included in the recovery success notification message that the parent IAB node can deliver.

- Node information that has previously given RLF detection notification, that is, its own information (BAP address)

- In addition, after successful recovery, BAP configuration information newly configured from the donor CU (eg, BAP configuration information, new BAP address, BH RLC CH configuration information, routing information, and IP address assigned to DU and / TNL linkage) information, etc.)

In the specific embodiments of the present disclosure described above, elements included in the invention are expressed in the singular or plural according to the specific embodiments presented. However, the singular or plural expression is appropriately selected for the context presented for convenience of description, and the present disclosure is not limited to the singular or plural element, and even if the element is expressed in plural, it is composed of the singular or singular. Even an expressed component may be composed of a plurality of components.

Meanwhile, although specific embodiments have been described in the detailed description of the present disclosure, various modifications are possible without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments and should be defined by the claims described below as well as the claims and equivalents.

Methods according to the embodiments described in the claims or specifications of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

When implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. One or more programs stored in the computer-readable storage medium are configured to be executable by one or more processors in an electronic device (device). One or more programs include instructions for causing an electronic device to execute methods according to embodiments described in a claim or specification of the present disclosure.

Such programs (software modules, software) include random access memory, non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable ROM (EEPROM: Electrically Erasable Programmable Read Only Memory), magnetic disc storage device, Compact Disc-ROM (CD-ROM), Digital Versatile Discs (DVDs), or any other form of It may be stored in an optical storage device or a magnetic cassette. Alternatively, it may be stored in a memory composed of a combination of some or all thereof. In addition, each configuration memory may be included in plurality.

In addition, the program is transmitted through a communication network composed of a communication network such as the Internet, Intranet, Local Area Network (LAN), Wide LAN (WLAN), or Storage Area Network (SAN), or a combination thereof. It may be stored on an attachable storage device that can be accessed. Such a storage device may be connected to a device implementing an embodiment of the present disclosure through an external port. In addition, a separate storage device on the communication network may be connected to the device implementing the embodiment of the present disclosure.

In the specific embodiments of the present disclosure described above, components included in the disclosure are expressed in the singular or plural according to the specific embodiments presented. However, the singular or plural expression is appropriately selected for the context presented for convenience of description, and the present disclosure is not limited to the singular or plural element, and even if the element is expressed in plural, it is composed of the singular or singular. Even an expressed component may be composed of a plurality of components.

Meanwhile, although specific embodiments have been described in the detailed description of the present disclosure, various modifications are possible without departing from the scope of the present disclosure. Therefore, the scope of the present invention should not be limited to the described embodiments and should be defined by the claims described below as well as the claims and equivalents. That is, it will be apparent to those of ordinary skill in the art to which the present disclosure pertains that other modifications may be made based on the technical spirit of the present disclosure. In addition, each of the above embodiments may be operated in combination with each other as needed. For example, a base station and a terminal may be operated by combining parts of the methods proposed in the present disclosure. In addition, although the above embodiments have been presented based on 5G and NR systems, other modifications based on the technical idea of the embodiments may be implemented in other systems such as LTE, LTE-A, and LTE-A-Pro systems.

Claims (1)

In a communication method of a combined access backhaul node (IAB node, Integrated Access Backhauled node) in a wireless communication system,
Receiving an RRCreconfiguration message from an IAB donor central unit (CU);
identifying failure case information and excluded cell information included in the RRCreconfiguration message; and
When RLF (Radio Link Failure) is detected in connection with the parent node, or when a recovery failure notification is received from the parent node, performing cell selection based on the identified information. How to include.

Images