Method, apparatus, and computer-readable medium for controlling downlink transmissions in an integrated access and backhaul network

Abstract

Methods for controlling downlink transmissions in an integrated access and backhaul network are disclosed. An example method may include: determining to control a first downlink transmission of a first interface, the first interface being between a second device associated with a user plane of the central unit of the donor and a node in the integrated access and backhaul network; and sending a first non-UE associated signaling request to the second device for controlling the first downlink transmission of the first interface, the first non-UE associated signaling request including information associated with the node. Related apparatus and computer readable media are also disclosed.

Description

Technical Field

[0001] Various embodiments are directed to methods, apparatus, and computer-readable media for controlling downlink transmissions in an integrated access and backhaul network. Background Art

[0002] Integrated access and backhaul (IAB) networks (in which a portion of the radio resources are also used for wireless backhaul) have been introduced in telecommunication systems such as new radio (NR or 5G) systems, so that, for example, flexible and dense deployment of NR cells can be achieved without proportionally densifying the transmission network, and site acquisition costs and fiber deployment costs can be reduced. Summary of the invention

[0003] In a first aspect, an apparatus is disclosed, comprising: at least one processor and at least one memory, wherein the at least one memory may include computer program code, and wherein the at least one memory and the computer program code may be configured to, together with the at least one processor, cause the apparatus as a first device associated with a control plane of a central unit of a donor in an integrated access and backhaul network to perform: determining a first downlink transmission to control a first interface, the first interface being between a second device associated with a user plane of the central unit of the donor and a node in the integrated access and backhaul network; and sending a first non-UE associated signaling request to the second device for controlling the first downlink transmission of the first interface, the first non-UE associated signaling request including information associated with the node.

[0004] In some embodiments, the first non-UE-associated signaling request may include: a request to start a first downlink transmission of the first interface; or a request to stop a first downlink transmission of the first interface.

[0005] In some embodiments, the first non-UE-associated signaling request may include at least one of: an identifier of a distributed unit of the node; an address of the node; an identifier of a cell associated with the node; a routing identifier of a routing path associated with the node; and a quality of service parameter value of a service associated with the node.

[0006] In some embodiments, the first non-UE-associated signaling request may further include at least one of: an identity of a distributed unit of a descendant node of the node in the integrated access and backhaul network; an address of the descendant node; an identifier of a cell associated with the descendant node; a routing identifier of a routing path associated with the descendant node, and a quality of service parameter value of a service associated with the descendant node.

[0007] In some embodiments, the at least one memory and the computer program code may be configured, together with the at least one processor, to cause the apparatus to further execute: sending a second non-UE associated signaling request to the second device to start a second downlink transmission of a second interface between the second device and a descendant node of the integrated access and backhaul network node, or to stop a second downlink transmission of the second interface, wherein the second non-UE associated signaling request includes information associated with the descendant node.

[0008] In some embodiments, the second non-UE-associated signaling request may include at least one of: an identifier of a distributed unit of the descendant node; an address of the descendant node; an identifier of a cell associated with the descendant node; a routing identifier of a routing path associated with the descendant node; and a quality of service parameter value of a service associated with the descendant node.

[0009] In a second aspect, a method is disclosed, comprising: determining, at a first device associated with a control plane of a central unit of a donor in an integrated access and backhaul network, a first downlink transmission to control a first interface between a second device associated with a user plane of the central unit of the donor and a node in the integrated access and backhaul network; and sending a first non-UE associated signaling request to the second device to control the first downlink transmission of the first interface, the first non-UE associated signaling request comprising information associated with the node.

[0010] In some embodiments, the first non-UE-associated signaling request may include: a request to start a first downlink transmission of the first interface; or a request to stop a first downlink transmission of the first interface.

[0011] In some embodiments, the first non-UE-associated signaling request may include at least one of: an identifier of a distributed unit of the node; an address of the node; an identifier of a cell associated with the node; a routing identifier of a routing path associated with the node; and a quality of service parameter value of a service associated with the node.

[0012] In some embodiments, the first non-UE-associated signaling request may further include at least one of the following: an identifier of a distributed unit of a descendant node of the node in the integrated access and backhaul network; an address of the descendant node; an identifier of a cell associated with the descendant node; a routing identifier of a routing path associated with the descendant node; and a quality of service parameter value of a service associated with the descendant node.

[0013] In some embodiments, the method may further include: sending a second non-UE associated signaling request to the second device to start a second downlink transmission of a second interface between the second device and a descendant node of the node in the integrated access and backhaul network, or stop a second downlink transmission of the second interface, wherein the second non-UE associated signaling request includes information associated with the descendant node.

[0014] In some embodiments, the second non-UE-associated signaling request may include at least one of: an identifier of a distributed unit of the descendant node; an address of the descendant node; an identifier of a cell associated with the descendant node; a routing identifier of a routing path associated with the descendant node; and a quality of service parameter value of a service associated with the descendant node.

[0015] In a third aspect, a device as a first device associated with a control plane of a central unit of a donor in an integrated access and backhaul network is disclosed. The device may include: means for determining a first downlink transmission to control a first interface between a second device associated with a user plane of the central unit of the donor and a node in the integrated access and backhaul network; and means for sending a first non-UE associated signaling request to the second device to control the first downlink transmission of the first interface, the first non-UE associated signaling request including information associated with the node.

[0016] In some embodiments, the first non-UE-associated signaling request may include: a request to start a first downlink transmission of the first interface; or a request to stop a first downlink transmission of the first interface.

[0017] In some embodiments, the first non-UE-associated signaling request may include at least one of: an identifier of a distributed unit of the node; an address of the node; an identifier of a cell associated with the node; a routing identifier of a routing path associated with the node; and a quality of service parameter value of a service associated with the node.

[0018] In some embodiments, the first non-UE-associated signaling request may further include at least one of the following: an identifier of a distributed unit of a descendant node of the node in the integrated access and backhaul network; an address of the descendant node; an identifier of a cell associated with the descendant node; a routing identifier of a routing path associated with the descendant node; and a quality of service parameter value of a service associated with the descendant node.

[0019] In some embodiments, the device may further include: sending a second non-UE associated signaling request to the second device to start a second downlink transmission of a second interface between the second device and a descendant node of the node in the integrated access and backhaul network, or to stop a second downlink transmission of the second interface, wherein the second non-UE associated signaling request includes information associated with the descendant node.

[0020] In some embodiments, the second non-UE-associated signaling request may include at least one of: an identifier of a distributed unit of the descendant node; an address of the descendant node; an identifier of a cell associated with the descendant node; a routing identifier of a routing path associated with the descendant node; and a quality of service parameter value of a service associated with the descendant node.

[0021] In a fourth aspect, a computer-readable medium is disclosed. The computer-readable medium may include instructions stored thereon for causing a first device associated with a control plane of a central unit of a donor in an integrated access and backhaul network to: determine a first downlink transmission for controlling a first interface between a second device associated with a user plane of the central unit of the donor and a node in the integrated access and backhaul network; and send a first non-UE-associated signaling request for controlling the first downlink transmission of the first interface to the second device, the first non-UE-associated signaling request including information associated with the node.

[0022] In some embodiments, the first non-UE-associated signaling request may include: a request to start a first downlink transmission of the first interface; or a request to stop a first downlink transmission of the first interface.

[0023] In some embodiments, the first non-UE-associated signaling request may include at least one of: an identifier of a distributed unit of the node; an address of the node; an identifier of a cell associated with the node; a routing identifier of a routing path associated with the node; and a quality of service parameter value of a service associated with the node.

[0024] In some embodiments, the first non-UE-associated signaling request may further include at least one of the following: an identifier of a distributed unit of a descendant node of the node in the integrated access and backhaul network; an address of the descendant node; an identifier of a cell associated with the descendant node; a routing identifier of a routing path associated with the descendant node; and a quality of service parameter value of a service associated with the descendant node.

[0025] In some embodiments, the instruction may cause the first device to further execute: sending a second non-UE associated signaling request to the second device to start a second downlink transmission of a second interface between the second device and a descendant node of the node in the integrated access and backhaul network, or to stop a second downlink transmission of the second interface, wherein the second non-UE associated signaling request includes information associated with the descendant node.

[0026] In some embodiments, the second non-UE-associated signaling request may include at least one of: an identifier of a distributed unit of the descendant node; an address of the descendant node; an identifier of a cell associated with the descendant node; a routing identifier of a routing path associated with the descendant node; and a quality of service parameter value of a service associated with the descendant node.

[0027] In a fifth aspect, an apparatus comprising at least one processor and at least one memory is disclosed, wherein the at least one memory may include computer program code, and wherein the at least one memory and the computer program code may be configured to, together with the at least one processor, cause the apparatus to execute as a first device associated with a user plane of a central unit of a donor in an integrated access and backhaul network: receiving a non-UE associated signaling request from a second device associated with a control plane of the central unit of the donor to control a first downlink transmission of a first interface between the first device and a node in the integrated access and backhaul network, the non-UE associated signaling request including information associated with the node; and controlling the first downlink transmission of the first interface based on the non-UE associated signaling request.

[0028] In some embodiments, the control may include: stopping the first downlink transmission of the first interface when the non-UE associated signaling request indicates stopping the first downlink transmission of the first interface; or starting the first downlink transmission of the first interface when the non-UE associated signaling request indicates starting the first downlink transmission of the first interface.

[0029] In some embodiments, the at least one memory and the computer program code can be configured to, together with the at least one processor, cause the apparatus to further execute: stopping the second downlink transmission of the second interface between the first device and a descendant node of a node in the integrated access and backhaul network when the non-UE associated signaling request indicates stopping the first downlink transmission of the first interface; or starting the second downlink transmission of the second interface when the non-UE associated signaling request indicates starting the first downlink transmission of the first interface.

[0030] In some embodiments, the non-UE-associated signaling request may include at least one of: an identifier of a distributed unit of the node; an address of the node; an identifier of a cell associated with the node; a routing identifier of a routing path associated with the node; and a quality of service parameter value of a service associated with the node.

[0031] In some embodiments, the non-UE associated signaling request may further include at least one of: an identifier of a distributed unit of a descendant node of a node in the integrated access and backhaul network; an address of the descendant node; an identifier of a cell associated with the descendant node; a routing identifier of a routing path associated with the descendant node; and a quality of service parameter value of a service associated with the descendant node.

[0032] In a sixth aspect, a method is disclosed, comprising: receiving, at a first device associated with a user plane of a central unit of a donor in an integrated access and backhaul network and from a second device associated with a control plane of the central unit of the donor, a non-UE associated signaling request to control a first downlink transmission of a first interface between the first device and a node in the integrated access and backhaul network, the non-UE associated signaling request comprising information associated with the node; and controlling the first downlink transmission of the first interface based on the non-UE associated signaling request.

[0033] In some embodiments, the control may include: stopping the first downlink transmission of the first interface when the non-UE associated signaling request indicates stopping the first downlink transmission of the first interface; or starting the first downlink transmission of the first interface when the non-UE associated signaling request indicates starting the first downlink transmission of the first interface.

[0034] In some embodiments, the method may further include: stopping the second downlink transmission of the second interface between the first device and a descendant node of the node in the integrated access and backhaul network when the non-UE associated signaling request indicates stopping the first downlink transmission of the first interface; or starting the second downlink transmission of the second interface when the non-UE associated signaling request indicates starting the first downlink transmission of the first interface.

[0035] In some embodiments, the non-UE-associated signaling request may include at least one of: an identifier of a distributed unit of the node; an address of the node; an identifier of a cell associated with the node; a routing identifier of a routing path associated with the node; and a quality of service parameter value for a service associated with the node.

[0036] In some embodiments, the non-UE associated signaling request may further include at least one of: an identifier of a distributed unit of a descendant node of a node in the integrated access and backhaul network; an address of the descendant node; an identifier of a cell associated with the descendant node; a routing identifier of a routing path associated with the descendant node; and a quality of service parameter value of a service associated with the descendant node.

[0037] In a seventh aspect, a device as a first device associated with a user plane of a central unit of a donor in an integrated access and backhaul network is disclosed. The device may include: means for receiving a non-UE associated signaling request from a second device associated with a control plane of the central unit of the donor to control a first downlink transmission of a first interface between the first device and a node in the integrated access and backhaul network, the non-UE associated signaling request including information associated with the node; and means for controlling the first downlink transmission of the first interface based on the non-UE associated signaling request.

[0038] In some embodiments, the control may include: stopping the first downlink transmission of the first interface when the non-UE associated signaling request indicates stopping the first downlink transmission of the first interface; or starting the first downlink transmission of the first interface when the non-UE associated signaling request indicates starting the first downlink transmission of the first interface.

[0039] In some embodiments, the device may further include: a device for stopping the second downlink transmission of the second interface between the first device and a descendant node of the node in the integrated access and backhaul network when the non-UE associated signaling request indicates stopping the first downlink transmission of the first interface; or for starting the second downlink transmission of the second interface when the non-UE associated signaling request indicates starting the first downlink transmission of the first interface.

[0040] In some embodiments, the non-UE-associated signaling request may include at least one of: an identifier of a distributed unit of the node; an address of the node; an identifier of a cell associated with the node; a routing identifier of a routing path associated with the node; and a quality of service parameter value of a service associated with the node.

[0041] In some embodiments, the non-UE associated signaling request may further include at least one of: an identifier of a distributed unit of a descendant node of a node in the integrated access and backhaul network; an address of the descendant node; an identifier of a cell associated with the descendant node; a routing identifier of a routing path associated with the descendant node; and a quality of service parameter value of a service associated with the descendant node.

[0042] In an eighth aspect, a computer-readable medium is disclosed. The computer-readable medium may include instructions stored thereon for causing a first device associated with a user plane of a central unit of a donor in an integrated access and backhaul network to: receive a non-UE-associated signaling request from a second device associated with a control plane of the central unit of the donor to control a first downlink transmission of a first interface between the first device and a node in the integrated access and backhaul network, the non-UE-associated signaling request including information associated with the node; and control the first downlink transmission of the first interface based on the non-UE-associated signaling request.

