WO2023158361A1

WO2023158361A1 - First node, network node, radio network node and methods performed thereby for handling configuration of the first node

Info

Publication number: WO2023158361A1
Application number: PCT/SE2023/050142
Authority: WO
Inventors: Gautham NAYAK SEETANADI; Ritesh SHREEVASTAV; Filip BARAC; Marco BELLESCHI; Antonino ORSINO
Original assignee: Telefonaktiebolaget LM Ericsson AB
Current assignee: Telefonaktiebolaget LM Ericsson AB
Priority date: 2022-02-17
Filing date: 2023-02-17
Publication date: 2023-08-24
Anticipated expiration: 2024-08-17

Abstract

A method performed by a first node (130). The first node (130) receives (801), from a network node (101, 102, 140), one or more first indications indicating one or more configurations to be applied upon fulfilment of one or more first criteria. The first node (130) is provided a wired connection to a core network by the first network node (101) via at least a wireless connection, and is capable to be provided a wired connection to the core network by a second network node (102) via at least another wireless connection. The first node (130) stores (804) the configurations and applies (806) a respective configuration upon fulfilment of criteria. The receiving (801) comprises receiving a plurality of configurations, the storing (804) comprises storing the plurality of configurations and the applying (806) comprises applying the respective configuration.

Description

FIRST NODE, NETWORK NODE, RADIO NETWORK NODE AND METHODS PERFORMED THEREBY FOR HANDLING CONFIGURATION OF THE FIRST NODE

TECHNICAL FIELD

The present disclosure relates generally to a first node and methods performed thereby for handling configuration of the first node. The present disclosure further relates generally to a network node and methods performed thereby, for handling the configuration of the first node. The present disclosure further relates generally to a radio network node and methods performed thereby, for handling the configuration of the first node.

BACKGROUND

Nodes within a communications network may be network nodes, such as radio network nodes, e.g., Transmission Points (TP). The communications network may cover a geographical area which may be divided into cell areas, each cell area being served by a network node such as a Base Station (BS), e.g. a Radio Base Station (RBS), which sometimes may be referred to as e.g., gNB, evolved Node B (“eNB”), “eNodeB”, “NodeB”, “B node”, or Base Transceiver Station (BTS), depending on the technology and terminology used. The base stations may be of different classes such as e.g. Wide Area Base Stations, Medium Range Base Stations, Local Area Base Stations and Home Base Stations, based on transmission power and thereby also cell size. A cell is the geographical area where radio coverage is provided by the base station at a base station site. One base station, situated on the base station site, may serve one or several cells. Further, each base station may support one or several communication technologies. The communications network may also be a non- cellular system, comprising network nodes which may serve receiving nodes, such as wireless devices, with serving beams. In 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE), base stations, which may be referred to as eNodeBs or even eNBs, may be directly connected to one or more core networks. In the context of this disclosure, the expression Downlink (DL) may be used for the transmission path from the base station to a wireless device. The so-called 5G system, from a radio perspective started to be standardized in 3GPP, and the so-called New Radio (NR) is the name for the radio interface. NR architecture is being discussed in 3GPP. In the current concept, gNB denotes NR BS, where one NR BS may correspond to one or more transmission/reception points. The expression Uplink (UL) may be used for the transmission path in the opposite direction i.e., from the wireless device to the base station.

Integrated Access and Backhaul (IAB) Overview Fifth Generation (5G) networks are being designed and deployed considering a dense deployment of small cells in order to simultaneously serve more User Equipment (UEs) with higher throughput and lower delay. However, building from scratch a completely new infrastructure is costly and takes time. Deploying a wireless backhaul is then envisioned to be an economically and technically viable approach to enable flexible and dense network.

This solution was standardized in 3GPP release 16, under the term Integrated Access and Backhaul (IAB), to support wireless relaying in New Generation Radio Access Network (NG-RAN) and has continued in release 17.

IAB Architecture

IAB may be understood to be based on the centralized unit (CU)- distributed unit (DU) split that was standardized in release 15. The CU may be understood to be in charge of the radio resource control (RRC) and the packet data convergence (PCDP) protocol, whereas the distributed unit (DU) may be understood to be in charge of the radio link control (RLC) and medium access control (MAC). The F1 interface may be understood to connect the CU and the DU. The CU-DU split may be understood to facilitate separate physical CU and DU, while also allowing a single CU to be connected to multiple DUs.

Figure 1 is a schematic diagram illustrating a basic architecture of IAB. The figure consists of a single IAB donor 1 connected to the core network (CN) 2. The IAB donor 1 in the example depicted in Figure 1 serves three direct IAB child nodes 3 through two collocated DUs 4 at the donor for wireless backhauling. The center IAB node 3 in turn serves two IAB nodes 5 through wireless backhaul. All IAB nodes in Figure 1 backhaul traffic both related to UEs 6 connected to it, and other backhaul traffic from downstream IAB nodes. The IAB donor 1 has also a collocated CU-Control Plane (CP) 7, a CU-User Plane (UP) 8 and other functions 9.

The main components of IAB architecture

The main components of IAB architecture may be understood to be:

1) IAB Node, which may be understood as a node that may allow wireless access to the UEs while also backhauling the traffic to other nodes. The IAB node may consist of a DU that may provide access to connected UEs. The node may also consist of a mobile termination (MT) that may connect to other IAB nodes or donors in the uplink direction for backhaul.

2) IAB Donor, which may be understood as a node that may provide UEs with an interface to the core network and wireless functionality to other lAB-nodes to backhaul their traffic to the core network.

The defining feature of IAB may be understood to be the use of wireless spectrum for both access of UEs, and backhauling of data through IAB donors. Thus, there may be understood to be a need for a clear separation of access and backhaul resources to avoid interference between them. This separation of access and backhaul resources cannot be handled during network planning due to the dynamic nature of IAB.

In release 16, IAB was standardized with basic support for multi-hop multi-path backhaul for directed acyclic graph (DAG) topology, no mesh-based topology was supported. Release 16 may also support Quality of Service (QoS) prioritization of backhaul traffic and flexible resource usage between access and backhaul. Current discussions in release 17 are on topology enhancements for IAB with partial migration of IAB nodes for Radio Link Failure (RLF) recovery and load balancing.

Further information regarding the already standardized IAB work may be found in, for example, Madapatha, Charitha et al. “On Integrated Access and Backhaul Networks: Current Status and Potentials.” IEEE Open Journal of the Communications Society 1 (2020): 1374- 1389, 3GPP TS 38.300, v.16.8.0. Section 4.7, 3GPP TR 38.874, v.16.0.0 Study on IAB.

In release 18, it is expected that the different Radio Access Network (RAN) groups will work towards enhancing functionality of IAB through focus on mobile-IAB/vehicle mounted relays (VMR) providing 5G coverage enhancement to onboard and surrounding UEs, and smart repeaters that may build on LTE-repeaters.

The initial use cases for mobile-IAB/VMR are expected to be based on 3GPP TR 22.839, v.18.1.0.

One of the main use cases of mobile IAB cell may be to serve the UEs which may be residing in the vehicle with the vehicle mounted relay. Other relevant use cases for mobile lABs may involve a mobile/nomadic IAB network node mounted on a vehicle that may provide extended coverage. This may involve scenarios where additional coverage may be required during special events such as concerts, during disasters, etc.. The nomadic IAB node may provide access to surrounding UEs while the backhaul traffic from the nomadic IAB node may then be transmitted wirelessly either with the help of IAB donors or Nonterrestrial networks (NTN). A nomadic IAB node may also reduce or even eliminate signal strength loss due to vehicle penetration for UEs that may be present in the vehicles.

Advantages of Mobile IAB may be understood to be reducing/eliminating the vehicle penetration loss, specially at high frequency, and/or reducing/eliminating group handover.

F1 interface

The F1 interface may be understood to connect the CU to the DU in the split architecture, which may be also applicable to the IAB architecture. The F1 interface may connect the CU from an IAB donor to an IAB DU in the child IAB nodes. The F1 interface may also support control and user plane separation through F1-C and F1-U respectively. This interface may hold even during IAB mobility, where an IAB node may move and connect to parent/donor IAB nodes. In such a scenario, the DU present in the mobile IAB node may connect to the CU present in the IAB donor.

The IAB-DU may initiate an F1 setup with the IAB-CU with which it may have a Transport Network Layer (TNL) connection, and the initial F1 setup is shown in Figure 2, which is described below, from section 8.5 of 38.401 , v.16.8.0. Once the F1 setup is completed, the IAB donor CU may send a GNB-CU CONFIGURATION UPDATE to optionally indicate the DU cells to be activated.

IAB Inter-donor topology redundancy procedure

This procedure may be used for configuring inter-donor topology redundancy between two different lAB-donor-CUs for the boundary IAB node and descendant node(s). Figure 8.X.1-1 , reproduced herein as Figure 2, shows the procedure for IAB inter-donor topology redundancy. At step 1, the NR-DC establishment procedure may be performed for the IAB- MT 21 of the boundary IAB node 22. During this procedure, the IP address(es) for the boundary/descendant IAB node 23 may be requested from IAB-donor2-CU 24. At step 2, the F1 UE Context Setup/Modification Procedures may be performed between the IAB-donor1-CU 25 and the IAB-DU 26, 27 of the boundary/descendant IAB node 22, 23. During those procedures, the UE contexts for the offloaded traffic may be configured, and the IAB-DU part 26, 27 may select the proper IP addresses for the offloaded traffic on the granularity of General Packet Radio Service Tunnelling Protocol User Plane (GTP-U) tunnel/TNL association. At step 3, the IAB-donor1-CU 25 may initiate IAB TRANSPORT MIGRATION MANAGEMENT REQUEST message to the IAB-donor2-CU 24 in order to provide the context of offloaded traffic. At step 4, the IAB-donor2-CU 24 may configure the routing and bearer mapping under its topology. At step 5, the IAB-donor2-CU 24 may respond with an IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE message to the IAB-donor1-CU 25 to provide the mapping information for the offloaded traffic. It may be noted that Step 2 may be performed after Step 3/4/5. At step 6, the IAB-donor1-25 may perform the configuration for bearer mapping, routing and header rewriting.

IAB inter-CU topology adaptation procedure

During the inter-CU topology adaptation for a single-connected lAB-node, the IAB-MT may switch connection from an old parent node to a new parent node, where the old and the new parent nodes are served by different lAB-donor-CUs. Without loss of generality, the old parent node may be referred to as source parent node, and the new parent node may be referred to as target parent node.

Figure 3 is a signalling diagram showing an example of the topology adaptation procedure where the migrating IAB-MT 31 is migrated from one lAB-donor-CU 32 to another lAB-donor-CU 33. In case the IAB-DU of the migrating lAB-node 31 retains its F1 connection with the first lAB-donor-CU 32, that is, the source lAB-donor-CU 32, after the migrating IAB- MT 31 connects to the second lAB-donor-CU 33, that is, the target lAB-donor-CU 33, this procedure may render the migrating lAB-node 31 as a boundary lAB-node. As depicted in Figure 3, starting on panel a), which shows Phase 1 of the procedure, the IAB-MT migration, a UE 34 may exchange downlink user data and uplink user data with the Next Generation Core (NGC) 35 through the migrating IAB node 31 and the source path 36. At Step 1, the source lAB-donor-CU 32 sends a handover request to the target lAB-donor-CU 33. At Step 2, the target lAB-donor-CU 33 sends a UE context setup request to the target parent lAB-donor 37 in the target path 38. At Step 3, the target parent lAB-donor 37 sends a UE context setup response to the target lAB-donor-CU 33. At Step 4, the target lAB-donor-CU 33 sends a handover request acknowledge, Radio Resource Request Reconfiguration (RRC), to the source lAB-donor CU 32. At Step 5, the source lAB-donor CU 32 sends a UE context modification request, as an RRC reconfiguration, to the source parent lAB-node 39. At Step 6, the source parent lAB-node 39 then sends an RRC reconfiguration to the migrating IAB node 31. At Step 7, the source parent lAB-node 39 sends a UE context modification response to the source lAB-donor-CU 32. At Step 8, the target parent lAB-donor 37 starts a random access procedure with the migrating IAB node 31 and at Step 9, the migrating IAB node 31 sends an RRCReconfigurationComplete to the target parent lAB-donor 37. At Step 10, the target parent lAB-donor 37 sends an Uplink (UL) RRC message transfer, with an RRCReconfigurationComplete message, to the target lAB-donor-CU 33. At Step 11, the target lAB-donor-CU 33 may then perform a path switch procedure with the NGC 35. At Step 12, the target lAB-donor-CU 33 sends a UE context release to the source lAB-donor CU 32. At Step 13, the Backhaul Adaptation Protocol (BAP) route along the source path 36 between the migrating lAB-node 31 and the source lAB-donor-DU 40 via source parent lAB-node 39 is released. Continuing on panel b), which shows the Phase 2 of the procedure, the F1 transport migration, at Step 14, a configuration is performed of Backhaul (BH) RLC channel, BAP route and mapping rules along the target path 38 between the migrating lAB-node 31 and the target lAB-donor-DU 41 the via target parent lAB-node 37. At Step 15, a redirection is performed of the migrating lAB-node-DU’s 31 F1-C to the target path 38 and reporting of new F1-U TNL information to the source lAB-donor-CU 32 may be performed. At Step 16, the source lAB- donor-CU 32 may send an IAB transport migration management request to the target lAB- donor-CU 33. At Step 17, a configuration or modification of BH RLC channel, BAP route and mapping rules may be performed along the target path 38 between the migrating lAB-node 31 and the target lAB-donor-DU 41 via the target parent lAB-node 37. At Step 18, the target lAB- donor-CU 33 may send an IAB transport migration management response to the source IAB- donor-CU 32. At Step 19, a redirection of migrating lAB-node-DU’s F1-LI to the target path and update of the BAP mapping configuration may be performed. At Step 20, steps 16-19 may be repeated as needed. After, downlink user data and uplink user data may be exchanged between the UE 34 and the NGC 35 via the migrating IAB node 31 , the target path 38 and the target lAB-donor-CU 33.

Mobile IAB

It may be considered that in most use cases, a mobile IAB may be expected to be mounted on public transport vehicles and to move to a large extent in a pre-determined route. Figure 4 is a schematic diagram showing a mobile lAB-Node 42 handover which involves Intra-Donor, Inter-Donor, same CU, and Inter CUs. Particularly, Figure 4 depicts one such mobile IAB 42 mounted on a bus 43 travelling on a route 44 that is covered by 4 different parent IAB nodes, IAB parent 1 45, 2 46, 3 47, 4 48. The parent nodes backhaul their traffic through 2 donor nodes, donor IAB X 49, Y 50.

An IAB node 42 may have a DU that may provide access to UEs around it and a MT that may provide a backhaul connection of the IAB node to its parent(s) and the rest of the network. The parent IAB nodes 45, 46, 47, 48 may consist of DUs that may provide access to UEs and the mobile IAB 42 present in their coverage. They may also consist of MTs that may backhaul its traffic together with traffic from the mobile IAB node 42. Finally, the two donor nodes 49, 50 may consist of DU that may provide access and CU that may be understood to be connected to the core network. The CUs in both donor nodes 49, 50 may maintain an F1 51 connection to parent nodes under it.

The mobile IAB node 42 may maintain an F1 connection to the donor, one donor at a time. In Figure 4, the mobile IAB 41 connects to the following nodes in the different positions as described below:

1) Position A: BH 52 through parent node 1 45, F1 51 connection to donor node X 49;

2) Position B: BH 53 through parent node 2 46, F1 54 connection to donor node X 49;

3) Position C: BH 55 through parent node 3 47, F1 56 connection to donor node Y 50;

4) Position D: BH 57 through parent node 4 48, F1 58 connection to donor node Y 50.

The mobile IAB 42 may be understood to need to change the F1 connection from donor X 49 to donor Y 50 when moving from position B to C, thus requiring an F1 handover and setup of backhaul RLC channels.

IAB nodes, including mobile IAB nodes, may be connected to an IAB donor and subsequently to the core network in a standalone or non-standalone method as described, according to TS 38.401, v.16.8.0. IAB-node Integration Procedure

Standalone (SA) IAB integration

A high-level flow chart for SA-based IAB integration is shown in the Figure 8.12.1-1 , which is reproduced herein as Figure 5, and described next. At Phase 1 , the IAB-MT setup may be performed. In this phase, the IAB-MT of the new IAB-node, e.g., IAB-node 2 59 in Figure 5, may connect to the network in the same way as a UE, by performing RRC connection setup procedure with the lAB-donor-CU 60, authentication with the core network 61 , IAB-node 2 59-related context management, IAB-node 2’s 59 access traffic-related radio bearer configuration at the RAN side, Signalling Radio Bearers (SRBs) and optionally Data Radio Bearers (DRBs), and, optionally, Operations, Administration and Maintenance (OAM) connectivity establishment by using the lAB-MT’s Protocol Data Unit (PDU) session. The IAB- node 59 may select the parent node for access based on an over-the-air indication from potential parent node IAB-DU, transmitted in System Information Block 1 (SIB1). To indicate its IAB capability, the IAB-MT may include the IAB-node indication in RRCSetupComplete message, to assist the lAB-donor to select an Access and Mobility Management Function (AMF) supporting IAB. It may be noted that the signalling flow for UE initial access procedure as shown in Figure 8.1-1/Figure 8.9.1-1 from TS 38.401 , v.16.8.0 may be used for the setup of the IAB-MT. In Phase 2-1 , BH RLC channel establishment may be performed. During the bootstrapping procedure, one default BH RLC channel for non-User Plane (UP) traffic, e.g., carrying F1-C traffic/non-F1 traffic to and from the IAB-node 2 59 in the integration phase, may be established. This may require the setup of a new BH RLC channel or modification of an existing BH RLC channel between IAB-node 1 62 and lAB-donor-DU 63. The lAB-donor-CU 60 may establish additional, non-default, BH RLC channels. This phase may also include configuring the BAP Address of the IAB-node 2 59 and default BAP Routing Identifier (ID) for the upstream direction. It may be noted that if the OAM connectivity is supported via backhaul IP layer by implementation, one or more BH RLC channels used for OAM traffic may also be established. In Phase 2-2, a routing update may be performed. In this phase, the BAP sublayer may be updated to support routing between the new IAB-node 2 59 and the lAB- donor-DU 63. For the downstream direction, the lAB-donor-CU 60 may initiate F1AP procedure to configure the lAB-donor-DU 63 with the mapping from Internet Protocol (IP) header field(s) to the BAP Routing ID related to IAB-node 2 59. The routing tables may be updated on all ancestor lAB-nodes, e.g., IAB-node 1 62 in Figure 5, and on the lAB-donor-DU 63, with routing entries for the new BAP Routing ID(s). This phase may also include the IP address allocation procedure for IAB-node 2 59. IAB-node 2 59 may request one or more IP addresses from the lAB-donor-CU 60 via RRC. The lAB-donor-CU 60 may send the IP address(es) to the lAB-node 2 59 via RRC. The lAB-donor-CU 60 may obtain the IP address(es) from the lAB-donor-DU 63 via F1- AP or by other means, e.g., OAM, Dynamic Host Configuration Protocol (DHCP). IP address allocation procedure may occur at any time after RRC connection has been established. In Phase 3, the IAB-DU part setup may be performed. In this phase, the IAB-DU of lAB-node 2 59 may be configured via OAM. The IAB- DU of lAB-node 2 59 may initiate the TNL establishment, and F1 setup, as defined in clause 8.5 of TS 38.401 , v.16.8.0, with the lAB-donor-CU 60 using the allocated IP address(es). The lAB-donor-CU 60 may discover collocation of IAB-MT and IAB-DU from the lAB-node’s BAP Address included in the F1 SETUP REQUEST message. After the F1 may be set up, the lAB- node 2 59 may start serving the UEs. It may be noted that the IAB-DU may discover the IAB- donor-CU’s IP address in the same manner as a non-IAB gNB-DU.

The sections below show the procedure for BAP layer mapping and configuration. The text is from TS 38.473, v.16.8.0.

BAP Mapping Configuration

General

The BAP Mapping Configuration Procedure may be initiated by the gNB-CU in order to configure the DL/UL routing information and/or traffic mapping information that may be needed for the gNB-DU. The procedure may use non-UE associated signalling.

It may be noted that implementation may need to ensure the avoidance of potential race conditions, that is, it may need to ensure that conflicting traffic mapping configurations are not concurrently performed using the non-U E-associated BAP Mapping Configuration procedure and the U E-associated UE Context Management procedures.

Figure 6 is a schematic diagram depicting a signalling diagram of a BAP Mapping Configuration procedure: Successful Operation, as depicted in Figure 8.10.1.2-1 of TS 38.473, v.16.8.0.

The gNB-CU 64 may initiate the procedure by sending a BAP MAPPING CONFIGURATION message to the gNB-DU 65. The gNB-DU 63 may reply to the gNB-CU 64 with a BAP MAPPING CONFIGURATION ACKNOWLEDGE.

If a BH Routing Information Added List Information Element (IE) is included in the BAP MAPPING CONFIGURATION message, the gNB-DU 65 may be required to, if supported, store the BH routing information from this IE and use it for DL/UL traffic forwarding as specified in TS 38.340, v.16.5.0 [30], If BH Routing Information Added List IE contains information for an existing BAP Routing ID, the gNB-DU 65 may be required to, if supported, replace the previously stored routing information for this BAP Routing ID with the corresponding information in the BH Routing Information Added List IE. If BH Routing Information Removed List IE is included in the BAP MAPPING CONFIGURATION message, the gNB-DU 65 may be required to, if supported, remove the BH routing information according to such IE.

If the Traffic Mapping Information IE is included in the BAP MAPPING CONFIGURATION message, the gNB-DU 65 may be required to, if supported, process the Traffic Mapping Information IE as follows. If the IP to Iayer2 Traffic Mapping Info IE is included, the gNB-DU 65 may be required to store the mapping information contained in the IP to Iayer2 Mapping Info To Add IE, if present, and remove the previously stored mapping information as indicated by the IP to Iayer2 Mapping Info To Remove IE, if present. The gNB- DU 65 may be required to use the mapping information stored for the mapping of IP traffic to layer 2, as specified in TS 38.340, v.16.5.0 [30], If the BAP layer BH RLC channel Mapping Info IE is included, the gNB-DU 65 may be required to store the mapping information contained in the BAP layer BH RLC channel Mapping Info To Add IE, if present, and remove the previously stored mapping information as indicated by the BAP layer BH RLC channel Mapping Info To Remove IE, if present. The gNB-DU 65 may be required to use the mapping information stored when forwarding traffic on BAP sublayer, as specified in TS 38.340, v.16.5.0 [30],

The sections below show the signalling related to setting up of backhaul RLC channel from TS 38.473, v.16.8.0, section 9.3.1.98.

BAP layer BH RLC channel mapping Information List

This IE may include the information used by the IAB-DU to perform the BH RLC channel mapping when forwarding traffic on BAP sublayer.

When this IE is included in the UE-associated F1AP signalling for setting up or modifying a BH RLC channel, it may contain either the Prior-Hop BAP Address IE and the Ingress BH RLC CH ID IE to configure a mapping in downlink direction, or the Next-Hop BAP address IE and the Egress BH RLC CH ID IE to configure a mapping in uplink direction. This IE may indicate the BH RLC channel served by the collocated IAB-MT.

When this IE is included in the non-U E-associated F1AP signalling, it may need to contain the Prior-Hop BAP Address IE, the Ingress BH RLC CH ID IE, the Next-Hop BAP address IE and the Egress BH RLC CH ID IE.

Existing methods for migrating nodes in an IAB deployment may lead to long service interruption and, potentially, connection loss.

SUMMARY

As part of the development of embodiments herein, one or more challenges with the existing technology will first be identified and discussed. In mobile IAB, an IAB node may be mounted onboard a vehicle. When the vehicle moves to a different geographical area, the backhaul traffic may need to be routed over a different parent node. This parent node may either be served by the same donor CU or a different donor CU. The mobile IAB may need to be provided with a new configuration, including, e.g., BAP address and BAP routing ID configuration, backhaul mapping configuration, each time the parent changes. If the reconfiguration is to be executed according to the current specifications, long service interruption and, potentially, connection loss, may occur.

It is therefore an object of embodiments herein to improve the handling of configuration of a first node operating in a communications network, the first node being served by a first network node.

According to a first aspect of embodiments herein, the object is achieved by a method, performed by a first node. The first node operates in a communications network. The first node is served by a first network node. The method is for handling configuration of the first node. The first node receives, from a network node, one or more first indications. The one or more first indications respectively indicate one or more first configurations to be applied by the first node upon fulfilment of one or more respective first criteria. The first node is provided a wired connection to a core network node of the communications network by the first network node via at least a wireless connection. The first node is capable to be provided a respective wired connection to the core network node of the communications network by a respective second network node via at least another respective wireless connection. The first node stores the one or more first configurations at the first node. The first node then applies, out of the stored one or more first configurations, a respective first configuration upon fulfilment of the one or more respective first criteria. The receiving comprises receiving a plurality of first configurations comprising the respective first configuration. The storing comprises storing the plurality of first configurations and the applying comprises applying the respective first configuration out of the stored plurality of first configurations. Each of the one or more first configurations is a BAP configuration.

According to a second aspect of embodiments herein, the object is achieved by a method, performed by the network node. The network node operates in the communications network. The method is for handling the configuration of the first node. The network node sends the one or more first indications to at least one of: i) the first node served by the first network node and ii) at least one first radio network node. The first node is served by the first network node through the at least one first radio network node. The at least one first radio network node has respective wireless connections with the first node and the first network node. The one or more first indications indicate one or more first configurations to be applied by the first node upon fulfilment of the one or more respective first criteria. The first node is provided the wired connection to a core network node of the communications network by the first network node via at least the wireless connection. The first node is capable to be provided the respective wired connection to the core network node of the communications network by the respective second network node via the at least another respective wireless connection. The sending comprises sending the plurality of first configurations comprising the respective first configuration to be applied by the first node upon fulfilment of the respective one or more first criteria. Each of the one or more first configurations is a BAP configuration.

According to a third aspect of embodiments herein, the object is achieved by a method, performed by the radio network node. The radio network node operates in the communications network. The method is for handling the configuration of the first node. The first node is provided the wired connection to the core network node of the communications network by the first network node via at least the wireless connection. The first node is capable to be provided the respective wired connection to the core network node of the communications network by the a respective second network node via the at least another respective wireless connection. The radio network node receives from the network node, an indication, wherein one of the following applies. With the proviso that the radio network node is the first radio network node, wherein the first node is served by the first network node through at least the first radio network node, the first radio network node having respective wireless connections with the first node and the first network node, the indication is a fourth indication. The fourth indication indicates that a fifth configuration with which the first network node serves the first node is no longer valid. With the proviso the radio network node is the respective second radio network node, wherein the first node is to be served by the respective second network node through at least the respective second radio network node, the respective second radio network node having the other respective wireless connections with the first node and the respective second network node, the indication is a second indication. The second indication indicates to activate the respective first configuration stored at the first radio network node.

According to a fourth aspect of embodiments herein, the object is achieved by the first node. The first node is configured to operate in the communications network. The first node is configured to be served by the first network node. The first node may be understood to be for handling the configuration of the first node. The first node is further configured to receive, from the network node the one or more first indications. The one or more first indications are configured to respectively indicate the one or more first configurations to be applied by the first node upon fulfilment of the one or more respective first criteria. The first node is configured to be provided the wired connection to the core network node of the communications network by the first network node via at least the wireless connection. The first node is configured to be capable to be provided the respective wired connection to the core network node of the communications network by the respective second network node via the at least another respective wireless connection. The first node is also configured to store the one or more first configurations at the first node. The first node is further configured to apply, out of the stored one or more first configurations, the respective first configuration upon fulfilment of the one or more respective first criteria. The receiving is configured to comprise receiving the plurality of first configurations configured to comprise the respective first configuration. The storing is configured to comprise storing the plurality of first configurations and the applying is configured to comprise applying the respective first configuration out of the stored plurality of first configurations. Each of the one or more first configurations is configured to be a BAP configuration.

According to a fifth aspect of embodiments herein, the object is achieved by the network node. The network node is configured to operate in the communications network. The network node may be understood to be for handling the configuration of the first node. The network node is further configured to send the one or more first indications to at least one of: i) the first node configured to be served by a first network node and ii) at least the one first radio network node. The first node is configured to be served by the first network node through the at least one first radio network node. The at least one first radio network node is configured to have the respective wireless connections with the first node and the first network node. The one or more first indications are configured to indicate the one or more first configurations to be applied by the first node upon fulfilment of the one or more respective first criteria. The first node is configured to be provided the wired connection to the core network node of the communications network by the first network node via at least the wireless connection. The first node is configured to be capable to be provided the respective wired connection to the core network node of the communications network by the respective second network node via at least the another respective wireless connection. The sending is configured to comprise sending the plurality of first configurations configured to comprise the respective first configuration to be applied by the first node upon fulfilment of the respective one or more first criteria. Each of the one or more first configurations is configured to be a BAP configuration.

According to a sixth aspect of embodiments herein, the object is achieved by the radio network node. The radio network node is configured to operate in the communications network. The radio network node may be understood to be for handling the configuration of the first node. The first node is configured to be provided the wired connection to the core network node of the communications network by the first network node via at least the wireless connection. The first node is configured to be capable to be provided the respective wired connection to the core network node of the communications network by the respective second network node via at least the another respective wireless connection. The radio network node is further configured to receive, from the network node, the indication, wherein one of the following applies. With the proviso that the radio network node is configured to be the first radio network node, wherein the first node is configured to be served by the first network node through at least the first radio network node, the first radio network node being configured to have the respective wireless connections with the first node and the first network node, the indication is configured to be the fourth indication. The fourth indication is configured to indicate that the fifth configuration with which the first network node is configured to serve the first node is no longer valid. With the proviso the radio network node is configured to be the respective second radio network node, wherein the first node is configured to be served by the respective second network node through at least the respective second radio network node, the respective second radio network node being configured to have the other respective wireless connections with the first node and the respective second network node, the indication is configured to be the second indication. The second indication is configured to indicate to activate the respective first configuration configured to be stored at the first radio network node.

As an advantage, embodiments herein may enable reduced service interruption and signaling through use of previously stored BAP configurations.

BRIEF DESCRIPTION OF THE DRAWINGS

Examples of embodiments herein are described in more detail with reference to the accompanying drawings, and according to the following description.

