Integrated Access and Backhaul Communication

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 embodiments of the present disclosure, a first donor central unit (CU) from a first operator (which is a participating operator) obtains identification information that relates 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 between the shared IAB node and the second donor CU based on the obtained identification information. Based on the determined association, the first donor CU sends a request for configuring a channel towards the shared IAB node to the second donor CU. In this way, the IAB nodes of the second operator can be shared with the first operator, and the first operator can operate cells and serve UEs via the IAB backhaul network of the second operator. This provides higher flexibility for the sharing of IAB deployments and can reduce the capital expenditure of the participating operators.

Description

Technical Field

[0001] Embodiments of the present disclosure generally relate to the field of telecommunications, and more particularly, to devices, methods, apparatuses, and computer-readable media for integrated access and backhaul (IAB) communication. Background Art

[0002] IAB has been introduced in Release 16 (Rel-16) of the 3rd Generation Partnership Project (3GPP) specifications as a key enabling factor for fast and cost-effective deployments. IAB nodes use the same or different spectrums and air interfaces for access and backhaul to create a hierarchical wireless multi-hop (multiple backhaul links) network between sites. The hops ultimately terminate at an IAB donor, which is connected to the core network via a conventional fixed backhaul. A key advantage of IAB is the ability to deploy cells flexibly and very densely without a proportional increase in the density of the transport network. Multiple deployment scenarios can be envisioned, including supporting outdoor small cell deployments, indoor (e.g., shopping malls), or even mobile relays (e.g., on buses or trains).

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

[0004] Generally, example embodiments of the present disclosure provide devices, methods, apparatuses, and computer-readable media for IAB communication.

[0005] In a first aspect, a first device is provided. The first device includes 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, together with the at least one processor, cause the first device from a first operator to obtain identification information that relates to at least one of a second device from a second operator and shared by the first operator and a third device from the second operator; determine an association between the second device and the third device based on the identification information; and send a request to the third device based on the determined association, the request being for configuring a radio channel towards the second device, and wherein the first device includes a first integrated access and backhaul donor central unit, the second device includes an integrated access and backhaul node, and the third device includes a second integrated access and backhaul donor central unit.

[0006] In a second aspect, a second device is provided. The second device includes 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 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 send 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 wherein the first device includes a first integrated access and backhaul donor central unit, the second device includes an integrated access and backhaul node, and the third device includes a second integrated access and backhaul donor central unit.

[0007] In a third aspect, a third device is provided. The third device includes 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 provide identification information related to at least one of the 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 receive a request from the first device for configuring a radio channel towards the second device, and wherein the first device includes a first integrated access and backhaul donor central unit, the second device includes an integrated access and backhaul node, and the third device includes a second integrated access and backhaul donor central unit.

[0008] In a fourth aspect, a method is provided. The method includes obtaining, at a first device from a first operator, identification information related 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 between the second device and the third device based on the identification information; and sending, based on the determined association, a request to the third device for configuring a radio channel towards the second device, and wherein the first device includes a first integrated access and backhaul donor central unit, the second device includes an integrated access and backhaul node, and the third device includes a second integrated access and backhaul donor central unit.

[0009] In a fifth aspect, a method is provided. The method includes 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 the 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 wherein the first device includes a first integrated access and backhaul donor central unit, the second device includes an integrated access and backhaul node, and the third device includes a second integrated access and backhaul donor central unit.

[0010] In a sixth aspect, a method is provided. The method includes providing, at a third device from a second operator, identification information related to at least one of a second device and a 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 receiving, from the first device, a request for configuring a radio channel towards the second device, and wherein the first device includes a first integrated access and backhaul donor central unit, the second device includes an integrated access and backhaul node, and the third device includes a second integrated access and backhaul donor central unit.

[0011] In a seventh aspect, a first apparatus is provided. The first apparatus from a first operator includes components for obtaining identification information related 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; components for determining an association between the second apparatus and the third apparatus based on the identification information; and components for sending, based on the determined association, a request to the third apparatus for configuring a radio channel towards the second apparatus, and wherein the first apparatus includes a first integrated access and backhaul donor central unit, the second apparatus includes an integrated access and backhaul node, and the third apparatus includes a second integrated access and backhaul donor central unit.

[0012] In an eighth aspect, a second apparatus is provided. The second apparatus from a second operator includes components for obtaining a first identifier uniquely identifying a third apparatus from the second operator and providing a control plane connection to a core network for the second apparatus; and components for sending the first identifier and a second identifier of the second apparatus assigned by the third device to a first apparatus from a first operator, and wherein the first apparatus includes a first integrated access and backhaul donor central unit, the second apparatus includes an integrated access and backhaul node, and the third apparatus includes a second integrated access and backhaul donor central unit.

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

[0014] In a tenth aspect, there is provided a computer-readable storage medium having program instructions stored thereon. When executed by a device, the instructions cause the device to perform the method according to the fourth, fifth, or sixth aspect described above.

[0015] It should be understood that the summary section is not intended to identify key or essential features of embodiments of the present disclosure, nor is it intended to limit the scope of the present disclosure. Other features of the present disclosure will become readily apparent through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] 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 the drawings, in which:

[0017] Figure 1 A block diagram of a system for IAB communication is shown;

[0018] Figure 2 A partial sharing scenario in which exemplary embodiments of the present disclosure can be applied is shown;

[0019] Figure 3a 、 Figure 3b and Figure 3c An exemplary IAB environment in which exemplary embodiments of the present disclosure can be implemented is shown;

[0020] Figure 4a A flowchart illustrating an exemplary process for sharing an IAB node according to some exemplary embodiments of the present disclosure is shown;

[0021] Figure 4b A flowchart illustrating an exemplary process for a non-shared IAB node according to some exemplary embodiments of the present disclosure is shown;

[0022] Figure 5 A flowchart illustrating another exemplary process for sharing an IAB node according to some exemplary embodiments of the present disclosure is shown;

[0023] Figure 6a An exemplary protocol stack for supporting the F1 user plane according to some exemplary embodiments of the present disclosure is shown;

[0024] Figure 6b An exemplary protocol stack for supporting the F1 control plane according to some exemplary embodiments of the present disclosure is shown;

[0025] Figure 7 A flowchart illustrating an exemplary method according to some exemplary embodiments of the present disclosure is shown;

[0026] Figure 8 A flowchart illustrating an exemplary method according to some exemplary embodiments of the present disclosure is shown;

[0027] Figure 9 A flowchart of an example method according to some example embodiments of the present disclosure is shown;

[0028] Figure 10 A simplified block diagram of a device suitable for implementing embodiments of the present disclosure is shown; and

[0029] Figure 11 A block diagram of an example computer-readable medium according to some example embodiments of the present disclosure is shown.

[0030] Throughout the drawings, the same or similar reference numerals denote the same or similar elements. Detailed Description

[0031] The principles of the present disclosure will now be described with reference to some example embodiments. It should be understood that the description of these embodiments is only for illustration and to assist those skilled in the art in understanding and implementing the present disclosure, and does not represent any limitation on the scope of the present disclosure. The disclosure described herein can be implemented in various other ways than those described below.

[0032] In the following description and claims, unless otherwise defined, 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 pertains.

[0033] References in this disclosure to "one embodiment", "an embodiment", "example embodiment", etc., indicate that the described embodiment may include a particular feature, structure, or characteristic, but not necessarily every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an example embodiment, it is considered within the knowledge of those skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments (whether or not explicitly described).

