Fault information of wireless relay network

By establishing dual connections between the wireless node and the radio access network, and utilizing the wireless relay node to detect and transmit fault information, the weak signal problem of the wireless backhaul link in the cellular mobile communication system is solved, thereby improving the system's reliability and stability.

CN113796115BActive Publication Date: 2024-11-26SHARP KK
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202080032894.6
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2019-05-02
Filing Date
2020-04-28
Publication Date
2024-11-26
Estimated Expiration
2040-04-28

AI Technical Summary

Technical Problem

In cellular mobile communication systems, the wireless backhaul link between the base station and the core network is prone to performance problems caused by weak signals, such as reduced data rates and link failures. Existing technologies are unable to effectively solve these problems.

Method used

By establishing dual connections between the wireless node and the radio access network, the wireless relay node detects radio link failures and transmits failure information messages through the second connection, enabling the wireless access node to perform appropriate reconfiguration and switching, thus ensuring communication stability.

Benefits of technology

It effectively solved the problem of faults on the wireless backhaul link, improved the reliability and stability of the system, and ensured the continuity and quality of data transmission.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113796115B_ABST
    Figure CN113796115B_ABST
Patent Text Reader

Abstract

The present invention discloses a wireless node, which communicates with a wireless access node of a radio access network (RAN) through a radio interface, and the wireless node includes: a processor circuit, which is configured to establish a dual connection (DC) with the wireless access node, including a first connection and a second connection, wherein the first connection is relayed by an integrated access and backhaul (IAB) node; a receiver circuit, which is configured to receive a notification message indicating a radio link failure (RLF) on the first connection from the IAB node, and; a transmitter circuit, which is configured to transmit a fault information message to the wireless access node using the second connection based on the notification message, wherein: the fault information message includes information indicating the RLF.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present technology relates to wireless communications, and in particular to radio architecture and operations for resolving problematic conditions of wireless backhaul links. Background Art

[0002] The radio access network typically resides between a wireless device (such as a user equipment (UE), a mobile phone, a mobile station, or any other device with a wireless terminal) and the core network. Examples of radio access network types include: GRAN, which is the GSM radio access network; GERAN, which includes EDGE packet radio service; UTRAN, which is the UMTS radio access network; E-UTRAN, which includes long term evolution; and g-UTRAN, which is new radio (NR).

[0003] The radio access network may include one or more access nodes, such as base station nodes, which facilitate wireless communications or otherwise provide an interface between a wireless terminal and a telecommunications system. Non-limiting examples of base stations may include Node B ("NB"), enhanced Node B ("eNB"), Home eNB ("HeNB"), gNB (for New Radio ["NR"] technology systems), or some other similar terminology, depending on the radio access technology type.

[0004] The 3rd Generation Partnership Project ("3GPP") is a group that develops collaborative agreements, such as 3GPP standards, that are intended to establish globally applicable technical specifications and technical reports for wireless communication systems. Various 3GPP documents may describe certain aspects of radio access networks. The overall architecture of fifth generation systems (e.g., 5G systems, also referred to as "NR" or "new radio", and "NG" or "next generation") is described in Fig.33 , and is also described in 3GPP TS 38.300. The 5G NR network consists of NGRAN (Next Generation Radio Access Network) and 5GC (5G Core Network). As shown in the figure, NGRAN consists of gNB (e.g., 5G base station) and ng-eNB (i.e., LTE base station). The Xn interface exists between gNB-gNB, between (gNB)-(ng-eNB), and between (ng-eNB)-(ng-eNB). Xn is a network interface between NG-RAN nodes. Xn-U represents the Xn user plane interface, and Xn-C represents the Xn control plane interface. The NG interface exists between 5GC and base stations (i.e., gNB and ng-eNB). The gNB node provides NR user plane and control plane protocol terminals to the UE and is connected to the 5GC via the NG interface. The 5G NR (New Radio) gNB is connected to the AMF (Access and Mobility Management Function) and UPF (User Plane Function) in the 5GC (5G Core Network).

[0005] In some cellular mobile communication systems and networks such as Long Term Evolution (LTE) and New Radio (NR), the service area is covered by one or more base stations, each of which can be connected to the core network via a fixed line backhaul link (e.g., a fiber optic cable). In some cases, due to the weak signal from the base station at the edge of the service area, users often encounter performance problems such as: reduced data rate, high probability of link failure, etc. The concept of relay nodes has been introduced to extend the coverage area and improve signal quality. As implemented, the relay node can be connected to the base station using a wireless backhaul link.

[0006] In the 3rd Generation Partnership Project (3GPP), the concept of relay nodes for fifth generation (5G) cellular systems has been discussed and standardized, where relay nodes can use the same 5G radio access technology (e.g., New Radio (NR)) to simultaneously provide services to user equipment (UE) (access link) and connect to the core network (backhaul link). These radio links can be multiplexed in time, frequency and / or space. This system can be called integrated access and backhaul (IAB).

[0007] Some such cellular mobile communication systems and networks may include an IAB bearer and an IAB node, wherein the IAB bearer may provide an interface to the core network for the UE and provide the IAB node with a wireless backhaul function; and in addition, the IAB node may provide the IAB function in combination with the wireless self-backhaul capability. The IAB node may need to periodically perform IAB inter-node discovery to detect new IAB nodes in its vicinity based on cell-specific reference signals (e.g., synchronization signals and PBCH block SSBs). The cell-specific reference signal may be broadcast on a physical broadcast channel (PBCH), where packets may be carried or broadcast on a master information block (MIB) section.

[0008] The demand for wireless traffic has increased significantly over time, and the IAB system is expected to be able to handle a variety of possible failures reliably and robustly. For the IAB backhaul design, these factors have been taken into account. In particular, methods and procedures for resolving radio link failures on the backhaul link are provided.

[0009] What are needed are methods, apparatus, and / or techniques to address adverse conditions or problems on wireless backhaul links. Summary of the invention

[0010] In one example, a wireless node is disclosed that communicates with a radio access node of a radio access network (RAN) via a radio interface, the wireless node comprising: a processor circuit configured to establish a dual connection (DC) with the radio access node comprising a first connection and a second connection, the first connection being relayed by an integrated access and backhaul (IAB) node; a receiver circuit configured to receive a notification message indicating a radio link failure (RLF) on the first connection from the IAB node, and; a transmitter circuit configured to transmit a fault information message to the radio access node using the second connection based on the notification message, wherein: the fault information message includes information indicating the RLF.

[0011] In one example, a method for a wireless node is disclosed, which communicates with a wireless access node of a radio access network (RAN) via a radio interface, the method comprising: establishing a dual connection (DC) with the radio access node comprising a first connection and a second connection, the first connection being relayed by an integrated access and backhaul (IAB) node; receiving a notification message indicating a radio link failure (RLF) on the first connection from the IAB node; based on the notification message, transmitting a failure information message to the wireless access node using the second connection; wherein the failure information message includes information indicating the RLF.

[0012] In one example, a wireless access node of a radio access network (RAN) is disclosed, which communicates with a wireless node via a radio interface, the wireless access node comprising: a processor circuit configured to establish a dual connection (DC) with the wireless node comprising a first connection and a second connection, the first connection being relayed by an integrated access and backhaul (IAB) node, and; a receiver circuit configured to receive a fault information message on the second connection; wherein the fault information message is based on a notification message received by the wireless node from the IAB node, the notification message indicating a radio link failure (RLF) on the first connection, and; the fault information message includes information representing the RLF.

[0013] In one example, a method is disclosed for a wireless access node of a radio access network (RAN), which communicates with a wireless node via a radio interface, the method comprising: establishing a dual connection (DC) with the wireless node comprising a first connection and a second connection, the first connection being relayed by an integrated access and backhaul (IAB) node, and; receiving a fault information message on the second connection; wherein the fault information message is based on a notification message received by the wireless node from a wireless relay node, the notification message indicating a radio link failure (RLF) on the first connection, and; the fault information message includes information representing the RLF. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] The foregoing and other objects, features, and advantages of the technology disclosed herein will be apparent from the following more particular description of preferred embodiments as illustrated in the accompanying drawings, in which reference numerals refer to the same parts in the various views. The accompanying drawings are not necessarily drawn to scale, emphasis instead being placed on illustrating the principles of the technology disclosed herein.

[0015] Figure 1 is a diagrammatic view showing a mobile network infrastructure using 5G signals and 5G base stations.

[0016] Figure 2 is a diagrammatic view depicting an example of a functional block diagram of an IAB bearer and an IAB node.

[0017] Figure 3 is a diagrammatic view showing the control plane (C-plane) and user plane (U-plane) protocols between the UE, IAB node and IAB bearer.

[0018] Figure 4 is a functional block diagram of an exemplary protocol stack configuration of the U-plane.

[0019] Figure 5A A functional block diagram depicts an exemplary protocol stack configuration for a C-plane between IAB nodes connected to an IAB bearer.

[0020] Figure 5B Depicted is a functional block diagram of an exemplary C-plane protocol stack configuration of an IAB node connected to another IAB node connected to an IAB bearer.

[0021] Figure 5C A functional block diagram depicts an exemplary C-plane protocol stack configuration for RRC signaling of a UE.

[0022] Fig. 6A Depicted is an exemplary message sequence for an IAB node to establish an RRC connection followed by an F1-AP* connection.

[0023] Figure 6B An exemplary message sequence for an IAB node to establish an RRC connection with an IAB bearer followed by an F1 setup procedure is depicted.

[0024] Figure 7 is a diagrammatic view of an exemplary scenario in which an IAB node detects a radio link failure (RLF) on an upstream link to its parent node.

[0025] Figure 8An exemplary flow of information transmission / reception and / or processing by a UE and / or an IAB node to handle a notification of RLF is shown, wherein the UE and / or the IAB node is connected to a group of IAB nodes in communication with an IAB bearer.

[0026] Fig.9A An exemplary flow of information transmission / reception and / or processing by a UE and / or an IAB node based on receiving an upstream RLF notification is shown, wherein the UE and / or the IAB node is connected to a group of IAB nodes in communication with an IAB bearer.

[0027] Fig. 9B Another exemplary flow of information transmission / reception and / or processing by a UE and / or an IAB node based on not having received an upstream RLF notification is shown, the UE and / or the IAB node being connected to a group of IAB nodes in communication with an IAB bearer.

[0028] Fig.10 is a diagrammatic view showing an example of a radio protocol architecture for a control plane and a user plane in a mobile communication network.

[0029] Fig.11 is a diagrammatic view illustrating another example diagram of a telecommunications system that may perform conditional autonomous handover to address wireless link backhaul conditions.

[0030] Fig.12 It is shown Fig.11 A diagrammatic view of an exemplary, non-limiting, more detailed implementation of at least a portion of a system.

[0031] Fig.13 It shows that Fig.11 A flowchart of exemplary, non-limiting basic actions or steps performed by a wireless access node in accordance with an embodiment of the present invention.

[0032] Fig.14 It shows that Fig.11 A flowchart of exemplary, non-limiting basic actions or steps performed by the child nodes of .

[0033] Fig.15 Describes the use Fig.11 Exemplary basic representative actions or steps of message flow for the illustrated system scenario.

[0034] Fig.16 is a diagrammatic view of another example diagram of a telecommunications system that illustrates that wireless link backhaul conditions may be addressed when redundant links are used.

[0035] Fig.17 It is shown Fig.16 A diagrammatic view of an exemplary, non-limiting, more detailed implementation of at least a portion of a system.

[0036] Fig.18 It shows that Fig.16 A flowchart of exemplary, non-limiting basic actions or steps performed by a wireless access node in accordance with an embodiment of the present invention.

[0037] Fig.19 It shows that Fig.16 A flowchart of exemplary, non-limiting basic actions or steps performed by the child nodes of .

[0038] Fig. 20A Describes the use Fig.16 Exemplary basic representative actions or steps of the message flow for the first exemplary system scenario are shown.

[0039] Fig. 20B Describes the use Fig.16 Exemplary basic representative actions or steps of the message flow for the first exemplary system scenario are shown.

[0040] Fig.21 is a diagrammatic view showing another example diagram of a telecommunications system that can use information from a conditional handover configuration message and information from a radio condition notification to perform conditional autonomous handover.

[0041] Fig. 22 It is shown Fig.12 A diagrammatic view of an exemplary, non-limiting, more detailed implementation of at least a portion of a system.

[0042] Fig.23A is a diagrammatic representation showing basic relevant parts or information elements of a conditional handover configuration message according to various exemplary implementations.

[0043] Fig. 23B is a diagrammatic representation showing basic relevant parts or information elements of a conditional handover configuration message according to various exemplary implementations.

[0044] Fig.23C is a diagrammatic representation showing basic relevant parts or information elements of a conditional handover configuration message according to various exemplary implementations.

[0045] Fig.23D is a diagrammatic representation showing basic relevant parts or information elements of a conditional handover configuration message according to various exemplary implementations.

[0046] Fig.23E is a diagrammatic representation showing basic relevant parts or information elements of a conditional handover configuration message according to various exemplary implementations.

[0047] Fig.24A It shows that according to Fig.21A graphical illustration of various types of comparisons that may be performed by a handover controller of an integrated access and backhaul (IAB) node, according to various corresponding implementations of a system.

[0048] Fig. 24B It shows that according to Fig.21 A graphical illustration of various types of comparisons that may be performed by a handover controller of an integrated access and backhaul (IAB) node, according to various corresponding implementations of a system.

[0049] Fig.24C It shows that according to Fig.21 A graphical illustration of various types of comparisons that may be performed by a handover controller of an integrated access and backhaul (IAB) node, according to various corresponding implementations of a system.

[0050] Fig.25 It shows that Fig.21 A flowchart of exemplary, non-limiting basic actions or steps performed by a wireless access node in accordance with an embodiment of the present invention.

[0051] Fig.26 It shows that Fig.21 A flowchart of exemplary, non-limiting basic actions or steps performed by the child nodes of .

[0052] Fig. 27 is a diagrammatic view of another example diagram of a telecommunication system showing information of a radio link failure (RLF) being reported to a wireless access node.

[0053] Fig.28 It is shown Fig. 27 A diagrammatic view of an exemplary, non-limiting, more detailed implementation of at least a portion of a system.

[0054] Fig.29A is a diagrammatic representation showing basic relevant parts or information elements of a fault information message according to various exemplary implementations.

[0055] Fig.29B is a diagrammatic representation showing basic relevant parts or information elements of a fault information message according to various exemplary implementations.

[0056] Fig.29C is a diagrammatic representation showing basic relevant parts or information elements of a fault information message according to various exemplary implementations.

[0057] Fig.30 It shows that Fig. 27 A flowchart of exemplary, non-limiting basic actions or steps performed by a wireless access node in accordance with an embodiment of the present invention.

[0058] Fig.31 It shows that Fig. 27A flowchart of exemplary, non-limiting basic actions or steps performed by a wireless node.

[0059] Fig.32 is a diagrammatic view showing exemplary elements comprising an electronic machine that may include a wireless terminal, a radio access node, and a core network node according to exemplary embodiments and modes.

[0060] Fig.33 is a diagrammatic view of the overall architecture of the 5G New Radio system. DETAILED DESCRIPTION

[0061] In one of its exemplary aspects, the technology disclosed herein relates to a wireless node that communicates with a wireless access node of a radio access network (RAN) through a radio interface, and a method of operation of the node. In a basic general exemplary embodiment and mode, the wireless node includes a receiver circuit, a processor circuit, and a transmitter circuit. The receiver circuit is configured to receive at least one reconfiguration message from the wireless access node and receive a notification message indicating a radio link failure (RLF) on a second data path from a wireless relay node. The reconfiguration message is used to activate a first data path and a second data path. The first data path and the second data path are established between the wireless access node and the wireless node, and the second data path is relayed by the wireless relay node. The processor circuit is configured to generate a fault information message based on the notification message and indicating the RLF that occurred on the second data path. The transmitter circuit is configured to transmit the fault information message to the wireless access node using the first data path.

[0062] In another aspect of its exemplary aspects, the technology disclosed herein relates to a radio access node of a radio access network (RAN) that communicates with a wireless node through a radio interface, and a method of operation of the wireless access node. In a basic general exemplary embodiment and mode, the wireless access node includes a processor circuit, a transmitter circuit, and a receiver circuit. The processor circuit is configured to generate at least one reconfiguration message. The transmitter circuit is configured to transmit the at least one reconfiguration message. The receiver circuit is configured to receive a fault information message on a first data path. The fault information message is based on a notification message received by the wireless node from a wireless relay node and indicates a radio link failure (RLF) on a second data path.

[0063] For ease of explanation and not limitation, specific details such as specific architectures, interfaces, technologies, etc. are proposed in the following description so as to thoroughly understand the technology disclosed herein. However, it is obvious to those skilled in the art that the technology disclosed herein can also be implemented in other embodiments different from these specific details. That is, those skilled in the art can conceive of various arrangements, although these arrangements are not explicitly described or shown in this article, they still embody the principles of the technology disclosed herein and are included in its spirit and scope. In some cases, detailed descriptions of well-known devices, circuits, and methods are omitted so that the description of the technology disclosed herein will not be obscure due to unnecessary details. All statements of the principles, aspects, and embodiments of the technology disclosed herein and their specific examples are described herein and are intended to cover their structural and functional equivalents. In addition, it is intended that such equivalents include currently known equivalents and equivalents developed in the future, that is, any element developed to perform the same function, regardless of the structure.