Figure 1 is a schematic diagram illustrating a basic architecture of IAB, according to existing methods.

Figure 2 is a signalling diagram illustrating an example of a IAB inter-donor topology redundancy procedure.

Figure 3 is a schematic diagram illustrating an example of a topology adaptation procedure for a migrating IAB-MT, according to existing methods.

Figure 4 is a schematic diagram illustrating an example of a mobile lAB-Node which involves intra-donor, inter-donor, same CU, and inter CUs, according to existing methods.

Figure 5 is a schematic diagram illustrating an example of an integration procedure for IAB- node in SA, according to Figure 8.12.1-1 of TS 38.401.

Figure 6 is a schematic diagram depicting a signalling diagram of a BAP Mapping Configuration procedure: Successful Operation, as depicted in Figure 8.10.1.2-1 of TS 38.473. Figure 7 is a schematic diagram illustrating a communications network, according to embodiments herein.

Figure 8 depicts a flowchart of a method in a first node, according to embodiments herein.

Figure 9 depicts a flowchart of a method in a network node, according to embodiments herein.

Figure 10 depicts a flowchart of a method in a radio network node, according to embodiments herein.

Figure 11 is a signalling diagram illustrating an example of a method according to embodiments herein.

Figure 12 is a signalling diagram illustrating an example of a newly defined procedure for storing the conditional BAP configuration.

Figure 13 is a signalling diagram illustrating an example of a newly defined procedure for activating the conditional BAP configuration.

Figure 14 is a signalling diagram illustrating an example of a newly defined procedure for storing the conditional BAP configuration.

Figure 15 is a schematic block diagram illustrating two non-limiting examples, a) and b), of a first node, according to embodiments herein.

Figure 16 is a schematic block diagram illustrating two non-limiting examples, a) and b), of a network node, according to embodiments herein.

Figure 17 is a schematic block diagram illustrating two non-limiting examples, a) and b), of a radio network node, according to embodiments herein.

Figure 18 depicts a flowchart of a method in a first node, according to examples related to embodiments herein.

Figure 19 depicts a flowchart of a method in a network node, according to examples related to embodiments herein.

Figure 20 depicts a flowchart of a method in a radio network node, according to examples related to embodiments herein.

Figure 21 is a schematic block diagram illustrating a telecommunication network connected via an intermediate network to a host computer, according to embodiments herein.

Figure 22 is a generalized block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection, according to embodiments herein.

Figure 23 is a flowchart depicting embodiments of a method in a communications system including a host computer, a base station and a user equipment, according to embodiments herein. Figure 24 is a flowchart depicting embodiments of a method in a communications system including a host computer, a base station and a user equipment, according to embodiments herein.

Figure 25 is a flowchart depicting embodiments of a method in a communications system including a host computer, a base station and a user equipment, according to embodiments herein.

Figure 26 is a flowchart depicting embodiments of a method in a communications system including a host computer, a base station and a user equipment, according to embodiments herein.

DETAILED DESCRIPTION

Certain aspects of the present disclosure and their embodiments may provide solutions to the challenges described in the Summary Section or other challenges. There are, proposed herein, various embodiments which address one or more of the issues disclosed herein.

As a brief overview, embodiments herein may be understood to relate to early BAP layer configuration for mobile IAB.

The determinism in the route of a mobile IAB node, e.g., the route of a train, ship, bus, onboard of which the mobile IAB node may be installed, may be exploited to configure the new configuration at the mobile IAB node in advance. The BAP layer configurations may be stored in each ancestor node and when the mobile IAB may connect to a new parent, the stored BAP configuration may be activated. The BAP layer configurations may consist of conditional configurations of BAP address, BAP routing Identifiers (IDs) that may be set up during, early or regular, F1 setup.

Some of the embodiments contemplated will now be described more fully hereinafter with reference to the accompanying drawings, in which examples are shown. In this section, the embodiments herein will be illustrated in more detail by a number of exemplary embodiments. Other embodiments, however, are contained within the scope of the subject matter disclosed herein. The disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art. It should be noted that the exemplary embodiments herein are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments.

Note that although terminology from LTE/5G has been used in this disclosure to exemplify the embodiments herein, this should not be seen as limiting the scope of the embodiments herein to only the aforementioned system. Other wireless systems with similar features, may also benefit from exploiting the ideas covered within this disclosure.

Figure 7 depicts a non-limiting example of a communications network 100, which may be a wireless communications network, sometimes also referred to as a wireless communications system, cellular radio system, or cellular network, in which embodiments herein may be implemented. The communications network 100 may be a 5G system, 5G network, NR-U or Next Gen System or network, Long-Term Evolution (LTE) system, or a combination of both. The communications network 100 may be, or may support, a younger system than a 5G system. The communications network 100 may support technologies such as, particularly, LTE-Advanced I LTE-Advanced Pro, e.g., LTE Frequency Division Duplex (FDD), LTE Time Division Duplex (TDD), LTE Half-Duplex Frequency Division Duplex (HD- FDD) and LTE operating in an unlicensed band. The communications network 100 may support yet other technologies such as, for example, License-Assisted Access (LAA), Narrow Band Internet of Things (NB-loT), Machine Type Communication (MTC), MulteFire, Wideband Code Division Multiplexing Access (WCDMA), Universal Terrestrial Radio Access (UTRA) TDD, Global System for Mobile communications (GSM) network, Enhanced Data for GSM Evolution (EDGE) network, GSM/EDGE Radio Access Network (GERAN) network, UltraMobile Broadband (UMB), network comprising of any combination of Radio Access Technologies (RATs) such as e.g., Multi-Standard Radio (MSR) base stations, multi-RAT base stations etc., any 3rd Generation Partnership Project (3GPP) cellular network, WiFi networks, Worldwide Interoperability for Microwave Access (WiMax). In particular embodiments, the communications network 100 may be an IAB network. Thus, although terminology from 5G/NR and LTE may be used in this disclosure to exemplify embodiments herein, this should not be seen as limiting the scope of the embodiments herein to only the aforementioned systems.

The communications network 100 comprises a plurality of network nodes, whereof a first network node 101 , a second network node 102, and a third network node 103 are depicted in the non-limiting example of Figure 7. The communications network 100 may comprise one or more second network nodes 110 comprising the second network node 102. Herein, the expression “one or more”, in some examples, may correspond to “a plurality”.

Different features may be described herein, wherein, out of a plurality of features of a same type, a particular feature may correspond to each of the members of a plurality. Hence, the term “respective” may be used to convey a particular feature, of a plurality of features, for a particular entity of a plurality of entities. Accordingly, embodiments herein may refer to a respective second network node 102 or a plurality of respective second network nodes 110. The communications network 100 further comprises a plurality of radio network nodes, whereof a first radio network node 111 , and a second radio second node 112 are depicted in the non-limiting example of Figure 7. It may be understood that the communications network 100 may comprise more network nodes and/or more radio network nodes, which are not represented in Figure 7 to simplify the Figure. Particularly, the communications network 100 may comprise a plurality of second radio network nodes 112 comprising the second radio network node 112.

The communications network 100 may also comprise a plurality of nodes, whereof a first node 130 is depicted in the non-limiting example of Figure 7.

Any of the first network node 101 , the one or more second network nodes 110 comprising the second network node 102, the third network node 103, the first radio network node 111 , the second radio network node 112, and the first node 130 may be a radio network node, such as a radio base station, base station or a transmission point, or any other network node with similar features capable of serving a user equipment, such as a wireless device or a machine type communication device, in the communications network 100. For example, any of the first network node 101, the one or more second network nodes 110 comprising the second network node 102, the third network node 103, first radio network node 111 , the second radio network node 112, and the first node 130 may be a gNB, an eNB, an eNodeB, or a Home Node B, or a Home eNode B. Any of the first network node 101 , the one or more second network nodes 110 comprising the second network node 102, the third network node 103, first radio network node 111 , the second radio network node 112, and the first node 130 may be of different classes, such as, e.g., macro base station (BS), home BS or pico BS, based on transmission power and thereby also cell size. In some embodiments, any of the first network node 101, the one or more second network nodes 110 comprising the second network node 102, the third network node 103, first radio network node 111 , the second radio network node 112, and the first node 130 may be implemented as one or more distributed nodes, such as virtual nodes in the cloud 135, and they may perform their functions entirely on the cloud 135, or partially, in collaboration with one or more radio network nodes.

Any of the first network node 101, the one or more second network nodes 110 comprising the second network node 102, the third network node 103, first radio network node 111 , the second radio network node 112, and the first node 130 may be an IAB node.

The first node 130 may be provided a wired connection to a core network node 140 of the communications network 100 by the first network node 101 via at least a wireless connection. The core network node 140, in some embodiments, may be, for example an Operations Administration and Maintenance (OAM) node, an AMF, etc. The third network node 103 may be a network node having a capability to manage configuration of nodes comprised in the communications network 100. The third network node 103 may be the core network node 140, or another core network node, or, as depicted in the non-limiting example of Figure 7, or another network node, e.g., radio network node, comprised in the communications system 100.

The first node 130 may be capable to be provided a wired connection to the core network node 140 of the communications network 100 by the respective second network node 102 via at least another respective wireless connection.

The first node 130 may be served by the first network node 101 through at least one first radio network node such as the first radio network node 111. The first radio network node 111 may have respective wireless connections with the first node 130 and the first network node 101.

The first node 130 may be to be served by the second network node 102 through at least one respective second radio network node such as the second radio network node 112. The respective second radio network node 112 may have other respective wireless connections with the first node 130 and the second network node 102, that is, a respective second network node 102 of the one or more second network nodes 110. The other second radio network nodes 112 in the plurality of second radio network nodes 112 are not depicted in Figure 7 to simplify the Figure. Each of the second radio network nodes 112 may have a respective connection to a respective second network node 102 of the one or more second network nodes 110. Some of the second radio network nodes 112 may be connected to the same second network node 102, or to different second network nodes.

The first network node 101 may be a Donor Centralized Unit (CU). The first network node 101 may be a source network node, e.g., a source donor CU.

The second network node 102 or respective second network node 102 may be a second Donor CU. The second network node 102 or respective second network node 102 may be a target network node, e.g., a target donor CU.

Any of the first radio network node 111 and the second radio network node 112 may be ancestor nodes. The first radio network node 111 may a source ancestor IAB node.

The second radio network node 112 may be a target ancestor IAB node.

In some examples, the first radio network node 111 may a source parent of the first node 130.

In some examples, the second radio network node 112 may a target parent of the first node 130.

The first node 130 may be a first Integrated Access and Backhaul, IAB, node. In particular examples, the first node 130 may be a mobile IAB (mlAB) node. The first node 130 may be a node, e.g., an IAB node, with no descendants.

Target may be, e.g., future, in a mobility operation from the source to the target.

As depicted in the non-limiting example of Figure 7, the communications network 100 may comprise a multi-hop deployment, wherein the first network node 101 may be a first donor node or source node, e.g., a first lAB-Donor CU, and the second network node 102 may be a second donor node or target node, e.g., a second lAB-Donor CU. A donor node may be understood to be, e.g., a node having a connection, e.g., a wired backhaul connection, to the core network, e.g., the core network node 140 of the communications network 100.

It may be understood that the communications network 100 may comprise more network nodes, radio network nodes and nodes, and more or other multi-hop arrangements, which are not depicted in Figure 7 to simplify the Figure.

Any of the first network node 101, and the one or more second network nodes 110, e.g., the second network node 102, and the core network node 140 may be referred to as a/the “network node 101, 102, 140”.

Any of the first radio network node 111 and the at least one second radio network node 112 may be referred to as a/the “radio network node 111, 112”.

The communications network 100 covers a geographical area which may be divided into cell areas, wherein each cell area may be served by any of the first network node 101 , the one or more second network nodes 110 comprising the second network node 102, the third network node 103, first radio network node 111 , the second radio network node 112, and the first node 130, although, any of the first network node 101, the one or more second network nodes 110 comprising the second network node 102, the third network node 103, first radio network node 111, the second radio network node 112, and the first node 130 may serve one or several cells. In the non-limiting example of Figure 7, not all the cells are depicted to simplify the Figure. Figure 7 depicts a first cell 121 served by the first network node 101 and a respective cell 122, or respective second cell 122, served by the respective second network node 102. Each of the first cell 121 and the respective cell 122 may be comprised of a respective plurality of cells. This is not depicted in Figure 7 to simplify the Figure.

One or more devices 150 may be located in the wireless communication network 100. The one or more devices 150 are depicted in Figure 7 by a single device to simplify the Figure. The one or more devices 150 may be served by first node 130.

Any of the one or more devices 150 may be wireless device, e.g., a 5G UE, which may be a wireless communication device which may also be known as e.g., a UE, a mobile terminal, wireless terminal and/or mobile station, a mobile telephone, cellular telephone, or laptop with wireless capability, just to mention some further examples. The wireless device may be, for example, portable, pocket-storable, hand-held, computer-comprised, or a vehicle- mounted mobile device, enabled to communicate voice and/or data, via the RAN, with another entity, such as a server, a laptop, a Personal Digital Assistant (PDA), or a tablet, Machine-to- Machine (M2M) device, device equipped with a wireless interface, such as a printer or a file storage device, modem, or any other radio network unit capable of communicating over a radio link in a communications system. The wireless device comprised in the communications network 100 is enabled to communicate wirelessly in the communications network 100. The communication may be performed e.g., via a RAN, and possibly the one or more core networks, which may be comprised within the communications network 100.

The first network node 101 may be configured to communicate in the communications network 100 with the second network node 102 over a first link 161. The first radio network node 111 may be configured to communicate in the communications network 100 with the first node 130 over a second link 162. The first node 130 may be configured to communicate in the communications network 100 with the first radio network node 111 over a third link 163. The second radio network node 112 may be configured to communicate in the communications network 100 with the first node 130 over a fourth link 164. The second radio network node 112 may be configured to communicate in the communications network 100 with the respective second network node 102 over a respective fifth link 165. The first network node 101 may be configured to communicate in the communications network 100 with the core network node 140 over a sixth link 166. The respective second network node 102 may be configured to communicate in the communications network 100 with the core network node 140 over a respective seventh link 167. The first network node 101 may be configured to communicate in the communications network 100 with the third network node 103 over an eighth link 168. The respective second network node 102 may be configured to communicate in the communications network 100 with the third network node 103 over a respective ninth link 169. The first node 130 may be configured to communicate in the communications network 100 with any of the one or more devices 150 over a respective link, which is not depicted to simplify the Figure.

The hollow arrow in Figure 7 represents the direction of a movement by the first node 130. This may happen, as a non-limiting example, during a movement of the first node 130 along a route 170, e.g., a fixed route. The first radio network node 111 and the second radio network node 112 may be deployed, e.g., at fixed locations, along the route 170, as depicted in Figure 7.

Any of the first link 161 , the sixth link 166, the respective seventh link 167, the eight link and the respective ninth link 169 may be a wired link.

Any of the second link 162, the third link 163, the fourth link 164, the respective fifth link 165, the eight link and the respective ninth link 169 may be, e.g., a radio link. Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the following description.

In general, the usage of “first”, “second”, “third”, “fourth”, “fifth”, “sixth”, “seventh”, ’’eighth”, “ninth” and/or “tenth” etc., herein may be understood to be an arbitrary way to denote different elements or entities, and may be understood to not confer a cumulative or chronological character to the nouns they modify, unless otherwise noted, based on context.

Several embodiments are comprised herein. It should be noted that the examples herein are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments.

More specifically, the following are embodiments related to a first node, such as the first node 130, e.g., an mlAB, embodiments related to a network node, such as the network node 101 , 102, 140, e.g., any of the first network node 101 , e.g., a first lAB-Donor CU, e.g., a source node, the second network node 102 such as a second lAB-Donor CU, e.g., a target node and the core network node 140, and embodiments related to a radio network node 111 , 112, such as the first radio network node 111 , e.g., a source ancestor IAB node or source parent IAB node, or the second radio network node 112, e.g., a target ancestor IAB node or target parent IAB node.

The terms “m-IAB”, “mobile IAB” and “m-IAB node” may be used interchangeably.

The terms “old donor”, “source donor” and “present donor” may be used interchangeably. The terms “new donor”, “target donor” and “future donor” may be used interchangeably.

Embodiments of a method, performed by a node, such as the first node 130, will now be described with reference to the flowchart depicted in Figure 8. The first node 130 operates in the communications network 100. The first node 130 is served by the first network node 101. The method is for handling configuration of the first node 130. The communications network 100 may be a multi-hop deployment. In some embodiments, the communications network 100 may be an IAB network.

Several embodiments are comprised herein. In some embodiments all the actions may be performed. In other embodiments, some of the actions may be performed. It should be noted that the examples herein are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments. One or more embodiments may be combined, where applicable. All possible combinations are not described to simplify the description. A non-limiting example of the method performed by the first node 130 is depicted in Figure 8. Some actions may be performed in a different order than that shown in Figure 8. In Figure 8, actions which may be optional in some examples are depicted with dashed boxes.

Action 801

In this Action 801 , the first node 130 receives, from the network node 101 , 102, 140, one or more first indications. The one or more first indications respectively indicate one or more first configurations to be applied by the first node 130 upon fulfilment of one or more respective first criteria, e.g., connection to a respective cell 122 served by a respective second network node 102, connection to a respective second network node 102, out of the one or more second network nodes 110, etc...

The first node 130 is provided a wired connection, e.g., the sixth link 166, to the core network node 140 of the communications network 100 by the first network node 101 via at least a wireless connection, e.g., the second link 162 or the third link 163.

The first node 130 is capable to be provided a respective wired connection, e.g., another wired connection, e.g., the respective seventh link 167, to the core network node 140 of the communications network 100 by the respective second network node 102 via at least another respective wireless connection, e.g., the respective fifth link 165.

In some embodiments, at least one of the following may apply. Each of the one or more first configurations may be a BAP configuration. The first node 130 may be a first IAB node, the first network node 101 may be a Donor CU, and the respective second network node 102 may be a second Donor CU. The one or more first indications may originate at the core network node 140. The core network node 140 may be an CAM node. The first node 130 may be an mlAB node. The first node 130 may be a node, e.g., an IAB node, with no descendants. The first node 130 may be served by the first network node 101 through at least one first radio network node, e.g., the first radio network node 111. That is, there may be more than one ancestor node. The first radio network node 111 may have respective wireless connections with the first node 130 and the first network node 101 . The first radio network node 111 may be a source ancestor IAB node. The first node 130 may be to be served by the respective second network node 102 through at least one respective second radio network node 112. The respective second radio network node 112 may have other respective wireless connections with the first node 130 and the respective second network node 102. Each of the one or more first configurations may be a respective BH RLC channel configuration, used to configure a respective RLC entity, e.g., a corresponding logical channel in Medium Access Control (MAC) for BH RLC channel between an lAB-node, e.g., the first node 130 and its respective parent node, e.g., the respective second radio network node 112. The respective second radio network node 112 may be a respective target ancestor IAB node. The respective second radio network node 112 may be a respective target parent IAB node. The one or more first configurations may be identified by a respective identifier. The respective identifier may be, e.g., of the respective cell 122, or of the respective second network node 102. The respective identifier may be a newly defined identifier. The one or more first indications may be one of: i) received in a standalone message, ii) comprising one or more respective first criteria upon the fulfilment of which the respective first configuration may have to be activated, iii) one or more enhanced messages, e.g., one or more enhanced existing messages. The one or more respective first criteria may comprise at least one of: i) the first node 130 identifying, e.g., and connecting to, the respective cell 122, e.g., via Physical Cell Identity (PCI), and/or Cell Global Identity (CGI), indicated in the respective first configuration, ii) the first node 130 entering a geographical area, e.g., a group of cells or a Tracking Area (TA), indicated in the respective first configuration, e.g., within the same donor CU, and iii) the first node 130 establishing a connection, e.g., an F1 connection, to the respective second network node 102, e.g., a new donor CU, e.g., identified by for example, another respective identifier, e.g., gNB-CU name. The first node 130 may receive a further indication, e.g., referred to later as the eighth indication, from the first network node 101 . The further indication may indicate an order in which a plurality of respective second network nodes 110, that is, the one or more second network nodes 110, comprising the respective second network node 102, and/or a plurality of second radio network nodes 112 comprising the respective second radio network node 112, may have to serve the first node 130.

Table 1 shows an example of BAP configurations, as defined in the paragraphs below for this Action 801 . Starting from the left, the first column shows an example of a first respective identifier, as a BAP configuration index, the second column depicts another example, a second respective identifier as a target IAB cell, which may correspond to the first respective identifier.

Table 1

The BH RLC CH configuration may be understood to refer to establishing one or more BH RLC channels between a new parent DU and the first node 130, so both sides may need to be configured.

Ancestors may also need to add additional BH RLC channels between them, although not necessarily.

A BH RLC channel configuration may be as described in existing specifications, reproduced next:

BH-RLC-ChannelConfig

The IE BH-RLC-ChannelConfig may be used to configure an RLC entity, a corresponding logical channel in MAC for BH RLC channel between lAB-node and its parent node.

BH-RLC-ChannelConfig information element

- ASN1 START

- TAG-BHRLCCHANNELCONFIG-START

BH-RLC-ChannelConfig-r16::= SEQUENCE { bh-LogicalChannelldentity-r16 BH-LogicalChannelldentity-r16 OPTIONAL, -- Cond LCH-SetupOnly bh-RLC-ChannellD-r16 BH-RLC-ChannellD-r16, reestablishRLC-r16 ENUMERATED {true} OPTIONAL, - Need N rlc-Config-r16 RLC-Config OPTIONAL, — Cond LCH-Setup mac-LogicalChannelConfig-r16 LogicalChannelConfig OPTIONAL, -- Cond LCH-Setup }

- TAG-BHRLCCHANNELCONFIG-STOP

- ASN1 STOP

Each of the one or more first configurations may comprise at least one of the following. In some embodiments, each of the one or more first configurations may comprise a respective BAP configuration comprising respective at least one of: i) one or more BAP addresses, for the first node 130, e.g., the m-IAB node, ii) one or more downlink (DL) and uplink (UL) BAP routing identifiers (IDs), for the first node 130, iii) one or more second configurations for backhaul mapping of UL traffic originating at the first node 130 or one or more devices 150 served by the first node 130; the mapping may be used for deriving the appropriate next-hop node, BH RLC channel towards the next-hop node, and UL BAP routing ID for an UL packet, depending on traffic type, iv) a BAP routing configuration, v) one or more third configurations for BAP header rewriting; this may include the rewriting of BAP routing ID in the packet header of DL and UL traffic, and vi) one or more fourth configurations for UL and/or DL local rerouting of traffic. In some embodiments, each of the one or more first configurations may comprise at least the respective BH RLC channel (CH) configuration, used to configure the respective RLC entity, e.g., a corresponding logical channel in MAC for BH RLC channel between lAB-node, e.g., the first node 130, and its parent node, e.g., the respective second radio network node 112.

It may be noted that the above configurations may be already standardized, but the focus of embodiments herein may be understood to be how and when, in advance, to deliver them to the first node 130, e.g., an m-IAB node.

The BAP routing configuration may be understood as mapping of DL and UL traffic that may traverse the first node 130, e.g., the m-IAB node, including the mapping from the previous hop node, designated by its BAP address, ingress BH RLC channel, to next-hop node, designated by its BAP address, egress BH RLC channel.

In some embodiments, at least one of the following may apply. At least one of the one or more first indications may be received during a procedure of setting up an F1 connection, e.g., inside an F1 SETUP RESPONSE message from the respective second network node 102. The one or more first indications may be received together with a conditional F1 setup message. The receiving of Action 801 may comprise receiving a plurality of configurations comprising the first configuration, each configuration in the plurality comprising a respective identifier. At least one of the one or more first indications may be comprised in an RRC message. At least one of the one or more first indications may be received via F1 AP. At least one of the one or more first indications may be received via Downlink Control Information (DC I) , or via a MAC control element (CE). The one or more respective first criteria may comprise at least one of: a) executing a handover to the respective cell 122, and b) the first node 130 establishing a connection, e.g., an F1 connection, to the respective second network node 102, e.g., a new donor CU, e.g., identified by for example, another respective identifier, e.g., gNB-Cll name.

Action 802

In some embodiments wherein the first node 130 may be served by the first network node 101 with a fifth configuration, which may be also referred to as a current configuration, an old configuration or an existing configuration, in this Action 802, the first node 130 may receive, from the network node 101, 102, 140, one or more second indications. The one or more second indications may indicate to activate the respective first configuration.

The fifth configuration may be a BAP configuration.

The one or more second indications may be received e.g., together or separate from the one or more first indications. In some examples the one or more first indications may be the same as the one or more second indications, or may be comprised in a same message.

Each of the one or more second indications may respectively indicate to activate the respective first configuration, e.g., immediately or upon fulfilment of the one or more respective first criteria, e.g., connection to the respective second network node 102 or the respective cell 122.

In some embodiments, at least one of the one or more first indications and the one or more second indications may be received during the procedure of setting up an F1 connection, e.g., inside an F1 SETUP RESPONSE message from the respective second network node 102.

At least one of the one or more first indications and the one or more second indications may be comprised in an RRC message.

At least one of the one or more first indications and the one or more second indications may be received via F1AP.

At least one of the one or more first indications and the one or more second indications may be received via DCI, or via a MAC CE. The one or more second indications may be received as part of, or together with, a handover command to the respective cell 122.

The one or more second indications may be respectively comprised in a control Protocol Data Unit (PDU), e.g., BAP control PDU, or a data PDU.

In an example, a fast activation of new first configuration may be initiated by the first network node 101 , wherein the fast activation may be a command that may activate at the first node 130 an already configured first configuration. Such activation may be based upon using a new control PDU or data PDU, e.g., BAP control PDU or data PDU. An example shown later in Figure 14 is for a BAP control PDU. This control message may be transmitted by the respective second network node 102, e.g., the target donor node to which the first node 130 may be migrating after the first node 130 may complete the migration. Alternatively, this control PDU may be transmitted by the first network node 101 , the source donor when it may initiate the migration of the first node 130, e.g., this control message may be transmitted in conjunction with the Handover (HO) command, e.g., RRCReconfigurationWithSync message, that may initiate the migration of the first node 130 to the respective second network node 102.

While the third indication and fourth indications will be explained later, the PDU may comprise other indications. Particularly, in some embodiments, the PDU may comprise at least one of the following: a) a fifth indication indicating an activation or deactivation flag of the respective first configuration, b) a sixth indication identifying the respective first configuration, and c) a seventh indication indicating a final destination of the first node 130 when served by the respective second network node 102, e.g., a new parent node.

The fifth indication may be, for example, an “A/D” field. The A/D field may represent an activation (“A”) or deactivation (“D”) flag of a certain BAP configuration, which may be identified by the M-IAB ID.

The sixth indication may be, for example, an M-IAB-ID field. The M-IAB-ID field may be a unique ID/configuration index, provided to the first node 130, e.g., m-IAB node and the new ancestors. As the m-IAB node, the ID may pertain to a particular BAP configuration, stored at the m-IAB node that may have to be activated. At the new ancestor nodes, the ID may pertain to the BAP routing entries at the new ancestors, where these routing entries may be used to route the packet to and from the m-IAB node. Hence, the PDU used for fast activation may be travelling hop by hop from the new donor, e.g., the respective second network node 102, via the new ancestors towards the new parent, e.g., the respective second radio network node 112, and may trigger the activation of BAP routing entries at new ancestor nodes, including the new parent, where these routing entries may pertain to the BAP routing IDs terminated at the m-IAB node. Once the PDU traverses all the ancestors and arrives at the new parent, e.g., the respective second radio network node 112, the routing path from the new donor to the m-IAB may be ready. In a variant, several BAP routing paths may exist from the new donor to the m- IAB node.

The seventh indication may be, for example, a Destination and Path field. This may be understood to represent the final destination of the fast activation indication, e.g., the new parent node, e.g., the respective second radio network node 112. The destination may be indicated by an identifier of the new parent, e.g., Destination = BAP address of the new parent, Path = path ID towards the new parent, or by an identifier, e.g., NR CGI, of the cell served by the new parent that the m-IAB may connect/disconnect. Each ancestor node may check this and may activate/deactivate the BAP config and pass the BAP PDU it to its child IAB node.

In another variant, the information may be conveyed via MAC CE or DCI, hop by hop, from the new donor to the new parent of the IAB node.

PDU type

Length: 4 bits

This field may indicate the type of control information included in the corresponding BAP Control PDU. Table 2 below, otherwise referred to as Table 6.3.7-1 , shows the description corresponding to the bit values the “PDU type” field in the PDU of Figure 14 may take. See Figure 14 for an illustration of the PDU.

Table 2

The Data/control PDU may traverse hop by hop and inform the involved parent and ancestor node of the connecting m-IAB node to activate the BAP configuration with respect to certain ID. This ID may be based upon m-IAB static pre-defined BAP configuration ID or configuration index.

The seventh indication may be a BAP routing ID. The BAP routing ID may comprise the BAP address of the first node 130 and a path ID, or it may simply be the BAP address of the first node 130.

There may be two or more such PDUs travelling towards the respective second radio network node 112, e.g., the new parent of the first node 130 along different paths under the respective second network node 102.

Action 803

In some embodiments wherein the first node 130 may be served by the first network node 101 with the fifth configuration, in this Action 803, the first node 130 may receive, from the network node 101, 102, 140, one or more third indications. The one or more third indications may indicate to store at least one of the one or more first configurations and the one or more second indications, until application of the respective first configuration.

Action 804

In this Action 803, the first node 130 stores the one or more first configurations at the first node 130.

The one or more first configurations may be stored, e.g., along with the respective identifier.

Fast Activation/deactivation of BAP configuration

As stated earlier, some actions may be performed in a different order than that shown in Figure 8. For example, Action 802 may be performed after Action 804, as will be described next.

In an example, it may be that once the BAP configuration, may have been stored in the first node 130, e.g., an m-IAB node, and the first radio network node 111, e.g., the ancestor node, a fast activation of a new BAP configuration, may be initiated by the first network node 101 , e.g., the IAB Donor node, wherein the fast activation may be a command that may activate at the first node 130, e.g., the m-IAB node, an already configured BAP configuration.

Such activation may be based upon using the new control PDU or data PDU, e.g., BAP control PDU or data PDU described in Action 802.

In one example, the fast activation of a BAP configuration may deactivate another active BAP configuration. In another example, the fast activation command may just activate a BAP configuration, whereas the other active BAP configuration may remain active until the migration may be completed, that is, until the m-IAB node may send the RRCReconfigurationComplete message to the target donor node.

