WO2021196197A1

WO2021196197A1 - Radio link failure (rlf) notification method and apparatus

Info

Publication number: WO2021196197A1
Application number: PCT/CN2020/083295
Authority: WO
Inventors: 马川; 郝金平; 刘琼; 谭巍
Original assignee: 华为技术有限公司
Priority date: 2020-04-03
Filing date: 2020-04-03
Publication date: 2021-10-07

Abstract

Provided are a radio link failure (RLF) notification method and apparatus, which facilitate the determination of a failure path. The method comprises: a first node pre-configuring path failure information of a second node for the second node, wherein the path failure information is used for indicating the failure of at least one uplink path; the at least one uplink path refers to at least one uplink path that includes a link subjected to radio link failure (RLF); and the link subjected to RLF is a link between the second node and the upstream node of the second node, such that the second node determines a failure path.

Description

Radio link failure RLF notification method and device

Technical field

This application relates to the field of communications, and more specifically, to a method and device for RLF notification of radio link failure.

Background technique

With the continuous development of mobile communication technology, spectrum resources are becoming increasingly scarce. In order to improve spectrum utilization, future base station deployment will be more intensive. In addition, dense deployment can also avoid the appearance of coverage holes. Under the traditional cellular network architecture, the base station establishes a connection with the core network through optical fiber. However, in many scenarios, the deployment cost of optical fiber is very high. The wireless relay node (RN) establishes a connection with the core network through a wireless backhaul link, which can save part of the fiber deployment cost.

Generally, the relay node establishes a wireless backhaul link with one or more upper-level nodes, and accesses the core network through the upper-level nodes. The upper-level node can perform certain control (for example, data scheduling, timing modulation, power control, etc.) on the relay node through a variety of signaling. In addition, the relay node can provide services for multiple subordinate nodes. The upper node of the relay node may be a base station or another relay node; the lower node of the relay node may be a terminal or another relay node. Considering the high bandwidth of future wireless networks, 5G new radio (NR) is considering the introduction of an integrated access and backhaul (IAB) solution to further reduce deployment costs and increase deployment flexibility. Integrated access and backhaul relay, namely IAB node (IAB-node).

In the IAB network, a radio link failure (radio link failure, RLF) may occur on the backhaul link. IAB-node can perform RLF monitoring of the backhaul link (RLF monitoring). When RLF is found on the backhaul link, the IAB-node can send an RLF notification (RLF notification) to its child nodes. Two types of RLF notifications are currently used in IAB networks. According to the content included in the RLF notification, the RLF notification can be divided into two types. However, both of these two RLF notification methods have limitations and are not conducive to determining the failure path.

Summary of the invention

In view of this, the present application provides a method and device for RLF notification of a radio link failure, which helps the IAB node to determine the failure path.

In a first aspect, a method for RLF notification of a radio link failure is provided, which includes: a first node (or a module in the first node, such as a chip) sending a first configuration message to a second node, and the first node The configuration message includes path failure information of the second node, the path failure information is used to indicate that at least one uplink path fails, and the at least one uplink path refers to at least one uplink path that includes an RLF link where a radio link failure occurs, The RLF occurrence link is a link between the second node and an upstream node of the second node. Compared with the prior art that only knows the link where the RLF occurs, the RLF notification method provided in the embodiment of the present application not only enables the second node to know the link where the RLF occurs, but also determines the corresponding failed uplink path.

Optionally, first, the first node determines the first configuration message, and then sends the first configuration message to the second node.

Optionally, the first configuration message further includes a first indication, and the first indication is used to indicate the type of RLF notification. The first indication is used to indicate that the RLF notification is a type 1 RLF notification. In this way, the second node knows that the first configuration message sent by the first node is applicable to the scenario where the type 1 RLF notification is used for the RLF notification.

Optionally, the first configuration message is a radio resource control RRC message or a MAC layer message. Therefore, the implementation form of the first configuration message is more flexible.

In a second aspect, an RLF notification method for radio link failure is provided, which includes: first, a second node (or a module in the second node, such as a chip) receives a first configuration message from the first node, so The first configuration message includes path failure information related to the second node, and the path failure information is used to indicate that at least one uplink path fails, and the at least one uplink path refers to the RLF link that includes the radio link failure. At least one uplink path, the RLF link is the link between the second node and the upstream node of the second node; then, receiving a first notification message from the parent node of the second node, and the first A notification message is used to notify the second node that RLF occurs on the link; finally, according to the first configuration message and the first notification message, it is determined that the at least one uplink path fails. Compared with the prior art that only knows the link where the RLF occurs, the RLF notification method provided in the embodiment of the present application not only enables the second node to know the link where the RLF occurs, but also determines the corresponding failed uplink path.

In a possible implementation manner, the method further includes: the second node sending a second notification message to a child node of the second node, and the second notification message is used to send a notification message to the child node of the second node. The child node notifies the link that RLF occurs. Here, the second node may also send an RLF notification to the child node.

Optionally, the first notification message includes an identifier of the link.

Optionally, the first configuration message further includes a first indication, and the first indication is used to indicate the type of RLF notification. In this way, the second node knows that the first configuration message sent by the first node is applicable to the scenario where the type 1 RLF notification is used for the RLF notification.

In a third aspect, a method for RLF notification of radio link failure is provided, which includes: a first node (or a module in the first node, such as a chip) sending a second configuration message to a second node, and the second node The configuration message includes the notification information of the first child node of the second node, the notification information is used to indicate the uplink path set notified by the RLF, and the RLF notification is the upstream node of the second node and the second node RLF notification when RLF occurs on the inter-link. In this way, the second node only needs to know that the uplink path set is notified to the first child node, and there is no need to notify the identifiers of uplink paths other than the uplink path set, thereby avoiding carrying unnecessary path information.

Alternatively, the notification information is used to indicate that in a case where an RLF occurs on the link between the second node and the upstream node of the second node, at least one uplink path through the first child node.

Optionally, first, the first node determines the second configuration message, and then sends the second configuration message to the second node.

Optionally, the second configuration message further includes the identifier of each uplink path in the uplink path set.

Optionally, the second configuration message further includes a second indication, and the second indication is used to indicate the type of RLF notification. The second indication is used to indicate that the RLF notification is a type 2 RLF notification. In this way, the second node is made aware that the first configuration message sent by the first node is suitable for the scenario where the type 2 RLF notification is used for the RLF notification.

Optionally, the second configuration message may be an RRC message or a MAC layer message. Therefore, the implementation form of the second configuration message is more flexible.

In a fourth aspect, an RLF notification method for radio link failure is provided, including: first, a second node (or a module in the second node, such as a chip) receives a second configuration message from the first node, so The second configuration message includes notification information of the first child node of the second node, the notification information is used to indicate the uplink path set notified by the RLF, and the RLF notification is the second node and the second node RLF notification in the case of RLF occurrence on the link between the upstream nodes of the RLF occurs on the link; finally, a third notification message is sent to the first child node of the second node. The third notification message includes the identifier of each uplink path in the uplink path set, and does not need to carry other than the uplink path set. The identifier of the upstream path of the network, thereby avoiding carrying unnecessary path information.

In a fifth aspect, an RLF notification device for radio link failure is provided. The device includes a module for executing the method in the first aspect or any possible implementation of the first aspect; or, including a module for executing the first aspect. The second aspect or the module of the method in any possible implementation of the second aspect; or, the module for executing the method in the third aspect or any of the possible implementation of the third aspect; or, the module for executing the method in any possible implementation of the third aspect or the third aspect; Module of the method in the foregoing fourth aspect or any possible implementation of the fourth aspect.

In a sixth aspect, an RLF notification device for radio link failure is provided, which includes a processor. The processor is coupled with the memory, and can be used to execute instructions in the memory to implement the method in any one of the foregoing first aspect or the third aspect. Optionally, the device further includes a memory. Optionally, the device further includes a communication interface, and the processor is coupled with the communication interface.

In one implementation, the device is the first node. When the device is the first node, the communication interface may be a transceiver, or an input/output interface.

In another implementation manner, the device is a chip configured in the first node. When the device is a chip configured in the first node, the communication interface may be an input/output interface.

Optionally, the transceiver may be a transceiver circuit. Optionally, the input/output interface may be an input/output circuit.

Exemplarily, the communication device may be a network device. In a seventh aspect, an RLF notification device for radio link failure is provided, including a processor. The processor is coupled with the memory and can be used to execute instructions in the memory to implement the method in any one of the foregoing second aspect or the fourth aspect. Optionally, the device further includes a memory. Optionally, the device further includes a communication interface, and the processor is coupled with the communication interface.

In one implementation, the device is the second node. When the device is the second node, the communication interface may be a transceiver, or an input/output interface.

In another implementation manner, the device is a chip configured in the second node. When the device is a chip configured in the second node, the communication interface may be an input/output interface.