[0043] In some embodiments, the control may include: stopping the first downlink transmission of the first interface when the non-UE associated signaling request indicates stopping the first downlink transmission of the first interface; or starting the first downlink transmission of the first interface when the non-UE associated signaling request indicates starting the first downlink transmission of the first interface.

[0044] In some embodiments, the instruction may cause the first device to further execute: when the non-UE associated signaling request indicates stopping the first downlink transmission of the first interface, stopping the second downlink transmission of the second interface between the first device and a descendant node of the node in the integrated access and backhaul network; or when the non-UE associated signaling request indicates starting the first downlink transmission of the first interface, starting the second downlink transmission of the second interface.

[0045] In some embodiments, the non-UE-associated signaling request may include at least one of: an identifier of a distributed unit of the node; an address of the node; an identifier of a cell associated with the node; a routing identifier of a routing path associated with the node; and a quality of service parameter value of a service associated with the node.

[0046] In some embodiments, the non-UE associated signaling request may further include at least one of: an identifier of a distributed unit of a descendant node of a node in the integrated access and backhaul network; an address of the descendant node; an identifier of a cell associated with the descendant node; a routing identifier of a routing path associated with the descendant node; and a quality of service parameter value of a service associated with the descendant node. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] Some embodiments will now be described by way of non-limiting examples with reference to the accompanying drawings.

[0048] Figure 1 An example of downlink transmission control in the IAB network in the embodiment is illustrated.

[0049] Figure 2 Another example of downlink transmission control in the IAB network in the embodiment is illustrated.

[0050] Figure 3 An example of an operation for controlling downlink transmission in an IAB network in an embodiment is illustrated.

[0051] Figure 4 An example of an operation for controlling downlink transmission in an IAB network in an embodiment is illustrated.

[0052] Figure 5 An example of an operation for controlling downlink transmission in an IAB network in an embodiment is illustrated.

[0053] Figure 6 An example of an operation for controlling downlink transmission in an IAB network in an embodiment is illustrated.

[0054] Figure 7 An example method for controlling downlink transmission in an IAB network in an embodiment is illustrated.

[0055] Figure 8 An example apparatus for controlling downlink transmission in an IAB network according to an embodiment is illustrated.

[0056] Fig. 9 Another example device for controlling downlink transmission in an IAB network according to an embodiment is illustrated.

[0057] Fig.10 Another example method for controlling downlink transmission in an IAB network in an embodiment is illustrated.

[0058] Fig.11 Another example apparatus for controlling downlink transmission in an IAB network according to an embodiment is illustrated.

[0059] Fig.12 Another example device for controlling downlink transmission in an IAB network according to an embodiment is illustrated. DETAILED DESCRIPTION

[0060] In an NR system, a base station (BS) may include a central unit (CU) and at least one distributed unit (DU), wherein the CU may host the radio resource control (RRC), the service data adaptation protocol (SDAP), and the packet data convergence protocol (PDCP), and may control the operation of one or more DUs. In addition, the CU may include NR user plane (UP) and control plane (CP) protocols to provide services to a terminal device or user equipment (UE). For example, the UP may provide functions related to processing UP data, such as packet routing and quality of service (QoS) processing, and the CP may provide functions such as security / authentication / authorization control, paging, and mobility management. The CP may also be referred to as CU-CP in this article. The UP may also be referred to as CU-UP in this article.

[0061] The IAB network may be configured with a spanning tree (ST) and directed acyclic graph (DAG) topology, which may include a donor BS (also referred to as a donor node or IAB donor in the IAB network, or simply referred to as a donor) hosting a CU function and one or more donor DUs, and one or more IAB nodes (or simply referred to as nodes in this document). The IAB node may include a mobile terminal (MT) function for communicating with a parent node in the IAB network (e.g., another IAB node serving the IAB node or the IAB donor), and at least one DU (or IAB-DU) function for communicating with a downstream IAB node in the IAB network (e.g., another IAB node served by the IAB node) or a UE served by the IAB node. The DU function of the IAB node is also referred to herein as a distributed unit of the IAB node or a distributed unit of the node. A backhaul (BH) radio link control (RLC) channel or connection may be used to transmit data packets between an IAB node and its parent IAB node or between an IAB node MT and an IAB donor DU. In the IAB network, communication between the CU-UP and the DU in the IAB donor or IAB node can be performed via an F1 user plane (F1-U) interface between the CU-UP and the DU in the IAB donor or IAB node. For example, a tunnel for communication can be established via an F1 user plane (F1-U) interface between the CU-UP and the DU in the IAB donor or IAB node based on the General Packet Radio System (GPRS) Tunneling Protocol (GTP). For example, the DL transmission between the CU-UP and the DU in the IAB donor or IAB node may include DL F1-U services related to one or more (e.g., all) descendant IAB nodes (e.g., including one or more of the following: a child IAB node directly connected to the IAB node; and other IAB nodes, such as a grandchild IAB node indirectly connected to the IAB node) or a UE served by the IAB donor or the DU in the IAB node.

[0062] For example, due to a possible failure in the BH connection in the IAB network, the IAB node may change its serving parent node, which may trigger topology adaptation of the IAB network. For example, in the case where the MT portion of the IAB node is detached from its serving cell, the IAB node may be disconnected from its serving parent node (e.g., another IAB node, or a DU of an IAB donor), and may be reconnected to its original serving parent node, or to another parent node under the same IAB donor in the IAB network (e.g., in the case of intra-donor topology adaptation), or to another parent node under a different IAB donor in the IAB network (e.g., in the case of inter-donor topology adaptation).

[0063] The CU-CP of the IAB donor (which may have an overview of the entire network topology / path) may be used for topology changes or adaptation. However, the CU-UP of the IAB donor may not be aware of, for example, the disconnection of an IAB node, and may therefore continue to send DL data for the F1-U interface between the CU-UP and the DU of the IAB node, which may result in, for example, packet loss and resource waste.

[0064] In one or more embodiments of the present application, the CU-CP of the IAB donor in the IAB network may be configured to determine an IAB node, which is, for example, disconnected or connected (or reconnected) to a parent node in the IAB network, and to do this, at least one F1-U interface between the CU-UP and the DU of the determined IAB node (e.g., all F1-U interfaces associated with the determined IAB node, or all GTP tunnels of the F1-U interface between the CU-UP and the DU of the determined IAB node, or some GTP tunnels of the F1-U interface between the CU-UP and the DU of the determined IAB node) is controlled (e.g., stopped in the case of disconnection, or started in the case of connection or reconnection). Then, the CU-CP may send a request to the CU-UP to control (e.g., stop or start) DL transmission of at least one F1-U interface associated with the determined IAB node (e.g., all F1-U interfaces, or all GTP tunnels of the F1-U interface, or some GTP tunnels of the F1-U interface), which may include information associated with the determined IAB node. For example, the request may use non-UE associated signaling to control the DL transmission of the F1-U GTP tunnels of multiple connected UEs, for example, when the interface between the CU-CP and the CU-UP is an E1 interface, the non-UE associated E1 application protocol (E1AP) signaling. Therefore, the request may also be referred to as a non-UE associated signaling request in this article. Similarly, the start request may also be referred to as a non-UE associated signaling start request in this article, and the stop request may also be referred to as a non-UE associated signaling stop request in this article. Based on the request received from the CU-CP, the CU-UP may be configured to control (e.g., stop or start) the DL transmission of at least one F1-U interface (e.g., all F1-U interfaces, or all GTP tunnels of the F1-U interface, or some GTP tunnels of the F1-U interface) associated with the determined IAB node. Therefore, for example, batch control of DL transmission for devices (including UEs and descendant IAB nodes) served by a determined IAB node can be allowed while reducing the signaling load, for example, by which potential packet loss and resource waste can be avoided or mitigated.

[0065] Figure 1 An example of DL transmission control in an IAB network in an embodiment is shown. Figure 1In the example shown, the IAB network may include a donor 101 and nodes 105, 107, 108, 111, 113, 114, etc. At least one DU 104 of the donor 101 may be controlled by a CU of the donor 101 including a CU-CP 102 and a CU-UP 103, and serves a node 105, a node 107, and a UE 106. The node 105 serves a UE 109 and a node 108, and the node 108 further serves a UE 110. The node 107 serves a node 111 and a UE 122. The node 111 further serves a node 113, a node 114, and a UE 115. The node 113 further serves a UE 116, a UE 117, and a UE 118. The node 114 further serves a UE 119 and a UE 120.

[0066] like Figure 1As shown, the connection 121 between the node 107 and the node 111 is disconnected, for example, when the connection 121 fails or the MT part of the node 111 is detached from the cell associated with the node 107. Then, the CU-CP 102 may send a request to the CU-UP 103 to stop DL transmission of the F1-U interface (for example, all F1-U interfaces, or all GTP tunnels of the F1-U interface, or some GTP tunnels of the F1-U interface) between the DUs of the CU-UP 103 and the node 111, which may, for example, include DL F1-U traffic related to the node 113, DL F1-U traffic related to the node 114, and DL F1-U traffic related to the terminal device served by the node 111 (such as the UE 115), and DL F1-U traffic related to the terminal devices served by the nodes 113 and 114. Such a stop request from CU-CP 102 to CU-UP 103 may include information associated with node 111, such as, but not limited to, one or more of the following: an identification (ID) of a DU of node 111; an address of node 111, such as an Internet Protocol address of an IAB-DU in node 111, or a backhaul adaptation protocol BAP address of node 111, etc.; an ID of a cell associated with node 111; a routing identifier (ID) of a routing path associated with node 111; a quality of service parameter of an F1-U service associated with node 111; or any other identifier that can identify multiple F1-U services associated with node 111. For example, in the case where there are multiple DUs in node 111, the stop request may further include a list of IDs of DUs of node 111. In another example, in the case where there are multiple addresses assigned to node 111, the stop request may further include a list of assigned addresses of node 111. In yet another example, in the case where there are multiple cells associated with node 111, the stop request may further include a list of IDs of cells associated with node 111. In yet another example, in the presence of multiple routing paths to node 111, the stop request may further include a list of routing IDs associated with node 111. For example, when node 111 has dual connections with two parent nodes and the connection with one parent node has a problem (e.g., a radio link failure), the stop request may indicate a list of routing IDs of the routing paths using the parent node. In yet another example, in the presence of multiple F1-U services with different quality of service requirements for node 111, the stop request may further include a list of quality of service parameters of the affected F1-U interfaces associated with node 111. For example, CU-CP 102 may request CU-UP 103 to stop all services related to specific quality of service parameters, such as when IAB node 111 cannot meet specific quality of service requirements.

[0067] In response to receiving a stop request from CU-CP 102, CU-UP 103 may stop DL transmission of the F1-U interface associated with the DU ID or IAB node address included in the stop request. For example, in the case where the stop request from CU-CP 102 includes a cell ID, CU-UP 103 may determine the F1-U interface associated with the cell based on the cell ID in the stop request, and may stop DL transmission of the F1-U interface associated with the cell as indicated in the stop request. Therefore, for example, DL transmission of the F1-U interface (or GTP tunnel) between CU-UP 103 and the DU of node 111 (including DL F1-U services related to node 113, DL F1-U services related to node 114, and DL F1-U services related to UE 115) may be stopped together by CU-UP 103 in response to a stop request associated with node 111 from CU-CP 102.

[0068] For example, in the case where CU-UP 103 is unaware of information associated with descendant IAB nodes of node 111 (including child IAB nodes 113 and 114), CU-CP 102 may further send to CU-UP 103: another request to stop DL transmission of the F1-U interface between CU-UP 103 and node 113 (e.g., all F1-U interfaces associated with the IAB node, or all GTP tunnels for the F1-U interface associated with the IAB node, or some GTP tunnels for the F1-U interface associated with the IAB node, or some GTP-U tunnels); and another request to stop DL transmission of the F1-U interface between CU-UP 103 and node 114 (e.g., all F1-U interfaces, or all GTP tunnels of the F1-U interface, or some GTP tunnels of the F1-U interface). Similar to the above-mentioned stop request associated with node 111, the stop request associated with node 113 may include information associated with node 113, such as an ID of a DU of node 113, an address of node 113 (e.g., an Internet Protocol address of an IAB-DU in node 113, or a Backhaul Adaptation Protocol (BAP) address of node 113, etc.), an ID of a cell associated with node 113, a routing identifier (ID) of a routing path associated with node 113, a quality of service parameter value of a service associated with node 113, or any other identifier that can identify a plurality of F1-U services associated with node 113. at least one of the above, and the stop request associated with node 114 may include information associated with node 114, for example, including at least one of: an ID of a DU of node 114; an address of node 114, for example, an Internet Protocol address of an IAB-DU in node 114, or a Backhaul Adaptation Protocol (BAP) address of node 114, etc.; an ID of a cell associated with node 114; a routing identifier (ID) of a routing path associated with node 114; or any other identifier that can identify multiple F1-U services associated with node 114, such as a quality of service parameter value of a service associated with node 114. Similar to the above-mentioned stop request associated with node 111, the stop request associated with node 113 may further include a list of IDs of DUs of node 113, and / or an address list of node 113, and / or an ID list of cells associated with node 113, and / or a list of routing IDs associated with node 113, and / or a list of service quality parameters of F1-U services associated with node 113, and the stop request associated with node 114 may further include a list of IDs of DUs of node 114, and / or an address list of node 114, and / or an ID list of cells associated with node 114, and / or a list of routing IDs associated with node 114, and / or a list of service quality parameters of F1-U services associated with node 114.In another example, the requests related to the above-mentioned nodes 111, 113, and 114 may be combined into a single request including the IDs of the multiple nodes.