[0034] It should be understood that although the terms "first" and "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. For example, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element, without departing from the scope of the example embodiments. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.

[0035] The terms used herein are for the purpose of describing particular embodiments only and are not intended to limit the 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" and / or "contains", when used herein, specify the presence of the 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 combinations thereof.

[0036] As used in this application, the term "circuit" may refer to one or more or all of the following:

[0037] (a) A pure hardware circuit implementation (such as an implementation using only analog and / or digital circuitry), and

[0038] (b) A combination of hardware circuits and software, such as, where applicable:

[0039] (i) A combination of (one or more) analog and / or digital hardware circuits and software / firmware, and

[0040] (ii) Any portion of (one or more) hardware processors (including digital signal processors), software, and (one or more) memories having software that work together to cause a device (such as a mobile phone or a server) to perform various functions, and

[0041] (c) (One or more) hardware circuits and / or (one or more) processors, such as (one or more) microprocessors or a portion of (one or more) microprocessors, which require software (e.g., firmware)

[0042] to operate, but the software may be absent when not needed to operate.

[0043] The definition of the circuitry shall apply to all uses of the term in this application, including in any claims. As a further example, as used in this application, the term circuitry also encompasses an implementation of only a hardware circuit or a processor (or processors) or a portion of a hardware circuit or a processor and its (or their) accompanying software and / or firmware. For example, if applicable to a particular claim element, the term circuitry also encompasses a baseband integrated circuit or a 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.

[0044] As used herein, the term "communication network" refers to a network that follows 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), etc. Additionally, the communication between a terminal device and a network device in the communication network or the communication between network devices can be performed according to any suitable communication protocol, including but not limited to the 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 to be developed in the future. Embodiments of the present disclosure can be applied to various communication systems. Given the rapid development of communications, there will of course also be future types of communication technologies and systems in which the present disclosure can be embodied. The scope of the present disclosure should not be regarded as being limited to the above systems only.

[0045] As used herein, the term "network device" refers to a node in a communication network through which a terminal device accesses the network and receives services therefrom. The network device may refer to a base station (BS) or an access point (AP), such as Node B (NodeB or NB), evolved Node B (eNodeB or eNB), NR NB (also known as gNB), Remote Radio Unit (RRU), Radio Header (RH), Remote Radio Head (RRH), relay, low power nodes such as femto, pico, etc., depending on the terminology and technology applied. Additionally, 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.

[0046] 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, a user equipment (UE), a user station (SS), a portable user station, a mobile station (MS), or an access terminal (AT). Terminal devices may include, but are not limited to, mobile phones, cellular phones, smart phones, IP voice (VoIP) phones, wireless local loop phones, tablet computers, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices such as digital cameras, game terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, lap-mounted embedded devices (LEEs), lap-mounted equipment (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., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in an industrial and / or automated processing chain environment), consumer electronic devices, devices operating on commercial and / or industrial wireless networks, etc. In the following description, the terms "terminal device", "communication device", "terminal", "user equipment", and "UE" may be used interchangeably.

[0047] As used herein, the term "operator-owned device" or a similar term means that the device is deployed by an operator and is associated with one or more public land mobile network (PLMN) identifiers (IDs) of the operator. The term "device owned by a first operator and shared for a second operator" or a similar term means that the device is deployed by the first operator and is associated with one or more PLMN IDs of the first operator and additional one or more PLMN IDs of the second operator.

[0048] Example environment

[0049] Figure 1 A block diagram of an example IAB system 100 is shown. 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 node 120".

[0050] 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 / fiber connection to the core network. The IAB donor 110 may include a CU 110-11 and one or more DUs.Figure 1 By way of example, it is shown that the IAB donor 110 includes a DU 110-12. Hereinafter, the CU of the IAB donor is also referred to as the donor CU or the donor central unit or the IAB donor CU; and the DU of the IAB donor is also referred to as the donor DU or the donor distributed unit or the IAB donor DU.

[0051] An IAB node (e.g., IAB node 120) may include a DU (also referred to as an IAB-DU), and a mobile terminal (MT, also referred to as an IAB-MT) that maintains a connection with one or more upstream nodes (e.g., using dual connectivity). Similar to a conventional user equipment (i.e., UE), the MT of the IAB node may use radio resource control (RRC) signaling to provide radio link measurements of alternative upstream nodes to its current serving gNB CU. Migration may be performed, for example, handover of the IAB-MT based on signal strength, signal quality, and other factors. Thus, an IAB topology such as Figure 1 shown may be non-static. As radio conditions fluctuate and IAB nodes move, are added, or are removed, the IAB topology may change over time.

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

[0053] The IAB donor 110 may serve directly connected IAB nodes (such as IAB node 120-11 and IAB node 120-12), and IAB nodes linked through 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). The IAB node 120 may serve one or more terminal devices directly connected to the IAB node 120. For example, as Figure 1 shown, the IAB node 120-11 may serve the terminal device 130 directly connected to the IAB node 120-11, the IAB node 120-21 may serve the terminal device 140 directly connected to the IAB node 120-21, and the IAB node 120-31 may serve the terminal device 150 directly connected to the IAB node 120-31.

[0054] 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. The backhaul (BH) radio link control (RLC) channel towards the IAB node 120 is established via the RRC procedure. To manage the BH RLC channel towards the IAB node 120, the donor CU 110-11 collocates the IAB-MT and the 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 that the donor CU 110-11 can know the collocation of the IAB-DU and a specific IAB-MT.

[0055] It should be understood that the number of IAB nodes and the number of terminal devices connected to the IAB nodes are for illustrative purposes only and do not imply any limitation. The IAB system may include any suitable number of IAB nodes and terminal devices adapted to implement the example embodiments of the present disclosure.

[0056] 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 can be shared among multiple operators. The donor gNB (i.e., the donor DU and / or the donor CU) from one operator is shared for another operator. Accordingly, the relays installed on the vehicles are also shared for other operators.

[0057] In some scenarios, network sharing for ordinary gNBs can be considered. For example, in some use cases, it may be necessary to support the sharing of gNBs (including sharing of gNB-DUs and gNB-CUs). In some cases, it may be necessary to support a scenario where only the gNB-DU is shared and the gNB-CU is not shared.

[0058] In the IAB system, it is also necessary to support the sharing of the network of IAB nodes (including IAB nodes, IAB donor CUs / DUs), and to share only the IAB nodes without sharing the donor CUs and donor DUs. For example, in a shopping mall, an airport, or a train, multiple users may require services from multiple operators. This requires a large number of installations to operate two or more IAB networks within the building, which will result in high costs and difficulty in finding antenna points. Therefore, it is desirable to share the IAB network among operators.

[0059] However, in the IAB system, it may not be necessary to share all IAB nodes. Instead, the operator of the donor gNB may only want to share a selected subset of its IAB nodes with another operator. Now refer to Figure 2 . Figure 2 Partial sharing of IAB nodes in the IAB network with multiple operators is shown.

[0060] In the sharing scenario 200 of the example section, the donor gNB 121 including the donor CU and the donor DU is deployed by the second operator 101, and the donor CU 122 is deployed by the first operator 102. The donor gNB 121 and the donor CU 122 communicate with each other, for example, via the Internet Protocol (IP) connection 143 between the DU of the donor gNB 121 and the donor CU 122, or the Xn interface between the CU of the donor gNB 121 and the donor CU 122.