Exemplarily, the communication device may be a network device.

In an eighth aspect, a processor is provided, including: an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive a signal through the input circuit, and transmit a signal through the output circuit, so that the processor executes any one of the above-mentioned first aspect to the fourth aspect in any one of the possible implementation manners Methods.

In the specific implementation process, the above-mentioned processor may be a chip, the input circuit may be an input pin, the output circuit may be an output pin, and the processing circuit may be a transistor, a gate circuit, a flip-flop, and various logic circuits. The input signal received by the input circuit may be received and input by, for example, but not limited to, a receiver, and the signal output by the output circuit may be, for example, but not limited to, output to the transmitter and transmitted by the transmitter, and the input circuit and output The circuit can be the same circuit, which is used as an input circuit and an output circuit at different times. The embodiments of the present application do not limit the specific implementation manners of the processor and various circuits.

In a ninth aspect, an apparatus is provided, including a processor and a memory. The processor is used to read instructions stored in the memory, receive signals through a receiver, and transmit signals through a transmitter, so as to execute the method in any one of the possible implementations of the first aspect to the fourth aspect .

Optionally, there are one or more processors, and one or more memories.

Optionally, the memory may be integrated with the processor, or the memory and the processor may be provided separately.

In the specific implementation process, the memory can be a non-transitory (non-transitory) memory, such as a read only memory (ROM), which can be integrated with the processor on the same chip, or can be set in different On the chip, the embodiment of the present application does not limit the type of the memory and the setting mode of the memory and the processor.

It should be understood that the related data interaction process, for example, sending instruction information may be a process of outputting instruction information from the processor, and receiving capability information may be a process of receiving input capability information by the processor. Specifically, the processed output data may be output to the transmitter, and the input data received by the processor may come from the receiver. Among them, the transmitter and receiver can be collectively referred to as a transceiver.

The device in the aforementioned ninth aspect may be a chip, and the processor may be implemented by hardware or software. When implemented by hardware, the processor may be a logic circuit, an integrated circuit, etc.; when implemented by software The processor may be a general-purpose processor, which is implemented by reading the software code stored in the memory. The memory may be integrated in the processor, may be located outside the processor, and exist independently.

In a tenth aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores a computer program or instruction. When the computer program or instruction is executed, any one of the first aspect to the fourth aspect is realized. The method in any possible implementation of the aspect.

In an eleventh aspect, a computer program product containing instructions is provided, when the instructions are executed, the method in any possible implementation manner of any one of the first to fourth aspects is implemented.

In a twelfth aspect, a communication chip is provided, in which instructions are stored, which when run on a computer device, cause the communication chip to execute the method in the first aspect or any possible implementation of the first aspect, Or, the communication chip is caused to execute the method in the foregoing third aspect or any possible implementation manner of the third aspect.

In a thirteenth aspect, a communication chip is provided, in which instructions are stored, which when run on a computer device, cause the communication chip to execute the method in the second aspect or any possible implementation of the second aspect, The communication chip is caused to execute the method in the foregoing fourth aspect or any possible implementation manner of the fourth aspect.

In a fourteenth aspect, a communication system is provided. The communication system includes a first node and one or more second nodes.

Optionally, the communication system further includes other devices that communicate with the first node and/or the second node.

Description of the drawings

Figure 1 is a schematic diagram of an IAB architecture applying this application;

Figure 2 is a schematic diagram of another IAB architecture to which this application is applied;

Figure 3 is a schematic diagram of an example of an IAB network;

FIG. 4 is a schematic interaction diagram of an RLF notification method according to an embodiment of the present application;

FIG. 5 is a schematic interaction diagram of another RLF notification method according to an embodiment of the present application;

Fig. 6 is a schematic block diagram of an RLF notification device according to an embodiment of the present application;

Fig. 7 is a schematic structural diagram of an RLF notification device according to an embodiment of the present application;

Fig. 8 is a schematic structural diagram of another RLF notification device according to an embodiment of the present application.

Detailed ways

The technical solution in this application will be described below in conjunction with the accompanying drawings.

In the description of the embodiments of the present application, unless otherwise specified, "plurality" or "multiple number" means two or more. In addition, "at least one" can be replaced with "one or more".

It should be understood that the names of all nodes and messages in this application are only the names set by this application for the convenience of description. The names in the actual network may be different. It should not be understood that this application limits the names of various nodes and messages. On the contrary, Any name that has the same or similar function as the node or message used in this application is regarded as a method or equivalent replacement of this application, and is within the protection scope of this application, and will not be repeated hereafter.

Considering the high bandwidth of future wireless networks, the 5th generation (5G) new radio (NR) is considering the introduction of integrated access and backhaul (IAB) solutions to further reduce deployment costs and increase Deployment flexibility, and thus the introduction of integrated access and backhaul relays, this application refers to the relay nodes that support integrated access and backhaul as IAB nodes (IAB nodes) to distinguish long-term evolution (long-term evolution). Term evolution, LTE) relay, the system including IAB node is also called relay system. There are two types of nodes in the IAB network: IAB-donor and IAB-node. IAB-donor is directly connected to the core network, which can provide access services for the UE, and can also provide the IAB-node with a backhaul exit to the core network. The IAB-node is not directly connected to the core network, but is connected to the IAB-donor through (single-hop or multi-hop) wireless backhaul, and the IAB-donor backhauls to the core network. The IAB-node can provide access services for the UE, and can also provide the relay of the backhaul link for other IAB-nodes. From the perspective of the UE, the IAB-node it accesses is called the access IAB-node (access IAB-node), and the IAB-node that returns the relay is called the intermediate IAB-node (intermediate IAB-node).

In order to better understand the method and device for RLF notification of a radio link failure disclosed in the embodiments of the present application, the following describes the network architecture used in the embodiments of the present invention. Please refer to FIG. 1. FIG. 1 is a schematic structural diagram of a communication system to which an embodiment of this application is applicable.

It should be noted that the communication systems mentioned in the embodiments of this application include, but are not limited to: narrowband-internet of things (NB-IoT) systems, wireless local access network (WLAN) systems, and LTE systems , The next generation 5G mobile communication system or the communication system after 5G, such as NR, device to device (device to device, D2D) communication system.

The following describes the IAB system to which this application is applied in conjunction with FIG. 1 and FIG. 2.

In the communication system shown in Figure 1, an integrated access and backhaul IAB system is given. An IAB system includes at least one base station 100, and one or more terminal equipment (terminal) 101 served by the base station 100, one or more relay node IAB nodes, and one or more terminal equipment served by the IAB node 110 111. The base station 100 is usually called a donor next generation node B (DgNB), and the IAB node 110 is connected to the base station 100 through a wireless backhaul link 113. The donor base station is also referred to as a donor node in this application, that is, a Donor node. Base stations include but are not limited to: evolved node B (evolved node base, eNB), radio network controller (RNC), node B (node B, NB), base station controller (base station controller, BSC), Base transceiver station (base transceiver station, BTS), home base station (for example, home evolved NodeB, or home node B, HNB), baseband unit (BBU), eLTE (evolved LTE, eLTE) base station, NR base station (next generation node B, gNB) etc. Terminal equipment includes but is not limited to: user equipment (UE), mobile station, access terminal, user unit, user station, mobile station, remote station, remote terminal, mobile equipment, terminal, wireless communication equipment, user agent, Station (ST), cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (wireless local loop, WLL) station, wireless local access network (WLAN) Personal digital assistant (PDA), handheld devices with wireless communication functions, computing devices, other processing devices connected to wireless modems, in-vehicle devices, wearable devices, mobile stations in the future 5G network, and public Any of the terminal devices in the public land mobile network (PLMN) network. The IAB node is a specific name of a relay node, and does not limit the solution of the embodiment of the present application. It may be one of the above-mentioned base stations or terminal devices with a forwarding function, or may be an independent device form.

The integrated access and backhaul system may also include multiple other IAB nodes, such as IAB node 120 and IAB node 130. The IAB node 120 is connected to the IAB node 110 through a wireless backhaul link 123 to access the network. The IAB node 130 is connected to the IAB node 110 through a wireless backhaul link 133 to access the network. The IAB node 120 serves one or more terminal devices 121, and the IAB node 130 serves one or more terminal devices 131. In FIG. 1, both the IAB node 110 and the IAB node 120 are connected to the network through a wireless backhaul link. In this application, the wireless backhaul links are all viewed from the perspective of the relay node. For example, the wireless backhaul link 113 is the backhaul link of the IAB node 110, and the wireless backhaul link 123 is the IAB node 120. Backhaul link. As shown in Figure 1, an IAB node, such as 120, can be connected to another IAB node 110 through a wireless backhaul link, such as 123, to connect to the network, and the relay node can be connected through a multi-level wireless relay node To the network. It should be understood that the use of IAB nodes in this application is only for the purpose of description, and does not mean that the solution of this application is only used in NR scenarios. In this application, IAB nodes can generally refer to any node or device with a relay function. The use of IAB node and relay node in this application should be understood to have the same meaning.