[0069] In another example, when CU-UP 103 is unaware of information associated with descendant IAB nodes of node 111 (including child IAB nodes 113 and 114), CU-CP 102 may further send another request to CU-UP 103 to stop at least one of: DL transmission of the F1-U interface between CU-UP 103 and node 113 (e.g., all F1-U interfaces associated with node 113, or all GTP tunnels used for the F1-U interface associated with node 113, or some GTP tunnels used for the F1-U interface associated with node 113); and DL transmission of the F1-U interface between CU-UP 103 and node 114 (e.g., all F1-U interfaces associated with node 114, or all GTP tunnels used for the F1-U interface associated with node 114, or some GTP tunnels used for the F1-U interface associated with node 114). For example, such a stop request associated with both node 113 and node 114 may include both information associated with node 113 and information associated with node 114 .

[0070] Then, in response to receiving the corresponding stop request from CU-CP 102, CU-UP 103 may perform substantially the same operation for the corresponding stop request to stop DL transmission of the F1-U interface associated with the DU ID or IAB node address included in the corresponding stop request. For example, in the case where the stop request from CU-CP 102 includes a cell ID, CU-UP 103 may determine the F1-U interface associated with the cell based on the cell ID included in the stop request, and may stop DL transmission of the F1-U interface or GTP tunnel associated with the cell as indicated in the stop request. Thus, for example, DL transmission of the F1-U interface (or GTP tunnel) between CU-UP 103 and the DU of node 111 (including DL F1-U traffic associated with node 113, DL F1-U traffic associated with node 114, and DL F1-U traffic associated with UE 115) can be stopped together by CU-UP 103 in response to a stop request associated with node 111 from CU-CP 102; DL transmission of the F1-U interface (or GTP tunnel) between CU-UP 103 and the DU of node 113 (including DL F1-U traffic associated with UE 116, DL F1-U traffic associated with UE 117, and DL F1-U traffic associated with UE 118) can be stopped together by CU-UP 103 in response to a stop request associated with node 113; and DL transmission of the F1-U interface (or GTP tunnel) between CU-UP 103 and the DU of node 114 (including DL F1-U traffic associated with UE 119) can be stopped together by CU-UP 103 in response to a stop request associated with node 111. The F1-U traffic, as well as the DL F1-U traffic related to UE 120 , may be stopped together by CU-UP 103 in response to a stop request associated with node 114 .

[0071] In another example, in the case where CU-UP 103 is unaware of information associated with descendant IAB nodes (including child IAB nodes 113 and 114) of node 111, the stop request associated with node 111 from CU-CP 102 to CU-UP 103 may further include information associated with descendant IAB nodes of node 111, such as but not limited to one or more of the following: an ID of a DU of node 113; an address of node 113, such as an Internet Protocol address of an IAB-DU in node 113, or a Backhaul Adaptation Protocol (BAP) address of node 113, etc.; an ID of a cell associated with node 113; a routing identifier (ID) of a routing path associated with node 113; a quality of service parameter of an F1-U service associated with node 113; or Any other identifier that can identify multiple F1-U services associated with node 113; the ID of the DU of node 114; the address of node 114, such as the Internet Protocol address of the IAB-DU in node 114, or the Backhaul Adaptation Protocol (BAP) address of node 114, etc.; the ID of the cell associated with node 114; the routing identifier (ID) of the routing path associated with node 114; the quality of service parameters of the F1-U services associated with node 114; or any other identifier that can identify multiple F1-U services associated with node 114. For example, in the case where one or both of nodes 113 and 114 has more than one address, and / or has more than one DU, and / or is associated with more than one cell, the stop request associated with node 111 may further include one or more of the following: an ID list of DUs of node 113; an address list of node 113; a list of IDs of cells associated with node 113; a list of routing IDs associated with node 113; a list of service quality parameter values ​​for F1-U services associated with node 113; an ID list of DUs of node 114; an address list of node 114; a list of IDs of cells associated with node 114; a list of routing IDs associated with node 114; a list of quality of service parameter values ​​for F1-U services associated with node 114, etc.

[0072] Then, in response to receiving the stop request from CU-CP 102, CU-UP 103 may stop DL transmission of the F1-U interface associated with the corresponding DU ID or IAB node address included in the stop request associated with node 111. For example, in the case where the stop request from CU-CP 102 includes at least one cell ID, CU-UP 103 may determine the F1-U interface associated with at least one cell based on the at least one cell ID included in the stop request, and may stop DL transmission of the F1-U interface or GTP tunnel associated with at least one cell as indicated in the stop request. Thus, for example, DL transmission for the F1-U interface (or GTP tunnel) between CU-UP 103 and the DU of node 111 (including DL F1-U traffic associated with node 113, DL F1-U traffic associated with node 114, and DL F1-U traffic associated with UE 115), DL transmission for the F1-U interface (or GTP tunnel) between CU-UP 103 and the DU of node 113 (including DL F1-U traffic associated with UE 116, DL F1-U traffic associated with UE 117, and DL F1-U traffic associated with UE 118), and DL transmission for the F1-U interface (or GTP tunnel) between CU-UP 103 and the DU of node 114 (including DL F1-U traffic associated with UE 119, and DL F1-U traffic associated with UE 120) may be transmitted by CU-UP 103 in response to a request from the CU-CP. 102 is stopped together with the stop request associated with node 111.

[0073] In another example, in the case where CU-UP 103 knows information associated with the descendant IAB nodes (including child IAB nodes 113 and 114) of node 111, CU-UP 103 may stop DL F1-U services related to both node 111 and one or more (e.g., all) descendant IAB nodes of node 111 in response to receiving a stop request associated with node 111. For example, CU-UP 103 may stop all DL F1-U services of terminal devices connected to node 111 and descendant IAB nodes of node 111.

[0074] For example, based on information associated with IAB nodes included in the stop request from CU-CP 102 , CU-UP 103 may determine that the stop request is associated with node 111 , and may know that descendant IAB nodes of node 111 include node 113 and node 114 . Then, for example, CU-UP 103 may stop together the DL transmission of the F1-U interface between CU-UP 103 and node 111 (including DL F1-U services related to node 113, DL F1-U services related to node 114, and DL F1-U services related to UE 115), the DL transmission of the F1-U interface between CU-UP 103 and the DU of node 113 (including DL F1-U services related to UE 116, DL F1-U services related to UE 117, and DL F1-U services related to UE 118), and the DL transmission of the F1-U interface between CU-UP 103 and the DU of node 114 (including DL F1-U services related to UE 119, and DL F1-U services related to UE 120).

[0075] For the DL F1-U data of the stopped DL transmission, for example, at least a portion of the DL F1-U data for the DL transmission of the F1-U interface between CU-UP 103 and node 111, and / or at least a portion of the DL F1-U data for the DL transmission of the F1-U interface between CU-UP 103 and a descendant IAB node of node 111 may be cached by CU-UP 103 for later resuming the DL transmission of the F1-U interface between CU-UP 103 and node 111 and / or a descendant IAB node of node 111.

[0076] In addition, if Figure 1As shown, a new connection 122 may be established between the node 111 and the node 105, so that the node 111 may be served by the node 105 in the new topology of the IAB network. Then, the CU-CP 102 may send a request to the CU-UP 103 to start or resume DL transmission of the F1-U interface (or GTP tunnel) between the CU-UP 103 and the node 111, for example, including DL F1-U services related to the node 113, DL F1-U services related to the node 114, and DL F1-U services related to the UE 1155. Similar to the stop request from the CU-CP 102 to the CU-UP 103, such a start request from the CU-CP 102 to the CU-UP 103 may further include information associated with the node 111. For example, such a start request may include, but is not limited to, one or more of the following: an ID of a DU of node 111; an address of node 111, such as an Internet Protocol address of an IAB-DU in node 111, or a Backhaul Adaptation Protocol (BAP) address of node 111, etc.; an ID of a cell associated with node 111; a routing identifier (ID) of a routing path associated with node 111; a quality of service parameter of an F1-U service associated with node 111; or any other identifier that can identify a plurality of F1-U services associated with node 111. In another example, such a start request associated with node 111 may include, but is not limited to, one or more of the following: a list of IDs of at least one DU of node 111; a list of addresses of node 111; a list of IDs of at least one cell associated with node 111; a list of routing IDs associated with node 111; and a list of quality of service parameter values ​​for F1-U services associated with node 111.

[0077] In response to receiving the start request from CU-CP 102, CU-UP 103 may start or resume DL transmission of the F1-U interface associated with at least one DU ID or IAB node address included in the start request. For example, in the case where the start request from CU-CP 102 includes at least one cell ID, CU-UP 103 may determine the F1-U interface associated with at least one cell based on the at least one cell ID included in the start request, and may start or resume DL transmission for the F1-U interface or GTP tunnel associated with at least one cell as indicated in the stop request. Therefore, for example, DL transmission for the F1-U interface (or GTP tunnel) between CU-UP 103 and node 111 (including DL F1-U traffic associated with node 113, DL F1-U traffic associated with node 114, and DL F1-U traffic associated with UE 115) can be started or resumed by CU-UP 103 in response to a start request associated with node 111 from CU-CP 102, via the new service node 105 instead of the original service node 107.

[0078] For example, CU-UP 103 may resume previously stopped DL transmission of an F1-U interface (or GTP tunnel) between CU-UP 103 and node 111 in response to a start request received from CU-CP 102 by using previously cached DL F1-U data so that DL transmission at the F1-U interface or at a user plane associated with node 111 may continue.

[0079] For example, in the case where CU-UP 103 is unaware of information associated with descendant IAB nodes of node 111 (including child IAB nodes 113 and 114), CU-CP 102 may further send to CU-UP 103: another request to start or resume DL transmission of the F1-U interface between CU-UP 103 and node 113 (e.g., all F1-U interfaces associated with node 113, or all GTP tunnels used for the F1-U interface associated with node 113, or some GTP tunnels used for the F1-U interface associated with node 113), and another request to start or resume DL transmission of the F1-U interface between CU-UP 103 and node 114 (e.g., all F1-U interfaces associated with node 114, or all GTP tunnels used for the F1-U interface associated with node 114, or some GTP tunnels used for the F1-U interface associated with node 114). For example, the start request associated with the node 113 may include information associated with the node 113, such as an ID of a DU of the node 113, an address of the node 113 (e.g., an Internet Protocol address of an IAB-DU in the node 113, or a Backhaul Adaptation Protocol (BAP) address of the node 113, etc.); an ID of a cell associated with the node 113; a routing identifier (ID) of a routing path associated with the node 113; a quality of service parameter of an F1-U service associated with the node 113; or any other identifier that may identify one of a plurality of F1-U services associated with the node 113. or more, and the start request associated with node 114 may include information associated with node 114, such as an ID of a DU of node 114; an address of node 114, such as an Internet Protocol address of an IAB-DU in node 114, or a Backhaul Adaptation Protocol (BAP) address of node 114, etc.; an ID of a cell associated with node 114; a routing identifier (ID) of a routing path associated with node 114; a quality of service parameter of an F1-U service associated with node 114; or any other identifier that may identify multiple F1-U services associated with node 114. For example, the startup request associated with node 113 may further include a list of IDs of DUs of node 113, and / or an address list of node 113, and / or an ID list of cells associated with node 113, and / or a list of routing IDs associated with node 113, and / or a list of service quality parameters for F1-U services associated with node 113, and the startup request associated with node 114 may further include a list of IDs of DUs of node 114, and / or an address list of node 114, and / or an ID list of cells associated with node 114, and / or a list of routing IDs associated with node 114, and / or a list of service quality parameters for F1-U services associated with node 114.In another example, the requests related to the above-mentioned nodes 111, 113, and 114 may be combined into a single request including the IDs of the multiple nodes.

[0080] In another example, when CU-UP 103 is unaware of information associated with descendant IAB nodes of node 111 (including child IAB nodes 113 and 114), CU-CP 102 may further send another request to CU-UP 103 to start or resume at least one of: DL transmission of the F1-U interface between CU-UP 103 and node 113 (e.g., all F1-U interfaces associated with node 113, or all GTP tunnels used for the F1-U interface associated with node 113, or some GTP tunnels used for the F1-U interface associated with node 113); and DL transmission of the F1-U interface between CU-UP 103 and node 114 (e.g., all F1-U interfaces associated with node 114, or all GTP tunnels used for the F1-U interface associated with node 114, or all GTP tunnels used for the F1-U interface associated with node 114). For example, such a launch request associated with both node 113 and node 114 may include both information associated with node 113 and information associated with node 114 .

[0081] Then, in response to receiving the corresponding start request from CU-CP 102, CU-UP 103 may perform substantially the same operation for the corresponding start request to start or resume F1-U interface DL transmission associated with at least one DUID or IAB node address included in the corresponding start request. For example, in the case where the start request from CU-CP 102 includes at least one cell ID, CU-UP 103 may determine the F1-U interface associated with at least one cell based on the at least one cell ID included in the start request, and may start or resume DL transmission of the F1-U interface or GTP tunnel associated with at least one cell as indicated in the start request. Thus, for example, DL transmission of the F1-U interface (or GTP tunnel) between CU-UP 103 and node 111 (including DL F1-U traffic associated with node 113, DL F1-U traffic associated with node 114, and DL F1-U traffic associated with UE 115) can be started or resumed together by CU-UP 103 in response to a start-up request associated with node 111 from CU-CP 102, DL transmission of the F1-U interface (or GTP tunnel) between CU-UP 103 and node 113 (including DL F1-U traffic associated with UE 116, DL F1-U traffic associated with UE 117, and DL F1-U traffic associated with UE 118) can be started or resumed together by CU-UP 103 in response to a start-up request associated with node 113, and DL transmission of the F1-U interface (or GTP tunnel) between CU-UP 103 and node 114 (including DL F1-U traffic associated with UE 119) can be started or resumed together by CU-UP 103 in response to a start-up request associated with node 111. The F1-U traffic, and the DL F1-U traffic related to the UE 120 ) may be started or resumed together by the CU-UP 103 in response to a start request associated with the node 114 .