[0064] Thus, for example, those skilled in the art will appreciate that the block diagrams herein can represent conceptual views of exemplary circuits or other functional units that embody technical principles. Similarly, it will be appreciated that any flow charts, state transition diagrams, pseudo codes, etc. represent various processes that can be substantially represented in a computer-readable medium and thus executed by a computer or processor, regardless of whether such a computer or processor is explicitly shown.

[0065] As used herein, the term "core network" may refer to a device, a group of devices, or a subsystem in a telecommunications network that provides services to telecommunications network users. Examples of services provided by the core network include aggregation, authentication, call switching, service invocation, gateways to other networks, etc.

[0066] As used herein, the term "wireless terminal" may refer to any electronic device used to transmit voice and / or data via a telecommunication system, such as, but not limited to, a cellular network. Other terms used to refer to wireless terminals and non-limiting examples of such devices may include user equipment terminal, UE, mobile station, mobile device, access terminal, subscriber station, mobile terminal, remote station, user terminal, terminal, subscriber unit, cellular phone, smart phone, personal digital assistant ("PDA"), laptop computer, tablet computer, netbook, e-reader, wireless modem, etc.

[0067] As used herein, the term "access node," "node," or "base station" may refer to any device or group of devices that facilitates wireless communications or otherwise provides an interface between a wireless terminal and a telecommunications system. In the 3GPP specifications, non-limiting examples of a base station may include a Node B ("NB"), an enhanced Node B ("eNB"), a Home eNB ("HeNB"), a gNB (for New Radio ["NR"] technology systems), or some other similar terminology.

[0068] As used herein, the term "telecommunication system" or "communication system" may refer to any network of devices used to transmit information. Non-limiting examples of telecommunication systems are cellular networks or other wireless communication systems.

[0069] As used herein, the term "cellular network" or "cellular radio access network" may refer to a network distributed over cells, each cell being served by at least one fixed-position transceiver such as a base station. A "cell" may be any communication channel specified by a standardization or regulatory body for advanced international mobile telecommunications ("IMTAdvanced"). All or a portion of a cell may be adopted by 3GPP as a licensed frequency band (e.g., frequency band) to be used for communication between a base station (such as a Node B) and a UE terminal. A cellular network using a licensed frequency band may include configured cells. A configured cell may include a cell that a UE terminal is aware of and is permitted by a base station to transmit or receive information. Examples of cellular radio access networks include E-UTRAN and any successor networks thereof (e.g., NUTRAN).

[0070] Any reference to "resources" herein refers to "radio resources" unless it is clear from the context that another meaning is intended. Generally speaking, as used herein, a radio resource ("resource") is a time-frequency unit that can transmit information (e.g., signal information or data information) over a radio interface. An example of a radio resource occurs in the context of a "frame" of information that is typically formatted and written by a node, for example. In Long Term Evolution (LTE), a frame having one or more downlink parts and one or more uplink parts is transmitted between a base station and a wireless terminal. Each LTE frame may include multiple subframes. For example, in the time domain, a 10ms frame consists of ten one-millisecond subframes. An LTE subframe is divided into two time slots (thus making 20 time slots in a frame). The signal transmitted in each time slot is described by a resource grid consisting of resource elements (REs). Each column of the two-dimensional grid represents a symbol (e.g., an OFDM symbol on a downlink (DL) from a node to a wireless terminal; an SC-FDMA symbol in an uplink (UL) frame from a wireless terminal to a node). Each row of the grid represents a subcarrier. A resource element (RE) is the minimum time-frequency unit used for downlink transmission in a subframe. That is, one symbol on one subcarrier in a subframe includes a resource element (RE) uniquely defined by an index pair (k, l) in a time slot (where k and l are indices in the frequency domain and time domain, respectively). In other words, one symbol on one subcarrier is a resource element (RE). Each symbol includes multiple subcarriers in the frequency domain, and the specific number depends on the channel bandwidth and configuration. The minimum time-frequency resource supported by today's standards is a set of multiple subcarriers and multiple symbols (e.g., multiple resource elements (RE)), and is referred to as a resource block (RB). In the case of a canonical cyclic prefix, a resource block may include, for example, 84 resource elements, i.e., 12 subcarriers and 7 symbols.

[0071] In a mobile network used in a wireless network, the source and destination may be interconnected through multiple nodes. In such a network, the source and destination may not be able to communicate directly with each other because the distance between the source and the destination is greater than the transmission range of the node. That is, an intermediate node is required to relay the communication and provide information transmission. Therefore, an intermediate node can be used to relay information signals in a relay network with a network topology, in which the source and the destination are interconnected through such intermediate nodes. In a hierarchical telecommunication network, the backhaul portion of the network may include an intermediate link between the core network of the entire hierarchical network and a small subnetwork. The integrated access and backhaul (IAB) next generation NodeB uses 5G new radio communications, such as sending and receiving NR user plane (U plane) data traffic and NR control plane (C plane) data. Both UE and gNB may include an addressable memory that communicates electronically with a processor. In one embodiment, instructions may be stored in a memory and executable instructions to process received packets and / or send packets according to different protocols (e.g., a media access control (MAC) protocol and / or a radio link control (RLC) protocol).

[0072] In some aspects of an embodiment for handling radio link failures in a wireless relay network, a mobile terminal (MT) function, typically provided by a user equipment (UE) terminal, is disclosed, which may be implemented by a base station (BTS or BS) node (e.g., an IAB node). In one embodiment, the MT function may include common functions such as: radio transmission and reception, encoding and decoding, error detection and correction, signaling, and access to a SIM.

[0073] In a mobile network, an IAB child node may establish a connection with an IAB node / carrier or parent using the same initial access process (discovery) as an access UE, thereby attaching to a network or pre-occupying a cell. In one embodiment, a radio resource control (RRC) protocol may be used to send signaling notifications between a 5G radio network and a UE, wherein the RRC may have at least two states (e.g., RRC_IDLE and RRC_CONNECTED) and state transitions. The RRC sublayer may enable a connection to be established based on broadcast system information, and may also include security procedures. The U-plane may include PHY, MAC, RLC, and PDCP layers.

[0074] Embodiments of the present system disclose methods and apparatus for an IAB node to notify a child node and / or a UE of upstream radio conditions, and therefore, the term "IAB node" may be used to represent a parent IAB node or a child IAB node, depending on the location of the IAB node in network communications with an IAB carrier responsible for making a physical connection with a core network. The present invention discloses embodiments in which an IAB node (child IAB node) may follow the same initial access process as a UE, including cell search, system information acquisition, and random access, in order to initially establish a connection with a parent IAB node or an IAB carrier. That is, when an IAB base station (eNB / gNB) needs to establish a backhaul connection to a parent IAB node or an IAB carrier or to pre-occupy a parent IAB node or an IAB carrier, the IAB node may perform the same process and steps as a UE, wherein the IAB node may be regarded as a UE, but the parent IAB node or IAB carrier distinguishes the IAB node from the UE.

[0075] In the embodiments disclosed in the present invention for handling radio link failures in a wireless relay network, the MT function usually provided by the UE can be implemented on the IAB node. In some examples of the disclosed system, method and device embodiments, it can be considered to enable the child IAB node to monitor the radio conditions on the radio link to the parent IAB node, wherein the parent IAB node itself can be a child IAB node communicating with the IAB bearer.

[0076] refer to Figure 1 , the present embodiment includes a mobile network infrastructure using 5G signals and 5G base stations (or cell sites). A system diagram of a radio access network utilizing an IAB node is depicted, wherein the radio access network may include, for example, one IAB carrier and multiple IAB nodes. Different embodiments may include different numbers of IAB carriers and IAB node ratios. In this article, the IAB node may be referred to as an IAB relay node. The IAB node may be a radio access network (RAN) node that supports wireless access to UEs and wireless backhaul of access traffic. The IAB carrier may be a RAN node that may provide an interface to the core network to the UE and provide wireless backhaul functionality to the IAB node. The IAB node / carrier may serve one or more IAB nodes using a wireless backhaul link and simultaneously serve the UE using a wireless access link. Therefore, the network backhaul traffic state may be realized based on a wireless communication system connected to multiple IAB nodes and UEs.

[0077] Further references Figure 1, multiple UEs are depicted as communicating with IAB nodes (e.g., IAB nodes and IAB carrier nodes) via wireless access links. In addition, IAB nodes (child nodes) may communicate with other IAB nodes and / or IAB carriers (all of which may be considered IAB parent nodes) via wireless backhaul links. For example, a UE may be connected to an IAB node, which itself may be connected to a parent IAB node in communication with an IAB carrier, thereby extending backhaul resources to allow backhaul traffic to be transmitted within the network and between parent and child for integrated access. Embodiments of the system provide the capabilities required to carry information bits using a broadcast channel (on a physical channel) and provide access to a core network.

[0078] Figure 2 Depicts the IAB carrier and IAB node (see Figure 1 ). The IAB carrier may include at least one centralized unit (CU) and at least one distributed unit (DU). The CU is a logical entity that manages the DUs arranged in parallel in the IAB carrier and the remote DUs residing in the IAB node. The CU may also be an interface connected to the core network, manifested as a RAN base station (e.g., eNB or gNB). In some embodiments, the DU is a logical entity that hosts the radio interface (backhaul / access) for other child IAB nodes and / or UEs. In one configuration, under the control of the CU, the DU may provide physical layer and layer 2 (L2) protocols (e.g., media access control (MAC), radio link control (RLC), etc.), while the CU may manage upper layer protocols (such as packet data convergence protocol (PDCP), radio resource control (RRC), etc.). The IAB node may include DU and mobile terminal (MT) functions, wherein in some embodiments, the DU may have the same functions as the DU in the IAB carrier, and the MT may be a UE-like function that terminates the radio interface layer. For example, the MT may be used to perform at least one of: radio transmission and reception, encoding and decoding, error detection and correction, signaling, and access to the SIM.

[0079] The embodiments include a mobile network infrastructure in which multiple UEs are connected to a set of IAB nodes, and the IAB nodes communicate with each other for relaying and / or communicating with the IAB carrier using different aspects of the embodiments of the present invention. In some embodiments, the UE may communicate with the CU of the IAB carrier on the C plane using the RRC protocol; and in other embodiments, the UE may use the Service Data Adaptation Protocol (SDAP) and / or the Packet Data Convergence Protocol (PDCP) radio protocol architecture for data transmission (U plane) through the NR gNB. In some embodiments, the DU of the IAB node may communicate with the CU of the IAB carrier using the 5G radio network layer signaling protocol: F1 Application Protocol (F1-AP*), which is a wireless backhaul protocol that provides signaling services between the DU of the IAB node and the CU of the IAB carrier. That is, as further described below, the protocol stack configuration may be interchangeable and different mechanisms may be used.

[0080] like Figure 3 As shown in the diagram shown, the protocols between the UE, IAB node and IAB bearer are grouped into a control plane (C-plane) and a user plane (U-plane). The C-plane carries control signals (signaling data) while the U-plane carries user data. Figure 3 An example of an implementation is shown where there are two IAB nodes, IAB Node 1 and IAB Node 2 (two hops) between the UE and the IAB bearer. Other implementations may include networks with a single hop or multiple hops where there may be more than two IAB nodes.

[0081] Figure 4 A functional block diagram of an exemplary protocol stack configuration for the U-plane is depicted, the stack including a service data protocol (e.g., SDAP, 3GPP TS 37.324) that can carry user data (e.g., via IP packets). In one embodiment, SDAP runs on top of PDCP (3GPP TS 38.323) and the L2 / physical layer. In one embodiment, an adaptation layer (e.g., Backhaul Adaptation Protocol, or BAP, 3GPP TS 38.340) is introduced between the IAB node and the IAB node / bearer, where the adaptation layer carries relay-specific information such as the IAB node / bearer address, QoS information, UE identifier, and potentially other information. In this embodiment, RLC (3GPP TS 38.322) can provide reliable transport in a hop-by-hop manner, while PDCP can perform end-to-end (UE-CU) error recovery. GTP-U (GPRS Tunneling Protocol User Plane) can be used to route user data between CU and DU within the IAB bearer.

[0082] Figure 5Ais a functional block diagram of an exemplary protocol stack configuration of the C-plane between an IAB node (IAB node 1) directly connected to an IAB carrier (via a single hop). In this embodiment, the MT component of the IAB node 1 may establish an RRC connection with the CU component of the IAB carrier. In parallel, the RRC may be used to carry another signaling protocol so that the CU / IAB carrier controls the DU component residing in the IAB node 1. In one embodiment, such a signaling protocol may be referred to as the F1 Application Protocol * (F1-AP*), which is a protocol called F1-AP specified in 3GPPTS 38.473, or a protocol based on F1-AP with potential extension features to accommodate wireless backhaul (the original F1-AP is designed for wired lines). In other embodiments, F1-AP may be used for CU-DU connections within the IAB carrier. It is assumed that below the RLC, the MAC / PHY layer is shared with the U-plane.

[0083] Figure 5B A functional block diagram of an exemplary C-plane protocol stack configuration of an IAB node 2 is depicted, which is connected to the aforementioned IAB node 1 (2 hops). In one embodiment, it can be assumed that the IAB node 1 has established an RRC / F1-AP* connection with the IAB bearer, such as Figure 5A As shown. In IAB node 1, the RRC / PDCP signaling bearer for IAB node 2 can be carried by the adaptation layer to the IAB bearer. Figure 5A , the RRC of IAB node 2 carries the F1-AP* signaling.

[0084] Figure 5C Depicted in Figure 5B Another functional block diagram of an exemplary C-plane protocol stack configuration for RRC signaling of a UE in a 2-hop relay configuration as shown. Thus, a UE with MT components and functions can be connected to a CU of an IAB bearer via a C-plane. As shown, although traffic is routed through IAB Node 2 and IAB Node 1, these two nodes are passive nodes because the data is passed to the next node without manipulation. That is, the UE transmits data to a node connected to, for example, IAB Node 2, which then transmits data to a node connected to, for example, IAB Node 1, which then transmits the data (without manipulation) to the IAB bearer.

[0085] Figure 5A , Figure 5B and Figure 5C It is shown that each IAB node or UE's MT itself has an end-to-end RRC connection with the CU of the IAB bearer. Similarly, each IAB node's DU has an end-to-end F1-AP* connection with the CU of the IAB bearer. Any IAB node present between such endpoints transparently transmits RRC or F1-AP signaling traffic.

[0086] Fig. 6A and Figure 6B is a diagram of an exemplary flow of information transmission / reception and / or processing performed by an IAB node and an IAB bearer according to aspects of an embodiment of the present invention.

[0087] Fig. 6A An exemplary message sequence is depicted regarding the IAB node 1 establishing an RRC connection and then establishing an F1-AP* connection. It is assumed that the IAB node 1 has been pre-configured with (or has been configured by the network) information indicating how to select a cell served by the IAB bearer. As shown in the figure, the IAB node 1 in an idle state (RRC_IDLE) can initiate an RRC connection establishment process by sending a random access preamble to the IAB bearer, which can be received and processed by the DU of the IAB bearer. Upon successful receipt of a random access response from the IAB bearer, the IAB node 1 can send an RRCSetupRequest, then receive an RRCSetup and transmit an RRCSetupComplete. At this point in the message sequence, the IAB node 1 can enter a connected state (RRC_CONNECTED) with the IAB bearer, and can continue with security procedures to configure encryption / integrity protection features. The CU of the IAB bearer can also send an RRCReconfiguration to the IAB node 1, which may include configuration parameters for configuring radio bearers (e.g., data radio bearers (DRBs) and signaling radio bearers (SRBs)). In some embodiments, RRCReconfiguration is sent to modify the RRC connection and establish a radio connection between the UE and the network, however, in this embodiment, RRCReconfiguration may also be sent to configure a connection between the IAB node and the network. The RRC connection reconfiguration message may be used, for example, to establish / modify / release a radio bearer and / or perform a handover, etc. In one embodiment, any RRC message transmitted from the IAB node 1 may include information identifying the IAB node 1 as an IAB node (rather than a UE). For example, a carrier CU may be configured with a list of node identifiers (e.g., IMSI or S-TMSI) that are allowed to use services from the carrier. This information may be used by the CU in subsequence operations, for example, to distinguish a UE from an IAB node.

[0088] As described above, after the RRC connection establishment process, the DU of the IAB node 1 and the IAB bearer may proceed to the F1 setup process using the F1-AP* protocol, which may activate one or more cells served by the DU of the IAB node 1, thereby allowing other IAB nodes and / or UEs to camp on the cells. In this process, the adaptation layer of the IAB node 1 and the IAB bearer may also be configured and activated.

[0089] Figure 6B An exemplary message sequence or information flow for establishing an RRC connection between an IAB node 2 and an IAB bearer and then performing an F1 setup procedure is depicted. In this embodiment, it is assumed that the IAB node 1 has already executed Fig. 6A The procedures for establishing RRC and F1-AP* connections disclosed in . Figure 3 According to aspects of embodiments of the present invention, an IAB node 2 is shown communicating with an IAB node 1 via a radio interface. Figure 6B Node 1 can also be depicted as a child node of IAB Node 1.