For the convenience of description, the basic terms or concepts involved in the embodiments of the present application are defined below.

Upper-level node (or upstream node): The node that provides wireless backhaul link resources, such as 110, is called the upper-level node of the IAB node 120. It should be understood that the upper-level node may be an IAB node, a donor base station (such as a Donor node), or a network device, etc., which is not limited.

Lower-level nodes (or downstream nodes): The nodes that use backhaul link resources to transmit data to the network or receive data from the network are called lower-level nodes. For example, 120 is called a relay node, 110 is a lower-level node, and 131 can become The lower-level node of 130, the network is a core network or a network above other access networks, such as the Internet, a private network, and so on.

Access link: The access link refers to the wireless link used by a node to communicate with its subordinate nodes, including uplink transmission and downlink transmission links. Uplink transmission on the access link is also referred to as uplink transmission on the access link, and downlink transmission is also referred to as downlink transmission on the access link. The nodes include but are not limited to the aforementioned IAB nodes.

Backhaul link: The backhaul link refers to the wireless link used by a node to communicate with its superior node, including uplink transmission and downlink transmission links. Uplink transmission on the backhaul link is also referred to as uplink transmission on the backhaul link, and downlink transmission is also referred to as downlink transmission on the backhaul link. The nodes include but are not limited to the aforementioned IAB nodes.

In another description, the IAB node can be divided into two parts, namely a mobile terminal (MT) and a distributed unit (DU). Among them, the MT is used for the communication between the IAB node and the upper-level node, and the DU is used for the communication between the IAB node and the lower-level node. The link between the MT in the IAB node and the upper-level node is called the parent BH link, and the link between the DU in the IAB node and its lower-level IAB node is called the child BH link. link), and the link between the DU in the IAB node and the subordinate UE is called an access link. However, in this application, for the convenience of description, the link between the IAB node and the upper-level node is called the backhaul link, and the link between the IAB node and the lower-level IAB node and/or UE is collectively called the access link.

Generally, the lower-level node can be regarded as a terminal device of the upper-level node. It should be understood that in the integrated access and backhaul system shown in Figure 1, an IAB node is connected to an upper-level node, but in the future relay system, in order to improve the reliability of the wireless backhaul link, an IAB node, For example, 120, multiple upper-level nodes can provide services for one IAB node at the same time. As shown in the figure, the IAB node 130 can also be connected to the IAB node 120 through the backhaul link 134, that is, both the IAB node 110 and the IAB node 120 are IAB The superior node of node 130. The names of the

IAB nodes

110, 120, and 130 do not limit the scenarios or networks in which they are deployed, and may be any other names such as relay and RN. The use of the IAB node in this application is only for the convenience of description.

In Figure 1, the wireless links 102, 112, 122, 132, 113, 123, 133, 134 can be bidirectional links, including uplink and downlink transmission links. In particular, the

wireless backhaul links

113, 123, 133, 134 can be used by upper-level nodes to provide services for lower-level nodes, for example, the upper-level node 100 is a lower-level node. 110 provides wireless backhaul services. It should be understood that the uplink and downlink of the backhaul link may be separated, that is, the uplink and the downlink are not transmitted through the same node. The downlink transmission refers to an upper-level node, such as node 100, and a lower-level node, such as node 110, transmitting information or data, and the uplink transmission refers to a lower-level node, such as node 110, and an upper-level node, such as node 100, transmitting information or data. The node is not limited to whether it is a network node or a terminal device. For example, in a D2D scenario, the terminal device can act as a relay node to serve other terminal devices. The wireless backhaul link can be an access link in some scenarios. For example, the backhaul link 123 can also be regarded as an access link to the node 110, and the backhaul link 113 is also the access link of the node 100. link. It should be understood that the foregoing upper-level node may be a base station or a relay node, and the lower-level node may be a relay node or a terminal device with a relay function. For example, in a D2D scenario, the lower-level node may also be a terminal device.

The relay nodes shown in Figure 1, such as 110, 120, and 130, can exist in two forms: one is to exist as an independent access node, which can independently manage the terminal equipment connected to the relay node. At this time, the relay node usually has an independent physical cell identifier (PCI). This type of relay usually requires complete protocol stack functions, such as radio resource control (RRC) functions. One type of relay is usually called a layer 3 relay; while another type of relay node and Donor node, such as Donor eNB, Donor gNB, belong to the same cell, and user management is performed by the donor base station, such as Donor node. Managed, this kind of relay is usually called a layer 2 relay. Layer 2 relay usually exists as the DU of the base station DgNB under the control and bearer separation (central unit and distributed unit, CU-DU) architecture of NR, through the F1 application protocol (F1 application protocol, F1-AP) interface or tunnel protocol and The CU communicates, where the tunneling protocol may be, for example, a general packet radio service tunneling protocol (GTP) protocol, which will not be repeated here. Donor node refers to a node that can access the core network through this node, or an anchor base station of the wireless access network, through which the anchor base station can access the network. The anchor base station is responsible for receiving the data of the core network and forwarding it to the relay node, or receiving the data of the relay node and forwarding it to the core network. Generally, the Donor node in the relay system is called IAB donor, that is, the host node. In this application, the two terms may be used interchangeably. It should be understood that IAB donor and host node are entities or network elements with different functions. .

In the embodiment of the present application, a relay node (such as an IAB node) or a terminal device or a network device includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also referred to as main memory). The operating system can be any one or more computer operating systems that implement business processing through processes, for example, Linux operating systems, Unix operating systems, Android operating systems, iOS operating systems, or windows operating systems. The application layer includes applications such as browsers, address books, word processing software, and instant messaging software. Moreover, the embodiments of the application do not specifically limit the specific structure of the execution body of the method provided in the embodiments of the application, as long as the program that records the codes of the methods provided in the embodiments of the application can be provided in accordance with the embodiments of the application. For example, the execution subject of the method provided in the embodiments of the present application may be a terminal device or a network device, or a functional module in the terminal device or the network device that can call and execute the program.

In another description, the IAB-donor adopts a separated architecture and consists of two parts: a centralized unit (CU) and a distributed unit (DU). The IAB-node is composed of two parts: mobile termination (MT) and DU: the function of the MT part is equivalent to the UE, and the IAB-node is connected to the upstream IAB-node or IAB-donor through MT; the function of the DU part is the same as that of the ordinary DU. IAB-node connects to UE or downstream IAB-node through DU. There is an F1 interface (logical interface) between IAB-donor CU and IAB-node DU, and a Uu interface between IAB-donor DU or IAB-node DU and downstream IAB-node MT. Figure 2 is another schematic diagram of the IAB architecture. In Figure 2, IAB-node1 and IAB-node2 include DU and MT, respectively; IAB-donor includes DU and CU. IAB-donor is directly connected to the core network through the NG interface. IAB-donor, IAB-node1 and IAB-node2 are all connected to UE through DU, and the interface is NR Uu interface. The DU of IAB-node1 and the MT of IAB-node2 are connected through the NR Uu interface; the MT of IAB-node1 and the DU of the IAB-donor are connected through the NR Uu interface. The DU of IAB-node1 and the DU of IAB-node2 are respectively connected to the CU of IAB-donor through the F1 interface.

In the IAB network, data packets are transmitted from the source node to the destination node through multiple hops (for downlink transmission, the source node is IAB-donor DU, and the destination node is access IAB-node; for uplink transmission) , The source node is access IAB-node, and the destination node is IAB-donor DU). This process is called routing. The routing function of IAB is in charge of the backhaul adaptation protocol (BAP) layer. The concepts related to IAB routing include BAP address (BAP address), routing table, BAP header (BAP header) and so on. The BAP layer is a protocol layer unique to IAB, which is responsible for functions such as RLC channel mapping and routing.

BAP address: Each IAB-node and IAB-donor DU has a BAP layer identifier, called BAP address.

Routing table: Each IAB-node maintains an upstream routing table and a downstream routing table. Each routing table contains the following items:

· Destination address: the BAP address of the destination node;

· Path ID: the identification of the data packet forwarding path;

· Next hop address: the BAP address of the next hop node;

· Priority (optional): If there are multiple forwarding paths to a destination address, the "priority" is used to indicate the priority order for selecting these paths.

BAP header: The BAP header contains the destination address and path ID, which is used to indicate the routing information of the data packet.

The routing process in IAB is summarized as follows: The source node determines the destination node and forwarding path of the data packet, and adds the destination address and path ID to the BAP header of the data packet, and then forwards the data packet to the next hop node. After receiving the data packet, the next hop node checks the destination address and path ID in the BAP header, then finds the corresponding next hop node according to the routing table, and forwards the data packet to this node (if the data packet cannot be forwarded to this node) For example, if the communication link with the node is interrupted, then other next hop nodes corresponding to the destination address can be selected in the routing table). Each intermediate IAB-node forwards the data packet in turn until the data packet reaches the destination node.