[0082] In another example, in the case where CU-UP 103 does not know information associated with descendant IAB nodes (including child IAB nodes 113 and 114) of node 111, the CU-CP 102 to CU-UP The start request associated with node 111 of 103 may further include information associated with a descendant IAB node of node 111, such as, but not limited to, one or more of the following: an ID of a DU of node 113; an address of node 113, such as, for example, an Internet Protocol address of an IAB-DU in node 113, or a Backhaul Adaptation Protocol (BAP) address of node 113, etc.; an ID of a cell associated with node 113; a routing ID associated with node 113; quality of service parameters of an F1-U service associated with node 113; an ID of a DU of node 114; an address of node 114, such as, for example, an Internet Protocol address of an IAB-DU in node 114, or a Backhaul Adaptation Protocol (BAP) address of node 114, etc.; an ID of a cell associated with node 114; a routing ID associated with node 114; quality of service parameters of an F1-U service associated with node 114, etc. For example, in the case where one or both of nodes 113 and 114 has more than one address, and / or has more than one DU, and / or is associated with more than one cell, and / or is associated with more than one routing path, the startup request associated with node 111 may further include one or more of the following: an ID list of DUs of node 113; an address list of node 113; an ID list of cells associated with node 113; a list of routing IDs associated with node 113; a list of service quality parameters for F1-U services associated with node 113; an ID list of DUs of node 114; an address list of node 114; an ID list of cells associated with node 114; a list of routing IDs associated with node 114; a list of service quality parameters for F1-U services associated with node 114, etc.

[0083] Then, in response to receiving the launch request from CU-CP 102, CU-UP 103 may start or resume F1-U interface DL transmission associated with the corresponding DU ID or IAB node address included in the launch request associated with node 111. For example, in the case where the launch request from CU-CP 102 includes at least one cell ID, CU-UP 103 may determine the F1-U interface associated with at least one cell based on the at least one cell ID included in the launch request, and may start or resume DL transmission of the F1-U interface or GTP tunnel associated with at least one cell as indicated in the launch request. Therefore, for example, DL transmission for the F1-U interface (or GTP tunnel) between CU-UP 103 and node 111 (including DL F1-U traffic related to node 113, DL F1-U traffic related to node 114, and DL F1-U traffic related to UE 115), DL transmission for the F1-U interface (or GTP tunnel) between CU-UP 103 and node 113 (including DL F1-U traffic related to UE 116, DL F1-U traffic related to UE 117, and DL F1-U traffic related to UE 118), and DL transmission for the F1-U interface (or GTP tunnel) between CU-UP 103 and node 114 (including DL F1-U traffic related to UE 119, and DL F1-U traffic related to UE 120) can be started or resumed together by CU-UP 103 in response to a start request associated with node 111 from CU-CP 102.

[0084] In another example, in the case where CU-UP 103 knows information associated with the descendant IAB nodes (including child IAB nodes 113 and 114) of node 111, CU-UP 103 may start or resume DL F1-U services related to both node 111 and one or more (e.g., all) descendant IAB nodes of node 111 in response to receiving a start request associated with node 111. For example, CU-UP 103 may start all DL F1-U services of terminal devices connected to node 111 and descendant IAB nodes of node 111.

[0085] For example, based on information associated with IAB nodes included in the launch request from CU-CP 102 , CU-UP 103 may determine that the launch request is associated with node 111 , and may know that descendant IAB nodes of node 111 include node 113 and node 114 . Then, for example, CU-UP 103 can together start or resume DL transmission of the F1-U interface between CU-UP 103 and node 111 (including DL F1-U services related to node 113, DL F1-U services related to node 114, and F1-U services related to UE 115), DL transmission of the F1-U interface between CU-UP 103 and node 113 (including DL F1-U services related to UE 116, DL F1-U services related to UE 117, and F1-U services related to UE 118), and DL transmission of the F1-U interface between CU-UP 103 and node 114 (including DL F1-U services related to UE 119, and DL F1-U services related to UE 120).

[0086] For example, CU-UP 103 may, in response to a start request associated with node 111 received from CU-CP 102, resume previously stopped DL transmissions of F1-U interfaces between CU-UP 103 and nodes 111, 113, and 114, respectively, by using previously cached DL F1-U data, so that DL transmissions of F1-U interfaces between CU-UP 103 and nodes 111, 113, and 114 may continue.

[0087] Figure 1 An example is illustrated in the case of donor topology adaptation, where the change of connections between IAB nodes is within the IAB network under the same donor 101 . Figure 2 Another example of DL transmission control in an IAB network in an embodiment is illustrated, which may be a case of inter-donor topology adaptation.

[0088] exist Figure 2 In the example shown, in addition to Figure 1 In addition to the IAB network shown, another IAB network including a donor 201 and a node 207 is also involved. Both the donor 101 and the donor 201 can be connected to a core network (CN) 205. At least one DU 204 of the donor 201 can be controlled by a CU of the donor 201 including a CU-CP 202 and a CU-UP 203, and serve the node 207 and the UE 206.

[0089] like Figure 2As shown, the connection 121 between the node 107 and the node 111 is now disconnected, for example, when the connection 121 or MT part of the node 111 is now to be detached from the cell associated with the node 107, and a new connection between the node 111 and the node 207 is desired, so that the node 111 originally served by the node 107 under the donor 101 will be served by the node 207 under another donor 201 after the inter-donor topology adaptation.

[0090] For the disconnection of node 111 from node 107, CU-CP 102 may send at least one request to CU-UP 103 to stop DL transmission of F1-U interfaces or GTP tunnels between CU-UP 103 and node 111 (e.g., all F1-U interfaces associated with node 111, or GTP tunnels for F1-U interfaces associated with node 111, or some GTP tunnels for F1-U interfaces associated with node 111), and / or stop DL transmission of F1-U interfaces or GTP tunnels between CU-UP 103 and one or more (e.g., all) descendant IAB nodes of node 111. The operations involved in this process may be similar to those already mentioned above. Figure 1 The operations related to the stop request are described and will not be repeated for the sake of simplicity and clarity.

[0091] For the DL F1-U data of the stopped DL transmission, for example, at least a portion of the DL F1-U data for the DL transmission of the F1-U interface between CU-UP 103 and node 111, and / or at least a portion of the DL F1-U data for the DL transmission of the F1-U interface between CU-UP 103 and a descendant IAB node of node 111 may be cached by CU-UP 103, or may be sent to donor 201, for example, via CN205 and then cached by CU-UP 203 for later resuming the DL transmission for the F1-U interface between CU-UP 103 and node 111 and / or a descendant IAB node of node 111.

[0092] When node 111 is connected to node 207 via new connection 208, CU-CP 202 may send a request to CU-UP 203 to start or enable DL transmission of the F1-U interface (or GTP tunnel) between CU-UP 203 and node 111, for example, including DL F1-U services related to node 113, DL F1-U services related to node 114, and DL F1-U services related to UE 115, which are transmitted via node 208 under donor 201 instead of the original node 107 under donor 101.

[0093] The activation request from CU-CP 202 to CU-UP 203 may be similar to the above reference Figure 1 The start request from CU-CP 102 to CU-UP 103 described above, and the operation of CU-UP 203 in response to the start request from CU-CP 202 may also be similar to the operation of CU-UP 103 in response to the start request from CU-CP 102, which has also been referred to above. Figure 1 describe.

[0094] For example, such a startup request associated with the node 111 from the CU-CP 202 to the CU-UP 203 may further include information associated with the node 111, including but not limited to one or more of the following: an ID of a DU of the node 111; an address of the node 111, for example, an Internet Protocol address of an IAB-DU in the node 111, or a Backhaul Adaptation Protocol (BAP) address of the node 111, etc.; an ID of a cell associated with the node 111; a routing ID associated with the node 111; a quality of service parameter of the F1-U service associated with the node 111, etc. In another example, such a startup request associated with the node 111 from the CU-CP 202 to the CU-UP 203 may include but not limited to one or more of the following: an ID list of at least one DU of the node 111; an address list of the node 111; an ID list of at least one cell associated with the node 111; a routing ID list associated with the node 111; and a quality of service parameter list of the F1-U service associated with the node 111.

[0095] In response to receiving the start request from CU-CP 202, CU-UP 203 may start or resume DL transmission of the F1-U interface associated with at least one DU ID or IAB node address included in the start request. For example, in the case where the start request from CU-CP 202 includes at least one cell ID, CU-UP 203 may determine the F1-U interface associated with at least one cell based on the at least one cell ID included in the start request, and may start or resume DL transmission of the F1-U interface or GTP tunnel associated with at least one cell as indicated in the stop request. Therefore, for example, DL transmission of the F1-U interface (or GTP tunnel) between CU-UP 203 and node 111 (including DL F1-U traffic related to node 113, DL F1-U traffic related to node 114, and DL F1-U traffic related to UE 115) can be started or resumed by CU-UP 203 in response to a start request associated with node 111 from CU-CP 202, via the new service node 207 under donor 201 instead of the original service node 107 under donor 101.

[0096] For example, in response to a received start request from CU-CP 202, CU-UP 203 may resume a previously stopped DL transmission of the F1-U interface (or GTP tunnel) between CU-UP 203 and node 111 by using DL F1-U data received from donor 101 via CN205 and cached at CU-UP 203, or by using DL F1-U data cached at CU-UP 103 and sent to donor 201 (which is, for example, received directly from donor 101, or indirectly received from donor 101 via CN205), so that the F1-U interface or the DL F1-U transmission at the user plane associated with node 111 can continue.

[0097] In the case where CU-UP 203 is unaware of information associated with descendant IAB nodes of node 111 (including child IAB nodes 113 and 114), for example, CU-CP 202 may further send another request to CU-UP 203 to start or resume DL transmission of the F1-U interface between CU-UP 203 and node 113 (e.g., all F1-U interfaces associated with node 113, or all GTP tunnels for the F1-U interface associated with node 113, or some GTP tunnels of the F1-U interface associated with node 113); and another request to start or resume DL transmission of the F1-U interface between CU-UP 203 and node 114 (e.g., all F1-U interfaces associated with node 114, or all GTP tunnels of the F1-U interface associated with node 114, or some GTP tunnels of the F1-U interface associated with node 114). For example, a startup request associated with node 113 from CU-CP 202 to CU-UP 203 may include information associated with node 113, such as the ID of the DU of node 113, the address of node 113 (e.g., the Internet Protocol address of the IAB-DU in node 113, or the Backhaul Adaptation Protocol (BAP) address of node 113, etc.), the ID of the cell associated with node 113, the routing ID associated with node 113, and at least one of the quality of service parameters of the F1-U service associated with node 113. The startup request associated with node 114 from CU-CP 202 to CU-UP 203 may include information associated with node 114, such as the ID of the DU of node 114, the address of node 114 (e.g., the Internet Protocol address of the IAB-DU in node 114, the Backhaul Adaptation Protocol (BAP) address of node 114, etc.), the ID of the cell associated with node 114, the routing ID associated with node 114, and at least one of the quality of service parameters of the F1-U service associated with node 114. For example, the startup request associated with node 113 from CU-CP 202 to CU-UP 203 may further include an ID list of DUs of node 113, and / or an address list of node 113, and / or an ID list of cells associated with node 113, and / or a routing ID list associated with node 113, and / or a service quality parameter list of F1-U services associated with node 113, and the startup request associated with node 114 from CU-CP 202 to CU-UP 203 may further include an ID list of DUs of node 114, and / or an address list of node 114, and / or an ID list of cells associated with node 114, and / or a routing ID list associated with node 114, and / or a service quality parameter list of F1-U services associated with node 114.

[0098] In another example, in the case where CU-UP 203 is unaware of information associated with descendant IAB nodes of node 111 (including child IAB nodes 113 and 114), CU-CP 202 may further send another request to CU-UP 203 to start or resume at least one of: DL transmission of the F1-U interface between CU-UP 203 and node 113 (e.g., all F1-U interfaces associated with node 113, or all GTP tunnels used for the F1-U interface associated with node 113, or some GTP tunnels used for the F1-U interface associated with node 113); and DL transmission of the F1-U interface between CU-UP 203 and node 114 (e.g., all F1-U interfaces associated with node 114, or all GTP tunnels used for the F1-U interface associated with node 114, or some GTP tunnels used for the F1-U interface associated with node 114). For example, such a launch request associated with both node 113 and node 114 may include both information associated with node 113 and information associated with node 114 .

[0099] Then, in response to receiving the corresponding start request from CU-CP 202, CU-UP 203 may perform substantially the same operation for the corresponding start request to start or resume F1-U interface DL transmission associated with at least one DUID or IAB node address included in the corresponding start request. For example, in the case where the start request from CU-CP 202 includes at least one cell ID, CU-UP 203 may determine the F1-U interface associated with at least one cell based on the at least one cell ID included in the start request, and may start or resume DL transmission of the F1-U interface or GTP tunnel associated with at least one cell as indicated in the start request. Thus, for example, DL transmission of the F1-U interface (or GTP tunnel) between CU-UP 203 and node 111 (including DL F1-U traffic associated with node 113, DL F1-U traffic associated with node 114, and DL F1-U traffic associated with UE 115) can be started or resumed together by CU-UP 203 in response to a start request associated with node 111 from CU-CP 202, DL transmission of the F1-U interface (or GTP tunnel) between CU-UP 203 and node 113 (including DL F1-U traffic associated with UE 116, DL F1-U traffic associated with UE 117, and DL F1-U traffic associated with UE 118) can be started or resumed together by CU-UP 203 in response to a start request associated with node 113 from CU-CP 202, and DL transmission of the F1-U interface (or GTP tunnel) between CU-UP 203 and node 114 (including DL F1-U traffic associated with UE 116, DL F1-U traffic associated with UE 117, and DL F1-U traffic associated with UE 118) can be started or resumed together by CU-UP 203 in response to a start request associated with node 113 from CU-CP 202. 119-related DL F1-U traffic, and DL F1-U traffic related to UE 120) can be started or resumed together by CU-UP 203 in response to a start request associated with node 114 from CU-CP 202.

