CN115553046A

CN115553046A - Integrated access and backhaul communication

Info

Publication number: CN115553046A
Application number: CN202180006095.6A
Authority: CN
Inventors: 许翔; O·布卢默; J·格贝特
Original assignee: Nokia Shanghai Bell Co Ltd; Nokia Solutions and Networks Oy
Current assignee: Nokia Shanghai Bell Co Ltd; Nokia Solutions and Networks Oy
Priority date: 2021-04-30
Filing date: 2021-04-30
Publication date: 2022-12-30
Also published as: WO2022227088A1

Abstract

Embodiments of the present disclosure relate to devices, methods, apparatuses, and computer-readable storage media for Integrated Access and Backhaul (IAB) communication. According to an embodiment of the present disclosure, a first donor Central Unit (CU) from a first operator (which is a participating operator) obtains identification information relating to at least one of a second donor CU from a second operator (which is a hosting operator) and an IAB node from the second operator and shared for the first operator. The first donor CU determines an association of the shared IAB node with the second donor CU based on the obtained identification information. Based on the determined association, the first donor CU sends a request to the second donor CU to configure a channel towards the shared IAB node. In this way, the IAB node of the second operator may be shared with the first operator, and the first operator may operate the cell and serve the UE via the IAB backhaul network of the second operator. This provides greater flexibility for sharing of IAB deployments and may reduce capital expenditure for participating operators.

Description

Integrated access and backhaul communication

Technical Field

Embodiments of the present disclosure relate generally to the field of telecommunications, and, in particular, to devices, methods, apparatuses, and computer-readable media for Integrated Access and Backhaul (IAB) communication.

Background

IAB has been introduced in release 16 (Rel-16) of the 3 rd generation partnership project (3 GPP) specifications as a key contributor to rapid and cost-effective deployment. IAB nodes access and backhaul using the same or different spectrum and air interfaces to create a hierarchical wireless multi-hop (multiple backhaul link) network between sites. The hops ultimately terminate at IAB donors that are connected to the core network over a conventional fixed backhaul. One key advantage of IABs is the ability to flexibly and very densely deploy cells without scaling up the density of the delivery network. A variety of deployment scenarios can be envisioned, including support for outdoor small cell deployments, indoors (e.g., shopping malls), or even mobile relays (e.g., on buses or trains).

For example, users in shopping malls, buses or trains typically subscribe to different network operators. Instead of deploying one IAB network for each operator, it is beneficial to share network resources among multiple operators and provide an IAB node that serves multiple operators.

Disclosure of Invention

In general, example embodiments of the present disclosure provide devices, methods, apparatuses, and computer-readable media for IAB communication.

In a first aspect, a first device is provided. The first device comprises at least one processor; and at least one memory including computer program code; wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the first device from the first operator to obtain identification information relating to at least one of a second device from the second operator and shared for the first operator and a third device from the second operator; determining an association of the second device with the third device based on the identification information; and sending a request to a third device based on the determined association, the request for configuring a radio channel towards the second device, and wherein the first device comprises a first integrated access and backhaul donor central unit, the second device comprises an integrated access and backhaul node, and the third device comprises a second integrated access and backhaul donor central unit.

In a second aspect, a second apparatus is provided. The second device comprises at least one processor; and at least one memory including computer program code; wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause a second device from a second operator to obtain a first identifier that uniquely identifies a third device, the third device being from the second operator and providing a control plane connection to the core network for the second device; and transmitting the first identifier and a second identifier of the second device assigned by the third device to a first device from the first operator, and wherein the first device comprises a first integrated access and backhaul donor central unit, the second device comprises an integrated access and backhaul node, and the third device comprises a second integrated access and backhaul donor central unit.

In a third aspect, a third apparatus is provided. The third device comprises at least one processor; and at least one memory including computer program code; wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause a third device from the second operator to provide, to the first device from the first operator, identification information relating to at least one of the second device and the third device, the second device being from the second operator and shared for the first operator; and receiving a request from the first device for configuring a radio channel towards the second device, and wherein the first device comprises a first integrated access and backhaul donor central unit, the second device comprises an integrated access and backhaul node, and the third device comprises a second integrated access and backhaul donor central unit.

In a fourth aspect, a method is provided. The method comprises obtaining, at a first device from a first operator, identification information relating to at least one of a second device from a second operator and shared for the first operator and a third device from the second operator; determining an association of the second device with the third device based on the identification information; and sending a request to a third device based on the determined association, the request for configuring a radio channel towards the second device, and herein the first device comprises a first integrated access and backhaul donor central unit, the second device comprises an integrated access and backhaul node, and the third device comprises a second integrated access and backhaul donor central unit.

In a fifth aspect, a method is provided. The method comprises obtaining, at a second device from a second operator, a first identifier uniquely identifying a third device, the third device being from the second operator and providing a control plane connection to a core network for the second device; and transmitting, to the first device from the first operator, the first identifier and a second identifier of a second device assigned by the third device, and wherein the first device comprises a first integrated access and backhaul donor central unit, the second device comprises an integrated access and backhaul node, and the third device comprises a second integrated access and backhaul donor central unit.

In a sixth aspect, a method is provided. The method comprises providing, at a third device from a second operator, to a first device from a first operator, identification information relating to at least one of the second device and the third device, the second device being from the second operator and shared for the first operator; and receiving a request from the first device for configuring a radio channel towards the second device, and wherein the first device comprises a first integrated access and backhaul donor central unit, the second device comprises an integrated access and backhaul node, and the third device comprises a second integrated access and backhaul donor central unit.

In a seventh aspect, a first apparatus is provided. The first apparatus from the first operator comprises means for obtaining identification information relating to at least one of a second apparatus from the second operator and shared for the first operator and a third apparatus from the second operator; means for determining an association of the second apparatus with a third apparatus based on the identification information; and means for sending a request to a third apparatus based on the determined association, the request for configuring a radio channel towards the second apparatus, and wherein the first apparatus comprises a first integrated access and backhaul donor central unit, the second apparatus comprises an integrated access and backhaul node, and the third apparatus comprises a second integrated access and backhaul donor central unit.

In an eighth aspect, a second apparatus is provided. The second apparatus from the second operator comprises means for obtaining a first identifier uniquely identifying a third apparatus, the third apparatus being from the second operator and providing a control plane connection to the core network for the second apparatus; and means for transmitting the first identifier and a second identifier of the second apparatus allocated by the third device to a first apparatus from the first operator, and wherein the first apparatus comprises a first integrated access and backhaul donor central unit, the second apparatus comprises an integrated access and backhaul node, and the third apparatus comprises a second integrated access and backhaul donor central unit.

In a ninth aspect, a third apparatus is provided. The third apparatus from the second operator comprises means for providing to a first apparatus from the first operator identification information relating to at least one of the second apparatus and a third apparatus, the second apparatus being from the second operator and shared for the first operator; and means for receiving a request from a first apparatus for configuring a radio channel towards a second apparatus, and wherein the first apparatus comprises a first integrated access and backhaul donor central unit, the second apparatus comprises an integrated access and backhaul node, and the third apparatus comprises a second integrated access and backhaul donor central unit.

In a tenth aspect, there is a computer readable storage medium comprising program instructions stored thereon. The instructions, when executed by an apparatus, cause the apparatus to perform a method according to the fourth, fifth or sixth aspect described above.

It should be understood that the summary is not intended to identify key or essential features of embodiments of the disclosure, nor is it intended to be used to limit the scope of the disclosure. Other features of the present disclosure will become readily apparent from the following description.

Drawings

The above and other objects, features and advantages of the present disclosure will become more apparent from the following more detailed description of some exemplary embodiments of the present disclosure in which:

FIG. 1 shows a block diagram of a system for IAB communication;

FIG. 2 illustrates a partial sharing scenario in which example embodiments of the present disclosure may be applied;

3a, 3b, and 3c illustrate example IAB environments in which example embodiments of the present disclosure may be implemented;

fig. 4a shows a flowchart illustrating an example process for sharing an IAB node, in accordance with some example embodiments of the present disclosure;

fig. 4b shows a flowchart illustrating an example process for a non-shared IAB node, according to some example embodiments of the present disclosure;

fig. 5 shows a flowchart illustrating another example process for sharing an IAB node, in accordance with some example embodiments of the present disclosure;

fig. 6a illustrates an example protocol stack for supporting the F1 user plane, in accordance with some example embodiments of the present disclosure;

fig. 6b illustrates an example protocol stack for supporting the F1 control plane, in accordance with some example embodiments of the present disclosure;

fig. 7 shows a flow diagram of an example method according to some example embodiments of the present disclosure;

fig. 8 shows a flow diagram of an example method according to some example embodiments of the present disclosure;

fig. 9 shows a flowchart of an example method according to some example embodiments of the present disclosure;

FIG. 10 shows a simplified block diagram of an apparatus suitable for implementing embodiments of the present disclosure; and

fig. 11 illustrates a block diagram of an example computer-readable medium, in accordance with some example embodiments of the present disclosure.

Throughout the drawings, the same or similar reference numbers refer to the same or similar elements.

Detailed Description

The principles of the present disclosure will now be described with reference to a few exemplary embodiments. It is understood that these examples are described merely to illustrate and assist those of ordinary skill in the art in understanding and practicing the disclosure, and are not intended to limit the scope of the disclosure in any way. The disclosure described herein may be implemented in various other ways than those described below.

In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

References in the present disclosure to "one embodiment," "an example embodiment," etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an example embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

It will be understood that, although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, a first element may be termed a second element, and, similarly, a second element may be termed a first element, without departing from the scope of example embodiments. As used herein, the term "and/or" includes any and all combinations of one or more of the listed terms.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises," "comprising," "has," "having," "includes" and/or "including," when used herein, specify the presence of stated features, elements, and/or components, etc., but do not preclude the presence or addition of one or more other features, elements, components, and/or groups thereof.