In the IAB network, a radio link failure (radio link failure, RLF) may occur on the backhaul link. IAB-node can perform RLF monitoring of the backhaul link (RLF monitoring). When RLF is found on the backhaul link, the IAB-node can send an RLF notification (RLF notification) to its child nodes.

RLF monitoring: IAB-node monitors the quality of the backhaul link (that is, the link between the IAB-node and the parent node). When the IAB-node finds that the quality of the backhaul link meets certain conditions (for example, the bit error rate of the downlink control channel is greater than the threshold, the number of RLC retransmissions is greater than the threshold, random access failure, etc.), it is considered RLF occurred on the backhaul link.

RLF notification: If the IAB-node finds that RLF occurs on the backhaul link, it will send an RLF notification to the child node to inform the child node that the backhaul link is RLF or which uplink path fails. After receiving the RLF notification, the child node can reselect the uplink path. At the same time, the child node can also send an RLF notification to its child node to inform the link that RLF occurs or which uplink path fails. According to the different content contained in RLF notifications, RLF notifications can be divided into two types:

Type 1 RLF notification: This type 1 RLF notification contains the identification of the link where the RLF occurred (the link identification can take many forms. For example, one ID can be used to identify a link, or the BAP address to identify a link), that is, this type 1 RLF notification can tell the IAB-node which link has RLF occurred.

Type 2 RLF notification: This type 2 RLF notification contains the ID of the failed uplink path, that is, this type 2 RLF notification can inform the IAB-node which uplink paths have failed (the failure of these uplink paths is caused by the occurrence of RLF on an upstream link of).

Take the IAB network shown in Figure 3 as an example. As shown in Figure 3, the IAB network includes IAB-node A, IAB-node B, IAB-node C, IAB-node D, IAB-node E, and IAB-node. donor X. There are 4 upstream paths in the IAB network. When an RLF occurs on the link XA, the IAB-node A sends an RLF notification to the child node IAB-node C, and the IAB-node C can send the RLF notification to the child nodes IAB-node D and IAB-node E after receiving the RLF notification. The above three RLF notifications may all be type 1 or type 2. The type 1 RLF notification includes the identifier of the link XA, and the type 2 RLF notification includes path 1 and path 2 (that is, path ID=1, 2).

Regarding Type 1 RLF notification, this application provides an RLF notification method, which can ensure that the IAB node knows which uplink path fails when RLF occurs on a certain link.

FIG. 4 is a schematic interaction diagram of an RLF notification method 400 according to an embodiment of the present application. As shown in FIG. 4, the method 400 includes:

S401. The first node sends a first configuration message to a second node, where the first configuration message includes path failure information of the second node, and the path failure information is used to indicate that at least one uplink path fails. An uplink path refers to at least one uplink path including an RLF link that has a radio link failure, and the RLF link is a link between the second node and an upstream node of the second node. Correspondingly, the second node receives the first configuration message.

Among them, at least one uplink path can be understood as one or more uplink paths.

For a unified explanation here, the first node is a device with IAB management functions. For example, the first node can be an IAB-donor. The second node is a node managed by the first node. For example, the second node may be an IAB-node.

Exemplarily, the first node is IAB-donor in FIG. 2, and the second node is IAB-node 1 or IAB-node 2 in FIG. 2. Exemplarily, the first node is IAB-donor X in FIG. 3, and the second node is IAB-node A, IAB-node B, IAB-node C, IAB-node D, or IAB-node E.

In the embodiment of the present application, the link where RLF occurs may include the link between the second node and its parent node, and may also include a certain link upstream of the second node (for example, a certain link upstream of the second node occurs). RLF, and then the upstream node sends RLF notifications in turn, so that the second node also learns that RLF occurs on the link).

Path failure information is used to indicate which uplink paths will fail when RLF occurs on the link. Taking the second node as an IAB-node as an example, a failure of an uplink path of the IAB-node means that the path cannot be used when the IAB-node performs uplink transmission (that is, transmits data to the IAB-donor). To put it another way, the path failure information is used to indicate that in the case where an RLF occurs on the link between the second node and the upstream node of the second node, at least one uplink path through the link fails. In other words, the path failure information can also be understood as the failure condition of the uplink path configured by the second node.

Taking the IAB-donor as the first node as an example, the IAB-donor can configure path failure information for each IAB-node in the IAB network. Suppose the first node is IAB-donor and the second node is IAB-node. Taking the IAB network in Figure 3 as an example, uplink paths 1 to 4 pass through IAB-node C, and uplink path 1 and uplink path 2 pass through IAB-node D , Upstream Path 3 and Upstream Path 4 pass through IAB-node E.

In Figure 3, the path failure information configured by IAB-donor for IAB-node C is: if RLF occurs on link XA, uplink path 1 and uplink path 3 fail; if RLF occurs on link XB, uplink path 2, uplink Path 4 is invalid. The path failure information configured by IAB-donor for IAB-node D is: if RLF occurs on link XA or link AC, uplink path 1 fails; if RLF occurs on link XB or link BC, uplink path 2 fails. The path failure information configured by IAB-donor to IAB-node E is: if RLF occurs on link XA or link AC, uplink path 3 fails; if RLF occurs on link XB or link BC, uplink path 4 fails.

Specifically, in the routing table, the path failure information may specifically be a path failure condition configured by the first node for each routing item of the second node. Taking the path failure information configured by IAB-donor for IAB-node D as an example, the path failure information configured by IAB-donor for IAB-node D can be specifically configured to configure a series of failure conditions for the upstream routing table of IAB-node D. For IAB-node D, the failure condition of uplink path 1 is: RLF occurs on link XA or RLF occurs on link AC, and the failure condition of uplink path 2 is: RLF occurs on link XB or RLF occurs on link BC. Table 1 shows the upstream routing table of IAB-node D. As shown in Table 1 below,

Table 1

目的地址Destination address	路径IDPath ID	下一跳地址Next hop address	优先级priority	路径失效信息Path failure information
XX	11	CC	11	链路XA发生RLF或者链路AC发生RLFRLF occurs on link XA or RLF occurs on link AC
XX	22	CC	CC	链路XB发生RLF或者链路BC发生RLFRLF occurs on link XB or RLF occurs on link BC

Take the second line in Table 1 as an example: the destination address of IAB-node D is X (X represents the address of IAB-donor), the next hop address is C (C represents the address of IAB-node C), and the upstream path 1 The failure condition (path ID is 1) is: RLF occurs on link XA or RLF occurs on link AC.

It can be understood that the content in the foregoing Table 1 is only an exemplary description, and does not constitute a limitation to the embodiments of the present application.

Exemplarily, taking the first configuration message being the routing configuration message of the F1 interface as an example, an information element (IE) may be added to the routing configuration message of the F1 interface, and the IE is used to indicate path failure information. For example, Table 2 is the routing configuration message BH ROUTING CONFIGURATION message of the F1 interface, which is sent by the IAB-donor CU to the IAB-node DU to configure the routing table for the IAB-node DU. In Table 2, lines 8 and 9 are used to indicate path failure information, where the 8th line Failure Condition List represents the path failure information list, and the 9th line Link ID is an item in the path failure information list, indicating the chain that has been interrupted. ID of the road. As shown in Table 2 below:

Table 2

It can be understood that the content in the foregoing Table 2 is only an exemplary description, and does not constitute a limitation to the embodiments of the present application.

When sending the first configuration message to the second node, the first node may carry a first indication in the first configuration message to indicate the type of RLF notification. Optionally, the first configuration message further includes a first indication, and the first indication is used to indicate that the RLF notification is a type 1 RLF notification. In this way, the second node knows that the first configuration message sent by the first node is applicable to the scenario where the type 1 RLF notification is used for the RLF notification.

Optionally, the first configuration message may be an F1 message, an RRC message, or a MAC layer message, which is not limited.

The above describes the case where the path failure information is configured by the first node for the second node, and the embodiment of the present application is not limited to this. For example, the path failure information may also be defined by the protocol.

S402: The parent node of the second node sends a first notification message to the second node, where the first notification message is used to notify the second node that RLF occurs on the link. Correspondingly, the second node receives the first notification message from the parent node of the second node.

Here, when the parent node of the second node detects that RLF occurs in the link between the second node and the upstream node of the second node (including the link between the second node and the parent node of the second node), the second node’s The parent node may send a type 1 RLF notification (for example, a first notification message) to the second node to inform the second node that RLF has occurred on the link.

Optionally, the first notification message includes the identifier of the occurrence of the RLF link. A unified description is provided here, and the embodiment of the present application does not specifically limit the form of the link identification. For example, the identification of the link can be represented by ID. For another example, the identification of the link can be identified by the BAP addresses of the nodes at both ends of the link.