[0090] Due to the nature of wireless communications, wireless backhaul links are susceptible to degradation or disconnection at any time. In various aspects of the embodiments of the present invention, the MT portion of the IAB node may continuously monitor the quality of the radio link and / or the signal quality upstream of the IAB node, where the radio link may be connected to the parent IAB node / carrier of the IAB node. If the radio problem cannot be recovered within a specified duration, the MT may declare a radio link failure (RLF), which means that a communication link loss may have occurred or the signal strength is difficult to continue (e.g., below a threshold).

[0091] Figure 7 An exemplary illustration of a scenario in which an IAB node (node ​​A) detects RLF on an upstream link to its parent node (parent node 1) is shown. In some embodiments, the MT component of node A may need to find another parent node visible from the node. In this case, the MT component can perform a cell selection process, and if a suitable cell (parent node 2) is successfully found, node A can use the suitable cell (parent node 2) to continue the RRC reconstruction process. It should be noted that in this case, node A needs to find a cell served by an IAB node or an IAB carrier (i.e., a cell that does not support IAB is not suitable). In one embodiment, a cell served by an IAB node or an IAB carrier may be, for example, broadcasted via a flag (e.g., broadcasted in system information such as MIB, system information block type 1 (SIB1) or any other SIB) status as an indication of the IAB capability, which may also include an indication of the current state of the IAB function, node type (IAB node or IAB carrier), hop count and / or connectivity to the parent node. Alternatively or in parallel, node A may be preconfigured or configured with a list of cell identifiers supporting IAB by the network.

[0092] While node A attempts to find a new suitable serving cell supporting IAB, the child IAB nodes (child nodes 1 and child nodes 2) and / or UEs (UE1 and UE2) may still be in connected mode with node A. If node A successfully recovers from RLF before the expiration of a preconfigured (or network configured) time period, the child nodes and / or UEs may not be aware of the RLF. However, in a scenario where node A fails to recover from RLF or fails to recover in a timely manner (e.g., before the expiration of a preconfigured / network configured time period), not only these child nodes / UEs may suffer interruption of service, but all nodes / UEs in the downstream may also suffer interruption of service.

[0093] Embodiments of the present invention disclose systems, methods and devices in which an IAB node can notify a connected node (subnode) or UE of upstream radio conditions. In some embodiments, the upstream radio condition information can enable the subnode or UE to decide whether to remain connected to the IAB node or find another node to connect to it.

[0094] Figure 8 An exemplary scenario of an upstream RLF notification is shown, which is detected upstream of a node (Node A) and sent from that node to a child node and / or a directly connected UE (also referred to as a downstream notification of backhaul (BL) RLF in 3GPP TR 38.874). In one embodiment, upon receiving the notification, each of the child node and / or UE may perform cell selection and, if successful, proceed with RRC reestablishment. Figure 8 As shown in FIG. 1 , after successfully selecting a new node (Node B), each of the subnodes and / or UEs may start a reestablishment process through the Node B. That is, once a successful selection is made, the subnode and / or UE may transmit a random access preamble / response message and then transmit an RRCReestablishmentRequest and subsequent messages, such as Figure 8 shown.

[0095] In one embodiment, the upstream RLF notification may be carried by the adaptation layer (e.g., a header portion or a message body of an adaptation layer protocol). In alternative embodiments, or in addition, the notification may be carried by RLC sublayer, MAC, or physical layer signaling (e.g., PDCCH). Additionally or alternatively, the notification may be broadcast via system information (e.g., MIB, SIB1, or any other SIB) or transmitted in a dedicated manner.

[0096] Therefore, in one embodiment, the RRC residing in each of the child node and / or the UE may perform cell selection upon receiving a notification indicating that an upstream RLF notification has been received from a lower layer. In this embodiment, this operation may be performed even if the radio link connected to the parent node remains in good condition. The node and / or the UE may then start a timer Txxx (e.g., T311 specified in 3GPP TS 38.331) based on the received notification, and when a suitable cell is selected while the timer Txxx is running, the node and / or the UE may stop the timer Txxx and initiate transmission of an RRCReestablishmentRequest to the IAB bearer.

[0097] Once the RRC connection is reestablished, the CU of the IAB bearer can update the F1-AP* configuration in the Node B and the child IAB node that initiated the RRC reestablishment. In the scenario where the connected device is a UE, since these devices do not have an F1-AP* interface, no F1-AP* configuration update is required. Therefore, the updated configuration from the IAB bearer can be used to reconfigure the routing topology that has been modified or changed due to RLF.

[0098] Fig.9A Another scenario is shown, in which the child node and / or UE may start a timer, such as timer Tyyy, based on receiving an upstream RLF notification. While timer Tyyy is running, node A may attempt to recover the upstream link by performing cell selection. In the scenario depicted in Figure 9, node A has successfully found a new parent node (parent node 2) and may initiate an RRC reestablishment process. Based on receiving an F1-AP* configuration update from the CU of the IAB bearer, node A may transmit / send an upstream recovery notification to the child IAB node and / or UE, indicating that the upstream is recovered. If the timer Tyyy has not expired, the child IAB node and / or UE receiving the notification may stop the timer Tyyy and remain connected to the node. If the timer expires before receiving the upstream recovery notification, the child IAB node and / or UE may perform cell selection / RRC reestablishment, such as Figure 8 In one embodiment, the timer value / configuration may be preconfigured. In another embodiment, the timer value / configuration may be configured by a parent node (e.g., parent node 1) via dedicated signaling or via broadcast signaling (e.g., system information, such as MIB, SIB1, or any other SIB).

[0099] Similar to the previous scenario, in one embodiment, the upstream RLF notification may be carried by adaptation layer, RLC, MAC or physical layer signaling. In addition, the notification may be broadcast via system information (eg, MIB, SIB1 or any other SIB) or transmitted in a dedicated manner.

[0100] In another embodiment of the scenario, the RRC residing in each of the child node and / or the UE may start a timer Tyyy when an upstream RLF notification is received from a lower layer. If the node and / or the UE receives a notification indicating that an upstream RLF notification is received from a lower layer while the timer Tyyy is running, the node and / or the UE may stop the timer Tyyy. If the timer Tyyy expires, the node and / or the UE may start a timer Txxx, and when a suitable cell is selected while the timer is running, the node and / or the UE may stop the timer and initiate transmission of an RRCReestablishmentRequest.

[0101] Fig. 9B Another scenario is shown in which node A may start timer Tzzz when RLF is detected. In this scenario, node A may or may not send the above upstream RLF notification to the child IAB node and / or UE. While timer Tzzz is running, node A may attempt to recover the upstream link by performing cell selection. Fig. 9B In the depicted scenario, at the expiration of the timer Tzzz (cell selection failure), node A may send a notification (e.g., upstream disconnection notification) to the child IAB node / UE, thereby notifying that the RLF recovery is unsuccessful. In this case, the child IAB node / UE receiving the notification may start the above-mentioned timer Txxx and start the cell selection process, such as Figure 8 As shown. The notification may be carried in a broadcast or in a dedicated manner by the adaptive layer, RLC, MAC or physical layer signaling. In one embodiment, timers Txxx and Tzzz may be the same timer or share the same configuration. In another embodiment, timers Txxx and Tzzz may be different timers or different configurations.

[0102] In addition, the notification provided by the IAB node to its downstream (child / UE) may not be limited to RLF or RLF recovery. In some embodiments, the IAB node may notify the child node and / or UE of signal quality (e.g., reference signal received power (RSRP), reference signal received quality (RSRQ)), reference signal strength indication (RSSI), signal to interference plus noise ratio (SINR), error rate, number of out-of-sync events, or any other type of measurement results indicating upstream radio conditions. In this case, the IAB node and / or UE may be pre-configured or configured by the network with conditions for initiating cell selection / reconstruction. The notification may be carried in a broadcast or in a dedicated manner by the adaptation layer, RLC, MAC, or physical layer signaling.

[0103] In one embodiment, upon receiving one of the notifications from the parent node, the IAB node and / or the UE may send a confirmation or reply confirmation back to the parent node, such as Figure 8 , Fig.9Aand Fig. 9B shown.

[0104] Fig.10 is a diagram showing an example of a radio protocol architecture for a control plane and a user plane in a mobile communication network. The radio protocol architecture of a UE and / or a gNodeB can be shown in three layers: Layer 1, Layer 2, and Layer 3. Layer 1 (L1 layer) is the lowest layer and implements various physical layer signal processing functions. Layer 2 (L2 layer) is above the physical layer and is responsible for the link between the UE and / or gNodeB above the physical layer. In the user plane, the L2 layer may include a media access control (MAC) sublayer, a radio link control (RLC) sublayer, and a packet data convergence protocol (PDCP) sublayer, which terminate at the gNodeB on the network side. Although not shown, the UE may have several upper layers above the L2 layer, including a network layer (e.g., an IP layer) that terminates at a PDN gateway on the network side, and an application layer that terminates at the other end of the connection (e.g., a remote UE, a server, etc.). The control plane also includes a radio resource control (RRC) sublayer in Layer 3 (L3 layer). The RRC sublayer is responsible for obtaining radio resources (ie, radio bearers) and for configuring lower layers between the IAB node and / or UE and the IAB bearer using RRC signaling.

[0105] Using autonomous switching to solve backhaul situations

[0106] Fig.11 Another example diagram of a telecommunications system 20 is shown, which includes: a wireless access node 22-1, also referred to as a carrier node 1; a wireless access node 22-2, also referred to as a carrier node 2; an IAB node 24A, also referred to as a node A or a relay node A; an IAB node 24B, also referred to as a node B or a relay node B; and a child node 1, also referred to as a child node 30. The child node 30 may be, for example, a user equipment, a UE, or an integrated access and backhaul (IAB) node, as described above. The wireless access node 22-1 and the wireless access node 22-2 may be connected via a wired backhaul link 32. Fig.11 Other elements may be connected via wireless backhaul links, for example, the wireless access node 22-1 may be connected to the IAB node 24A via a wireless backhaul link 34A; the wireless access node 22-2 may be connected to the IAB node 24B via a wireless backhaul link 34B; the IAB node 24A may be connected to the sub-node 30 via a wireless backhaul link 36A; and the IAB node 24B may be connected to the sub-node 30 via 36B.

[0107] Figures 11 to 15The exemplary embodiments and modes of the present invention relate to using autonomous switching to resolve problem conditions on a wireless backhaul link. Generally speaking, the wireless access node 22-1 generates a message and sends the message to the child node 30, the message including information configured to facilitate a conditional handover of a wireless terminal. As used herein, the terms "handover" and "cross-zone handover" are used interchangeably and generally involve transferring a connection or communication at least in part from one node or a group of nodes to another node. Although the message may be of any appropriate type and have any suitable name, in the exemplary embodiments and modes described herein, the message is a reconfiguration message and, for purposes of illustration, is arbitrarily and not completely known and is referred to in detail in the example embodiments and modes described herein. Fig.11 40. The information comprising the message (e.g., conditional handover preparation message 40) includes at least one identity of the target cell, and one or more conditions that at least partially enable the wireless terminal to autonomously perform conditional handover. In some configurations, the identity of the target cell may include one or a combination of the following: a physical cell identity (PCI), a cell identity (a cell identifier for explicitly identifying a cell within a PLMN), a PLMN identity, a tracking area identity, and a RAN area code. As understood herein, the one or more conditions include receiving a notification from a wireless relay node (e.g., from an IAB node 24A). Such notifications are also known herein and are described herein. Fig.11 4, and may be a notification of a problem condition on the wireless backhaul link. Upon receiving the condition notification 42, the child node 30 may perform an autonomous switch, such as Fig.11 Execution of autonomous handover 44 is based on information provided in conditional handover prepare message 40, for example enabled by using at least this information.

[0108] Fig.12 It is further shown in Fig.11 The various components and functions of the node are shown. Fig.12The wireless access node 22-1 is shown as including a centralized unit 50-1 and a distributed unit 52-1. The centralized unit 50-1 and the distributed unit 52-1 may be implemented (e.g., composed of) or include one or more processor circuits (e.g., node processor 54-1), for example. The centralized unit 50-1 and the distributed unit 52-1 may share one or more node processors 54-1, or each of the centralized unit 50-1 and the distributed unit 52-1 may include one or more node processors 54-1. In addition, the centralized unit 50-1 and the distributed unit 52-1 may be co-located at the same node site, or alternatively, one or more distributed units 52-2 may be located at a site away from the centralized unit 50-1 and connected to it via a packet network. The distributed unit 52-1 may include a transceiver circuit 56, which may include a transmitter circuit 57 and a receiver circuit 58. The transceiver circuit 56 includes an antenna for wireless transmission. The transmitter circuit 57 includes, for example, an amplifier, a modulation circuit and other conventional transmission devices. Receiver circuitry 58 includes, for example, amplifiers, demodulation circuits, and other conventional receiver devices.

[0109] like Fig.12 As further shown in FIG. 5 , the node processor 54-1 of the wireless access node 22-1 may include a message generator 60 and a handover coordinator 62. The message generator 60 is used to generate, for example, a conditional handover preparation message 40 as described herein. As described above, the conditional handover preparation message 40 includes information including at least one identity of a target cell and one or more conditions for the wireless terminal to autonomously perform a conditional handover. The handover coordinator 62 is used to communicate with the target cell, for example, to communicate with another node that may be involved in the handover, so that appropriate information and preparations can be obtained for the handover. In the exemplary scenario described herein, the target cell will be a cell served by the wireless access node 22-2.

[0110] like Fig.12As shown, in an exemplary embodiment and mode, the IAB node 24A (also referred to as a wireless relay node 24A) includes a relay node mobile terminal unit 70A and a relay node distributed unit 72A. The relay node mobile terminal unit 70A and the relay node distributed unit 72A may be implemented (e.g., constituted) by, for example, one or more processor circuits (e.g., relay node processor 74A) or include one or more processor circuits. One or more relay node processors 74A may be shared by the relay node mobile terminal unit 70A and the relay node distributed unit 72A, or each of the relay node mobile terminal unit 70A and the relay node distributed unit 72A may include one or more relay node processors 74A. The relay node distributed unit 72A may include a transceiver circuit 76, which may include a transmitter circuit 77 and a receiver circuit 78. The transceiver circuit 76 includes an antenna for wireless transmission. The transmitter circuit 77 may include, for example, an amplifier, a modulation circuit, and other conventional transmission devices. The receiver circuit 78 may include, for example, an amplifier, a demodulation circuit, and other conventional receiver devices.

[0111] Fig.12 Also shown, the IAB node 24A may include a radio condition detector 80 and a notification generator 82. Both the condition detector 80 and the notification generator 82 may be implemented or constituted by the relay node processor 74. The notification generator 82 is used to generate the condition notification 42 based on the condition detected by the condition detector 80.

[0112] It should be understood that although Fig.12 Not shown, but Fig.11 and Fig.15 The wireless access node 22-2 and the IAB node 24B may have similar components and functionality as the wireless access node 22-1 and the IAB node 24A, respectively, but with different numbered / alphabetized suffixes to represent similar components.

[0113] Fig.12 Subnode 30 is shown as including transceiver circuit 86 in an exemplary non-limiting embodiment and mode. Transceiver circuit 86 may in turn include transmitter circuit 87 and receiver circuit 88. Transceiver circuit 86 includes an antenna for wireless transmission. Transmitter circuit 87 may include, for example, an amplifier, a modulation circuit, and other conventional transmission equipment. Receiver circuit 88 may include, for example, an amplifier, a demodulation circuit, and other conventional receiver equipment. Fig.12Also shown is a subnode 30, which (as previously noted) may be a user device or an integrated access and backhaul (IAB) node, and also includes node processor circuitry such as one or more node processors 90, and interfaces 92, including one or more user interfaces. Such user interfaces may be used for user input and output operations, and may include, for example, a screen such as a touch screen that may display information to a user and receive information input by a user. For example, the user interface 48 may also include other types of devices, such as a speaker, a microphone, or a tactile feedback device.

[0114] exist Fig.12 In the exemplary, non-limiting embodiments and modes shown, the subnode 30 may include a frame / message generator / processor 94 and a handover controller 96. As will be appreciated by those skilled in the art, in some telecommunication systems, one or more "resources" (e.g., "radio resources") are used to transmit messages, signals, and / or data via a radio or air interface. The frame / message generator / processor 94 is used to process messages, signals, and data received from other nodes, including, but not limited to, the conditional handover preparation message 40 and the status notification 42 described herein.

[0115] In the most basic exemplary implementation and mode, the wireless access node of the technology disclosed herein transmits a message including information configured to facilitate conditional handover of a wireless terminal, the information including at least one identity of a target cell and one or more conditions for the wireless terminal to autonomously perform conditional handover, the condition including receiving a notification from a wireless relay node. In the most basic exemplary implementation and mode of the technology disclosed herein, the wireless terminal (e.g., subnode 30) receives such a message.