[0100] In another example, in the case where CU-UP 203 does not know information associated with descendant IAB nodes (including child IAB nodes 113 and 114) of node 111, the CU-CP 202 to CU-UP The start request 203 associated with node 111 may further include information associated with a descendant IAB node of node 111, such as, but not limited to, one or more of the following: an ID of a DU of node 113; an address of node 113, such as, for example, an Internet Protocol address of an IAB-DU in node 113, or a Backhaul Adaptation Protocol (BAP) address of node 113, etc.; an ID of a cell associated with node 113; a routing ID associated with node 113; and quality of service parameters of an F1-U service associated with node 113; an ID of a DU of node 114; an address of node 114, such as, for example, an Internet Protocol address of an IAB-DU in node 114, or a Backhaul Adaptation Protocol (BAP) address of node 114, etc.; an ID of a cell associated with node 114; a routing ID associated with node 114; and quality of service parameters of an F1-U service associated with node 114. For example, in the case where one or both of nodes 113 and 114 has more than one address, and / or has more than one DU, and / or is associated with more than one cell, the startup request from CU-CP 202 to CU-UP 203 associated with node 111 may further include one or more of the following: an ID list of DUs of node 113; an address list of node 113; an ID list of cells associated with node 113; a list of routing IDs associated with node 113; a list of service quality parameters for F1-U services associated with node 113; an ID list of DUs of node 114; an address list of node 114; an ID list of cells associated with node 114; a list of routing IDs associated with node 114; a list of service quality parameters for F1-U services associated with node 114, and the like.

[0101] Then, in response to receiving the start request from CU-CP 202, CU-UP 203 may start or resume DL transmission of the F1-U interface associated with the corresponding DU ID or IAB node address included in the start request. For example, in the case where the start request from CU-CP 202 includes at least one cell ID, CU-UP 203 may determine the F1-U interface associated with at least one cell based on the at least one cell ID included in the stop request, and may start or resume DL transmission of the F1-U interface or GTP tunnel associated with at least one cell as indicated in the start request. Therefore, for example, DL transmission for the F1-U interface (or GTP tunnel) between CU-UP 203 and node 111 (including DL F1-U traffic related to node 113, DL F1-U traffic related to node 114, and DL F1-U traffic related to UE 115), DL transmission for the F1-U interface (or GTP tunnel) between CU-UP 203 and node 113 (including DL F1-U traffic related to UE 116, DL F1-U traffic related to UE 117, and DL F1-U traffic related to UE 118), and DL transmission for the F1-U interface (or GTP tunnel) between CU-UP 203 and node 114 (including DL F1-U traffic related to UE 119, and DL F1-U traffic related to UE 120) can be started or resumed together by CU-UP 203 in response to a start request associated with node 111 from CU-CP 202.

[0102] In another example, in the case where CU-UP 203 knows information associated with the descendant IAB nodes (including child nodes 113 and 114) of node 111, CU-UP 203 may start or resume DL F1-U services related to both node 111 and one or more (e.g., all) descendant IAB nodes of node 111 in response to receiving a start request associated with node 111. For example, CU-UP 203 may start all DL F1-U services of terminal devices connected to node 111 and descendant IAB nodes of node 111.

[0103] For example, based on the information associated with the IAB nodes included in the launch request from CU-CP 202 , CU-UP 203 may determine that the launch request is associated with node 111 , and may know that the descendant IAB nodes of node 111 include node 113 and node 114 . Then, for example, CU-UP 203 can together start or resume DL transmission of the F1-U interface (or GTP tunnel) between CU-UP 203 and node 111 (including DL F1-U services related to node 113, DL F1-U services related to node 114, and DL F1-U services related to UE 115), DL transmission of the F1-U interface (or GTP tunnel) between CU-UP 203 and node 113 (including DL F1-U services related to UE 116, DL F1-U services related to UE 117, and DL F1-U services related to UE 118), and DL transmission of the F1-U interface (or GTP tunnel) between CU-UP 203 and node 114 (including DL F1-U services related to UE 119, and DL F1-U services related to UE 120).

[0104] For example, in response to a startup request received from CU-CP 202, CU-UP 203 may resume DL transmission of the F1-U interface (or GTP tunnel) between CU-UP 203 and node 111 by using DL F1-U data previously received from donor 101 via CN205 and cached at CU-UP 203, or by using DL F1-U data cached at CU-UP 103 and sent to donor 201 (which is, for example, received directly from donor 101, or indirectly received from donor 101 via CN205), so that DL transmission at the F1-U interface or at the user plane associated with node 111 can continue.

[0105] Figures 3 to 6 The diagram illustrates an example of the operation of the CU-CP and CU-UP for controlling DL transmission in different embodiments, where an example of the CU-CP 301 may include: Figure 1 or Figure 2 The CU-CP 102 or 202 in the above examples shown, and examples of the CU-UP 302 may include Figure 1 or Figure 2 CU-UP 103 or 203 in the above examples is shown.

[0106] like Figure 3As shown, in one embodiment, the CU-CP 301 may determine to control the DL transmission of the F1-U interface (e.g., all F1-U interfaces associated with the IAB node, or all GTP tunnels for the F1-U interface associated with the IAB node, or some GTP tunnels for the F1-U interface associated with the IAB node), which is between the CU-UP and the IAB node, and thus may be associated with the IAB node in operation 303. For example, the DL transmission for the F1-U interface associated with the IAB node may include DL F1-U services related to at least one descendant IAB node or UE served by the IAB node. In one embodiment, the control may include starting (or enabling or restarting or resuming) the DL transmission. In another embodiment, the control may further include stopping (or disabling) the DL transmission. In various embodiments, the CU-CP 301 may perform operation 303 in any suitable manner or method. For example, CU-CP 301 may make such a determination in operation 303 in response to receiving a handover message, or in response to detecting that one or more predetermined conditions are satisfied (eg, no traffic on the IAB node for a predetermined period of time, or a radio link failure with the IAB node).

[0107] Then, the CU-CP 301 may send a request 304 to the CU-UP 302 to control the DL transmission of the F1-U interface between the CU-UP 302 and the IAB node, wherein the request 304 is not associated with a single specific UE, but it is related to the entire F1-U interface. Since the request is not of UE-associated nature, it is also referred to as non-UE-associated signaling. The non-UE-associated signaling request may include information associated with the IAB node determined by the CU-CP 301 in operation 303, such as but not limited to the ID of the DU of the determined IAB node, the address of the determined IAB node, the ID of the cell associated with the determined IAB node, the routing ID associated with the determined IAB node, the service quality parameters of the business associated with the determined IAB node, etc. One or more. Depending on the determination in operation 303, in an embodiment, for example, in the case of attachment or reconnection of the IAB node to the IAB network, the request 304 may be a start request to start or resume the DL transmission of the F1-U interface between the CU-UP 302 and the determined IAB node. In another embodiment, the request 304 may be a stop request to stop DL transmission of the F1-U interface between the CU-UP 302 and a determined IAB node, for example, if the IAB node is detached or disconnected from the IAB network.

[0108] Then, in operation 305, in response to receiving the request 304, the CU-UP 302 may control the DL transmission of the F1-U interface between the CU-UP 302 and the IAB node, for example, in association with at least one of the following: the corresponding DU ID of the corresponding DU in the IAB node indicated in the request 304, and / or at least one address of the IAB node indicated in the request 304, and / or at least one cell ID indicated in the request 304, and / or at least a routing ID, and / or at least one quality of service parameter indicated in the request 304. For example, in operation 305, if the request 304 is a stop request, the CU-UP 302 may stop the DL transmission of the F1-U interface between the CU-UP 302 and the IAB node as indicated in the request 304, thereby stopping the DL transmission of all F1-U GTP tunnels terminated at the DU of the IAB node. In another example, the CU-UP 302 may stop the DL transmission of all F1-U GTP tunnels corresponding to the addresses as indicated in the request 304. In yet another example, the CU-UP 302 may stop DL transmission of all F1-U GTP tunnels corresponding to the cell identity as indicated in the request 304. For example, for all UEs served by the cell as indicated in the request 304, the CU-UP 302 may stop DL transmission of all F1-U GTP tunnels associated with those UEs. In yet another example, the CU-UP 302 may stop DL transmission of all F1-U GTP tunnels corresponding to the routing path as indicated in the request 304. For example, the traffic of these F1-U GTP tunnels is sent to the IAB node via the routing path as indicated by the routing ID in the request 304. If the request 304 is a start request, the CU-UP 302 may start DL transmission of the F1-U interface between the CU-UP 302 and the IAB node as indicated in the request 304, thereby starting DL transmission of all F1-U GTP tunnels terminated at the DU of the IAB node. In another example, the CU-UP 302 may initiate DL transmission of all F1-U GTP tunnels corresponding to the identification as indicated in the request 304. In yet another example, the CU-UP 302 may initiate DL transmission of all F1-U GTP tunnels corresponding to the cell identification as indicated in the request 304. For example, for all UEs served by the cell as indicated in the request 304, the CU-UP 302 may initiate DL transmission of all F1-U GTP tunnels associated with those UEs. In yet another example, the CU-UP 302 may initiate DL transmission of all F1-U GTP tunnels corresponding to the routing path as indicated in the request 304. As indicated by the routing ID in the request 304, the traffic of these F1-U GTP tunnels is sent to the IAB node via the routing path.For example, CU-UP 302 previously stopped DL transmission of a dual-connected IAB node that declared a problem with the connection to one parent node. After the connection is restored, CU-CP 310 can request CU-UP 302 to start DL transmission of all GTP tunnels using the routing ID that corresponds to the routing path using the parent node. CU-UP 302 can use the routing ID to start DL transmission of all F1-U GTP tunnels that correspond to the routing path using the parent node.

[0109] In another embodiment, in operation 401, when CU-UP 302 knows information associated with descendant nodes of the IAB node as indicated in request 304, such as Figure 4 The CU-UP 302 shown may further control the DL transmission of the F1-U interface between the CU-UP 302 and the descendant node of the IAB node. For example, in operation 401, if the request 304 is a start request, the CU-UP 302 may further start or resume the DL transmission of the F1-U interface between the CU-UP 302 and the descendant node of the IAB node. In operation 401, if the request 304 is a stop request, the CU-UP 302 may further stop the DL transmission of the F1-U interface between the CU-UP 302 and the descendant node of the IAB node.

[0110] In another embodiment, in the case where the CU-UP 302 does not know the information associated with the descendant nodes of the IAB node, such as Figure 5As shown, request 501 may be sent from CU-CP 301 to CU-UP 302 instead of request 304. For example, request 501 may include information associated with both the IAB node determined in operation 303 and the descendant node of the IAB node. For example, request 501 may include the information in request 304. In addition, for the descendant node of the IAB node, request 501 may further include one or more of the DU ID of the descendant node, the address of the descendant node, the cell ID associated with the descendant node, the routing ID associated with the descendant node, and the quality of service parameters of the business associated with the descendant node. Therefore, when CU-UP 302 does not have information associated with the descendant node of the IAB node as indicated in request 501, CU-UP 302 may also be enabled to perform operation 502 to control DL transmission for the F1-U interface between CU-UP 302 and the descendant node of the IAB node. For example, if the request 501 is a start request, the CU-UP 302 may further start or resume DL transmission of the F1-U interface between the CU-UP 302 and the descendant node of the IAB node in operation 502. If the request 501 is a stop request, the CU-UP 302 may further stop DL transmission of the F1-U interface between the CU-UP 302 and the descendant node of the IAB node in operation 502.

[0111] In another embodiment, in the case where the CU-UP 302 does not know the information associated with the descendant nodes of the IAB node, for example, Figure 6 As shown, except for Figure 3 In addition to the operations shown, for the first descendant node of the IAB node determined in operation 303 and indicated in request 304, the CU-CP 301 may further send another request 601 to control the DL transmission of the F1-U interface or GTP tunnel between the CU-UP 302 and the first descendant node. If request 304 is a start request, request 601 may also be a start request. If request 304 is a stop request, request 601 may also be a stop request. In various embodiments, request 601 may include, but is not limited to, one or more of the following: DU ID of the first descendant node; address of the first descendant node; cell ID associated with the first descendant node; routing ID associated with the first descendant node; quality of service parameters of the service associated with the first descendant node, etc.

[0112] Then, in operation 602, in response to receiving request 601, CU-UP 302 may control DL transmission of the F1-U interface between CU-UP 302 and the first descendant node, for example, in association with the DU ID of the first descendant node indicated in request 601, and / or the address of the first descendant node indicated in request 601, and / or the cell ID indicated in request 601. For example, in operation 602, if request 601 is a stop request, CU-UP 302 may stop DL transmission of the F1-U interface between CU-UP 302 and the first descendant node as indicated in request 601, thereby stopping DL transmission of all F1-U GTP tunnels terminated at the DU of the first descendant node. In another example, CU-UP 302 may stop DL transmission of all F1-U GTP tunnels corresponding to the address as indicated in request 601. In yet another example, CU-UP 302 may stop DL transmission of all F1-U GTP tunnels corresponding to the cell identifier as indicated in request 601. For example, for all UEs served by the cell as indicated in request 601, CU-UP 302 may stop DL transmission of all F1-U GTP tunnels associated with those UEs. In yet another example, CU-UP 302 may stop DL transmission of all F1-U GTP tunnels corresponding to the routing path as indicated in request 601. For example, as indicated by the routing ID in request 601, the traffic of these F1-U GTP tunnels is sent to the IAB node via the routing path. If request 601 is a start request, CU-UP 302 may start DL transmission of the F1-U interface between CU-UP 302 and the first descendant node as indicated in request 601, thereby starting DL transmission of all F1-U GTP tunnels terminated at the DU of the first descendant node. In another example, CU-UP 302 may start DL transmission of all F1-U GTP tunnels corresponding to the address indicated in request 601. In yet another example, the CU-UP 302 may initiate DL transmission of all F1-U GTP tunnels corresponding to the cell identity as indicated in the request 601. For example, for all UEs served by the cell as indicated in the request 601, the CU-UP 302 may initiate DL transmission of all F1-U GTP tunnels associated with those UEs. In yet another example, the CU-UP 302 may initiate DL transmission of all F1-U GTP tunnels corresponding to the routing path as indicated in the request 601. The traffic of these F1-U GTP tunnels is sent to the IAB node via the routing path as indicated by the routing ID in the request 601. For example, the CU-UP 302 previously stopped DL transmission of a dual-connected IAB node that declared a problem with the connection to a parent node.After the connection is restored, CU-CP 310 may request CU-UP 302 to start DL transmission of all GTP tunnels using the routing ID corresponding to the routing path using the parent node. CU-UP 302 may use the routing ID to start DL transmission of all F1-U GTP tunnels corresponding to the routing path using the parent node.