After receiving the first notification message, the second node determines the invalid uplink path in combination with the first configuration message.

S403: The second node determines that the at least one uplink path is invalid according to the first configuration message and the first notification message.

Here, the second node can know the link where the RLF occurs based on the first notification message. In addition, based on the first configuration message, the second node can learn which specific uplink paths fail in the case of RLF on the link. In this way, the second node can reselect an unfailed uplink path in the routing table for uplink transmission. Compared with the prior art that only knows the link where the RLF occurs, the RLF notification method provided in the embodiment of the present application can not only know the link where the RLF occurs, but also determine the corresponding failed uplink path.

The second node may also send a type 1 RLF notification to the child nodes of the second node to inform the child nodes of the second node that RLF has occurred on the link. Optionally, the method 400 includes: S404. The second node sends a second notification message to a child node of the second node, where the second notification message is used to notify the child node of the second node of the RLF occurred on the link. Correspondingly, the child node of the second node receives the second notification message. The child node of the second node may send a Type 1 RLF notification to its downstream node.

Still taking the example in Figure 3 for description, after IAB-node A detects that RLF has occurred on link XA, it sends a type 1 RLF notification to the child node IAB-node C to inform that RLF has occurred on link XA. After the IAB-node C receives the Type 1 RLF notification, it can know that RLF occurs on the link XA. Then, according to the path failure information configured by IAB-donor, the IAB-node C can know that the uplink path 1 and the uplink path 3 are invalid. The IAB-node C can send a Type 1 RLF notification to the child nodes IAB-node D and IAB-node E to inform the link XA that RLF has occurred. After IAB-node D and IAB-node E receive the type 1 RLF notification, they can know that RLF occurs on link XA. According to the uplink path failure conditions configured by IAB-donor, IAB-node D can know that uplink path 1 is invalid; IAB-node E can know that uplink path 3 fails according to the uplink path failure conditions configured by IAB-donor.

The foregoing describes the embodiment of the RLF notification method provided in this application for Type 1 RLF notification. For Type 2 RLF notification, an embodiment of the RLF notification method provided in this application will be described below.

When RLF occurs on a link, the Type 2 RLF notification will include the IDs of all failed uplink paths passing through the link. However, for IAB-nodes that receive Type 2 RLF notifications, not every failed uplink path passes through itself. If the Type 2 RLF notification contains a path that does not pass through the IAB-node, then this information in the RLF notification is unnecessary for the IAB-node (that is, the RLF notification may contain Necessary information). The RLF notification method provided in this application for Type 2 RLF notification can avoid unnecessary information contained in the RLF notification.

FIG. 5 is a schematic interaction diagram of a method 500 for RLF notification according to another embodiment of the present application. As shown in FIG. 5, the method 500 includes:

S501: The first node sends a second configuration message to the second node, where the second configuration message includes notification information of the first child node of the second node, and the notification information is used to indicate an uplink path set notified by the RLF. The RLF notification is an RLF notification when an RLF occurs on the link between the second node and the upstream node of the second node. Correspondingly, the second node receives the second configuration message.

For related explanations of the first node and the second node, reference may be made to the description in the method 400.

The second node may have one or more child nodes, which is not specifically limited. Here, the first child node is taken as an example for description. The notification information may be understood as an uplink path set (or referred to as an RLF notification range) notified by the second node to the first child node by the RLF. The uplink path set notified by the second node to the first child node by the RLF can be understood as: if the uplink path in the uplink path set fails, the second node can notify the first child node through Type 2 RLF notification; and for If the uplink path in the uplink path set fails, the second node does not need to notify the first child node, thereby avoiding the type 2 RLF notification from including unnecessary path information.

In other words, the notification information of the first child node can also be understood as: the notification information is used to indicate that in the case of RLF occurring in the link between the second node and the upstream node of the second node, the notification information includes (or passes through) At least one uplink path of the first child node.

Taking the IAB-donor as the first node as an example, the IAB-donor can configure notification information for each IAB-node in the IAB network. Assuming that the first node is IAB-donor and the second node is IAB-node C, taking the IAB network in Figure 3 as an example, IAB-donor can send notification information to IAB-node C to IAB-node D. The notification information The indicated uplink path set includes: uplink path 1 and uplink path 2. In other words, if uplink path 1 or uplink path 2 fails, then IAB-node C can send Type 2 RLF notification to IAB-node D to inform the failed path; if other paths fail, IAB-node C does not need to send IAB-node D sends RLF notification.

In addition, the IAB-donor may send notification information to the IAB-node E to the IAB-node C, and the uplink path set indicated by the notification information includes: the uplink path 3 and the uplink path 4. In other words, if uplink path 3 or uplink path 4 fails, then IAB-node C can send Type 2 RLF notification to IAB-node E to inform the failed path; if other paths fail, IAB-node C does not need to send IAB-node E send RLF notification.

When sending the second configuration message to the second node, the first node may carry a second indication in the second configuration message to indicate the type of RLF notification. Optionally, the second configuration message further includes a second indication, and the second indication is used to indicate that the RLF notification is a type 2 RLF notification. The second indication is used to indicate that the RLF notification is a type 2 RLF notification. In this way, the second node is made aware that the first configuration message sent by the first node is suitable for the scenario where the type 2 RLF notification is used for the RLF notification.

Optionally, the second configuration message may include the identifier of each uplink path in the uplink path set.

Optionally, the second configuration message may be an RRC message or a MAC layer message, which is not limited.

The first node may configure the notification information of the child nodes for the second node in advance. The foregoing describes the case where the notification information of the child node is configured by the first node for the second node, and the embodiment of the present application is not limited to this. For example, the notification information of the child node may also be defined by the protocol.

S502: The parent node of the second node sends a second notification message to the second node, where the second notification message is used to notify the second node that RLF occurs on the link. Correspondingly, the second node receives the second notification message from the parent node of the second node.

Here, when the parent node of the second node detects that RLF occurs in the link between the second node and the upstream node of the second node (including the link between the second node and the parent node of the second node), the second node’s The parent node may send a type 2 RLF notification (for example, a second notification message) to the second node to inform the second node that RLF has occurred on the link.

When the second node learns that RLF occurs on the link, it sends a type 2 RLF notification to the first child node, so as to inform the first child node of the second node that RLF occurs on the link.

S503: The second node sends a third notification message to the first child node of the second node, where the third notification message includes the identifier of each uplink path in the uplink path set. Correspondingly, the first child node of the second node receives the third notification message.

Here, based on the second notification message, the second node can know the link where the RLF occurred. In addition, based on the second configuration message, the second node can learn the set of failed uplink paths of the first child node in the case that RLF occurs on the link. The second node may send a type 2 RLF notification (for example, a third notification message) to the first child node, and carry the identifier of each uplink path in the uplink path set in the type 2 RLF notification, without carrying the uplink path set The identifier of the upstream path other than that, so as to avoid carrying unnecessary path information.

Still taking the example in Figure 3 for description, after IAB-node A detects RLF on link XA, it can determine that uplink path 1 and uplink path 3 are invalid (because in the routing table of IAB-node A, uplink path 1 and The next hop node corresponding to the uplink path 3 is X). According to the notification information of IAB-node C configured by IAB-donor, IAB-node A (assuming that the uplink path set notified by IAB-node A to IAB-node D includes uplink path 1 and uplink path 3). The node IAB-node C informs that the uplink path 1 and the uplink path 3 are invalid. Therefore, IAB-node A sends a type 2 RLF notification to IAB-node C. The type 2 RLF notification includes uplink path 1 and uplink path 3 (that is, invalid uplink path ID=1 and 3). After the IAB-node C receives the type 2 RLF notification, it can know that the uplink path 1 and the uplink path 3 are invalid. According to the notification information of IAB-node D configured by IAB-donor, IAB-node C can know that it needs to notify the child node IAB-node D that uplink path 1 is invalid. According to the notification information of IAB-node E configured by IAB-donor, It is learned that the child node IAB-node E needs to be notified that the uplink path 3 is invalid. Therefore, IAB-node C sends a type 2 RLF notification to IAB-node D. The type 2 notification includes uplink path 1 (that is, the invalid uplink path ID = 1), and sends a type 2 RLF notification to IAB-node E, which is type 2 The notification includes uplink path 3 (ie, invalid uplink path ID=3).

It is understandable that some optional features in the embodiments of the present application, in some scenarios, may not depend on other features, such as the solutions they are currently based on, but can be implemented independently to solve the corresponding technical problems and achieve the corresponding The effect can also be combined with other features according to requirements in some scenarios. Correspondingly, the devices given in the embodiments of the present application can also implement these features or functions accordingly, which will not be repeated here.

It should also be understood that the various solutions of the embodiments of the present application can be used in a reasonable combination, and the explanations or descriptions of various terms appearing in the embodiments can be referred to or explained in the various embodiments, which is not limited.