As used in this application, the term "circuitry" may refer to one or more or all of the following:

(a) A purely hardware circuit implementation (such as an implementation using only analog and/or digital circuitry), and

(b) A combination of hardware circuitry and software, such as (as applicable):

(i) Combinations of analog and/or digital hardware circuit(s) and software/firmware, and

(ii) Hardware processor(s) with software (including digital signal processors), software, and any portion of memory(s) that work together to cause a device, such as a mobile phone or server, to perform various functions, and

(c) Hardware circuit(s) and/or processor(s), such as microprocessor(s) or a portion of microprocessor(s), that require software (e.g., firmware)

The operation is performed but the software may not exist when the operation is not required.

The definition of circuitry is intended to be consistent with all use of the term in this application, including in any claims. As a further example, as used in this application, the term circuitry also encompasses implementations of only a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware. For example, the term circuitry, if applicable to a particular claim element, also encompasses a baseband integrated circuit or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, a cellular network device, or other computing or network device.

As used herein, the term "communication network" refers to a network that conforms to any suitable communication standard, such as Long Term Evolution (LTE), LTE-advanced (LTE-a), wideband Code Division Multiple Access (WCDMA), high Speed Packet Access (HSPA), narrowband internet of things (NB-IoT), new Radio (NR), and so forth. Further, communication between the terminal device and the network device or between the network devices in the communication network may be performed according to any suitable communication protocol, including but not limited to first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, future fifth generation (5G) communication protocols, and/or any other protocol currently known or developed in the future. Embodiments of the present disclosure may be applied to various communication systems. In view of the rapid development of communications, there will, of course, also be future types of communication techniques and systems that may embody the present disclosure. And should not be taken as limiting the scope of the disclosure to only the above-described systems.

As used herein, the term "network device" refers to a node in a communication network via which a terminal device accesses the network and receives services therefrom. A network device may refer to a Base Station (BS) or an Access Point (AP), e.g., a node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), an NR NB (also known as a gNB), a Remote Radio Unit (RRU), a Radio Header (RH), a Remote Radio Head (RRH), a relay, a low power node such as femto, pico, etc., depending on the terminology and technology applied. Further, an IAB-node, an IAB donor central unit (IAB donor CU) or an IAB donor distributed unit (IAB donor DU) are examples of network devices. In the following description, the terms "network device", "BS" and "node" may be used interchangeably.

The term "terminal device" refers to any terminal device capable of wireless communication. By way of example, and not limitation, a terminal device may also be referred to as a communication device, user Equipment (UE), a Subscriber Station (SS), a portable subscriber station, a Mobile Station (MS), or an Access Terminal (AT). The end devices may include, but are not limited to, mobile phones, cellular phones, smart phones, voice over IP (VoIP) phones, wireless local loop phones, tablet computers, wearable end devices, personal Digital Assistants (PDAs), portable computers, desktop computers, image capture end devices such as digital cameras, gaming end devices, music storage and playback devices, in-vehicle wireless end devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop installation devices (LMEs), USB dongles, smart devices, wireless client devices (CPEs), internet of things (IoT) devices, watches or other wearable devices, head Mounted Displays (HMDs), vehicles, drones, medical devices and applications (e.g., tele-surgery), industrial devices and applications (e.g., robots and/or other wireless devices operating in industrial and/or automated processing chain environments), consumer electronics, devices operating on commercial and/or industrial wireless networks, and the like. In the following description, the terms "terminal device", "communication device", "terminal", "user equipment" and "UE" may be used interchangeably.

As used herein, the term "device from an operator" or similar terms means that the device is deployed by the operator and is associated with one or more Public Land Mobile Network (PLMN) Identifiers (IDs) of the operator. The term "a device from a first operator and shared for a second operator" or similar terms means that the device is deployed by the first operator and is associated with one or more PLMN IDs of the first operator and another one or more PLMN IDs of the second operator.

Example Environment

Fig. 1 shows a block diagram of an example IAB system 100. The IAB system 100 includes an IAB donor 110 and IAB nodes 120-11, 120-12, 120-21, 120-22, 120-31 located below the IAB donor 110. The IAB nodes 120-11, 120-12, 120-21, 120-22, 120-31 may be collectively referred to as "IAB nodes 120" or individually referred to as "IAB nodes 120".

The IAB donor 110 may be implemented as a gNB that terminates a wireless backhaul radio interface from one or more IAB nodes. The IAB donor 110 has a wired/optical connection to the core network. The IAB donor 110 may include a CU 110-11 and one or more DUs. Fig. 1 shows, by way of example, that IAB donor 110 includes DUs 110-12. In the following, a CU of an IAB donor is also referred to as donor CU or donor central unit or IAB donor CU; and the IAB-donor DU is also referred to as a donor DU or donor distribution unit or IAB donor DU.

An IAB node (e.g., IAB node 120) may include DUs (also referred to as IAB-DUs) and Mobile Terminals (MTs) that maintain connections (e.g., using dual connections) with one or more upstream nodes (also referred to as IAB-MTs). Similar to conventional user equipment (i.e., UE), the MT of an IAB node can provide radio link measurements of alternative upstream nodes to its current serving gNB CU using Radio Resource Control (RRC) signaling. Migration may be performed, such as performing a handover to the IAB-MT based on signal strength, signal quality, and other factors. Thus, an IAB topology such as that shown in fig. 1 may be non-static. As radio conditions fluctuate and IAB nodes move, add, or delete, the IAB topology may change over time.

A CU, such as a donor CU, may be a logical node that may include functions such as user data transfer, mobility control, radio access network sharing, positioning, session management, etc. (e.g., a gNB function), in addition to the functions exclusively allocated to DUs. The CU may control the operation of the DU through a forward (F1) interface. The DU is a logical node that may include a subset of functions (e.g., the gNB functions). One gNB-DU (e.g., IAB-DU, or IAB donor DU) is connected to only one gNB-CU (e.g., IAB donor CU) via the F1 interface. The IAB-DU or IAB donor DU initiates F1 setup with the donor CU.

The IAB donor 110 may serve directly connected IAB nodes (such as IAB node 120-11 and IAB node 120-12), as well as IAB nodes linked by multiple wireless backhaul hops (such as IAB node 120-21, IAB node 120-22, and IAB node 120-31). The IAB donor 110 may also serve directly connected terminal devices (not shown). IAB node 120 may serve one or more terminal devices that are directly connected to IAB node 120. For example, as shown in fig. 1, IAB node 120-11 may serve terminal device 130 connected directly to IAB node 120-11, IAB node 120-21 may serve terminal device 140 connected directly to IAB node 120-21, and IAB node 120-31 may serve terminal device 150 connected directly to IAB node 120-31.

During the RRC procedure, the donor CU 110-11 assigns a Backhaul Adaptation Protocol (BAP) address to the IAB-MT of the IAB node 120. A Backhaul (BH) Radio Link Control (RLC) channel towards the IAB node 120 is established via an RRC procedure. To manage the BH RLC channel towards the IAB node 120, the donor CU 110-11 will identify the concatenation of IAB-MT and IAB-DU. For example, the IAB-DU of the IAB node 120 may provide its BAP address to the donor CU 110-11 during the F1 setup procedure, so the donor CU 110-11 may know the concatenation of the IAB-DU with a particular IAB-MT.

It should be understood that the number of IAB nodes and terminal devices connected to the IAB nodes is for illustration purposes only and does not imply any limitation. The IAB system may include any suitable number of IAB nodes and terminal devices suitable for implementing example embodiments of the present disclosure.

Instead of deploying an IAB network for each operator, it may be beneficial to share network resources among multiple operators. For example, in one scenario, a vehicle relay network may be shared among multiple operators. A donor gNB (i.e., donor DU and/or donor CU) from one operator is shared for another operator. Thus, the relays installed on the vehicle are also shared for other operators.

In some scenarios, network sharing for a normal gNB may be considered. For example, in some use cases, it may be desirable to support sharing of the gNB (including sharing of gNB-DUs and gNB-CUs). In some cases, it may be desirable to support schemes that only share gNB-DUs and not gNB-CUs.

In the IAB system, there is also a need for a network that supports shared IAB nodes (including IAB nodes, IAB donor CUs/DUs), and that only shares IAB nodes and not donor CUs and donor DUs. For example, in a shopping mall, airport, or train, multiple users may require service from multiple operators. This requires a large number of installations to run two or more IAB networks within a building, which results in high cost and difficulty in finding antenna points. Therefore, it is desirable to share the IAB network between operators.

However, in an IAB system, it may not be necessary to share all IAB nodes. In contrast, an operator of a donor gNB may only want to share a selected subset of its IAB nodes with another operator. Reference is now made to fig. 2. Fig. 2 illustrates partial sharing of an IAB node with multiple operators in an IAB network.

In the example partial sharing scenario 200, a donor gNB121, comprising a donor CU and a donor DU, is deployed by the second operator 101, and a donor CU 122 is deployed by the first operator 102. Donor gNB121 and donor CU 122 communicate with each other, e.g., via an Internet Protocol (IP) connection 143 between a DU of donor gNB121 and donor CU 122, or an Xn interface between a CU of donor gNB121 and donor CU 122.

IAB node 111 and IAB node 112 are deployed by the second operator 101 in a building 150 (e.g., a shopping mall). The IAB node 112 is shared with the first operator 102. In this way, terminal devices 130 subscribed to the first operator 102 may be served by the IAB node 112. As shown in fig. 2, a transfer path 150 between IAB node 112 and first operator 102 includes a wireless backhaul link between IAB node 112 and IAB node 111, a wireless backhaul link between IAB node 111 and donor gNB121, and an IP connection 143.