[0113] In addition, for the second descendant node of the IAB node determined in operation 303, the CU-CP 301 may also send another request 603 to control the DL transmission of the F1-U interface or GTP tunnel between the CU-UP 302 and the second descendant node. If request 304 is a start request, request 603 may also be a start request. If request 304 is a stop request, request 603 may also be a stop request. In various embodiments, request 603 may include, but is not limited to, one or more of the following: DU ID of the second descendant node; address of the second descendant node; cell ID associated with the second descendant node; routing ID associated with the second descendant node; quality of service parameters for services associated with the second descendant node, etc.

[0114] Then, in response to receiving the request 603, in operation 604, the CU-UP 302 may control the DL transmission of the F1-U interface between the CU-UP 302 and the second descendant node or the F1-U interface between the GTP tunnels, which is, for example, associated with the DU ID of the second descendant node indicated in the request 603, and / or the address of the second descendant node indicated in the request 603, and / or the cell ID indicated in the request 603. For example, in operation 604, if the request 603 is a stop request, the CU-UP 302 may stop the DL transmission of the F1-U interface between the CU-UP 302 and the second descendant node as indicated in the request 603, thereby stopping the DL transmission of all F1-U GTP tunnels terminated at the DU of the second descendant node. In another example, the CU-UP 302 may stop the DL transmission of all F1-U GTP tunnels corresponding to the addresses as indicated in the request 603. In yet another example, CU-UP 302 may stop DL transmission of all F1-U GTP tunnels corresponding to the cell identifier as indicated in request 603. For example, for all UEs served by the cell as indicated in request 603, CU-UP 302 may stop DL transmission of all F1-U GTP tunnels associated with those UEs. In yet another example, CU-UP 302 may stop DL transmission of all F1-U GTP tunnels corresponding to the routing path as indicated in request 603. For example, the traffic of these F1-U GTP tunnels is sent to the IAB node via the routing path indicated by the routing ID in request 603. If request 603 is a start request, CU-UP 302 may start DL transmission of the F1-U interface between CU-UP 302 and the second descendant node as indicated in request 603, thereby starting DL transmission of all F1-U GTP tunnels terminated at the DU of the second descendant node. In another example, CU-UP 302 may initiate DL transmission of all F1-U GTP tunnels corresponding to the address indicated in request 603. In yet another example, CU-UP 302 may initiate DL transmission of all F1-U GTP tunnels corresponding to the cell identifier as indicated in request 603. For example, for all UEs served by the cell as indicated in request 603, CU-UP 302 may initiate DL transmission of all F1-U GTP tunnels associated with those UEs. In yet another example, CU-UP 302 may initiate DL transmission of all F1-U GTP tunnels corresponding to the routing path as indicated in request 603. For example, the traffic of these F1-U GTP tunnels is sent to the IAB node via the routing path as indicated by the routing ID in request 603. For example, CU-UP 302 previously stopped DL transmission of a dual-connected IAB node that declared a problem with the connection of a parent node.After the connection is restored, CU-CP 310 may request CU-UP 302 to start DL transmission of all GTP tunnels using the routing ID corresponding to the routing path using the parent node. CU-UP 302 may start DL transmission of all F1-U GTP tunnels using the routing ID corresponding to the routing path using the parent node.

[0115] It should be understood that the present application is not limited to the above examples. Figure 6 In the example shown, different signaling sequences for each request may be adopted, and different operation orders may also be adopted in the above examples. In another example, request 304 or 501 or 601 or 603 may include information associated with another one or more IAB nodes in the IAB network, which is not limited to the descendant nodes of the determined IAB node (e.g., node 111), so that control of DL transmission associated with any one or more specified or expected IAB nodes may be allowed. In another example, any two or more of requests 304, 601 and 603 may be combined into one request. In addition, it should be understood that the wording in the singular form may also have the meaning of the plural form. For example, "the address of the IAB node" may further include examples of "at least one address of the IAB node", or "one or more addresses of the IAB node", or "a list of addresses of the IAB node", etc.

[0116] Figure 7 An example method 700 for controlling DL transmission in an IAB network is illustrated, which may be performed, for example, in a device associated with a CU-CP (eg, CU-CP 102, 202, or 301 in the above examples) of a donor (eg, donor 101 or 201 in the above examples) in the IAB network.

[0117] like Figure 7 As shown, the example method 700 may include operation 701, that is, determining another device associated with a CU-UP (eg, CU-UP 103 or 203 or 302 in the above example) of a donor in the IAB network and a node in the IAB network (eg, Figure 1 and Figure 2 111 in the example shown) between the first interface (eg, F1-U interface). Examples of operation 701 may include: Figures 3 to 6 Operation 303 is shown.

[0118] In addition, the example method 700 may further include an operation 702, that is, sending a first non-UE associated signaling request (e.g., request 304 or 501 in the above example) to another device associated with a CU-UP of a donor in the IAB network (e.g., CU-UP 103 or 203 or 302 in the above example) to control a first DL transmission of a first interface (e.g., F1-U interface) between the other device and the node. The first non-UE associated signaling request may include information associated with the node, which may include but is not limited to one or more of the following: a DU ID of the node, an address of the node, a cell ID associated with the node, a routing ID associated with the node, a quality of service parameter value of a service associated with the node, etc.

[0119] Depending on the determination made in operation 701, the first non-UE-associated signaling request may be a request to start a first DL transmission between another device and a node, or may be a request to start a first DL transmission between another device and a node.

[0120] Therefore, batch control of DL transmission of at least one (e.g., all) F1-U interfaces or GTP tunnels between the CU-UP and a determined IAB node (e.g., including DL F1-U services of UEs and descendant IAB nodes served by the determined IAB node) can be allowed while reducing the signaling load, by which, for example, potential packet loss and resource waste can be avoided or mitigated.

[0121] In some embodiments, the first non-UE-associated signaling request may further include information associated with another node in the IAB network, such as information associated with a descendant node of the node in the IAB network (e.g., one or more of the nodes 113 and 114, which are child nodes of the node 111), and examples of the first non-UE-associated signaling request in these embodiments may include the request 501 in the above example. For example, for another node in the IAB network that may or may not be a descendant of the node, the first non-UE-associated signaling request may further include one or more of the following: DU ID of another node; address of another node; cell ID associated with another node; routing ID associated with another node; quality of service parameter value of a service associated with another node, etc. Therefore, even if another device associated with the CU-UP does not know information associated with the descendant node of the node or the topology of the IAB network, DL transmission of the F1-U interface between the CU-UP and multiple nodes in the IAB network (e.g., associated with both the node and at least one descendant node of the node) can be controlled.

[0122] In some embodiments, the example method 700 may further include an operation of sending a second non-UE-associated signaling request (e.g., request 601 and request 603 in the above example) to another device associated with the CU-UP. In some embodiments, the second non-UE-associated signaling request may be a request to start a second DL transmission of a second interface (e.g., an F1-U interface) between another device and a descendant node of the node. In some embodiments, the second non-UE-associated signaling request may be a request to stop a second DL transmission of the second interface. For example, the second non-UE-associated signaling request may include information associated with the descendant node. For example, the second non-UE-associated signaling request may include one or more of the following: a DU ID of a descendant node; an address of a descendant node; a cell ID associated with a descendant node; a routing ID associated with a descendant node; a quality of service parameter value for a service associated with a descendant node, etc. Therefore, even if another device associated with the CU-UP does not know the information associated with the descendant node of the node, the DL transmission of the F1-U interface or GTP tunnel between the CU-UP of the node and the descendant node can be controlled.

[0123] Figure 8 An example apparatus 800 for controlling DL transmission in an IAB network is illustrated, which may be at least a portion of an apparatus associated with a CU-CP (eg, CU-CP 102, 202, or 301 in the above examples) of a donor (eg, donor 101 or 201 in the above examples) in the IAB network.

[0124] like Figure 8 As shown, the example apparatus 800 may include at least one processor 801 and at least one memory 802, and the memory 802 may include computer program code 803. The at least one memory 802 and the computer program code 803 may be configured to, together with the at least one processor 801, cause the apparatus 800 to at least perform at least the operations of the above example method 700.

[0125] In various embodiments, at least one processor 801 in the example device 800 may include, but is not limited to, at least one hardware processor, including at least one microprocessor such as a central processing unit (CPU), a portion of at least one hardware processor, and any other suitable dedicated processor such as those developed based on, for example, a field programmable gate array (FPGA) and an application specific integrated circuit (ASIC). In addition, the at least one processor 801 may further include Figure 8 At least one other circuit or element not shown.

[0126] In various embodiments, at least one memory 802 in the example apparatus 800 may include at least one storage medium in various forms, such as volatile memory and / or non-volatile memory. Volatile memory may include, but is not limited to, for example, random access memory (RAM), cache, etc. Non-volatile memory may include, but is not limited to, for example, read-only memory (ROM), hard disk, flash memory, etc. In addition, at least the memory 802 may include, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared or semiconductor systems, devices or devices, or any combination of the above.

[0127] Additionally, in various embodiments, the example apparatus 800 may further include at least one other circuit, element, and interface, such as at least one IO interface, at least one antenna element, and the like.

[0128] In various embodiments, the circuits, components, elements, and interfaces in the example device 800, including at least one processor 801 and at least one memory 802, can be coupled together in any suitable manner (e.g., electrically, magnetically, optically, electromagnetically, etc.) via any suitable connection (including but not limited to buses, crossbar switches, wiring, and / or wireless lines).

[0129] Fig. 9 Another example apparatus 900 for controlling DL transmission in an IAB network is illustrated, which may be at least part of an apparatus associated with a CU-CP (e.g., CU-CP 102, 202, or 301 in the above examples) of a donor (e.g., donor 101 or 201 in the above examples) in the IAB network.

[0130] like Fig. 9 As shown, the example device 900 may include means 901 for performing operation 701 of the example method 700 and means 902 for performing operation 702 of the example method 700. In one or more other embodiments, the example device 900 may further include at least one I / O interface, at least one antenna element, etc. In some embodiments, the example of the means in the device 900 may include circuits. In some embodiments, the example of the means may further include software modules and any other suitable functional entities. In some embodiments, one or more additional means may be included in the device 900 for performing one or more additional operations of the example method 900.

[0131] The term "circuitry" throughout this application may refer to one or more or all of the following: (a) a hardware-only implementation of a circuit (such as an implementation in analog and / or digital circuits only); (b) a combination of hardware circuitry and software, such as (where applicable); (i) a combination of analog and / or digital hardware circuitry and software / firmware; and (ii) a hardware processor and any portion of software (including a digital signal processor), software, and memory that work together to enable a device such as a mobile phone or server to perform various functions); and (c) a hardware circuit and / or processor that requires software (e.g., firmware) to operate, such as a microprocessor or a portion of a microprocessor, but the software may not be present when not required to operate. This definition of circuitry applies to one or all uses of the term in this application (including in any claims). As a further example, as used in this application, the term "circuitry" also covers an implementation of a hardware circuit or processor (or multiple processors) or a portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. For example, and where applicable to a claim element, the term circuitry also covers a baseband integrated circuit or a processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular network device, or other computing or networking device.

[0132] Fig.10 An example method 1000 for controlling DL transmission in an IAB network is illustrated, which may be performed, for example, in a device associated with a CU-UP (e.g., CU-UP 103 or 203 or 302 in the above examples) of a donor (e.g., donor 101 or 201 in the above examples) in the IAB network to cooperate with the example method 700.

[0133] like Fig.10 As shown, the example method 1000 may include operation 1001, that is, receiving a request (e.g., request 304 or 501 or 601 or 603 in the above example) from another device associated with a CU-CP of a donor in an IAB network (e.g., CU-CP 102 or 202 or 301 in the above example) to control a first DL transmission (e.g., F1-U interface) of a first interface between the device and a node in the IAB network (e.g., node 111 in the above example). For example, the request may include information associated with the node, such as, but not limited to, one or more of the following: DU ID of the node; address of the node; cell ID associated with the node; routing ID associated with the node; quality of service parameter value of a service associated with the node, etc.

[0134] In addition, the example method 1000 may further include an operation 1002 of controlling a first DL transmission of the first interface based on the request received in operation 1001. Depending on the request received in operation 1001, the control in operation 1002 may include stopping the first DL transmission of the first interface if the request indicates stopping the first DL transmission of the first interface, or starting the first DL transmission of the first interface if the request indicates starting the first DL transmission of the first interface.

[0135] Therefore, batch control of DL transmission of the F1-U interface or GTP tunnel (for example, all F1-U interfaces associated with the IAB node, or all GTP tunnels of the F1-U interface associated with the IAB node, or some GTP tunnels of the F1-U interface associated with the IAB node) between the CU-UP and a determined IAB node (including DL F1-U services of the UE and descendant IAB nodes served by the determined IAB node) can be allowed while reducing the signaling load, by which, for example, potential packet loss and resource waste can be avoided or mitigated.