[0116] In addition to the basic exemplary embodiments and modes described above, Fig.13 It is also shown that Fig.11 and Fig.12The wireless access node 22-1 of the present invention is a wireless access node 22-1. The wireless access node 22-1 of the present invention is a wireless access node 22-2. The wireless access node 22-1 is a wireless access node 22-2. The wireless access node 22-2 is a wireless access node 22-3. The wireless access node 22-3 is a wireless access node 22-4. The wireless access node 22-4 is a wireless access node 22-5. The wireless access node 22-5 is a wireless access node 22-6. The wireless access node 22-6 is a wireless access node 22-7. The wireless access node 22-8 is a wireless access node 22-9. The wireless access node 22-1 is a wireless access node 22-1. The wireless access node 22-1 is a wireless access node 22-2 ...2 is a wireless access node 22-3. The wireless access node 22-4 is a wireless access node 22-5. The wireless access node 22-6 is a wireless access node 22-7. The wireless access node 22-8 is a wireless access node 22-1. The wireless access node 22-1 is a wireless access node 22-2. The wireless access node 22-2 is a wireless access node 22-1. The wireless access node 22-2 is a wireless access node 22-3. The wireless access node 22-4 is a wireless access node 22-5. The wireless access node 22-6 is a wireless access node 22-7. The wireless access node 22-8 is a wireless access node 22-1. The wireless access node 22-2 is a wireless access node 22-1. The wireless access

[0117] In addition to the basic exemplary embodiments and modes described above, Fig.14 It is also shown that Fig.11 and Fig.12 30 of the sub-node 30 of the embodiment of the present invention.Action 14-1 includes receiving a message including information configured to facilitate the conditional handover of the wireless terminal.The message may be, for example, a conditional handover preparation message 40 as described herein, which includes at least one identity of the target cell and one or more conditions for the wireless terminal to autonomously perform the conditional handover.Action 14-2 includes receiving a status notification 42 from an appropriate node such as an IAB node 24A, which notification suggests that autonomous handover may be required.Action 14-3 includes, upon receiving the status notification 42, performing an autonomous handover 44 to another node (e.g., via an IAB node 24B to a wireless access node 22-2).

[0118] exist Fig.11 In the exemplary scenario shown, the IAB node 22A (also referred to as node A or radio access node 22A) may detect a radio condition, such as a radio link failure RLF, on an upstream link to its parent node (e.g., radio access node 22-1 or carrier 1). Fig.11In an exemplary scenario, a child node 30 (which may be an IAB node or a UE) is configured by a carrier node radio access node 22-1 to use conditional handover (e.g., a conditional handover preparation message 40, which may be a reconfiguration utilizing synchronization), which allows the child node 30 to autonomously perform a handover to a designated cell (e.g., a candidate target cell) when one or more conditions configured by the RRC of carrier 1 are met. In some configurations, the condition may include receiving some of the aforementioned notifications from the parent node, such as an upstream RLF notification. When such conditions are met, the child node 1 (e.g., the child node 30) may begin accessing the designated cell (e.g., Node B / carrier 2, also referred to as IAB node 24B / radio access node 22-2) and perform a handover procedure. In one exemplary embodiment and mode, the carrier node 1 and the carrier node 2 may be physically collocated, or even the same entity. In another exemplary embodiment and mode, the two carrier nodes (e.g., radio access node 22-1 and radio access node 22-2) may be separate nodes (e.g., radio access node 22-1 and radio access node 22-2) interconnected by a wired backhaul link. Fig.11 As shown). It is assumed that before providing the configuration for conditional switching to the child node 30, the two carrier nodes, namely the wireless access node 22-1 and the wireless access node 22-2, can perform negotiation / coordination on switching, for example, action 11-3 described above. If the carrier node 1 and the carrier node 2 are the same entity, the negotiation / coordination can be performed inside the carrier node 1.

[0119] Fig.15 Describes the use Fig.11 An exemplary message flow for the scenario shown. Fig.15 In the case of the child node 30 being in connected mode, as shown in action 15-1. As action 15-3, the currently serving carrier node, i.e., carrier 1 or radio access node 22-1, may initiate handover coordination with a node serving a potential target cell (e.g., a cell served by carrier 2 or radio access node 22-2). The coordination of action 15-3 may include sharing an identity of child node 1 (e.g., child node 30); security parameters; and radio link / resource configuration. Fig.15 As shown, the coordination of act 15-3 may be triggered by act 15-2 (eg, receipt of a measurement report transmitted by child node 1), where child node 30 reports that sufficient signal quality is observed from a cell served by a Node B (eg, from IAB node 24B).

[0120] After the coordination of action 15-3 is completed, as action 15-4, the child node 30 (in the RRC_CONNECTED state, as indicated by action 15-1) may receive a conditional handover preparation message 40. In an exemplary embodiment and mode, the conditional handover preparation message 40 may be an RRCReconfiguration message including a potential target cell (e.g., a cell served by a Node B or IAB node 24B) and one or more conditions for autonomous handover. Fig.15 In the exemplary process of , the condition may include receiving an upstream RLF notification. Other non-limiting examples of the condition may include or include a signal quality threshold of a downlink signal from a current serving node (e.g., node A=IAB node 24A), and some of the other aforementioned notifications, such as an upstream disconnection notification.

[0121] exist Fig.15 In the exemplary flow shown, as action 15-5, node A (e.g., IAB node 24A) may detect RLF on an upstream link (e.g., wireless backhaul link 32). The condition on wireless backhaul link 32 may be detected by condition detector 80 of IAB node 24A. Node A may then send an upstream RLF notification 42 to its child nodes / UEs, including child node 30. Condition notification 42 may be generated by notification generator 82. As optional action 15-7, child node 30 may send an acknowledgement back. In addition, due to the configured conditions, as action 15-8, child node 30 may initiate a conditional handover to a configured target cell (e.g., in the exemplary scenario, a cell served by IAB node 24B) by performing a random access procedure. The random access procedure in which child node 30 participates includes, as action 15-8, sending a random access preamble message to IAB node 24B, and, as action 15-9, receiving a random access response message from IAB node 24B. Action 15-10 includes the child node 30 sending a message to the bearer of the target cell (e.g., bearer 2 = radio access node 22-2) via the node B = IAB node 24B. As action 15-11, the radio access node 22-2 can use F1-AP* to update the routing configuration for the child node 1 at the node B (e.g., the IAB node 24B for the child node 30), and as action 15-12, can interact with the radio access node 22-1 to report the completion of the conditional handover. The radio access node 22-1 can then release the resources reserved for the child node 30.

[0122] Therefore, in Figures 11 to 15In an exemplary embodiment and mode of the invention, the IAB node or UE may be configured to utilize conditional handover according to a condition, wherein the condition includes receiving a notification indicating a radio condition of an upstream radio link of a parent node and at least one identification of a target node. Upon receiving such a notification, the IAB node or UE may then perform an autonomous handover to a cell served by the target node.

[0123] Solving backhaul situations involving redundant connections

[0124] Fig.16 Another example diagram of a telecommunications system 20 is shown. Fig.15 The telecommunication system 20 of is similar to that of , including a wireless access node 22-1, also referred to as a carrier node 1; a wireless access node 22-2, also referred to as a carrier node 2; an IAB node 24A, also referred to as a node A or a relay node A; an IAB node 24B, also referred to as a node B or a relay node B; and a child node 1, also referred to as a child node 30. The child node 30 may be, for example, a user equipment, a UE, or an integrated access and backhaul (IAB) node, as described above. The wireless access node 22-1 and the wireless access node 22-2 may be connected via a wired backhaul link 32. Fig.16 Other elements may be connected via wireless backhaul links, for example, the wireless access node 22-1 may be connected to the IAB node 24A via a wireless backhaul link 34A; the wireless access node 22-2 may be connected to the IAB node 24B via a wireless backhaul link 34B; the IAB node 24A may be connected to the sub-node 30 via a wireless backhaul link 36A; and the IAB node 24B may be connected to the sub-node 30 via 36B.

[0125] Figures 16 to 20A , Fig. 20B The exemplary embodiments and modes of the invention relate to using redundant links to resolve problem conditions on wireless backhaul links. Generally speaking, the wireless access node 22-1 generates and sends a message to the child node 30, the message including a signaling data path (such as a redundant link) configured to activate multiple signaling data paths. Fig.16 The first signaling data path SRB_f and the second signaling data path SRB_s) are shown. The first signaling data path SRB_f is established between the wireless access node 22-1 and the wireless terminal, also referred to as the child node 30, and has its signaling data routed via the wireless access node 22-1 and the IAB node 24A. In one configuration, the second signaling data path SRB_s may be established between the wireless access node 22-2 and the child node 30, and has its signaling data relayed by the IAB node 24B. In another configuration ( Fig.16(not shown in the figure), the second signaling data path SRB_s may be established directly between the radio access node 22-2 and the subnode 30 without being relayed by the IAB node. It should be noted that either the first signaling data path or the second signaling data path may be a primary signaling radio bearer, for example, a signaling data bearer established first, and the other signaling data path may be a secondary signaling radio bearer that may be added after the primary signaling radio bearer is established.

[0126] Although the message configured to activate multiple signaling data paths may be of any appropriate type and have any suitable name, in the exemplary embodiments and modes described herein, the message is a reconfiguration message and is arbitrarily and not completely known for purposes of illustration and is referred to in Fig.16 140. The multipath activation message 140 is received by the child node 30, after which the first signaling data path SRB_f and the second signaling data path SRB_s are activated. If the child node 30 receives a notification from the IAB node 24A thereafter, the child node 30 may generate a report message (also referred to as a fault information message) and transmit the message via the second signaling path SRB_s. The report message may include information based on the notification, and the notification may be based on the radio condition detected on the first signaling data path.

[0127] Fig.17 It is further shown in Fig.16 The various components and functions of the node are shown. Fig.17 With Fig.12 Components with similar names also have similar functions. Fig.17The wireless access node 22-1 is shown as including a centralized unit 50-1 and a distributed unit 52-1. The centralized unit 50-1 and the distributed unit 52-1 may be implemented (e.g., composed of) or include one or more processor circuits (e.g., node processor 54-1), for example. The centralized unit 50-1 and the distributed unit 52-1 may share one or more node processors 54-1, or each of the centralized unit 50-1 and the distributed unit 52-1 may include one or more node processors 54-1. In addition, the centralized unit 50-1 and the distributed unit 52-1 may be co-located at the same node site, or alternatively, one or more distributed units 52-2 may be located at a site away from the centralized unit 50-1 and connected to it via a packet network. The distributed unit 52-1 may include a transceiver circuit 56, which may include a transmitter circuit 57 and a receiver circuit 58. The transceiver circuit 56 includes an antenna for wireless transmission. The transmitter circuit 57 includes, for example, an amplifier, a modulation circuit and other conventional transmission devices. Receiver circuitry 58 includes, for example, amplifiers, demodulation circuits, and other conventional receiver devices.

[0128] like Fig.17 As further shown in FIG. 1 , the node processor 54-1 of the wireless access node 22-1 may include a message generator 60; a multipath controller 162; and a report handler 163. The message generator 60 is used to generate a multipath activation message 140, such as described herein. The multipath controller 162 is used to, for example, activate multiple paths, including a first signaling data path SRB_f and a second signaling data path SRB_s. The report handler 163 is configured to receive and process a report from the child node 30, the report being based on a notification indicating a radio condition detected on one of the signaling data paths.

[0129] like Fig.17As shown, in an exemplary embodiment and mode, the IAB node 24A (also referred to as a wireless relay node 24A) includes a relay mobile terminal unit 70A and a relay distributed unit 72A. The relay mobile terminal unit 70A and the relay distributed unit 72A may be implemented (e.g., constituted) by, for example, one or more processor circuits (e.g., relay node processor 74A) or include one or more processor circuits. One or more relay node processors 74A may be shared by the relay mobile terminal unit 70A and the relay distributed unit 72A, or each of the mobile terminal unit 70A and the distributed unit 72A may include one or more relay node processors 74A. The relay node distributed unit 72A may include a transceiver circuit 76, which may include a transmitter circuit 77 and a receiver circuit 78. The transceiver circuit 76 includes an antenna for wireless transmission. The transmitter circuit 77 may include, for example, an amplifier, a modulation circuit, and other conventional transmission devices. The receiver circuit 78 may include, for example, an amplifier, a demodulation circuit, and other conventional receiver devices.

[0130] Fig.17 Also shown, the IAB node 24A may include a radio condition detector 80 and a notification generator 82. Both the condition detector 80 and the notification generator 82 may be implemented or constituted by the relay node processor 74. The notification generator 82 is used to generate the condition notification 42 based on the condition detected by the condition detector 80.

[0131] It should be understood that although Fig.17 Not shown, but Fig.16 and Fig.17 The wireless access node 22-2 and the IAB node 24B may have similar components and functionality as the wireless access node 22-1 and the IAB node 24A, respectively, but with different numbered / alphabetized suffixes to represent similar components.

[0132] Fig.17 Subnode 30 is shown as including transceiver circuit 86 in an exemplary non-limiting embodiment and mode. Transceiver circuit 86 may in turn include transmitter circuit 87 and receiver circuit 88. Transceiver circuit 86 includes an antenna for wireless transmission. Transmitter circuit 87 may include, for example, an amplifier, a modulation circuit, and other conventional transmission equipment. Receiver circuit 88 may include, for example, an amplifier, a demodulation circuit, and other conventional receiver equipment. Fig.17Also shown is a subnode 30, which (as previously noted) may be a user device or an integrated access and backhaul (IAB) node, and also includes node processor circuitry such as one or more node processors 90, and interfaces 92, including one or more user interfaces. Such user interfaces may be used for user input and output operations, and may include, for example, a screen such as a touch screen that may display information to a user and receive information input by a user. For example, the user interface 48 may also include other types of devices, such as a speaker, a microphone, or a tactile feedback device.

[0133] exist Fig.17 In the exemplary, non-limiting embodiment and mode shown, the child node 30 may include a frame / message generator / handler 94; a path controller 196; and a report generator 198. As will be appreciated by those skilled in the art, in some telecommunication systems, messages, signals and / or data are transmitted over a radio or air interface using one or more "resources" (e.g., "radio resources"). The frame / message generator / handler 94 is used to process messages, signals and data received from other nodes, including but not limited to incoming messages such as the multipath activation message 140 and status notification 42 described herein, and outgoing messages such as the report message 199 generated by the report generator 198. The path controller 196 works in conjunction with establishing, activating and deactivating the signaling data paths (such as the first signaling data path SRB_f and the second signaling data path SRB_s) in which the child node 30 participates.

[0134] In the most basic exemplary embodiment and mode, the wireless access node of the technology disclosed herein transmits at least one message activating the first signaling data path and the second signaling data path. The first signaling data path (e.g., the first signaling data path SRB_f) and the second signaling data path (e.g., the second signaling data path SRB_s) are both established between the wireless access node (e.g., the wireless access node 22-1) and the wireless terminal (e.g., the subnode 30). The signaling data on the first signaling data path is relayed by the wireless relay node (e.g., the IAB node 24A). In the most basic exemplary embodiment and mode of the technology disclosed herein, the wireless terminal (e.g., the subnode 30) receives such a message. In addition, when a condition occurs on the first signaling data path SRB_f, the subnode 30 can process the notification received from the wireless relay node, and upon receiving the notification, transmit a report message to the wireless access node on the second signaling data path. The report message includes information based on the notification, and the notification is based on the radio condition detected on the first signaling data path.

[0135] In addition to the basic exemplary embodiments and modes described above, Fig.18 It is also shown that Fig.16 and Fig.17 18-1 includes generating at least one message, for example, a message configured to activate a first signaling data path and a second signaling data path. As described above, the first signaling data path and the second signaling data path are established between the wireless access node and the wireless terminal, and the signaling data on the second signaling data path is relayed by the wireless relay node. The message of action 18-1 (which may be referred to as a multipath activation message 140) may be generated by the message generator 60. Action 18-2 includes transmitting at least one message (e.g., a multipath activation message 140) to the child node 30. The multipath activation message 140 may be transmitted by the transmitter circuit 57 of the wireless access node 22-1.

[0136] A problem condition may then occur, and for purposes of example, the problem condition is shown herein as a radio link failure occurring on the first signaling data path SRB_f. Action 18-3 includes the radio access node 22-1 receiving a report from the child node 30, and in particular, receiving a report message including information based on a notification received by the child node 30. The notification is preferably based on a radio condition detected on the first signaling data path. The notification may be a condition notification 42 as described herein. The report message (e.g., report message 199) may be received by the receiver circuit 58 and processed by the report handler 163. Action 18-4 includes determining and / or performing an action based on the report message. An example of such an action for action 18-4 may be, for example, deactivating the first signaling data path SRB_f.

[0137] In addition to the basic exemplary embodiments and modes described above, Fig.19 It is also shown that Fig.16 and Fig.17 , and the like. The present invention further exemplifies, non-limitingly, basic actions or steps performed by the child node 30 of the wireless access node 22. Action 19-1 includes receiving a message activating a first signaling data path and a second signaling data path (e.g., a first signaling data path SRB_f and a second signaling data path SRB_s). Action 19-2 includes receiving a notification of a condition detected on the first signaling data path SRB_f. The message of action 19-1 may be the multipath activation message 140 described herein, which is generated by the wireless access node 22-1; the message of action 19-2 may be the condition notification 42 described herein, which is generated by the IAB node 24A. The messages of both action 19-1 and action 19-2 may be received by the receiver circuit 88 and processed by the frame / message generator / handler 94. Action 19-3 includes transmitting a report message to the wireless access node upon receiving the notification of action 19-2. The report message includes information based on the notification; the notification is based on the radio condition detected on the first signaling data path.

[0138] exist Fig.16 In the exemplary scenario shown, a subnode 30 (e.g., subnode 1, which may be an IAB node or a UE) establishes redundant connections (i.e., multiple connections or simultaneous connections, such as dual connectivity (DC)) for at least signaling radio bearers (SRBs) (and possibly data radio bearers (DRBs)). Fig.16 In the scenario of , SRB can be carried by two (or more) separate paths: (1) signaling data path SRB_f, which includes radio access node 22-1, IAB node 24A and child node 30, for example, carrier 1-node A-child node 1 (SRB_f), and (2) signaling data path SRB_s, which involves radio access node 22-1, radio access node 22-2, IAB node 24B and 30, for example, carrier 1-carrier 2-node B-child node 1 (SRB_s). In one configuration, radio access node 22-1 (e.g., carrier 1) can act as a master node, and radio access node 22-2 (e.g., carrier 2) can act as a slave (or slave) node. In another configuration, radio access node 22-1 (e.g., carrier 1) can act as a slave (or slave) node, and radio access node 22-2 (e.g., carrier 2) can act as a master node. In one configuration, the signaling data may be repeated and transmitted on multiple paths, for example, repeated and transmitted on a first signaling data path SRB_f and a second signaling data path SRB_s. In another configuration, packets for the signaling data are divided into two paths, for example, a first signaling data path SRB_f and a second signaling data path SRB_s, to increase throughput.

[0139] After establishing an RRC connection to the radio access node 22-1 (e.g., to carrier 1), the child node 30 may be provided with configuration via a secondary cell served by the radio access node 22-2 and the IAB node 24B. Following this configuration, the child node 30 may use the multiple paths to transmit / receive signaling bearers (and possibly data bearers). In this exemplary embodiment and mode, at least one of the parent nodes of the child node 30 may send some of the aforementioned notifications representing the radio condition of its upstream radio link. That is, when the radio condition occurs, the IAB node 24A or the IAB node 24B may send such a notification. For example, similar to the previously disclosed embodiments, when a radio link failure (RLF) is detected on the upstream radio link of the IAB node 24A, the IAB node 24A may send an upstream RLF notification to its child nodes, including the child node 30. In this case, the child node 30 may attempt to report the event to at least one of the serving carriers using a path that is not affected by the RLF. In Fig.16In the illustrated scenario, the child node 30 may use path SRB_s to send a report to the radio access node 22-2 via the IAB node 24B. In some exemplary configurations, the report may also be transmitted to the radio access node 22-1 (e.g., carrier 1), which may decide to reconfigure an updated redundant connection to the child node 30.

[0140] Fig. 20A Shown for Fig.16 1, where the child node 30 may first establish an RRC connection with the bearer 1, which results in the establishment of SRB_f. Fig. 20A 20-1), the wireless access node 22-1 may decide to configure an additional connection and, as shown in action 20-2, begin coordination with the wireless access node 22-2. It should be noted that, similar to the previously disclosed embodiments, the wireless access node 22-1 and the wireless access node 22-2 may be physically collocated or separate entities, or even the same entity. As action 10-3, the wireless access node 22-1 may send an RRCReconfiguration including a configuration for adding a new SRB (SRB_s) and an identity of a cell serving the SRB_s (an identity of a cell served by the IAB node 24B) to the child node 30. As action 20-4, the child node 30 may then confirm the RRCReconfiguration by sending an RRCReconfigurationComplete message. As action 20-5, the wireless access node 22-2 may use F1-AP* to update the routing configuration for the child node 30 at the Node B (e.g., at the IAB node 24B).