Action 805

In some embodiments, wherein the first node 130 may be served by the first network node 101 with the fifth configuration, in this Action 805, the first node 130 may receive, from the network node 101, 102, 140, a fourth indication. The fourth indication may indicate that the fifth configuration is no longer valid.

Action 806

In this Action 806, the first node 130 applies, out of the stored one or more first configurations, a respective first configuration. The applying, out of the stored one or more first configurations, of the respective first configuration may be performed upon fulfilment of the one or more respective first criteria, e.g., connection to the respective second network node 102 and/or the respective cell 122.

In embodiments herein, the receiving in Action 801 comprises receiving a plurality of first configurations comprising the respective first configuration, the storing in Action 804 comprises storing the plurality of first configurations and the applying in this Action 806 comprises applying the respective first configuration out of the stored plurality of first configurations. Each of the one or more first configurations is a BAP configuration.

In some embodiments, at least one of the following may apply. The first node 130 may be a first I AB node, the first network node 101 may be a Donor CU, and the respective second network node 102 may be a second Donor CU. The one or more first indications may originate at the core network node 140. The core network node 140 may be an CAM node. The first node 130 may be an mlAB node. The first node 130 may be a node, with no descendants. The applying of Action 806 may be performed during the movement of the first node 130 along the route 170, e.g., a fixed route. The first node 130 may be served by the first network node 101 through at least one first radio network node, e.g., the first radio network node 111. The first radio network node 111 may have respective wireless connections with the first node 130 and the first network node 101. The first radio network node 111 may be the source ancestor IAB node. The first node 130 may be to be served by the respective second network node 102 through at least one respective second radio network node 112. The respective second radio network node 112 may have other respective wireless connections with the first node 130 and the respective second network node 102. Each of the one or more first configurations may be the respective BH RLC channel configuration, used to configure the RLC entity. The respective second radio network node 112 may be the respective target ancestor IAB node. The respective second radio network node 112 may be the respective target parent IAB node. The one or more first configurations may be identified by the respective identifier. The respective identifier may be a newly defined identifier. The one or more first indications may be one of: i) received in the standalone message, ii) comprising the one or more respective first criteria upon the fulfilment of which the respective first configuration may have to be activated, iii) the one or more enhanced messages. The one or more respective first criteria may comprise at least one of: i) the first node 130 identifying the respective cell 122, indicated in the respective first configuration, ii) the first node 130 entering the geographical area, indicated in the respective first configuration, and iii) the first node 130 establishing the connection, to the respective second network node 102. The first node 130 may receive the further indication, from the first network node 101. The further indication may indicate the order in which the plurality of respective second network nodes 110, comprising the respective second network node 102, and/or the plurality of second radio network nodes 112 comprising the respective second radio network node 112, may have to serve the first node 130.

Action 807

In some embodiments wherein the first node 130 may be served by the first network node 101 with the fifth configuration, the method may further comprise, after activating the respective first configuration, in this Action 807, the first node 130 performing an action on the fifth configuration. The action may be selected from: i) deleting the fifth configuration and keeping other previous BAP configurations and/or BH RLC channel configurations, ii) deactivating the fifth configuration, e.g., a previous BAP configuration and/or BH RLC channel configuration, iii) keeping the fifth configuration in a list of previous BAP configurations and/or BH RLC channel configurations, and iv) deleting the fifth configuration and any other previous BAP configurations and/or BH RLC channel configurations.

Embodiments of a method, performed by a network node, such as the network node 101 , 102, 140, will now be described with reference to the flowchart depicted in Figure 9. The network node 101 , 102, 140 operates in the communications network 100. The method is for handling the configuration of the first node 130.

The communications network 100 may be a multi-hop deployment. In some embodiments, the communications network 100 may be an IAB network.

In some embodiments, the network node 101, 102, 140 may be the first network node 101. In some embodiments, the network node 101, 102, 140 may be the respective second network node 102. In some embodiments, the network node 101 , 102, 140 may be the core network node 140.

Several embodiments are comprised herein. The method may comprise one or more of the following actions. In some embodiments, all the actions may be performed. In other embodiments, one or more actions may be performed. It should be noted that the examples herein are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments. One or more embodiments may be combined, where applicable. All possible combinations are not described to simplify the description. A non-limiting example of the method performed by the network node 101 , 102, 140 is depicted in Figure 9. Some actions may be performed in a different order than that shown in Figure 9. In Figure 9, actions which may be optional in some examples are depicted with dashed boxes. The detailed description of some of the following corresponds to the same references provided above, in relation to the actions described for the first node 130 and will thus not be repeated here to simplify the description. For example, in some examples the one or more first indications may be the same as the one or more second indications, or may be comprised in a same message.

Action 901

In this Action 901 , the network node 101 , 102, 140 may send a first message the core network node 140. The message may request at least one of the one or more first configurations, that is, the BAP configurations.

In some embodiments, at least one of the following may apply: a) the first message may be an NG Application Protocol (NGAP) message towards one or more serving AMFs, b) the first message may comprise an indication, referred to herein as a ’’tenth indication”, indicating a quantification of current or predicted traffic load at the first node 130, c) the core network node 140 may be the GAM node, and d) the first message may comprise information about the fifth configuration. That is, the configuration with which the first node 130 may be being served by the first network node 101.

Action 902

In some embodiments, in this Action 902, the network node 101 , 102, 140 may obtain the one or more first configurations from at least one of: i) the one or more respective second network nodes 110 comprising the respective second network node 102, wherein the one or more respective second network nodes 110 may have a capability to provide, to the first node 130, the respective wired connection to the core network node 140 of the communications network 100 via at least a respective wireless connection, and ii) the third network node 103 managing configuration of nodes comprised in the communications network 100.

The obtaining in this Action 902 of the one or more first configurations may be in response to the sent first message in Action 901.

Each of the one or more first configurations may comprise at least one of: a) the respective BAP configuration comprising the respective at least one of: i) the one or more BAP addresses for the first node 130, ii) the one or more DL and UL BAP routing IDs for the first node 130, iii) the one or more second configurations for backhaul mapping of UL traffic originating at the first node 130 or the one or more devices 150 served by the first node 130, iv) the BAP routing configuration, v) the one or more third configurations for BAP header rewriting, and vi) the one or more fourth configurations for UL and/or DL local rerouting of traffic, and b) the respective BH RLC channel configuration, used to configure the respective RLC entity, e.g., the corresponding logical channel in MAC for BH RLC channel between IAB- node, e.g., the first node 130 and its parent node, e.g., the respective second radio network node 112.

Action 903

In some embodiments, in this Action 903, the network node 101 , 102, 140 may obtain, from at least one of the one or more respective second network nodes 110, the third network node 103 and the core network node 140, at least one of an eight indication and a ninth indication. The eighth indication may indicate an order in which the plurality of respective second network nodes 110 and/or the plurality of respective second radio network nodes 112 comprising the respective second radio network node 112 may have to serve the first node 130, e.g., along the route 170. The ninth indication may indicate a list of the one or more respective second network nodes 110 from which the first network node 101 may have to request the respective first configuration of the one or more first configurations.

At least one of the obtaining 902 of the one or more first configurations and the obtaining 903 of the at least one of the eighth indication and the ninth indication may be performed via one of: i) one or more XnAP messages, and ii) by means of signalling traversing the core network 140 of the communications network 100.

The interplay of Actions 901, 902 and 903 may be described as follows.

Obtaining the BAP configurations from future serving donor CUs

This section explains how the donor which may be presently serving the first node 130, e.g., the m-IAB node, may obtain the future BAP configurations. That is, how the first network node 101 may obtain the future BAP configurations.

In one example, the donor which may be presently serving the m-IAB node (“present donor”), that is, the first network node 101, may obtain, in Action 902, the BAP configurations from one or more donors that may be going to serve the m-IAB node after the present donor (“future donors”) that is, the plurality of respective second network nodes 110.

In one variant, the BAP configurations to be used at future donors may be obtained, in Action 902, from a network entity, e.g., the third network node 103, that may manage a pool of configurations to be used by m-IAB nodes at various donor, e.g., the OAM entity. The information received may also contain, according to Action 903, an indication of the order in which the future donors may serve the m-IAB, e.g., the next donor to serve it, the subsequent donor etc. that is, the eighth indication.

In one variant, the OAM, according to Action 903, may configure the present donor with the list of future donors from which the present donor may need to request future BAP configurations that is, the ninth indication. The list of donors, according to Action 903, may also contain an indication of the order in which the future donors may serve the m-IAB, e.g., the next donor to serve it, the subsequent donor etc. that is, the eighth indication. In another variant, this list, of future donors to be contacted by the present donor, may be obtained, according to Action 903, from another network node, e.g., a core network node.

In one variant, the BAP configurations may be obtained from future donors via XnAP by means of a newly defined procedure or an enhancement of an existing procedure. Herein, based on the list of future donors, received as described above, the present node may send a request message, according to Action 901 , to future donors via XnAP, and future donors may respond, according to Action 902, to the message and include the future configurations in this message.

In another variant, in case where the present donor does not have an established XnAP interface with the future donors, it may obtain the configurations from future donors by means of signalling that traverses the core network. For example, 1) the present donor may send a newly defined or an enhanced existing NG Application Protocol (NGAP) message towards its serving AMF, containing the ID of a future donor, this ID may, e.g., be the (existing) gNB ID, from which the future BAP configuration may be requested, according to Action 901. The request may also contain: a) a quantification of the DL/LIL traffic load currently served by the m-IAB node or an estimate of future traffic load, e.g., at the time the node may be expected to connect to the future donor, and b) information about the current BAP configuration of the IAB node, containing, e.g., the parameters described in Action 801. 2) The AMF may forward the request to the future donor, based on the future donor ID. If the future donor is served by another AMF, the AMF serving the present donor may forward the request(s) to the AMF(s) serving the future donor(s), by means of inter-AMF signalling, newly defined or an enhanced existing signalling. 3) The future donor may reply to the request, , by sending it to the AMF, which may forward it, according to Action 902, to the present donor, directly or via the AMF serving the present donor.

In one variant, the above may be executed only towards the next donor to serve the m- IAB. In another variant, the above may be executed towards multiple subsequent donors, namely the plurality of one or more second network nodes 110.

Action 904

In this Action 904, the network node 101 , 102, 140 sends the one or more first indications to at least one of: i) the first node 130 served by the first network node 101 and ii) at least one first radio network node 111. The first node 130 is served by the first network node 101 through the at least one first radio network node 111. The at least one first radio network node 111 has the respective wireless connections with the first node 130 and the first network node 101.

The one or more first indications indicate the one or more first configurations to be applied by the first node 130 upon fulfilment of the one or more respective first criteria, e.g., connection to the respective cell 122 served by the respective second network node 102.

The first node 130 is provided the wired connection to the core network node 140 of the communications network 100 by the first network node 101 via at least the wireless connection. The first node 130 is capable to be provided the respective wired connection to the core network node 140 of the communications network 100 by the respective second network node 102 via at least the another respective wireless connection.

The sending in this Action 904 comprises sending the plurality of first configurations comprising the respective first configuration to be applied by the first node 130 upon fulfilment of the respective one or more first criteria. Each of the one or more first configurations is a BAP configuration.

In some embodiments, at least one of the following may apply. The first node 130 may be a first I AB node, the first network node 101 may be a Donor CU, and the respective second network node 102 may be a second Donor CU. Each of the at least one first radio network node 111 may be an ancestor node. The one or more first indications may originate at the core network node 140, e.g., as obtained in Action 902. The core network node 140 may be an CAM node. The first node 130 may be an mlAB node. The first node 130 may be a node, e.g., an IAB node, with no descendants. The sending of this Action 904 may be performed during the movement of the first node 130 along the route 170, e.g., a fixed route. The first radio network node 111 may be a source ancestor IAB node. The first node 130 may be to be served by the respective second network node 102 through at least the one respective second radio network node 112. The respective second radio network node 112 may have the other respective wireless connections with the first node 130 and the respective second network node 102. Each of the one or more first configurations may be a respective BH RLC channel configuration, used to configure a respective RLC entity, e.g., a corresponding logical channel in MAC for BH RLC channel between an lAB-node, e.g., the first node 130 and its respective parent node, e.g., the respective second radio network node 112. The respective second radio network node 112 may be a respective target ancestor IAB node. The respective second radio network node 112 may be a respective target parent IAB node. The one or more first configurations may be identified by the respective identifier. The respective identifier may be, e.g., of the respective cell 122, or of the respective second network node 102. The respective identifier may be the newly defined identifier. The one or more first indications may be one of: i) received in the standalone message, ii) comprising the one or more respective first criteria upon the fulfilment of which the respective first configuration may have to be activated, iii) the one or more enhanced messages, e.g., the one or more enhanced existing messages. The one or more respective first criteria may comprise at least one of: i) the first node 130 identifying, e.g., and connecting to, the respective cell 122, e.g., via Physical Cell Identity (PCI), and/or Cell Global Identity (CGI), indicated in the respective first configuration, ii) the first node 130 entering the geographical area, e.g., the group of cells or the TA, indicated in the respective first configuration, e.g., within the same donor CU, and iii) the first node 130 establishing a connection, e.g., the F1 connection, to the respective second network node 102, e.g., the new donor CU, e.g., identified by for example, another respective identifier, e.g., gNB-CU name. The network node 101 , 102, 140 may send to the first node 130 the further indication, e.g., referred to later as the eighth indication, from the first network node 101. The further indication may indicate the order in which the plurality of respective second network nodes 110, that is, the one or more second network nodes 110, comprising the respective second network node 102, and/or the plurality of second radio network nodes 112 comprising the respective second radio network node 112, may have to serve the first node 130, e.g., along the route 170.

Action 905

In some embodiments, wherein the network node 101 , 102, 140 may be one of the first network node 101 and the respective second network node 102, and wherein the first node 130 may be served by the first network node 101 with the fifth configuration, the network node 101 , 102may perform this Action 905.

In this Action 905, the network node 101 , 102, 140 may send, to at least one of the first node 130 and the radio network node 111, 112, the one or more second indications. The one or more second indications may indicate, e.g., respectively, to activate the respective first configuration, e.g., immediately or upon fulfilment of the one or more respective first criteria, e.g., connection to the respective second network node 102 or the respective cell 122.

The one or more second indications may be sent e.g., together or separate from the one or more first indications.

In some embodiments, at least one of the following may apply: i) at least one of the one or more first indications and the one or more second indications may be sent during the procedure of setting up an F1 connection, e.g., inside an F1 SETUP RESPONSE message from the respective second network node 102, ii) the one or more first indications may be sent together with the conditional F1 setup message, iii) the sending of Action 904 may comprise sending the plurality of configurations comprising the first configuration, each configuration in the plurality comprising the respective identifier, iv) at least one of the one or more first indications and the one or more second indications may be comprised in a RRC message, v) at least one of the one or more first indications and the one or more second indications may be received via F1AP, vi) at least one of the one or more first indications and the one or more second indications may be received via DC I , or via a MAC control element, vii) the one or more respective first criteria may comprise at least one of: a) executing a handover to the respective cell 122, and b) the first node 130 establishing the connection, e.g., an F1 connection, to the respective second network node 102, e.g., the new donor CU, e.g., identified by for example, the another respective identifier, e.g., gNB-Cll name, viii) the one or more second indications may be sent as part of, or together with, the handover command to the respective cell 122, and ix) the one or more second indications may be respectively comprised in the control PDU, e.g., BAP control PDU, or a data PDU.

The PDU may comprise at least one of the following: a) the fifth indication indicating the activation or deactivation flag of the respective first configuration, b) the sixth indication identifying the respective first configuration, and c) the seventh indication indicating the final destination of the first node 130 when served by the respective second network node 102, e.g., the new parent node.

Action 906

In some embodiments, wherein the network node 101 , 102, 140 may be one of the first network node 101 and the respective second network node 102, and wherein the first node 130 may be served by the first network node 101 with the fifth configuration, the network node 101 , 102 may perform this Action 906.

In this Action 906, the network node 101, 102, 140 may send, to at least one of the first node 130 and the radio network node 111 , 112, the one or more third indications.

The one or more third indications may indicate to store at least one of the one or more first configurations and the one or more second indications, until application of the respective first configuration.

Action 907

In this Action 907, the network node 101 , 102, 140 may store the one or more first configurations, e.g., along with the respective identifier.

Action 908

In some embodiments, wherein the network node 101 , 102, 140 may be one of the first network node 101 and the respective second network node 102, and wherein the first node 130 may be served by the first network node 101 with the fifth configuration, the network node 101 , 102 may, e.g., after activating the first configuration, perform this Action 908.

In this Action 908, the network node 101 , 102, 140 may send, to at least one of the first node 130 and the at least one first network node 111 , the fourth indication.

The fourth indication may indicate that the fifth configuration is no longer valid.

Action 909

In this Action 909, the network node 101, 102, 140 may apply the stored respective first configuration upon fulfilment of the one or more respective first criteria, e.g., connection to the respective second network node 102 and/or the respective cell 122.

Action 910

In some embodiments, e.g., wherein the network node 101 , 102, 140 may be the first network node 101 , and wherein the first network node 101 may serve the first node 130 with the fifth configuration, the network node 101, 102, 140 may, in this Action 910, perform the action, after activating the respective first configuration. The performing of the action may be on the fifth configuration. The action may be selected from: i) deleting the fifth configuration and keeping other previous BAP configurations and/or BH RLC channel configurations, ii) deactivating the fifth configuration, e.g., a previous BAP configuration and/or BH RLC channel configuration, iii) keeping the fifth configuration in a list of previous BAP configurations and/or BH RLC channel configurations, and iv) deleting the fifth configuration and any other previous BAP configurations and/or BH RLC channel configurations.

Embodiments of a method, performed by a radio network node, such as the radio network node 111, 112, will now be described with reference to the flowchart depicted in Figure 10. The radio network node 111, 112 operates in the communications network 100. The method is for handling the configuration of the first node 130.

The communications network 100 may be a multi-hop deployment. In some embodiments, the communications network 100 may be an IAB network. In some embodiments, the radio network node 111, 112 may be the first radio network node 111. In some embodiments, the radio network node 111, 112 may be the respective second radio network node 112.

Several embodiments are comprised herein. The method may comprise one or more of the following actions. In some embodiments, all the actions may be performed. In other embodiments, one or more actions may be performed. It should be noted that the examples herein are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments. One or more embodiments may be combined, where applicable. All possible combinations are not described to simplify the description. A non-limiting example of the method performed by the radio network node 111 , 112 is depicted in Figure 10. Some actions may be performed in a different order than that shown in Figure 10. In Figure 10, actions which may be optional in some examples are depicted with dashed boxes. The detailed description of some of the following corresponds to the same references provided above, in relation to the actions described for the first node 130 and will thus not be repeated here to simplify the description. For example, the BH RLC CH configuration may be understood to refer to establishing one or more BH RLC channels between a new parent DU and the first node 130.

Action 1001

In this Action 1001, the radio network node 111 , 112 may receive, from the network node 101 , 102, 140, the first indication.

The first indication may indicate the respective first configuration to be applied by the first node 130 upon fulfilment of the one or more respective first criteria, e.g., connection to the respective cell 122 served by the respective second network node 102. The respective first configuration may be identified by the respective identifier, e.g., of the respective cell 122, or of the respective second network node 102.

The respective first configuration may comprise at least one of: a) the respective BAP configuration comprising the respective at least one of: i) the one or more BAP addresses, for the first node 130, ii) the one or more DL and UL BAP routing IDs, for the first node 130, iii) the one or more second configurations for backhaul mapping of UL traffic originating at the first node 130 or one or more devices 150 served by the first node 130, iv) the BAP routing configuration, v) the one or more third configurations for BAP header rewriting, and vi) the one or more fourth configurations for UL and/or DL local rerouting of traffic, and b) the respective BH RLC channel configuration, e.g., the respective BH RLC channel configuration, used to configure the respective RLC entity, e.g., the corresponding logical channel in MAC for BH RLC channel between lAB-node, e.g., the first node 130 and its parent node, e.g., the respective second radio network node 112.

Action 1002

In this Action 1002, the radio network node 111, 112 receives, from the network node

101 , 102, 140, an indication, wherein at least one of the following may apply. With the proviso that the radio network node 111, 112 is the first radio network node 111, wherein the first node 130 is served by the first network node 101 through at least the first radio network node 111, the first radio network node 111 having the respective wireless connections with the first node 130 and the first network node 101 , the indication is the fourth indication. The fourth indication indicates that the fifth configuration with which the first network node 101 serves the first node 130 is no longer be valid. With the proviso the radio network node 111, 112 is the respective second radio network node 112, wherein the first node 130 is to be served by the respective second network node 102 through at least the respective second radio network node 112, the respective second radio network node 112 having the other respective wireless connections with the first node 130 and the respective second network node 102, the indication is the second indication. The second indication indicates to activate the respective first configuration stored at the first radio network node 111 , e.g., immediately or upon fulfilment of the one or more first criteria, e.g., connection by the first node 130 to the respective second network node

102.

In some embodiments, at least one of the following may apply: i) at least one of the first indication and the second indication may be received during the procedure of setting up an F1 connection, e.g., inside an F1 SETUP RESPONSE message from the respective second network node 102, ii) the first indication may be received together with a conditional F1 setup message, iii) the receiving of Action 1001 may comprise receiving the plurality of configurations comprising the respective first configuration, each configuration in the plurality comprising the respective identifier, iv) at least one of the first indication and the second indication may be comprised in an RRC message, v) at least one of the first indication and the second indication may be received via F1AP, vi) at least one of the first indication and the second indication may be received via DCI, or via a MAC control element, vii) the one or more respective first criteria may comprise at least one of: a) the first node 130 executing a handover to the cell 122, e.g., the respective cell 122, and b) the first node 130 establishing a connection, e.g., an F1 connection, to the respective second network node 102, e.g., respective second network node 102, e.g., the new donor CU, e.g., identified by for example, another respective identifier, e.g., gNB-CU name, viii) the second indication may be received as part of, or together with, a handover command to the cell 122, e.g., the respective cell 122, and ix) the second indication may be comprised in a PDU, e.g., BAP control PDU, or a data PDU.

The PDU may comprise at least one of the following: a) the fifth indication indicating the activation or deactivation flag of the first configuration, b) the sixth indication identifying the first configuration, and c) the seventh indication indicating the final destination of the first node 130 when served by the respective second network node 102, e.g., the new parent node.

In some embodiments, the respective second radio network node 112 may be to directly serve the first node 130 as a new parent. In some of these embodiments, the second indication may be an existing F1AP UE CONTEXT SETUP REQUEST message with a particular, e.g., gNB-CU UE F1AP ID, gNB-DU UE F1AP ID, identifier pair.

The identifier pair may have been previously, e.g., at the time when the BAP routing config was given to the new parent, associated to a BAP routing configuration.

In some embodiments, the second indication may activate a respective BH RLC channel configuration at the respective second radio network node 112.

Action 1003

In some embodiments wherein the first node 130 may be served by the first network node 101 with the fifth configuration, the radio network node 111, 112 may receive, from the network node 101, 102, 140, the third indication.

The third indication may indicate to store at least one of the respective first configuration and the second indication, until application of the respective first configuration.

Action 1004

In this Action 1004, the radio network node 111 , 112 may store the respective first configuration at the radio network node 111, 112, e.g., along with the identifier.

Action 1005

In this Action 1005, the radio network node 111 , 112 may apply the second or fourth indication may be immediately, or upon fulfilment of the one or more respective first criteria, e.g., connection to the respective second network node 102 and/or the respective cell 122.

In some embodiments, at least one of the following may apply: i) the respective first configuration may be a BAP configuration, ii) the respective first configuration may be a respective BH RLC channel configuration, used to configure a respective RLC entity, iii) the first node 130 may be a first IAB node, the first network node 101 may be a Donor CU, and the respective second network node 102, e.g., respective second network node 102, may be a second Donor CU, iv) the first indication may originate at the core network node 140, the core network node 140 being the OAM node, v) the first node 130 may be an mlAB node, vi) the first node 130 may be a node, e.g., an IAB node, with no descendants, vii) the applying of Action 1005 may be performed during the movement of the first node 130 along the route 170, e.g., a fixed route, viii) the first radio network node 111 may be a source ancestor IAB node, ix) the first node 130 may be to be served by the respective second network node 102 through at least the one respective second radio network node 112, the respective second radio network node 112 having other respective wireless connections with the first node 130 and the respective second network node 102, x) the respective second radio network node 112 may be a respective target ancestor IAB node, xi) the respective second radio network node 112 may be a respective target parent IAB node, xii) the first indication may be one of: a) received in the standalone message, b) comprising the one or more respective first criteria upon the fulfilment of which the respective first configuration may have to be activated, and c) the enhanced message, e.g., the enhanced existing message, and xiii) the one or more respective first criteria may comprise at least one of: a) the first node 130 identifying , e.g., and connecting to, the respective cell 122, e.g., via PCI, and/or CGI, indicated in the respective first configuration, b) the first node 130 entering the geographical area, e.g., the group of cells or the TA, indicated in the respective first configuration, e.g., within the same donor CU, and c) the first node 130 establishing the connection, e.g., an F1 connection, to the respective second network node 102, e.g., the new donor CU, e.g., identified by for example, another respective identifier, e.g., gNB-CU name.

Action 1006

In some embodiments, e.g., wherein the first node 130 may be served by the first network node 101 with the fifth configuration, the radio network node 111, 112 may, in this Action 1006, after activating the respective first configuration, perform the action. The performing of the action may be on the fifth configuration. The action may be selected from: i) deleting the fifth configuration and keeping other previous BAP configurations and/or BH RLC channel configurations, ii) deactivating the fifth configuration, e.g., a previous BAP configuration and/or BH RLC channel configuration, iii) keeping the fifth configuration in a list of previous BAP configurations and/or BH RLC channel configurations, and iv) deleting the fifth configuration and any other previous BAP configurations and/or BH RLC channel configurations.

Some embodiments herein will now be further described with some non-limiting examples. Any of the details described in the following examples may be understood to be able to be combined with any of the embodiments just described, as pertinent. In the following description, any reference to a/the mobile I AB, and/or the mlAB, and/or mobile IAB node, and/or mlAB node may be understood to equally refer the first node 130; any reference to a/the “old donor”, “source donor”, “source CU”, “present donor”, “current donor”, “currently serving donor”, “current source” “present node”, may be understood to equally refer the network node 101 ; any reference to a/the “new donor”, “target donor”, “target donor node”, “target CU”, “new source”, “future serving donor”, “future donor CU” and “future donor” may be understood to equally refer the respective second network node 102; any reference to a/the source/old/present parent or ancestor may be understood to equally refer the first radio network node 111 ; any reference to a/the target/new/future parent or ancestor or ancestor node may be understood to equally refer the respective second radio network node 112; any reference to a/the core network node may be understood to equally refer the core network node 140.

EXAMPLES

The following is an example of embodiments herein the first node 130 may be a mobile IAB node. First, in accordance with Action 801 , the mobile IAB node may be provided and configured with one or more BAP configurations that may have to be applied. In one variant, the mobile IAB may be provided with BAP configurations as a newly defined standalone message, also including the criteria upon the fulfilment of which the configuration may be activated. Alternatively, the configurations may be provided as part of existing, enhanced, messages. For example, criteria for the activation of the said configuration may be activated may be as follows. A first criteria may be that the m-IAB may connect to a cell served by a certain donor, wherein the cell may be identified by the PCI or by the CGI and wherein the cell in which the BAP configuration may have to be applied may be indicated as part of the BAP configuration itself. A second criteria may be that the m-IAB node may enter a certain geographical or tracking area, after which it may report to its currently serving donor that the handover to the donor serving the area may have to be considered. In one variant, the mobile IAB node may be provided, in accordance with Action 801, with BAP configurations during the F1 setup procedure, e.g., inside a F1 SETUP RESPONSE message from the new donor, with an indication of applying the BAP configurations. Alternatively, the F1 SETUP RESPONSE from the new donor may contain an indication for configuration activation, whereas the configuration itself may be conveyed to the node earlier.

In one variant, the mobile IAB may be provided, in accordance with Action 801 , with BAP configurations together with a conditional F1 setup message with an indication of applying them after either successful handover or fulfilment of one or more criteria.

In one variant, the mobile IAB may be provided, in accordance with Action 801 , with multiple candidate BAP configurations with an identifier used to distinguish the different BAP configurations. The identifier may be explicit, e.g., an index, target cell NR CGI, target gNB ID, target PCI, or implicit.

In one variant, the mobile I AB may be indicated, in accordance with Action 803, that previous BAP routing configurations sent previously by a donor CU may have to be retained by the IAB node, e.g., stored in a local variable, until they may be applied upon fulfilling the aforementioned criteria.

In one variant, the mobile IAB may be indicated, in accordance with Action 805, that the previous BAP configurations are not valid anymore and may need to be changed with the new ones just received. For example, a certain BAP configuration may be only valid in a certain geographical area or tracking area, or in a certain cell or list of cells. If the mobile IAB node exits such area, or cell, e.g., list of cells, the IAB node may release the BAP configuration previously provided. In another example, assuming that the IAB node has configured a BAP configuration valid in a certain area, or cell, e.g., list of cells, such BAP configuration may be deconfigured/removed if the IAB node receives a new BAP configuration valid for the same area, or cell, e.g., list of cells. In one variant, the mobile IAB may be indicated that the previous BAP configurations are still valid and that the new ones received may have to be added to the old ones.

In one variant the m-IAB may receive, in accordance with Action 801 , the configurations while still being connected to the old parent and donor, from the old donor. In another variant, it may receive, in accordance with Action 801 , the configurations when it may connect to a new parent/donor.

The mobile IAB node may be provided, in accordance with Action 801 , with the BAP configuration(s) in one of the following ways.

In one variant, the BAP configurations may be delivered, in accordance with Action 801 , to the mobile IAB-MT of the mobile IAB node via RRC from the old donor, either through an existing RRC message or a newly defined message.

The m-IAB-MT may receive, in accordance with Action 802, an indication for activation from the new donor via RRC, e.g., as a part of handover or conditional handover signaling, or after handover may have been completed.

In one variant, the BAP configurations may be provided, in accordance with Action 801 , to the mobile IAB-DU by the old donor via F1AP, either through an existing F1 procedure, e.g., gNB-Dll Configuration Update or gNB-CU Configuration Update, or a newly defined F1 procedure.