[0136] In some embodiments, the request may further include information associated with another node in the IAB network, such as a descendant node of the node in the IAB network (e.g., one or more of node 113 and node 114, which are descendant nodes of node 111), and examples of requests in these embodiments may include request 501 in the above example. For example, the request may further include one or more of the following: a DU ID of another node; an address of another node; a cell ID associated with another node; a routing ID associated with another node; a quality of service parameter value of a service associated with another node, etc. Therefore, even if another device associated with the CU-UP does not know information associated with the descendant nodes of the node or the topology of the IAB network, the DL transmission or F1-U interface between the CU-UP and multiple nodes in the IAB network (e.g., both the node and at least one descendant node of the node) can be controlled together.

[0137] In some embodiments, for example, where the device associated with the CU-UP knows information associated with the descendant node of the node (e.g., from a request or according to any other suitable configuration), the example method 1000 may further include: for example, when the request indicates to stop the first DL of the first interface, the operation of stopping the second DL transmission of the second interface between the device and the descendant node of the node; or, for example, when the request indicates to start the first DL transmission of the first interface, the operation of starting the second DL transmission of the second interface. Therefore, DL transmissions associated with, for example, both the node and the descendant node of the node can be controlled together.

[0138] Fig.11 An example apparatus 1100 for controlling DL transmission in an IAB network is illustrated, which may be at least part of an apparatus associated with a CU-UP (eg, CU-UP 103, 203, or 302 in the above examples) of a donor (eg, donor 101 or 201 in the above examples) in the IAB network.

[0139] like Fig.11 As shown, the example apparatus 1100 may include at least one processor 1101 and at least one memory 1102, and the memory 1102 may include computer program code 1103. The at least one memory 1102 and the computer program code 1103 may be configured to, together with the at least one processor 1101, cause the apparatus 1100 to at least perform at least the operations of the example method 1000 described above.

[0140] In various embodiments, at least one processor 1101 in the example device 1100 may include, but is not limited to, at least one hardware processor, including at least one microprocessor such as a CPU, a portion of at least one hardware processor, and any other suitable dedicated processor such as a processor developed based on an FPGA and an ASIC. In addition, at least one processor 1101 may also include Fig.11 At least one other circuit or element not shown.

[0141] In various embodiments, at least one memory 1102 in the example apparatus 1100 may include at least one storage medium in various forms, such as volatile memory and / or non-volatile memory. Volatile memory may include, but is not limited to, for example, RAM, cache, etc. Non-volatile memory may include, but is not limited to, for example, ROM, hard disk, flash memory, etc. In addition, at least the memory 1102 may include, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared or semiconductor systems, devices or equipment, or any combination thereof.

[0142] Additionally, in various embodiments, the example apparatus 1100 may further include at least one other circuit, element, and interface (eg, at least one I / O interface), at least one antenna element, and the like.

[0143] In various embodiments, the circuits, components, elements, and interfaces in the example device 1100, including at least one processor 1101 and at least one memory 1102, can be coupled together in any suitable manner (e.g., electrically, magnetically, optically, electromagnetically, etc.) via any suitable connection (including but not limited to buses, cross switches, wiring and / or wireless lines).

[0144] Fig.12Another example apparatus 1200 for controlling DL transmission in an IAB network is illustrated, which may be at least part of an apparatus associated with a CU-UP (eg, CU-UP 103, 203, or 302 in the above examples) of a donor (eg, donor 101 or 201 in the above examples) in the IAB network.

[0145] like Fig.12 As shown, the example device 1200 may include means 1201 for performing operation 1001 of the example method 1000 and means 1202 for performing operation 1002 of the example method 1000. In one or more other embodiments, at least one IO interface, at least one antenna element, etc. may be further included in the example device 1200. In some embodiments, the example of the means in the device 1200 may include a circuit. In some embodiments, the example of the means may further include a software module and any other suitable functional entity. In some embodiments, one or more additional means may be included in the device 1200 for performing one or more additional operations of the example method 1200.

[0146] Another example embodiment may involve computer program code or instructions that cause an apparatus to perform at least the above-described corresponding method. Another example embodiment may involve a computer-readable medium having such computer program code or instructions stored thereon. In some embodiments, such a computer-readable medium may include at least one storage medium in various forms, such as volatile memory and / or non-volatile memory. Volatile memory may include, but is not limited to, for example, RAM, cache, etc. Non-volatile memory may include, but is not limited to, ROM, hard disk, flash memory, etc. Non-volatile memory may also include, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared or semiconductor systems, devices or equipment or any combination thereof.

[0147] It should be understood that the present application is not limited to the above examples or embodiments. For example, in another embodiment, the request and response use non-UE associated signaling, the interface between the CU-CP 102 / 202 / 301 and the CU-UP 103 / 203 / 302 may be an E1 interface, and the request and response between them may be E1 application protocol (E1AP) messages.

[0148] Unless the context clearly requires otherwise, throughout the specification and claims, the words "include", "comprises", etc. should be interpreted in an inclusive sense, rather than exclusive or exhaustive; that is, in the sense of "including but not limited to". As generally used herein, the term "coupled" refers to two or more elements that can be directly connected, or connected through one or more intermediate elements. Similarly, as generally used herein, the term "connected" refers to two or more elements that can be directly connected or connected through one or more intermediate elements. In addition, when used in this application, the words "herein", "above", "below" and words of similar meanings should refer to the application as a whole, rather than to any particular part of the application. Where the context permits, words used in the description in the singular or plural may also include the plural or singular, respectively. The word "or" refers to a list of two or more items, and the word covers all the following interpretations of the word: all items in the list, any item in the list, and any combination of items in the list. In addition, it should be understood that modifiers such as "first" and "second" throughout the specification are used to distinguish different elements, components, devices, operations, etc., and are not intended to refer to some specific elements, components, devices, operations, etc., or to emphasize the order, importance, priority, etc. of the corresponding elements, components, devices, operations, etc. For example, in one embodiment, the "first device" may be the "second device" in another embodiment.

[0149] Furthermore, conditional language used herein, such as "may," "could," "might," "can," "for example," "example," "such as," and the like, unless otherwise specifically stated or otherwise understood in the context of use, is generally intended to convey that some embodiments include and other embodiments do not include certain features, elements, and / or states. Thus, such conditional language is generally not intended to indicate that features, elements, and / or states are in any way required for one or more embodiments, or that one or more embodiments necessarily include logic for determining that such features, elements, and / or states are included or to be performed in any particular example embodiment, with or without author input or prompting.

[0150] Although some embodiments have been described, these embodiments have been given by way of example and are not intended to limit the scope of the present disclosure. In fact, the apparatus (equipment), method and system described herein can be embodied in a variety of other forms. In addition, without departing from the spirit of the present disclosure, various omissions, replacements and changes can be made to the form of the methods and systems described herein. For example, although the frame is presented in a given arrangement, an alternative embodiment can perform similar functions with different components and / or circuit topologies, and some frames can be deleted, moved, added, subdivided, combined and / or modified. At least one of these frames can be implemented in various different ways. The order of these frames can also be changed. Any appropriate combination of the elements and actions of some of the above-mentioned embodiments can be combined to provide other embodiments. The attached claims and their equivalents are intended to cover these forms or modifications that will fall within the scope and spirit of the application.

Claims

1. A device for communication, comprising: at least one processor; as well as at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to execute as a first device associated with a control plane of a central unit of a donor in an integrated access and backhaul network: determining to control a first downlink transmission of a first interface between a second device associated with a user plane of the central unit of the donor and a node in the integrated access and backhaul network; According to determining that the second device knows the descendant node of the node in the integrated access and backhaul network, sending a first non-UE-associated signaling request for controlling the first downlink transmission of the first interface to the second device, the first non-UE-associated signaling request including information associated with the node in the integrated access and backhaul network; wherein the first non-UE-associated signaling request includes: a request to start the first downlink transmission of the first interface; or a request to stop the first downlink transmission of the first interface; and According to determining that the second device is unaware of descendant nodes of the node in the integrated access and backhaul network, sending the first non-UE associated signaling request to the second device; and Sending a second non-UE associated signaling request to the second device to start downlink transmission of one or more interfaces between the second device and one or more descendant nodes of a node in the integrated access and backhaul network, or to stop downlink transmission of the one or more interfaces between the second device and the one or more descendant nodes of a node in the integrated access and backhaul network, wherein the second non-UE associated signaling request includes information associated with the one or more descendant nodes; The sending of the second non-UE associated signaling request to the second device includes: sending a request including information associated with a first descendant node of the node in the integrated access and backhaul network to the second device to start a third downlink transmission of a third interface between the second device and the first descendant node, or to stop a third downlink transmission of the third interface; and sending a request including information associated with a second descendant node of the node in the integrated access and backhaul network to the second device to start a fourth downlink transmission of a fourth interface between the second device and the second descendant node, or to stop a fourth downlink transmission of the fourth interface, The one or more descendant nodes include the first descendant node and the second descendant node, the second descendant node is a descendant node of the first descendant node, and the one or more interfaces include the third interface and the fourth interface.

2. The device according to claim 1, wherein: The first non-UE-associated signaling request includes at least one of the following: an identification of a distributed unit of said node in said integrated access and backhaul network; an address of the node in the integrated access and backhaul network; an identifier of a cell associated with the node in the integrated access and backhaul network; a routing identifier of a routing path associated with the node in the integrated access and backhaul network; as well as and quality of service parameters for traffic associated with the node in the integrated access and backhaul network.

3. The device as claimed in claim 2, wherein: The first non-UE-associated signaling request further includes at least one of the following: an identification of a distributed unit of a descendant node of a node in the integrated access and backhaul network; The address of the descendant node; an identifier of a cell associated with the descendant node; a routing identifier of a routing path associated with the descendant node; as well as A quality of service parameter of a service associated with the descendant node.

4. The device according to claim 1, wherein: The second non-UE-associated signaling request includes at least one of the following: an identification of a distributed unit of the descendant node; The address of the descendant node; an identifier of a cell associated with the descendant node; a routing identifier of a routing path associated with the descendant node; as well as A quality of service parameter of a service associated with the descendant node.

5. A device for communication, comprising: at least one processor; as well as at least one memory including computer program code, the at least one memory and the computer program code being configured to, with the at least one processor, cause the apparatus to execute as a first device associated with a user plane of a central unit of a donor in an integrated access and backhaul network: In the case where the first device knows descendant nodes of a node in the integrated access and backhaul network, receiving, from a second device associated with a control plane of a central unit of the donor, a first non-UE associated signaling request to control a first downlink transmission of a first interface between the first device and a node in the integrated access and backhaul network, the first non-UE associated signaling request including information associated with the node in the integrated access and backhaul network; as well as controlling, based on the non-UE associated signaling request, a first downlink transmission of the first interface and downlink transmission of one or more interfaces between the first device and one or more descendant nodes of the node; Wherein, the control includes: When the first non-UE-associated signaling request indicates to stop the first downlink transmission of the first interface, stop the first downlink transmission of the first interface; or In a case where the first non-UE associated signaling request indicates starting a first downlink transmission of the first interface, starting a first downlink transmission of the first interface; The at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to further perform: In a case where the first non-UE-associated signaling request indicates stopping the first downlink transmission of the first interface, stopping downlink transmission of the one or more interfaces between the first device and the one or more descendant nodes of the node in the integrated access and backhaul network; or In a case where the first non-UE-associated signaling request indicates initiation of a first downlink transmission of the first interface, initiating downlink transmission of the one or more interfaces between the first device and the one or more descendant nodes of a node in the integrated access and backhaul network; In the case where the first device is unaware of descendant nodes of a node in the integrated access and backhaul network, receiving the first non-UE associated signaling request from the second device; If the first non-UE-associated signaling request indicates to stop the first downlink transmission of the first interface, stop the first downlink transmission of the first interface; or if the first non-UE-associated signaling request indicates to start the first downlink transmission of the first interface, start the first downlink transmission of the first interface; and receiving a second non-UE associated signaling request from the second device to control downlink transmission of one or more interfaces between the first device and one or more descendant nodes of a node in the integrated access and backhaul network, the second non-UE associated signaling request including information associated with the one or more descendant nodes; The receiving of a second non-UE associated signaling request to control downlink transmission of one or more interfaces between the first device and one or more descendant nodes of a node in the integrated access and backhaul network comprises: receiving, from the second device, a request including information associated with a first descendant node of the node in the integrated access and backhaul network to control a third downlink transmission of a third interface between the first device and the first descendant node; If the request of the information associated with the first descendant node indicates to stop the third downlink transmission of the third interface, stop the third downlink transmission of the third interface; or if the request of the information associated with the first descendant node indicates to start the third downlink transmission of the third interface, start the third downlink transmission of the third interface; receiving, from the second device, a request including information associated with a second descendant node of the node in the integrated access and backhaul network to control a fourth downlink transmission of a fourth interface between the first device and the second descendant node; and In a case where the request of the information associated with the second descendant node indicates stopping the fourth downlink transmission of the fourth interface, stopping the fourth downlink transmission of the fourth interface; or in a case where the request of the information associated with the second descendant node indicates starting the fourth downlink transmission of the fourth interface, starting the fourth downlink transmission of the fourth interface, The one or more descendant nodes include the first descendant node and the second descendant node, the second descendant node is a descendant node of the first descendant node, and the one or more interfaces include the third interface and the fourth interface.

6. The device according to claim 5, wherein: The non-UE-associated signaling request includes at least one of the following: an identification of a distributed unit of said node in said integrated access and backhaul network; an address of the node in the integrated access and backhaul network; an identifier of a cell associated with the node in the integrated access and backhaul network; a routing identifier of a routing path associated with the node in the integrated access and backhaul network; as well as and quality of service parameters for traffic associated with the node in the integrated access and backhaul network.