It should also be understood that, in various embodiments of the present application, the size of the sequence number of the above-mentioned processes does not mean the order of execution, and the execution order of the processes should be determined by their functions and internal logic. The various numerical numbers or serial numbers involved in the above-mentioned various processes are only for easy distinction for description, and should not constitute any limitation on the implementation process of the embodiments of the present application.

Corresponding to the methods given in the foregoing method embodiments, the embodiments of the present application also provide corresponding devices, and the devices include corresponding modules for executing the foregoing embodiments. The module can be software, hardware, or a combination of software and hardware. It can be understood that the technical features described in the method embodiments are also applicable to the following device embodiments.

Fig. 6 is a schematic block diagram of an RLF notification device provided by an embodiment of the present application. Taking the communication device 1000 as an example, as shown in FIG. 6, the communication device 1000 may include a transceiver unit 1100. Optionally, the communication device 1000 may further include a processing unit 1200.

In a possible design, the communication device 1000 may correspond to the first node in the above method embodiment, for example, it may be the first node or a chip configured in the first node.

Specifically, the communication device 1000 may correspond to the first node in the method 400 or the method 500 according to the embodiment of the present application, and the communication device 1000 may include the first node for executing the method 400 in FIG. 4 or the method 500 in FIG. 5 A unit of method executed by a node. In addition, the units in the communication device 1000 and the other operations or functions described above are respectively intended to implement the corresponding process of the first node in the method 400 in FIG. 4 or the method 500 in FIG. 5.

In a possible implementation manner, the transceiver unit 1100 is configured to send a first configuration message to a second node, where the first configuration message includes path failure information of the second node, and the path failure information is used for Indicates that at least one uplink path fails, the at least one uplink path refers to at least one uplink path including an RLF link that has a radio link failure, and the RLF link is between the second node and an upstream node of the second node Link.

Optionally, the first configuration message further includes a first indication, and the first indication is used to indicate the type of RLF notification.

Optionally, the first configuration message is a radio resource control RRC message or a media access control MAC layer message.

Or, in a possible implementation manner, the transceiver unit 1100 is configured to send a second configuration message to the second node, where the second configuration message includes notification information of the first child node of the second node, so The notification information is used to indicate an uplink path set notified by the RLF, and the RLF notification is an RLF notification in the case where an RLF occurs on the link between the second node and the upstream node of the second node.

Optionally, the second configuration message further includes a second indication, and the second indication is used to indicate the type of RLF notification.

Optionally, the second configuration message is a radio resource control RRC message or a media access control MAC layer message.

It should be understood that the specific process for each unit to execute the foregoing corresponding steps has been described in detail in the foregoing method embodiment, and is not repeated here for brevity.

It should be understood that when the communication device 1000 is a base station, the transceiver unit 1100 in the communication device 1000 may correspond to the radio frequency unit 3012 and the antenna 3011 in the base station 3000 shown in FIG. 7, and the processing unit 1100 in the communication device 1000 may It is implemented by at least one processor, and may correspond to the processor 3022 in the base station 3000 shown in FIG. 7, for example.

It should also be understood that when the communication device 1000 is a chip configured in the first node, the transceiver unit 1200 in the communication device 1000 may be an input/output interface.

Optionally, the communication device 1000 further includes a storage unit, which can be used to store instructions or data, and the processing unit can call the instructions or data stored in the storage unit to implement corresponding operations. The storage unit may be implemented by at least one memory, for example, may correspond to the memory 3021 in the base station 3000 in FIG. 7.

In a possible design, the communication device 1000 may correspond to the second node in the above method embodiment, for example, it may be the second node or a chip configured in the second node.

Specifically, the communication device 1000 may correspond to the second node in the method 400 or the method 500 according to the embodiment of the present application, and the communication device 1000 may include a method for executing the method 400 in FIG. 4 or the first node in the method 500 in FIG. The unit of the method executed by the two nodes. In addition, the units in the communication device 1000 and the other operations or functions described above are used to implement the corresponding process of the second node in the method 400 in FIG. 4 or the method 500 in FIG. 5, respectively.

Or, in a possible implementation manner, the transceiving unit 1100 and the processing unit 1200 are respectively configured to:

The transceiver unit 1100 is configured to receive a first configuration message from a first node, where the first configuration message includes path failure information related to the second node, and the path failure information is used to indicate that at least one uplink path fails, The at least one uplink path refers to at least one uplink path including an RLF link that has a radio link failure, and the RLF link is a link between the second node and an upstream node of the second node; and Receiving a first notification message from a parent node of the second node, where the first notification message is used to notify the second node that RLF has occurred on the link.

The processing unit 1200 is configured to determine that the at least one uplink path is invalid according to the first configuration message and the first notification message.

Optionally, the transceiver unit 1100 is further configured to send a second notification message to a child node of the second node, where the second notification message is used to notify the child node of the second node of the link RLF occurs.

Optionally, the first notification message includes an identifier of the link.

Or, in a possible implementation manner, the transceiving unit 1100 is configured to receive a second configuration message from a first node, where the second configuration message includes notification information of a first child node of the second node, The notification information is used to indicate the uplink path set notified by the RLF, and the RLF notification is the RLF notification when the RLF occurs on the link between the second node and the upstream node of the second node; and is also used to receive from A second notification message of the parent node of the second node, where the second notification message is used to notify the second node that RLF has occurred on the link; and is also used to notify the first child node of the second node Send a third notification message, where the third notification message includes the identifier of each uplink path in the uplink path set.

It should be understood that when the communication device 1000 is a base station, the transceiver unit 1100 in the communication device 1000 may correspond to the transceiver 1203 shown in FIG. 8, and the processing unit 1100 in the communication device 1000 may be implemented by at least one processor. For example, it may correspond to the processor 1201 shown in FIG. 8.

It should also be understood that when the communication device 1000 is a chip configured in the second node, the transceiver unit 1200 in the communication device 1000 may be an input/output interface.

Optionally, the communication device 1000 further includes a storage unit, which can be used to store instructions or data, and the processing unit can call the instructions or data stored in the storage unit to implement corresponding operations. The storage unit may be implemented by at least one memory, for example, may correspond to the memory 1202 in FIG. 8.

FIG. 7 is a schematic structural diagram of an RLF notification apparatus provided in an embodiment of the present application, and may be a schematic structural diagram of a base station 3000, for example. The base station 3000 can be applied to the system shown in FIG. 1 to perform the function of the first node in the foregoing method embodiment. As shown in the figure, the base station 3000 may include one or more DU 3010 and one or more CU 3020. The CU 3020 can communicate with NGcore (Next Generation Core Network, NC). The DU 3010 may include at least one antenna 3011, at least one radio frequency unit 3012, at least one processor 3013, and at least one memory 3014. The DU 3010 part is mainly used for the transmission and reception of radio frequency signals, the conversion of radio frequency signals and baseband signals, and part of baseband processing. The CU 3020 may include at least one processor 3022 and at least one memory 3021. CU 3020 and DU 3010 can communicate through interfaces, where the control plane (CP) interface can be Fs-C, such as F1-C, and the user plane (UP) interface can be Fs-U. For example, F1-U.

The CU 3020 part is mainly used for baseband processing, control of base stations, and so on. The DU 3010 and the CU 3020 may be physically set together, or may be physically separated, that is, a distributed base station. The CU 3020 is the control center of the base station, which may also be referred to as a processing unit, and is mainly used to complete baseband processing functions. For example, the CU 3020 may be used to control the base station to execute the operation procedure of the access network device in the foregoing method embodiment.

Specifically, the baseband processing on the CU and the DU can be divided according to the protocol layer of the wireless network. For example, the functions of the PDCP layer and the above protocol layers are set in the CU, and the protocol layers below the PDCP, such as the RLC layer and the MAC layer, are set in the DU. . For another example, the CU implements the functions of the RRC layer and the PDCP layer, and the DU implements the functions of the RLC layer, the MAC layer, and the PHY layer.

In addition, optionally, the base station 3000 may include one or more radio frequency units (RU), one or more DUs, and one or more CUs. The DU may include at least one processor 3013 and at least one memory 3014, the RU may include at least one antenna 3011 and at least one radio frequency unit 3012, and the CU may include at least one processor 3022 and at least one memory 3021.

In an example, the CU 3020 may be composed of one or more single boards, and multiple single boards may jointly support a wireless access network (such as a 5G network) with a single access indication, and may also support different access standards. Wireless access network (such as LTE network, 5G network or other networks). The memory 3021 and the processor 3022 may serve one or more single boards. In other words, the memory and the processor can be set separately on each board. It can also be that multiple boards share the same memory and processor. In addition, necessary circuits can be provided on each board. The DU 3010 can be composed of one or more single boards. Multiple single boards can jointly support a wireless access network with a single access indication (such as a 5G network), or can respectively support wireless access networks with different access standards ( Such as LTE network, 5G network or other networks). The memory 3014 and the processor 3013 may serve one or more single boards. In other words, the memory and the processor can be set separately on each board. It can also be that multiple boards share the same memory and processor. In addition, necessary circuits can be provided on each board.