In one variant, the BAP configurations may be provided, in accordance with Action 801 , to the mobile IAB node by the CAM. In one variant, the m-IAB-MT may receive, in accordance with Action 802, an indication for activation from the new parent, which may have previously received it from the new donor, whereas the indication may be conveyed inside a DCI or a MAC CE. The indication may be implicit or explicit, e.g., an index assigned to the configuration that may have to be activated. The indication may e.g., be received after the m-IAB-MT may establish an RRC connection to the new donor, or during this establishment.

The mobile IAB may be instructed, in accordance with Action 802, to activate the BAP configuration.

In one variant, the BAP configuration may be activated when the mobile IAB-MT may execute a handover to the target cell if it is indicated that the said BAP configuration may have to be applied for the said target cell.

In one variant, the mobile IAB node may be instructed, in accordance with Action 803, to store the previous BAP configuration after the application of a new configuration.

In one variant, which BAP configuration, among the ones stored, may have to be activated may be indicated, in accordance with Action 802, explicitly through an activation command as part of the handover command to the target cell. In this example, each BAP configuration may be associated to a BAP configuration ID, and the activation command may convey the BAP configuration ID of the BAP configuration to be activated.

In one variant, the BAP configuration may be activated, in accordance with Action 806, with the mobile IAB-MT fulfil one of the criteria configured for that BAP mapping configuration. The mobile IAB-DU may activate the BAP configuration as instructed in accordance with Action 802.

Once that a BAP configuration may be activated, e.g., when a previously used configuration may be superseded by a newly activated BAP configuration, the mobile IAB node may perform at least one of the following actions, in accordance with Action 807.

The previous BAP mapping configuration may be deleted from the list while other BAP configurations may be kept.

The previous BAP configuration used may be still kept in the list of previously configured BAP configurations.

When one of the BAP configurations is used, all the others previous BAP configurations may be deleted.

Figure 11 is a signalling diagram according to embodiments herein, wherein the first node 130 is an mlAB, with an MT 1101 and a DU 1101. Each source donor, such as the first network node 101 , may, according to Action 904, Action 906, Action 801 and Action 803, provide the BAP configuration that the mobile IAB Node may need to store. At 1103, the mlAB-MT 1101 may provide the one or more first indications to the mlAB-DU. Next, the source donor may also, according to Action 904, Action 906, provide, and ask to store the one or more first configurations to the first radio network node 111. When at 1104 there may be change of parent I AB node, change of source donor etc; the UE may need to use another stored configuration that may be valid for that cell. The configuration may be stored, in accordance with Action 804, in the mobile IAB MT 1101 and as the IAB MT 1101 may perform handover and may select a new cell, it may provide the corresponding index at 1105 to the mobile IAB DU 1102 to activate the configuration pertaining to that index. Once the handover may have been completed, the mlAB-MT 1101 may send an RRC Conditional Handover (CHO) Complete to the respective second network node 102, the target donor, at 1106. The mlAB-DU may then, according to Action 806, switch to the stored BAP configuration based on the new cell/ or new IAB donor.

Figure 12 is a signalling diagram depicting an example of newly defined procedure for storing the conditional BAP configuration, referred to herein also as Figure 6.2.1 : A. The first network node 101 , according to Action 801 , may send a BAP mapping configuration for mobile IAB to the first node 130, here, an m-IAB, which may receive it according to Action 801. The BAP configuration provided/received in Action 904/Action 801 may be as shown in Table 1.

Figure 13 is a signalling diagram illustrating an example of a newly defined procedure for activating a first configuration, here, the conditional BAP configuration. In this example, the steps start when a handover request is received at 1301 by the new donor, the respective second network node 102, from the old donor, the first network node 101. This may instead of handover also be a new early warning message from the current donor, the first network node

101 , to a potential new donor, the respective second network node 102, that a mobile IAB such as the first node 130, may be approaching towards the area controlled by the new Donor. This part is further explained also in the Section entitled “Obtaining the BAP configurations from future serving donor CUs”. The information from the current source to the new source may be include the potential cell ID lists or measurement report that may guide the new donor to know which cell the mobile IAB-MT may connect to. Based upon input from the above step, and once the mobile IAB may attach to the new parent, the respective second network node

102, the new donor may send, according to Action 902, an activation command for activating the stored BAP configuration to the ancestor node 1302, which may activate the BH channel, BAP address and BAP path to route traffic to/from the mobile IAB node. New ancestors may also receive an update of their own backhaul routing configs. The activation command for activating the stored BAP configuration may reach the new parent node, the respective second radio network node 112, in accordance with Action 1002. Similar to the activation step, a deactivation step may be followed in the old Donor IAB node, where the old ancestors may receive a release message for the configurations.

Figure 14 is a schematic diagram depicting an example of the control PDU, e.g., BAP control PDU, or a data PDU, wherein the one or more second indications may be comprised in. As described in Action 802, the PDU may comprise, in the first octate (Oct), a Data or Control field (D/C) field 1401 , the PDU type field 1402, the fifth indication as the “A/D” field 1403, and two reserved fields “R” 1406, 1407. In the second Oct is the seventh indication as the Destination field 1408, and a path field 1409. The path field 1409 may be understood to denote which path to select for transmission in case there may exist multiple paths to the destination. The third Oct is occupied by the sixth indication as the M-IAB-ID field 1410.

Certain embodiments disclosed herein may provide one or more of the following technical advantage(s), which may be summarized as follows.

Figure 15 depicts two different examples in panels a) and b), respectively, of the arrangement that the first node 130 may comprise. In some embodiments, the first node 130 may comprise the following arrangement depicted in Figure 15a. The first node 130 is configured to operate in the communications network 100. The first node 130 is configured to be served by the first network node 101. The first node 130 may be understood to be for handling the configuration of the first node 130.

Several embodiments are comprised herein. It should be noted that the examples herein are not mutually exclusive. One or more embodiments may be combined, where applicable. All possible combinations are not described to simplify the description. Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments. The detailed description of some of the following corresponds to the same references provided above, in relation to the actions described for the first node 130 and will thus not be repeated here to simplify the description. For example, in some examples the one or more first indications may be configured to be the same as the one or more second indications, or may be configured to be comprised in the same message.

In Figure 15, optional units are indicated with dashed boxes.

The first node 130 is configured to perform the receiving in Action 801 , e.g. by means of a receiving unit 1501 within the first node 130, configured to receive, from the network node 101 , 102, 140, the one or more first indications. The one or more first indications are configured to respectively indicate the one or more first configurations to be applied by the first node 130 upon fulfilment of the one or more respective first criteria. The first node 130 is configured to be provided the wired connection to the core network node 140 of the communications network 100 by the first network node 101 via at least the wireless connection, and the first node 130 is configured to be capable to be provided the respective wired connection to the core network node 140 of the communications network 100 by the respective second network node 102 via at least the another respective wireless connection.

The first node 130 is also configured to perform the storing in Action 804, e.g. by means of a storing unit 1502 within the first node 130, configured to store the one or more first configurations at the first node 130.

The first node 130 is also configured to perform the applying of Action 806, e.g. by means of an applying unit 1503 within the first node 130, configured to apply, out of the stored one or more first configurations, the respective first configuration upon fulfilment of the one or more respective first criteria. The receiving is configured to comprise receiving the plurality of first configurations configured to comprise the respective first configuration. The storing is configured to comprise storing the plurality of first configurations and the applying is configured to comprise applying the respective first configuration out of the stored plurality of first configurations. Each of the one or more first configurations is configured to be a BAP configuration.

In some embodiments, at least one of the following may apply: a)the first node 130 may be configured to be the first IAB node. The first network node 101 may be configured to be a Donor CU, and the respective second network node 102 may be configured to be a second Donor CU, b) the one or more first indications may be configured to originate at the core network node 140, the core network node 140 being configured to be an CAM node, c) the first node 130 may be configured to be a mobile IAB node, d) the first node 130 may be configured to be a node with no descendants, e) the applying may be configured to be performed during the movement of the first node 130 along the route 170, f) the first node 130 may be configured to be served by the first network node 101 through at least one first radio network node 111 , the first radio network node 111 being configured to have respective wireless connections with the first node 130 and the first network node 101, g) the first radio network node 111 may be configured to be a source ancestor IAB node, h) the first node 130 may be to be served by the respective second network node 102 through the at least one respective second radio network node 112, the respective second radio network node 112 being configured to have the other respective wireless connections with the first node 130 and the respective second network node 102, i) each of the one or more first configurations may be configured to be a respective BH RLC channel configuration, used to configure the respective RLC entity, j) the respective second radio network node 112 may be configured to be a respective target ancestor I AB node, k) the respective second radio network node 112 may be configured to be a respective target parent IAB node, I) the one or more first configurations may be configured to be identified by the respective identifier, m) the respective identifier may be configured to be the newly defined identifier, n) the one or more first indications may be configured to be one of: i) received in the standalone message, ii) comprising the one or more respective first criteria upon the fulfilment of which the respective first configuration may be to be activated, iii) the one or more enhanced messages, o) the one or more respective first criteria may be configured to comprise at least one of: i) the first node 130 identifying, the respective cell 122, configured to be indicated in the respective first configuration, ii) the first node 130 entering the geographical area, configured to be indicated in the respective first configuration, and iii) the first node 130 establishing a connection, to the respective second network node 102, and p) the first node 130 may be configured to receive the further indication from the first network node 101 , the further indication being configured to indicate the order in which the plurality of respective second network nodes 110 configured comprise the respective second network node 102, and/or a plurality of second radio network nodes 112 configured to comprise the respective second radio network node 112, may be to serve the first node 130.

In some embodiments, each of the one or more first configurations may be configured to comprise at least one of: a) the respective BAP configuration configured to comprise respective at least one of: i) the one or more BAP addresses for the first node 130, ii) the one or more DL and UL BAP routing IDs for the first node 130, iii) the one or more second configurations for backhaul mapping of UL traffic configured to originate at the first node 130 or the one or more devices 150 configured to be served by the first node 130, iv) the BAP routing configuration, and v) the one or more third configurations for BAP header rewriting, and vi) the one or more fourth configurations for UL and/or DL local rerouting of traffic, and b) the respective BH RLC channel configuration, configured to be used to configure the respective RLC entity.

In some embodiments, the first node 130 may be configured to perform the receiving of Action 802, e.g. by means of the receiving unit 1501 within the first node 130 configured to receive, from the network node 101, 102, 140, the one or more second indications, the one or more second indications being configured to indicate to activate the respective first configuration.

In some embodiments, wherein the first node 130 may be configured to be served by the first network node 101 with the fifth configuration, the first node 130 may be further configured to perform the receiving of Action 803, e.g. by means of the receiving unit 1501 within the first node 130, configured to receive, from the network node 101, 102, 140, the one or more third indications. The one or more third indications may be configured to indicate to store at least one of the one or more first configurations and the one or more second indications, until application of the respective first configuration.

In some embodiments, wherein the first node 130 may be configured to be served by the first network node 101 with the fifth configuration, the first node 130 may be further configured to perform the receiving of Action 805, e.g. by means of the receiving unit 1501 within the first node 130, configured to receive, from the network node 101, 102, 140, the fourth indication. The fourth indication may be configured to indicate that the fifth configuration is no longer valid.

In some embodiments, at least one of the following may apply: a) at least one of the one or more first indications and the one or more second indications may be configured to be received during the procedure of setting up the F1 connection, b) the one or more first indications may be configured to be received together with the conditional F1 setup message, c) the receiving may be configured to comprise receiving the plurality of configurations comprising the first configuration, each configuration in the plurality being configured to comprise the respective identifier, d) at least one of the one or more first indications and the one or more second indications may be configured to be comprised in an RRC message, e) at least one of the one or more first indications and the one or more second indications may be configured to be received via F1AP, f) at least one of the one or more first indications and the one or more second indications may be configured to be received via DC I , or via a MAC CE, g) the one or more respective first criteria may be configured to comprise at least one of: i) executing the handover to the respective cell 122, and ii) the first node 130 establishing a connection, to the respective second network node 102, h) the one or more second indications may be configured to be received as part of, or together with, the handover command to the respective cell 122, and i) the one or more second indications may be configured to be respectively comprised in the control PDU.

In some embodiments, the PDU may be configured to comprise at least one of: i) the fifth indication configured to indicate the activation or deactivation flag of the respective first configuration, ii) the sixth indication configured to identify the respective first configuration, and iii) the seventh indication configured to indicate the final destination of the first node 130 when served by the respective second network node 102.

In some embodiments, wherein the first node 130 may be configured to be served by the first network node 101 with the fifth configuration, the first node 130 may be further configured to, after activating the respective first configuration, perform the performing of Action 807, e.g. by means of a performing unit 1504 within the first node 130, configured to perform the action on the fifth configuration configured to be selected from: i) deleting the fifth configuration and keeping other previous BAP configurations and/or BH RLC channel configurations, ii) deactivating the fifth configuration, iii) keeping the fifth configuration in the list of previous BAP configurations and/or BH RLC channel configurations, and iv) deleting the fifth configuration and any other previous BAP configurations and/or BH RLC channel configurations.

Other units 1505 may be comprised in the first node 130.

The embodiments herein in the first node 130 may be implemented through one or more processors, such as a processor 1506 in the first node 130 depicted in Figure 15a, together with computer program code for performing the functions and actions of the embodiments herein. A processor, as used herein, may be understood to be a hardware component. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the first node 130. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the first node 130.

The first node 130 may further comprise a memory 1507 comprising one or more memory units. The memory 1507 is arranged to be used to store obtained information, store data, configurations, schedulings, and applications etc. to perform the methods herein when being executed in the first node 130.

In some embodiments, the first node 130 may receive information from, e.g., the first network node 101 , the one or more second network nodes 110, the respective second network node 102, the third network node 103, the first radio network node 111 , the one or more second radio network nodes 112, e.g., the respective second radio network node 112, the one or more devices 150, the host computer 2210 described later, and/or any of the other nodes or devices, through a receiving port 1508. In some embodiments, the receiving port 1508 may be, for example, connected to one or more antennas in first node 130. In other embodiments, the first node 130 may receive information from another structure in the communications network 100 through the receiving port 1508. Since the receiving port 1508 may be in communication with the processor 1506, the receiving port 1508 may then send the received information to the processor 1506. The receiving port 1508 may also be configured to receive other information.

The processor 1506 in the first node 130 may be further configured to transmit or send information to e.g., the first network node 101 , the one or more second network nodes 110, the respective second network node 102, the third network node 103, the first radio network node 111 , the one or more second radio network nodes 112, e.g., the respective second radio network node 112, the one or more devices 150, the host computer 2210, and/or any of the other nodes or devices, or another structure in the communications network 100, through a sending port 1509, which may be in communication with the processor 1506, and the memory 1507.

Those skilled in the art will also appreciate that the units 1501-1505 described above may refer to a combination of analog and digital circuits, and/or one or more processors configured with software and/or firmware, e.g., stored in memory, that, when executed by the one or more processors such as the processor 1506, perform as described above. One or more of these processors, as well as the other digital hardware, may be included in a single Application-Specific Integrated Circuit (ASIC), or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a System-on-a-Chip (SoC).

Also, in some embodiments, the different units 1501-1505 described above may be a processor 1506 of the first node 130, or may be implemented as one or more applications running on one or more processors such as the processor 1506.

Thus, the methods according to the embodiments described herein for the first node 130 may be respectively implemented by means of a computer program 1510 product, comprising instructions, i.e., software code portions, which, when executed on at least one processor 1506, cause the at least one processor 1506 to carry out the actions described herein, as performed by the first node 130. The computer program 1510 product may be stored on a computer-readable storage medium 1511. The computer-readable storage medium 1511, having stored thereon the computer program 1510, may comprise instructions which, when executed on at least one processor 1506, cause the at least one processor 1506 to carry out the actions described herein, as performed by the first node 130. In some embodiments, the computer-readable storage medium 1511 may be a non-transitory computer-readable storage medium, such as a CD ROM disc, or a memory stick. In other embodiments, the computer program 1510 product may be stored on a carrier containing the computer program 1510 just described, wherein the carrier is one of an electronic signal, optical signal, radio signal, or the computer-readable storage medium 1511 , as described above.

The first node 130 may comprise a communication interface configured to facilitate communications between the first node 130 and other nodes or devices, e.g., the first network node 101, the one or more second network nodes 110, the respective second network node 102, the third network node 103, the first radio network node 111, the one or more second radio network nodes 112, e.g., the respective second radio network node 112, the one or more devices 150, the host computer 2210, and/or any of the other nodes or devices. The interface may, for example, include a transceiver configured to transmit and receive radio signals over an air interface in accordance with a suitable standard.

In other embodiments, the first node 130 may comprise the following arrangement depicted in Figure 15b. The first node 130 may comprise a processing circuitry 1506, e.g., one or more processors such as the processor 1506, in the first node 130 and the memory 1507. The first node 130 may also comprise a radio circuitry 1512, which may comprise e.g., the receiving port 1508 and the sending port 1509. The processing circuitry 1506 may be configured to, or operable to, perform the method actions according to Figure 8, Figures 11-14 and/or Figures 22-26, in a similar manner as that described in relation to Figure 15a. The radio circuitry 1512 may be configured to set up and maintain at least a wireless connection with any of the first network node 101, the one or more second network nodes 110, the respective second network node 102, the third network node 103, the first radio network node 111 , the one or more second radio network nodes 112, e.g., the respective second radio network node 112, the one or more devices 150, the host computer 2210, and/or any of the other nodes or devices. Circuitry may be understood herein as a hardware component.

Hence, embodiments herein also relate to the first node 130 operative to operate in the communications network 100. The first node 130 may comprise the processing circuitry 1506 and the memory 1507, said memory 1507 containing instructions executable by said processing circuitry 1506, whereby the first node 130 is further operative to perform the actions described herein in relation to the first node 130, e.g., in Figure 8, Figures 11-14 and/or Figures 22-26.

Figure 16 depicts two different examples in panels a) and b), respectively, of the arrangement that the network node 101 , 102, 140 may comprise. In some embodiments, the network node 101 , 102, 140 may comprise the following arrangement depicted in Figure 16a. The network node 101, 102, 140 is configured to operate in the communications network 100. The network node 101, 102, 140 may be understood to be for handling the configuration of the first node 130.

Several embodiments are comprised herein. Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments. The detailed description of some of the following corresponds to the same references provided above, in relation to the actions described for the first node 130, and will thus not be repeated here. For example, in some examples the one or more first indications may be configured to be the same as the one or more second indications, or may be configured to be comprised in the same message.

In Figure 16, optional units are indicated with dashed boxes.

The network node 101, 102, 140 may be configured to perform the sending of Action 904 action, e.g. by means of a sending unit 1601 within the network node 101, 102, 140, configured to send the one or more first indications to at least one of: i) the first node 130 configured to be served by the first network node 101 and ii) the at least one first radio network node 111, wherein the first node 130 is configured to be served by the first network node 101 through the at least one first radio network node 111. The at least one first radio network node 111 is configured to have the respective wireless connections with the first node 130 and the first network node 101. The one or more first indications are configured to indicate the one or more first configurations to be applied by the first node 130 upon fulfilment of the one or more respective first criteria. The first node 130 is configured to be provided the wired connection to the core network node 140 of the communications network 100 by the first network node 101 via at least the wireless connection. The first node 130 is configured to be capable to be provided the respective wired connection to the core network node 140 of the communications network 100 by the respective second network node 102 via the at least another respective wireless connection. The sending is configured to comprise sending the plurality of first configurations configured to comprise the respective first configuration to be applied by the first node 130 upon fulfilment of the respective one or more first criteria. Each of the one or more first configurations is configured to be a BAP configuration.

In some embodiments, at least one of the following may apply: a) the first node 130 may be configured to be the first IAB node. The first network node 101 may be configured to be a Donor CU, and the respective second network node 102 may be configured to be a second Donor CU, b) each of the at least one first radio network node 111 may be configured to be an ancestor node, c) the one or more first indications may be configured to originate at the core network node 140, the core network node 140 being configured to be an CAM node, d) the first node 130 may be configured to be a mobile IAB node, e) the first node 130 may be configured to be a node with no descendants, f) the sending may be configured to be performed during the movement of the first node 130 along the route 170, g) the first radio network node 111 may be configured to be a source ancestor IAB node, h) the first node 130 may be to be served by the respective second network node 102 through the at least one respective second radio network node 112, the respective second radio network node 112 being configured to have the other respective wireless connections with the first node 130 and the respective second network node 102, i) each of the one or more first configurations may be configured to be a respective BH RLC channel configuration, used to configure the respective RLC entity, j) the respective second radio network node 112 may be configured to be a respective target ancestor IAB node, k) the respective second radio network node 112 may be configured to be a respective target parent IAB node, I) the one or more first configurations may be configured to be identified by the respective identifier, m) the respective identifier may be configured to be the newly defined identifier, n) the one or more first indications may be configured to be one of: i) received in the standalone message, ii) comprising the one or more respective first criteria upon the fulfilment of which the respective first configuration may be to be activated, iii) the one or more enhanced messages, o) the one or more respective first criteria may be configured to comprise at least one of: i) the first node 130 identifying, the respective cell 122, configured to be indicated in the respective first configuration, ii) the first node 130 entering the geographical area, configured to be indicated in the respective first configuration, and iii) the first node 130 establishing a connection, to the respective second network node 102, and p) the network node 101 , 102, 140 may be configured to send to the first node 130 the further indication from the first network node 101, the further indication being configured to indicate the order in which the plurality of respective second network nodes 110 configured to comprise the respective second network node 102 and/or the plurality of second radio network nodes 112 configured to comprising the respective second radio network node 112 may have to serve the first node 130.

In some embodiments, each of the one or more first configurations may be configured to comprise at least one of: a) the respective BAP configuration configured to comprise the respective at least one of: i) the one or more BAP addresses for the first node 130, ii) the one or more DL and UL BAP routing IDs for the first node 130, iii) the one or more second configurations for backhaul mapping of UL traffic configured to originate at the first node 130 or the one or more devices 150 configured to be served by the first node 130, iv) the BAP routing configuration, and v) the one or more third configurations for BAP header rewriting, and vi) the one or more fourth configurations for UL and/or DL local rerouting of traffic, and b) the respective BH RLC channel configuration, configured to be used to configure the respective RLC entity.

In some embodiments wherein the network node 101, 102, may be configured to be one of the first network node 101 and the respective second network node 102, and the first node 130 may be configured to be served by the first network node 101 with the fifth configuration, the network node 101 , 102, 140 may be configured to perform the sending of Action 905, e.g., by means of the sending unit 1601 , configured to send, to at least one of the first node 130 and the radio network node 111 , 112, the one or more second indications. The one or more second indications may be configured to indicate to activate the respective first configuration. In some embodiments wherein the network node 101, 102, may be configured to be one of the first network node 101 and the respective second network node 102, and the first node 130 may be configured to be served by the first network node 101 with the fifth configuration, the network node 101, 102, 140 may be configured to perform the sending of Action 906, e.g., by means of the sending unit 1601, configured to send, to at least one of the first node 130 and the radio network node 111, 112, the one or more third indications. The one or more third indications may be configured to indicate to store at least one of the one or more first configurations and the one or more second indications, until application of the respective first configuration.

In some embodiments wherein the network node 101 , 102, may be configured to be one of the first network node 101 and the respective second network node 102, and the first node 130 may be configured to be served by the first network node 101 with the fifth configuration, the network node 101, 102, 140 may be configured to perform the sending of Action 908, e.g., by means of the sending unit 1601, configured to send, to at least one of the first node 130 and the at least one first network node 111 , the fourth indication. The fourth indication may be configured to indicate that the fifth configuration is no longer valid.

In some embodiments, at least one of the following may apply: a) at least one of the one or more first indications and the one or more second indications may be configured to be sent during the procedure of setting up the F1 connection, b) the one or more first indications may be configured to be sent together with the conditional F1 setup message, c) the sending may be configured to comprise sending the plurality of configurations configured to comprise the first configuration, each configuration in the plurality being configured to comprise the respective identifier, d) at least one of the one or more first indications and the one or more second indications may be configured to be comprised in an RRC message, e) at least one of the one or more first indications and the one or more second indications may be configured to be received via F1AP, f) at least one of the one or more first indications and the one or more second indications may be configured to be received via DCI, or via a MAC CE, g) the one or more respective first criteria may be configured to comprise at least one of: i) executing the handover to the respective cell 122, and ii) the first node 130 establishing a connection, to the respective second network node 102, h) the one or more second indications may be configured to be received as part of, or together with, the handover command to the respective cell 122, and i) the one or more second indications may be configured to be respectively comprised in the control PDU.

In some embodiments wherein the network node 101 , 102, may be configured to be the first network node 101, and the first network node 101 may be configured to serve the first node 130 with the fifth configuration, the network node 101 , 102, 140 may be configured to, after activating the first configuration, perform the performing of Action 910, e.g., by means of a performing unit 1602 within the network node 101, 102, 140, configured to perform the action on the fifth configuration configured to be selected from: i) deleting the fifth configuration and keeping other previous BAP configurations and/or BH RLC channel configurations, ii) deactivating the fifth configuration, iii) keeping the fifth configuration in the list of previous BAP configurations and/or BH RLC channel configurations, and iv) deleting the fifth configuration and any other previous BAP configurations and/or BH RLC channel configurations.

The network node 101, 102, 140 may be configured to perform the obtaining of Action

902, e.g., by means of an obtaining unit 1603 within the network node 101, 102, 140, configured to obtain the one or more first configurations from at least one of: i) the one or more respective second network nodes 110 configured to comprise the respective second network node 102, wherein the one or more respective second network nodes 110 may be configured to have the capability to provide, to the first node 130, the respective wired connection to the core network node 140 of the communications network 100 via at least the respective wireless connection, and ii) the third network node 103 configured to manage configuration of nodes comprised in the communications network 100.

903, e.g., by means of the obtaining unit 1603 within the network node 101, 102, 140, configured to obtain, from at least one of the one or more respective second network nodes 110, the third network node 103 and the core network node 140, at least one of: i) the eighth indication configured to indicate the order in which the plurality of one or more respective second network nodes 110 and/or the plurality of second radio network nodes 112 configured to comprise the respective second radio network node 112 may have to serve the first node 130, and ii) the ninth indication configured to indicate the list of the one or more respective second network nodes 110 from which the first network node may have to request the respective first configuration of the one or more first configurations.

In some embodiments, at least one of the obtaining of the one or more first configurations and the obtaining of the at least one of the eighth indication and the ninth indication may be configured to be performed via one of: i) the one or more XnAP messages, and ii) by means of signalling traversing the core network 140 of the communications network 100. The network node 101 , 102, 140 may be configured to perform the sending of Action 901 , e.g. by means of the sending unit 1601 , configured to send the first message to the core network node 140. The message is configured to request at least one of the one or more first configurations. The obtaining of the one or more first configurations may be configured to be in response to the first message configured to be sent.

The network node 101 , 102, 140 may be configured to perform the storing of Action 907, e.g. by means of a storing unit 1604 within the network node 101 , 102, 140, configured to store the one or more first configurations.

The network node 101 , 102, 140 may be configured to perform the applying of Action 909, e.g. by means of an applying unit 1605 within the network node 101 , 102, 140, configured to apply the stored respective first configuration upon fulfilment of the one or more respective first criteria.

In some embodiments, at least one of the following may apply: i) the first message may be configured to be an NGAP message towards one or more AMFs, ii) the first message may be configured to comprise the tenth indication configured to indicate the quantification of current or predicted traffic load at the first node 130, and iii) the core network node 140 may be configured to be an OAM node, and iv) the first message may be configured to comprise information about the fifth configuration.

Other units 1606 may be comprised in the network node 101, 102, 140.

The embodiments herein in the network node 101 , 102, 140 may be implemented through one or more processors, such as a processor 1607 in the network node 101, 102, 140 depicted in Figure 16a, together with computer program code for performing the functions and actions of the embodiments herein. A processor, as used herein, may be understood to be a hardware component. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the network node 101, 102, 140. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the network node 101, 102, 140.

The network node 101 , 102, 140 may further comprise a memory 1608 comprising one or more memory units. The memory 1608 is arranged to be used to store obtained information, store data, configurations, schedulings, and applications etc. to perform the methods herein when being executed in the network node 101 , 102, 140.

In some embodiments, the network node 101 , 102, 140 may receive information from, e.g., the first node 130, the first network node 101, the one or more second network nodes 110, the respective second network node 102, the third network node 103, the first radio network node 111, the one or more second radio network nodes 112, e.g., the respective second radio network node 112, the one or more devices 150, the host computer 2210, and/or any of the other nodes or devices, through a receiving port 1609. In some embodiments, the receiving port 1609 may be, for example, connected to one or more antennas in the network node 101, 102, 140. In other embodiments, the network node 101 , 102, 140 may receive information from another structure in the communications network 100 through the receiving port 1609. Since the receiving port 1609 may be in communication with the processor 1607, the receiving port 1609 may then send the received information to the processor 1607. The receiving port 1609 may also be configured to receive other information.

The processor 1607 in the network node 101 , 102, 140 may be further configured to transmit or send information to e.g., the first node 130, the first network node 101, the one or more second network nodes 110, the respective second network node 102, the third network node 103, the first radio network node 111, the one or more second radio network nodes 112, e.g., the respective second radio network node 112, the one or more devices 150, the host computer 2210, and/or any of the other nodes or devices, or another structure in the communications network 100, through a sending port 1610, which may be in communication with the processor 1607, and the memory 1608.

Those skilled in the art will also appreciate that the units 1601-1606 described above may refer to a combination of analog and digital circuits, and/or one or more processors configured with software and/or firmware, e.g., stored in memory, that, when executed by the one or more processors such as the processor 1607, perform as described above. One or more of these processors, as well as the other digital hardware, may be included in a single Application-Specific Integrated Circuit (ASIC), or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a System-on-a-Chip (SoC).

Also, in some embodiments, the different units 1601-1606 described above implemented as a processor, such as the processor 1607, or as one or more applications running on one or more processors such as the processor 1607.