[0141] As action 20-6, the child node 30 may initiate a random access procedure by sending a random access preamble message, and as action 20-7, may receive a random access response message. The random access procedures of actions 20-6 and 207 are used to synchronize the child node 30 to the IAB node 24B.

[0142] Finally, as action 20-8, IAB node 24A may detect the specified radio condition on its upstream link. Fig. 20A In the exemplary scenario shown, the specified upstream condition may be a radio link failure (RLF), but may be other radio link conditions. Action 20-9 includes IAB node 24A sending a notification, such as condition notification 42, to child node 30. Fig. 20AIn the exemplary scenario shown, where the specified upstream condition may be a radio link failure (RLF), the condition notification 42 may be an upstream RLF notification, which may be sent to child nodes / UEs of the IAB node 24A, including but not necessarily limited to the child node 30. As an action 20-10, the child node 30 may send an acknowledgement of the condition notification 42 back to the IAB node 24A. In addition, upon receiving the notification of action 20-9, for example, upon receiving the condition notification 42, as an action 20-11, the child node 30 may generate and transmit a report message reporting the RLF occurring on the path of SRB_f. The report message 199 may be generated by the report generator 198 upon receiving the condition notification 42.

[0143] exist Fig. 20A In one exemplary embodiment and mode shown, the report message of action 20-11 can be an RRC message of action 20-11 involving carrier 1 (e.g., wireless access node 22-1). As action 20A-12, carrier 2 (e.g., wireless access node 22-2) can transmit the report message to carrier 1 using an inter-node message on the wired backhaul link 32. Upon receiving the report message, carrier 1 can coordinate with carrier 2 to deactivate the problematic signaling data path (e.g., the first signaling data path SRB_f), as shown in action 20A-13. In one specific implementation, the wireless access node 22-1 (also known as carrier 1) now recognizes that SRB_f is deactivated and can reconfigure the child node 30 with a new SRB configuration, for example, by sending another RRCReconfiguration to release SRB_f. In parallel, if the child node 30 is an IAB node, the wireless access node 22-1 can also use F1-AP* to update the routing configuration of the child node 30.

[0144] exist Fig. 20B In another exemplary embodiment and mode shown, the report message 42 of action 20B-11 is addressed to a parent node, such as IAB node 24B, using adaptation layer, RLC layer, MAC layer or physical layer signaling. Then, as action 20B-12, the parent node IAB node 24B may transmit the report message to bearer 2, such as to wireless access node 22-2, using a protocol (e.g., F1-AP*). As action 20B-13, wireless access node 22-2 may redirect the report message to bearer 1, such as wireless access node 22-1, using an inter-node message on wired backhaul link 32. Similar to Fig. 20AIn the previous embodiment and mode shown, in one specific implementation, the wireless access node 22-1 (also known as the carrier 1) now recognizes that SRB_f is deactivated and can reconfigure the child node 30 with a new SRB configuration, for example, by sending another RRCReconfiguration to release SRB_f. In parallel, if the child node 30 is an IAB node, the wireless access node 22-1 can also use F1-AP* to update the routing configuration of the child node 30.

[0145] exist Fig. 20A Exemplary embodiments and modes of Fig. 20B In the exemplary embodiments and modes of the present invention, upon receiving the report message 199, the radio access node 22-1 may take appropriate actions, such as, for example, deactivating the first signaling data path SRB_f.

[0146] In one exemplary embodiment and mode, the child node is preconfigured to send a report message upon receiving one of the specified notifications from the parent node (e.g., from the IAB node 24A). In another exemplary embodiment and mode, the child node is configured by the IAB carrier node to send a report message upon receiving one of the specified notifications. In the latter case, RRCReconfiguration can be used to configure the specified notification for sending the report message.

[0147] Therefore, in Figures 16 to 20A and Fig. 20B In an exemplary embodiment and mode of the invention, an IAB node or UE configured with multiple radio paths for signaling radio bearers may receive a notification from a parent node indicating a radio condition of an upstream radio link of one of the parent nodes. The IAB node or UE may use one or more other radio paths to send a report message reporting the radio condition to at least one IAB bearer node. The IAB bearer node receiving the report message may initiate a reconfiguration of an updated topology and / or routing of the relay network accordingly.

[0148] The IAB system should be reliable and robust to various possible failures. Therefore, the technology disclosed in this article provides a method and process for handling radio link failures on the backhaul link. Conditional handover configuration in wireless relay networks

[0149] Fig.21 Another example diagram of a telecommunications system 20 is shown, which includes: a wireless access node 22, an IAB node 24A (also referred to as a wireless relay node 24A); a target IAB node 24B; and a child node 30. The child node 30 may be, for example, a user equipment, a UE, or an integrated access and backhaul (IAB) node, as described above. For simplicity, the node 30 may be referred to herein as an IAB node 30 or a wireless node 30. Fig.21The telecommunications system 20 may also include Fig.11 The other access nodes and backhaul connections shown are shown, and the target IAB node 224B can be connected to such other access nodes or additional IAB nodes. Fig. 22 Aspects of the wireless access node 22, wireless relay node 24A, and IAB node 30 are described in greater detail.

[0150] With Fig.11 In a similar way, Fig.21 The elements may be connected via wireless backhaul links, for example, wireless access node 22 may be connected to IAB node 24 via wireless backhaul link 34; IAB node 24A may be connected to sub-node 30 via wireless backhaul link 36; and after switching, target IAB node 24B may be connected to sub-node 30 via link 33B.

[0151] Figure 21 to Figure 26 The exemplary embodiments and modes also involve using autonomous switching to resolve problem conditions on the wireless backhaul link. Generally speaking, the wireless access node 22-1 generates a message and sends the message (referred to as a conditional switching configuration message in the exemplary embodiment) to the child node 30, the message including information configured to facilitate conditional switching of the wireless terminal. As used herein, the terms "switching" and "cross-zone handover" are used interchangeably and generally involve transferring a connection or communication at least in part from one node or a group of nodes to another. Although the message can be of any appropriate type and have any suitable name, in the exemplary embodiments and modes described herein, the message is a reconfiguration message and, for purposes of illustration, is arbitrarily and not completely known, and is used in the example embodiment. Fig.21 The conditional switching configuration message 40 (21) is shown in FIG.

[0152] Fig. 22 It is further shown in Fig.21 The various components and functions of the node are shown. Fig. 22 The wireless access node 22 is shown to include a centralized unit 50 and a distributed unit 52. The centralized unit 50 and the distributed unit 52 may be implemented (e.g., composed of) or include one or more processor circuits (e.g., node processor 54), for example. The centralized unit 50 and the distributed unit 52 may share one or more node processors 54, or each of the centralized unit 50 and the distributed unit 52 may include one or more node processors 54. The transceiver circuit 56 includes an antenna for wireless transmission. The transmitter circuit 57 includes, for example, an amplifier, a modulation circuit, and other conventional transmission devices. The receiver circuit 58 includes, for example, an amplifier, a demodulation circuit, and other conventional receiver devices.

[0153] like Fig. 22As further shown in FIG. 1 , the node processor 54 of the wireless access node 22 may include a message generator 60 (21) and a handover coordinator 62. The message generator 60 (21) is used to generate a conditional handover configuration message 40 (21) such as described herein. As described in more detail, the conditional handover configuration message 40 (21) includes information including at least one identity of a target cell (also referred to as a candidate target cell) and one or more conditions for the wireless terminal to autonomously perform conditional handover. The handover coordinator 62 is used to communicate with the target cell, for example, with another node that may be involved in the handover (such as a wireless relay node 24B), so that appropriate information and preparations can be obtained for the handover.

[0154] As described above, the subnode 30 may be a UE-type wireless terminal or an IAB node. For the purpose of representative discussion, Fig. 22 The subnode 30 in the form of an IAB node is shown, which itself can also be a relay node for other nodes. Fig. 22 As shown, the IAB node 30 includes a mobile termination unit 70 and a distributed unit 72. The node mobile terminal unit 70 and the node distributed unit 72 may be implemented (e.g., composed of) or include one or more processor circuits (e.g., IAB node processor 74), for example. One or more node processors 74 may be shared by the node mobile terminal unit 70 and the node distributed unit 72, or each of the node mobile terminal unit 70 and the node distributed unit 72 may include one or more node processors 74. The node distributed unit 72 may include a transceiver circuit 76, which may include a transmitter circuit 77 and a receiver circuit 78. The transceiver circuit 76 includes an antenna for wireless transmission. The transmitter circuit 77 may include, for example, an amplifier, a modulation circuit, and other conventional transmission devices. The receiver circuit 78 may include, for example, an amplifier, a demodulation circuit, and other conventional receiver devices.

[0155] Fig. 22 It is also shown that the IAB node 24A may include a frame / message handler / generator 94(22) and a handoff controller 96(22). The handoff controller 96(22) in turn includes an evaluation unit or comparison unit 97 that compares information 98 representing the trigger condition with information 99 representing the radio condition.

[0156] In the exemplary embodiment and mode in which the child node 30 is a wireless terminal or user equipment rather than an IAB node, it should be understood that the handoff controller 96 (22) and its evaluation unit or comparison unit 97 may be provided in a wireless terminal processor, such as reference Fig.12 Understood.

[0157] Fig.21The exemplary embodiment of the present invention discloses a detailed design of a conditional switching configuration for an IAB node. Unless otherwise specified, the operations and modes for the "MT part of the IAB node" disclosed in the embodiments below can also be applied to other suitable circuits of the IAB node or wireless terminal (e.g., user equipment). In one configuration, Fig.11 shown in and as Fig.21 The RRCReconfiguration message of the conditional handover configuration message 40 (21) in the RRCReconfiguration message may include an information element CHOConfig, which may include a set of parameters to configure conditional handover for the MT part of the IAB node. In another configuration, another message such as RRCCCHOConfiguration may be used to carry CHOConfig.

[0158] Fig.23A Non-limiting examples of parameters that may be included in CHOConfig are shown. Such parameters may include: identification of the candidate target cell; events that trigger the execution of CHO (e.g., conditional handover); RACH configuration of the candidate target cell; uplink / downlink, UL / DL configuration of the candidate target cell; new UE identity (e.g., RNTI) to be used for the candidate target cell.

[0159] Listing 1 shows an exemplary format of an information element (IE) CHOConfig to be included in a message for CHO configuration.

[0160] List 1

[0161]

[0162]

[0163]

[0164]

[0165] In an exemplary implementation, the event that triggers the conditional switching listed in Table 1 is defined as follows:

[0166] Event Al: the service becomes better than the absolute threshold;

[0167] Event A2: The service becomes worse than the absolute threshold;

[0168] Event A3: The neighbor changes to a better offset than the PCell / PSCell;

[0169] Event A4: The neighbor becomes better than the absolute threshold;

[0170] Event A5: PCell / PSCell becomes worse than an absolute threshold, and neighbor / SCell becomes better than another absolute threshold 2;

[0171] Event A6: The neighbor becomes a better offset than the SCell.

[0172] Primary Cell (PCell): A Master Cell Group (MCG) cell, operating on a primary frequency, where the UE performs an initial connection establishment procedure or initiates a connection re-establishment procedure.

[0173] Primary SCG (Secondary Cell Group) cell (PSCell): For dual connectivity operation, the SCG cell in which the UE performs random access when reconfiguration is performed using a synchronization procedure.

[0174] Secondary cell (SCell): For UEs configured with CA, a cell that provides additional radio resources in addition to the special cell

[0175] IAB nodes such as Fig.21 and Fig. 22 The IAB node 30 of the embodiment may determine that a conditional handover will occur by evaluating one or more measurements on one or more direct upstream links relative to appropriate thresholds for the corresponding links. A "direct" upstream link is a link that the IAB node actually uses to receive radio communications from its direct parent node, rather than a link between the parent nodes of the IAB node. For example, in Fig.21 In this case, the direct upstream link may be link 36A.

[0176] The measurements may correspond to certain radio condition "events", as described above. As described herein, one or more events to be evaluated and appropriate thresholds for each event may be communicated to the IAB node in a conditional handover configuration message 40 (21). For example, if an evaluation of a measurement of a radio reception event relative to a threshold indicates that the link quality or condition is not as good as the quality from another node or cell, the IAB node may autonomously perform a conditional handover. The foregoing describes the IAB node 30 determining whether a conditional handover should be performed based on the measured quality of the direct upstream link. However, there are other situations in which a parent node (e.g., wireless relay node 24A) detects a problem link between it and a node that is also upstream of the parent node, such as by a Fig.21 Conditional switching should also occur if the radio link failure indicated by the RLF in the RLF in the IAB node is detected. In this case, the IAB node 30 may also need to perform conditional switching. The IAB node 30 can only know the failure that occurred somewhere upstream of the parent node through the notification message 42 (21) sent from the upstream parent node to the IAB node. However, enhancing the conditional switching configuration message to include additional situations that cover the adverse radio conditions encountered by the parent node may undesirably complicate the conditional switching configuration message.