7. The device according to claim 6, wherein: The non-UE-associated signaling request further includes at least one of the following: an identification of a distributed unit of a descendant node of a node in the integrated access and backhaul network; The address of the descendant node; an identifier of a cell associated with the descendant node; a routing identifier of a routing path associated with the descendant node; as well as A quality of service parameter of a service associated with the descendant node.

8. A method for communication, comprising: determining, at a first device associated with a control plane of a central unit of a donor in an integrated access and backhaul network, controlling a first downlink transmission of a first interface between a second device associated with a user plane of the central unit of the donor and a node in the integrated access and backhaul network; According to determining that the second device knows the descendant node of the node in the integrated access and backhaul network, sending a first non-UE associated signaling request to the second device to control the first downlink transmission of the first interface, the first non-UE associated signaling request includes information associated with the node in the integrated access and backhaul network; wherein the first non-UE associated signaling request includes: a request to start the first downlink transmission of the first interface; or a request to stop the first downlink transmission of the first interface; and According to determining that the second device is unaware of descendant nodes of the node in the integrated access and backhaul network, sending the first non-UE associated signaling request to the second device; and sending a second non-UE associated signaling request to the second device to start downlink transmission of one or more interfaces between the second device and one or more descendant nodes of a node in the integrated access and backhaul network, or to stop downlink transmission of the one or more interfaces between the second device and one or more descendant nodes of a node in the integrated access and backhaul network, wherein the second non-UE associated signaling request includes information associated with the one or more descendant nodes; The sending of the second non-UE associated signaling request to the second device includes: sending a request including information associated with a first descendant node of the node in the integrated access and backhaul network to the second device to start a third downlink transmission of a third interface between the second device and the first descendant node, or to stop a third downlink transmission of the third interface; and sending a request including information associated with a second descendant node of the node in the integrated access and backhaul network to the second device to start a fourth downlink transmission of a fourth interface between the second device and the second descendant node, or to stop a fourth downlink transmission of the fourth interface, The one or more descendant nodes include the first descendant node and the second descendant node, the second descendant node is a descendant node of the first descendant node, and the one or more interfaces include the third interface and the fourth interface.

9. The method of claim 8, wherein: The first non-UE-associated signaling request includes at least one of the following: an identification of a distributed unit of said node in said integrated access and backhaul network; an address of the node in the integrated access and backhaul network; an identifier of a cell associated with the node in the integrated access and backhaul network; a routing identifier of a routing path associated with the node in the integrated access and backhaul network; as well as Quality of service parameters for traffic associated with the node in the integrated access and backhaul network.

10. The method of claim 9, wherein: The first non-UE-associated signaling request further includes at least one of the following: an identification of a distributed unit of a descendant node of a node in the integrated access and backhaul network; The address of the descendant node; an identifier of a cell associated with the descendant node; a routing identifier of a routing path associated with the descendant node; as well as A quality of service parameter of a service associated with the descendant node.

11. The method of claim 8, wherein: The second non-UE-associated signaling request includes at least one of the following: an identification of a distributed unit of the descendant node; The address of the descendant node; an identifier of a cell associated with the descendant node; a routing identifier of a routing path associated with the descendant node; as well as A quality of service parameter of a service associated with the descendant node.

12. A method for communication, comprising: In case a first device associated with a user plane of a central unit of a donor in an integrated access and backhaul network knows descendant nodes of a node in the integrated access and backhaul network, receiving, at the first device and from a second device associated with a control plane of a central unit of the donor, a first non-UE associated signaling request to control a first downlink transmission of a first interface between the first device and a node in the integrated access and backhaul network, the first non-UE associated signaling request including information associated with the node in the integrated access and backhaul network; as well as controlling, based on the non-UE associated signaling request, a first downlink transmission of the first interface and downlink transmission of one or more interfaces between the first device and one or more descendant nodes of the node in the integrated access and backhaul network; Wherein, the control includes: When the first non-UE-associated signaling request indicates to stop the first downlink transmission of the first interface, stop the first downlink transmission of the first interface; or In a case where the first non-UE associated signaling request indicates starting a first downlink transmission of the first interface, starting a first downlink transmission of the first interface; The method further comprises: If the first non-UE-associated signaling request indicates to stop the first downlink transmission of the first interface, stop the downlink transmission of one or more interfaces between the first device and one or more descendant nodes of a node in the integrated access and backhaul network; or In a case where the first non-UE-associated signaling request indicates initiation of a first downlink transmission of the first interface, initiating downlink transmission of the one or more interfaces between the first device and the one or more descendant nodes of a node in the integrated access and backhaul network; In the case where the first device is unaware of descendant nodes of a node in the integrated access and backhaul network, receiving, at the first device, the first non-UE associated signaling request from the second device; If the first non-UE-associated signaling request indicates to stop the first downlink transmission of the first interface, stop the first downlink transmission of the first interface; or if the first non-UE-associated signaling request indicates to start the first downlink transmission of the first interface, start the first downlink transmission of the first interface; and receiving a second non-UE associated signaling request from the second device to control downlink transmission of one or more interfaces between the first device and one or more descendant nodes of a node in the integrated access and backhaul network, the second non-UE associated signaling request including information associated with the one or more descendant nodes; The receiving of a second non-UE associated signaling request to control downlink transmission of one or more interfaces between the first device and one or more descendant nodes of a node in the integrated access and backhaul network includes: receiving, from the second device, a request including information associated with a first descendant node of the node in the integrated access and backhaul network to control a third downlink transmission of a third interface between the first device and the first descendant node; In a case where the request of the information associated with the first descendant node indicates stopping the third downlink transmission of the third interface, stopping the third downlink transmission of the third interface; or in a case where the request of the information associated with the first descendant node indicates starting the third downlink transmission of the third interface, starting the third downlink transmission of the third interface; receiving, from the second device, a request including information associated with a second descendant node of the node in the integrated access and backhaul network to control a fourth downlink transmission of a fourth interface between the second device and the second descendant node; and In a case where the request of the information associated with the second descendant node indicates stopping the fourth downlink transmission of the fourth interface, stopping the fourth downlink transmission of the fourth interface; or in a case where the request of the information associated with the second descendant node indicates starting the fourth downlink transmission of the fourth interface, starting the fourth downlink transmission of the fourth interface, The one or more descendant nodes include the first descendant node and the second descendant node, the second descendant node is a descendant node of the first descendant node, and the one or more interfaces include the third interface and the fourth interface.

13. The method of claim 12, wherein: The non-UE-associated signaling request includes at least one of the following: an identification of a distributed unit of said node in said integrated access and backhaul network; an address of the node in the integrated access and backhaul network; an identifier of a cell associated with the node in the integrated access and backhaul network; a routing identifier of a routing path associated with the node in the integrated access and backhaul network; as well as Quality of service parameters for traffic associated with the node in the integrated access and backhaul network.

14. The method of claim 13, wherein: The non-UE-associated signaling request further includes at least one of the following: an identification of a distributed unit of a descendant node of a node in the integrated access and backhaul network; The address of the descendant node; an identifier of a cell associated with the descendant node; a routing identifier of a routing path associated with the descendant node; as well as A quality of service parameter of a service associated with the descendant node.

15. A computer readable medium comprising instructions stored thereon for causing a first device associated with a control plane of a central unit of a donor in an integrated access and backhaul network to execute: determining to control a first downlink transmission of a first interface between a second device associated with a user plane of a central unit of the donor and a node in the integrated access and backhaul network; as well as According to determining that the second device knows a descendant node of the node in the integrated access and backhaul network, sending a first non-UE associated signaling request for controlling a first downlink transmission of the first interface to the second device, wherein the first non-UE associated signaling request includes information associated with the node in the integrated access and backhaul network; wherein The first non-UE associated signaling request includes: a request to start a first downlink transmission of the first interface; or a request to stop a first downlink transmission of the first interface; The instruction causes the first device to further execute: According to determining that the second device is unaware of descendant nodes of the node in the integrated access and backhaul network, sending the first non-UE associated signaling request to the second device; and Sending a second non-UE associated signaling request to the second device to start downlink transmission of one or more interfaces between the second device and one or more descendant nodes of a node in the integrated access and backhaul network, or to stop downlink transmission of the one or more interfaces between the second device and the one or more descendant nodes of a node in the integrated access and backhaul network, wherein the second non-UE associated signaling request includes information associated with the descendant node; The sending of the second non-UE associated signaling request to the second device includes: sending a request including information associated with a first descendant node of the node in the integrated access and backhaul network to the second device to start a third downlink transmission of a third interface between the second device and the first descendant node, or to stop a third downlink transmission of the third interface; and sending a request including information associated with a second descendant node of the node in the integrated access and backhaul network to the second device to start a fourth downlink transmission of a fourth interface between the second device and the second descendant node, or to stop a fourth downlink transmission of the fourth interface, The one or more descendant nodes include the first descendant node and the second descendant node, the second descendant node is a descendant node of the first descendant node, and the one or more interfaces include the third interface and the fourth interface.

16. The computer-readable medium of claim 15, wherein: The first non-UE-associated signaling request includes at least one of the following: an identification of a distributed unit of said node in said integrated access and backhaul network; an address of the node in the integrated access and backhaul network; an identifier of a cell associated with the node in the integrated access and backhaul network; a routing identifier of a routing path associated with the node in the integrated access and backhaul network; as well as and quality of service parameters for traffic associated with the node in the integrated access and backhaul network.

17. The computer-readable medium of claim 16, wherein: The first non-UE-associated signaling request further includes at least one of the following: an identification of a distributed unit of a descendant node of a node in the integrated access and backhaul network; The address of the descendant node; an identifier of a cell associated with the descendant node; a routing identifier of a routing path associated with the descendant node; as well as A quality of service parameter of a service associated with the descendant node.

18. The computer-readable medium of claim 15, wherein the second non-UE-associated signaling request comprises at least one of: an identification of a distributed unit of the descendant node; The address of the descendant node; an identifier of a cell associated with the descendant node; a routing identifier of a routing path associated with the descendant node; and A quality of service parameter of a service associated with the descendant node.

19. A computer readable medium comprising instructions stored thereon for causing a first device associated with a user plane of a central unit of a donor in an integrated access and backhaul network to: In the case where the first device knows descendant nodes of a node in the integrated access and backhaul network, receiving, from a second device associated with a control plane of a central unit of the donor, a first non-UE associated signaling request to control a first downlink transmission of a first interface between the first device and a node in the integrated access and backhaul network, the first non-UE associated signaling request including information associated with the node in the integrated access and backhaul network; as well as controlling, based on the first non-UE associated signaling request, a first downlink transmission of the first interface and downlink transmission of one or more interfaces between the first device and one or more descendant nodes of the node in the integrated access and backhaul network; in, The control includes: When the first non-UE-associated signaling request indicates to stop the first downlink transmission of the first interface, stop the first downlink transmission of the first interface; or In a case where the first non-UE associated signaling request indicates starting a first downlink transmission of the first interface, starting a first downlink transmission of the first interface; The instructions cause the first device to further execute: In a case where the first non-UE-associated signaling request indicates to stop the first downlink transmission of the first interface, stop the downlink transmission of the one or more interfaces between the first device and the one or more descendant nodes of the node in the integrated access and backhaul network; or In a case where the first non-UE-associated signaling request indicates initiation of a first downlink transmission of the first interface, initiating downlink transmission of the one or more interfaces between the first device and the one or more descendant nodes of a node in the integrated access and backhaul network; In the case where the first device is unaware of descendant nodes of a node in the integrated access and backhaul network, receiving the first non-UE associated signaling request from the second device; If the first non-UE-associated signaling request indicates to stop the first downlink transmission of the first interface, stop the first downlink transmission of the first interface; or if the first non-UE-associated signaling request indicates to start the first downlink transmission of the first interface, start the first downlink transmission of the first interface; and receiving a second non-UE associated signaling request from the second device to control downlink transmission of one or more interfaces between the first device and one or more descendant nodes of a node in the integrated access and backhaul network, the second non-UE associated signaling request including information associated with the descendant node; The receiving of a second non-UE associated signaling request to control downlink transmission of the one or more interfaces between the first device and the one or more descendant nodes of the node in the integrated access and backhaul network includes: receiving a request including information associated with a first descendant node of the node in the integrated access and backhaul network to control a third downlink transmission of a third interface between the first device and the first descendant node; If the request of the information associated with the first descendant node indicates to stop the third downlink transmission of the third interface, stop the third downlink transmission of the third interface; or if the request of the information associated with the first descendant node indicates to start the third downlink transmission of the third interface, start the third downlink transmission of the third interface; receiving a request including information associated with a second descendant node of the node in the integrated access and backhaul network to control a fourth downlink transmission of a fourth interface between the second device and the second descendant node; and In a case where the request of the information associated with the second descendant node indicates stopping the fourth downlink transmission of the fourth interface, stopping the fourth downlink transmission of the fourth interface; or in a case where the request of the information associated with the second descendant node indicates starting the fourth downlink transmission of the fourth interface, starting the fourth downlink transmission of the fourth interface, The one or more descendant nodes include the first descendant node and the second descendant node, the second descendant node is a descendant node of the first descendant node, and the one or more interfaces include the third interface and the fourth interface.

20. The computer readable medium of claim 19, wherein: The non-UE-associated signaling request includes at least one of the following: an identification of a distributed unit of said node in said integrated access and backhaul network; an address of the node in the integrated access and backhaul network; an identifier of a cell associated with the node in the integrated access and backhaul network; a routing identifier of a routing path associated with the node in the integrated access and backhaul network; as well as and quality of service parameters for traffic associated with the node in the integrated access and backhaul network.

21. The computer readable medium of claim 20, wherein: The non-UE-associated signaling request further includes at least one of the following: an identification of a distributed unit of a descendant node of a node in the integrated access and backhaul network; The address of the descendant node; an identifier of a cell associated with the descendant node; a routing identifier of a routing path associated with the descendant node; as well as A quality of service parameter of a service associated with the descendant node.

Images