Thus, the methods according to the embodiments described herein for the network node 101 , 102, 140 may be respectively implemented by means of a computer program 1611 product, comprising instructions, i.e., software code portions, which, when executed on at least one processor 1607, cause the at least one processor 1607 to carry out the actions described herein, as performed by the network node 101 , 102, 140. The computer program 1611 product may be stored on a computer-readable storage medium 1612. The computer-readable storage medium 1612, having stored thereon the computer program 1611, may comprise instructions which, when executed on at least one processor 1607, cause the at least one processor 1607 to carry out the actions described herein, as performed by the network node 101 , 102, 140. In some embodiments, the computer-readable storage medium 1612 may be a non-transitory computer-readable storage medium, such as a CD ROM disc, or a memory stick. In other embodiments, the computer program 1611 product may be stored on a carrier containing the computer program 1611 just described, wherein the carrier is one of an electronic signal, optical signal, radio signal, or the computer-readable storage medium 1612, as described above.

The network node 101, 102, 140 may comprise a communication interface configured to facilitate communications between the network node 101 , 102, 140 and other nodes or devices, e.g., the first node 130, the first network node 101 , the one or more second network nodes 110, the respective second network node 102, the third network node 103, the first radio network node 111 , the one or more second radio network nodes 112, e.g., the respective second radio network node 112, the one or more devices 150, the host computer 2210, and/or any of the other nodes or devices. The interface may, for example, include a transceiver configured to transmit and receive radio signals over an air interface in accordance with a suitable standard.

In other embodiments, the network node 101, 102, 140 may comprise the following arrangement depicted in Figure 16b. The network node 101, 102, 140 may comprise a processing circuitry 1607, e.g., one or more processors such as the processor 1607, in the network node 101, 102, 140 and the memory 1608. The network node 101 , 102, 140 may also comprise a radio circuitry 1613, which may comprise e.g., the receiving port 1609 and the sending port 1610. The processing circuitry 1607 may be configured to, or operable to, perform the method actions according to Figure 9, Figures 11-14 and/or Figures 22-26, in a similar manner as that described in relation to Figure 16a. The radio circuitry 1613 may be configured to set up and maintain at least a wireless connection with the first node 130, the first network node 101 , the one or more second network nodes 110, the respective second network node 102, the third network node 103, the first radio network node 111, the one or more second radio network nodes 112, e.g., the respective second radio network node 112, the one or more devices 150, the host computer 2210, and/or any of the other nodes or devices. Circuitry may be understood herein as a hardware component.

Hence, embodiments herein also relate to the network node 101 , 102, 140 operative to operate in the communications network 100. The network node 101, 102, 140 may comprise the processing circuitry 1607 and the memory 1608, said memory 1608 containing instructions executable by said processing circuitry 1607, whereby the network node 101 , 102, 140 is further operative to perform the actions described herein in relation to the network node 101, 102, 140, e.g., in Figure 9, Figures 11-14 and/or Figures 22-26.

Figure 17 depicts two different examples in panels a) and b), respectively, of the arrangement that the radio network node 111, 112 may comprise. In some embodiments, the radio network node 111 , 112 may comprise the following arrangement depicted in Figure 17a. The radio network node 111, 112 is configured to operate in the communications network 100. The radio network node 111, 112 may be understood to be for handling the configuration of the first node 130. The first node 130 may be configured to be provided the wired connection to the core network node 140 of the communications network 100 by the first network node 101 via at least the wireless connection. The first node 130 may be configured to be capable to be provided the respective wired connection to the core network node 140 of the communications network 100 by the respective second network node 102 via the at least another respective wireless connection.

Several embodiments are comprised herein. Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments. The detailed description of some of the following corresponds to the same references provided above, in relation to the actions described for the first node 130, and will thus not be repeated here. For example, the BH RLC CH configuration may be understood to refer to a configuration to establish one or more BH RLC channels between a new parent DU and the first node 130.

In Figure 17, optional units are indicated with dashed boxes.

The radio network node 111, 112 may be configured to perform the receiving in Action 1002, e.g. by means of a receiving unit 1701 within the radio network node 111 , 112, configured to receive, from the network node 101, 102, 140, the indication, wherein one of the following may apply, i) With the proviso that the radio network node 111 , 112 is configured to be the first radio network node 111, wherein the first node 130 is configured to be served by the first network node 101 through at least the first radio network node 111 , the first radio network node 111 being configured to have the respective wireless connections with the first node 130 and the first network node 101, the indication is configured to be the fourth indication, wherein the fourth indication is configured to indicate that the fifth configuration with which the first network node 101 is configured to serve the first node 130 is no longer valid, ii) With the proviso the radio network node 111, 112 is configured to be the respective second radio network node 112, wherein the first node 130 is configured to be served by the respective second network node 102 through at least the respective second radio network node 112, the respective second radio network node 112 being configured to have the other respective wireless connections with the first node 130 and the respective second network node 102, the indication is configured to be the second indication, wherein the second indication is configured to indicate to activate the respective first configuration configured to be stored at the first radio network node 111.

The radio network node 111, 112 may be configured to perform the receiving of Action 1001, e.g. by means of the receiving unit 1701 within the radio network node 111 , 112, configured to receive , from the network node 101, 102, 140, the first indication. The first indication may be configured to indicate the respective first configuration to be applied by the first node 130 upon fulfilment of the one or more respective first criteria.

The radio network node 111, 112 may be configured to perform the storing of Action

1004, e.g. by means of a storing unit 1702 within the radio network node 111 , 112, configured to store the respective first configuration at the radio network node 111, 112.

The radio network node 111, 112 may be configured to perform the applying of Action

1005, e.g. by means of an applying unit 1703 within the radio network node 111 , 112, configured to apply the second or fourth indication immediately or upon fulfilment of the one or more respective first criteria.

In some embodiments, at least one of the following may apply: a) the respective first configuration may be configured to be a BAP configuration, b) the respective first configuration may be configured to be a respective BH RLC channel, configuration, used to configure the respective RLC entity, c) the first node 130 may be configured to be the first IAB node. The first network node 101 may be configured to be a Donor CU, and the respective second network node 102 may be configured to be a second Donor CU, d) the first indication may be configured to originate at the core network node 140, the core network node 140 being configured to be an CAM node, e the first node 130 may be configured to be a mobile IAB node, f) the first node 130 may be configured to be a node with no descendants, g) the applying may be configured to be performed during the movement of the first node 130 along the route 170, h) the first radio network node 111 may be configured to be a source ancestor IAB node, i) the first node 130 may be to be served by the respective second network node 102 through the at least one respective second radio network node 112, the respective second radio network node 112 being configured to have the other respective wireless connections with the first node 130 and the respective second network node 102, j) the respective second radio network node 112 may be configured to be a respective target ancestor IAB node, k) the respective second radio network node 112 may be configured to be a respective target parent IAB node, I) the first indication may be configured to be one of: i) received in the standalone message, ii) comprising the one or more respective first criteria upon the fulfilment of which the respective first configuration may be to be activated, iii) the enhanced message, and m) the one or more respective first criteria may be configured to comprise at least one of: i) the first node 130 identifying, the respective cell 122, ii) the first node 130 entering the geographical area, configured to be indicated in the respective first configuration, and iii) the first node 130 establishing the connection, to the respective second network node 102.

In some embodiments, the respective first configuration may be configured to comprise at least one of: a) the respective BAP configuration configured to comprise the respective at least one of: i) the one or more BAP addresses for the first node 130, ii) the one or more DL and UL BAP routing IDs for the first node 130, iii) the one or more second configurations for backhaul mapping of UL traffic configured to originate at the first node 130 or the one or more devices 150 configured to be served by the first node 130, iv) the BAP routing configuration, and v) the one or more third configurations for BAP header rewriting, and vi) the one or more fourth configurations for UL and/or DL local rerouting of traffic, and b) the respective BH RLC channel configuration, configured to be used to configure the respective RLC entity.

In some embodiments wherein the first node 130 may be configured to be served by the first network node 101 with the fifth configuration, the first node 130 may be configured to perform the receiving of Action 1003, e.g. by means of the receiving unit 1701 within the radio network node 111, 112, configured to receive, from the network node 101, 102, 140, the third indication. The third indication may be configured to indicate to store at least one of the respective first configuration and the second indication, until application of the respective first configuration.

In some embodiments, at least one of the following may apply: a) at least one of the first indication and the second indication may be configured to be received during the procedure of setting up the F1 connection, b) the first indication may be configured to be received together with the conditional F1 setup message, c) the receiving may be configured to comprise receiving the plurality of configurations configured to comprise the respective first configuration, each configuration in the plurality being configured to comprise the respective identifier, d) at least one of the first indications and the second indication may be configured to be comprised in an RRC message, e) at least one of the first indication and the second indication may be configured to be received via F1 AP, f) at least one of the one of first indication and the second indication may be configured to be received via DCI, or via a MAC CE, g) the one or more respective first criteria may be configured to comprise at least one of: i) the first node 130 executing the handover to the cell 122, and ii) the first node 130 establishing a connection, to the respective second network node 102, h) the second indication may be configured to be received as part of, or together with, the handover command to the cell 122, and i) the second indication may be configured to be comprised in the control PDU. In some embodiments, the PDU may be configured to comprise at least one of: i) the fifth indication configured to indicate the activation or deactivation flag of the respective first configuration, ii) the sixth indication configured to identify the respective first configuration, and iii) the seventh indication configured to indicate the final destination of the first node 130 when served by the respective second network node 102.

In some embodiments, wherein the first node 130 may be configured to be served by the first network node 101 with the fifth configuration, the radio network node 111, 112 may be configured to perform the performing of Action 1006, e.g. by means of a performing unit 1704 within the radio network node 111 , 112, configured to, after activating the respective first configuration, perform the action on the fifth configuration configured to be selected from: i) deleting the fifth configuration and keeping other previous BAP configurations and/or BH RLC channel configurations, ii) deactivating the fifth configuration, iii) keeping the fifth configuration in the list of previous BAP configurations and/or BH RLC channel configurations, and iv) deleting the fifth configuration and any other previous BAP configurations and/or BH RLC channel configurations.

In some embodiments, wherein the respective second radio network node 112 may have to directly serve the first node 130 as a new parent, the second indication may be configured to be the existing F1AP UE CONTEXT SETUP REQUEST message with the particular, identifier pair, wherein the identifier pair may be configured to have been previously associated to the BAP routing configuration.

In some embodiments, the second indication is configured to activate a respective BH RLC channel configuration at the respective second radio network node 112.

Other units 1705 may be comprised in the first node 130.

The embodiments herein in the radio network node 111, 112 may be implemented through one or more processors, such as a processor 1706 in the radio network node 111, 112 depicted in Figure 17a, together with computer program code for performing the functions and actions of the embodiments herein. A processor, as used herein, may be understood to be a hardware component. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the radio network node 111, 112. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the radio network node 111, 112.

The radio network node 111 , 112 may further comprise a memory 1707 comprising one or more memory units. The memory 1707 is arranged to be used to store obtained information, store data, configurations, schedulings, and applications etc. to perform the methods herein when being executed in the radio network node 111, 112.

In some embodiments, the radio network node 111 , 112 may receive information from, e.g., the first node 130, the first network node 101, the one or more second network nodes 110, the respective second network node 102, the third network node 103, the first radio network node 111, the one or more second radio network nodes 112, e.g., the respective second radio network node 112, the one or more devices 150, the host computer 2210, and/or any of the other nodes or devices, through a receiving port 1708. In some embodiments, the receiving port 1708 may be, for example, connected to one or more antennas in radio network node 111, 112. In other embodiments, the radio network node 111 , 112 may receive information from another structure in the communications network 100 through the receiving port 1708. Since the receiving port 1708 may be in communication with the processor 1706, the receiving port 1708 may then send the received information to the processor 1706. The receiving port 1708 may also be configured to receive other information.

The processor 1706 in the radio network node 111 , 112 may be further configured to transmit or send information to e.g., the first node 130, the first network node 101, the one or more second network nodes 110, the respective second network node 102, the third network node 103, the first radio network node 111 , the one or more second radio network nodes 112, e.g., the respective second radio network node 112, the one or more devices 150, the host computer 2210, and/or any of the other nodes or devices, or another structure in the communications network 100, through a sending port 1709, which may be in communication with the processor 1706, and the memory 1707.

Those skilled in the art will also appreciate that the units 1701-1705 described above may refer to a combination of analog and digital circuits, and/or one or more processors configured with software and/or firmware, e.g., stored in memory, that, when executed by the one or more processors such as the processor 1706, perform as described above. One or more of these processors, as well as the other digital hardware, may be included in a single Application-Specific Integrated Circuit (ASIC), or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a System-on-a-Chip (SoC).

Also, in some embodiments, the different units 1701-1705 described above may be a processor 1706 of the radio network node 111, 112, or may be implemented as one or more applications running on one or more processors such as the processor 1706.

Thus, the methods according to the embodiments described herein for the radio network node 111, 112 may be respectively implemented by means of a computer program 1710 product, comprising instructions, i.e., software code portions, which, when executed on at least one processor 1706, cause the at least one processor 1706 to carry out the actions described herein, as performed by the radio network node 111, 112. The computer program 1710 product may be stored on a computer-readable storage medium 1711. The computer- readable storage medium 1711 , having stored thereon the computer program 1710, may comprise instructions which, when executed on at least one processor 1706, cause the at least one processor 1706 to carry out the actions described herein, as performed by the radio network node 111, 112. In some embodiments, the computer-readable storage medium 1711 may be a non-transitory computer-readable storage medium, such as a CD ROM disc, or a memory stick. In other embodiments, the computer program 1710 product may be stored on a carrier containing the computer program 1710 just described, wherein the carrier is one of an electronic signal, optical signal, radio signal, or the computer-readable storage medium 1711, as described above.

The radio network node 111 , 112 may comprise a communication interface configured to facilitate communications between the radio network node 111 , 112 and other nodes or devices, e.g., the first node 130, the first network node 101 , the one or more second network nodes 110, the respective second network node 102, the third network node 103, the first radio network node 111 , the one or more second radio network nodes 112, e.g., the respective second radio network node 112, the one or more devices 150, the host computer 2210, and/or any of the other nodes or devices. The interface may, for example, include a transceiver configured to transmit and receive radio signals over an air interface in accordance with a suitable standard.

In other embodiments, the radio network node 111, 112 may comprise the following arrangement depicted in Figure 17b. The radio network node 111, 112 may comprise a processing circuitry 1706, e.g., one or more processors such as the processor 1706, in the radio network node 111, 112 and the memory 1707. The radio network node 111 , 112 may also comprise a radio circuitry 1712, which may comprise e.g., the receiving port 1708 and the sending port 1709. The processing circuitry 1706 may be configured to, or operable to, perform the method actions according to Figure 10, Figures 11-14 and/or Figures 22-26, in a similar manner as that described in relation to Figure 17a. The radio circuitry 1712 may be configured to set up and maintain at least a wireless connection with any of the first node 130, the first network node 101, the one or more second network nodes 110, the respective second network node 102, the third network node 103, the first radio network node 111, the one or more second radio network nodes 112, e.g., the respective second radio network node 112, the one or more devices 150, the host computer 2210, and/or any of the other nodes or devices. Circuitry may be understood herein as a hardware component. Hence, embodiments herein also relate to the radio network node 111 , 112 operative to operate in the communications network 100. The radio network node 111, 112 may comprise the processing circuitry 1706 and the memory 1707, said memory 1707 containing instructions executable by said processing circuitry 1706, whereby the radio network node 111, 112 is further operative to perform the actions described herein in relation to the radio network node 111 , 112, e.g., in Figure 10, Figures 11-14 and/or Figures 22-26.

As used herein, the expression “at least one of:” followed by a list of alternatives separated by commas, and wherein the last alternative is preceded by the “and” term, may be understood to mean that only one of the list of alternatives may apply, more than one of the list of alternatives may apply or all of the list of alternatives may apply. This expression may be understood to be equivalent to the expression “at least one of:” followed by a list of alternatives separated by commas, and wherein the last alternative is preceded by the “or” term.

When using the word "comprise" or “comprising” it shall be interpreted as non- limiting, i.e. meaning "consist at least of".

A processor may be understood herein as a hardware component.

The embodiments herein are not limited to the above described preferred embodiments. Various alternatives, modifications and equivalents may be used. Therefore, the above embodiments should not be taken as limiting the scope of the invention.

Examples related to embodiments herein:

The first node 130 embodiments relate to Figure 18, Figures 11-14, Figure 15 and Figures 21-26.

A method, performed by a node, such as the first node 130 is described herein. The first node 130 may operate in the communications network 100. The first node 130 may be served by the first network node 101. The method may be understood to be for handling configuration of the first node 130.

The communications network 100 may be a multi-hop deployment. In some embodiments, the communications network 100 may be an Integrated Access Backhaul (IAB) network.

The method may comprise one or more of the following actions.

In some embodiments all the actions may be performed. In other embodiments, one or more actions may be performed. One or more embodiments may be combined, where applicable. All possible combinations are not described to simplify the description. Some actions may be performed in a different order than that shown in Figure 18. In Figure 18, actions which may be optional in some examples are depicted with dashed boxes. o Receiving 801 one or more first indications. The first node 130 may be configured to perform the receiving in this Action 801 action, e.g. by means of a receiving unit 1501 within the first node 130, configured to perform this action.

The first node 130 may receive the one or more first indications from the network node

101 , 102, 140.

The one or more first indications may respectively indicate one or more first configurations to be applied by the first node 130.

The one or more first indications may respectively indicate one or more first configurations to be applied by the first node 130 upon fulfilment of one or more respective first criteria, e.g., connection to a respective cell 122 served by a respective second network node

102, connection to a respective second network node 102, out of the one or more second network nodes 110, etc...

The first node 130 may be provided a wired connection, e.g., the sixth link 166, to the core network node 140 of the communications network 100 by the first network node 101 via at least a wireless connection, e.g., the second link 162 or the third link 163.

The first node 130 may be capable to be provided a wired connection, e.g., the respective seventh link 167, to the core network node 140 of the communications network 100 by the respective second network node 102 via at least another respective wireless connection, e.g., the respective fifth link 165.

The one or more first configurations may be identified by a respective identifier. The respective identifier may be, e.g., of the respective cell 122, or of the respective second network node 102.

In some embodiments, the method may comprise one or more of the following actions: o Storing 804 the one or more first configurations at the first node 130.

The first node 130 may be configured to perform the storing of this Action 804, e.g. by means of a storing unit 1502 within the first node 130, configured to perform this action.

The one or more first configurations may be stored, e.g., along with the respective identifier. o Applying 806, out of the stored one or more first configurations, a respective first configuration. The first node 130 may be configured to perform the applying of this Action 806, e.g. by means of an applying unit 1503 within the first node 130, configured to perform this action. The applying, out of the stored one or more first configurations, of the respective first configuration may be performed upon fulfilment of the respective one or more first criteria, e.g., connection to the respective second network node 102 and/or the respective cell 122.

In some embodiments, at least one of the following may apply:

- each of the one or more first configurations may be a Backhaul Adaptation Protocol (BAP) configuration,

- the first node 130 may be a first Integrated Access and Backhaul (IAB) node, the first network node 101 may be a Donor Centralized Unit, CU, and the respective second network node 102 may be a second Donor CU,

- the one or more first indications may originate at the core network node 140, the core network node 140 being an CAM node,

- the first node 130 may be a mobile IAB node (mlAB node),

- the first node 130 may be a node, e.g., an IAB node, with no descendants,

- the applying of Action 806 may be performed during a movement of the first node 130 along the route 170, e.g., a fixed route,

- the first node 130 may be served by the first network node 101 through at least the one first radio network node 111 , that is there may be more than one ancestor node; the first radio network node 111 may have respective wireless connections with the first node 130 and the first network node 101,

- the first radio network node 111 may be a source ancestor IAB node,

- the first node 130 may be to be served by the second network node 102 through at least one respective second radio network node 112, the respective second radio network node 112 having other respective wireless connections with the first node 130 and the second network node 102,

- each of the one or more first configurations may be a respective BH RLC channel, configuration, used to configure an RLC entity, e.g., a corresponding logical channel in Medium Access Control (MAC) for BH RLC channel between lAB-node, e.g., the first node 130 and its respective parent node, e.g., the respective second radio network node 112,

- the respective second radio network node 112 may be a respective target ancestor IAB node,

- the respective second radio network node 112 may be a respective target parent IAB node,

- the respective identifier may be a newly defined identifier,

- the one or more first indications may be one of: i. received in a standalone message, ii. comprising the one or more respective first criteria upon the fulfilment of which the respective first configuration may have to be activated, iii. one or more enhanced messages, e.g., one or more enhanced existing messages,

- the one or more respective first criteria may comprise at least one of: i. the first node 130 identifying , e.g., and connecting to, the respective cell 122, e.g., via PCI, and/or CGI, indicated in the respective first configuration, ii. the first node 130 entering a geographical area, e.g., a group of cells or a TA, indicated in the respective first configuration, e.g., within the same donor CU, and iii. the first node 130 establishing a connection, e.g., an F1 connection, to the respective second network node 102, e.g., a new donor CU, e.g., identified by for example, another respective identifier, e.g., gNB-CU name, and

- the first node 130 may receive a further indication, e.g., referred to later as the eighth indication, from the first network node 101 ; the further indication may indicate an order in which a plurality of respective second network nodes 110, that is, the one or more second network nodes 110, comprising the respective second network node 102, and/or a plurality of second radio network nodes 112 comprising the second radio network node 112, may have to serve the first node 130.

Each of the one or more first configurations may comprise at least one of:

- a respective BAP configuration comprising respective at least one of: i. one or more BAP addresses, for the first node 130, ii. one or more downlink (DL) and uplink (UL) BAP routing identifiers (IDs), for the first node 130, iii. one or more second configurations for backhaul mapping of UL traffic originating at the first node 130 or one or more devices 150 served by the first node 130, iv. a BAP routing configuration, v. one or more third configurations for BAP header rewriting, and

- one or more fourth configurations for UL and/or DL local rerouting of traffic, and the respective BH RLC channel configuration, used to configure the respective RLC entity, e.g., a corresponding logical channel in MAC for BH RLC channel between lAB-node, e.g., the first node 130 and its parent node, e.g., the respective second radio network node 112.

A BH RLC channel configuration as be a described in existing specifications, reproduced next:

"BH-RLC-ChannelConfig

The IE BH-RLC-ChannelConfig is used to configure an RLC entity, a corresponding logical channel in MAC for BH RLC channel between lAB-node and its parent node.

BH-RLC-ChannelConfig information element - ASN1 START

- TAG-BHRLCCHANNELCONFIG-START

BH-RLC-ChannelConfig-r16::= SEQUENCE { bh-LogicalChannelldentity-r16 BH-LogicalChannelldentity-r16 OPTIONAL, -- Cond LCH-SetupOnly bh-RLC-ChannellD-r16 BH-RLC-ChannellD-r16, reestablishRLC-r16 ENUMERATED {true} OPTIONAL, - Need N rlc-Config-r16 RLC-Config OPTIONAL, — Cond LCH-Setup mac-LogicalChannelConfig-r16 LogicalChannelConfig OPTIONAL, -- Cond LCH-Setup

- TAG-BHRLCCHANNELCONFIG-STOP

- ASN1 STOP"

In some embodiments, the method may comprise one or more of the following actions: o Receiving 802 one or more second indications. The first node 130 may be configured to perform the receiving of this Action 802, e.g. by means of the receiving unit 1501 within the first node 130, configured to perform this action.

The one or more second indications may be received from the network node 101, 102, 140.

The one or more second indications may be received e.g., together or separate from the one or more first indications. In some examples the one or more first indications may be the same as the one or more second indications, or may be comprised in a same message. Each of the one or more second indications may respectively indicate to activate the respective first configuration, e.g., immediately or upon fulfilment of the one or more respective first criteria, e.g., connection to the respective second network node 102 or the respective cell 122. o Receiving 803 one or more third indications. The first node 130 may be configured to perform the receiving of this Action 803, e.g. by means of the receiving unit 1501 within the first node 130, configured to perform this action.

The one or more third indications may be received from the network node 101, 102, 140.

In some embodiments, e.g., the first node 130 may be served by the first network node 101 with a second configuration, which may be also referred to as a current configuration, and old configuration or an existing configuration.

In some of such embodiments, the method further comprise Action 805. o Receiving 805 a fourth indication. The first node 130 may be configured to perform the receiving of this Action 805, e.g. by means of the receiving unit 1501 within the first node 130, configured to perform this action.

The fourth indication may be received from the network node 101, 102, 140.

The fourth indication may indicate that the second configuration is no longer valid.

In some embodiments, at least one of the following may apply:

- at least one of the one or more first indications and the one or more second indications may be received during a procedure of setting up an F1 connection, e.g., inside an F1 SETUP RESPONSE message from the respective second network node 102,

- the one or more first indications may be received together with a conditional F1 setup message,

- the receiving of Action 801 may comprise receiving a plurality of configurations comprising the first configuration, each configuration in the plurality comprising a respective identifier,

- at least one of the one or more first indications and the one or more second indications may be comprised in a Radio Resource Control (RRC) message,

- at least one of the one or more first indications and the one or more second indications may be received via F1AP, - at least one of the one or more first indications and the one or more second indications may be received via Downlink Control Information (DCI), or via a MAC control element,

- the one or more respective first criteria may comprise at least one of: a) executing a handover to the respective cell 122, and b) the first node 130 establishing a connection, e.g., an F1 connection, to the respective second network node 102, e.g., a new donor CU, e.g., identified by for example, another respective identifier, e.g., gNB-Cll name,

- the one or more second indications may be received as part of, or together with, a handover command to the respective cell 122, and

- the one or more second indications may be respectively comprised in a control Protocol Data Unit (PDU), e.g., BAP control PDU, or a data PDU.

The PDU may comprise at least one of the following:

- a fifth indication indicating an activation or deactivation flag of the respective first configuration,

- a sixth indication identifying the respective first configuration, and

- a seventh indication indicating a final destination of the first node 130 when served by the respective second network node 102, e.g., a new parent node.

There may be two or more such PDUs travelling towards the second radio network node 102, e.g., the new parent of the first node 130 along different paths under the respective second network node 102.

In some embodiments, e.g., the first node 130 may be served by the first network node 101 with the second configuration.

In some of such embodiments, the method further comprise, after activating the respective first configuration Action 807. o Performing 807 an action. The first node 130 may be configured to perform the performing of this Action 807, e.g. by means of a performing unit 1504 within the first node 130, configured to perform this action.

The performing of the action may be on the second configuration. The action may be selected from: i. deleting the second configuration and keeping other previous BAP configurations and/or BH RLC channel configurations, ii. deactivating the second configuration, e.g., a previous BAP configuration and/or BH RLC channel configuration, iii. keeping the second configuration in a list of previous BAP configurations and/or BH RLC channel configurations, and iv. deleting the second configuration and any other previous BAP configurations and/or BH RLC channel configurations.

In some embodiments, wherein the communications network 100 is an Integrated Access and Backhaul (IAB) network.

Other units 1505 may be comprised in the first node 130.

The first node 130 may also be configured to communicate user data with a host application unit in a host computer 2210, e.g., via another link such as 2250.

In Figure 15, optional units are indicated with dashed boxes.

The first node 130 may comprise an interface unit to facilitate communications between the first node 130 and other nodes or devices, e.g., the first network node 101, the one or more second network nodes 110, the second network node 102, the third network node 103, the first radio network node 111, the one or more second radio network nodes 112, e.g., the second radio network node 112, the one or more devices 150, the host computer 2210, and/or any of the other nodes or devices. In some particular examples, the interface may, for example, include a transceiver configured to transmit and receive radio signals over an air interface in accordance with a suitable standard.

The first node 130 may comprise an arrangement as shown in Figure 15 or in Figure 22.

The network node 101 , 102, 140 embodiments relate to Figure 19, Figures 11-14, Figure 16 and Figures 21-26.

A method performed by a network node, such as the network node 101 , 102, 140 is described herein. The network node 101, 102, 140 may operate in the communications network 100. The method may be understood to be for handling configuration of the first node 130.

In some embodiments, the network node 101, 102, 140 may be the first network node 101. In some embodiments, the network node 101 , 102, 140 may be the second network node 102. In some embodiments, the network node 101, 102, 140 may be the core network node 140.

The method may comprise one or more of the following actions. In some embodiments all the actions may be performed. In other embodiments, one or more actions may be performed. One or more embodiments may be combined, where applicable. All possible combinations are not described to simplify the description. Some actions may be performed in a different order than that shown in Figure 19. In Figure 19, actions which may be optional in some examples are depicted with dashed boxes.

The detailed description of some of the following corresponds to the same references provided above, in relation to the actions described for the first node 130 and will thus not be repeated here to simplify the description. For example, in some examples the one or more first indications may be the same as the one or more second indications, or may be comprised in a same message. o Sending 904 the one or more first indications. The network node 101,

102, 140 may be configured to perform the sending in this Action 904 action, e.g. by means of a sending unit 1601 within the network node 101, 102, 140, configured to perform this action.

The network node 101 , 102, 140 may send the one or more first indications to at least one of: i. the first node 130 served by the first network node 101 and ii. at least one first radio network node 111 ; the first node 130 may be served by the first network node 101 through the at least one first radio network node 111 ; the at least one first radio network node 111 , may have the respective wireless connections with the first node 130 and the first network node 101.

The one or more first indications may indicate the one or more first configurations to be applied by the first node 130 upon fulfilment of the one or more respective first criteria, e.g., connection to the respective cell 122 served by the respective second network node 102.

The first node 130 may be provided the wired connection to the core network node 140 of the communications network 100 by the first network node 101 via at least a wireless connection. The first node 130 may be capable to be provided the wired connection to the core network node 140 of the communications network 100 by the respective second network node 102 via at least another respective wireless connection.

The one or more first configurations may be identified by the respective identifier, e.g., of the respective cell 122, or of the respective second network node 102.

In some embodiments, at least one of the following may apply:

- each of the one or more first configurations may be a BAP configuration,

- the first node 130 may be a first IAB node, the first network node 101 may be a Donor CU, and the respective second network node 102 may be a second Donor CU, - each of the at least one first radio network node 111 may be an ancestor node,

- the one or more first indications may originate at the core network node 140, the core network node 140 being an OAM node,

- the first node 130 may be an mlAB node,

- the first node 130 may be a node, e.g., an IAB node, with no descendants,

- the sending of Action 904 may be performed during the movement of the first node 130 along the route 170, e.g., a fixed route,

- the first radio network node 111 may be a source ancestor IAB node,

- the first node 130 may be to be served by the second network node 102 through at least one respective second radio network node 112, the respective second radio network node 112 having the other respective wireless connections with the first node 130 and the second network node 102,

- each of the one or more first configurations may be a respective BH RLC channel configuration, used to configure an RLC entity, e.g., a corresponding logical channel in MAC for BH RLC channel between lAB-node, e.g., the first node 130 and its respective parent node, e.g., the respective second radio network node 112,