Reference is now made to fig. 3a and 3b. Fig. 3a and 3b illustrate

example IAB environments

300 and 305 in which example embodiments of the present disclosure may be implemented. The deployment examples shown in fig. 3a and 3b may be used in the example scenario 200 shown in fig. 2.

Example IAB environments

300 and 305 involve three operator Public Land Mobile Networks (PLMNs). Specifically,

IAB environments

300 and 305 include a donor CU from an IAB donor node of a first operator (also referred to as "donor l-CU 311"), a donor CU from another IAB donor node of a second operator (also referred to as "donor 2-CU 321"), and a donor CU from another IAB donor node of a third operator (also referred to as "donor 3-CU 331").

In the IAB environment 300 of fig. 3a, an IP connection 351 is established between the donor l-CU 311 and a donor DU (also referred to as "donor 2-DU 322") from the IAB donor node of the second operator. The IAB node 323, the IAB node 324, and the IAB node 325 are deployed by a second operator and controlled by a donor 2-CU321, the donor 2-CU321 providing a control plane connection to a core network (not shown in fig. 3 a) for the IAB node deployed by the second operator. For example, the donor 2-CU321 is the termination point of the control plane connections to the core network for the IAB-MT in the IAB node 323 and the IAB-MT in the IAB node 324. The IAB node 324 is shared with the first operator. At least one cell of the IAB node 324 is shared for the first operator. It is possible that only one cell, or more than one cell, or all cells of the IAB node 324 are shared for the first operator. As a result, the IAB node 324 may serve the terminal devices 315 subscribed to the first operator and the IAB node 312 deployed by the first operator. The IAB node 312 in turn serves an IAB node 313 deployed by the first operator and terminal devices 314 subscribed to the first operator. In this case, the shared cell(s) provided by the shareab node 324 can be considered to be the cells served by the donor 1-CU 311 and donor 2-CU321, e.g., when the donor 1-CU 311 or donor 2-CU321 exchanges the served cell information with the neighboring gNB CU over an Xn interface.

Another IP connection 352 is established between donor l-CU 311 and a donor DU from a third operator (also referred to as "donor 3-DU 332"). The IAB node 333 and the IAB node 334 are deployed by a third operator and controlled by a donor 3-CU331, the donor 3-CU331 providing a control plane connection to a core network (not shown in fig. 3 a) for the IAB node deployed by the third operator. For example, donor 3-CU331 is the termination point of the control plane connection to the core network for IAB-MT in IAB node 333 and IAB-MT in IAB node 334. The IAB node 333 is shared with the first operator. As a result, the IAB node 333 may serve the IAB node 317 deployed by the first operator. In this case, the shared cell(s) provided by the shareab node 333 may be considered to be the cells served by both the donor 1-CU 311 and the donor 3-CU331, e.g., when the donor 1-CU 311 or the donor 2-CU331 exchanges the served cell information with the neighboring gNB CU over an Xn interface.

The IAB environment 300 of fig. 3a also shows a donor DU (also referred to as "donor 1-DU 318") from the first operator. The IAB node 316 is deployed by a first operator and is controlled by a donor 1-CU 311, the donor 1-CU 311 providing a control plane connection to a core network (not shown in fig. 3 a) for the IAB node deployed by the first operator. For example, donor 1-CU 311 is the termination point of the IAB-MT's control plane connection to the core network in IAB node 316.

In the IAB environment 305, an IP connection 353 is established between donor l-CU 311 and donor 2-DU 322. Similarly, another IP connection 354 is established between the donor 3-CU331 and the donor 2-DU 322. The IAB node 324 deployed by the second operator is shared with both the first operator and the third operator. As a result, the IAB node 324 may serve terminal devices 335 subscribed to the third operator and the IAB node 312 deployed by the first operator. In this case, the shared cell(s) provided by the shared IAB node 324 may be considered to be the cells served by the donor 1-CU 311, donor 2-CU321, and donor 3-CU331, e.g., when the donor 1-CU 311 or donor 2-CU321 or donor 3-CU331 exchanges the served cell information with neighboring gNB CUs over an Xn interface.

For the shared IAB node 324 shown in fig. 3a, the second operator is the hosting operator with operational control of the shared IAB node, and the first operator is the participating operator authorized to access the resources of the shared IAB. An IAB node. Similarly, for the shared IAB node 324 shown in fig. 3b, the second operator is the hosting operator, the first operator is the participating operator, and the third operator is another participating operator. In some example embodiments, the shared IAB node may include an IAB-DU for interfacing with the F1 of the donor CU from the hosting operator, another IAB-DU for interfacing with the F1 of the donor CU from the first participating operator, and another IAB-DU for interfacing with the F1 of the donor CU from the second participating operator, among others. For example, in fig. 3a, the shared IAB node 324 may include an IAB-DUa (not shown in fig. 3 a) for interfacing with F1 of donor 1-CU 311 from a first operator, and an IAB-DUb (not shown in fig. 3 a) for interfacing with F1 of donor 2-CU321 from a second operator. As another example, in fig. 3b, the shared IAB node 324 may include an IAB-DUa (not shown in fig. 3 b) for interfacing with F1 of donor l-CU 311 from a first operator, an IAB-DUb (not shown in fig. 3 b) for interfacing with F1 of donor 2-CU321 from a second operator, and an IAB-DUc (not shown in fig. 3 b) for interfacing with F1 of donor 3-CU331 from a third operator.

Similarly, for the shared IAB node 333 as shown in fig. 3a, the third operator is the hosting operator and the first operator is the participating operator. In some example embodiments, the shared IAB node 333 may include an IAB-DUa (not shown in fig. 3 a) for interfacing with F1 of the donor 1-CU 311 from the first operator, and an IAB-DUb (not shown in fig. 3 a) for interfacing with F1 of the donor 3-CU331 from the third operator.

It should be understood that the deployment examples of fig. 3a and 3b are for illustration purposes only and do not imply any limitations. Example embodiments of the present disclosure may be implemented in an IAB environment having any suitable deployment. As another deployment example, a complete tree or sub-tree of IAB nodes may be shared. For example, the second operator may share IAB node 324, IAB node 325, IAB node 312, and IAB node 313 with the first operator and the third operator.