It should be understood that the base station 3000 shown in FIG. 7 can implement each process involving the first node in the method embodiment shown in FIG. 4 or FIG. 5. The operations and/or functions of the various modules in the base station 3000 are to implement the corresponding procedures in the foregoing method embodiments. For details, please refer to the description in the foregoing method embodiment, and to avoid repetition, detailed description is omitted here as appropriate.

It should be understood that the base station 3000 shown in FIG. 7 is only a possible architecture of the first node, and should not constitute any limitation in this application. The method provided in this application can be applied to access network equipment of other architectures. For example, access network equipment including CU, DU, and AAU, etc. This application does not limit the specific architecture of the first node.

FIG. 8 shows a schematic structural diagram of an apparatus 1200 for resource configuration according to an embodiment of the present application. As shown in FIG. 8, the apparatus 1200 includes a processor 1201.

It should be understood that the processor 1201 may call an interface to perform the above-mentioned transceiving action, where the called interface may be a logical interface or a physical interface, which is not limited. Optionally, the physical interface can be implemented by a transceiver. Optionally, the device 1200 further includes a transceiver 1203.

Optionally, the device 1200 further includes a memory 1202, and the memory 1202 can store the program codes in the foregoing method embodiments, so that the processor 1201 can call them.

Specifically, if the device 1200 includes the processor 1201, the memory 1202, and the transceiver 1203, the processor 1201, the memory 1202, and the transceiver 1203 communicate with each other through internal connection paths, and transfer control and/or data signals. In a possible design, the processor 1201, the memory 1202, and the transceiver 1203 may be implemented by chips. The processor 1201, the memory 1202, and the transceiver 1203 may be implemented on the same chip or may be implemented on different chips. Or any combination of two functions can be implemented in one chip. The memory 1202 can store program codes, and the processor 1201 calls the program codes stored in the memory 1202 to implement the corresponding functions of the device 1200.

It should be understood that the apparatus 1200 may also be used to perform other steps and/or operations on the second node side in the foregoing embodiment, and for the sake of brevity, details are not described here.

It should be understood that the apparatus 1200 shown in FIG. 8 is only a possible architecture of the second node, and should not constitute any limitation to this application. The method provided in this application can be applied to relay nodes of other architectures. For example, relay nodes including DU and MT, etc. This application does not limit the specific architecture of the second node.

According to the method provided in the embodiments of the present application, the present application also provides a computer program product, the computer program product includes: computer program code, when the computer program code runs on a computer, the computer executes the steps shown in FIG. 4 or FIG. 5 The method on the side of the first node in the embodiment is shown.

According to the method provided in the embodiments of the present application, the present application also provides a computer program product, the computer program product includes: computer program code, when the computer program code runs on a computer, the computer executes the steps shown in FIG. 4 or FIG. 5 The method on the second node side in the embodiment is shown.

According to the method provided by the embodiments of the present application, the present application also provides a computer-readable medium storing program code, which when the program code runs on a computer, causes the computer to execute the steps shown in FIG. 4 or FIG. 5 The method on the side of the first node in the embodiment is shown.

According to the method provided by the embodiments of the present application, the present application also provides a computer-readable medium storing program code, which when the program code runs on a computer, causes the computer to execute the steps shown in FIG. 4 or FIG. 5 The method on the second node side in the embodiment is shown.

An embodiment of the present application also provides a processing device, including a processor and an interface; the processor is configured to execute the RLF notification method in any of the foregoing method embodiments.

The first node and the second node in the communication device and method embodiment in the foregoing device embodiments completely correspond, and the corresponding module or unit executes the corresponding steps. For example, the communication unit (transceiver) performs the receiving or receiving in the method embodiment. In the sending step, other steps except sending and receiving can be executed by the processing unit (processor). For the functions of specific units, refer to the corresponding method embodiments. Among them, there may be one or more processors.

Those skilled in the art may also understand that various illustrative logical blocks and steps listed in the embodiments of the present application can be implemented by electronic hardware, computer software, or a combination of the two. Whether such a function is implemented by hardware or software depends on the specific application and the design requirements of the entire system. Those skilled in the art can use various methods to implement the described functions for each specific application, but such implementation should not be construed as going beyond the protection scope of the embodiments of the present application.

It should be understood that the processor in the embodiment of the present application may be an integrated circuit chip with signal processing capability. In the implementation process, the steps of the foregoing method embodiments may be completed by hardware integrated logic circuits in the processor or instructions in the form of software. The above-mentioned processor may be a general-purpose processor, a digital signal processor (digital signal processor, DSP), an application specific integrated circuit (ASIC), a field programmable gate array (field programmable gate array, FPGA) or other Programming logic devices, discrete gates or transistor logic devices, discrete hardware components can also be system on chip (SoC), central processor unit (CPU), or network processor (network processor). processor, NP), can also be a digital signal processing circuit (digital signal processor, DSP), can also be a microcontroller (microcontroller unit, MCU), can also be a programmable controller (programmable logic device, PLD) or other Integrated chip. The methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like. The steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor. The software module can be located in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

The technology described in this application can be implemented in various ways. For example, these technologies can be implemented in hardware, software, or a combination of hardware. For hardware implementation, the processing unit used to execute these technologies at a communication device (for example, a base station, a terminal, a network entity, or a chip) can be implemented in one or more general-purpose processors, DSPs, digital signal processing devices, ASICs, Programmable logic device, FPGA, or other programmable logic device, discrete gate or transistor logic, discrete hardware component, or any combination of the foregoing. The general-purpose processor may be a microprocessor. Alternatively, the general-purpose processor may also be any traditional processor, controller, microcontroller, or state machine. The processor can also be implemented by a combination of computing devices, such as a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors combined with a digital signal processor core, or any other similar configuration. accomplish.

It can be understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory can be read-only memory (ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), and electrically available Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory. The volatile memory may be random access memory (RAM), which is used as an external cache. By way of exemplary but not restrictive description, many forms of RAM are available, such as static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), and synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory (synchlink DRAM, SLDRAM) ) And direct memory bus random access memory (direct rambus RAM, DR RAM). It should be noted that the memories of the systems and methods described herein are intended to include, but are not limited to, these and any other suitable types of memories.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented by software, it can be implemented in the form of a computer program product in whole or in part. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on the computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center. Transmission to another website, computer, server, or data center via wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center integrated with one or more available media. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a high-density digital video disc (digital video disc, DVD)), or a semiconductor medium (for example, a solid state disk, SSD)) etc.

It should be understood that the “embodiment” mentioned throughout the specification means that a specific feature, structure, or characteristic related to the embodiment is included in at least one embodiment of the present application. Therefore, the various embodiments throughout the specification do not necessarily refer to the same embodiment. In addition, these specific features, structures or characteristics can be combined in one or more embodiments in any suitable manner. It should be understood that in the various embodiments of the present application, the size of the sequence number of the above-mentioned processes does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic, and should not correspond to the embodiments of the present application. The implementation process constitutes any limitation.

It should also be understood that in this application, "when", "if" and "if" all mean that the UE or the base station will make corresponding processing under certain objective circumstances, and it is not a time limit, and the UE is not required Or, when the base station is implemented, there must be a judgment action, which does not mean that there are other restrictions.

Those of ordinary skill in the art can understand that the various numerical numbers such as first and second involved in the present application are only for easy distinction for description, and are not used to limit the scope of the embodiments of the present application, but also indicate a sequence.

The use of the singular element in this application is intended to mean "one or more" rather than "one and only one", unless otherwise specified. In this application, unless otherwise specified, "at least one" is intended to mean "one or more", and "multiple" is intended to mean "two or more".

In addition, the terms "system" and "network" in this article are often used interchangeably in this article. The term "and/or" in this article is only an association relationship describing the associated objects, which means that there can be three relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, exist alone In the three cases of B, A can be singular or plural, and B can be singular or plural.

The character "/" generally indicates that the associated objects before and after are in an "or" relationship.

The term "at least one of..." or "at least one of..." as used herein means all or any combination of the listed items, for example, "at least one of A, B and C", It can mean: A alone exists, B alone exists, C exists alone, A and B exist at the same time, B and C exist at the same time, and there are six cases of A, B and C at the same time, where A can be singular or plural, and B can be Singular or plural, C can be singular or plural.

It should be understood that in the embodiments of the present application, "B corresponding to A" means that B is associated with A, and B can be determined according to A. However, it should also be understood that determining B based on A does not mean that B is determined only based on A, and B can also be determined based on A and/or other information.