- the respective identifier may be the newly defined identifier,

- the one or more first indications may be one of: i. received in the standalone message, ii. comprising the one or more respective first criteria upon the fulfilment of which the respective first configuration may have to be activated, iii. the one or more enhanced messages, e.g., the one or more enhanced existing messages,

- the one or more respective first criteria may comprise at least one of: i. the first node 130 identifying , e.g., and connecting to, the respective cell 122, e.g., via PCI, and/or CGI, indicated in the respective first configuration, ii. the first node 130 entering the geographical area, e.g., the group of cells or a TA, indicated in the respective first configuration, e.g., within the same donor CU, and iii. the first node 130 establishing a connection, e.g., the F1 connection, to the respective second network node 102, e.g., the new donor CU, e.g., identified by for example, another respective identifier, e.g., gNB-Cll name, and

- the network node 101 , 102, 140 may send the first node 130 the further indication, e.g., referred to later as the eighth indication, from the first network node 101 ; the further indication may indicate the order in which the plurality of respective second network nodes 110, that is, the one or more second network nodes 110, comprising the respective second network node 102, and/or a plurality of second radio network nodes 112 comprising the second radio network node 112, may have to serve the first node 130.

Each of the one or more first configurations may comprise at least one of:

- the respective BAP configuration comprising the respective at least one of: i. the one or more BAP addresses, for the first node 130, ii. the one or more DL and UL BAP routing IDs for the first node 130, iii. the one or more second configurations for backhaul mapping of UL traffic originating at the first node 130 or one or more devices 150 served by the first node 130, iv. the BAP routing configuration, v. the one or more third configurations for BAP header rewriting, and vi. the one or more fourth configurations for UL and/or DL local rerouting of traffic, and

- the respective BH RLC channel configuration, used to configure the respective RLC entity, e.g., the corresponding logical channel in MAC for BH RLC channel between lAB-node, e.g., the first node 130 and its parent node, e.g., the respective second radio network node 112.

In some embodiments, the method may comprise one or more of the following actions: o Sending 905 the one or more second indications. The network node 101 ,

102, 140 may be configured to perform the sending of this Action 905, e.g., by means of the sending unit 1601 , configured to perform this action.

The sending in this Action 905 may be to at least one of the first node 130 and the radio network node 111 , 112.

The one or more second indications may indicate, e.g., respectively, to activate the respective first configuration, e.g., immediately or upon fulfilment of the one or more respective first criteria, e.g., connection to the respective second network node 102 or the respective cell 122. o Sending 906 the one or more third indications. The network node 101,

102, 140 may be configured to perform the sending of this Action 906, e.g., by means of the sending unit 1601 , configured to perform this action.

The sending in this Action 906 may be to at least one of the first node 130 and the radio network node 111 , 112.

In some embodiments, e.g., wherein the network node 101 , 102, 140 may be one of the first network node 101 and the second network node 102, the first node 130 may be served by the first network node 101 with the second configuration.

In some of such embodiments, the method further comprise Action 908. o Sending 908 the fourth indication. The network node 101 , 102, 140 may be configured to perform the sending of this Action 908, e.g., by means of the sending unit 1601, configured to perform this action.

The sending in this Action 908 may be to at least one of the first node 130 and the at least one first network node 111.

In some embodiments, at least one of the following may apply:

- at least one of the one or more first indications and the one or more second indications may be sent during the procedure of setting up an F1 connection, e.g., inside an F1 SETUP RESPONSE message from the respective second network node 102,

- the one or more first indications may be sent together with the conditional F1 setup message,

- the receiving of Action 801 may comprise receiving the plurality of configurations comprising the first configuration, each configuration in the plurality comprising the respective identifier,

- at least one of the one or more first indications and the one or more second indications may be comprised in a RRC message,

- at least one of the one or more first indications and the one or more second indications may be received via F1AP,

- at least one of the one or more first indications and the one or more second indications may be received via DCI, or via a MAC control element, - the one or more respective first criteria may comprise at least one of: a) executing a handover to the respective cell 122, and b) the first node 130 establishing a connection, e.g., an F1 connection, to the respective second network node 102, e.g., the new donor CU, e.g., identified by for example, the another respective identifier, e.g., gNB-Cll name,

- the one or more second indications may be sent as part of, or together with, a handover command to the respective cell 122, and

- the one or more second indications may be respectively comprised in a control PDU, e.g., BAP control PDU, or a data PDU.

The PDU may comprise at least one of the following:

- the fifth indication indicating the activation or deactivation flag of the respective first configuration,

- the sixth indication identifying the respective first configuration, and

- the seventh indication indicating the final destination of the first node 130 when served by the respective second network node 102, e.g., the new parent node.

In some embodiments, e.g., wherein the network node 101 , 102, 140 may be the first network node 101 , the first node 130 may be served by the first network node 101 with the second configuration.

In some of such embodiments, the method may further comprise, e.g., after activating the first configuration, Action 908. o Performing 910 the action. The network node 101, 102, 140 may be configured to perform the performing of this Action 910, e.g., by means of a performing unit 1602 within the network node 101, 102, 140, configured to perform this action.

The performing of the action may be on the second configuration. The action may be selected from: i. deleting the second configuration and keeping other previous BAP configurations and/or BH RLC channel configurations, ii. deactivating the second configuration, e.g., a previous BAP configuration and/or BH RLC channel configuration, iii. keeping the second configuration in a list of previous BAP configurations and/or BH RLC channel configurations, and iv. deleting the second configuration and any other previous BAP configurations and/or BH RLC channel configurations. In some embodiments, e.g., wherein the network node 101 , 102, 140 may be the first network node 101 the method may further comprise: o Obtaining 902 the one or more first configurations. The network node

101 , 102, 140 may be configured to perform the obtaining of this Action 902, e.g., by means of an obtaining unit 1603 within the network node 101 , 102, 140, configured to perform this action.

The obtaining of the one or more first configurations may be from at least one of: i. the one or more second network nodes 110 comprising the respective second network node 102, wherein the one or more second network nodes 110 may have a capability to provide, to the first node 130, a respective wired connection to the core network node 140 of the communications network 100 via at least a respective wireless connection, and ii. the third network node 103 managing configuration of nodes comprised in the communications network 100. o Obtaining 903 at least one of an eight indication and a ninth indication.

The network node 101, 102, 140 may be configured to perform the obtaining of this Action 903, e.g., by means of the obtaining unit 1603 within the network node 101 , 102, 140, configured to perform this action.

The obtaining in this Action 903 may be from at least one of the one or more second network nodes 110, the third network node 103 and the core network node 140. i. The eighth indication may indicate the order in which the plurality of one or more second network nodes 110 may have to serve the first node 130. ii. The ninth indication may indicate a list of the one or more second network nodes 110 from which the first network node 101 may have to request a respective first configuration of the one or more first configurations.

At least one of the obtaining 902 of the one or more first configurations and the obtaining 903 of the at least one of the eighth indication and the ninth indication may be performed via one of: i. one or more XnAP messages, and ii. by means of signalling traversing the core network 140 of the communications network 100. o Sending 901 a first message. The network node 101 , 102, 140 may be configured to perform the sending of this Action 901, e.g. by means of the sending unit 1601 , configured to perform this action. The sending in this Action 901 of the first message may be to the core network node 140. The message may request at least one of the one or more first configurations. The obtaining in Action 902 of the one or more first configurations may be in response to the sent first message. o Storing 907 the one or more first configurations, e.g., along with the respective identifier. The network node 101 , 102, 140 may be configured to perform the storing in this Action 907, e.g. by means of a storing unit 1604 within the network node 101, 102, 140, configured to perform this action. o Applying 909 stored respective first configuration. The network node 101,

102, 140 may be configured to perform the applying in this Action 909, e.g. by means of an applying unit 1605 within the network node 101 , 102, 140, configured to perform this action.

The applying in this Action 909 may be upon fulfilment of the one or more respective first criteria, e.g., connection to the respective second network node 102 and/or the respective cell 122.

In some embodiments, at least one of the following may apply:

- the first message may be an NG Application Protocol, NGAP, message towards one or more serving Access and Mobility Management Functions (AMFs),

- the first message may comprise a tenth indication indicating a quantification of current or predicted traffic load at the first node 130,

- the core network node 140 may be the GAM node, and

- the first message may comprise information about the second configuration. Other units 1606 may be comprised in the network node 101, 102, 140.

The network node 101, 102, 140 may also be configured to communicate user data with a host application unit in a host computer 2210, e.g., via another link such as 2250.

In Figure 16, optional units are indicated with dashed boxes.

The network node 101 , 102, 140 may comprise an interface unit to facilitate communications between the network node 101 , 102, 140 and other nodes or devices, e.g., the first node 130, the first network node 101, the one or more second network nodes 110, the second network node 102, the third network node 103, the first radio network node 111 , the one or more second radio network nodes 112, e.g., the second radio network node 112, the one or more devices 150, the host computer 2210, and/or any of the other nodes or devices. In some particular examples, the interface may, for example, include a transceiver configured to transmit and receive radio signals over an air interface in accordance with a suitable standard.

The network node 101 , 102, 140 may comprise an arrangement as shown in Figure 16 or in Figure 22. The radio network node 111, 112 embodiments relate to Figure 20, Figures 11-14, Figure 17 and Figures 21-26.

A method, performed by a radio network node, such as the radio network node 111, 112 is described herein. The radio network node 111, 112 may operate in the communications network 100. The method may be understood to be for handling configuration of the first node 130. The first node 130 may be provided a wired connection to the core network node 140 of the communications network 100 by the first network node 101 via at least the wireless connection. The first node 130 may be capable to be provided a wired connection to the core network node 140 of the communications network 100 by the second network node 102 via at least the another wireless connection.

In some embodiments, the radio network node 111 , 112 may be the first radio network node 111. In some embodiments, the radio network node 111, 112 may be the second radio network node 112.

The method may comprise one or more of the following actions.

In some embodiments all the actions may be performed. In other embodiments, one or more actions may be performed. One or more embodiments may be combined, where applicable. All possible combinations are not described to simplify the description. Some actions may be performed in a different order than that shown in Figure 20. In Figure 20, actions which may be optional in some examples are depicted with dashed boxes. The detailed description of some of the following corresponds to the same references provided above, in relation to the actions described for the first node 130 and will thus not be repeated here to simplify the description. For example, the BH RLC CH configuration may be understood to refer to establishing one or more BH RLC channels between a new parent DU and the first node 130. o Receiving 1002 an indication. The radio network node 111, 112 may be configured to perform the receiving in this Action 1002 action, e.g. by means of a receiving unit 1701 within the radio network node 111 , 112, configured to perform this action.

The radio network node 111, 112 may receive the indication from the network node 101, 102, 140.

At least one of the following may apply: i. with the proviso that the radio network node 111, 112 is a first radio network node 111 , wherein the first node 130 is served by the first network node 101 through at least the first radio network node 111 , the first radio network node 111 having respective wireless connections with the first node 130 and the first network node 101 , the indication may be the fourth indication; the fourth indication may indicate that the second configuration with which the first node 111 may serve the first node 130 may no longer be valid, and ii. with the proviso the radio network node 111, 112 is a second radio network node 112, wherein the first node 130 is to be served by the second network node 102 through at least the second radio network node 112, the second radio network node 112 having other respective wireless connections with the first node 130 and the second network node 102, the indication may be the second indication; the second indication may indicate to activate the respective first configuration stored at the first radio network node 111 , e.g., immediately or upon fulfilment of the one or more first criteria, e.g., connection by the first node 130 to the second network node 102.

In some embodiments, the method may comprise one or more of the following actions: o Receiving 1001 the first indication. The radio network node 111 , 112 may be configured to perform the receiving of this Action 1001 , e.g. by means of the receiving unit 1701 within the radio network node 111 , 112, configured to perform this action.

The radio network node 111, 112 may receive the first indication from the network node 101 , 102, 140.

The first indication may indicate the respective first configuration to be applied by the first node 130 upon fulfilment of the one or more respective first criteria, e.g., connection to the respective cell 122 served by the second network node 102. The respective first configuration may be identified by the respective identifier, e.g., of the respective cell 122, or of the second network node 102. o Storing 1004 the respective first configuration at the radio network node

111 , 112, e.g., along with the identifier. The radio network node 111, 112 may be configured to perform the storing of this Action 1004, e.g. by means of a storing unit 1702 within the radio network node 111 , 112, configured to perform this action. o Applying 1005 the second or fourth indication. The radio network node

111 , 112 may be configured to perform the applying of this Action 1005, e.g. by means of an applying unit 1703 within the radio network node 111 , 112, configured to perform this action.

The applying in this Action 1005 of the second or fourth indication may be immediately, or upon fulfilment of the one or more respective first criteria, e.g., connection to the second network node 102 and/or the respective cell 122. In some embodiments, at least one of the following may apply:

- the first configuration may be a BAP configuration,

- the first node 130 may be a first IAB node, the first network node 101 may be a Donor CU, and the respective second network node 102 may be a second Donor CU,

- the first indication may originate at the core network node 140, the core network node 140 being the CAM node,

- the first node 130 may be a mlAB node,

- the first node 130 may be a node, e.g., an IAB node, with no descendants,

- the applying of Action 1005 may be performed during the movement of the first node 130 along the route 170, e.g., a fixed route,

- the first radio network node 111 may be a source ancestor IAB node,

- the respective second radio network node 112 may be a target ancestor IAB node,

- the respective second radio network node 112 may be a target parent IAB node,

- the first indication may be one of: i. received in the standalone message, ii. comprising the one or more first criteria upon the fulfilment of which the respective first configuration may have to be activated, iii. the enhanced message, e.g., the enhanced existing message,

- the one or more respective first criteria may comprise at least one of: i. the first node 130 identifying , e.g., and connecting to, the respective cell 122, e.g., via PCI, and/or CGI, indicated in the respective first configuration, ii. the first node 130 entering a geographical area, e.g., the group of cells or the TA, indicated in the first configuration, e.g., within the same donor CU, and iii. the first node 130 establishing a connection, e.g., an F1 connection, to the respective second network node 102, e.g., the new donor CU, e.g., identified by for example, another respective identifier, e.g., gNB-CU name.

The first configuration may comprise at least one of:

- the BAP configuration comprising the respective at least one of: i. the one or more BAP addresses, for the first node 130, ii. the one or more DL and UL BAP routing IDs, for the first node 130, iii. the one or more second configurations for backhaul mapping of UL traffic originating at the first node 130 or one or more devices 150 served by the first node 130, iv. the BAP routing configuration, v. the one or more third configurations for BAP header rewriting, and vi. the one or more fourth configurations for UL and/or DL local rerouting of traffic, and the respective BH RLC channel configuration, used to configure the respective RLC entity, e.g., the corresponding logical channel in MAC for BH RLC channel between lAB-node, e.g., the first node 130 and its parent node, e.g., the respective second radio network node 112.

In some embodiments, wherein the first node 130 is served by the first network node 101 with a second configuration the method may comprise the following action: o Receiving 1003 the third indication. The first node 130 may be configured to perform the receiving of this Action 1003, e.g. by means of the receiving unit 1701 within the radio network node 111 , 112, configured to perform this action.

The third indication may be received from the network node 101 , 102, 140.

The third indication may indicate to store at least one of the first configuration and the second indications, until application of the first configuration.

In some embodiments, at least one of the following may apply:

- at least one of the first indication and the second indication may be received during a procedure of setting up an F1 connection, e.g., inside an F1 SETUP RESPONSE message from the respective second network node 102,

- the first indication may be received together with a conditional F1 setup message, - the receiving of Action 1001 may comprise receiving the plurality of configurations comprising the first configuration, each configuration in the plurality comprising the respective identifier,

- at least one of the first indication and the second indication may be comprised in an RRC message,

- at least one of the first indication and the second indication may be received via F1AP,

- at least one of the first indication and the second indication may be received via DCI, or via a MAC control element,

- the one or more respective first criteria may comprise at least one of: a) executing a handover to the respective cell 122, and b) the first node 130 establishing a connection, e.g., an F1 connection, to the respective second network node 102, e.g., the new donor CU, e.g., identified by for example, another respective identifier, e.g., gNB-Cll name,

- the second indication may be received as part of, or together with, a handover command to the respective cell 122, and

- the second indication may be comprised in a PDU, e.g., BAP control PDU, or a data PDU.

The PDU may comprise at least one of the following:

- the fifth indication indicating the activation or deactivation flag of the first configuration,

- the sixth indication identifying the first configuration, and

In some of such embodiments, the method further comprise, after activating the first configuration Action 1006. o Performing 1006 an action. The radio network node 111, 112 may be configured to perform the performing of this Action 807, e.g. by means of a performing unit 1704 within the radio network node 111 , 112, configured to perform this action.

In some embodiments, wherein the second radio network node 112 may be to directly serve the first node 130 as a new parent. In some of these embodiments, the second indication may be an existing F1AP UE CONTEXT SETUP REQUEST message with a particular, e.g., gNB-CU UE F1AP ID, gNB-DU UE F1AP ID, identifier pair.

The identifier pair may have previously, e.g., at the time when the BAP routing config was given to the new parent, associated to a BAP routing configuration.

In some embodiments, the second indication may activate a respective BH RLC channel configuration at the second radio network node 112

Other units 1705 may be comprised in the first node 130.

The radio network node 111, 112 may also be configured to communicate user data with a host application unit in a host computer 2210, e.g., via another link such as 2250.

In Figure 17, optional units are indicated with dashed boxes.

The radio network node 111, 112 may comprise an interface unit to facilitate communications between the radio network node 111, 112 and other nodes or devices, e.g., the first node 130, the first network node 101, the one or more second network nodes 110, the second network node 102, the third network node 103, the first radio network node 111 , the one or more second radio network nodes 112, e.g., the second radio network node 112, the one or more devices 150, the host computer 2210, and/or any of the other nodes or devices. In some particular examples, the interface may, for example, include a transceiver configured to transmit and receive radio signals over an air interface in accordance with a suitable standard.

The radio network node 111, 112 may comprise an arrangement as shown in Figure 17 or in Figure 22.

EXAMPLES related to embodiments herein: Example 1. A method performed by a first node (130) operating in a communications network (100), the first node (130) being served by a first network node (101), the method being for handling configuration of the first node (130), and wherein the method further comprises:

- receiving (801), from a network node (101 , 102, 140), one or more first indications, the one or more first indications respectively indicating one or more first configurations to be applied by the first node (130) upon fulfilment of one or more respective first criteria, e.g., connection to a respective cell (122) served by a respective second network node (102), wherein the first node (130) is provided a wired connection to a core network node (140) of the communications network (100) by the first network node (101) via at least a wireless connection, and wherein the first node (130) is capable to be provided a wired connection to the core network node (140) of the communications network (100) by the respective second network node (102) via at least another respective wireless connection, e.g., the one or more first configurations being identified by a respective identifier, e.g., of the respective cell (122), or of the respective second network node (102),

- storing (804) the one or more first configurations at the first node (130), e.g., along with the respective identifier, and

- applying (806), out of the stored one or more first configurations, a respective first configuration upon fulfilment of the respective one or more first criteria, e.g., connection to the respective second network node (102) and/or the respective cell (122).

Example 2. The method according to example 1 wherein at least one of:

- each of the one or more first configurations is a Backhaul Adaptation Protocol, BAP, configuration,

- the first node (130) is a first Integrated Access and Backhaul, IAB, node, the first network node (101) is a Donor Centralized Unit, CU, and the respective second network node (102) is a second Donor CU,

- the one or more first indications originate at the core network node (140), the core network node (140) being an Operations Administration and Maintenance, OAM, node,

- the first node (130) is a mobile IAB node,

- the first node (130) is a node, e.g., an IAB node, with no descendants,

- the applying (806) is performed during a movement of the first node (130) along a route (170), e.g., a fixed route, - the first node (130) is served by the first network node (101) through at least one first radio network node (111), the first radio network node (111) having respective wireless connections with the first node (130) and the first network node (101),

- the first radio network node (111) is a source ancestor IAB node,

- the first node (130) is to be served by the second network node (102) through at least one respective second radio network node (112), the respective second radio network node (112) having other respective wireless connections with the first node (130) and the second network node (102),

- each of the one or more first configurations is a respective Backhaul, BH, Radio Link Control, RLC, channel, configuration, used to configure an RLC entity, e.g., a corresponding logical channel in Medium Access Control, MAC, for BH RLC channel between lAB-node, e.g., the first node (130) and its respective parent node, e.g., the respective second radio network node (112),

- the respective second radio network node (112) is a respective target ancestor IAB node,

- the respective second radio network node (112) is a respective target parent IAB node,

- the respective identifier is a newly defined identifier,

- the one or more first indications are one of: i. received in a standalone message, ii. comprising the one or more respective first criteria upon the fulfilment of which the respective first configuration is to be activated, iii. one or more enhanced messages, e.g., one or more enhanced existing messages,

- the one or more respective first criteria comprise at least one of: i. the first node (130) identifying , e.g., and connecting to, the respective cell (122), e.g., via PCI, and/or CGI, indicated in the respective first configuration, ii. the first node (130) entering a geographical area, e.g., a group of cells or a TA, indicated in the respective first configuration, e.g., within the same donor CU, and iii. the first node (130) establishing a connection, e.g., an F1 connection, to the respective second network node (102), e.g., a new donor CU, e.g., identified by for example, another respective identifier, e.g., gNB-CU name, and - the first node (130) receives a further indication from the first network node

(101), the further indication indicating an order in which a plurality of respective second network nodes (110) comprising the respective second network node

(102), and/or a plurality of second radio network nodes 112 comprising the second radio network node 112, are to serve the first node (130).

Example 3. The method according to example 2, wherein each of the one or more first configurations comprises at least one of:

- a respective BAP configuration comprising respective at least one of: i. one or more BAP addresses, for the first node (130) ii. one or more downlink, DL, and uplink, UL, BAP routing identifiers, IDs, for the first node (130), iii. one or more second configurations for backhaul mapping of UL traffic originating at the first node (130) or one or more devices (150) served by the first node (130), iv. a BAP routing configuration, v. one or more third configurations for BAP header rewriting, and

- one or more fourth configurations for UL and/or DL local rerouting of traffic, and the respective BH RLC channel configuration, used to configure the respective RLC entity, e.g., a corresponding logical channel in MAC for BH RLC channel between lAB-node, e.g., the first node (130) and its parent node, e.g., the respective second radio network node (112).

Example 4. The method according to any of examples 1-3, wherein the first node (130) is served by the first network node (101) with a second configuration, and wherein the method further comprises at least one of:

- receiving (802), from the network node (101 , 102, 140), one or more second indications, e.g., together or separate from the one or more first indications, the one or more second indications indicating, e.g., respectively, to activate the respective first configuration, e.g., immediately or upon fulfilment of the one or more respective first criteria, e.g., connection to the respective second network node (102),

- receiving (803), from the network node (101 , 102, 140), one or more third indications, the one or more third indications indicating to store at least one of the one or more first configurations and the one or more second indications, until application of the respective first configuration, and receiving (805), from the network node (101 , 102, 140), a fourth indication, the fourth indication indicating that the second configuration is no longer valid.

Example 5. The method according to example 4, wherein at least one of:

- at least one of the one or more first indications and the one or more second indications are received during a procedure of setting up an F1 connection, e.g., inside an F1 SETUP RESPONSE message from the respective second network node (102),

- the one or more first indications are received together with a conditional F1 setup message,

- the receiving (801) comprises receiving a plurality of configurations comprising the first configuration, each configuration in the plurality comprising a respective identifier,

- at least one of the one or more first indications and the one or more second indications are comprised in a Radio Resource Control, RRC, message,

- at least one of the one or more first indications and the one or more second indications are received via F1AP,

- at least one of the one or more first indications and the one or more second indications are received via Downlink Control Information, DCI, or via a Medium Access Control, MAC, control element,

- the one or more respective first criteria comprise at least one of: a) executing a handover to the respective cell (122), and b) the first node (130) establishing a connection, e.g., an F1 connection, to the respective second network node (102), e.g., a new donor CU, e.g., identified by for example, another respective identifier, e.g., gNB-CU name,

- the one or more second indications are received as part of, or together with, a handover command to the respective cell (122), and

- the one or more second indications are respectively comprised in a control Protocol Data Unit, PDU, e.g., BAP control PDU, or a data PDU.

Example 6. The method according to example 5, wherein the PDU comprises at least one of:

- a sixth indication identifying the respective first configuration, and

- a seventh indication indicating a final destination of the first node (130) when served by the respective second network node (102), e.g., a new parent node. Example 7. The method according to any of examples 4-6, wherein the first node (130) is served by the first network node (101) with a second configuration, and wherein the method further comprises, after activating the respective first configuration:

- performing (807) an action on the second configuration selected from: i. deleting the second configuration and keeping other previous BAP configurations and/or BH RLC channel configurations, ii. deactivating the second configuration, e.g., a previous BAP configuration and/or BH RLC channel configuration, iii. keeping the second configuration in a list of previous BAP configurations and/or BH RLC channel configurations, and iv. deleting the second configuration and any other previous BAP configurations and/or BH RLC channel configurations.

Example 8. A method performed by a network node (101, 102, 140) operating in a communications network (100), the method being for handling configuration of a first node (130), wherein the method further comprises:

- sending (904) one or more first indications to at least one of: i. the first node (130) served by a first network node (101) and ii. at least one first radio network node (111), wherein the first node (130) is served by the first network node (101) through the at least one first radio network node (111), the at least one first radio network node (111), having respective wireless connections with the first node (130) and the first network node (101), the one or more first indications indicating one or more first configurations to be applied by the first node (130) upon fulfilment of one or more respective first criteria, e.g., connection to a respective cell (122) served by a respective second network node (102), wherein the first node (130) is provided a wired connection to a core network node (140) of the communications network (100) by the first network node (101) via at least a wireless connection, and wherein the first node (130) is capable to be provided a wired connection to the core network node (140) of the communications network (100) by the respective second network node (102) via at least another respective wireless connection, e.g., the one or more first configurations being identified by a respective identifier, e.g., of the respective cell (122), or of the respective second network node (102). Example 9. The method according to example 8 wherein at least one of:

- each of the at least one first radio network nodes (111) is an ancestor node,

- the first node (130) is a mobile IAB node,

- the first node (130) is a node, e.g., an IAB node, with no descendants,

- the sending (904) is performed during a movement of the first node (130) along a route (170), e.g., a fixed route,

- the first radio network node (111) is a source ancestor IAB node,

- the respective identifier is a newly defined identifier,

- the one or more first indications are one of: i. received in a standalone message, ii. comprising the one or more respective first criteria upon the fulfilment of which a respective first configuration is to be activated, iii. one or more enhanced messages, e.g., one or more enhanced existing messages, - the one or more respective first criteria comprise at least one of: i. the first node (130) identifying , e.g., and connecting to, the respective cell (122), e.g., via PCI, and/or CGI, indicated in the respective first configuration, ii. the first node (130) entering a geographical area, e.g., a group of cells or a TA, indicated in the respective first configuration, e.g., within the same donor CU, and iii. the first node (130) establishing a connection, e.g., an F1 connection, to the respective second network node (102), e.g., a new donor CU, e.g., identified by for example, another respective identifier, e.g., gNB-CU name, and

- the network node (101 , 102, 140) sends to the first node (130) a further indication from the first network node (101), the further indication indicating an order in which a plurality of respective second network nodes (110) comprising the respective second network node (102) and/or a plurality of second radio network nodes 112 comprising the second radio network node 112 are to serve the first node (130).

Example 10. The method according to example 9, wherein each of the one or more first configurations comprises at least one of:

- a respective BAP configuration comprising respective at least one of: i. one or more BAP addresses, for the first node (130) ii. one or more downlink, DL, and uplink, UL, BAP routing identifiers, IDs, for the first node (130), iii. one or more second configurations for backhaul mapping of UL traffic originating at the first node (130) or one or more devices (150) served by the first node (130), iv. a BAP routing configuration, v. one or more third configurations for BAP header rewriting, and vi. one or more fourth configurations for UL and/or DL local rerouting of traffic, and.

- the respective BH RLC channel configuration, used to configure the respective RLC entity, e.g., a corresponding logical channel in MAC for BH RLC channel between lAB-node, e.g., the first node (130) and its parent node, e.g., the respective second radio network node (112). Example 11. The method according to any of examples 8-10, wherein the network node (101, 102, 140) is one of the first network node (101) and the second network node (102), wherein the first node (130) is served by the first network node (101) with a second configuration, and wherein the method further comprises at least one of:

- sending (905), to at least one of the first node (130) and a radio network node (111, 112), one or more second indications, e.g., together or separate from the one or more first indications, the one or more second indications indicating to activate a respective first configuration, e.g., immediately or upon fulfilment of the one or more respective first criteria, e.g., connection to the respective second network node (102),

- sending (906), to at least one of the first node (130) and the radio network node (111 , 112), one or more third indications, the one or more third indications indicating to store at least one of the one or more first configurations and the one or more second indications, until application of the respective first configuration, and

- sending (908), to at least one of the first node (130) and the at least one first network node (111), a fourth indication, the fourth indication indicating that the second configuration is no longer valid.

Example 12. The method according to example 11, wherein at least one of:

- at least one of the one or more first indications and the one or more second indications are sent during a procedure of setting up an F1 connection, e.g., inside an F1 SETUP RESPONSE message from the respective second network node (102),

- the one or more first indications are sent together with a conditional F1 setup message,

- the sending (904) comprises sending a plurality of configurations comprising the first configuration, each configuration in the plurality comprising a respective identifier,

- at least one of the one or more first indications and the one or more second indications are comprised in a Radio Resource Control, RRC, message, and

- at least one of the one or more first indications and the one or more second indications are received via Downlink Control Information, DCI, or via a Medium Access Control, MAC, control element, - the one or more respective first criteria comprise at least one of: a) executing a handover to the respective cell (122), and b) the first node (130) establishing a connection, e.g., an F1 connection, to the respective second network node (102), e.g., a new donor CU, e.g., identified by for example, another respective identifier, e.g., gNB-Cll name,

- the one or more second indications are sent as part of, or together with, a handover command to the respective cell (122), and

Example 13. The method according to example 12, wherein the PDU comprises at least one of:

- a sixth indication identifying the respective first configuration, and

- a seventh indication indicating a final destination of the first node (130) when served by the respective second network node (102), e.g., a new parent node.