[0061] The IAB nodes 111 and 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, the terminal device 130 subscribed to the first operator 102 can be served by the IAB node 112. As Figure 2 shown, the transfer path 150 between the IAB node 112 and the first operator 102 includes a wireless backhaul link between the IAB node 112 and the IAB node 111, a wireless backhaul link between the IAB node 111 and the donor gNB 121, and the IP connection 143.

[0062] Now refer to Figure 3a and Figure 3b . Figure 3a and Figure 3b show example IAB environments 300 and 305 in which example embodiments of the present disclosure can be implemented. Figure 3a and Figure 3b The deployment examples shown can be used for Figure 2 the example scenario 200 shown.

[0063] The example IAB environments 300 and 305 relate to the Public Land Mobile Network (PLMN) of three operators. Specifically, the IAB environments 300 and 305 include the donor CU (also referred to as "donor l-CU 311") of the IAB donor node from the first operator, the donor CU (also referred to as "donor 2-CU 321") of another IAB donor node from the second operator, and the donor CU (also referred to as "donor 3-CU 331") of another IAB donor node from the third operator.

[0064] In Figure 3aIn the IAB environment 300, an IP connection 351 is established between the donor l-CU 311 and the donor DU (also referred to as "donor 2-DU 322") of the IAB donor node from the second operator. The IAB nodes 323, 324, and 325 are deployed by the second operator and controlled by the donor 2-CU 321, and the donor 2-CU 321 provides a control plane connection to the core network ( Figure 3a not shown in the figure) for the IAB nodes deployed by the second operator. For example, the donor 2-CU 321 is the termination point of the control plane connection of the IAB-MT in the IAB node 323 and the IAB-MT in the IAB node 324 to the core network. 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 can serve the terminal device 315 subscribed to the first operator and the IAB node 312 deployed by the first operator. The IAB node 312 in turn serves the IAB node 313 deployed by the first operator and the terminal device 314 subscribed to the first operator. In this case, the (multiple) shared cells provided by the shared IAB node 324 can be considered as the cells served by the donor 1-CU 311 and the donor 2-CU 321. For example, when the donor 1-CU 311 or the donor 2-CU 321 exchanges the served cell information with the adjacent gNB CU through the Xn interface.

[0065] Another IP connection 352 is established between the donor l-CU 311 and the donor DU (also referred to as "donor 3-DU 332") from the third operator. The IAB nodes 333 and 334 are deployed by the third operator and controlled by the donor 3-CU 331, and the donor 3-CU 331 provides a control plane connection to the core network ( Figure 3a not shown in the figure) for the IAB nodes deployed by the third operator. For example, the donor 3-CU 331 is the termination point of the control plane connection of the IAB-MT in the IAB node 333 and the IAB-MT in the IAB node 334 to the core network. The IAB node 333 is shared with the first operator. As a result, the IAB node 333 can serve the IAB node 317 deployed by the first operator. In this case, the (multiple) shared cells provided by the shared IAB node 333 can be considered as the cells served by both the donor 1-CU 311 and the donor 3-CU 331. For example, when the donor 1-CU 311 or the donor 2-CU331-CU 331 exchanges the served cell information with the adjacent gNB CU through the Xn interface.

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

[0067] In the IAB environment 305, an IP connection 353 is established between the donor l - CU 311 and the donor 2 - DU 322. Similarly, another IP connection 354 is established between the donor 3 - CU 331 and the donor 2 - DU 322. The IAB node 324 deployed by the second operator is shared by both the first operator and the third operator. As a result, the IAB node 324 can serve the terminal device 335 subscribed to the third operator and the IAB node 312 deployed by the first operator. In this case, the (multiple) shared cells provided by the shared IAB node 324 can be considered as the cells served by the donor 1 - CU 311, the donor 2 - CU 321, and the donor 3 - CU 331. For example, when the donor 1 - CU 311 or the donor 2 - CU 321 or the donor 3 - CU 331 exchanges the served cell information with the adjacent gNB CU through the Xn interface.

[0068] For the shared IAB node 324 as Figure 3a shown, the second operator is the hosting operator with the operation control right of the shared IAB node, and the first operator is the participating operator authorized to access the resources of the shared IAB. IAB node. Similarly, for the shared IAB node 324 as Figure 3b shown, 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 the F1 interface with the donor CU from the hosting operator, another IAB - DU for the F1 interface with the donor CU from the first participating operator, and another IAB - DU for the F1 interface with the donor CU from the second participating operator, etc. For example, in Figure 3a the shared IAB node 324 may include an IAB - DUa for the F1 interface with the donor 1 - CU 311 from the first operator ( Figure 3a not shown in), and an IAB - DUb for the F1 interface with the donor 2 - CU 321 from the second operator ( Figure 3a not shown in). As another example, in Figure 3bAmong them, the shared IAB node 324 may include an IAB-DUa for the F1 interface with the donor l-CU 311 from the first operator ( Figure 3b not shown in the figure), an IAB-DUb for the F1 interface with the donor 2-CU 321 from the second operator ( Figure 3b not shown in the figure), and an IAB-DUc for the F1 interface with the donor 3-CU 331 from the third operator ( Figure 3b not shown in the figure).

[0069] Similarly, for the shared IAB node 333 as shown in Figure 3a the figure, 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 for the F1 interface with the donor 1-CU 311 from the first operator ( Figure 3a not shown in the figure), and an IAB-DUb for the F1 interface with the donor 3-CU 331 from the third operator ( Figure 3a not shown in the figure).

[0070] It should be understood that Figure 3a and Figure 3b the deployment examples are for illustrative purposes only and do not imply any limitations. The example embodiments of the present disclosure can be implemented in an IAB environment with any suitable deployment. As another deployment example, the entire tree or subtree of IAB nodes can be shared. For example, the second operator can share the IAB node 324, the IAB node 325, the IAB node 312, and the IAB node 313 with the first operator and the third operator.