In a partially shared IAB environment, IAB nodes are shared among different operators without sharing donor CUs and other intermediate nodes (e.g., donor DUs, intermediate IAB nodes). To manage a radio channel, such as a BH RLC channel, towards the shared IAB node 324, the donor 1-CU 311 from the participating operator should identify the concatenation of the IAB-MT and the IAB-DU of the shared IAB node. However, no solution is available for donor 1-CU 311 from the participating operator to know the concatenation of IAB-MT and IAB-DU of the shared IAB node 324. This is because the BAP address (e.g., BAP address # 001) of the shared IAB node 324 is assigned by the donor 2-CU321 from the hosting operator, and donor CUs from different operators may assign the same BAP address to different IAB nodes. For example, donor l-CU 311 may have assigned the same BAP address (e.g., BAP address # 001) to its own IAB node, such as IAB node 316. As a result, donor l-CU 311 cannot know the concatenation of IAB-MT and IAB-DU of the shared IAB node 324 even though the IAB-DU of the shared IAB node 324 includes the BAP address in the F1 SETUP REQUEST message during the F1 SETUP procedure with the donor l-CU 311. The donor l-CU 311 may erroneously determine that the IAB-DU is collocated with the IAB-MT in the IAB node 316 instead of the IAB-MT in the IAB node 324.

The donor l-CU cannot request to set up or modify the BH RLC channel towards the shared IAB node since it does not know the IAB-MT collocated with the IAB-DU of the shared IAB node. Furthermore, the donor 1-CU does not know which donor controls the IAB-MT of the shared IAB node, and the donor 1-CU does not know where the request should be sent, e.g., a request to establish a BH RLC channel towards the shared IAB node.

Similar problems may exist in non-IAB shared environments as well. Fig. 3c illustrates another example IAB environment 306 in which some example embodiments of the present disclosure may be implemented. In particular, the IAB environment 306 includes a donor CU of a first IAB donor node (also referred to as "donor l-CU 361") and a donor CU of a second IAB donor node (also referred to as "donor 2-CU 371"). IAB environment 306 also includes a donor DU (also referred to as "donor 1-DU 368") for a first IAB donor node and a donor DU (also referred to as "donor 2-DU 372") for a second IAB donor node. IAB environment 306 also includes IAB nodes 373, 374, 375, 366.

IAB nodes

373, 374, 375, 366, donor 2-CU371, donor 1-CU 361, donor 2-DU 372 and donor 1-DU 368 are deployed by the same operator. An IP connection 355 is established between donor 1-CU 361 and donor 2-DU 372. IAB node 374 is connected to IAB node 373. The RRC establishment procedure initiated by the IAB-MT of the IAB node 374 terminates at the donor 2-CU371, and the donor 2-CU371 provides a control plane connection to the core network (not shown in fig. 3 c). For example, donor 2-CU371 is the termination point of the control plane connection to the core network for the IAB-MT in the IAB node 374. During the RRC establishment procedure, the donor 2-CU371 assigns a BAP address (e.g., # 002) to the IAB-MT of the IAB node 374. However, the IAB-DU in the IAB node 374 is configured to use the donor 1-CU 361 for the F1 interface, e.g., for load balancing reasons when the donor 2-CU371 is overloaded and cannot accept a new F1 setup from the IAB-DU in the IAB node 374. To manage a radio channel, such as a BH RLC channel, towards the IAB node 374, the donor 1-CU 361 should identify the concatenation of the IAB-MT and the IAB-DU of the IAB node 374. Donor 1-CU 361 has no solution available to know the concatenation of IAB-MT and IAB-DU for IAB node 374. This is because the BAP address of IAB node 374 (e.g., BAP address # 002) is assigned by donor 2-CU371, and donor 1-CU 361 may assign the same BAP address to different IAB nodes. For example, donor l-CU 361 may have assigned the same BAP address (e.g., BAP address # 002) to its own IAB node (e.g., IAB node 366). As a result, when donor 1-CU 361 receives an F1 SETUP REQUEST message from an IAB-DU in IAB node 374 that includes a BAP address (e.g., # 002), donor 1-CU 361 cannot know the concatenation of the IAB-MT and the IAB-DU of IAB node 374. Donor l-CU 361 may erroneously determine that an IAB-DU is collocated with the IAB-MT in IAB node 366 instead of the IAB-MT in IAB node 374.

Example embodiments of the present disclosure provide a solution for IAB communication. In some embodiments, the solution enables different operators to share IAB nodes. In some embodiments, the solution enables load balancing of different donor CUs of the same operator. Some example embodiments address some of the issues discussed above, and some example embodiments further address one or more other potential issues.

In some embodiments, a first donor CU from a first operator (e.g., a participating operator) obtains identification information relating to at least one of a second donor CU from a second operator (e.g., a hosting operator) and an IAB node from the second operator and shared for the first operator. In some example embodiments, the first donor CU may receive the unique identifier of the second donor CU from the shared IAB node (e.g., from an IAB-DU of the shared IAB node). Alternatively or additionally, in some example embodiments, the first donor CU may receive an identifier of a shared IAB node (e.g., a BAP address or an IAB address) and at least another identifier of a cell served by the shared IAB node from the second donor CU.

The first donor CU determines an association of the shared IAB node with the second donor CU based on the obtained identification information. For example, the first donor CU may identify the second donor DU control shared IAB node based on the acquired identification information. Based on the determined association, the first donor CU may send a request to the second donor CU to configure a radio channel towards the shared IAB node, if needed. For example, a first donor CU may send a request to a second donor CU to establish or modify a BH RCL channel towards a shared IAB node.

In an example embodiment, a shared IAB node and a donor controlling the shared IAB node may be identified by a donor from a participating operator. IAB node sharing is enabled without sharing donor and intermediate IAB nodes. In this way, flexibility in IAB deployment may be achieved and capital expenditure for participating operators may be reduced.

Example procedure

Some example embodiments are detailed below. Fig. 4a shows a flowchart illustrating an example process 400 for sharing an IAB node, according to some example embodiments of the present disclosure. For purposes of discussion, the process 400 will be described with reference to fig. 3a and 3b. Process 400 involves at least donor 1-CU 311 from a first operator, donor 2-CU321 from a second operator, and IAB node 324 shared between the first operator and the second operator. As shown in FIG. 4a, the IAB node 324 includes an IAB-MT 401 and one or more IAB-DUs. For example, the IAB node 324 may include an IAB-DUa403 for interfacing with F1 of the donor l-CU 311 and an IAB-DUb402 for interfacing with F1 of the donor 2-CU 321. It should be understood that although IAB-DUa403 and IAB-DUb402 are shown separately, this is for illustrative purposes only and does not represent any limitation on the scope of protection. The IAB-DUa403 and the IAB-DUb402 may be implemented by the same device or apparatus.

In process 400, the donor 2-CU321 sends 405 to the IAB node 324 an identifier (hereinafter also referred to as a "second identifier") of the IAB node 324 that was assigned by the donor 2-CU 321. The second identifier may be any suitable identifier assigned by the donor 2-CU321 to identify the IAB node 324.

In some example embodiments, the second identifier is a BAP address of the IAB node 324 assigned by the donor 2-CU 321. For example, during a UE initial access procedure of IAB-MT 401, IAB-MT 401 may initiate establishment of an RRC connection with donor 2-CU 321. The donor 2-CU321 may assign a BAP address to the IAB node 324 and send an RRC reconfiguration message including the BAP address to the IAB-MT 401. The UE initial access procedure of the IAB-MT also includes a connection setup with the core network (not shown in fig. 4 a). The donor 2-CU321 terminates the control plane connection of the IAB-MT 401 to the core network.

The IAB node 324 obtains 410 an identifier that uniquely identifies the donor 2-CU 321. Such an identifier is also referred to as a "first identifier" or unique identifier. The first identifier may be any identity capable of uniquely identifying the donor 2-CU321 in a multi-operator deployment (e.g., the example deployment shown in fig. 3a and 3 b). As an example, the first identifier may be a global gbb ID of the donor 2-CU321, which includes a PLMN ID of an operator (i.e., the second operator in this example) that deploys and controls the donor 2-CU, and a gbb ID of the donor 2-CU 321.

In some example embodiments, the IAB node 324 may receive the first identifier from the donor 2-CU 321. As an example, the first identifier may be included in a F1 application protocol (F1 AP) message provided to the IAB-DUb402 from the donor 2-CU321, e.g., during a F1 setup procedure between the IAB-DUb402 and the donor 2-CU 321. As another example, the first identifier may be included in an RRC message provided from the donor 2-CU321 to the collocated IAB-MT 401 during an RRC procedure, e.g., during an RRC connection establishment procedure or during an RRC reconfiguration procedure or at 405.

Alternatively or additionally, in some example embodiments, the IAB node 324 may receive the first identifier from an Operations Administration and Maintenance (OAM) entity (not shown). For example, the OAM entity of the second operator may provide configuration information including the first identifier to the IAB-DUb402 or the IAB-DUa 403. The first identifier may also be provided by the OAM entity when the OAM entity configures other parameters related to the IAB-DU of the IAB node 324.

In some example embodiments, internal communication 415 may be performed within the IAB node 324 to communicate identification information relating to the IAB node 324 and the donor 2-CU 321. In the case where the IAB node 324 includes an IAB-DUa403 and an IAB-DUb402, the BAP address assigned to the IAB-MT 401 may be shared between the IAB-MT 401, the collocated IAB-DUa403, and the collocated IAB-DUb402, and the first identifier of the donor 2-CU may be shared between the IAB-MT 401, the collocated IAB-DUa403, and the collocated IAB-DUb 402. For example, the BAP address received at 405 may be sent from IAB-MT 401 to IAB-DUb402 and IAB-DUa 403. The first identifier of the donor 2-CU obtained at 410 may be sent from the IAB-DUb402 (or IAB-MT 401) to the IAB-DUa 403.

The IAB node 324 sends 420 identification information relating to the IAB node 324 and the donor 2-CU321 to the donor l-CU 311. For example, the IAB-DUa403 provides the donor 1-CU 311 with a first identifier of the donor 2-CU321 and a second identifier of the IAB node 324.

In some example embodiments, the first identifier and the second identifier may be sent during a procedure for establishing a Fl interface between the IAB node 324 and the donor l-CU 311. For example, the first identifier and the second identifier may be included in an F1 SETUP REQUEST message from the IAB-DUa403 to the donor 1-CU 311.

Alternatively or additionally, in some example embodiments, the first identifier and the second identifier may be sent during a procedure for updating a configuration of an IAB-DU of the IAB node 324. For example, the IAB-DUa403 may include the first identifier and the second identifier in a message towards the donor 1-CU 311 during the F1gNB-DU configuration update procedure.

Alternatively or additionally, in some example embodiments, the first identifier and the second identifier may be sent during a process for updating the configuration of the donor l-CU 311. For example, the IAB-DUa403 may include the first identifier and the second identifier in a message towards the donor 1-CU 311 during the F1 gbb-CU configuration update procedure.

Upon receiving the identification information, the donor l-CU 311 determines 425 the association of the IAB node 324 with the donor 2-CU 321. In other words, based on the first identifier and the second identifier, the donor l-CU 311 may identify that the IAB-MT 401 is collocated with the IAB-DUa403 and determine that the donor 2-CU321 manages the IAB node 324. For example, donor l-CU 311 may identify that IAB-DUa403 is collocated with an IAB-MT from a second operator, and that collocated IAB-MT 401 is managed by donor 2-CU321, donor 2-CU321 providing a control plane connection to the core network for collocated IAB-MT 401.

Based on the determined association, the donor l-CU 311 may send 430 a request to the donor 2-CU321 to configure the radio channel towards the IAB node 324, if needed. The request includes a second identifier for identifying the IAB node 324 of the IAB-MT 401. For example, the request may include a BAP address for the IAB node 324 that identifies the IAB-MT 401.

As an example, when a BH RLC channel towards the IAB-MT 401 needs to be established or modified, the donor l-CU 311 may send an Xn request message to the donor 2-CU321 to establish or modify the BH RLC channel towards the IAB-MT 401. The Xn request includes a BAP address that identifies IAB-MT 401.

The donor 2-CU321 initiates 435 a procedure for configuring a radio channel towards the IAB node 324. For example, donor 2-CU321 may initiate an F1AP procedure or an RRC procedure to establish or modify a BH RLC channel towards IAB-MT 401. The BH RLC channel is also used to convey traffic, e.g., traffic for the F1 control plane (F1-C) or F1 user plane (F1-U) between the IAB-DUa403 and the donor 1-CU 311, and/or traffic for the F1-C or F1-U between the IAB-DUb402 and the donor 2-CU 321.

In the example process 400, a unique identifier of a donor CU from a hosting operator is provided by a shared IAB node to a donor CU from a participating operator. In this way, donor CUs from participating operators may identify donor CUs that control the shared IAB node. Thus, IAB node sharing is enabled without sharing the donor and an intermediate IAB node from the hosting operator.

In some example embodiments, the first and second operators may be the same, and in this case, the second device (e.g., IAB node 324) is not an IAB node shared by different operators (and referred to as a non-shared IAB node), but the IAB node has a connection with more than one donor CU from the same operator. An example is shown in fig. 4 b. Fig. 4b shows a flowchart illustrating an example process 450 for a non-shared IAB node, according to some example embodiments of the present disclosure. For purposes of discussion, the process 450 will be described with reference to fig. 3 c. Process 450 involves at least donor 1-CU 361, donor 2-CU371, and IAB node 374, which may be deployed by the same operator. As shown in FIG. 4b, the IAB node 374 includes IAB-MT 451 and an IAB-DU 453. The IAB-DU453 may have an F1 interface with the donor 1-CU 361, but the donor 2-CU371 is the termination point of the control plane connection to the core network for the IAB-MT 451.

In the process 450, the donor 2-CU371 sends 455 an identifier (hereinafter also referred to as a "second identifier") of the IAB node 374 assigned by the donor 2-CU371 to the IAB node 374. The second identifier may be any suitable identifier assigned by the donor 2-CU371 for identifying the IAB node 374.

In some example embodiments, the second identifier is the BAP address of the IAB node 374 assigned by the donor 2-CU 371. For example, during a UE initial access procedure of the IAB-MT 451, the IAB-MT 451 may initiate establishment of an RRC connection with the donor 2-CU 371. The donor 2-CU371 may assign a BAP address to the IAB node 374 and send an RRC reconfiguration message including the BAP address to the IAB-MT 451. The UE initial access procedure of the IAB-MT also includes connection establishment with the core network (not shown in fig. 4 b).

The IAB node 374 obtains 460 an identifier that uniquely identifies the donor 2-CU 371. Such an identifier is also referred to as a "first identifier" or unique identifier. The first identifier may be any identity capable of uniquely identifying the donor 2-CU371 in an IAB network (e.g., the example deployment shown in fig. 3 c) that includes multiple donor CUs. As an example, the first identifier may be the global gbb ID of the donor 2-CU371 when the IAB network has other IABs from other operators, or the gbb ID of the donor 2-CU371 without PLMN IDs when the IAB network has only IABs from a single operator.

The first identifier may be obtained in a manner similar to that described with reference to fig. 4 a. For example, the IAB node 374 may receive the first identifier from the donor 2-CU 371. As an example, the first identifier may be included in an RRC message provided from the donor 2-CU371 to the collocated IAB-MT 451 during an RRC procedure, e.g., during an RRC connection establishment procedure or during an RRC reconfiguration procedure or at 455. Alternatively or additionally, in some example embodiments, the IAB node 374 may receive the first identifier from an OAM entity (not shown).

In some example embodiments, internal communication may be performed 465 within the IAB node 374 to communicate identification information relating to the IAB node 374 and the donor 2-CU 371. In the case where the first identifier is provided to the IAB node 374 via an RRC procedure, the IAB-MT 451 may share the first identifier and the BAP address assigned to the IAB-MT 451 with the collocated IAB-DU 453.

The IAB node 374 sends 470 identification information relating to the IAB node 374 and donor 2-CU371 to the donor l-CU 361 in a manner similar or identical to that described with reference to fig. 4a and operation 420.

Upon receiving the identification information, donor l-CU 361 determines 475IAB node 374 association with donor 2-CU 371. In other words, based on the first identifier and the second identifier, donor l-CU 361 may identify that IAB-MT 451 is collocated with IAB-DU453 and determine that donor 2-CU371 manages IAB node 374. For example, the donor 1-CU 361 may identify that the IAB-DU453 is collocated with the IAB-MT in the IAB node 374, and that the collocated IAB-MT 451 is managed by the donor 2-CU371, the donor 2-CU371 providing a control plane connection to the core network for the collocated IAB-MT 451.

Based on the determined association, the donor l-CU 361 may send 480 a request to the donor 2-CU371 for configuring a radio channel towards the IAB node 374, if needed. The donor 2-CU371 initiates 485 procedures for configuring the radio channel towards the IAB node 374. The operations performed at 480 and 485 are similar or identical to the operations described with reference to 430 and 435 of fig. 4 a.

In the example process 450, the unique identifier of the donor l-CU 371 providing the control plane connection to the core network for the IAB-MT 451 of the IAB node 324 is provided by the IAB-DU453 in the IAB node 374 to the donor CU 361, and the donor CU 361 provides the F1 termination point for the IAB-DU453 of the IAB node 374. In this way, a first donor CU that terminates the F1 interface of an IAB-DU in an IAB node may identify a second donor CU that provides a control plane connection for the collocated IAB-MT of the IAB node. Thus, load balancing between donor CUs can be achieved by using different donor CUs to provide a control plane connection to the core network for an IAB-MT in an IAB node and terminating the F1 interface with an IAB-DU in the IAB node.

Reference is now made to fig. 5. Fig. 5 shows a flowchart illustrating an example process 500 for sharing an IAB node, in accordance with some example embodiments of the present disclosure. For discussion purposes, the process 500 will be described with reference to fig. 3a and 3b. Process 500 involves at least donor 1-CU 311 from a first operator, donor 2-CU321 from a second operator, and IAB node 324 shared between the first operator and the second operator. It should be understood that actions having the same reference numerals as in fig. 4a are the same as those described with reference to fig. 4a and thus will not be described again herein.

In process 500, the donor 2-CU321 sends 405 a second identifier for the IAB node 324 assigned by the donor 2-CU321 to the IAB node 324. For example, donor 2-CU321 may send an RRC reconfiguration message to IAB-MT 401 that includes the BAP address.

In some example embodiments, the internal communication may be performed 515 within the IAB node 324 to communicate identification information related to the IAB node 324. In the case where the IAB node 324 includes IAB-DUa403 and IAB-DUb402, the BAP address assigned to the IAB-MT 401 may be shared with the collocated IAB-DUa403 and collocated IAB-DUb 402. For example, the BAP address received at 405 can be sent from IAB-MT 401 to collocated IAB-DUb402 and IAB-DUa 403.

The IAB node 324 sends 520 identification information relating to the IAB node 324 to the donor l-CU 311. For example, the IAB-DUa403 provides a second identifier (e.g., BAP address) of the IAB node 324 to the donor l-CU 311. The IAB-DUa403 may also provide information to the donor 1-CU 311 relating to its cell, as well as identification information relating to the IAB node 324 at 520. In this example embodiment, the donor 1-CU 311 may know the first identifier of the donor 2-CU321 via an interface (e.g., an Xn interface) between the donor 1-CU 311 and the donor 2-CU 321.

In some example embodiments, the second identifier may be sent during the process for establishing the Fl interface between the IAB node 324 and the donor l-CU 311. For example, the second identifier may be included in a Fl SETUP REQUEST message from the IAB-DUa403 to the donor 1-CU 311.

Alternatively or additionally, in some example embodiments, the second identifier may be sent during a procedure for updating the configuration of the IAB-DU for the IAB node 324. For example, the IAB-DUa403 may include the second identifier in a message towards the donor 1-CU 311 during the F1gNB-DU configuration update procedure.

Alternatively or additionally, in some example embodiments, the second identifier may be sent during a process for updating the configuration of the donor l-CU 311. For example, the IAB-DUa403 may include the second identifier in a message towards the donor 1-CU 311 during the F1 gNB-CU configuration update procedure.

It should be appreciated that since the second identifier is assigned to the IAB node 324 by the donor 2-CU321, the same identifier as the second identifier may be assigned by the donor 1-CU 311 to an IAB node under the domain of donor 1, e.g., the IAB node 316 shown in fig. 3a and 3b. As an example, when the second identifier is a BAP address, the donor 2-CU321 assigns a BAP address (e.g., # 3) to the IAB node 324. The IAB node 316 may have been assigned the same BAP address (i.e., # 3) by the donor 1-CU 311.

In this case, the donor l-CU 311 may incorrectly determine that the IAB-DUa403 is collocated with the IAB-MT of the IAB node 316 based on the second identifier, e.g., the BAP address (e.g., # 3), received from the IAB-DUa403 at 520. Thus, in some example embodiments, an indication may be sent with the second identifier of the IAB node 324 to avoid erroneous determination of the juxtaposition of the IAB-DUb 403 by the donor 1-CU 311. For example, the indication may be a flag that informs the donor l-CU 311 not to determine (or not to bind) the collocated IAB-MT for (or to) the IAB-DU based on the identification information sent at 520. Instead, donor 1-CU 311 will determine (or bind) the collocated IAB-MT later, e.g., upon receiving other identity information from donor 2-CU321 at 525. In case the second identifier is included in the F1 SETUP REQUEST message, the F1 SETUP REQUEST message may further include the indication. In one example embodiment, the indication may be a BAP address assigned to the IAB node 324 by the donor 2-CU321, e.g., at 405. In some example embodiments, donor l-CU 311 may be preconfigured to determine the collocated IAB-MT based on the received second identifier and other information from donor 2-CU321, and thus such an indication (e.g., flag) may be avoided.

Continuing with process 500, donor 2-CU321 sends 525 cell information to donor l-CU 311. The cell information includes a second identifier of the IAB node 324 and at least one identifier 324 (hereinafter also referred to as a "third identifier") of a cell served by the IAB node. The third identifier may include a cell ID of a cell served by the IAB node 324.

In other words, for one or more cells provided by the shared IAB 324 deployed by the second operator and shared with the first operator, the cell information includes the BAP address assigned to the shared IAB node 324 by the donor 2-CU321, i.e., the BAP address assigned to the IAB-MT 401 of the shared IAB node 324. For example, the cell information includes BAP addresses of IAB nodes 324 of one or more cells provided by collocated IAB-DUa403 sharing the IAB nodes 324.

In the case where the IAB node 324 is shared for multiple operators, multiple donor CUs from multiple operators may report the same cell of the IAB node 324 as its served cell to the donor l-CU 311. Only the donor CU (i.e., donor 2-CU 321) from the hosting operator provides the BAP address of the shared IAB node 324. As an example, the IAB node 324 is shared with the first operator and the third operator, as shown in fig. 3b. In this case, both the donor 2-CU321 and the donor 3-CU331 report the cell of the IAB node 324 as the served cell to the donor l-CU 331. The donor 2-CU321 provides the BAP address of the IAB node 324 along with the cell ID, while the donor 3-CU331 provides the cell ID without the BAP address of the IAB node 324.

In some example embodiments, the cell information may be sent during a procedure for establishing an Xn interface between donor 2-CU321 and donor l-CU 311. For example, donor 2-CU321 may include cell information in a message towards donor 1-CU 311 during the Xn setup procedure.

Alternatively or additionally, in some example embodiments, the cell information may be sent during a process for updating the configuration needed for donor 2-CU321 and donor 1-CU 311 to interoperate over the Xn interface. For example, donor 2-CU321 may include cell information in a message to donor l-CU 311 during the Xn NG-RAN node configuration update procedure.

In the example embodiment described above, donor l-CU 311 may reuse the gNB ID in the Xn message to identify donor 2-CU 321. Furthermore, the trigger for sending cell information may be similar to normal gbb-DU sharing.

In some example embodiments, the transmission of cell information at 525 may be performed prior to the transmission of identification information related to the IAB node 324 at 520. In this way, it may be avoided that the concatenation of the IAB-DUb 403 is erroneously determined by the donor 1-CU 311 as described above.

Continuing with the process 500, the donor l-CU 311 determines 530 the association of the IAB node 324 with the donor 2-CU321 based on the cell information and the identification information related to the IAB node 324. In other words, based on the cell information and identification information received at 520 and 525, donor l-CU 311 may identify IAB-MT 401 collocated with IAB-DUa403 and determine that donor 2-CU321 manages the collocated IAB-MT 401.

In an example embodiment where the second identifier comprises a BAP address, donor l-CU 311 receives the BAP address from IAB-DUa 403. Donor l-CU 311 receives cell information from donor 2-CU321 that also includes a BAP address. For example, the donor l-CU 311 receives 520 an indication (e.g., a specific BAP address # 3) and cell information (e.g., cell ID # 111) from the IAB-DUa403, and receives 525 a cell ID #111 of a specific cell and a specific BAP address (e.g., # 3) of the specific cell of the IAB node 324 from the donor 2-CU 321. In this case, donor l-CU 311 may determine IAB-MT 401 collocated with IAB-DUa403 and determine that donor 2-CU321 manages the collocated IAB-MT. It should be understood that the values of the BAP address and the cell ID are given for convenience of illustration and do not limit the scope of protection.

Then, based on the determined association, the donor l-CU 311 sends 430 a request to the donor 2-CU 312 to configure the radio channel towards the IAB node 324. The request includes a second identifier for identifying the IAB node 324 of the IAB-MT 401. The donor 2-CU321 initiates 435 a procedure for configuring the radio channel towards the IAB node 324.

In the example process 400, the identifiers of the shareab node and the identifiers of the one or more cells of the shareab node are provided by donor CUs from the hosting operator to donor CUs from the participating operators. In this way, donor CUs from the participating operators may identify the donor CU that controls the shared IAB node. Thus, IAB node sharing is supported without sharing donor and intermediate IAB nodes.

It should be understood that although IAB-DUa403 and IAB-DUb402 are shown separately in fig. 4 and 5, this is for illustrative purposes only and does not represent any limitation on the scope of protection. In some example embodiments, the actions described with respect to IAB-DUa403 and IAB-DUb402 may be implemented by the same device or apparatus.

It should also be understood that although the example processes 400 and 500 are described separately, aspects of both processes may be combined. For example, in some embodiments, the first identifier, the second identifier, and the third identifier may all be provided to donor l-CU 311.

Example protocol Stack

Reference is now made to fig. 6a and 6b. Fig. 6a illustrates an example protocol stack 610 for supporting the F1-U plane, according to some example embodiments of the present disclosure. Fig. 6b illustrates an example protocol stack 650 for supporting the F1-C plane, according to some example embodiments of the present disclosure. Fig. 6a and 6b are described in relation to fig. 3a and 3b.

Typically, the IAB network comprises a network 601 managed by a first operator and a network 602 managed by a second operator. The network 601 includes a donor 1-CU 311, an IAB-DUa from the first operator's IAB node 312 and a shared IAB node 324. The network 602 includes the donor 2-DU322, the IAB node 323, the IAB-DUb of the IAB-MT shared IAB node 324, and the IAB-DUb of the shared IAB node 324.

As shown in FIGS. 6a and 6b, a BH RLC channel may be established between the IAB MT of the IAB node 312 and the IAB-DUa of the shared IAB node 324, between the IAB-MT of the shared IAB node 324 and the IAB-DU of the IAB node 323, and between the IAB-MT of the IAB node 323 and the donor 2-DU. The protocol layers include, from bottom to top, a Physical (PHY) layer, a Medium Access Control (MAC) layer, a Radio Link Control (RLC) layer, and a BAP layer.

The F1 plane traffic includes F1-U plane traffic (also referred to as "F1-U traffic") and F1-C plane traffic (also referred to as "F1-C traffic"). The F1-U traffic and the F1-C traffic are passed over the BAP layer. Specifically, the protocol layers of the F1-U traffic include, from bottom to top, an IP layer, a User Datagram Protocol (UDP) layer, and a General Packet Radio Service (GPRS) tunneling protocol user (GTP-U) layer. The protocol layers of the F1-C service comprise an IP layer, a Stream Control Transmission Protocol (SCTP) layer and an F1AP layer from bottom to top.

As shown in fig. 6a and 6b, F1-U traffic and F1-C traffic between a donor 1-CU 311 from a first operator (which is a participating operator) and its IAB node (e.g., IAB node 312) in a shared backhaul network are IP routed from a second operator (which is a hosting operator) via a donor 2-DU322 and passed over the backhaul network 602 of the second operator. The shared IAB node 324 uses the BAP address assigned by the second operator. The first operator may fully configure and manage the child IAB nodes under the shared IAB node 324 without sharing the child IAB nodes and without involving the second operator. The shared IAB node 324 broadcasts the PLMN ID for the second operator and the first operator. The child IAB nodes of the first operator broadcast the PLMN ID of the first operator. For terminal devices subscribed to a first operator, the use of a shared backhaul from a second operator is transparent.

Thus, in the example environment of fig. 3a, IAB node 312 and IAB node 313 from the first operator are configured to have BAP addresses from the first operator. To route BAP packets for IAB node 312 and IAB node 313 through the IAB network of the second operator to donor 1-CU 311 of the first operator, shared IAB node 324 may be configured to perform BAP header conversion. For example, the BAP address translation may be similar to address translations used in inter-donor routing in inter-donor topological redundancy.

Example methods and apparatus

Fig. 7 illustrates a flowchart of an example method 700 for configuring an IAB node, in accordance with some example embodiments of the present disclosure. The method 700 may be implemented at a first device. For discussion purposes, the method 700 will be described with reference to fig. 3a, 3b, and 3 c.

At block 710, a first device from a first operator obtains identification information relating to at least one of a second device from a second operator and a third device from the second operator. In some embodiments, the first operator and the second operator are different operators, and the second device is shared for the first operator. For example, a first device may include donor l-CU 311, a second device may include IAB node 324, and a third device may include donor 2-CU 321.

In some example embodiments, the first device may receive, from the second device, a first identifier that uniquely identifies the third device and a second identifier of the second device assigned by the third device. For example, the first identifier may include the global gbb ID of the donor 2-CU321, and the second identifier may include the BAP address of the IAB node 324.

In some example embodiments, the first identifier and the second identifier may be received during a process for establishing an F1 interface between the first device and the second device. Alternatively or additionally, the first identifier and the second identifier may be received during a process for updating a configuration of a distributed unit of the second device. Alternatively or additionally, the first identifier and the second identifier may be received during a process for updating a configuration of the first device.

In some example embodiments, the first device may receive, from the third device, a second identifier of the second device assigned by the third device and at least a third identifier of a cell served by the second device. In some example embodiments, the second identifier may include a BAP address of the IAB node 324. The third identifier may include a cell ID of the cell.

In some example embodiments, the second identifier and the third identifier may be received during a process for establishing an Xn interface between the first device and the third device. Alternatively or additionally, the second identifier and the third identifier may be received during a process for updating a configuration required for the first device and the third device to interoperate over the Xn interface.

At block 720, the first device determines an association of the second device with the third device based on the identification information. At block 730, the first device sends a request to the third device for configuring a radio channel towards the second device based on the determined association.

In some embodiments, the first operator and the second operator may be the same operator, and in this case, the second device is an IAB node having connections with more than one donor CU from the same operator. For example, a first device includes a donor CU that manages an interface (e.g., an F1 interface) with a second device. The third device comprises another donor CU providing a control plane connection to the core network for the second device. For example, the second device may comprise the IAB node 374, the first device may comprise the donor 1-CU 361, and the third device may comprise the donor 2-CU 371.

Fig. 8 shows a flowchart of an example method 800 for configuring an IAB node, in accordance with some example embodiments of the present disclosure. The method 800 may be implemented at a second device. For discussion purposes, the method 800 will be described with reference to fig. 3a, 3b, and 3 c.

At block 810, a second device from a second operator obtains a first identifier that uniquely identifies a third device. The third device is from a second operator and provides a control plane connection to the core network for the second device. For example, the first identifier may include a global gNB ID of the donor 2-CU 321. In some example embodiments, the first operator and the second operator are different operators, and the second device is shared for the first operator. For example, a first device may include donor l-CU 311, a second device may include IAB node 324, and a third device may include donor 2-CU 321.

In some example embodiments, the second device may receive, from the third device, an F1AP message including the first identifier. Alternatively or additionally, the second device may receive an RRC message from the third device including the first identifier. Alternatively or additionally, the second device may receive configuration information from the OAM entity that includes the first identifier.

At block 820, the second device transmits to the first device from the first operator the first identifier and a second identifier of the second device assigned by the third device. For example, the second identifier may include a BAP address of the IAB node 324.

In some example embodiments, the first identifier and the second identifier may be transmitted during a process for establishing an F1 interface between the first device and the second device. Alternatively or additionally, the first identifier and the second identifier may be sent during a procedure for updating a configuration of a DU of the second device (e.g., an IAB-DU of the IAB node 324). Alternatively or additionally, the first identifier and the second identifier may be transmitted during a process for updating the configuration of the first device.

In some embodiments, the first operator and the second operator may be the same operator, and in this case, the second device is an IAB node having connections with more than one donor CU from the same operator. For example, a first device includes a donor CU that manages an interface (e.g., an F1 interface) with a second device. The third device comprises another donor CU providing a control plane connection to the core network for the second device. For example, the second device may include IAB node 374, the first device may include donor 1-CU 361, and the third device may include donor 2-CU 371.

Fig. 9 illustrates a flowchart of an example method 900 for sharing IAB nodes, according to some example embodiments of the present disclosure. The method 900 may be implemented at a third device. For discussion purposes, the method 900 will be described with reference to fig. 3a, 3b, and 3 c.

At block 910, a third device from the second operator provides identification information to the first device from the first operator, the identification information relating to at least one of the second device and the third device. In some embodiments, the first operator and the second operator are different operators, and the second device is from the second operator and shared for the first operator. For example, a first device may include donor l-CU 311, a second device may include IAB node 324, and a third device may include donor 2-CU 321.

In some example embodiments, the third device may send, to the first device via the second device, a first identifier that uniquely identifies the third device. For example, the third device may send the first identifier to the second device, and the second device then forwards the first identifier to the first device. The first identifier may include a global gbb ID of the donor 2-CU 321.

In some example embodiments, the third device may send an F1AP message including the first identifier to the second device. Alternatively or additionally, the first device may send an RRC message including the first identifier to the second device.

In some example embodiments, the third device may send to the first device a second identifier of the second device assigned by the third device and at least a third identifier of a cell served by the second device. In some example embodiments, the second identifier may include a BAP address of the IAB node 324. The third identifier may include a cell ID of the cell.

In some example embodiments, the second identifier and the third identifier may be transmitted during a process for establishing an Xn interface between the first device and the third device. Alternatively or additionally, the second identifier and the third identifier may be sent during a process for updating a configuration required for the first device and the third device to interoperate over the Xn interface.

At block 920, the third device receives a request from the first device to configure a radio channel towards the second device. The third device may initiate a procedure for configuring a radio channel towards the IAB node 324.

It should be understood that the transmission of the identification information (including the first identifier, the second identifier, the third identifier) is not limited to any particular manner. In other words, in some embodiments, these identifiers may be sent in a different process with different signaling than described in the above examples.

In some example embodiments, a first apparatus (e.g., donor l-CU 311) capable of performing method 700 may include means for performing the respective operations of method 700. The component may be implemented in any suitable form. For example, the components may be implemented in circuitry or software modules. The first means may be implemented as the donor l-CU 311 or included in the donor l-CU 311.

In some example embodiments, a first apparatus from a first operator comprises: means for obtaining identification information, the identification information relating to at least one of a second apparatus from a second operator and a third apparatus from the second operator; means for determining an association of the second apparatus with a third apparatus based on the identification information; and means for sending a request to a third apparatus for configuring a radio channel towards the second apparatus based on the determined association. The first apparatus comprises a first integrated access and backhaul donor central unit, the second apparatus comprises an integrated access and backhaul node, and the third apparatus comprises a second integrated access and backhaul donor central unit.

In some example embodiments, the first operator and the second operator may be different operators, and the second apparatus is shared for the first operator. In some example embodiments, the first operator and the second operator may be the same operator, and the second apparatus is an IAB node having connections with more than one donor CU from the same operator.

In some example embodiments, the means for obtaining identification information comprises: means for receiving, from the second apparatus, a first identifier that uniquely identifies the third apparatus and a second identifier of the second apparatus assigned by the third apparatus.

In some example embodiments, the first identifier and the second identifier are received during at least one of: a procedure for establishing a Fl interface between a first device and a second device, a procedure for updating a configuration of a distributed unit of the second device, or a procedure for updating a configuration of the first device.

In some example embodiments, the means for obtaining identification information comprises: means for receiving, from a third apparatus, a second identifier of the second apparatus assigned by the third apparatus and at least a third identifier of a cell served by the second apparatus.

In some example embodiments, the second identifier and the third identifier are received during at least one of: a procedure for establishing an Xn interface between the first device and the third device, or a procedure for updating a configuration required for the first device and the third device to interoperate through the Xn interface.

In some example embodiments, the second identifier of the second apparatus comprises a backhaul adaptation protocol address assigned by the third apparatus.

In some example embodiments, a second apparatus (e.g., IAB node 324) capable of performing method 800 may include means for performing the respective operations of method 800. The component may be implemented in any suitable form. For example, the component may be implemented in circuitry or a software component. The second apparatus may be implemented as the IAB node 324 or included in the IAB node 324.

In some example embodiments, the second apparatus from the second operator comprises: means for obtaining a first identifier uniquely identifying a third apparatus, the third apparatus being from a second operator and providing a control plane connection to a core network for the second apparatus; and means for transmitting the first identifier and a second identifier of the second apparatus allocated by the third apparatus to the first apparatus from the first operator. The first apparatus comprises a first integrated access and backhaul donor central unit, the second apparatus comprises an integrated access and backhaul node, and the third apparatus comprises a second integrated access and backhaul donor central unit.

In some example embodiments, the means for obtaining the first identifier comprises at least one of: the apparatus may include means for receiving an F1 application protocol message including a first identifier from a third apparatus, means for receiving a radio resource control message including the first identifier from the third apparatus, or means for receiving configuration information including the first identifier from an operations management and maintenance entity.

In some example embodiments, the first identifier and the second identifier are transmitted during at least one of: a procedure for establishing a Fl interface between a first device and a second device, a procedure for updating a configuration of a distributed unit of the second device, or a procedure for updating a configuration of the first device.

In some example embodiments, a third apparatus (e.g., donor 2-CU 321) capable of performing method 900 may include means for performing the respective operations of method 900. The component may be implemented in any suitable form. For example, the components may be implemented in circuitry or software modules. The first apparatus may be implemented as the donor 2-CU321 or included in the donor 2-CU 321.

In some example embodiments, the third apparatus from the second operator comprises: means for providing, to a first apparatus from a first operator, identification information relating to at least one of a second apparatus and a third apparatus, the second apparatus from a second operator; and means for receiving a request from the first apparatus for configuring a radio channel towards the second apparatus. The first apparatus comprises a first integrated access and backhaul donor central unit, the second apparatus comprises an integrated access and backhaul node, and the third apparatus comprises a second integrated access and backhaul donor central unit.

In some example embodiments, the means for providing the identification information to the first apparatus comprises: means for transmitting, to the first apparatus via the second apparatus, a first identifier that uniquely identifies the third apparatus.

In some example embodiments, the means for transmitting the first identifier comprises at least one of: means for transmitting an F1 application protocol message including the first identifier to the second apparatus, or means for transmitting a radio resource control message including the first identifier to the second apparatus.

In some example embodiments, the means for providing the identification information to the first apparatus comprises: means for transmitting, to the first apparatus, the second identifier of the second apparatus assigned by the third apparatus and at least a third identifier of a cell served by the second apparatus.

In some example embodiments, the second identifier and the third identifier are transmitted during at least one of: a procedure for establishing an Xn interface between the first device and the third device, or a procedure for updating a configuration required for the first device and the third device to interoperate through the Xn interface.

Fig. 10 is a simplified block diagram of a device 1000 suitable for implementing embodiments of the present disclosure. For example, donor l-CU 311, donor 2-CU 322, IAB node 324, etc., shown in fig. 3a and/or fig. 3b may be implemented by device 1000. As shown, the device 1000 includes one or more processors 1010, one or more memories 1020 coupled to the processors 1010, and one or more communication components 1040 coupled to the processors 1010.

The communication section 1040 is for bidirectional communication. Communications section 1040 has at least one antenna to facilitate communications. A communication interface may represent any interface necessary to communicate with other network elements.

The processor 1010 may be of any type suitable for a local technology network, and may include, as non-limiting examples, one or more of the following: general purpose computers, special purpose computers, microprocessors, digital Signal Processors (DSPs) and processors based on a multi-core processor architecture. Device 1000 may have multiple processors, such as application specific integrated circuit chips that are time dependent from a clock synchronized to the main processor.

The memory 1020 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memory include, but are not limited to, read Only Memory (ROM) 1024, electrically Programmable Read Only Memory (EPROM), flash memory, a hard disk, a Compact Disk (CD), a Digital Versatile Disk (DVD), and other magnetic and/or optical storage. Examples of volatile memory include, but are not limited to, random Access Memory (RAM) 1022 and other volatile memory that does not persist during a power failure.

Computer programs 1030 include computer-executable instructions that are executed by the associated processor 1010. The program 1030 may be stored in the ROM 1020. Processor 1010 may perform any suitable actions and processes by loading program 1030 into RAM 1020.

Embodiments of the present disclosure may be implemented by way of program 1030 such that device 1000 may perform any of the processes of the present disclosure as discussed with reference to fig. 4-5 and 7-9. Embodiments of the present disclosure may also be implemented by hardware or a combination of software and hardware.

In some example embodiments, the program 1030 may be tangibly embodied in a computer-readable medium, which may be included in the device 1000 (such as in memory 1020) or in other storage accessible to the device 1000. Device 1000 can load program 1030 from the computer-readable medium into RAM 1022 for execution. The computer readable medium may include any type of tangible, non-volatile memory, such as a ROM, EPROM, flash memory, hard disk, CD, DVD, etc. Fig. 11 shows an example of a computer readable medium 1000 in the form of a CD or DVD. The program 1030 is stored on a computer readable medium.

It should be appreciated that future networks may utilize Network Function Virtualization (NFV), which is a network architecture concept that proposes virtualizing network node functions as "building blocks" or entities that may be operatively connected or linked together to provide services. A Virtualized Network Function (VNF) may comprise one or more virtual machines that run computer program code using standard or general-purpose types of servers rather than custom hardware. Cloud computing or data storage may also be utilized. In radio communication, this may mean that the node operation should be performed at least partly in a central/centralized unit CU (e.g. a server, a host or a node) operatively coupled to a distributed unit DU (e.g. a radio head/node). Node operations may also be distributed among multiple servers, nodes, or hosts. It should also be understood that the allocation of work between core network operation and base station operation may vary depending on the implementation.

In one embodiment, the server may generate a virtual network through which the server communicates with the distributed elements. In general, virtual networks may involve the process of combining hardware and software network resources and network functions into a single software-based management entity (virtual network). Such a virtual network may provide flexible distribution of operations between the server and the radio heads/nodes. In practice, any digital signal processing task may be performed in a CU or DU, and the boundary at which responsibility is transferred between a CU and DU may be chosen depending on the implementation.

Thus, in one embodiment, a CU-DU architecture is implemented. In this case, the device 1000 may be included in a central unit (e.g., control unit, edge cloud server, server) operably coupled (e.g., via a wireless or wired network) to a distributed unit (e.g., remote radio head/node). That is, the central unit (e.g., edge cloud server) and the distributed units may be independent devices that communicate with each other via a radio path or via a wired connection. Alternatively, they may be in the same entity communicating via a wired connection or the like. An edge cloud or edge cloud server may serve multiple distributed units or radio access networks. In an embodiment, at least some of the described processes may be performed by a central unit. In another embodiment, device 1000 may instead be included in a distributed unit, and at least some of the described processes may be performed by the distributed unit.

In one embodiment, the execution of at least some of the functions of the device 1000 may be shared between two physically separated devices (DU and CU) forming one operational entity. Accordingly, the apparatus may be considered to depict an operational entity comprising one or more physically separate devices for performing at least some of the described processes. In one embodiment, such CU-DU architecture may provide flexible distribution of operations between CUs and DUs. In practice, any digital signal processing task may be performed in a CU or DU, and the boundary at which responsibility between the CU and DU is transferred may be chosen depending on the implementation. In one embodiment, the apparatus 1000 controls the execution of processes regardless of the location of the devices and regardless of where the processes/functions are executed.

In general, the various embodiments of the disclosure may be implemented using hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented using hardware, while other aspects may be implemented using firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects of the embodiments of the disclosure are illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that the blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product comprises computer executable instructions, such as instructions comprised in a program component, which are executed in a device on a target real or virtual processor to perform the method 700 as described above with reference to fig. 7, the method 800 as described above with reference to fig. 8 and the method 900 as described above with reference to fig. 9. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform particular tasks or implement particular abstract data types. In various embodiments, the functionality of the program modules may be combined or split between program modules as desired. Machine-executable instructions of program modules may be executed within a local or distributed facility. In a distributed facility, program modules may be located in both local and remote memory storage media.

Program code for performing the methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowchart and/or block diagram to be performed. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of this disclosure, computer program code or related data may be carried by any suitable carrier to enable an apparatus, device or processor to perform various processes and operations as described above. Examples of a carrier include a signal, computer readable medium, and the like.

The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a computer-readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

Further, while operations are described in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In some cases, multitasking and parallel processing may be advantageous. Also, while several specific implementation details are included in the above discussion, these should not be construed as limitations on the scope of the disclosure, but rather as descriptions of features that may be specific to particular embodiments. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.

Although the disclosure has been described in language specific to structural features and/or methodological acts, it is to be understood that the disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

1. A first device, comprising:

at least one processor; and

at least one memory including computer program code;

wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the first device from a first operator to:

obtaining identification information relating to at least one of a second device from a second operator and shared for the first operator and a third device from the second operator;

determining an association of the second device with the third device based on the identification information; and

sending a request to the third device based on the determined association, the request for configuring a radio channel towards the second device, an

Wherein the first device comprises a first integrated access and backhaul donor central unit, the second device comprises an integrated access and backhaul node, and the third device comprises a second integrated access and backhaul donor central unit.

2. The first device of claim 1, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the first device to obtain the identification information by:

receiving, from the second device, a first identifier that uniquely identifies the third device and a second identifier of the second device assigned by the third device.

3. The first device of claim 2, wherein the first identifier and the second identifier are received during at least one of:

a procedure for establishing an F1 interface between the first device and the second device,

a procedure for updating the configuration of the distributed unit of the second device, or

A process for updating a configuration of the first device.

4. The first apparatus of claim 1, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the first apparatus to obtain the identification information by:

receiving, from the third device, a second identifier of the second device assigned by the third device and at least a third identifier of a cell served by the second device.

5. The first device of claim 4, wherein the second identifier and the third identifier are received during at least one of:

a procedure for establishing an Xn interface between the first device and the third device, or

A process for updating a configuration required for the first device and the third device to interoperate over the Xn interface.

6. The first device of any of claims 2-4, wherein the second identifier of the second device comprises a backhaul adaptation protocol address assigned by the third device.

7. A second device, comprising:

at least one processor; and

at least one memory including computer program code;

wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the second device from a second operator to:

obtaining a first identifier uniquely identifying a third device, the third device being from the second operator and providing a control plane connection to a core network for the second device; and

sending the first identifier and a second identifier of the second device assigned by the third device to a first device from a first operator, and

8. The second device of claim 7, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the second device to obtain the first identifier by at least one of:

receiving an F1 application protocol message including the first identifier from the third device,

receiving a radio resource control message including the first identifier from the third device, or

Receiving configuration information including the first identifier from an operations administration and maintenance entity.

9. The second device of claim 7, wherein the first identifier and the second identifier are transmitted during at least one of:

A process for updating a configuration of the first device.

10. A third apparatus, comprising:

at least one processor; and

at least one memory including computer program code;

wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the third device from a second operator to:

providing, to a first device from a first operator, identification information relating to at least one of a second device and the third device, the second device being from the second operator and shared for the first operator; and

receiving a request from the first device for configuring a radio channel towards the second device, an

11. The third device of claim 10, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the third device to provide the identification information to the first device by:

transmitting, to the first device via the second device, a first identifier that uniquely identifies the third device.

12. The third device of claim 11, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the third device to transmit the first identifier by at least one of:

sending an F1 application protocol message including the first identifier to the second device, or

Transmitting a radio resource control message including the first identifier to the second device.

13. The third device of claim 10, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the third device to provide the identification information to the first device by:

transmitting, to the first device, a second identifier of the second device assigned by the third device and at least a third identifier of a cell served by the second device.

14. The third device of claim 13, wherein the second identifier and the third identifier are transmitted during at least one of:

15. The third device of claim 13, wherein the second identifier of the second device comprises a backhaul adaptation protocol address assigned by the third device.

16. A method, comprising:

obtaining, at a first device from a first operator, identification information relating to at least one of a second device from a second operator and shared for the first operator and a third device from the second operator;

17. A method, comprising:

obtaining, at a second device from a second operator, a first identifier that uniquely identifies a third device, the third device being from the second operator and providing a control plane connection to a core network for the second device; and

18. A method, comprising:

providing, at a third device from a second operator, identification information relating to at least one of a second device and the third device to a first device from a first operator, the second device being from the second operator and shared for the first operator; and

19. A first apparatus from a first operator, the first apparatus comprising:

means for obtaining identification information relating to at least one of a second apparatus from a second operator and shared for the first operator and a third apparatus from the second operator;

means for determining an association of the second apparatus with the third apparatus based on the identification information; and

means for sending a request to the third apparatus based on the determined association, the request for configuring a radio channel towards the second apparatus, an

Wherein the first apparatus comprises a first integrated access and backhaul donor central unit, the second apparatus comprises an integrated access and backhaul node, and the third apparatus comprises a second integrated access and backhaul donor central unit.

20. A second apparatus from a second operator, the second apparatus comprising:

means for obtaining a first identifier uniquely identifying a third apparatus, the third apparatus being from the second operator and providing a control plane connection to a core network for the second apparatus; and

means for transmitting to a first apparatus from a first operating direction said first identifier and a second identifier of said second apparatus allocated by said third apparatus, and

21. A third apparatus from a second operator, the third apparatus comprising:

means for providing identification information relating to at least one of a second apparatus and the third apparatus to a first apparatus from a first operator, the second apparatus being from the second operator and shared for the first operator; and

means for receiving a request from the first apparatus for configuring a radio channel towards the second apparatus, an

22. A computer readable medium comprising program instructions for causing an apparatus to perform at least a method according to any one of claims 16 to 18.