Example 14. The method according to any of examples 11-13, wherein the network node (101 , 102, 140) is the first network node (101), wherein the first network node (101) serves the first node (130) with a second configuration, and wherein the method further comprises, after activating the first configuration:

- performing (910) an action on the second configuration selected from: i. deleting the second configuration and keeping other previous BAP configurations and/or BH RLC channel configurations, ii. deactivating the second configuration and/or BH RLC channel configurations, iii. keeping the second configuration in a list of previous BAP configurations and/or BH RLC channel configurations, and iv. deleting the second configuration and any other previous BAP configurations and/or BH RLC channel configurations.

Example 15. The method according to any of examples 8-14, further comprising, e.g., wherein the network node (101) is the first network node (101):

- obtaining (902) the one or more first configurations from at least one of: i. one or more second network nodes (110) comprising the respective second network node (102), wherein the one or more second network nodes (110) have a capability to provide, to the first node (130), a respective wired connection to the core network node (140) of the communications network (100) via at least a respective wireless connection, and ii. a third network node (103) managing configuration of nodes comprised in the communications network (100).

Example 16. The method according to example 15, further comprising:

- obtaining (903), from at least one of the one or more second network nodes (110), the third network node (103) and the core network node (140), at least one of: i. an eighth indication indicating an order in which the plurality of one or more second network nodes (110) and/or a plurality of second radio network nodes 112 comprising the second radio network node 112 are to serve the first node (130), and ii. a ninth indication indicating a list of the one or more second network nodes (110) from which the first network node (101) is to request a respective first configuration of the one or more first configurations.

Example 17. The method according to example 16, wherein at least one of the obtaining (902) of the one or more first configurations and the obtaining (903) of the at least one of the eighth indication and the ninth indication is performed via one of: iii. one or more XnAP messages, iv. by means of signalling traversing the core network (140) of the communications network (100).

Example 18. The method according to any of examples 16-17, further comprising at least one of:

- sending (901) a first message to the core network node (140), the message requesting at least one of the one or more first configurations, and wherein the obtaining (902) of the one or more first configurations is in response to the sent first message,

- storing (907) the one or more first configurations, e.g., along with the respective identifier, and applying (909) a stored respective first configuration upon fulfilment of the one or more respective first criteria, e.g., connection to the respective second network node (102) and/or the respective cell (122).

Example 19. The method according to example 18, wherein at least one of:

- the first message is an NG Application Protocol, NGAP, message towards one or more serving Access and Mobility Management Functions, AMFs,

- the first message comprises a tenth indication indicating a quantification of current or predicted traffic load at the first node (130),

- the core network node (140) is an GAM node, and

- the first message comprises information about the second configuration.

Example 20. A method performed by a radio network node (111, 112) operating in a communications network (100), the method being for handling configuration of a first node (130), wherein the first node (130) is provided a wired connection to a core network node (140) of the communications network (100) by a first network node (101) via at least a wireless connection, and wherein the first node (130) is capable to be provided a wired connection to the core network node (140) of the communications network (100) by a second network node (102) via at least another wireless connection, and wherein the method further comprises:

- receiving (1002), from a network node (101, 102, 140), an indication, wherein one of: i. with the proviso that the radio network node (111 , 112) is a first radio network node (111), wherein the first node (130) is served by the first network node (101) through at least the first radio network node (111), the first radio network node (111) having respective wireless connections with the first node (130) and the first network node (101), the indication is a fourth indication, wherein the fourth indication indicates that a second configuration with which the first node (111) serves the first node (130) is no longer valid, and ii. with the proviso the radio network node (111, 112) is a second radio network node (112), wherein the first node (130) is to be served by the second network node (102) through at least the second radio network node (112), the second radio network node (112) having other respective wireless connections with the first node (130) and the second network node (102), the indication is a second indication, wherein the second indication indicates to activate a respective first configuration stored at the first radio network node (111), e.g., immediately or upon fulfilment of the one or more first criteria, e.g., connection by the first node (130) to the second network node (102).

Example 21. The method according to example 20, further comprising at least one of:

- receiving (1001), from the network node (101, 102, 140), a first indication, the first indication indicating the respective first configuration to be applied by the first node (130) upon fulfilment of one or more respective first criteria, e.g., connection to a respective cell (122) served by a second network node (102), e.g., the respective first configuration being identified by a respective identifier, e.g., of the respective cell (122), or of the second network node (102),

- storing (1004) the respective first configuration at the radio network node (111, 112), e.g., along with the identifier, and

- applying (1005) the second or fourth indication immediately or upon fulfilment of the one or more respective first criteria, e.g., connection to the second network node (102) and/or the respective cell (122).

Example 22. The method according to example 21 wherein at least one of:

- the first configuration is a Backhaul Adaptation Protocol, BAP, configuration,

- each of the one or more first configurations is a Backhaul Radio Link Control channel, BH RLC channel, configuration, used to configure an RLC entity, a corresponding logical channel in MAC for BH RLC channel between lAB-node and its parent node,

- the first node (130) is a first Integrated Access and Backhaul, I AB, node, the first network node (101) is a Donor Centralized Unit, CU, and the second network node (102) is a second Donor CU,

- the first indication originates at the core network node (140), the core network node (140) being an Operations Administration and Maintenance, OAM, node,

- the first node (130) is a mobile I AB node,

- the first node (130) is a node, e.g., an IAB node, with no descendants,

- the applying (1005) is performed during a movement of the first node (130) along a route (170), e.g., a fixed route,

- the first radio network node (111) is a source ancestor IAB node,

- the first configuration is a Backhaul, BH, Radio Link Control, RLC, channel, configuration, used to configure an RLC entity, e.g., a corresponding logical channel in Medium Access Control, MAC, for BH RLC channel between IAB- node, e.g., the first node (130) and its respective parent node, e.g., the respective second radio network node (112),

- the second radio network node (112) is a target ancestor I AB node,

- the second radio network node (112) is a target parent I AB node,

- the first indication is one of: i. received in a standalone message, ii. comprising the one or more first criteria upon the fulfilment of which the first configuration is to be activated, iii. an enhanced message, e.g., an enhanced existing message, and

- the one or more respective first criteria comprise at least one of: i. the first node (130) identifying , e.g., and connecting to, the respective cell (122), e.g., via PCI, and/or CGI, indicated in the first configuration, ii. the first node (130) entering a geographical area, e.g., a group of cells or a TA, indicated in the first configuration, and iii. the first node (130) establishing a connection, e.g., an F1 connection, to the second network node (102), e.g., a new donor CU, e.g., identified by for example, another respective identifier, e.g., gNB-CU name.

Example 23. The method according to example 22, wherein the first configuration comprises at least one of: a BAP configuration comprising respective at least one of: i. one or more BAP addresses, for the first node (130) ii. one or more downlink, DL, and uplink, UL, BAP routing identifiers, IDs, for the first node (130), iii. one or more second configurations for backhaul mapping of UL traffic originating at the first node (130) or one or more devices (150) served by the first node (130), iv. a BAP routing configuration, v. one or more third configurations for BAP header rewriting, and vi. one or more fourth configurations for UL and/or DL local rerouting of traffic, and - the BH RLC channel configuration, used to configure the RLC entity, e.g., a corresponding logical channel in MAC for BH RLC channel between lAB-node, e.g., the first node (130) and its parent node, e.g., the respective second radio network node (112).

Example 24. The method according to any of examples 20-23, wherein the first node (130) is served by the first network node (101) with a second configuration, and wherein the method further comprises:

- receiving (1003), from the network node (101 , 102, 140), a third indication, the third indication indicating to store at least one of the first configuration and the second indication, until application of the first configuration.

Example 25. The method according to example 24, wherein at least one of:

- at least one of the first indication and the second indication are received during a procedure of setting up an F1 connection, e.g., inside an F1 SETUP RESPONSE message from the second network node (102),

- the first indication is received together with a conditional F1 setup message,

- the receiving (1001) comprises receiving a plurality of configurations comprising the first configuration, each configuration in the plurality comprising a respective identifier,

- at least one of the first indication and the second indication are comprised in a Radio Resource Control, RRC, message, and

- at least one of the first indication and the second indication are received via F1AP,

- at least one of the first indication and the second indication are received via Downlink Control Information, DCI, or via a Medium Access Control, MAC, control element,

- the one or more respective first criteria comprise at least one of: a) the first node (130) executing a handover to the cell (122), and b) the first node (130) establishing a connection, e.g., an F1 connection, to the second network node (102), e.g., a new donor CU, e.g., identified by for example, another respective identifier, e.g., gNB-CU name,

- the second indication is received as part of, or together with, a handover command to the cell (122), and

- the second indication is comprised in a control Protocol Data Unit, PDU, e.g., BAP control PDU, or a data PDU. Example 26. The method according to example 25, wherein the PDU comprises at least one of:

- a fifth indication indicating an activation or deactivation flag of the first configuration,

- a sixth indication identifying the first configuration, and

- a seventh indication indicating a final destination of the first node (130) when served by the second network node (102), e.g., a new parent node.

Example 27. The method according to any of examples 24-26, wherein the first node (130) is served by the first network node (101) with a second configuration, and wherein the method further comprises, after activating the first configuration:

- performing (1006) an action on the second configuration selected from: i. deleting the second configuration and keeping other previous BAP configurations and/or BH RLC channel configurations, ii. deactivating the second configuration and/or BH RLC channel configurations, iii. keeping the second configuration in a list of previous BAP configurations and/or BH RLC channel configurations, and iv. deleting the second configuration and any other previous BAP configurations and/or BH RLC channel configurations.

Example 28. The method according to any of examples example 20-27, wherein the second radio network node (112) is to directly serve the first node (130) as a new parent, and wherein the second indication is an existing F1AP UE CONTEXT SETUP REQUEST message with a particular, e.g., gNB-CU UE F1AP ID, gNB-DU UE F1AP ID, identifier pair, wherein the identifier pair was previously, e.g., at the time when the BAP routing config was given to the new parent, associated to a BAP routing configuration.

Example 29. The method according to example 28, wherein the second indication activates a respective BH RLC channel configuration at the second radio network node (112).

Further Extensions And Variations Figure 21 : Telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments

With reference to FIGURE 21 , in accordance with an embodiment, a communication system includes telecommunication network 2110 such as the communications network 100, for example, a 3GPP-type cellular network, which comprises access network 2111 , such as a radio access network, and core network 2114. Access network 2111 comprises a plurality of network nodes such as the first node 130, the first network node 101 , the respective second network node 102, the first radio network node 111 and/or the respective second radio network node 112. For example, base stations 2112a, 2112b, 2112c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 2113a, 2113b, 2113c. Each base station 2112a, 2112b, 2112c is connectable to core network 2114 over a wired or wireless connection 2115. A plurality of wireless devices, such as the one or more devices 150 are comprised in the communications network 100. In Figure 21 , a first UE 2191 located in coverage area 2113c is configured to wirelessly connect to, or be paged by, the corresponding base station 2112c. A second UE 2192 in coverage area 2113a is wirelessly connectable to the corresponding base station 2112a. While a plurality of UEs 2191 , 2192 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 2112. Any of the UEs 2191 , 2192 are examples of the one or more devices 150.

Telecommunication network 2110 is itself connected to host computer 2130, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. Host computer 2130 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. Connections 2121 and 2122 between telecommunication network 2110 and host computer 2130 may extend directly from core network 2114 to host computer 2130 or may go via an optional intermediate network 2120. Intermediate network 2120 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 2120, if any, may be a backbone network or the Internet; in particular, intermediate network 2120 may comprise two or more sub-networks (not shown).

The communication system of Figure 21 as a whole enables connectivity between the connected UEs 2191 , 2192 and host computer 2130. The connectivity may be described as an over-the-top (OTT) connection 2150. Host computer 2130 and the connected UEs 2191 , 2192 are configured to communicate data and/or signaling via OTT connection 2150, using access network 2111 , core network 2114, any intermediate network 2120 and possible further infrastructure (not shown) as intermediaries. OTT connection 2150 may be transparent in the sense that the participating communication devices through which OTT connection 2150 passes are unaware of routing of uplink and downlink communications. For example, base station 2112 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer 2130 to be forwarded (e.g., handed over) to a connected UE 2191. Similarly, base station 2112 need not be aware of the future routing of an outgoing uplink communication originating from the UE 2191 towards the host computer 2130.

In relation to Figures 22, 23, 24, 25, and 26, which are described next, it may be understood that a UE is an example of the one or more devices 150, and that any description provided for the UE equally applies to the one or more devices 150. It may be also understood that the base station is an example of the first node 130, the first network node 101 , the respective second network node 102, the first radio network node 111 and/or the respective second radio network node 112, and that any description provided for the base station equally applies to the first node 130, the first network node 101 , the respective second network node 102, the first radio network node 111 and/or the respective second radio network node 112.

Figure 22: Host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments

Example implementations, in accordance with an embodiment, of the one or more devices 150, e.g., a UE, the first node 130, the first network node 101 , the respective second network node 102, the first radio network node 111 and/or the respective second radio network node 112, e.g., a base station and host computer discussed in the preceding paragraphs will now be described with reference to Figure 22. In communication system 2200, such as the communications network 100, host computer 2210 comprises hardware 2215 including communication interface 2216 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 2200. Host computer 2210 further comprises processing circuitry 2218, which may have storage and/or processing capabilities. In particular, processing circuitry 2218 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Host computer 2210 further comprises software 2211 , which is stored in or accessible by host computer 2210 and executable by processing circuitry 2218. Software 2211 includes host application 2212. Host application 2212 may be operable to provide a service to a remote user, such as UE 2230 connecting via OTT connection 2250 terminating at UE 2230 and host computer 2210. In providing the service to the remote user, host application 2212 may provide user data which is transmitted using OTT connection 2250.

Communication system 2200 further includes the first node 130, the first network node 101 , the respective second network node 102, the first radio network node 111 and/or the respective second radio network node 112, exemplified in Figure 22 as a base station 2220 provided in a telecommunication system and comprising hardware 2225 enabling it to communicate with host computer 2210 and with UE 2230. Hardware 2225 may include communication interface 2226 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 2200, as well as radio interface 2227 for setting up and maintaining at least wireless connection 2270 with the one or more devices 150, exemplified in Figure 22 as a UE 2230 located in a coverage area (not shown in Figure 22) served by base station 2220. Communication interface 2226 may be configured to facilitate connection 2260 to host computer 2210. Connection 2260 may be direct or it may pass through a core network (not shown in Figure 22) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware 2225 of base station 2220 further includes processing circuitry 2228, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Base station 2220 further has software 2221 stored internally or accessible via an external connection.

Communication system 2200 further includes UE 2230 already referred to. Its hardware 2235 may include radio interface 2237 configured to set up and maintain wireless connection 2270 with a base station serving a coverage area in which UE 2230 is currently located. Hardware 2235 of UE 2230 further includes processing circuitry 2238, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. UE 2230 further comprises software 2231 , which is stored in or accessible by UE 2230 and executable by processing circuitry 2238. Software 2231 includes client application 2232. Client application 2232 may be operable to provide a service to a human or non-human user via UE 2230, with the support of host computer 2210. In host computer 2210, an executing host application 2212 may communicate with the executing client application 2232 via OTT connection 2250 terminating at UE 2230 and host computer 2210. In providing the service to the user, client application 2232 may receive request data from host application 2212 and provide user data in response to the request data. OTT connection 2250 may transfer both the request data and the user data. Client application 2232 may interact with the user to generate the user data that it provides.

It is noted that host computer 2210, base station 2220 and UE 2230 illustrated in Figure 22 may be similar or identical to host computer 2130, one of base stations 2112a, 2112b, 2112c and one of UEs 2191 , 2192 of Figure 21 , respectively. This is to say, the inner workings of these entities may be as shown in Figure 22 and independently, the surrounding network topology may be that of Figure 21.

In Figure 22, OTT connection 2250 has been drawn abstractly to illustrate the communication between host computer 2210 and UE 2230 via base station 2220, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from UE 2230 or from the service provider operating host computer 2210, or both. While OTT connection 2250 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

Wireless connection 2270 between UE 2230 and base station 2220 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to UE 2230 using OTT connection 2250, in which wireless connection 2270 forms the last segment. More precisely, the teachings of these embodiments may improve the latency, signalling overhead, and service interruption and thereby provide benefits such as reduced user waiting time, better responsiveness and extended battery lifetime.

A measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring OTT connection 2250 between host computer 2210 and UE 2230, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection 2250 may be implemented in software 2211 and hardware 2215 of host computer 2210 or in software 2231 and hardware 2235 of UE 2230, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which OTT connection 2250 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 2211 , 2231 may compute or estimate the monitored quantities. The reconfiguring of OTT connection 2250 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station 2220, and it may be unknown or imperceptible to base station 2220. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating host computer 2210’s measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that software 2211 and 2231 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection 2250 while it monitors propagation times, errors etc. The first node 130 embodiments relate to Figure 8, Figures 11-14, Figure 15 and Figures 21-26.

The first node 130 may comprise an interface unit to facilitate communications between the first node 130 and other nodes or devices, e.g., the first network node 101, the one or more second network nodes 110, the second network node 102, the third network node 103, the first radio network node 111, the one or more second radio network nodes 112, e.g., the respective second radio network node 112, the one or more devices 150, the host computer 2210, and/or any of the other nodes or devices. In some particular examples, the interface may, for example, include a transceiver configured to transmit and receive radio signals over an air interface in accordance with a suitable standard.

The network node 101 , 102, 140 embodiments relate to Figure 9, Figures 11-14, Figure 16 and Figures 21-26.

The network node 101, 102, 140 may comprise an interface unit to facilitate communications between the network node 101 , 102, 140 and other nodes or devices, e.g., the first node 130, the first network node 101, the one or more second network nodes 110, the second network node 102, the third network node 103, the first radio network node 111 , the one or more second radio network nodes 112, e.g., the respective second radio network node 112, the one or more devices 150, the host computer 2210, and/or any of the other nodes or devices. In some particular examples, the interface may, for example, include a transceiver configured to transmit and receive radio signals over an air interface in accordance with a suitable standard.

The network node 101, 102, 140 may comprise an arrangement as shown in Figure 16 or in Figure 22.

The radio network node 111, 112 embodiments relate to Figure 10, Figures 11-14, Figure 17 and Figures 21-26.

The radio network node 111, 112 may comprise an interface unit to facilitate communications between the radio network node 111, 112 and other nodes or devices, e.g., the first node 130, the first network node 101, the one or more second network nodes 110, the second network node 102, the third network node 103, the first radio network node 111 , the one or more second radio network nodes 112, e.g., the respective second radio network node 112, the one or more devices 150, the host computer 2210, and/or any of the other nodes or devices. In some particular examples, the interface may, for example, include a transceiver configured to transmit and receive radio signals over an air interface in accordance with a suitable standard.

The radio network node 111 , 112 may comprise an arrangement as shown in Figure 17 or in Figure 22.

Figure 23: Methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments

Figure 23 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 21 and 22. For simplicity of the present disclosure, only drawing references to Figure 23 will be included in this section. In step 2310, the host computer provides user data. In substep 2311 (which may be optional) of step 2310, the host computer provides the user data by executing a host application. In step 2320, the host computer initiates a transmission carrying the user data to the UE. In step 2330 (which may be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 2340 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

Figure 24: Methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments

Figure 24 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 21 and 22. For simplicity of the present disclosure, only drawing references to Figure 24 will be included in this section. In step 2410 of the method, the host computer provides user data. In an optional substep (not shown) the host computer provides the user data by executing a host application. In step 2420, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In step 2430 (which may be optional), the UE receives the user data carried in the transmission. Figure 25: Methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments

Figure 25 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 21 and 22. For simplicity of the present disclosure, only drawing references to Figure 25 will be included in this section. In step 2510 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 2520, the UE provides user data. In substep 2521 (which may be optional) of step 2520, the UE provides the user data by executing a client application. In substep 2511 (which may be optional) of step 2510, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep 2530 (which may be optional), transmission of the user data to the host computer. In step 2540 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

Figure 26: Methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments

Figure 26 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 21 and 22. For simplicity of the present disclosure, only drawing references to Figure 26 will be included in this section. In step 2610 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step 2620 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 2630 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.

The term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.

Further numbered embodiments

1 . A base station configured to communicate with a user equipment (UE), the base station comprising a radio interface and processing circuitry configured to perform one or more of the actions described herein as performed by the first node 130, the first network node 101 , the respective second network node 102, the first radio network node 111 and/or the respective second radio network node 112.

5. A communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE), wherein the cellular network comprises a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform one or more of the actions described herein as performed by the first node 130, the first network node 101 , the respective second network node 102, the first radio network node 111 and/or the respective second radio network node 112.

6. The communication system of embodiment 5, further including the base station.

7. The communication system of embodiment 6, further including the UE, wherein the UE is configured to communicate with the base station. 8. The communication system of embodiment 7, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application.

11. A method implemented in a base station, comprising one or more of the actions described herein as performed by the first node 130, the first network node 101, the respective second network node 102, the first radio network node 111 and/or the respective second radio network node 112.

15. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs one or more of the actions described herein as performed by the first node 130, the first network node 101, the respective second network node 102, the first radio network node 111 and/or the respective second radio network node 112.

16. The method of embodiment 15, further comprising: at the base station, transmitting the user data.

17. The method of embodiment 16, wherein the user data is provided at the host computer by executing a host application, the method further comprising: at the UE, executing a client application associated with the host application.

21. A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to perform one or more of the actions described herein as performed by the one or more devices 150.

25. A communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to perform one or more of the actions described herein as performed by the one or more devices 150.

26. The communication system of embodiment 25, further including the UE.

27. The communication system of embodiment 26, wherein the cellular network further includes a base station configured to communicate with the UE.

28. The communication system of embodiment 26 or 27, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE’s processing circuitry is configured to execute a client application associated with the host application.

31. A method implemented in a user equipment (UE), comprising one or more of the actions described herein as performed by the one or more devices 150.

35. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs one or more of the actions described herein as performed by the one or more devices 150.

36. The method of embodiment 35, further comprising: at the UE, receiving the user data from the base station.

41. A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to perform one or more of the actions described herein as performed by the one or more devices 150.

45. A communication system including a host computer comprising: a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to: perform one or more of the actions described herein as performed by the one or more devices 150.

46. The communication system of embodiment 45, further including the UE.

47. The communication system of embodiment 46, further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.

48. The communication system of embodiment 46 or 47, wherein: the processing circuitry of the host computer is configured to execute a host application; and the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.

49. The communication system of embodiment 46 or 47, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing request data; and the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data.

51. A method implemented in a user equipment (UE), comprising one or more of the actions described herein as performed by the one or more devices 150.

52. The method of embodiment 51 , further comprising: providing user data; and forwarding the user data to a host computer via the transmission to the base station.

55. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, receiving user data transmitted to the base station from the UE, wherein the UE performs one or more of the actions described herein as performed by the one or more devices 150. 56. The method of embodiment 55, further comprising: at the UE, providing the user data to the base station.

57. The method of embodiment 56, further comprising: at the UE, executing a client application, thereby providing the user data to be transmitted; and at the host computer, executing a host application associated with the client application.

58. The method of embodiment 56, further comprising: at the UE, executing a client application; and at the UE, receiving input data to the client application, the input data being provided at the host computer by executing a host application associated with the client application, wherein the user data to be transmitted is provided by the client application in response to the input data.

61. A base station configured to communicate with a user equipment (UE), the base station comprising a radio interface and processing circuitry configured to perform one or more of the actions described herein as performed by the first node 130, the first network node 101 , the respective second network node 102, the first radio network node 111 and/or the respective second radio network node 112.

65. A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station’s processing circuitry configured to perform one or more of the actions described herein as performed by the first node 130, the first network node 101 , the respective second network node 102, the first radio network node 111 and/or the respective second radio network node 112.

66. The communication system of embodiment 65, further including the base station.

67. The communication system of embodiment 66, further including the UE, wherein the UE is configured to communicate with the base station.

68. The communication system of embodiment 67, wherein: the processing circuitry of the host computer is configured to execute a host application; the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.

71. A method implemented in a base station, comprising one or more of the actions described herein as performed by the first node 130, the first network node 101, the respective second network node 102, the first radio network node 111 and/or the respective second radio network node 112.

75. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs one or more of the actions described herein as performed by the one or more devices 150.

76. The method of embodiment 75, further comprising: at the base station, receiving the user data from the UE.

77. The method of embodiment 76, further comprising: at the base station, initiating a transmission of the received user data to the host computer.

REFERENCES

1.TS 38.331 v 16.6.0 - Radio Resource Control (RRC) protocol specification

2.TR 38.874 v 168.0 - Study on Integrated Access and Backhaul

3.TS 38.423 v 16.8.0 - Xn application protocol (XnAP)

4.TS 38.473, v16.8.0 - F1 application protocol (F1AP)

5.TS 38.413, v16.8.0 - NG application protocol (NGAP)

Claims

CLAIMS:

1 . A method performed by a first node (130) operating in a communications network (100), the first node (130) being served by a first network node (101), the method being for handling configuration of the first node (130), and wherein the method further comprises:

- receiving (801), from a network node (101 , 102, 140), one or more first indications, the one or more first indications respectively indicating one or more first configurations to be applied by the first node (130) upon fulfilment of one or more respective first criteria, wherein the first node (130) is provided a wired connection to a core network node (140) of the communications network (100) by the first network node (101) via at least a wireless connection, and wherein the first node (130) is capable to be provided a respective wired connection to the core network node (140) of the communications network (100) by a respective second network node (102) via at least another respective wireless connection,

- storing (804) the one or more first configurations at the first node (130), and

- applying (806), out of the stored one or more first configurations, a respective first configuration upon fulfilment of the one or more respective first criteria, wherein the receiving (801) comprises receiving a plurality of first configurations comprising the respective first configuration, the storing (804) comprises storing the plurality of first configurations and the applying (806) comprises applying the respective first configuration out of the stored plurality of first configurations, and wherein each of the one or more first configurations is a Backhaul Adaptation Protocol, BAP, configuration.

2. The method according to claim 1 wherein at least one of:

- the first node (130) is a mobile IAB node,

- the first node (130) is a node with no descendants, - the applying (806) is performed during a movement of the first node (130) along a route (170),

- the first node (130) is served by the first network node (101) through at least one first radio network node (111), the first radio network node (111) having respective wireless connections with the first node (130) and the first network node (101),

- the first radio network node (111) is a source ancestor I AB node,

- the first node (130) is to be served by the respective second network node (102) through at least one respective second radio network node (112), the respective second radio network node (112) having other respective wireless connections with the first node (130) and the respective second network node (102),

- each of the one or more first configurations is a respective Backhaul, BH, Radio Link Control, RLC, channel, configuration, used to configure a respective RLC entity,

- the one or more first configurations are identified by a respective identifier,

- the respective identifier is a newly defined identifier,

- the one or more first indications are one of: i. received in a standalone message, ii. comprising the one or more respective first criteria upon the fulfilment of which the respective first configuration is to be activated, iii. one or more enhanced messages,

- the one or more respective first criteria comprise at least one of: i. the first node (130) identifying, a respective cell (122), indicated in the respective first configuration, ii. the first node (130) entering a geographical area, indicated in the respective first configuration, and iii. the first node (130) establishing a connection, to the respective second network node (102), and

- the first node (130) receives a further indication from the first network node (101), the further indication indicating an order in which a plurality of respective second network nodes (110) comprising the respective second network node (102), and/or a plurality of second radio network nodes (112) comprising the respective second radio network node (112), are to serve the first node (130).

3. The method according to claim 2, wherein each of the one or more first configurations comprises at least one of:

- a respective BAP configuration comprising respective at least one of: i. one or more BAP addresses, for the first node (130) ii. one or more downlink, DL, and uplink, UL, BAP routing identifiers, IDs, for the first node (130), iii. one or more second configurations for backhaul mapping of UL traffic originating at the first node (130) or one or more devices (150) served by the first node (130), iv. a BAP routing configuration, and v. one or more third configurations for BAP header rewriting, vi. one or more fourth configurations for UL and/or DL local rerouting of traffic, and

- the respective BH RLC channel configuration, used to configure the respective RLC entity.

4. The method according to any of claims 1-3, wherein the first node (130) is served by the first network node (101) with a fifth configuration, and wherein the method further comprises at least one of:

- receiving (802), from the network node (101 , 102, 140), one or more second indications, the one or more second indications indicating, to activate the respective first configuration,

- receiving (803), from the network node (101, 102, 140), one or more third indications, the one or more third indications indicating to store at least one of the one or more first configurations and the one or more second indications, until application of the respective first configuration, and

- receiving (805), from the network node (101, 102, 140), a fourth indication, the fourth indication indicating that the fifth configuration is no longer valid.

5. The method according to claim 4, wherein at least one of:

- at least one of the one or more first indications and the one or more second indications are received during a procedure of setting up an F1 connection, - the one or more first indications are received together with a conditional F1 setup message,

- the one or more respective first criteria comprise at least one of: a) executing a handover to the respective cell (122), and b) the first node (130) establishing a connection, to the respective second network node (102),

- the one or more second indications are respectively comprised in a control Protocol Data Unit, PDU. The method according to claim 5, wherein the PDU comprises at least one of:

- a sixth indication identifying the respective first configuration, and

- a seventh indication indicating a final destination of the first node (130) when served by the respective second network node (102). The method according to any of claims 4-6, wherein the first node (130) is served by the first network node (101) with the fifth configuration, and wherein the method further comprises, after activating the respective first configuration:

- performing (807) an action on the fifth configuration selected from: i. deleting the fifth configuration and keeping other previous BAP configurations and/or BH RLC channel configurations, ii. deactivating the fifth configuration, iii. keeping the fifth configuration in a list of previous BAP configurations and/or BH RLC channel configurations, and iv. deleting the fifth configuration and any other previous BAP configurations and/or BH RLC channel configurations. A method performed by a network node (101 , 102, 140) operating in a communications network (100), the method being for handling configuration of a first node (130), wherein the method further comprises:

- sending (904) one or more first indications to at least one of: i. the first node (130) served by a first network node (101) and ii. at least one first radio network node (111), wherein the first node (130) is served by the first network node (101) through the at least one first radio network node (111), the at least one first radio network node (111), having respective wireless connections with the first node (130) and the first network node (101), the one or more first indications indicating one or more first configurations to be applied by the first node (130) upon fulfilment of one or more respective first criteria, wherein the first node (130) is provided a wired connection to a core network node (140) of the communications network (100) by the first network node (101) via at least a wireless connection, and wherein the first node (130) is capable to be provided a respective wired connection to the core network node (140) of the communications network (100) by a respective second network node (102) via at least another respective wireless connection, wherein the sending (904) comprises sending a plurality of first configurations comprising a respective first configuration to be applied by the first node (130) upon fulfilment of the respective one or more first criteria, and wherein each of the one or more first configurations is a Backhaul Adaptation Protocol, BAP, configuration. The method according to claim 8 wherein at least one of:

- each of the at least one first radio network node (111) is an ancestor node,

- the one or more first indications originate at the core network node (140), the core network node (140) being an Operations Administration and Maintenance, OAM, node, - the first node (130) is a mobile I AB node,

- the first node (130) is a node with no descendants,

- the sending (904) is performed during a movement of the first node (130) along a route (170),

- the first radio network node (111) is a source ancestor IAB node,

- each of the one or more first configurations is a respective Backhaul, BH, Radio Link Control, RLC, channel configuration, used to configure a respective RLC entity,

- the respective identifier is a newly defined identifier,

- the one or more respective first criteria comprise at least one of: i. the first node (130) identifying a respective cell (122), ii. the first node (130) entering a geographical area, and iii. the first node (130) establishing a connection, to the respective second network node (102), and

- the network node (101, 102, 140) sends to the first node (130) a further indication from the first network node (101), the further indication indicating an order in which a plurality of respective second network nodes (110) comprising the respective second network node (102) and/or a plurality of second radio network nodes (112) comprising the respective second radio network node

(112) are to serve the first node (130). The method according to claim 9, wherein each of the one or more first configurations comprises at least one of:

- a respective BAP configuration comprising respective at least one of: i. one or more BAP addresses for the first node (130) ii. one or more downlink, DL, and uplink, UL, BAP routing identifiers, IDs, for the first node (130), iii. one or more second configurations for backhaul mapping of UL traffic originating at the first node (130) or one or more devices (150) served by the first node (130), iv. a BAP routing configuration, v. one or more third configurations for BAP header rewriting, and vi. one or more fourth configurations for UL and/or DL local rerouting of traffic, and

- the respective BH RLC channel configuration, used to configure the respective RLC entity. The method according to any of claims 8-10, wherein the network node (101 , 102, 140) is one of the first network node (101) and the respective second network node (102), wherein the first node (130) is served by the first network node (101) with a fifth configuration, and wherein the method further comprises at least one of:

- sending (905), to at least one of the first node (130) and a radio network node (111 , 112), one or more second indications, the one or more second indications indicating to activate the respective first configuration,

- sending (908), to at least one of the first node (130) and the at least one first network node (111), a fourth indication, the fourth indication indicating that the fifth configuration is no longer valid. The method according to claim 11 , wherein at least one of: at least one of the one or more first indications and the one or more second indications are sent during a procedure of setting up an F1 connection, - the one or more first indications are sent together with a conditional F1 setup message,

- the one or more respective first criteria comprise at least one of: a) executing a handover to a respective cell (122), and b) the first node (130) establishing a connection, to the respective second network node (102),

- the one or more second indications are respectively comprised in a control Protocol Data Unit, PDU. The method according to claim 12, wherein the PDU comprises at least one of:

- a sixth indication identifying the respective first configuration, and

- a seventh indication indicating a final destination of the first node (130) when served by the respective second network node (102). The method according to any of claims 11-13, wherein the network node (101, 102, 140) is the first network node (101), wherein the first network node (101) serves the first node (130) with the fifth configuration, and wherein the method further comprises, after activating the respective first configuration:

- performing (910) an action on the fifth configuration selected from: i. deleting the fifth configuration and keeping other previous BAP configurations and/or BH RLC channel configurations, ii. deactivating the fifth configuration, iii. keeping the fifth configuration in a list of previous BAP configurations and/or BH RLC channel configurations, and iv. deleting the fifth configuration and any other previous BAP configurations and/or BH RLC channel configurations. The method according to any of claims 8-14, further comprising:

- obtaining (902) the one or more first configurations from at least one of: i. one or more respective second network nodes (110) comprising the respective second network node (102), wherein the respective one or more second network nodes (110) have a capability to provide, to the first node (130), a respective wired connection to the core network node (140) of the communications network (100) via at least a respective wireless connection, and ii. a third network node (103) managing configuration of nodes comprised in the communications network (100). The method according to claim 15, further comprising:

- obtaining (903), from at least one of the one or more respective second network nodes (110), the third network node (103) and the core network node (140), at least one of: i. an eighth indication indicating an order in which the plurality of respective second network nodes (110) and/or a plurality of respective second radio network nodes (112) comprising the respective second radio network node (112) are to serve the first node (130), and ii. a ninth indication indicating a list of the one or more respective second network nodes (110) from which the first network node (101) is to request the respective first configuration of the one or more first configurations. The method according to claim 16, wherein at least one of the obtaining (902) of the one or more first configurations and the obtaining (903) of the at least one of the eighth indication and the ninth indication is performed via one of: i. one or more XnAP messages, ii. by means of signalling traversing the core network (140) of the communications network (100). The method according to any of claims 16-17, further comprising at least one of:

- storing (907) the one or more first configurations, and

- applying (909) the stored respective first configuration upon fulfilment of the one or more respective first criteria. The method according to claim 18, wherein at least one of:

- the core network node (140) is an GAM node, and

- the first message comprises information about a fifth configuration. A method performed by a radio network node (111, 112) operating in a communications network (100), the method being for handling configuration of a first node (130), wherein the first node (130) is provided a wired connection to a core network node (140) of the communications network (100) by a first network node (101) via at least a wireless connection, and wherein the first node (130) is capable to be provided a respective wired connection to the core network node (140) of the communications network (100) by a respective second network node (102) via at least another respective wireless connection, and wherein the method further comprises:

- receiving (1002), from a network node (101 , 102, 140), an indication, wherein one of: i. with the proviso that the radio network node (111 , 112) is a first radio network node (111), wherein the first node (130) is served by the first network node (101) through at least the first radio network node (111), the first radio network node (111) having respective wireless connections with the first node (130) and the first network node (101), the indication is a fourth indication, wherein the fourth indication indicates that a fifth configuration with which the first network node (101) serves the first node (130) is no longer valid, and ii. with the proviso the radio network node (111, 112) is a respective second radio network node (112), wherein the first node (130) is to be served by the respective second network node (102) through at least the respective second radio network node (112), the respective second radio network node (112) having other respective wireless connections with the first node (130) and the respective second network node (102), the indication is a second indication, wherein the second indication indicates to activate a respective first configuration stored at the first radio network node (111).

21. The method according to claim 20, further comprising at least one of:

- receiving (1001), from the network node (101 , 102, 140), a first indication, the first indication indicating the respective first configuration to be applied by the first node (130) upon fulfilment of one or more respective first criteria,

- storing (1004) the respective first configuration at the radio network node (111, 112), and

- applying (1005) the second or fourth indication immediately or upon fulfilment of the one or more respective first criteria.

22. The method according to claim 21 wherein at least one of:

- the respective first configuration is a Backhaul Adaptation Protocol, BAP, configuration,

- the respective first configuration is a respective Backhaul, BH, Radio Link Control, RLC, channel, configuration, used to configure a respective RLC entity,

- the first node (130) is a mobile IAB node,

- the first node (130) is a node with no descendants,

- the applying (1005) is performed during a movement of the first node (130) along a route (170),

- the first radio network node (111) is a source ancestor IAB node,

- the first indication is one of: i. received in a standalone message, ii. comprising the one or more respective first criteria upon the fulfilment of which the respective first configuration is to be activated, and iii. an enhanced message, and

- the one or more respective first criteria comprise at least one of: i. the first node (130) identifying, a respective cell (122), ii. the first node (130) entering a geographical area, indicated in the respective first configuration, and iii. the first node (130) establishing a connection, to the respective second network node (102).

23. The method according to claim 22, wherein the respective first configuration comprises at least one of: a respective BAP configuration comprising respective at least one of: i. one or more BAP addresses, for the first node (130) ii. one or more downlink, DL, and uplink, UL, BAP routing identifiers, IDs, for the first node (130), iii. one or more second configurations for backhaul mapping of UL traffic originating at the first node (130) or one or more devices (150) served by the first node (130), iv. a BAP routing configuration, v. one or more third configurations for BAP header rewriting, and vi. one or more fourth configurations for UL and/or DL local rerouting of traffic, and

- the respective BH RLC channel configuration, used to configure the respective RLC entity. The method according to any of claims 20-23, wherein the first node (130) is served by the first network node (101) with a fifth configuration, and wherein the method further comprises:

- receiving (1003), from the network node (101 , 102, 140), a third indication, the third indication indicating to store at least one of the respective first configuration and the second indication, until application of the respective first configuration. The method according to claim 24, wherein at least one of:

- at least one of the first indication and the second indication are received during a procedure of setting up an F1 connection,

- the receiving (1001) comprises receiving a plurality of configurations comprising the respective first configuration, each configuration in the plurality comprising a respective identifier,

- the one or more respective first criteria comprise at least one of: a) the first node (130) executing a handover to a cell (122), and b) the first node (130) establishing a connection, to the respective second network node (102),

- the second indication is comprised in a control Protocol Data Unit, PDU. The method according to claim 25, wherein the PDU comprises at least one of:

- a sixth indication identifying the respective first configuration, and

- a seventh indication indicating a final destination of the first node (130) when served by the respective second network node (102). The method according to any of claims 24-26, wherein the first node (130) is served by the first network node (101) with the fifth configuration, and wherein the method further comprises, after activating the respective first configuration:

- performing (1006) an action on the fifth configuration selected from: i. deleting the fifth configuration and keeping other previous BAP configurations and/or BH RLC channel configurations, ii. deactivating the fifth configuration, iii. keeping the fifth configuration in a list of previous BAP configurations and/or BH RLC channel configurations, and iv. deleting the fifth configuration and any other previous BAP configurations and/or BH RLC channel configurations. The method according to any of claims claim 20-27, wherein the respective second radio network node (112) is to directly serve the first node (130) as a new parent, and wherein the second indication is an existing F1AP UE CONTEXT SETUP REQUEST message with a particular, identifier pair, wherein the identifier pair was previously associated to a BAP routing configuration. The method according to claim 28, wherein the second indication activates a respective BH RLC channel configuration at the respective second radio network node (112). A first node (130) configured to operate in a communications network (100), the first node (130) being configured to be served by a first network node (101), the first node (130) being for handling configuration of the first node (130), and wherein the first node (130) is further configured to:

- receive, from a network node (101 , 102, 140), one or more first indications, the one or more first indications are configured to respectively indicate one or more first configurations to be applied by the first node (130) upon fulfilment of one or more respective first criteria, wherein the first node (130) is configured to be provided a wired connection to a core network node (140) of the communications network (100) by the first network node (101) via at least a wireless connection, and wherein the first node (130) is configured to be capable to be provided a respective wired connection to the core network node (140) of the communications network (100) by a respective second network node (102) via at least another respective wireless connection, - store the one or more first configurations at the first node (130), and

- apply, out of the stored one or more first configurations, a respective first configuration upon fulfilment of the one or more respective first criteria, wherein the receiving is configured to comprise receiving a plurality of first configurations configured to comprise the respective first configuration, the storing is configured to comprise storing the plurality of first configurations and the applying is configured to comprise applying the respective first configuration out of the stored plurality of first configurations, and wherein each of the one or more first configurations is configured to be a Backhaul Adaptation Protocol, BAP, configuration. first node (130) according to claim 30 wherein at least one of:

- the first node (130) is configured to be a first Integrated Access and Backhaul,

I AB, node, the first network node (101) is configured to be a Donor Centralized Unit, CU, and the respective second network node (102) is configured to be a second Donor CU,

- the one or more first indications are configured to originate at the core network node (140), the core network node (140) being configured to be an Operations Administration and Maintenance, OAM, node,

- the first node (130) is configured to be a mobile IAB node,

- the first node (130) is configured to be a node with no descendants,

- the applying (806) is configured to be performed during a movement of the first node (130) along a route (170),

- the first node (130) is configured to be served by the first network node (101) through at least one first radio network node (111), the first radio network node (111) being configured to have respective wireless connections with the first node (130) and the first network node (101),

- the first radio network node (111) is configured to be a source ancestor IAB node,

- the first node (130) is to be served by the respective second network node (102) through at least one respective second radio network node (112), the respective second radio network node (112) being configured to have other respective wireless connections with the first node (130) and respective the second network node (102), - each of the one or more first configurations is configured to be a respective Backhaul, BH, Radio Link Control, RLC, channel, configuration, used to configure a respective RLC entity,

- the respective second radio network node (112) is configured to be a respective target ancestor IAB node,

- the respective second radio network node (112) is configured to be a respective target parent IAB node,

- the one or more first configurations are configured to be identified by a respective identifier,

- the respective identifier is configured to be a newly defined identifier,

- the one or more first indications are configured to be one of: i. received in a standalone message, ii. comprising the one or more respective first criteria upon the fulfilment of which the respective first configuration is to be activated, iii. one or more enhanced messages,

- the one or more respective first criteria are configured to comprise at least one of: i. the first node (130) identifying, a respective cell (122), configured to be indicated in the respective first configuration, ii. the first node (130) entering a geographical area, configured to be indicated in the respective first configuration, and iii. the first node (130) establishing a connection, to the respective second network node (102), and

- the first node (130) is configured to receive a further indication from the first network node (101), the further indication being configured to indicate an order in which a plurality of respective second network nodes (110) configured comprise the respective second network node (102), and/or a plurality of second radio network nodes (112) configured to comprise the respective second radio network node (112), are to serve the first node (130). The first node (130) according to claim 31 , wherein each of the one or more first configurations is configured to comprise at least one of:

- a respective BAP configuration configured to comprise respective at least one of: i. one or more BAP addresses, for the first node (130) ii. one or more downlink, DL, and uplink, UL, BAP routing identifiers, IDs, for the first node (130), iii. one or more second configurations for backhaul mapping of UL traffic configured to originate at the first node (130) or one or more devices (150) configured to be served by the first node (130), iv. a BAP routing configuration, and v. one or more third configurations for BAP header rewriting, vi. one or more fourth configurations for UL and/or DL local rerouting of traffic, and

- the respective BH RLC channel configuration, configured to be used to configure the respective RLC entity. The first node (130) according to any of claims 30-32, wherein the first node (130) is configured to be served by the first network node (101) with a fifth configuration, and wherein the first node (130) is further configured to at least one of:

- receive, from the network node (101 , 102, 140), one or more second indications, the one or more second indications being configured to indicate to activate the respective first configuration,

- receive, from the network node (101 , 102, 140), one or more third indications, the one or more third indications configured to indicate to store at least one of the one or more first configurations and the one or more second indications, until application of the respective first configuration, and

- receive, from the network node (101 , 102, 140), a fourth indication, the fourth indication being configured to indicate that the fifth configuration is no longer valid. The first node (130) according to claim 33, wherein at least one of:

- at least one of the one or more first indications and the one or more second indications are configured to be received during a procedure of setting up an F1 connection,

- the one or more first indications are configured to be received together with a conditional F1 setup message,

- the receiving is configured to comprise receiving a plurality of configurations comprising the first configuration, each configuration in the plurality being configured to comprise a respective identifier, - at least one of the one or more first indications and the one or more second indications are configured to be comprised in a Radio Resource Control, RRC, message,

- at least one of the one or more first indications and the one or more second indications are configured to be received via F1AP,

- at least one of the one or more first indications and the one or more second indications are configured to be received via Downlink Control Information, DCI, or via a Medium Access Control, MAC, control element,

- the one or more respective first criteria are configured to comprise at least one of: a) executing a handover to the respective cell (122), and b) the first node (130) establishing a connection, to the respective second network node (102),

- the one or more second indications are configured to be received as part of, or together with, a handover command to the respective cell (122), and

- the one or more second indications are configured to be respectively comprised in a control Protocol Data Unit, PDU.

35. The first node (130) according to claim 34, wherein the PDU is configured to comprise at least one of:

- a fifth indication configured to indicate an activation or deactivation flag of the respective first configuration,

- a sixth indication configured to identify the respective first configuration, and

- a seventh indication configured to indicate a final destination of the first node (130) when served by the respective second network node (102).

36. The first node (130) according to any of claims 33-35, wherein the first node (130) is configured to be served by the first network node (101) with the fifth configuration, and wherein the first node (130) is further configured to, after activating the respective first configuration:

- perform an action on the fifth configuration configured to be selected from: i. deleting the fifth configuration and keeping other previous BAP configurations and/or BH RLC channel configurations, ii. deactivating the fifth configuration, iii. keeping the fifth configuration in a list of previous BAP configurations and/or BH RLC channel configurations, and iv. deleting the fifth configuration and any other previous BAP configurations and/or BH RLC channel configurations. A network node (101 , 102, 140) configured to operate in a communications network (100), the network node (101 , 102, 140) being for handling configuration of a first node (130), wherein the network node (101 , 102, 140) is further configured to:

- send one or more first indications to at least one of: i. the first node (130) configured to be served by a first network node (101) and ii. at least one first radio network node (111), wherein the first node (130) is configured to be served by the first network node (101) through the at least one first radio network node (111), the at least one first radio network node (111), being configured to have respective wireless connections with the first node (130) and the first network node (101), the one or more first indications being configured to indicate one or more first configurations to be applied by the first node (130) upon fulfilment of one or more respective first criteria, wherein the first node (130) is configured to be provided a wired connection to a core network node (140) of the communications network (100) by the first network node (101) via at least a wireless connection, and wherein the first node (130) is configured to be capable to be provided a respective wired connection to the core network node (140) of the communications network (100) by a respective second network node (102) via at least another respective wireless connection, wherein the sending is configured to comprise sending a plurality of first configurations configured to comprise a respective first configuration to be applied by the first node (130) upon fulfilment of the respective one or more first criteria, and wherein each of the one or more first configurations is configured to be a Backhaul Adaptation Protocol, BAP, configuration. The network node (101, 102, 140) according to claim 37 wherein at least one of:

- each of the at least one first radio network node (111) is configured to be an ancestor node, - the one or more first indications are configured to originate at the core network node (140), the core network node (140) being configured to be an Operations Administration and Maintenance, OAM, node,

- the first node (130) is configured to be a mobile IAB node,

- the first node (130) is configured to be a node with no descendants,

- the sending (904) is configured to be performed during a movement of the first node (130) along a route (170),

- the first node (130) is to be served by the respective second network node (102) through at least one respective second radio network node (112), the respective second radio network node (112) being configured to have other respective wireless connections with the first node (130) and the respective second network node (102),

- each of the one or more first configurations is configured to be a respective Backhaul, BH, Radio Link Control, RLC, channel configuration, used to configure a respective RLC entity,

- the respective identifier is configured to be a newly defined identifier,

- the one or more respective first criteria are configured to comprise at least one of: i. the first node (130) identifying a respective cell (122), ii. the first node (130) entering a geographical area, and iii. the first node (130) establishing a connection, to the respective second network node (102), and - the network node (101, 102, 140) is configured to send to the first node (130) a further indication from the first network node (101), the further indication being configured to indicate an order in which a plurality of respective second network nodes (110) configured to comprise the respective second network node (102) and/or a plurality of second radio network nodes (112) configured to comprising the respective second radio network node (112) are to serve the first node (130).

39. The network node (101 , 102, 140) according to claim 38, wherein each of the one or more first configurations is configured to comprise at least one of:

- a respective BAP configuration comprising respective at least one of: i. one or more BAP addresses for the first node (130) ii. one or more downlink, DL, and uplink, UL, BAP routing identifiers, IDs, for the first node (130), iii. one or more second configurations for backhaul mapping of UL traffic configured to originate at the first node (130) or one or more devices (150) configured to be served by the first node (130), iv. a BAP routing configuration, v. one or more third configurations for BAP header rewriting, and vi. one or more fourth configurations for UL and/or DL local rerouting of traffic, and

- the respective BH RLC channel configuration, configured to be used to configure the respective RLC entity.

40. The network node (101, 102, 140) according to any of claims 37-39, wherein the network node (101 , 102, 140) is configured to be one of the first network node (101) and the respective second network node (102), wherein the first node (130) is configured to be served by the first network node (101) with a fifth configuration, and wherein the network node (101 , 102, 140) is further configured to at least one of:

- send, to at least one of the first node (130) and a radio network node (111,

112), one or more second indications, the one or more second indications being configured to indicate to activate the respective first configuration,

- send, to at least one of the first node (130) and the radio network node (111, 112), one or more third indications, the one or more third indications being configured to indicate to store at least one of the one or more first configurations and the one or more second indications, until application of the respective first configuration, and

- send, to at least one of the first node (130) and the at least one first network node (111), a fourth indication, the fourth indication being configured to indicate that the fifth configuration is no longer valid. The network node (101 , 102, 140) according to claim 40, wherein at least one of:

- at least one of the one or more first indications and the one or more second indications are configured to be sent during a procedure of setting up an F1 connection,

- the one or more first indications are configured to be sent together with a conditional F1 setup message,

- the sending is configured to comprise sending a plurality of configurations configured to comprise the first configuration, each configuration in the plurality being configured to comprise a respective identifier,

- at least one of the one or more first indications and the one or more second indications are configured to be comprised in a Radio Resource Control, RRC, message, and

- the one or more respective first criteria are configured to comprise at least one of: a) executing a handover to a respective cell (122), and b) the first node (130) establishing a connection, to the respective second network node (102),

- the one or more second indications are configured to be sent as part of, or together with, a handover command to the respective cell (122), and

- the one or more second indications are configured to be respectively comprised in a control Protocol Data Unit, PDU. The network node (101 , 102, 140) according to claim 41, wherein the PDU is configured to comprise at least one of:

- a sixth indication configured to identify the respective first configuration, and a seventh indication configured to indicate a final destination of the first node (130) when served by the respective second network node (102). The network node (101, 102, 140) according to any of claims 40-42, wherein the network node (101 , 102, 140) is configured to be the first network node (101), wherein the first network node (101) is configured to serve the first node (130) with the fifth configuration, and wherein the network node (101, 102, 140) is further configured to, after activating the first configuration:

- perform an action on the fifth configuration configured to be selected from: i. deleting the fifth configuration and keeping other previous BAP configurations and/or BH RLC channel configurations, ii. deactivating the fifth configuration, iii. keeping the fifth configuration in a list of previous BAP configurations and/or BH RLC channel configurations, and iv. deleting the fifth configuration and any other previous BAP configurations and/or BH RLC channel configurations. The network node (101, 102, 140) according to any of claims 37-43, further configured to:

- obtain the one or more first configurations from at least one of: i. one or more respective second network nodes (110) configured to comprise the respective second network node (102), wherein the respective one or more second network nodes (110) are configured to have a capability to provide, to the first node (130), a respective wired connection to the core network node (140) of the communications network (100) via at least a respective wireless connection, and ii. a third network node (103) configured to manage configuration of nodes comprised in the communications network (100). The network node (101 , 102, 140) according to claim 44, being further configured to:

- obtain, from at least one of the one or more respective second network nodes (110), the third network node (103) and the core network node (140), at least one of: i. an eighth indication configured to indicate an order in which the plurality of respective second network nodes (110) and/or a plurality of respective second radio network nodes (112) configured to comprise the second radio network node (112) are to serve the first node (130), and ii. a ninth indication configured to indicate a list of the one or more respective second network nodes (110) from which the first network node (101) is to request the respective first configuration of the one or more first configurations.

46. The network node (101 , 102, 140) according to claim 46, wherein at least one of the obtaining of the one or more first configurations and the obtaining of the at least one of the eighth indication and the ninth indication is configured to be performed via one of: i. one or more XnAP messages, and ii. by means of signalling traversing the core network (140) of the communications network (100).

47. The network node (101, 102, 140) according to any of claims 45-46, being further configured to at least one of:

- send a first message to the core network node (140), the message being configured to request at least one of the one or more first configurations, and wherein the obtaining of the one or more first configurations is configured to be in response to the first message configured to be sent,

- store the one or more first configurations, and

- apply the stored respective first configuration upon fulfilment of the one or more respective first criteria.

48. The network node (101 , 102, 140) according to claim 47, wherein at least one of:

- the first message is configured to be an NG Application Protocol, NGAP, message towards one or more serving Access and Mobility Management Functions, AMFs,

- the first message is configured to comprise a tenth indication configured to indicate a quantification of current or predicted traffic load at the first node (130),

- the core network node (140) is configured to be an GAM node, and

- the first message is configured to comprise information about a fifth configuration. A radio network node (111 , 112) configured to operate in a communications network

(100), the radio network node (111 , 112) being for handling configuration of a first node (130), wherein the first node (130) is configured to be provided a wired connection to a core network node (140) of the communications network (100) by a first network node

(101) via at least a wireless connection, and wherein the first node (130) is configured to be capable to be provided a respective wired connection to the core network node (140) of the communications network (100) by a respective second network node (102) via at least another respective wireless connection, and wherein the radio network node (111 , 112) is further configured to:

- receive, from a network node (101 , 102, 140), an indication, wherein one of: i. with the proviso that the radio network node (111 , 112) is configured to be a first radio network node (111), wherein the first node (130) is configured to be served by the first network node (101) through at least the first radio network node (111), the first radio network node (111) being configured to have respective wireless connections with the first node (130) and the first network node (101), the indication is configured to be a fourth indication, wherein the fourth indication is configured to indicate that a fifth configuration with which the first network node (101) is configured to serve the first node (130) is no longer valid, and ii. with the proviso the radio network node (111 , 112) is configured to be a respective second radio network node (112), wherein the first node (130) is configured to be served by the respective second network node

(102) through at least the respective second radio network node (112), the respective second radio network node (112) being configured to have other respective wireless connections with the first node (130) and the respective second network node (102), the indication is configured to be a second indication, wherein the second indication is configured to indicate to activate a respective first configuration configured to be stored at the first radio network node (111). The radio network node (111 , 112) according to claim 49, being further configured to at least one of:

- receive, from the network node (101 , 102, 140), a first indication, the first indication being configured to indicate the respective first configuration to be applied by the first node (130) upon fulfilment of one or more respective first criteria, store the respective first configuration at the radio network node (111 , 112), and apply the second or fourth indication immediately or upon fulfilment of the one or more respective first criteria.

51. The radio network node (111, 112) according to claim 50 wherein at least one of:

- the respective first configuration is configured to be a Backhaul Adaptation Protocol, BAP, configuration,

- the respective first configuration is configured to be a respective Backhaul, BH, Radio Link Control, RLC, channel, configuration, used to configure a respective RLC entity,

- the first indication is configured to originate at the core network node (140), the core network node (140) being configured to be an Operations Administration and Maintenance, OAM, node,

- the first node (130) is configured to be a mobile IAB node,

- the first node (130) is configured to be a node with no descendants,

- the applying (1005) is configured to be performed during a movement of the first node (130) along a route (170),

- the first indication is configured to be one of: i. received in a standalone message, ii. comprising the one or more respective first criteria upon the fulfilment of which the respective first configuration is to be activated, and iii. an enhanced message, and

- the one or more respective first criteria are configured to comprise at least one of: i. the first node (130) identifying, a respective cell (122), ii. the first node (130) entering a geographical area, configured to be indicated in the respective first configuration, and iii. the first node (130) establishing a connection, to the respective second network node (102).

52. The radio network node (111, 112) according to claim 51, wherein the respective first configuration is configured to comprise at least one of: a respective BAP configuration configured to comprise respective at least one of: i. one or more BAP addresses, for the first node (130) ii. one or more downlink, DL, and uplink, UL, BAP routing identifiers, IDs, for the first node (130), iii. one or more second configurations for backhaul mapping of UL traffic configured to originate at the first node (130) or one or more devices (150) configured to be served by the first node (130), iv. a BAP routing configuration, v. one or more third configurations for BAP header rewriting, and vi. one or more fourth configurations for UL and/or DL local rerouting of traffic, and

53. The radio network node (111 , 112) according to any of claims 50-52, wherein the first node (130) is configured to be served by the first network node (101) with a fifth configuration, and wherein the radio network node (111, 112) is further configured to:

- receive, from the network node (101 , 102, 140), a third indication, the third indication being configured to indicate to store at least one of the respective first configuration and the second indication, until application of the respective first configuration.

54. The radio network node (111, 112) according to claim 53, wherein at least one of: - at least one of the first indication and the second indication are configured to be received during a procedure of setting up an F1 connection,

- the first indication is configured to be received together with a conditional F1 setup message,

- the receiving is configured to comprise receiving a plurality of configurations configured to comprise the respective first configuration, each configuration in the plurality being configured to comprise a respective identifier,

- at least one of the first indication and the second indication are configured to be comprised in a Radio Resource Control, RRC, message, and

- at least one of the first indication and the second indication are configured to be received via F1AP,

- at least one of the first indication and the second indication are configured to be received via Downlink Control Information, DCI, or via a Medium Access Control, MAC, control element,

- the one or more respective first criteria are configured to comprise at least one of: a) the first node (130) executing a handover to a cell (122), and b) the first node (130) establishing a connection, to the respective second network node (102),

- the second indication is configured to be received as part of, or together with, a handover command to the cell (122), and

- the second indication is configured to be comprised in a control Protocol Data Unit, PDU. The radio network node (111, 112) according to claim 54, wherein the PDU is configured to comprise at least one of:

- a seventh indication configured to indicate a final destination of the first node (130) when served by the respective second network node (102). The radio network node (111 , 112) according to any of claims 53-55, wherein the first node (130) is configured to be served by the first network node (101) with the fifth configuration, and wherein the radio network node (111 , 112) is further configured to, after activating the respective first configuration:

- perform an action on the fifth configuration configured to be selected from: i. deleting the fifth configuration and keeping other previous BAP configurations and/or BH RLC channel configurations, ii. deactivating the fifth configuration, iii. keeping the fifth configuration in a list of previous BAP configurations and/or BH RLC channel configurations, and iv. deleting the fifth configuration and any other previous BAP configurations and/or BH RLC channel configurations. The radio network node (111, 112) according to any of claims claim 49-56, wherein the respective second radio network node (112) is to directly serve the first node (130) as a new parent, and wherein the second indication is configured to be an existing F1AP UE CONTEXT SETUP REQUEST message with a particular, identifier pair, wherein the identifier pair is configured to have been previously associated to a BAP routing configuration. The radio network node (111 , 112) according to claim 57, wherein the second indication is configured to activate a respective BH RLC channel configuration at the respective second radio network node (112).