[0177] Therefore, according to one aspect of the technology disclosed herein, in order to determine whether a triggering event is occurring (eg, whether a triggering condition is satisfied / met), the IAB node 20 (eg, Fig. 22 The MT portion 70 of the IAB node 30 may process or consider the notification message indicating the upstream RLF event of the parent node as if the RLF occurred at the direct upstream link of the IAB node itself, thereby facilitating possible conditional handover as explained herein.

[0178] to this end, Fig. 22 The handover controller 96 (22) is configured to make a determination whether to perform a handover based on both the conditional handover configuration message and the notification received from the parent node. For example, Fig. 22 The handover controller 96 (22) may determine whether to perform a handover based on both the trigger condition received in the conditional handover configuration message and the information indicating the radio condition received in the notification from the wireless relay node. To this end, Fig. 22 The handover controller 96 (22) is shown to include an evaluation unit or comparison unit 97 which compares information 98 representative of the triggering condition and information 99 representative of the radio conditions.

[0179] exist Fig.24A In the exemplary case shown, in which the IAB node 30 itself detects a problem on one of its direct upstream links, the comparison unit 97 compares a threshold value including information 98 representing a trigger condition 98 with the signal strength / quality of the signal on the direct upstream link (wireless backhaul link 36) measured by the IAB node 30, for example, the actually measured signal strength / quality is used as information 99 representing the radio condition.

[0180] On the other hand, Fig. 24B In the exemplary scenario shown, upon receiving the notification message 42 (21), the IAB node may assume that the received signal strength / quality (e.g., RSRP, RSRQ, or SINR) of the serving cell, PCell, and / or PSCell is equal to or lower than a predetermined (or preconfigured) value (such as negative infinity) in order to compare the received signal with the threshold in conjunction with the conditional handover determination. In this case, the predetermined / preconfigured value is compared with the threshold of the trigger condition of interest. For example, when the IAB node 30 receives the notification message 42 (21) indicating RLF, the IAB node 30 behaves as if the signal strength / quality of the direct upstream link is equal to or lower than the predetermined value. In other words, the information 99 representing the radio condition is assumed to be a predetermined value. Assuming that the predetermined value is sufficiently low compared to the threshold constituting the information 98 representing the trigger condition, the handover controller 96 (22) will trigger at least one configured trigger event.

[0181] The predetermined value of the received information 99 which may be used by the comparison unit 97 to represent the radio condition may be configured at the IAB node, preconfigured or configured by the network. For example, the predetermined value may be included in a conditional handover configuration message.

[0182] For example, assume that event A3 is configured as a triggering event for conditional switching to the MT part of the IAB node. Upon receiving a notification message (e.g., upstream RLF notification), based on this implementation, the MT part of the IAB node may consider that the A3 event is occurring (even if its direct upstream link does not trigger the event). The MT part of the IAB node may then perform conditional switching according to the configuration of CHOConfig.

[0183] like Fig. 23B As shown, the conditional switching configuration message may include multiple trigger conditions, such as multiple trigger events. The multiple trigger events may include one or more of those listed above, such as event A1, event A2, event A3, event A4, event A5 and event A6. In this case, the predetermined / pre-configured value is compared with the threshold value of the trigger condition being concerned.

[0184] If the information 99 representing the radio condition is above the threshold for all events indicated in the conditional handover configuration message, none of the conditions for the configured events will be met, and therefore the handover controller 96 (22) will not declare or determine the conditional handover. However, if the notification 42 (21) is a radio link failure (RLF), and if the assumed predetermined value should be sufficiently low, such as negative infinity, the handover controller 96 (22) should determine the handover. If the notification indicates that the parent node is experiencing low signal strength / quality or RLF, it may be reasonable that the IAB node can perform a HO, provided that the IAB node is configured with a conditional HO condition regarding signal strength / quality.

[0185] In an exemplary implementation, when a notification message is received, for an IAB node having an MT part, the MT part of the IAB node may consider automatically satisfying some of the triggering events, such as events A2, A3, and A5. For example, if A2, A3, or A5 is configured as a trigger condition in the conditional handover configuration message, and if the information indicating the radio condition is RLF, a determination is made to perform a handover. If multiple triggering events are configured, the IAB node may evaluate each of these triggering events. Once at least one of them is satisfied, HO is performed.

[0186] like Fig.23C As shown, each trigger event may include a threshold associated with the corresponding event, and optionally may also include Fig.23D and Fig.23EAs described below, the applicability indication indicates whether the corresponding trigger condition is applicable to the notification message 42 (21).

[0187] like Fig.23D As shown, a conditional switching configuration message, such as CHOConfig, may include at least one indication, such as an applicability indication, which is used to indicate whether the trigger condition in CHOConfig is also applicable to notifications about RLF on upstream links of the parent node (not only applicable to direct upstream links). If the indication associated with the trigger event indicates that the trigger event is applicable to the notification message, the condition of the trigger event is evaluated using the information in the notification message. On the other hand, if the indication indicates that the condition is not applicable to the notification message, the IAB node evaluates the condition based on its own measurements of one or more direct upstream links and does not use the notification to evaluate the condition. If the associated indication is set to true or exists, the MT of the IAB node may evaluate the trigger event according to the configuration disclosed above in this embodiment. Otherwise, only the direct upstream links of the MT of the IAB node can be used to evaluate the trigger event. Listing 2-1 also shows Fig.23D An exemplary implementation of wherein one applicability indication is common to all triggering events.

[0188] exist Fig.23E In another exemplary configuration shown and List 2-2, an applicability indication is provided in the conditional switching configuration message for each trigger event (useForRLFNotification) that can be used. For example, assume that A2 and A3 are configured for conditional switching, and for A2 useForRLFNotification = false (or does not exist) and for A3 useForRLFNotification = true (or exists). When the IAB node detects an A2 or A3 event on its direct link based on measurement results, it will trigger a conditional switching. However, when the IAB node receives a notification message containing RLF, it will only evaluate A3. In the case of using a predetermined value, it is ensured that the target (= neighbor) cell becomes a better offset than the PCell / PSCell (= service) because the predetermined value is lower, such as negative infinity.

[0189] List 2-1

[0190]

[0191] List 2-2

[0192]

[0193] In yet another configuration, for one RAT, one indication may be used for each CHO configuration (eg, CHOConfigNR, CHOConfigInterRAT).

[0194] Alternatively, the above applicability indication (common or per trigger event) may indicate (i) applicable to both direct upstream links and notification messages, (ii) applicable only to direct upstream links, or (iii) applicable only to notification messages.

[0195] i. The condition may be evaluated against measurements on its immediate upstream link and against the information in the notification.

[0196] ii. The condition may be evaluated against measurements on its direct upstream link but not against the information in the notification. For example, if the notification indicates RLF, the notification will not be evaluated and therefore it will not trigger a handover by itself.

[0197] iii. The condition can be evaluated against the information in the notification message. For example, even if the radio condition measured at its direct upstream link deteriorates, it will not cause a handover based on that condition. This is mainly to provide thresholds specified for notification messages (e.g., two A2 events, one for measurement and one for notification, each with a different threshold).

[0198] Fig.24C Another exemplary scenario is shown, which may be employed as an alternative or in addition to the exemplary scenario described above. In the exemplary scenario of FIG. 24 , the notification message 42(21) may carry a signal quality / strength value / indicator measured by the parent node at the parent node's upstream link. In other words, the parent node may provide a measurement of the signal quality / strength value / indicator in the notification message 42(21). Upon receiving such a notification message carrying the measurement, the MT of the IAB node may use such a value / indicator to evaluate the configured trigger event. That is, Fig.24C As shown, the information 99 representing the radio condition may include the measurement reported in the notification message, and the handover controller 96 (22) may compare the measurement with the threshold of the information 98 representing the trigger condition. For example, in the case where event A3 is configured with an RSRP value (MeasTriggerQuantity=rsrp), upon receiving a notification message including the RSRP value from its parent node, the MT part of the IAB node may use the RSRP value as if the value was measured from the serving cell, PCell, or PSCell.

[0199] Therefore, it can be seen from the foregoing that conditions such as thresholds can be used to define events such as A1, A2, etc. The IAB node uses this condition to check whether the event occurs. For example, if A2 is configured, the IAB node will (1) measure the result (in Fig.24A In the case of Fig.24C ) and / or a predetermined value (in Fig. 24B In the case of (2) comparing with a threshold value (e.g., information 98 indicating the trigger condition). If the measurement result (or the value in the message) shows that it is below the threshold value, then the A2 event occurs and triggers the switch.

[0200] In addition, the conditional handover configuration CHOConfig may include one or more triggering events for RLF on the upstream link of the parent node specified for the notification message. For example, event Ax (e.g., A7) may be defined as receiving the aforementioned upstream RLF notification. Similarly, event Ay (e.g., A8) may be defined as receiving the aforementioned upstream disconnection notification. Listing 3 shows an exemplary implementation of the configuration for such events, where event A7 may be associated with the timer value of Tyyy.

[0201] List 3

[0202]

[0203]

[0204] Thus, in one configuration, a handover may be performed immediately after evaluating a configured triggering event. In another configuration, a final decision to perform a conditional handover may be made upon or after expiration of a timer (such as the aforementioned Tyyy), which may be started upon receipt of a notification indicating RLF (e.g., an upstream RLF notification) from its parent node. The timer may be stopped (without performing a handover) upon receipt of another notification (e.g., an upstream recovery notification) indicating RLF recovery (i.e., successful connection reestablishment). The use of timers such as those described above may be combined with the aforementioned exemplary embodiments and modes (such as Figure 8 , Fig.9A and Fig. 9B ) to understand.

[0205] Fig.25 shows that a wireless access node such as Fig.21 and Fig. 22 The general representative basic actions or steps performed by the wireless access node 22 of FIG. 25-1 include generating a conditional handover configuration message including a trigger condition. The conditional handover configuration message is shown as Fig.21 The conditional switching configuration message 40(21) can be Fig. 22The message generator 60 (21) of . Action 25-2 includes transmitting the conditional handover configuration message to the wireless node. As described above, the notification message is sent by the wireless relay node to the wireless node and includes information representing the radio condition detected on the path between the wireless relay node and the wireless access node. The trigger condition and the information representing the radio condition enable the wireless node to make a determination whether the wireless node performs the handover.

[0206] Fig.26 It shows that Fig.21 and Fig. 22 The general representative basic actions or steps performed by the IAB node 30 and the subnode of the wireless access node 26-1 include receiving a conditional handover configuration message including a trigger condition from the wireless access node. Action 26-2 includes receiving a first notification message from the wireless relay node, the first notification message including information indicating a radio condition detected on a path between the wireless relay node and the wireless access node. Action 26-3 includes determining whether to perform a handover based on the trigger condition and the information indicating the radio condition.

[0207] Therefore, the technology disclosed herein allows (1) sharing the conditions of the triggering event with the conventional conditional HO based on the measurement of the direct link, and (2) sharing the new conditional HO conditions based on the information given by the notification message. If the predetermined / preconfigured values ​​are not used, there is no need to configure the conditions specified for the new conditional HO.

[0208] Therefore, the conditional handover configuration of the technology disclosed herein provides the conditions under which the IAB node can autonomously move to the candidate target cell. Once the condition is given, it is evaluated by the IAB node. In the prior art, the condition is evaluated (compared) against the signal quality measured on the (direct) radio link. In various aspects of the technology disclosed herein, the condition can also be evaluated against the information provided by the notification message.

[0209] Fault Information in Wireless Relay Networks

[0210] Figures 27 to 31 Yet another exemplary embodiment and mode of telecommunication system 20 is shown. Figures 27 to 31 The telecommunication system 20 provides configuration and content for the aforementioned report message, which reports a radio link failure RLF occurring on one path among a plurality of configured paths (eg, DC). Figures 27 to 31 The exemplary embodiments and modes of the present invention are applicable to any other exemplary embodiments and modes described herein and can be combined therewith. Fig. 27Whether for the exemplary embodiments and modes or for any other exemplary embodiments and modes, the report message may sometimes be referred to as a FailureInformation message, and in the case where the RLF occurs on the primary cell group (MCG) path, the report message may also be referred to as an MCGFailureInformation message, or in the case where the RLF occurs on the secondary cell group (SCG) path, the report message may be referred to as an SCGFailureInformation message.

[0211] Fig. 27 and Fig.28 Specifically shown are a wireless access node 22 (27), which may be a bearer access node; a wireless relay node 24 (27) and a child node 30 (27). The child node 30 (27) may be, for example, a user equipment, UE, or an integrated access and backhaul (IAB) node, as described above. For simplicity, the node 30 (27) may be referred to herein as an IAB node 30 (27) or a wireless node 30 (27). Fig. 27 The telecommunications system 20 may also include Fig.11 Other access nodes and backhaul connections are shown.

[0212] Fig.28 It is further shown in Fig. 27 The various components and functions of the node are shown. Fig.28 The wireless access node 22 (27) is shown as including a centralized unit 50 and a distributed unit 52. The centralized unit 50 and the distributed unit 52 may be implemented (e.g., composed of) or include one or more processor circuits (e.g., node processor 54), for example. The centralized unit 50 and the distributed unit 52 may share one or more node processors 54, or each of the centralized unit 50 and the distributed unit 52 may include one or more node processors 54. The transceiver circuit 56 includes an antenna for wireless transmission. The transmitter circuit 57 includes, for example, amplifiers, modulation circuits, and other conventional transmission devices. The receiver circuit 58 includes, for example, amplifiers, demodulation circuits, and other conventional receiver devices.

[0213] like Fig.28 As further shown, the node processor 54 of the wireless access node 22 (27) may include a message generator 60 (27) and a path activation controller 162 (27). The message generator 60 (27) is used to generate, for example, one or more reconfiguration messages 200, such as Fig. 27 As shown in the reconfiguration message 200 in FIG. The reconfiguration message 200 is used to activate the first data path 202 and the second data path 204. Fig. 27As shown, a first data path 202 is established between the wireless access node 22 (27) and the wireless node 30 (27); a second data path 204 is relayed by the wireless relay node 24 (27). The message generator 60 (27) may generate a radio resource control RRC message, such as an RRCReconfiguration message, and thus may be included in or constitute an RRC entity of the wireless access node 22 (27).

[0214] In an exemplary embodiment and mode, the wireless relay node 24 (27) includes a relay node mobile terminal unit 70 (27), a relay node distributed unit 72 (27), and a similar manner to the previously described IAB node. The relay node mobile terminal unit 70 (27) and the relay node distributed unit 72 (27) may be implemented (e.g., constituted) by, for example, one or more processor circuits (e.g., relay node processor 74 (27)) or include one or more processor circuits. One or more relay node processors 74 (27) may be shared by the relay node mobile terminal unit 70 (27) and the relay node distributed unit 72 (27), or each of the relay node mobile terminal unit 70 (27) and the relay node distributed unit 72 (27) may include one or more relay node processors 74 (27). The relay node distributed unit 72 (27) may include a transceiver circuit 76, which in turn may include a transmitter circuit 77 and a receiver circuit 78, as understood with reference to the previously described exemplary embodiments and modes. The wireless relay node 24 (27) may include a radio condition detector 80 and a notification generator 82 (27). Both the condition detector 80 and the notification generator 82 (27) may be implemented or constituted by the relay node processor 74. The notification generator 82 (27) is used to generate Fig. 27 A radio link failure RLF notification message 42 ( 27 ) is shown, which indicates a radio link failure (RLF) on the second data path 204 .

[0215] The wireless node 30 (27) may be a UE type wireless terminal or an IAB node. For the purpose of representative discussion, Fig.28 The sub-node 30 is shown in the form of a wireless terminal, but it should also be understood that the wireless node 30 (27) may take the form of an IAB node, such as Fig. 22IAB node 30. In the case of being shown as a wireless terminal, in an exemplary, non-limiting embodiment and mode, the wireless node 30 (27) includes a transceiver circuit 86 (27). As understood with reference to the embodiments and modes previously described, the transceiver circuit 86 (27) may in turn include a transmitter circuit 87 and a receiver circuit 88. The wireless node 30 (27) also includes a node processor circuit, such as one or more node processors 90 (27), and an interface 92 (97), including one or more user interfaces, as previously described with reference to other exemplary embodiments and modes. In addition, in Fig.28 In the exemplary, non-limiting embodiment and mode shown, the sub-node 30 may include a frame / message generator / processor 94(27) and a switching controller 96(27). The wireless node 30(27) also includes a fault information message generator 210 that generates Fig. 27 Fault information message 212 is shown. Fault information message generator 210 may be constructed or included in switch controller 96(27) or in some other unit or function of node processor 90(27).

[0216] exist Fig. 27 and Fig.28 In the exemplary embodiment and mode of the present invention, the wireless node 30 (27) generates and sends the FailureInformation message 212 when: (1) RLF is detected on one of the direct upstream links of the multiple radio paths, or (2) an RLF notification message 42 (27) is received. The RLF notification message 42 (27) can be one of the aforementioned notification messages related to the RLF occurring on the upstream link of the parent node, for example, upstream RLF notification, upstream disconnection notification.

[0217] FIG. 29A to FIG. 29C Various example contents or information elements of a fault information message 212 are shown according to different example implementations of the technology disclosed herein. FIG. 29A to FIG. 29C The content or information elements are not exhaustive, but are merely intended to illustrate specific types of information of interest for the technology disclosed herein.

[0218] For example, Fig.29A The FailureInformation message may include an indication indicating whether the message is sent due to (1) or (2), for example, whether (1) the FailureInformation message 212 is sent when the wireless node 30 (27) itself detects RLF on one of the direct upstream links of the multiple radio paths, or (2) the wireless node 30 (27) receives the RLF Notification message 42 (27) from another node such as the wireless relay node 24 (27). Fig.29AIn the exemplary implementation shown, the indication is implemented as a FailureType, which is an information element (IE) in a FailureInformation message that indicates the type of failure that caused the transmission of the message.

[0219] remove Fig.29A In addition to or as an alternative to the information elements of the Failure Information message 212 shown, the wireless node 30 (27) may generate a FailureInformation message using information received via the RLF Notification message 42 (27) received from the wireless relay node 24 (27). Fig.29B A first example of using the RLF Notification message 42 (27) to generate the Failure Information message 212 is understood, where the Failure Information message 212 is shown to include measurement data (e.g., signal quality / strength, such as RSRP, RSRQ, SINR, etc.) of the parent node's upstream link obtained from the RLF Notification message 42 (27). Fig.29C This second example of using the RLF Notification message 42 (27) to generate the FailureInformation message 212 is understood, where the FailureInformation message 212 is shown to include an identifier of the node that detected the radio link problem (eg, RLF).

[0220] Listing 4 shows an example format of an example FailureInformation message.

[0221] List 4

[0222]

[0223]

[0224] It should be understood that in some exemplary configurations, when the wireless node 30 (27) is a wireless terminal, the fault information message 212 may be generated by the fault information message generator 210, such as Fig.28 On the other hand, if the wireless node 30 (27) takes the form of an IAB node, the fault information message 212 may be generated by a similar fault information message generator in the mobile terminal portion of the IAB node.

[0225] Fig.30 shows that a wireless access node such as Fig. 27 and Fig.28 The general representative basic actions or steps performed by the wireless access node 22 (27) of FIG. 30-1 include generating at least one reconfiguration message. The at least one reconfiguration message (such as Fig. 27The at least one reconfiguration message 200 of the present invention is used to activate a first data path 202 and a second data path 204. The first data path 202 and the second data path 204 are established between the wireless access node and the wireless node, and the second data path 204 is relayed by a wireless relay node such as the wireless relay node 24 (27). Action 30-2 includes transmitting the at least one reconfiguration message. Action 30-3 includes receiving a fault information message on the first data path, the fault information message being based on a radio link fault notification message received by the wireless node from the wireless relay node.

[0226] Fig.31 It shows that Fig. 27 and Fig.28 31-1 comprises receiving at least one reconfiguration message, such as reconfiguration message 200, from a wireless access node. Reconfiguration message 200 is used to activate a first data path 202 and a second data path 204. Action 31-2 comprises receiving a notification message from a wireless relay node indicating a radio link failure (RLF) on the second data path. Action 31-3 comprises transmitting a failure information message to the wireless access node using the first data path. As described above, the failure information message may be based on the notification message and indicate a RLF that occurred on the second data path.

[0227] In some implementations, the various exemplary embodiments and modes described herein may be used alone, while in other implementations, one or more of the various exemplary embodiments and modes may be combined so that the features and advantages thereof may be cumulatively utilized.

[0228] The technology disclosed herein provides methods for handling situations where an IAB node loses connection with the network due to a radio link failure. Exemplary, non-limiting methods and features include:

[0229] • The IAB node transmits information representing the radio conditions of its upstream link to its child nodes / UEs.

[0230] • The child node / UE decides whether to stay on the current serving IAB node or whether to reselect another cell / IAB node based on the received information.

[0231] • The child node / UE may wait for a specified duration before making a decision, expecting the serving IAB node to recover the upstream radio link during that duration.

[0232] • A child node / UE can be configured with conditional handover which allows autonomous handover to occur when its parent node suffers from specified radio conditions on its upstream link.

[0233] • A subnode / UE may be configured with multiple signaling paths and may use one of the remaining paths to report the occurrence of a specified radio condition on one of the paths.

[0234] • The configuration for conditional handover includes a set of triggering events, which the child node / UE can evaluate using the received information representing the radio conditions of its upstream link.

[0235] In case multiple paths are configured, the child node / UE may obtain information about RLF-related events occurring on one of the multiple paths and generate / send a fault report including the information.

[0236] Certain units and functions of system 20 may be implemented by electronic machinery. For example, electronic machinery may refer to processor circuits described herein, such as node processor 54, relay node processor 74, and processor 90. In addition, the term "processor circuit" is not limited to meaning one processor, but may include multiple processors, where multiple processors operate at one or more sites. In addition, as used herein, the term "server" is not limited to one server unit, but may cover multiple servers and / or other electronic devices, and may be located at one site or distributed to different sites. Based on these understandings, Fig.32 An example of an electronic machine such as a processor circuit is shown, which includes one or more processors 290, program instruction memory 292; other memory 294 (e.g., RAM, cache, etc.); input / output interfaces 296 and 297, peripheral device interface 298; support circuits 299; and a bus 300 for communication between the aforementioned units. Processor 290 may include processor circuits described herein, such as node processor 54, relay node processor 74, and node processor 90.

[0237] The memory or registers described herein may be depicted as memory 294 or any computer readable medium, which may be one or more of readily available memory such as random access memory (RAM), read-only memory (ROM), floppy disk, hard disk, flash memory, or any other form of digital storage (local or remote), and preferably has non-volatile properties, and thus may include memory. Support circuits 299 are coupled to processor 290 to support the processor in a conventional manner. These circuits include caches, power supplies, clock circuits, input / output circuits and subsystems, etc.

[0238] Although the processes and methods of the disclosed embodiments may be discussed as being implemented as software routines, some of the method steps disclosed therein may be performed in hardware and by a processor running the software. Thus, the embodiments may be implemented in software executed on a computer system, in hardware such as an application specific integrated circuit or other type of hardware, or in a combination of software and hardware. The software routines of the disclosed embodiments can be executed on any computer operating system and can be executed using any CPU architecture.

[0239] The functions of the various elements including functional blocks (including but not limited to those labeled or described as "computers", "processors" or "controllers") may be provided through the use of hardware such as circuit hardware and / or hardware capable of executing software in the form of programming instructions stored on computer-readable media. Therefore, such functions and illustrated functional blocks should be understood to be hardware-implemented and / or computer-implemented, and therefore machine-implemented.

[0240] In terms of hardware implementation, the functional blocks may include or encompass, but are not limited to, digital signal processor (DSP) hardware, a reduced instruction set processor, hardware (e.g., digital or analog) circuits, including but not limited to one or more application specific integrated circuits [ASICs] and / or one or more field programmable gate arrays (FPGAs), and (where appropriate) state machines capable of performing such functions.

[0241] In terms of computer implementation, a computer is generally understood to include one or more processors or one or more controllers, and the terms computer and processor and controller are used interchangeably herein. When provided by a computer or processor or controller, these functions may be provided by a single dedicated computer or processor or controller, by a single shared computer or processor or controller, or by multiple separate computers or processors or controllers (some of which may be shared or distributed). In addition, the use of the term "processor" or "controller" may also be interpreted to refer to other hardware capable of performing such functions and / or executing software, such as the exemplary hardware described above.

[0242] Nodes that communicate using the air interface also have suitable radio communication circuits.In addition, the technology disclosed herein may be further considered to be fully embodied in any form of computer-readable memory, such as a solid-state memory, a magnetic disk, or an optical disk containing a suitable set of computer instructions that will cause a processor to perform the technology described herein.

[0243] In addition, each functional block or various features of the wireless terminal 22, wireless relay node 24 and / or wireless terminal / wireless node 30 used in each of the aforementioned embodiments can be implemented or executed by a circuit (usually an integrated circuit or multiple integrated circuits). The circuit designed to perform the functions described in this specification may include a general-purpose processor, a digital signal processor (DSP), a dedicated or general-purpose integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device or a discrete hardware component or a combination thereof. The general-purpose processor can be a microprocessor, or alternatively, the processor can be a conventional processor, a controller, a microcontroller or a state machine. The general-purpose processor or each of the above-mentioned circuits can be configured by a digital circuit, or can be configured by an analog circuit. In addition, when the technology of making an integrated circuit that replaces the current integrated circuit appears due to the progress of semiconductor technology, the integrated circuit produced by the technology can also be used.

[0244] It should be understood that the technology disclosed herein is intended to solve problems centered on radio communications and is necessarily rooted in computer technology and overcomes problems that occur specifically in radio communications. In addition, the technology disclosed herein improves the basic functions of radio access networks, for example, methods and processes for handling problem conditions such as radio link failures (RLFs) on backhaul links.

[0245] The technology disclosed herein encompasses one or more of the following non-limiting, non-exclusive exemplary embodiments and modes:

[0246] Exemplary embodiment 1: A wireless node, which communicates with a wireless access node of a radio access network (RAN) via at least one wireless relay node and through a radio interface, and the wireless node includes: a receiver circuit, the receiver circuit being configured to: receive a conditional switching configuration message including a trigger condition from the wireless access node; receive a notification message from the wireless relay node, the notification message including information representing a radio condition detected on a path between the wireless relay node and the wireless access node; a processor circuit, the processor circuit being configured to make a determination whether to perform a switch; wherein the determination of whether to perform a switch is based on the trigger condition and the information representing the radio condition.

[0247] Example 2: A wireless node according to Example 1, wherein the trigger condition includes at least one threshold to be compared with signal strength / quality.

[0248] Exemplary embodiment 3: A wireless node according to exemplary embodiment 2, wherein the information representing the radio condition is a radio link failure (RLF), and a predetermined signal quality / strength value is used to compare with the at least one threshold.

[0249] Example 4: A wireless node according to Example 2, wherein the information representative of the radio condition is one or more signal quality / strength values ​​to be compared with the at least one threshold.

[0250] Exemplary embodiment 5: A wireless node according to exemplary embodiment 1, wherein the trigger condition is reception of the notification message, and the information indicating the radio condition is RLF.

[0251] Example 6: A wireless node according to Example 1, wherein the trigger condition is associated with an applicability indication indicating whether the trigger condition is applicable to the notification message.

[0252] Exemplary embodiment 7: A wireless node according to exemplary embodiment 6, wherein the conditional switching configuration message includes multiple trigger conditions, and wherein each of the multiple trigger conditions includes an applicability indication indicating the applicability of the corresponding trigger condition to the notification message.

[0253] Example embodiment 8: A wireless node according to example embodiment 1, wherein the determination whether to perform the handover is made after a timer expires, and the timer starts when or after the notification message is received.

[0254] Exemplary embodiment 9: A wireless node according to exemplary embodiment 8, wherein the timer stops upon receiving a second notification message, the second notification message including information representing a radio condition detected on a path between the wireless relay node and the wireless access node, the information representing the radio condition indicating RLF recovery.

[0255] Example 10: The wireless node of Example 8, wherein the duration of the timer is configured by the wireless access node.

[0256] Exemplary embodiment 11: A method for a wireless node, wherein the wireless node communicates with a wireless access node of a radio access network (RAN) via at least one wireless relay node and through a radio interface, the method comprising: receiving a conditional switching configuration message including a trigger condition from the wireless access node; receiving a notification message from the wireless relay node, the notification message including information representing a radio condition detected on a path between the wireless relay node and the wireless access node; making a determination whether to perform a switch; wherein the determination of whether to perform a switch is based on the trigger condition and the information representing the radio condition.

[0257] Example 12: A method according to example 11, wherein the trigger condition includes at least one threshold to be compared with signal strength / quality.

[0258] Exemplary embodiment 13: A method according to exemplary embodiment 12, wherein the information representing the radio condition is a radio link failure (RLF), and a predetermined signal quality / strength value is used to compare with the at least one threshold.

[0259] Example 14: A method according to Example 12, wherein the information representing the radio condition is one or more signal quality / strength values ​​to be compared with the at least one threshold.

[0260] Example 15: A method according to Example 11, wherein the trigger condition is receiving the notification message, and the information indicating the radio condition is RLF.

[0261] Example 16: A method according to example 11, wherein the trigger condition is associated with an indication indicating whether the trigger condition is applicable to the notification message.

[0262] Exemplary embodiment 17: A method according to exemplary embodiment 16, wherein the conditional switching configuration message includes multiple trigger conditions, and wherein each of the multiple trigger conditions includes an applicability indication indicating the applicability of the corresponding trigger condition to the notification message.

[0263] Example embodiment 18: A method according to example embodiment 11, wherein the determination whether to perform the handover is made after a timer expires, and the timer starts when or after the notification message is received.

[0264] Exemplary embodiment 19: A method according to exemplary embodiment 18, wherein the timer is stopped upon receiving a second notification message, the second notification message including information representing a radio condition detected on a path between the wireless relay node and the wireless access node, the information representing the radio condition indicating RLF recovery.

[0265] Example 20: A method according to Example 18, wherein the duration of the timer is configured by the wireless access node.

[0266] Exemplary embodiment 21: A wireless access node of a wireless access network (RAN), the wireless access node communicating with a wireless node via at least one wireless relay node and through a radio interface, the wireless access node comprising: a processor circuit, the processor circuit being configured to generate a conditional switching configuration message including a trigger condition; a transmitter circuit, the transmitter circuit being configured to transmit the conditional switching configuration message to the wireless node; wherein a notification message is sent by the wireless relay node to the wireless node, the notification message including information representing a radio condition detected on a path between the wireless relay node and the wireless access node, and; the trigger condition and the information representing the radio condition enable the wireless node to determine whether the wireless node performs a switch.

[0267] Example embodiment 22: The wireless access node of example embodiment 21, wherein the trigger condition includes at least one threshold to be compared with signal strength / quality.

[0268] Example 23: A wireless access node according to Example 22, wherein the information representing the radio condition is a radio link failure (RLF), and a predetermined signal quality / strength value is used to compare with the at least one threshold.

[0269] Example embodiment 24: A wireless access node according to example embodiment 22, wherein the information representative of the radio condition is one or more signal quality / strength values ​​to be compared with the at least one threshold.

[0270] Example 25: The wireless access node according to Example 21, wherein the trigger condition is reception of the notification message, and the information indicating the radio condition is RLF.

[0271] Example 26: A wireless access node according to Example 21, wherein the trigger condition is associated with an indication indicating whether the trigger condition is applicable to the notification message.

[0272] Exemplary embodiment 27: A wireless access node according to exemplary embodiment 26, wherein the conditional switching configuration message includes multiple trigger conditions, and wherein each of the multiple trigger conditions includes an applicability indication indicating the applicability of the corresponding trigger condition to the notification message.

[0273] Example embodiment 28: A wireless access node according to example embodiment 21, wherein the determination whether to perform a handover is made after a timer expires, and the timer starts when or after the notification message is received.

[0274] Exemplary embodiment 29: A wireless access node according to exemplary embodiment 28, wherein the timer stops when the wireless node receives a second notification message, the second notification message including information representing a radio condition detected on a path between the wireless relay node and the wireless access node, the information representing the radio condition indicating RLF recovery.

[0275] Example 30: The wireless access node of Example 28, wherein the duration of the timer is configured by the wireless access node to the wireless node.

[0276] Exemplary embodiment 31: A method for a wireless access node of a wireless access network (RAN), wherein the wireless access node communicates with a wireless node via at least one wireless relay node and through a radio interface, the method comprising: generating a conditional switching configuration message including a trigger condition; transmitting the conditional switching configuration message to the wireless node; wherein: a notification message is sent by the wireless relay node to the wireless node, the notification message including information representing a radio condition detected on a path between the wireless relay node and the wireless access node, and; the trigger condition and the information representing the radio condition enable the wireless node to make a determination as to whether the wireless node performs a switch.

[0277] Example 32: A method according to example 31, wherein the trigger condition includes at least one threshold to be compared with signal strength / quality.

[0278] Exemplary embodiment 33: A method according to exemplary embodiment 32, wherein the information representing the radio condition is a radio link failure (RLF), and a predetermined signal quality / strength value is used to compare with the at least one threshold.

[0279] Example 34: A method according to Example 32, wherein the information representing the radio condition is one or more signal quality / strength values ​​to be compared with the at least one threshold.

[0280] Example 35: A method according to Example 31, wherein the trigger condition is receiving the notification message, and the information indicating the radio condition is RLF.

[0281] Exemplary embodiment 36: A method according to exemplary embodiment 31, wherein the trigger condition is associated with an indication indicating whether the trigger condition is applicable to the notification message.

[0282] Exemplary embodiment 37: A wireless access node according to exemplary embodiment 36, wherein the conditional switching configuration message includes multiple trigger conditions, and wherein each of the multiple trigger conditions includes an applicability indication indicating the applicability of the corresponding trigger condition to the notification message.

[0283] Example embodiment 38: A method according to example embodiment 31, wherein the determination whether to perform the handover is made after a timer expires, and the timer starts when or after the notification message is received.

[0284] Exemplary embodiment 39: A method according to exemplary embodiment 38, wherein the timer stops when the wireless node receives a second notification message, the second notification message including information representing a radio condition detected on a path between the wireless relay node and the wireless access node, the information representing the radio condition indicating RLF recovery.

[0285] Example 40: A method according to Example 38, wherein the duration of the timer is configured by the wireless access node to the wireless node.

[0286] Exemplary embodiment 41: A wireless node, which communicates with a wireless access node of a radio access network (RAN) via a radio interface, the wireless node comprising: a receiver circuit, the receiver circuit being configured to: receive at least one reconfiguration message from the wireless access node, the reconfiguration message activating a first data path and a second data path, the first data path and the second data path being established between the wireless access node and the wireless node, the second data path being relayed by a wireless relay node, and; receive a notification message from the wireless relay node indicating a radio link failure (RLF) on the second data path; a processor circuit, the processor circuit being configured to generate a fault information message; a transmitter circuit, the transmitter circuit being configured to transmit the fault information message to the wireless access node using the first data path; wherein the fault information message is based on the notification message and indicates the RLF occurring on the second data path.

[0287] Exemplary embodiment 42: A wireless node according to exemplary embodiment 41, wherein the fault information message includes a type of fault, and the type of fault indicates whether the transmission of the fault information message is caused by the notification message.

[0288] Exemplary embodiment 43: A wireless node according to exemplary embodiment 41, wherein the notification message includes location information identifying the node detecting the RLF on the second data path, and the fault information message includes the location information.

[0289] Exemplary embodiment 44: A wireless node according to exemplary embodiment 41, wherein the notification message includes one or more measurement values ​​of signal strength / quality, and the fault information message includes the one or more measurement values.

[0290] Exemplary embodiment 45: A method for a wireless node, wherein the wireless node communicates with a wireless access node of a radio access network (RAN) via a radio interface, the method comprising: receiving at least one reconfiguration message from the wireless access node, the reconfiguration message activating a first data path and a second data path, the first data path and the second data path being established between the wireless access node and the wireless node, the second data path being relayed by a wireless relay node, and; receiving a notification message from the wireless relay node indicating a radio link failure (RLF) on the second data path; generating a fault information message; transmitting the fault information message to the wireless access node using the first data path; wherein the fault information message is based on the notification message and indicates the RLF occurring on the second data path.

[0291] Exemplary embodiment 46: A method according to exemplary embodiment 45, wherein the fault information message includes a type of fault, and the type of fault indicates whether the transmission of the fault information message is caused by the notification message.

[0292] Exemplary embodiment 47: A method according to exemplary embodiment 45, wherein the notification message includes location information identifying the node on the second data path that detects the RLF, and the fault information message includes the location information.

[0293] Exemplary embodiment 48: A method according to exemplary embodiment 45, wherein the notification message includes one or more measurement values ​​of signal strength / quality, and the fault information message includes the one or more measurement values.

[0294] Exemplary embodiment 49: A wireless access node of a radio access network (RAN), the wireless access node communicating with a wireless node via a radio interface, the wireless access node comprising: a processor circuit, the processor circuit being configured to generate at least one reconfiguration message, the at least one reconfiguration message activating a first data path and a second data path, the first data path and the second data path being established between the wireless access node and the wireless node, the second data path being relayed by a wireless relay node; a transmitter circuit, the transmitter circuit being configured to transmit the at least one reconfiguration message; a receiver circuit, the receiver circuit being configured to receive a fault information message on the first data path; wherein the fault information message is based on a notification message received by the wireless node from the wireless relay node, the notification message indicating a radio link failure (RLF) on the second data path.

[0295] Example 50: A wireless access node according to Example 49, wherein the fault information message includes a type of fault, and the type of fault indicates whether the transmission of the fault information message is caused by the notification message.

[0296] Exemplary embodiment 51: A wireless access node according to exemplary embodiment 49, wherein the notification message includes location information identifying the node detecting the RLF on the second data path, and the fault information message includes the location information.

[0297] Example embodiment 52: A wireless access node according to example embodiment 49, wherein the notification message includes one or more measurement values ​​of signal strength / quality, and the fault information message includes the one or more measurement values.

[0298] Exemplary embodiment 53: A method for a wireless access node of a wireless access network (RAN), wherein the wireless access node communicates with a wireless node via a radio interface, the method comprising: generating at least one reconfiguration message, wherein the at least one reconfiguration message activates a first data path and a second data path, wherein the first data path and the second data path are established between the wireless access node and the wireless node, and the second data path is relayed by a wireless relay node; transmitting the at least one reconfiguration message; receiving a fault information message on the first data path; wherein the fault information message is based on a notification message received by the wireless node from the wireless relay node, and the notification message indicates a radio link failure (RLF) on the second data path.

[0299] Exemplary embodiment 54: A method according to exemplary embodiment 53, wherein the fault information message includes a type of fault, and the type of fault indicates whether the transmission of the fault information message is caused by the notification message.

[0300] Exemplary embodiment 55: A method according to exemplary embodiment 54, wherein the notification message includes location information identifying the node on the second data path that detects the RLF, and the fault information message includes the location information.

[0301] Example 56: A method according to example embodiment 53, wherein the notification message includes one or more measurement values ​​of signal strength / quality, and the fault information message includes the one or more measurement values.

[0302] Exemplary embodiment 57: A wireless node, which communicates with a wireless access node of a radio access network (RAN) via an integrated access and backhaul (IAB) node and through a radio interface, the wireless node comprising: a receiver circuit, the receiver circuit being configured to: receive a reconfiguration message including a conditional switching configuration from the wireless access node, the conditional switching configuration including a trigger condition and a configuration of a candidate target cell, the trigger condition including at least one threshold; receive a notification message from the IAB node, the notification message including information representing radio conditions measured on a path between the IAB node and the wireless access node, and; a processor circuit, the processor circuit being configured to perform switching using the configuration of the candidate target cell based on the trigger condition and the information.

[0303] Example embodiment 58: A wireless node according to example embodiment 57, wherein the information corresponds to signal strength / quality, and the switching is performed by evaluating the signal strength / quality and / or the at least one threshold.

[0304] Exemplary embodiment 59: A wireless node according to exemplary embodiment 57, wherein the information corresponds to a radio link failure (RLF), and the switching is performed by evaluating a predetermined signal quality / strength value and / or the at least one threshold.

[0305] Exemplary embodiment 60: A wireless node according to exemplary embodiment 57, wherein the trigger condition also includes an applicability indication indicating whether the trigger condition is applicable to the notification message.

[0306] Exemplary embodiment 61: A method for a wireless node, wherein the wireless node communicates with a wireless access node of a radio access network (RAN) via at least one integrated access and backhaul (IAB) node and through a radio interface, the method comprising: receiving a reconfiguration message including a conditional switching configuration from the wireless access node, the conditional switching configuration including a trigger condition and a configuration of a candidate target cell; receiving a notification message from the IAB node, and; making a determination whether to use the conditional switching configuration to perform a switch; wherein the trigger condition includes at least one threshold; the notification message includes information representing a radio condition detected on a path between the wireless relay node and the wireless access node, and; the determination is based on the at least one threshold and the information.

[0307] Example embodiment 61: A method according to example embodiment 60, wherein the information corresponds to signal strength / quality, and the determination is performed by comparing the signal strength / quality and the at least one threshold.

[0308] Example embodiment 62: A method according to example embodiment 60, wherein the information corresponds to a radio link failure (RLF), and the determination is performed by comparing a predetermined signal quality / strength value and the at least one threshold.

[0309] Exemplary embodiment 63: A method according to exemplary embodiment 60, wherein the trigger condition also includes an applicability indication indicating whether the trigger condition is applicable to the notification message.

[0310] Exemplary embodiment 64: A wireless access node of a radio access network (RAN), the wireless access node communicating with a wireless node via an integrated access and backhaul (IAB) node and through a radio interface, the wireless access node comprising: a processor circuit, the processor circuit being configured to generate a reconfiguration message including a conditional switching configuration, the conditional switching configuration including a trigger condition and a configuration of a candidate target cell, the trigger condition including at least one threshold; a transmitter circuit, the transmitter circuit being configured to transmit the reconfiguration message to the wireless node; wherein the wireless node uses the trigger condition and information to perform switching using the configuration of the candidate target cell, the information representing radio conditions measured on a path between the IAB node and the wireless access node, and; the information is included in a notification message sent by the IAB node to the wireless node.

[0311] Example embodiment 65: A wireless access node according to example embodiment 64, wherein the information corresponds to signal strength / quality, and the switching is performed by evaluating the signal strength / quality and / or the at least one threshold.

[0312] Example embodiment 66: A wireless access node according to example embodiment 64, wherein the information corresponds to a radio link failure (RLF), and the determination is performed by evaluating a predetermined signal quality / strength value and / or the at least one threshold.

[0313] Example 67: A wireless access node according to Example 64, wherein the trigger condition also includes an applicability indication indicating whether the trigger condition is applicable to the notification message.

[0314] Exemplary embodiment 68: A method for a wireless access node of a wireless access network (RAN), wherein the wireless access node communicates with a wireless node via an integrated access and backhaul (IAB) node and through a radio interface, the method comprising: generating a reconfiguration message including a conditional switching configuration, the conditional switching configuration including a trigger condition and a configuration of a candidate target cell, the trigger condition including at least one threshold; sending the reconfiguration message to the wireless node; wherein: the wireless node uses the trigger condition and information to perform switching using the configuration of the candidate target cell, the information representing radio conditions measured on a path between the IAB node and the wireless access node, and; the information is included in a notification message sent by the IAB node to the wireless node.

[0315] Example embodiment 69: A method according to example embodiment 68, wherein the information corresponds to signal strength / quality, and the switching is performed by evaluating the signal strength / quality and / or the at least one threshold.

[0316] Exemplary embodiment 70: A method according to exemplary embodiment 68, wherein the information corresponds to a radio link failure (RLF), and the determination is performed by evaluating a predetermined signal quality / strength value and / or the at least one threshold.

[0317] Exemplary embodiment 71: A method according to exemplary embodiment 68, wherein the trigger condition also includes an applicability indication indicating whether the trigger condition is applicable to the notification message.

[0318] Exemplary embodiment 72: A wireless node, which communicates with a wireless access node of a radio access network (RAN) via a radio interface, the wireless node comprising: a processor circuit, the processor circuit being configured to establish a dual connection (DC) with the radio access node comprising a first connection and a second connection, the first connection being relayed by an integrated access and backhaul (IAB) node; a receiver circuit, the receiver circuit being configured to receive a notification message indicating a radio link failure (RLF) on the first connection from the IAB node, and; a transmitter circuit, the transmitter circuit being configured to transmit a fault information message to the wireless access node using the second connection based on the notification message, wherein: the fault information message includes information representing the RLF.

[0319] Exemplary embodiment 73: A wireless node according to exemplary embodiment 72, wherein the information representing the RLF includes a type of fault, and the type of fault indicates whether the transmission of the fault information message is caused by the RLF on the return link indicated in the notification message.

[0320] Exemplary embodiment 74: A wireless node according to exemplary embodiment 72, wherein the notification message includes information identifying the node that detects the RLF on the first connection, and the information indicating the RLF includes the information identifying the node.

[0321] Example embodiment 75: A wireless node according to example embodiment 72, wherein the notification message includes one or more measurement values ​​of signal strength / quality, and the information representing the RLF includes the one or more measurement values.

[0322] Exemplary embodiment 76: A method for a wireless node, which communicates with a wireless access node of a radio access network (RAN) via a radio interface, the method comprising: establishing a dual connection (DC) with the radio access node comprising a first connection and a second connection, the first connection being relayed by an integrated access and backhaul (IAB) node; receiving a notification message indicating a radio link failure (RLF) on the first connection from the IAB node; based on the notification message, transmitting a fault information message to the wireless access node using the second connection; wherein the fault information message includes information representing the RLF.

[0323] Exemplary embodiment 77: A method according to exemplary embodiment 76, wherein the information representing the RLF includes a type of fault, and the type of fault indicates whether the transmission of the fault information message is caused by the RLF on the return link indicated in the notification message.

[0324] Example embodiment 78: A method according to example embodiment 76, wherein the notification message includes information identifying a node on the first connection that detects the RLF, and the information indicating the RLF includes the information identifying the node.

[0325] Example embodiment 79: A method according to example embodiment 76, wherein the notification message includes one or more measurement values ​​of signal strength / quality, and the information representing the RLF includes the one or more measurement values.

[0326] Exemplary embodiment 80: A wireless access node of a radio access network (RAN), the wireless access node communicating with a wireless node via a radio interface, the wireless access node comprising: a processor circuit, the processor circuit being configured to establish a dual connection (DC) with the wireless node comprising a first connection and a second connection, the first connection being relayed by an integrated access and backhaul (IAB) node, and; a receiver circuit, the receiver circuit being configured to receive a fault information message on the second connection; wherein the fault information message is based on a notification message received by the wireless node from the IAB node, the notification message indicating a radio link failure (RLF) on the first connection, and; the fault information message includes information representing the RLF.

[0327] Exemplary embodiment 81: A wireless access node according to exemplary embodiment 80, wherein the information representing the RLF includes a type of fault, and the type of fault indicates whether the transmission of the fault information message is caused by the RLF on the return link indicated in the notification message.

[0328] Exemplary embodiment 82: A wireless access node according to exemplary embodiment 80, wherein the notification message includes information identifying a node detecting the RLF on the first connection, and the information indicating the RLF includes the information identifying the node.

[0329] Example embodiment 83: A wireless access node according to example embodiment 80, wherein the notification message includes one or more measurement values ​​of signal strength / quality, and the information representing the RLF includes the one or more measurement values.

[0330] Exemplary embodiment 84: A method for a wireless access node of a radio access network (RAN), the wireless access node communicating with a wireless node via a radio interface, the method comprising: establishing a dual connection (DC) with the wireless node comprising a first connection and a second connection, the first connection being relayed by an integrated access and backhaul (IAB) node, and; receiving a fault information message on the second connection; wherein the fault information message is based on a notification message received by the wireless node from the wireless relay node, the notification message indicating a radio link failure (RLF) on the first connection, and; the fault information message includes information representing the RLF.

[0331] Exemplary embodiment 85: A method according to exemplary embodiment 84, wherein the information representing the RLF includes a type of fault, and the type of fault indicates whether the transmission of the fault information message is caused by the RLF on the return link indicated in the notification message.

[0332] Exemplary embodiment 86: A method according to exemplary embodiment 84, wherein the notification message includes information identifying a node on the first connection that detects the RLF, and the information representing the RLF includes location information identifying the node.

[0333] Example embodiment 87: A method according to example embodiment 84, wherein the notification message includes one or more measurement values ​​of signal strength / quality, and the information representing the RLF includes the one or more measurement values.

[0334] One or more of the following documents may be relevant to the technology disclosed herein (all of which are incorporated herein by reference in their entirety):

[0335]

[0336]

[0337] Although the above description contains many specific instructions, these should not be interpreted as limiting the scope of the technology disclosed herein, but only provide illustrations for some current preferred embodiments of the technology disclosed herein. Therefore, the scope of the technology disclosed herein should be determined by the attached claims and their legal equivalents. Therefore, it should be understood that the scope of the technology disclosed herein fully covers other embodiments that may become obvious to those skilled in the art, and therefore the scope of the technology disclosed herein is limited only by the attached claims, where the reference element in the singular form does not mean "only one" (unless explicitly stated as such), but refers to "one or more". The above embodiments can be combined with each other. All structural, chemical and functional equivalents of the elements of the above preferred embodiments known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the present claims. In addition, a device or method does not necessarily solve every problem that the technology disclosed herein seeks to solve, because it will be covered by the present claims. In addition, the elements, components or method steps of the present disclosure are not intended to be dedicated to the public, regardless of whether the elements, components or method steps are explicitly stated in the claims.

[0338] <Cross Reference>

[0339] This nonprovisional application claims priority under 35 U.S.C. 119 to provisional application No. 62 / 842,374, filed on May 2, 2019, the entire contents of which are hereby incorporated by reference.

Claims

1. A wireless node, the wireless node communicating with a wireless access node of a radio access network RAN ​​via a radio interface, the wireless node include: A processor circuit, the processor circuit being configured to establish a dual connection DC including a first connection and a second connection with the radio access node, the first connection being relayed by an integrated access and backhaul IAB node; a receiver circuit configured to receive a notification message indicating a radio link failure RLF on the first connection from the IAB node, and; a transmitter circuit configured to transmit a fault information message to the radio access node using the second connection based on the notification message, wherein: The fault information message includes a fault type indicating that transmission of the fault information message is caused by reception of the notification message on the first connection, and The fault type included in the fault information message is set from a plurality of given fault types, and The plurality of given fault types include a fault type indicating the RLF and a fault type indicating a fault other than the RLF.

2. The wireless node of claim 1, wherein the notification message includes information identifying a node on the first connection that detects the RLF, and the failure information message further includes the information identifying the node.

3. The wireless node of claim 1, wherein the notification message includes one or more measurements of signal strength / quality, and the fault information message further includes the one or more measurements.

4. A method for a wireless node, the wireless node communicating with a wireless access node of a radio access network RAN ​​via a radio interface, the method include: Establishing a dual connection DC including a first connection and a second connection with the wireless access node, wherein the first connection is relayed by an integrated access and backhaul IAB node; receiving a notification message indicating a radio link failure (RLF) on the first connection from the IAB node; Based on the notification message, using the second connection to transmit a fault information message to the wireless access node; wherein the fault information message comprises a fault type, the fault type indicating that the transmission of the fault information message is caused by receiving the notification message on the first connection, and The fault type included in the fault information message is set from a plurality of given fault types, and The plurality of given fault types include a fault type indicating the RLF and a fault type indicating a fault other than the RLF.

5. A radio access node of a radio access network RAN, the radio access node communicating with a wireless node via a radio interface, the radio access node include: a processor circuit configured to establish a dual connection DC including a first connection and a second connection with the wireless node, the first connection being relayed by an integrated access and backhaul IAB node, and; a receiver circuit configured to receive a fault information message on the second connection; wherein the failure information message is based on a notification message received by the wireless node from the IAB node, the notification message indicating a radio link failure RLF on the first connection, and; The fault information message includes a fault type indicating that transmission of the fault information message is caused by reception of the notification message on the first connection, and The fault type included in the fault information message is set from a plurality of given fault types, and The plurality of given fault types include a fault type indicating the RLF and a fault type indicating a fault other than the RLF.

6. The radio access node according to claim 5, wherein the notification message includes information identifying a node on the first connection that detects the RLF, and the fault information message further includes the information identifying the node.

7. The wireless access node of claim 5, wherein the notification message includes one or more measurements of signal strength / quality, and the fault information message further includes the one or more measurements.