The configuration in the embodiments of this application can be understood as notification through RRC signaling, MAC signaling, and physical layer information. The physical layer information can be notified through physical downlink control channel (physical downlink control channel, PDCCH) or physical downlink shared channel (physical downlink control channel). shared channel, PDSCH) transmission.

Those skilled in the art can clearly understand that, for the convenience and conciseness of description, the specific working process of the system, device and unit described above can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here.

Various aspects or features of the present application can be implemented as methods, devices, or products using standard programming and/or engineering techniques. The term "article of manufacture" used in this application encompasses a computer program accessible from any computer-readable device, carrier, or medium. For example, computer-readable media may include, but are not limited to: magnetic storage devices (for example, hard disks, floppy disks, or tapes, etc.), optical disks (for example, compact discs (CD), digital versatile discs (DVD)) Etc.), smart cards and flash memory devices (for example, erasable programmable read-only memory (EPROM), cards, sticks or key drives, etc.). In addition, various storage media described herein may represent one or more devices and/or other machine-readable media for storing information. The term "machine-readable medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing, and/or carrying instructions and/or data.

A person of ordinary skill in the art may be aware that the units and algorithm steps of the examples described in combination with the embodiments disclosed herein can be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether these functions are executed by hardware or software depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.

In the several embodiments provided in this application, it should be understood that the disclosed system, device, and method can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or It can be integrated into another system, or some features can be ignored or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.

In addition, the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.

If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium. Based on this understanding, the technical solution of the present application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), magnetic disks or optical disks and other media that can store program codes. .

The above are only specific implementations of this application, but the protection scope of this application is not limited to this. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in this application. Should be covered within the scope of protection of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims

An RLF notification method for radio link failure, which is characterized in that it includes:

The first node sends a first configuration message to the second node, where the first configuration message includes path failure information of the second node, and the path failure information is used to indicate that at least one uplink path fails, and the at least one uplink path It refers to at least one uplink path including an RLF link that has a radio link failure, and the RLF link is a link between the second node and an upstream node of the second node.
The method according to claim 1, wherein the first configuration message further comprises a first indication, and the first indication is used to indicate the type of RLF notification.
The method according to claim 1 or 2, wherein the first configuration message is a radio resource control RRC message or a medium access control MAC layer message.
An RLF notification method for radio link failure, which is characterized in that it includes:

The second node receives a first configuration message from the first node, where the first configuration message includes path failure information related to the second node, and the path failure information is used to indicate that at least one uplink path fails. An uplink path refers to at least one uplink path including an RLF link that has a radio link failure, and the RLF link is a link between the second node and an upstream node of the second node;

Receiving, by the second node, a first notification message from a parent node of the second node, where the first notification message is used to notify the second node that RLF has occurred on the link;

The second node determines that the at least one uplink path is invalid according to the first configuration message and the first notification message.
The method according to claim 4, wherein the method further comprises:

The second node sends a second notification message to the child nodes of the second node, where the second notification message is used to notify the child nodes of the second node that RLF occurs on the link.
The method according to claim 4 or 5, wherein the first notification message includes an identifier of the link.
The method according to any one of claims 4 to 6, wherein the first configuration message further comprises a first indication, and the first indication is used to indicate the type of RLF notification.
An RLF notification method for radio link failure, which is characterized in that it includes:

The first node sends a second configuration message to the second node, where the second configuration message includes notification information of the first child node of the second node, and the notification information is used to indicate the uplink path set notified by the RLF. The RLF notification is an RLF notification when an RLF occurs on the link between the second node and the upstream node of the second node.
The method according to claim 8, wherein the second configuration message further includes an identifier of each uplink path in the uplink path set.
The method according to claim 8 or 9, wherein the second configuration message further includes a second indication, and the second indication is used to indicate the type of RLF notification.
The method according to any one of claims 8 to 10, wherein the second configuration message is a radio resource control RRC message or a medium access control MAC layer message.
An RLF notification method for radio link failure, which is characterized in that it comprises:

The second node receives a second configuration message from the first node, the second configuration message includes notification information of the first child node of the second node, and the notification information is used to indicate the uplink path set notified by the RLF, so The RLF notification is an RLF notification when an RLF occurs on the link between the second node and the upstream node of the second node;

Receiving, by the second node, a second notification message from a parent node of the second node, where the second notification message is used to notify the second node that RLF has occurred on the link;

The second node sends a third notification message to the first child node of the second node, where the third notification message includes the identifier of each uplink path in the uplink path set.
The method according to claim 12, wherein the second configuration message further includes an identifier of each uplink path in the set of uplink paths.
The method according to claim 12 or 13, wherein the second configuration message further includes a second indication, and the second indication is used to indicate the type of RLF notification.
An RLF notification device for radio link failure, which is characterized in that it comprises:

The transceiver unit is configured to send a first configuration message to a second node, where the first configuration message includes path failure information of the second node, and the path failure information is used to indicate that at least one uplink path fails. An uplink path refers to at least one uplink path including an RLF link that has a radio link failure, and the RLF link is a link between the second node and an upstream node of the second node.
The apparatus according to claim 15, wherein the first configuration message further comprises a first indication, and the first indication is used to indicate the type of RLF notification.
The apparatus according to claim 15 or 16, wherein the first configuration message is a radio resource control RRC message or a media access control MAC layer message.
An RLF notification device for radio link failure, which is characterized in that it comprises:

The transceiver unit is configured to receive a first configuration message from a first node, where the first configuration message includes path failure information related to the second node, and the path failure information is used to indicate that at least one uplink path fails, so The at least one uplink path refers to at least one uplink path including an RLF link where a radio link failure occurs, and the RLF link is a link between the second node and an upstream node of the second node; and is also used for receiving A first notification message from the parent node of the second node, where the first notification message is used to notify the second node that RLF has occurred on the link;

The processing unit is configured to determine that the at least one uplink path is invalid according to the first configuration message and the first notification message.
The apparatus according to claim 18, wherein the transceiver unit is further configured to send a second notification message to a child node of the second node, and the second notification message is used to send a second notification message to the second node. The child node of informs the link that RLF occurs.
The device according to claim 18 or 19, wherein the first notification message includes an identifier of the link.
The apparatus according to any one of claims 18 to 20, wherein the first configuration message further comprises a first indication, and the first indication is used to indicate the type of RLF notification.
An RLF notification device for radio link failure, which is characterized in that it comprises:

The transceiver unit is configured to send a second configuration message to the second node, the second configuration message including notification information of the first child node of the second node, and the notification information is used to indicate the uplink path set notified by the RLF, The RLF notification is an RLF notification when an RLF occurs on the link between the second node and the upstream node of the second node.
The apparatus according to claim 22, wherein the second configuration message further includes an identifier of each uplink path in the uplink path set.
The apparatus according to claim 22 or 23, wherein the second configuration message further comprises a second indication, and the second indication is used to indicate the type of RLF notification.
The apparatus according to any one of claims 22 to 24, wherein the second configuration message is a radio resource control RRC message or a medium access control MAC layer message.
An RLF notification device for radio link failure, which is characterized in that it comprises:

The transceiver unit is configured to receive a second configuration message from the first node, the second configuration message including notification information of the first child node of the second node, and the notification information is used to indicate the uplink path set notified by the RLF The RLF notification is an RLF notification when an RLF occurs on the link between the second node and the upstream node of the second node; and is also used to receive a second notification message from the parent node of the second node The second notification message is used to notify the second node that RLF has occurred on the link; and is also used to send a third notification message to the first child node of the second node, where the third notification message includes The identifier of each uplink path in the set of uplink paths.
The apparatus according to claim 26, wherein the second configuration message further includes an identifier of each uplink path in the set of uplink paths.
The apparatus according to claim 26 or 27, wherein the second configuration message further comprises a second indication, and the second indication is used to indicate the type of RLF notification.
A communication device, characterized by comprising a processor and an interface circuit, the interface circuit is used to receive signals from other communication devices other than the communication device and transmit them to the processor or transfer signals from the processor The signal is sent to other communication devices other than the communication device, and the processor is used to implement claims 1 to 3, or 4 to 7, or 8 to 11, or 12 to 14 through logic circuits or executing code instructions. The method of any one of.
A communication system, characterized by comprising the device according to any one of claims 15 to 16 and the device according to any one of claims 18 to 21;

Or, including the device according to any one of claims 22 to 25, and the device according to any one of claims 26 to 28.
A computer-readable storage medium, characterized in that a program or instruction is stored in the storage medium, and when the program or instruction is executed, the implementation of claims 1 to 3, or 4 to 7, or 8 to 11 , Or the method described in any one of 12 to 14.
A computer program product, characterized in that, the computer product includes a program or instruction, and when the program or instruction is executed, the implementation of claims 1 to 3, or 4 to 7, or 8 to 11, or 12 to 14. The method of any one of 14.