[0071] In a partial shared IAB environment, the IAB nodes are shared among different operators, without sharing the donor CU and other intermediate nodes (e.g., donor DU, intermediate IAB nodes). To manage the radio channels towards the shared IAB node 324, e.g., the BH RLC channel, the donor 1-CU 311 from the participating operator should identify the co-location of the IAB-MT and the IAB-DU of the shared IAB node. However, the donor 1-CU 311 from the participating operator has no available solution to know the co-location of the IAB-MT and the IAB-DU of the shared IAB node 324. This is because the BAP address of the shared IAB node 324 (e.g., BAP address #001) is assigned by the donor 2-CU 321 from the hosting operator, and donor CUs from different operators can assign the same BAP address to different IAB nodes. For example, the donor 1-CU 311 may have assigned the same BAP address (e.g., BAP address #001) to its own IAB node, e.g., IAB node 316. As a result, even if the IAB-DU of the shared IAB node 324 includes the BAP address in the F1 SETUP REQUEST message during the F1 establishment process with the donor 1-CU 311, the donor 1-CU 311 cannot know the co-location of the IAB-MT and the IAB-DU of the shared IAB node 324. The donor 1-CU 311 may incorrectly determine that the IAB-DU is co-located with the IAB-MT in the IAB node 316 rather than the IAB-MT in the IAB node 324.

[0072] Due to not knowing the IAB-MT co-located with the IAB-DU of the shared IAB node, the donor 1-CU cannot request to establish or modify the BH RLC channel towards the shared IAB node. In addition, 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 to send the request, e.g., the request to establish the BH RLC channel towards the shared IAB node.

[0073] Similar problems may also exist in a non-IAB shared environment. Figure 3cAnother example IAB environment 306 is shown in which some example embodiments of the present disclosure may be implemented. Specifically, the IAB environment 306 includes a donor CU of a first IAB donor node (also referred to as "donor 1-CU 361") and a donor CU of a second IAB donor node (also referred to as "donor 2-CU 371"). The IAB environment 306 further includes a donor DU of the first IAB donor node (also referred to as "donor 1-DU 368") and a donor DU of the second IAB donor node (also referred to as "donor 2-DU 372"). The IAB environment 306 further includes IAB nodes 373, 374, 375, 366. The IAB nodes 373, 374, 375, 366, donor 2-CU 371, 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 the donor 1-CU 361 and the donor 2-DU 372. The IAB node 374 is connected to the IAB node 373. The RRC establishment procedure initiated by the IAB-MT of the IAB node 374 terminates at the donor 2-CU 371, and the donor 2-CU 371 provides access to the core network ( Figure 3cThe control plane connection (not shown in the figure) to the core network of the IAB-MT in the donor 2-CU 371 is terminated at the IAB node 374. For example, the donor 2-CU 371 is the termination point of the control plane connection of the IAB-MT in the IAB node 374 to the core network. During the RRC establishment process, the donor 2-CU 371 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, for example, for load balancing reasons when the donor 2-CU 371 is overloaded and cannot accept new F1 establishments from the IAB-DU in the IAB node 374. To manage the radio channels towards the IAB node 374, such as the BH RLC channel, the donor 1-CU 361 should identify the co-location of the IAB-MT and the IAB-DU of the IAB node 374. The donor 1-CU 361 does not yet have an available solution to know the co-location of the IAB-MT and the IAB-DU of the IAB node 374. This is because the BAP address of the IAB node 374 (e.g., BAP address #002) is assigned by the donor 2-CU 371, and the donor 1-CU 361 can assign the same BAP address to different IAB nodes. For example, the donor 1-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 the donor 1-CU 361 receives an F1 SETUP REQUEST message including the BAP address (e.g., #002) from the IAB-DU in the IAB node 374, the donor 1-CU 361 cannot know the co-location of the IAB-MT and the IAB-DU of the IAB node 374. The donor 1-CU 361 may incorrectly determine that the IAB-DU is co-located with the IAB-MT in the IAB node 366 rather than the IAB-MT in the IAB node 374.

[0074] 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 among different donor CUs of the same operator. Some example embodiments solve some of the above problems, and some example embodiments further solve one or more other potential problems.

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

[0076] The first donor CU determines an association between the shared IAB node and the second donor CU based on the obtained identification information. For example, the first donor CU may identify that the second donor DU controls the shared IAB node based on the obtained identification information. Based on the determined association, the first donor CU may send a request for configuring a radio channel towards the shared IAB node to the second donor CU when needed. For example, the first donor CU may send a request for establishing or modifying a BHRCL channel towards the shared IAB node to the second donor CU.

[0077] In an example embodiment, the shared IAB node and the donor that controls the shared IAB node may be identified by a donor from a participating operator. IAB node sharing is enabled without sharing donors and intermediate IAB nodes. In this way, flexibility of IAB deployment can be achieved and capital expenditure of the participating operator can be reduced.

[0078] Example process

[0079] Some example embodiments are described in detail below. Figure 4a A flowchart illustrating an example process 400 for sharing an IAB node in accordance with some example embodiments of the present disclosure is shown. For purposes of discussion, process 400 will be described with reference to Figure 3a and Figure 3b Process 400 involves at least a donor 1-CU 311 from a first operator, a donor 2-CU 321 from a second operator, and an IAB node 324 shared between the first operator and the second operator. As Figure 4aAs shown, 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-DUa 403 for the F1 interface with the donor l-CU 311 and an IAB-DUb 402 for the F1 interface with the donor 2-CU 321. It should be understood that although the IAB-DUa 403 and the IAB-DUb 402 are shown separately, this is only for illustrative purposes and does not represent any limitation on the scope of protection. The IAB-DUa 403 and the IAB-DUb 402 may be implemented by the same device or apparatus.

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

[0081] In some example embodiments, the second identifier is the BAP address of the IAB node 324 assigned by the donor 2-CU 321. For example, during the UE initial access procedure of the IAB-MT 401, the IAB-MT 401 may initiate the establishment of an RRC connection with the donor 2-CU 321. The donor 2-CU 321 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 the establishment of a connection with the core network ( Figure 4a not shown in the figure). The donor 2-CU 321 terminates the control plane connection of the IAB-MT 401 to the core network.

[0082] 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 a unique identifier. The first identifier may be any identity that can uniquely identify the donor 2-CU 321 in a multi-operator deployment (e.g., Figure 3a and Figure 3b the example deployment shown). As an example, the first identifier may be the global gNB ID of the donor 2-CU 321, which includes the PLMN ID of the operator (i.e., the second operator in this example) that deploys and controls the donor 2-CU 321, and the gNB ID of the donor 2-CU 321.

[0083] In some example embodiments, the IAB node 324 may receive a first identifier from the donor 2-CU 321. As an example, the first identifier may be included in an F1 Application Protocol (F1AP) message provided from the donor 2-CU 321 to the IAB-DUb 402, for example, during the F1 setup procedure between the IAB-DUb 402 and the donor 2-CU 321. As another example, the first identifier may be included in an RRC message provided from the donor 2-CU 321 to the collocated IAB-MT 401 during an RRC procedure, for example, during the RRC connection setup procedure or during the RRC reconfiguration procedure or at 405.

[0084] 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, an OAM entity of a second operator may provide configuration information including the first identifier to the IAB-DUb 402 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.

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

[0086] The IAB node 324 sends 420 identification information related to the IAB node 324 and the donor 2-CU 321 to the donor 1-CU 311. For example, the IAB-DUa 403 provides the first identifier of the donor 2-CU 321 and the second identifier of the IAB node 324 to the donor 1-CU 311.

[0087] In some example embodiments, the first identifier and the second identifier may be sent during the process for establishing the F1 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 the F1 SETUP REQUEST message from the IAB-DUa 403 to the donor l-CU 311.

[0088] Alternatively or additionally, in some example embodiments, the first identifier and the second identifier may be sent during the process for updating the configuration of the IAB-DU of the IAB node 324. For example, the IAB-DUa 403 may include the first identifier and the second identifier in the message towards the donor l-CU 311 during the F1 gNB-DU configuration update process.

[0089] Alternatively or additionally, in some example embodiments, the first identifier and the second identifier may be sent during the process for updating the configuration of the donor l-CU 311. For example, the IAB-DUa 403 may include the first identifier and the second identifier in the message towards the donor l-CU 311 during the F1 gNB-CU configuration update process.

[0090] 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-DUa 403 and determine that the donor 2-CU 321 manages the IAB node 324. For example, the donor l-CU 311 may identify that the IAB-DUa 403 is collocated with the IAB-MT from a second operator, and the collocated IAB-MT 401 is managed by the donor 2-CU 321, and the donor 2-CU 321 provides a control plane connection to the core network for the collocated IAB-MT 401.

[0091] Based on the determined association, the donor l-CU 311 may send 430 a request for configuring the radio channel towards the IAB node 324 to the donor 2-CU 321 when needed. The request includes the second identifier of the IAB node 324 for identifying the IAB-MT 401. For example, the request may include the BAP address of the IAB node 324 for identifying the IAB-MT 401.

[0092] As an example, when establishing or modifying the BH RLC channel towards the IAB-MT 401, the donor 1-CU 311 may send an Xn request message to the donor 2-CU 321 to establish or modify the BH RLC channel towards the IAB-MT 401. The Xn request includes the BAP address for identifying the IAB-MT 401.

[0093] The donor 2-CU 321 initiates 435 a process for configuring the radio channel towards the IAB node 324. For example, the donor 2-CU 321 may initiate an F1AP process or an RRC process for establishing or modifying the BH RLC channel towards the IAB-MT 401. The BH RLC channel is also used to convey traffic, for example, traffic for the F1 control plane (F1-C) or the F1 user plane (F1-U) between the IAB-DUa 403 and the donor 1-CU 311, and / or traffic for the F1-C or the F1-U between the IAB-DUb 402 and the donor 2-CU 321.

[0094] In the example process 400, the unique identifier of the donor CU from the hosting operator is provided to the donor CU from the participating operator by the shared IAB node. In this way, the donor CU from the participating operator can identify the donor CU that controls the shared IAB node. Thus, IAB node sharing is enabled without sharing the donor and the intermediate IAB nodes from the hosting operator.

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

[0096] In process 450, donor 2-CU 371 sends 455 to IAB node 374 an identifier of IAB node 374 (hereinafter also referred to as "second identifier") assigned by donor 2-CU 371. The second identifier can be any suitable identifier assigned by donor 2-CU 371 to identify IAB node 374.

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

[0098] IAB node 374 obtains 460 an identifier that uniquely identifies donor 2-CU 371. Such an identifier is also referred to as "first identifier" or unique identifier. The first identifier can be any identity that can uniquely identify donor 2-CU 371 in an IAB network including multiple donor CUs (e.g., Figure 3c the example deployment shown). As an example, when the IAB network has other IABs from other operators, the first identifier can be the global gNB ID of donor 2-CU 371, or when the IAB network has only IABs from a single operator, the first identifier can be the gNB ID of donor 2-CU 371 without a PLMN ID.

[0099] The first identifier can be obtained in a manner similar to that described in reference Figure 4a For example, IAB node 374 may receive the first identifier from donor 2-CU 371. As an example, the first identifier may be included in an RRC message that is provided from donor 2-CU 371 to 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, IAB node 374 may receive the first identifier from an OAM entity (not shown).

[0100] In some example embodiments, internal communication 465 can be performed within the IAB node 374 to convey identification information related to the IAB node 374 and the donor 2-CU 371. In the case where a first identifier is provided to the IAB node 374 via an RRC procedure, the IAB-MT 451 can share the first identifier and the BAP address assigned to the IAB-MT 451 with the co-located IAB-DU 453.

[0101] The IAB node 374 sends 470 identification information related to the IAB node 374 and the donor 2-CU 371 to the donor l-CU361 in a manner similar or identical to the manner described in reference Figure 4a and operation 420.

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

[0103] Based on the determined association, the donor l-CU 361 can send 480 a request for configuring a radio channel towards the IAB node 374 to the donor 2-CU 371 when needed. The donor 2-CU371 initiates 485 a procedure for configuring a radio channel towards the IAB node 374. The operations performed at 480 and 485 are similar or identical to the operations described in reference Figure 4a of 430 and 435.

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

[0105] Now refer to Figure 5 . Figure 5 FIG. shows a flowchart of an example procedure 500 for sharing an IAB node according to some example embodiments of the present disclosure. For purposes of discussion, procedure 500 will be described with reference to Figure 3a and Figure 3b . Procedure 500 involves at least a donor 1-CU 311 from a first operator, a donor 2-CU 321 from a second operator, and an IAB node 324 shared between the first operator and the second operator. It should be understood that the actions with the same reference numerals as in Figure 4a are the same as the actions described with reference to Figure 4a and will not be repeated here.

[0106] In procedure 500, the donor 2-CU 321 sends 405 a second identifier of the IAB node 324 assigned by the donor 2-CU 321 to the IAB node 324. For example, the donor 2-CU 321 may send an RRC reconfiguration message including a BAP address to the IAB-MT 401.

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

[0108] The IAB node 324 sends 520 to the donor l-CU 311 the identification information related to the IAB node 324. For example, the IAB-DUa 403 provides the second identifier (e.g., BAP address) of the IAB node 324 to the donor l-CU 311. At 520, the IAB-DUa 403 can also provide the donor 1-CU 311 with information related to its cell and the identification information related to the IAB node 324. In this example embodiment, the donor 1-CU 311 can know the first identifier of the donor 2-CU 321 via the interface (e.g., Xn interface) between the donor 1-CU 311 and the donor 2-CU 321.

[0109] In some example embodiments, the second identifier can be sent during the process of establishing the F1 interface between the IAB node 324 and the donor l-CU 311. For example, the second identifier can be included in the F1 SETUP REQUEST message from the IAB-DUa 403 to the donor 1-CU 311.

[0110] Alternatively or additionally, in some example embodiments, the second identifier can be sent during the process of updating the configuration of the IAB-DU of the IAB node 324. For example, the IAB-DUa 403 can include the second identifier in the message towards the donor 1-CU 311 during the F1 gNB-DU configuration update process.

[0111] Alternatively or additionally, in some example embodiments, the second identifier can be sent during the process of updating the configuration of the donor l-CU 311. For example, the IAB-DUa 403 can include the second identifier in the message towards the donor 1-CU 311 during the F1 gNB-CU configuration update process.

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

[0113] In this case, based on the second identifier received from the IAB-DUa 403 at 520, e.g., the BAP address (e.g., #3), the donor l-CU 311 may incorrectly determine that the IAB-DUa 403 is collocated with the IAB-MT of the IAB node 316. Thus, in some example embodiments, an indication may be sent together with the second identifier of the IAB node 324 to avoid the incorrect determination of the collocation of the IAB-DUb 403 by the donor 1-CU311. For example, the indication may be a flag notifying the donor l-CU 311 not to determine the collocated IAB-MT for the IAB-DU based on the identification information sent at 520 (or not to bind the IAB-DU to the collocated IAB-MT). Instead, at a later time, e.g., when receiving other identity information from the donor 2-CU 321 at 525, the donor 1-CU 311 will determine the collocated IAB-MT (or bind the IAB-DU to the collocated IAB-MT). In the case where the second identifier is included in the F1 SETUPREQUEST message, the F1 SETUP REQUEST message may also include the indication. In one example embodiment, the indication may be the BAP address assigned to the IAB node 324 by the donor 2-CU 321, e.g., at 405. In some example embodiments, the donor l-CU 311 may be pre-configured to determine the collocated IAB-MT based on the received second identifier and other information from the donor 2-CU 321, and thus such an indication (e.g., flag) may be avoided.

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

[0115] 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-CU 321, i.e., the BAP address of the IAB-MT 401 assigned to the shared IAB node 324. For example, the cell information includes the BAP address of the IAB node 324 for one or more cells provided by the collocated IAB-DUa 403 of the shared IAB node 324.

[0116] In the case of sharing by the IAB node 324 among multiple operators, multiple donor CUs from multiple operators can report the same cell of the IAB node 324 as their served cell to the donor l-CU 311. Only the donor CU from the hosting operator (i.e., the donor 2-CU 321) 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 Figure 3b shown. In this case, both the donor 2-CU 321 and the donor 3-CU 331 report the cell of the IAB node 324 as the served cell to the donor l-CU 331. The donor 2-CU 321 provides the BAP address of the IAB node 324 and the cell ID, while the donor 3-CU 331 provides the cell ID without the BAP address of the IAB node 324.

[0117] In some example embodiments, the cell information can be sent during the process for establishing the Xn interface between the donor 2-CU 321 and the donor l-CU 311. For example, the donor 2-CU 321 can include the cell information in the message towards the donor 1-CU 311 during the Xn establishment process.

[0118] Alternatively or additionally, in some example embodiments, the cell information can be sent during the process for updating the configuration required for the donor 2-CU 321 and the donor 1-CU 311 to interoperate via the Xn interface. For example, the donor 2-CU 321 can include the cell information in the message to the donor l-CU 311 during the Xn NG-RAN node configuration update process.

[0119] In the above example embodiments, the donor l-CU 311 can reuse the gNB ID in the Xn message to identify the donor 2-CU 321. In addition, the trigger for sending the cell information can be similar to normal gNB-DU sharing.

[0120] In some example embodiments, the transmission of the cell information at 525 can be performed before the transmission of the identification information related to the IAB node 324 at 520. In this way, the mis-determination of the co-location of the IAB-DUb 403 by the donor 1-CU 311 as described above can be avoided.

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

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

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

[0124] In the example process 400, the identifier of the shared IAB node and the identifiers of one or more cells of the shared IAB node are provided by the donor CU from the hosting operator to the donor CU from the participating operator. In this way, the donor CU from the participating operator can identify the donor CU that controls the shared IAB node. Therefore, IAB node sharing is supported without sharing the donor and intermediate IAB nodes.

[0125] It should be understood that although the IAB-DUa 403 and the IAB-DUb 402 are shown in FIGS. 4 and Figure 5Although shown separately in the figure, this is for illustrative purposes only and does not represent any limitation to the scope of protection. In some example embodiments, the actions described with respect to IAB-DU a403 and IAB-DU b402 can be implemented by the same device or apparatus.

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

[0127] Example protocol stack

[0128] Now refer to Figure 6a and Figure 6b . Figure 6a FIG. shows an example protocol stack 610 for supporting the F1-U plane according to some example embodiments of the present disclosure. Figure 6b FIG. shows an example protocol stack 650 for supporting the F1-C plane according to some example embodiments of the present disclosure. Figure 6a and Figure 6b are described with respect to Figure 3a and Figure 3b .

[0129] Generally, the IAB network includes 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 node 312 from the first operator, and an IAB-DU a sharing the IAB node 324. The network 602 includes a donor 2-DU 322, an IAB node 323, an IAB-MT sharing the IAB node 324 of the IAB-DUb, and an IAB-DUb sharing the IAB node 324.

[0130] As Figure 6a and Figure 6b shown, a BH RLC channel can be established between the IAB MT of the IAB node 312 and the IAB-DU a sharing the 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 from bottom to top include a physical (PHY) layer, a media access control (MAC) layer, a radio link control (RLC) layer, and a BAP layer.

[0131] The F1 plane services include the services of the F1-U plane (also referred to as "F1-U services") and the services of the F1-C plane (also referred to as "F1-C services"). The F1-U services and F1-C services are carried over the BAP layer. Specifically, the protocol layers of the F1-U services from bottom to top include the IP layer, the User Datagram Protocol (UDP) layer, and the GPRS Tunneling Protocol User (GTP-U) layer. The protocol layers of the F1-C services from bottom to top include the IP layer, the Stream Control Transmission Protocol (SCTP) layer, and the F1AP layer.

[0132] As Figure 6a and Figure 6b shown, the F1-U services and F1-C services between the donor 1-CU 311 from the first operator (which is a participating operator) and its IAB node (e.g., IAB node 312) in the shared backhaul network are IP routed via the donor 2-DU 322 from the second operator (which is a hosting operator) and are carried by 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 can fully configure and manage the sub-IAB nodes under the shared IAB node 324 without sharing the sub-IAB nodes and without involving the second operator. The shared IAB node 324 broadcasts the PLMN IDs of the second operator and the first operator. The sub-IAB nodes of the first operator broadcast the PLMN ID of the first operator. For the terminal devices subscribed to the first operator, using the shared backhaul from the second operator is transparent.

[0133] Therefore, in Figure 3a the example environment, the IAB nodes 312 and 313 from the first operator are configured with the BAP addresses from the first operator. To route the BAP packets of the IAB nodes 312 and 313 through the IAB network of the second operator to the donor 1-CU 311 of the first operator, the shared IAB node 324 can be configured to perform BAP header conversion. For example, this BAP address conversion can be similar to the address conversion used in the inter-donor routing in the inter-donor topology redundancy.

[0134] Example methods and apparatus

[0135] Figure 7 shows a flowchart of an example method 700 for configuring an IAB node according to some example embodiments of the present disclosure. The method 700 can be implemented at a first device. For the purpose of discussion, method 700 will be described with reference to Figure 3a , Figure 3b and Figure 3c .

[0136] At block 710, a first device of a first operator obtains identification information that relates to at least one of a second device of a second operator and a third device of 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, the first device may include a donor l-CU 311, the second device may include an IAB node 324, and the third device may include a donor 2-CU 321.

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

[0138] In some example embodiments, the first identifier and the second identifier may be received during a procedure 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 procedure for updating the configuration of the distributed unit of the second device. Alternatively or additionally, the first identifier and the second identifier may be received during a procedure for updating the configuration of the first device.

[0139] In some example embodiments, the first device may receive the 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 from the third device. In some example embodiments, the second identifier may include the BAP address of the IAB node 324. The third identifier may include the cell ID of the cell.

[0140] In some example embodiments, the second identifier and the third identifier may be received during a procedure 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 procedure for updating the configuration required for the first device and the third device to interoperate via the Xn interface.

[0141] At block 720, the first device determines the association between the second device and the third device based on the identification information. At block 730, the first device sends a request to the third device based on the determined association, the request being for configuring a radio channel towards the second device.

[0142] 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 to more than one donor CU from the same operator. For example, the first device includes a donor CU that manages an interface (e.g., F1 interface) with the second device. The third device includes another donor CU that provides a control plane connection to the core network for the second device. For example, the second device may include an IAB node 374, the first device may include a donor 1-CU 361, and the third device may include a donor 2-CU 371.

[0143] Figure 8 FIG. 800 is a flow chart of an example method for configuring an IAB node in accordance with some example embodiments of the present disclosure. Method 800 may be implemented at a second device. For purposes of discussion, method 800 will be described with reference to Figure 3a 、 Figure 3b and Figure 3c 。

[0144] 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 the second operator and provides a control plane connection to the core network for the second device. For example, the first identifier may include the 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, the first device may include a donor l-CU311, the second device may include an IAB node 324, and the third device may include a donor 2-CU 321.

[0145] In some example embodiments, the second device may receive an F1 AP message including the first identifier from the third device. Alternatively or additionally, the second device may receive an RRC message including the first identifier from the third device. Alternatively or additionally, the second device may receive configuration information including the first identifier from an OAM entity.

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

[0147] In some example embodiments, the first identifier and the second identifier may be sent 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 process for updating a configuration of a DU (e.g., an IAB-DU of IAB node 324) of the second device. Alternatively or additionally, the first identifier and the second identifier may be sent during a process for updating a configuration of the first device.

[0148] 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 to more than one donor CU from the same operator. For example, the first device includes a donor CU that manages an interface (e.g., an F1 interface) with the second device. The third device includes another donor CU that provides a control plane connection to the core network for the second device. For example, the second device may include an IAB node 374, the first device may include a donor 1-CU 361, and the third device may include a donor 2-CU 371.

[0149] Figure 9 FIG. 9 is a flowchart of an example method 900 for sharing an IAB node according to some example embodiments of the present disclosure. The method 900 may be implemented at a third device. For the purpose of discussion, reference will be made to FIG. Figure 3a , Figure 3b and Figure 3c To describe method 900.

[0150] At block 910, a third device from a second operator provides identification information to a first device from a 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 is shared for the first operator. For example, the first device may include a donor 1-CU 311, the second device may include an IAB node 324, and the third device may include a donor 2-CU 321.

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

[0152] 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.

[0153] In some example embodiments, the third device may send to the first device a second identifier of the second device allocated 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 the BAP address of the IAB node 324. The third identifier may include the cell ID of the cell.

[0154] In some example embodiments, the second identifier and the third identifier may be sent 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 via the Xn interface.

[0155] At block 920, the third device receives from the first device a request for configuring a radio channel towards the second device. The third device may initiate a process for configuring a radio channel towards the IAB node 324.

[0156] 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 to more than one donor CU from the same operator. For example, the first device includes a donor CU that manages an interface (e.g., F1 interface) with the second device. The third device includes another donor CU that provides a control plane connection to the core network for the second device. For example, the second device may include the IAB node 374, the first device may include the donor 1-CU 361, and the third device may include the donor 2-CU 371.

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

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

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

[0160] In some example embodiments, the first operator and the second operator may be different operators, and the second device 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 device is an IAB node having connections to more than one donor CU from the same operator.

[0161] In some example embodiments, the component for obtaining identification information includes: a component for 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.

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

[0163] In some example embodiments, the component for obtaining identification information includes: a component for 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.

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

[0165] In some example embodiments, the second identifier of the second device includes a backhaul adaptation protocol address assigned by the third device.

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

[0167] In some example embodiments, a second apparatus from a second operator includes: components for obtaining a first identifier that uniquely identifies 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 components for sending the first identifier and a second identifier of the second apparatus assigned by the third apparatus to a first apparatus from a first operator. The first apparatus includes a first integrated access and backhaul donor central unit, the second apparatus includes an integrated access and backhaul node, and the third apparatus includes a second integrated access and backhaul donor central unit.

[0168] 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 to more than one donor CU from the same operator.

[0169] In some example embodiments, the components for obtaining the first identifier include at least one of the following: components for receiving an F1 application protocol message including the first identifier from the third apparatus, components for receiving a radio resource control message including the first identifier from the third apparatus, or components for receiving configuration information including the first identifier from an operation management and maintenance entity.

[0170] In some example embodiments, the first identifier and the second identifier are sent during at least one of the following: a process for establishing an Fl interface between the first apparatus and the second apparatus, a process for updating the configuration of the distributed unit of the second apparatus, or a process for updating the configuration of the first apparatus.

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

[0172] In some example embodiments, a third device from a second operator includes: components for providing identification information regarding 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 components for receiving a request from the first device, the request being for configuring a radio channel towards the second device. The first device includes a first integrated access and backhaul donor central unit, the second device includes an integrated access and backhaul node, and the third device includes a second integrated access and backhaul donor central unit.

[0173] In some example embodiments, the first operator and the second operator may be different operators, and the second device 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 device is an IAB node having connections to more than one donor CU from the same operator.

[0174] In some example embodiments, the components for providing identification information to the first device include: components for sending, via the second device, a first identifier that uniquely identifies the third device to the first device.

[0175] In some example embodiments, the components for sending the first identifier include at least one of the following: components for sending an F1 application protocol message including the first identifier to the second device, or components for sending a radio resource control message including the first identifier to the second device.

[0176] In some example embodiments, the components for providing identification information to the first device include: components for sending 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.

[0177] In some example embodiments, the second identifier and the third identifier are sent during at least one of the following: a process 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 via the Xn interface.

[0178] In some example embodiments, the second identifier of the second device includes a backhaul adaptation protocol address assigned by the third device.

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

[0180] Communication component 1040 is used for two-way communication. Communication component 1040 has at least one antenna to facilitate communication. The communication interface can represent any interface necessary for communicating with other network elements.

[0181] Processor 1010 can be of any type suitable for the local technical network and, by way of non-limiting example, can include one or more of the following: general-purpose computer, special-purpose computer, microprocessor, digital signal processor (DSP), and processor based on a multi-core processor architecture. Device 1000 can have multiple processors, such as an application-specific integrated circuit chip that is subordinate to a clock synchronized with the main processor in time.

[0182] Memory 1020 can include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 1024, electrically programmable read-only memory (EPROM), flash memory, hard disk, compact disc (CD), digital versatile disc (DVD), and other magnetic storage and / or optical storage. Examples of volatile memories include, but are not limited to, random access memory (RAM) 1022 and other volatile memories that do not persist during a power outage.

[0183] Computer program 1030 includes computer-executable instructions executed by the associated processor 1010. Program 1030 can be stored in ROM 1020. Processor 1010 can perform any suitable actions and processes by loading program 1030 into RAM 1020.

[0184] Embodiments of the present disclosure can be implemented by means of program 1030 such that device 1000 can execute any process of the present disclosure as discussed with reference to FIGS. 4 to Figure 5 and Figures 7 to 9 Embodiments of the present disclosure can also be implemented by hardware or a combination of software and hardware.

[0185] In some example embodiments, program 1030 may be tangibly embodied in a computer-readable medium, which may be included in device 1000 (such as in memory 1020) or in other storage devices accessible to device 1000. Device 1000 may 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 ROM, EPROM, flash memory, hard disk, CD, DVD, etc. Figure 11 An example of a computer-readable medium 1000 in the form of a CD or DVD is shown. Program 1030 is stored on the computer-readable medium.

[0186] It should be understood that future networks may utilize network function virtualization (NFV), which is a network architecture concept that proposes virtualizing network node functions into "building blocks" or entities that can be operationally connected or linked together to provide services. Virtualized network functions (VNFs) may include one or more virtual machines that use standard or common types of servers rather than custom hardware to run computer program code. Cloud computing or data storage may also be utilized. In radio communications, this may mean that node operations should be performed at least in part in a central / centralized unit CU (such as a server, host, or node) that is operationally coupled to a distributed unit DU (such as a radio head / node). Node operations may also be distributed among multiple servers, nodes, or hosts. It should also be understood that the work distribution between core network operations and base station operations may vary according to the implementation.

[0187] In one embodiment, the server may generate a virtual network through which the server communicates with the distributed unit. Generally speaking, a virtual network 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 a flexible distribution of operations between the server and the radio head / node. In practice, any digital signal processing tasks may be performed in the CU or DU, and the boundary at which the responsibilities transfer between the CU and the DU may be selected according to the implementation.

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

[0189] In one embodiment, the execution of at least some of the functions of device 1000 can be shared between two physically separate devices (DU and CU) that form an operating entity. Thus, the apparatus can be considered to depict an operating entity that includes one or more physically separate devices for performing at least some of the processes described. In one embodiment, such a CU-DU architecture can provide a flexible distribution of operations between the CU and the DU. In practice, any digital signal processing task can be performed in the CU or the DU, and the boundary at which the responsibilities shift between the CU and the DU can be selected according to the implementation. In one embodiment, device 1000 controls the execution of the process, regardless of the location of the apparatus and regardless of where the process / function is performed.

[0190] Generally, the various embodiments of the present disclosure can be implemented using hardware or a dedicated circuit, software, logic, or any combination thereof. Some aspects can be implemented using hardware, while other aspects can be implemented using firmware or software that can be executed by a controller, a microprocessor, or other computing device. Although the various aspects of the embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other graphical representation, it should be understood that, as a non-limiting example, the blocks, apparatus, systems, techniques, or methods described herein can be implemented using hardware, software, firmware, a dedicated circuit or logic, general hardware or a controller or other computing device, or some combination thereof.

[0191] 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 includes computer-executable instructions, such as the instructions included in the program components, that are executed in a device on a target real or virtual processor to perform the method 700 as described above with reference to Figure 7 described above with reference to Figure 8The described method 800 and as described above with reference to Figure 9 The described method 900. Generally, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc. that perform a particular task or implement a particular abstract data type. In various embodiments, the functions of program modules may be combined or split among program modules as needed. The machine-executable instructions of a program module may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.

[0192] The program code for performing the methods of the present disclosure may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general purpose computer, a special purpose computer, or other programmable data processing apparatus such that the program code, when executed by the processor or controller, causes the functions / operations specified in the flowchart and / or block diagram to be implemented. 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 a remote machine or server.

[0193] In the context of the present disclosure, computer program code or related data may be carried by any suitable carrier such that a device, apparatus, or processor can perform the various processes and operations described above. Examples of carriers include signals, computer-readable media, etc.

[0194] A 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 floppy disk, 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.

[0195] Furthermore, although operations are described in a particular order, this should not be construed as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed to obtain a desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the above discussion, these should not be construed as limitations on the scope of the present disclosure, but rather as descriptions of features that may be specific to particular embodiments. Certain features described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented separately or in any suitable sub-combination in multiple embodiments.

[0196] Although the present 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 above specific features and acts are disclosed as example forms of implementing the claims.

Claims

1. A first device for communication, 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, together with the at least one processor, cause the first device from the first operator: to receive identification information that relates to at least one of a second device from the second operator and shared with the first operator and a third device from the second operator; to determine an association between the second device and the third device based on the identification information; and to send a request to the third device based on the determined association, the request being for configuring a radio channel towards the second device, and wherein the first device includes a first integrated access and backhaul donor central unit, the second device includes an integrated access and backhaul node, and the third device includes a second integrated access and backhaul donor central unit.

2. The first device according to claim 1, wherein the at least one memory and the computer program code are configured to, together with the at least one processor, cause the first device to receive the identification information by: Receiving a first identifier that uniquely identifies the third device and a second identifier of the second device assigned by the third device from the second device.

3. The first device according to claim 2, wherein the first identifier and the second identifier are received during at least one of the following: A process for establishing an F1 interface between the first device and the second device, A process for updating the configuration of the distributed unit of the second device, or A process for updating the configuration of the first device.

4. The first device according to claim 1, wherein the at least one memory and the computer program code are configured to, together with the at least one processor, cause the first device to receive the identification information by: Receiving 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 from the third device.

5. The first device according to claim 4, wherein the second identifier and the third identifier are received during at least one of the following: A process for establishing an Xn interface between the first device and the third device, or A process for updating the configuration required for the first device and the third device to interoperate through the Xn interface.

6. The first device according to any one of claims 2 to 4, wherein the second identifier of the second device includes a backhaul adaptation protocol address assigned by the third device.

7. A second device for communication, 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, together with the at least one processor, cause the second device from the second operator: to obtain a first identifier that uniquely identifies a third device from the second operator and provides a control plane connection to the core network for the second device; and to send 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 includes a first integrated access and backhaul donor central unit, the second device includes an integrated access and backhaul node, and the third device includes a second integrated access and backhaul donor central unit.

8. The second device according to claim 7, wherein the at least one memory and the computer program code are configured to, together with the at least one processor, cause the second device to obtain the first identifier by at least one of the following: 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 operation management and maintenance entity.

9. The second device according to claim 7, wherein the first identifier and the second identifier are sent during at least one of the following: A process for establishing an F1 interface between the first device and the second device, A process for updating the configuration of the distributed unit of the second device, or A process for updating the configuration of the first device.

10. A third device for communication, 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, together with the at least one processor, cause the third device from the second operator: to send identification information relating to at least one of a second device and the third device to a first device from the first operator, the second device being from the second operator and shared with the first operator; and to receive a request from the first device, the request being for configuring a radio channel towards the second device, and wherein the first device includes a first integrated access and backhaul donor central unit, the second device includes an integrated access and backhaul node, and the third device includes a second integrated access and backhaul donor central unit.

11. The third device according to claim 10, wherein the at least one memory and the computer program code are configured to, together with the at least one processor, cause the third device to send the identification information to the first device by the following operation: Sending a first identifier that uniquely identifies the third device to the first device via the second device.

12. The third device according to claim 11, wherein the at least one memory and the computer program code are configured to, together with the at least one processor, cause the third device to send the first identifier by at least one of the following: Send an F1 application protocol message including the first identifier to the second device, or Send a radio resource control message including the first identifier to the second device.

13. The third device according to claim 10, wherein the at least one memory and the computer program code are configured to, together with the at least one processor, cause the third device to send the identification information to the first device by: Send 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 to the first device.

14. The third device according to claim 13, wherein the second identifier and the third identifier are sent during at least one of the following: A process 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 through the Xn interface.

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

16. A communication method, comprising: Receiving, at a first device from the first operator, identification information that relates to at least one of a second device from the second operator and shared with the first operator and a third device from the second operator; Determining an association between the second device and the third device based on the identification information; and Sending a request to the third device based on the determined association, the request being for configuring a radio channel towards the second device, and The first device includes a first integrated access and backhaul donor central unit, the second device includes an integrated access and backhaul node, and the third device includes a second integrated access and backhaul donor central unit.

17. A communication method, comprising: Obtain a first identifier that uniquely identifies a third device at a second device from a second operator, the third device being from the second operator and providing a control plane connection to a core network for the second device; And Send 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 The first device includes a first integrated access and backhaul donor central unit, the second device includes an integrated access and backhaul node, and the third device includes a second integrated access and backhaul donor central unit.

18. A communication method, comprising: Send, at a third device from a second operator, identification information related to at least one of the 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 Receive a request from the first device, the request for configuring a radio channel towards the second device, and The first device includes a first integrated access and backhaul donor central unit, the second device includes an integrated access and backhaul node, and the third device includes a second integrated access and backhaul donor central unit.

19. A first device from a first operator, the first device comprising: A component for receiving identification information related 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; A component for determining an association between the second device and the third device based on the identification information; And A component for sending a request to the third device based on the determined association, the request for configuring a radio channel towards the second device, and The first device includes a first integrated access and backhaul donor central unit, the second device includes an integrated access and backhaul node, and the third device includes a second integrated access and backhaul donor central unit.

20. A second device from a second operator, the second device comprising: A component for receiving 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 A component for 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 The first device includes a first integrated access and backhaul donor central unit, the second device includes an integrated access and backhaul node, and the third device includes a second integrated access and backhaul donor central unit.

21. A third device from a second operator, the third device comprising: A component for sending identification information related to at least one of a second device and a 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 A component for receiving a request from the first device, the request for configuring a radio channel towards the second device, and Wherein the first device includes a first integrated access and backhaul donor central unit, the second device includes an integrated access and backhaul node, and the third device includes a second integrated access and backhaul donor central unit.

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

Images