Integrated access backhaul (IAB) configuration at mobility

Abstract

A method, system and apparatus are disclosed. According to some embodiments, a network node (16) is provided. The network node (16) is configured to: transmit information associated with at least one of an integrated access and backhaul, IAB, type or location information associated with the network node (16); receive a first operations, administration and Maintenance, OAM, system address of a plurality of OAM system addresses, the first OAM system address being associated with: the information and a first OAM system that has a capability to configure the network node (16), and participate in an OAM session with the first OAM system using the OAM system address.

Description

[0001] INTEGRATED ACCESS BACKHAUL (IAB) CONFIGURATION AT MOBILITY

[0002] FIELD

[0003] The present disclosure relates to wireless communications, and in particular, to integrated access backhaul (IAB) configuration.

[0004] BACKGROUND

[0005] The Third Generation Partnership Project (3 GPP) has developed and is developing standards for Fourth Generation (4G) (also referred to as Long Term Evolution (LTE)) and Fifth Generation (5G) (also referred to as New Radio (NR)) wireless communication systems. Such systems provide, among other features, broadband communication between network nodes, such as base stations, and mobile user equipments (UE), as well as communication between network nodes and between UEs. The 3GPP is also developing standards for Sixth Generation (6G) wireless communication networks.

[0006] In 5G architecture, there is a use case where the gNB (either distributed unit (DU) only or both centralized unit (CU) and DU) may be moved into a new location.

[0007] FIG. 1 is a diagram of an example of the overall architecture of IAB (Integrated Access and Backhaul).

[0008] The NG-RAN supports IAB by the lAB-node wirelessly connecting to the gNB (e.g., network node) capable of serving the lAB-nodes, named lAB-donor.

[0009] The lAB-donor consists of an lAB-donor-CU and one or more lAB-donor-DU(s). In case of separation of gNB-CU-control plane (CP) and gNB-CU-user plane (UP), the lAB-donor may consist of an lAB-donor-CU-CP, multiple lAB-donor-CU-UPs and multiple lAB-donor-DUs.

[0010] The lAB-node connects to an upstream lAB-node or an lAB-donor-DU via a subset of the UE functionalities of the NR Uu interface (referred to as the lAB-mobile termination (MT) function of the lAB-node). The lAB-node provides a wireless backhaul to the downstream lAB-nodes and UEs via the network functionalities of the NR Uu interface (named IAB-DU function of lAB-node).

[0011] The Fl-C traffic between a first lAB-node and lAB-donor-CU is backhauled via the lAB-donor-DU and the optional intermediate hop lAB-node(s).

[0012] The Fl-U traffic between a second lAB-node and lAB-donor-CU is backhauled via the lAB-donor-DU and the optional intermediate hop lAB-node(s). However, 3GPP does not specify how to configure an IAB node based on its specific location.

[0013] SUMMARY

[0014] Some embodiments advantageously provide methods, systems, and apparatuses for IAB configuration such as, for example, at mobility.

[0015] In some embodiments, the IAB node may be configured by OAM based on its precise location. In particular, various embodiments define a mechanism to support location-based configuration for the IAB node. Further, various embodiments may support location-based configuration for the IAB node in current 3GPP release, and WAB in further 3GPP releases.

[0016] The embodiments described herein provide one or more of the following advantages:

[0017] • Possibility to support location-based configuration for the IAB node in existing 3GPP release(s), and WAB (e.g., wireless access backhaul) in future 3GPP releases.

[0018] • Minor impacts on existing IAB implementations.

[0019] • No impacts on existing 5G core (5GC) and NR-RAN implementations.

[0020] According to one aspect of the present disclosure, a method implemented by a network node is provided. Information associated with at least one of an integrated access and backhaul, IAB, type or location information associated with the network node is transmitted. A first operations, administration and Maintenance, OAM, system address of a plurality of OAM system addresses is received where he first OAM system address is associated with: the information and a first OAM system that has a capability to configure the network node. Participate in an OAM session with the first OAM system using the OAM system address.

[0021] According to one or more embodiments of this aspect, the information is transmitted to a security gateway, where the first OAM system address is received from the security gateway.

[0022] According to one or more embodiments of this aspect, the information comprises one of: at least one internet engineering task force, IETF, attribute; or at least one third generation partnership project, 3 GPP, attribute.

[0023] According to one or more embodiments of this aspect, the at least one IETF attribute or the at least one 3GPP attribute comprises one or more of: a parent network node identifier where a network node-mobile termination, -MT, of the network node is attached; a parent network node donor-distributed unit, -DU, identity associated with the network node-MT; and at least one unique identifier in use by the network node, the at least one unique identifier comprising one or both of a trace area identity and a cell identifier.

[0024] According to one or more embodiments of this aspect, the at least one 3 GPP attribute comprises one or both of: vendor name associated with the network node; and IAB function type associated with the network node.

[0025] According to one or more embodiments of this aspect, a security tunnel is at least in part established with a security gateway, where the transmission of the information to the security gateway is via the security tunnel.

[0026] According to one or more embodiments of this aspect, the network node is an IAB network node, where the location information is transmitted to the first OAM system via the OAM session, and an IAB configuration is received from the first OAM system where the IAB configuration being associated with the location information.

[0027] According to one or more embodiments of this aspect, the IAB configuration comprises at least one IAB -distributed unit, IAB-DU, instantiate configuration.

[0028] According to one or more embodiments of this aspect, the transmission of the information is associated with one of a startup procedure or power up procedure of the network node.

[0029] According to one or more embodiments of this aspect, the network node is an IAB network node and where the transmission of the information is associated with mobility of the IAB network node.

[0030] According to another aspect of the present disclosure, a network node is configured to: transmit information associated with at least one of an integrated access and backhaul, IAB, type or location information associated with the network node and receive a first operations, administration and Maintenance, OAM, system address of a plurality of OAM system addresses, where the first OAM system address is associated with: the information; and a first OAM system that has a capability to configure the network node. The network node is further configured to participate in an OAM session with the first OAM system using the OAM system address.

[0031] According to one or more embodiments of this aspect, the information is transmitted to a security gateway, and the first OAM system address is received from the security gateway. According to one or more embodiments of this aspect, the information comprises one of: at least one internet engineering task force, IETF, attribute, or at least one third generation partnership project, 3 GPP, attribute.

[0032] According to one or more embodiments of this aspect, the at least one IETF attribute or the at least one 3GPP attribute comprises one or more of: a parent network node identifier where a network node-mobile termination, -MT, of the network node is attached; a parent network node donor-distributed unit, -DU, identity associated with the network node-MT; and at least one unique identifier in use by the network node, where the at least one unique identifier comprises one or both of a trace area identity and a cell identifier.

[0033] According to one or more embodiments of this aspect, the at least one 3 GPP attribute comprises one or both of: vendor name associated with the network node; and IAB function type associated with the network node.

[0034] According to one or more embodiments of this aspect, the network node is further configured to at least in part establish a security tunnel with a security gateway, where the transmission of the information to the security gateway is via the security tunnel.

[0035] According to one or more embodiments of this aspect, the network node is an IAB network node, and the IAB network node is further configured to: transmit, to the first GAM system, the location information via the 0AM session; and receive, from the first 0AM system, an IAB configuration, where the IAB configuration is associated with the location information.

[0036] According to one or more embodiments of this aspect, the IAB configuration comprises at least one IAB -distributed unit, IAB-DU, instantiate configuration.

[0037] According to one or more embodiments of this aspect, the transmission of the information is associated with one of a startup procedure or power up procedure of the network node.

[0038] According to one or more embodiments of this aspect, the network node is an IAB network node, where the transmission of the information is associated with mobility of the IAB network node.

[0039] According to another aspect of the present disclosure, a method implemented by a security gateway is provided. Information is received from a network node, where the information is associated with at least one of an integrated access and backhaul, IAB, type or location information associated with the network node. A first operations, administration and Maintenance, 0AM, system of a plurality of 0AM systems is selected based on the information, where the first OAM system has a capability to configure the network node. An OAM system address of the first OAM system is transmitted to the network node.

[0040] According to one or more embodiments of this aspect, the information comprises one of: at least one internet engineering task force, IETF, attribute; or at least one third generation partnership project, 3 GPP, attribute.

[0041] According to one or more embodiments of this aspect, the at least one IETF attribute or the at least one 3GPP attribute comprises one or more of: a parent network node identifier where a network node-mobile termination, -MT, of the network node is attached; a parent network node donor-distributed unit, -DU, identity associated with the network node-MT; and at least one unique identifier in use by the network node where the at least one unique identifier comprises one or both of a trace area identity and a cell identifier.

[0042] According to one or more embodiments of this aspect, the at least one 3 GPP attribute comprises one or both of: vendor name associated with the network node; and IAB function type associated with the network node.

[0043] According to one or more embodiments of this aspect, a security tunnel is at least in part established with the network node, where the information is received from the network node via the security tunnel.

[0044] According to one or more embodiments of this aspect, the network node is an IAB network node.

[0045] According to one or more embodiments of this aspect, the receiving of the information is associated with one of a startup procedure or power up procedure of the network node.

[0046] According to one or more embodiments of this aspect, the network node is an IAB network node, and the receiving of the information is associated with mobility of the IAB network node.

[0047] According to one or more embodiments, a security gateway is configured to receive information from a network node, where the information is associated with at least one of an integrated access and backhaul, IAB, type or location information associated with the network node; select a first operations, administration and Maintenance, OAM, system of a plurality of OAM systems based on the information where the first OAM system has a capability to configure the network node; and transmit, to the network node, an OAM system address of the first OAM system. According to one or more embodiments of this aspect, the information comprises one of: at least one internet engineering task force, IETF, attribute; or at least one third generation partnership project, 3 GPP, attribute.

[0048] According to one or more embodiments of this aspect, the at least one IETF attribute or the at least one 3GPP attribute comprises one or more of: a parent network node identifier where a network node-mobile termination, -MT, of the network node is attached; a parent network node donor-distributed unit, -DU, identity associated with the network node-MT; and at least one unique identifier in use by the network node, where the at least one unique identifier comprises one or both of a trace area identity and a cell identifier.

[0049] According to one or more embodiments of this aspect, the at least one 3 GPP attribute comprises one or both of: vendor name associated with the network node; and IAB function type associated with the network node.

[0050] According to one or more embodiments of this aspect, the security gateway is further configured to at least in part establish a security tunnel with the network node, where the information is received from the network node via the security tunnel.

[0051] According to one or more embodiments of this aspect, the network node is an IAB network node.

[0052] According to one or more embodiments of this aspect, the receiving of the information is associated with one of a startup procedure or power up procedure of the network node.

[0053] According to one or more embodiments of this aspect, the network node is an IAB network node; and the receiving of the information is associated with mobility of the IAB network node.

[0054] BRIEF DESCRIPTION OF THE DRAWINGS

[0055] A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein:

[0056] FIG. 1 is a block diagram of an example IAB architecture;

[0057] FIG. 2 is a diagram of an example mobility procedure;

[0058] FIG. 3 is a schematic diagram of an example network architecture illustrating a communication system according to principles disclosed herein; FIG. 4 is a block diagram of a network node in communication with a user equipment over a wireless connection according to some embodiments of the present disclosure;

[0059] FIG. 5 is a block diagram of a security gateway according to some embodiment of the present disclosure;

[0060] FIG. 6 is a flowchart of an example process in a network node according to some embodiments of the present disclosure;

[0061] FIG. 7 is a flowchart of another example process in a network node according to some embodiments of the present disclosure;

[0062] FIG. 8 is a flowchart of an example process in a security gateway according to some embodiments of the present disclosure;

[0063] FIG. 9 is a flowchart of another example process in a security gateway according to some embodiments of the present disclosure;

[0064] FIG. 10 is a diagram of an ORAN configuration according to some embodiments of the present disclosure;

[0065] FIG. 11 is a diagram of an example overall architecture of IAB according to some embodiments of the present disclosure;

[0066] FIG. 12 is a diagram of an example IAB node that connects to 0AM system at power up according to some embodiments of the present disclosure;

[0067] FIG. 13 is a diagram of an example mobile IAB -DU inter-CU migration procedure according to some embodiments of the present disclosure; and

[0068] FIG. 14 is a diagram of an example mobile IAB node connected to an 0AM system during mobility according to some embodiments of the present disclosure.

[0069] DETAILED DESCRIPTION

[0070] The following is an IAB bootstrapping procedure which is consistent with the PnC (plug and connect) procedure specified in 3GPP technical specification (TS) 28.315 and the IAB integration procedure specified in 3GPP TS 38.401.

[0071] Bootstrapping procedure

[0072] 1. IAB -MT sets up the PDN connection / PDU session

[0073] [IAB integration Phase 1 ]

[0074] 2. IAB -DU instantiation a) DNS query, with IAB node type and IAB node location info, to receive the corresponding 0AM GW address. [PnC] b) OAM session setup, including security verification. [PnC] c) Download all necessary configuration data from OAM gateway (GW) [PnC] d) Additional lAB-donor-CU based configurations, optionally.

[0075] [TAB integration Phase 2-1 & 2-2] e) Fl link setup between IAB-DU and lAB-donor-CU

[0076] [IAB integration Phase 3 ]

[0077] In step 2b, the IAB needs to set up a secured session with a specific OAM system. And in step 2c, a specific configuration is downloaded from the OAM system, but how this is performed is not yet defined in 3GPP standards.

[0078] FIG. 2 is a diagram of an example mobility procedure and is discussed below.

[0079] 1. IAB-MT handover from lAB-donor-DUl to IAB-donor-DU2

[0080] - may occur after step 2

[0081] 2. IAB-DU2 instantiation a) Domain name system (DNS) query, with IAB node type and IAB node location information, to receive the corresponding OAM 2c address. b) OAM session setup, including security verification. c) Download all necessary configuration data from OAM 2c d) Additional IAB-donor-CU2 configurations, optionally.

[0082] [IAB integration Phase 2-1 & 2-2] e) Fl link setup between IAB-DU2 and IAB-donor-CU2

[0083] [IAB integration Phase 3 ]

[0084] • IAB-donor-CU2 reconfigurations over Fl-C, optionally.

[0085] 3. UE handover from IAB -DU 1 to IAB -DU2

[0086] 4. Removing IAB -DUE

[0087] Same as the bootstrapping procedure, in step 2b, the IAB needs to set up a secured session with a specific OAM system. And in step 2c, a specific configuration is downloaded from the OAM system, but it is not defined in 3GPP standards how one or more of these steps can be performed.

[0088] Further, in existing 3 GPP specification, only IAB-DU is defined inside the IAB- node.

[0089] One or more embodiments described herein solves the problem(s) with existing systems but providing a mechanism to support location-based configuration for the IAB node. Before describing in detail exemplary embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to location-based configuration for the IAB node. Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

[0090] One or more or all functions specified for a gNB-DU are equally applicable for an IAB-DU and lAB-donor-DU, unless otherwise stated, and one or more or all functions specified for a gNB-CU are equally applicable for an lAB-donor-CU, unless otherwise stated. All functions specified for the UE context are equally applicable for managing the context of IAB-MT, unless otherwise stated.

[0091] As used herein, relational terms, such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. 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,” “includes” and / or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0092] In embodiments described herein, the joining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. One having ordinary skill in the art will appreciate that multiple components may interoperate and modifications and variations are possible of achieving the electrical and data communication.

[0093] In some embodiments described herein, the term “coupled,” “connected,” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and / or wireless connections. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. 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,” “includes” and / or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0094] The term “network node” used herein can be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), integrated backhaul access (IAB) node (also referred to as IAB network node), Node B, multistandard radio (MSR) radio node such as MSR BS, multi-cell / multicast coordination entity (MCE), relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also comprise test equipment. The term “radio node” used herein may be used to also denote a user equipment (UE) such as a wireless device (WD) or a radio network node.

[0095] In some embodiments, the non-limiting terms wireless device (WD) or a user equipment (UE) are used interchangeably. The UE herein can be any type of user equipment capable of communicating with a network node or another UE over radio signals, such as a wireless device (WD). The UE may also be a radio communication device, target device, device to device (D2D) UE, machine type UE or UE capable of machine to machine communication (M2M), low-cost and / or low-complexity UE, a sensor equipped with UE, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (loT) device, or a Narrowband loT (NB-IOT) device etc.

[0096] Also, in some embodiments the generic term “radio network node” is used. It can be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell / multicast Coordination Entity (MCE), relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).

[0097] Note that although terminology from one particular wireless system, such as, for example, 3GPP LTE and / or New Radio (NR), may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system. Other wireless systems, including without limitation Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM), may also benefit from exploiting the ideas covered within this disclosure.

[0098] Note further, that functions described herein as being performed by a user equipment or a network node may be distributed over a plurality of user equipments and / or network nodes. In other words, it is contemplated that the functions of the network node and user equipment described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.

[0099] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

[0100] Some embodiments are directed to IAB configuration at, for example, mobility.

[0101] Referring again to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in FIG. 3 a schematic diagram of a communication system 10, according to an embodiment, such as a 3GPP-type cellular network that may support standards such as LTE and / or NR (5G), which comprises an access network 12, such as a radio access network, and a core network 14. The access network 12 comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas 18). In one or more embodiments, network node 16 may be an IAB network node. System 10 further comprises a security gateway 19 that may be part of the access network or may be part of the core network 14. Each network node 16a, 16b, 16c is connectable to the core network 14 over a wired or wireless connection 20. A first user equipment (UE) 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a. A second UE 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of UEs 22a, 22b (collectively referred to as user equipments 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding network node 16. Note that although only two UEs 22 and three network nodes 16 are shown for convenience, the communication system may include many more UEs 22 and network nodes 16.

[0102] Also, it is contemplated that a UE 22 can be in simultaneous communication and / or configured to separately communicate with more than one network node 16 and more than one type of network node 16. For example, a UE 22 can have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR. As an example, UE 22 can be in communication with an eNB for LTE / E-UTRAN and a gNB for NR / NG-RAN.

[0103] Further, the core network 14 may comprise one or more 0AM systems 23.

[0104] A network node 16 (eNB or gNB or IAB network node) is configured to include a IAB unit 24 which is configured to perform one or more network node functions described herein such as, for example, with respect to IAB configuration at mobility. Security gateway 19 is configured to include configuration unit 21 which is configured to perform one or more security gateway 19 functions as described herein such as, for example, with respect to IAB configuration mobility.

[0105] Example implementations, in accordance with an embodiment, of the UE 22 and network node 16 discussed in the preceding paragraphs will now be described with reference to FIG. 4.

[0106] The communication system 10 includes a network node 16 provided in a communication system 10 and including hardware 28 enabling it to communicate with the UE 22. The hardware 28 may include a radio interface 30 for setting up and maintaining at least a wireless connection 32 with a UE 22 located in a coverage area 18 served by the network node 16. The radio interface 30 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The radio interface 30 includes an array of antennas 34 to radiate and receive signal(s) carrying electromagnetic waves. In the embodiment shown, the hardware 28 of the network node 16 further includes processing circuitry 36. The processing circuitry 36 may include a processor 38 and a memory 40. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 36 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 38 may be configured to access (e.g., write to and / or read from) the memory 40, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0107] Thus, the network node 16 further has software 42 stored internally in, for example, memory 40, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection. The software 42 may be executable by the processing circuitry 36. The processing circuitry 36 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by network node 16. Processor 38 corresponds to one or more processors 38 for performing network node 16 functions described herein. The memory 40 is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 42 may include instructions that, when executed by the processor 38 and / or processing circuitry 36, causes the processor 38 and / or processing circuitry 36 to perform the processes described herein with respect to network node 16. For example, processing circuitry 36 of the network node 16 may include IAB unit 24 which is configured to perform one or more network node functions as described herein such as, for example, with respect to IAB configuration.

[0108] The communication system 10 further includes the UE 22 already referred to. The UE 22 may have hardware 44 that may include a radio interface 46 configured to set up and maintain a wireless connection 32 with a network node 16 serving a coverage area 18 in which the UE 22 is currently located. The radio interface 46 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The radio interface 46 includes an array of antennas 48 to radiate and receive signal(s) carrying electromagnetic waves. The hardware 44 of the UE 22 further includes processing circuitry 50. The processing circuitry 50 may include a processor 52 and memory 54. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 50 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 52 may be configured to access (e.g., write to and / or read from) memory 54, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0109] Thus, the UE 22 may further comprise software 56, which is stored in, for example, memory 54 at the UE 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the UE 22. The software 56 may be executable by the processing circuitry 50. The software 56 may include a client application 58. The client application 58 may be operable to provide a service to a human or non-human user via the UE 22.

[0110] The processing circuitry 50 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by UE 22. The processor 52 corresponds to one or more processors 52 for performing UE 22 functions described herein. The UE 22 includes memory 54 that is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 56 and / or the client application 58 may include instructions that, when executed by the processor 52 and / or processing circuitry 50, causes the processor 52 and / or processing circuitry 50 to perform the processes described herein with respect to UE 22.

[0111] The communication system 10 further includes the security gateway 19 already referred to. FIG. 5 is a block diagram of security gateway 19 according to some embodiments of the present disclosure. The security gateway may have hardware 60 that may include a communication interface 62 configured to set up and maintain wired connection(s) and / or wireless connection(s) with one or more entities in system 10. The communication interface 62 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The hardware 60 of the security gateway 19 further includes processing circuitry 64. The processing circuitry 64 may include a processor 66 and memory 68. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 64 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 66 may be configured to access (e.g., write to and / or read from) memory 68, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0112] Thus, the security gateway 19 may further comprise software 70, which is stored in, for example, memory 68 at the security gateway 19, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the security gateway 19. The software 70 may be executable by the processing circuitry 64.

[0113] The processing circuitry 64 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by security gateway 19. The processor 66 corresponds to one or more processors 66 for performing security gateway 19 functions described herein. The security gateway 19 includes memory 68 that is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 70 may include instructions that, when executed by the processor 66 and / or processing circuitry 64, causes the processor 66 and / or processing circuitry 64 to perform the processes described herein with respect to security gateway 19. For example, the processing circuitry 64 of the security gateway 19 may include configuration unit 21 which is configured to perform one or more security gateway 19 functions as described herein such as, for example, with respect to IAB configuration.

[0114] In some embodiments, the inner workings of the network node 16, UE 22 and security gateway 19 may be as shown in FIGS. 4-5 and independently, the surrounding network topology may be that of FIG. 3.

[0115] The wireless connection 32 between the UE 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and / or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc. In some embodiments, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.

[0116] Although FIGS. 3-5 show various “units” such as configuration unit 21 and IAB unit 24 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.

[0117] FIG. 6 is a flowchart of an example process in a network node 16 according to one or more embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 36 (including the IAB unit 24), processor 38, and / or radio interface 30. Network node 16 is configured to transmit (Block S 100) information associated with at least one of an integrated access and backhaul, IAB, type or location information associated with the network node 16, as described herein. Network node 16 is configured to receive (Block S 102) a first operations, administration and Maintenance, 0AM, system address of a plurality of 0AM system addresses, where the first 0AM system address is based on the information and associated with a first 0AM system 23 that has the capability to configure the network node 16, as described herein. Network node 16 is configured to participate (Block S104) in an 0AM session with the first 0AM system 23, as described herein.

[0118] According to one or more embodiments, the information is transmitted to a security gateway 19, and the first 0AM system address is received from the security gateway 19.

[0119] According to one or more embodiments, the location information comprises at least one of: a parent network node-donor-distributed unit, DU, identifier associated with the network node mobile termination, MT; or at least one other unique identifier associated with the network node 16.

[0120] According to one or more embodiments, the at least one other unique identifier associated with the network node 16 comprises at least one of a trace area identifier or cell identifier.

[0121] According to one or more embodiments, the information is included one of a configuration payload attribute or a control plane attribute, as described herein. According to one or more embodiments, an internet key exchange, IKE, payload vendor identifier is included in a value set of the configuration payload attribute, as described herein.

[0122] According to one or more embodiments, the network node 16 is further configured to receive, from the first OAM system 23, an IAB configuration, as described herein.

[0123] According to one or more embodiments, the network node 16 is an IAB network node, as described herein.

[0124] According to one or more embodiments, the OAM session with the first OAM system 23 is part of a network node mobile termination, MT, handover from a first network node-donor-distributed unit, DU, to a second network node-donor-DU.

[0125] According to one or more embodiments, the IAB type corresponds to at least one of a vendor name or IAB function.

[0126] FIG. 7 is a flowchart of another example process in a network node 16 according to one or more embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 36 (including the IAB unit 24), processor 38, and / or radio interface 30. Network node 16 is configured to transmit (Block S106) information associated with at least one of an integrated access and backhaul, IAB, type or location information associated with the network node 16, as described herein. Network node 16 is configured to receive (Block S 108) a first operations, administration and Maintenance, OAM, system address of a plurality of OAM system addresses, the first OAM system address being associated with the information; and a first OAM system that has a capability to configure the network node 16, as described herein. Network node 16 is configured to participate (Block SI 10) in an OAM session with the first OAM system using the OAM system address, as described herein.

[0127] According to one or more embodiments, the information is transmitted to a security gateway, and the first OAM system address is received from the security gateway 19.

[0128] According to one or more embodiments, the information comprises one of: at least one internet engineering task force, IETF, attribute; or at least one third generation partnership project, 3 GPP, attribute.

[0129] According to one or more embodiments, the at least one IETF attribute or the at least one 3GPP attribute comprises one or more of: a parent network node identifier where a network node-mobile termination, -MT, of the network node 16 is attached; a parent network node donor-distributed unit, -DU, identity associated with the network node-MT; and at least one unique identifier in use by the network node 16 where the at least one unique identifier comprises one or both of a trace area identity and a cell identifier.

[0130] According to one or more embodiments, the at least one 3GPP attribute comprises one or both of: vendor name associated with the network node 16; and IAB function type associated with the network node 16.

[0131] According to one or more embodiments, the network node 16 is further configured to at least in part establish a security tunnel with a security gateway 19, where the transmission of the information to the security gateway 19 is via the security tunnel.

[0132] According to one or more embodiments, the network node 16 is an IAB network node, and the IAB network node is further configured to: transmit, to the first OAM system, the location information via the OAM session; and receive, from the first OAM system, an IAB configuration, where the IAB configuration is associated with the location information.

[0133] According to one or more embodiments, the IAB configuration comprises at least one IAB -distributed unit, IAB -DU, instantiate configuration.

[0134] According to one or more embodiments, the transmission of the information is associated with one of a startup procedure or power up procedure of the network node 16.

[0135] According to one or more embodiments, the network node 16 is an IAB network node; and the transmission of the information is associated with mobility of the IAB network node.

[0136] FIG. 8 is a flowchart of an example process in a security gateway 19 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of security gateway such as by one or more of processing circuitry 64 (including the configuration unit 21), processor 66, and / or communication interface 62. Security gateway 19 is configured to receive (Block SI 12) information from a network node 16, where the information is associated with at least one of an integrated access and backhaul, IAB, type or location information associated with the network node 16, as described herein. Security gateway 19 is configured to select (Block SI 14) a first operations, administration and Maintenance, OAM, system of a plurality of OAM systems based on the information, where the first OAM system has the capability to configure the network node 16, as described herein. Security gateway 19 is configured to transmit (Block SI 16), to the network node 16, an OAM system address of the first OAM system 23, as described herein. According to one or more embodiments, the location information comprises at least one of: a parent network node-donor-distributed unit, DU, identifier associated with the network node mobile termination, MT; or at least one other unique identifier associated with the network node 16.

[0137] According to one or more embodiments, the at least one other unique identifier associated with the network node 16 comprises at least one of a trace area identifier or cell identifier.

[0138] According to one or more embodiments, the information is included one of a configuration payload attribute or a control plane attribute.

[0139] According to one or more embodiments, an internet key exchange, IKE, payload vendor identifier is included in a value set of the configuration payload attribute.

[0140] According to one or more embodiments, the network node 16 is an IAB network node.

[0141] According to one or more embodiments, the IAB type corresponds to at least one of a vendor name or IAB function.

[0142] FIG. 9 is a flowchart of an example process in a security gateway 19 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of security gateway 19 such as by one or more of processing circuitry 64 (including the configuration unit 21), processor 66, and / or communication interface 62. Security gateway 19 is configured to receive (Block SI 18) information from a network node 16, where the information is associated with at least one of an integrated access and backhaul, IAB, type or location information associated with the network node 16, as described herein. Security gateway 19 is configured to select (Block S 120) a first operations, administration and Maintenance, 0AM, system of a plurality of 0AM systems based on the information, where the first 0AM system has a capability to configure the network node 16, as described herein. Security gateway 19 is configured transmit (Block S122), to the network node 16, an 0AM system address of the first 0AM system, as described herein.

[0143] According to one or more embodiments, the information comprises one of: at least one internet engineering task force, IETF, attribute; or at least one third generation partnership project, 3 GPP, attribute.

[0144] According to one or more embodiments, the at least one IETF attribute or the at least one 3GPP attribute comprises one or more of: a parent network node identifier where a network node-mobile termination, -MT, of the network node 16 is attached; a parent network node donor-distributed unit, -DU, identity associated with the network node-MT; and at least one unique identifier in use by the network node 16, the at least one unique identifier comprising one or both of a trace area identity and a cell identifier.

[0145] According to one or more embodiments, the at least one 3GPP attribute comprises one or both of: vendor name associated with the network node 16; and IAB function type associated with the network node 16.

[0146] According to one or more embodiments, the security gateway 19 is further configured to at least in part establish a security tunnel with the network node 16, where the information is received from the network node 16 via the security tunnel.

[0147] According to one or more embodiments, the network node 16 is an IAB network node.

[0148] According to one or more embodiments, the receiving of the information is associated with one of a startup procedure or power up procedure of the network node 16.

[0149] According to one or more embodiments, the network node 16 is an IAB network node; and the receiving of the information is associated with mobility of the IAB network node.

[0150] Further, as described above, one or more embodiments may support location-based configuration for a WAB in further 3GPP releases. For example, network node 16 may be configured to transmit information associated with a wireless access backhaul, WAB, type; or location information associated with the network node 16. Network node 16 is further configured to receive a first operations, administration and Maintenance, GAM, system address of a plurality of 0AM system addresses, where the first 0AM system address is associated with: the information; and a first 0AM system that has a capability to configure the network node 16. The network node 16 is further configured to participate in an 0AM session with the first 0AM system using the 0AM system address.

[0151] According to one or more embodiments, the information is transmitted to a security gateway 19, and the first 0AM system address is received from the security gateway 19.

[0152] According to one or more embodiments, the information comprises one of at least one internet engineering task force, IETF, attribute or at least one third generation partnership project, 3 GPP, attribute.

[0153] According to one or more embodiments, the at least one IETF attribute or the at least one 3GPP attribute comprises one or more of: a parent network node identifier where a network node-mobile termination, -MT, of the network node 16 is attached; a parent network node donor-distributed unit, -DU, identity associated with the network node-MT; and at least one unique identifier in use by the network node 16, the at least one unique identifier comprising one or both of a trace area identity and a cell identifier.

[0154] According to one or more embodiments, the at least one 3GPP attribute comprises one or both of: vendor name associated with the network node 16; and WAB function type associated with the network node 16.

[0155] According to one or more embodiments, the network node 16 is further configured to at least in part establish a security tunnel with a security gateway 19, where the transmission of the information to the security gateway 19 is via the security tunnel.

[0156] According to one or more embodiments, the network node 16 is an WAB network node; and the WAB network node is further configured to: transmit, to the first OAM system, the location information via the OAM session; and receive, from the first OAM system, an WAB configuration, where the WAB configuration is associated with the location information.

[0157] According to one or more embodiments, the WAB configuration comprises at least one WAB -distributed unit, WAB -DU, instantiate configuration.

[0158] According to one or more embodiments, the transmission of the information is associated with one of a startup procedure or power up procedure of the network node 16.

[0159] According to one or more embodiments, the network node 16 is an WAB network node, and the transmission of the information is associated with mobility of the IAB network node.

[0160] In some embodiments, the telecommunication system 10 may include one or more Open-RAN (ORAN) network nodes 16. An ORAN network node 16 is a node in the telecommunication system 10 that supports an ORAN specification (e.g., a specification published by the 0-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication system 10, including one or more network nodes 16 in the access network 12 and / or core network nodes.

[0161] Examples of an ORAN network node 16 include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near- real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the O- RAN Alliance or comparable technologies. The network nodes 16 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 22a, 22b, 22c, and 22d (one or more of which may be generally referred to as UEs 22) to the core network 14 over one or more wireless connections.

[0162] FIG. 10 is a block diagram illustrating a virtualization environment 94 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 94 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 94 includes components defined by the 0-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface.

[0163] Applications 96 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 94 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0164] Hardware 98 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 100 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 102a and 102b (one or more of which may be generally referred to as VMs 102), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 100 may present a virtual operating platform that appears like networking hardware to the VMs 102.

[0165] The VMs 102 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 100. Different embodiments of the instance of a virtual appliance 96 may be implemented on one or more of VMs 102, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0166] In the context of NFV, a VM 102 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non- virtualized machine. Each of the VMs 102, and that part of hardware 98 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 102 on top of the hardware 98 and corresponds to the application 96.

[0167] Hardware 98 may be implemented in a standalone network node with generic or specific components. Hardware 98 may implement some functions via virtualization. Alternatively, hardware 98 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 104, which, among others, oversees lifecycle management of applications 96. In some embodiments, hardware 98 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 106 which may alternatively be used for communication between hardware nodes and radio units.

[0168] Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the sections below provide details and examples of arrangements for IAB configuration such as, for example, at mobility.

[0169] Some embodiments provide for IAB configuration.

[0170] Part A: determine a specific 0AM system 23 for the IAB node during security validation.

[0171] In step 2b above, when performing the security verification, the IAB node (e.g., network node 16) sets up a security tunnel with security gateway 19. In one or more embodiments, DNS is not used as it may be assumed that there is only one security gateway 19 in the network but there are a plurality of OAMs, i.e., 0AM systems. The plurality of 0AM systems 23 may be per IAB type based and location based. During this procedure, the IAB node may provide its type and location information to the security gateway 19. In one or more embodiments, the IAB type may refer to vendor name and / or IAB function, e.g., vendor 1 -IAB -DU, vendor2-IAB-CU, etc.

[0172] In response to or based on receiving the IAB location information, the security gateway 19 maps the IAB location identity and IAB type information to a specific 0AM system 23 (e.g., of a plurality of 0AM systems) which has the capability to configure the IAB node at its location with specific (e.g., correct) configuration data.

[0173] The security gateway 19 responds with the specific 0AM system address.

[0174] One example of providing IAB location information is that if IKEv2 is used in this step, there are several different ways to achieve the same functionality. However, the present disclosure is not limited to IKEv2 as other protocols are applicable in accordance with the teachings described herein.

[0175] Option 1:

[0176] 1. A new internet engineering task force (IETF) CP attribute is provided. The new IETF CP attribute may have a specific name, e.g., “IAB-L0CATI0N-INF0”. This attribute uses a type of value from the values that are reserved for internet assigned numbers authority (IANA) [e.g., from range: 16-16383].

[0177] 2. The content of this attribute includes the following information: a. The parent gNB ID where the IAB -MT is attached. b. The parent lAB-donor-DU identity where the IAB-MT is communicated. MT may correspond to a low layer function used by IAB where MT may not be managed by OAM system 23. c. One or more other unique identities the IAB is using, e.g. TAI (Trace Area Identity), Cell ID, etc.

[0178] Option 2:

[0179] 1. A new standards development organization (SDO)’s, e.g., 3GPP, specific Configuration Payload attribute which may have the name e.g., “IAB- LOCATION-INFO”. This attribute uses a type value from the values that are reserved for private use but unique within the specific SDO [Private Use range: 16384-32767]

[0180] 2. The content of this attribute includes the following information: a. The parent gNB ID where the IAB-MT is attached. b. The parent lAB-donor-DU identity where the IAB-MT is communicated. c. One or more other unique identities the IAB is using, e.g. TAI (Trace Area Identity), Cell ID, etc.

[0181] In this case, to help ensure that the initiator and the responder understand that the new attribute is defined within the specific SDO domain, the IKE pay load Vendor ID MUST be included with the value set to the specific SDO ID, e.g., 3GPP, etc.

[0182] Another example of providing IAB type information is described as follows. If IKEv2 is used in this step, there are a few different ways to achieve the same functionality.

[0183] Option 1:

[0184] 1. A new IETF CP attribute is provided. The new IETF CP attribute may have a specific name e.g., “IAB -TYPE-INFO”. This attribute uses a type of value from the values that are reserved for IANA [from range: 16-16383].

[0185] 2. The content of this attribute includes the following information: a. IAB vendor id b. IAB function type.

[0186] Option 2:

[0187] 1. A new SDO, e.g., 3GPP, specific Configuration Payload attribute is provided. The new SDO specific Configuration Pay load attribute may have the name e.g., “IAB- LOCATION-INFO”. This attribute uses a type value from the values that are reserved for private use but that are unique within the specific SDO [Private Use range: 16384-32767] 2. The content of this attribute includes the following information: a. IAB vendor id. b. IAB function type.

[0188] In this case, to help ensure that the initiator and the responder understand that the new attribute is defined within the specific SDO domain, the IKE pay load Vendor ID is included with the value set to the specific SDO ID, e.g., 3GPP, etc.

[0189] Part B: provide specific (e.g., correct) configurations based on the IAB node location by OAM system 23

[0190] After step 2b, it may be assumed that the IAB node could talk with a specific OAM system 23. An OAM session is setup between the OAM system 23 and the IAB node.

[0191] In step 2c, the IAB node queries the OAM system 23. The IAB node may also need to send its location information as defined for the IKEv2 protocol, but in a different format and protocol to the OAM system 23.

[0192] Upon receiving the query request, the OAM maps the received location information into a set of configurations and sends it to the IAB for IAB -DU instantiate configurations.

[0193] The above procedure is applicable to both IAB node bootstrapping procedures. It is also applicable to the IAB node mobility procedure where a new IAB -DU instantiate is created. The above procedure may also be supported in the PnC procedure.

[0194] In one or more embodiments, the triggering of retrieving CM information is an IAB DU instantiation procedure at IAB bootstrapping or mobility.

[0195] In one or more embodiments, the IAB mobility procedure involves IAB -donor CU+DU change, or CU change only. In one or more embodiments, the IAB -MT may occur first, followed by IAB -DU instantiation. The last step may be UE 22 handover.

[0196] Examples

[0197] Example Al. A network node 16 (e.g., IAB node) configured to, and / or comprising a radio interface 30 and / or comprising processing circuitry 36 configured to: cause transmission of information, the information being associated with at least one of an integrated access and backhaul, IAB, type or location information associated with the network node 16; receive a first operations, administration and Maintenance, OAM, system address of a plurality of OAM system addresses, the first OAM system address being based on the information and associated with a first OAM system that has the capability to configure the network node 16; and participate in an OAM session with the first OAM system.

[0198] Example A2. The network node 16 of Example Al, wherein the information is transmitted to a security gateway 19; and the first OAM system address is received from the security gateway 19.

[0199] Example A3. The network node 16 of Examples A1-A2, wherein the location information comprises at least one of: a parent network node-donor-distributed unit, DU, identifier associated with the network node mobile termination, MT ; or at least one other unique identifier associated with the network node 16.

[0200] Example A4. The network node 16 of Example A3, wherein the at least one other unique identifier associated with the network node 16 comprises at least one of a trace area identifier or cell identifier.

[0201] Example A5. The network node 16 of any one of Examples A1-A4, wherein the information is included one of a configuration payload attribute or a control plane attribute.

[0202] Example A6. The network node 16 of Example A5, wherein an internet key exchange, IKE, payload vendor identifier is included in a value set of the configuration payload attribute.

[0203] Example A7. The network node 16 of any one of Examples A1-A6, wherein the network node 16 is further configured to receive, from the first OAM system, an IAB configuration.

[0204] Example A8. The network node 16 of any one of Examples A1-A7, wherein the network node 16 is an IAB network node.

[0205] Example A9. The network node 16 of any one of Examples A1-A8, wherein the OAM session with the first OAM system is part of a network node mobile termination, MT, handover from a first network node-donor-distributed unit, DU, to a second network node-donor-DU.

[0206] Example A10. The network node 16 of any one of Examples A1-A9, wherein the IAB type corresponds to at least one of a vendor name or IAB function.

[0207] Example Bl. A method implementing a network node 16, the method comprising: causing transmission of information, the information being associated with at least one of an integrated access and backhaul, IAB, type or location information associated with the network node 16; receiving a first operations, administration and Maintenance, OAM, system address of a plurality of OAM system addresses, the first OAM system address being based on the information and associated with a first OAM system that has the capability to configure the network node 16; and participating in an OAM session with the first OAM system.

[0208] Example B2. The method of Example Bl, wherein the information is transmitted to a security gateway 19; and the first OAM system address is received from the security gateway 19.

[0209] Example B3. The method of Examples B 1-B2, wherein the location information comprises at least one of: a parent network node-donor-distributed unit, DU, identifier associated with the network node mobile termination, MT ; or at least one other unique identifier associated with the network node 16.

[0210] Example B4. The method of Example B3, wherein the at least one other unique identifier associated with the network node 16 comprises at least one of a trace area identifier or cell identifier.

[0211] Example B5. The method of any one of Examples B 1-B4, wherein the information is included one of a configuration payload attribute or a control plane attribute.

[0212] Example B6. The method of Example B5, wherein an internet key exchange, IKE, payload vendor identifier is included in a value set of the configuration payload attribute.

[0213] Example B7. The method of any one of Examples B 1-B6, further comprising receiving, from the first OAM system, an IAB configuration.

[0214] Example B8. The method of any one of Examples B 1-B7, wherein the network node 16 is an IAB network node.

[0215] Example B9. The method of any one of Examples B 1-B8, wherein the OAM session with the first OAM system is part of a network node mobile termination, MT, handover from a first network node-donor-distributed unit, DU, to a second network node- donor-DU. Example BIO. The network node 16 of any one of Examples B1-B9, wherein the IAB type corresponds to at least one of a vendor name or IAB function.

[0216] Example Cl. An security gateway 19 configured to, and / or comprising a radio interface and / or processing circuitry 64 configured to: receive information from a network node 16, the information being associated with at least one of an integrated access and backhaul, IAB, type or location information associated with the network node 16; select a first operations, administration and Maintenance, OAM, system of a plurality of OAM systems based on the information, the first OAM system having the capability to configure the network node 16; and cause transmission, to the network node 16, of an OAM system address of the first OAM system.

[0217] Example C2. The security gateway 19 of Example Cl, wherein the location information comprises at least one of: a parent network node-donor-distributed unit, DU, identifier associated with the network node mobile termination, MT ; or at least one other unique identifier associated with the network node 16.

[0218] Example C3. The security gateway 19 of Example C2, wherein the at least one other unique identifier associated with the network node 16 comprises at least one of a trace area identifier or cell identifier.

[0219] Example C4. The security gateway 19 of any one of Examples C1-C3, wherein the information is included one of a configuration payload attribute or a control plane attribute.

[0220] Example C5. The security gateway 19 of Example C4, wherein an internet key exchange, IKE, payload vendor identifier is included in a value set of the configuration payload attribute.

[0221] Example C6. The security gateway 19 of any one of Examples C1-C5, wherein the network node 16 is an IAB network node.

[0222] Example C7. The security gateway 19 of any one of Examples C1-C6, wherein the IAB type corresponds to at least one of a vendor name or IAB function.

[0223] Example DI. A method implemented by a security gateway 19, the method comprising: receiving information from a network node 16, the information being associated with at least one of an integrated access and backhaul, IAB, type or location information associated with the network node 16; selecting a first operations, administration and Maintenance, OAM, system of a plurality of OAM systems based on the information, the first OAM system having the capability to configure the network node 16; and causing transmission, to the network node 16, of an OAM system address of the first OAM system.

[0224] Example D2. The method of Example DI, wherein the location information comprises at least one of: a parent network node-donor-distributed unit, DU, identifier associated with the network node mobile termination, MT ; or at least one other unique identifier associated with the network node 16.

[0225] Example D3. The method of Example D2, wherein the at least one other unique identifier associated with the network node 16 comprises at least one of a trace area identifier or cell identifier.

[0226] Example D4. The method of any one of Examples D1-D3, wherein the information is included one of a configuration payload attribute or a control plane attribute.

[0227] Example D5. The method of Example D4, wherein an internet key exchange, IKE, payload vendor identifier is included in a value set of the configuration payload attribute.

[0228] Example D6. The method of any one of Examples D1-D5, wherein the network node 16 is an IAB network node.

[0229] Example D7. The method of any one of Examples D1-D6, wherein the IAB type corresponds to at least one of a vendor name or IAB function.

[0230] STANDARDIZING THE PROPOSED SOLUTIONS

[0231] Described below are non-limiting examples of how certain aspects of the proposed solutions, described herein, could be implemented within the framework of a specific communication standard. In particular, the description below provides non-limiting examples of how the proposed solutions could be implemented within the framework of a 3 GPP TSG RAN standard. The changes described below are merely intended to illustrate how certain aspects of the proposed solutions could be implemented in a particular standard. However, the proposed solutions could also be implemented in other suitable manners, both in the 3GPP Specification and in other specifications or standards.

[0232] Potential use cases and requirements to support IAB node management

[0233] [x] 3GPP TS 38.401: “NG-RAN; Architecture description”.

[0234] [y] 3GPP TS 28.315: “Management and orchestration; Plug and Connect; Procedure flows”

[0235] [z] 3GPP TS 23.501: “System architecture for the 5G System (5GS)”

[0236] The below description corresponds to proposed changes and / or added material to, for example, 3GPP TR 28.875.

[0237] 5.x Use case #x IAB node powers up and connects to OAM system

[0238] 5.x.l Description

[0239] FIG. 11 is an example diagram of an overall architecture of IAB as specified in TS 38.401 [x]. The lAB-node connects to an upstream lAB-node or an lAB-donor-DU via a subset of the UE functionalities of the NR Uu interface (named IAB-MT function of lAB- node).

[0240] When lAB-node powers up, it needs to connect to OAM system. FIG. 12 is an example diagram of a view of OAM connectivity.

[0241] Today NE connects to OAM system when powers up via Plug and Connect (PnC) procedures as described in TS 28.315[y]. NE needs to obtain initial IP configuration from IP autoconfiguration service (e.g., DHCP server), satisfy security aspect including CA / RA enrolment and connectivity to SeGW before connecting to SCS. The initial IP configuration for OAM connectivity includes basic IP configuration information (e.g., IP address, netmask, default gateway, domain name, IP address(es) of DNS servers, time servers) or together with information such as IP address or FQDN of CA / RA server, IP address or FQDN of SeGW, IP address or FQDN of SCS, etc depends on operator’s deployment scenarios.

[0242] IAB node differs from NE as static node in term of its wireless connection with IAB -donor-node and UE, it can’t reach to DHCP server in the same way as NE like gNB. This use case studies the potential requirements and solutions how the IAB node obtains the IP configuration for OAM connectivity, with that IAB node performs the subsequent PnC procedures as same as specified today in the PnC specifications. This may involve connecting to multiple OAM systems in sequence as described in TS 28.315 [y] clause 5.1.

[0243] 5.x.2 Potential requirements REQ_IAB_CON_1: 3GPP management system should have the capability to support IP configuration for OAM connectivity based on IAB node location.

[0244] REQ_IAB_C0N_2: 3GPP management system should have the capability to enable IAB node to obtain the IP configuration for OAM connectivity based on location during the integration procedure.

[0245] REQ_IAB_C0N_3: IAB node should meet the security requirement of PnC procedures to connect to OAM system at power up.

[0246] Potential use cases and requirements to support IAB node management

[0247] [x] 3GPP TS 38.401: “NG-RAN; Architecture description”.

[0248] [y] 3GPP TS 28.315: “Management and orchestration; Plug and Connect; Procedure flows”

[0249] [z] 3GPP TS 23.501: “System architecture for the 5G System (5GS)”

[0250] The below description corresponds to proposed changes and / or added material to, for example, 3GPP TR 28.875.

[0251] 5.x Use case #x IAB node connects to different OAM system due to mobility

[0252] 5.x.1 Description

[0253] Since Rel-18 IAB node mobility is supported, the mobility scenarios focus on mobile IAB node mounted on vehicles providing 5G coverage / capacity enhancement to onboard and / or surrounding UEs. The procedures of IAB-MT inter-donor handover and mobile IAB migration are specified in TS 38.401 [x]. In TS 23.501[z], roaming of the MBSR is supported, MBSR (IAB-DU) can use lAB-node integration procedure or inter- IAB -donor gNB mobility procedure to integrate into the serving PLMN to provide service.

[0254] In some mobility scenarios mobile IAB node may need to connect to a different OAM system within same PLMN in non-roaming scenarios or different serving PLMN (VPLMN) in roaming scenarios.

[0255] This use case takes mobile IAB-DU migration scenario to study the potential requirement and solution to support mobile IAB node connectivity to a different OAM system due to mobility.

[0256] Referring to TS 38.401 [x] section 8.23.3, FIG. 13 describes the mobile IAB-DU migration procedure. To support this procedure, the mobile IAB node concurrently supports two logical mobile lAB-DUs. At the end of the procedure, the Fl link between source logical DU and source lAB-donor-CU is removed. FIG. 14 describes simplified view of mobile IAB node connect to OAM system during mobility. Before mobile IAB-DU migration, mobile IAB node is connected to source OAM system, mobile IAB node may need to connect to target OAM system at the end of this procedure.

[0257] Today PnC procedures specified in TS 28.315 [y] enable NE to connect the OAM system while satisfy the security aspect. To allow mobile IAB node to use PnC procedures to connect to the OAM system in mobility scenarios, mobile IAB node needs to obtain IP configuration for OAM connectivity (TS 28.315 [y] clause 5.2) based on its location.

[0258] 5.x.2 Potential requirements

[0259] REQ_IAB_MOB_CON_1: 3GPP management system should have the capability to support IP configuration for OAM connectivity based on mobile IAB node location.

[0260] REQ_IAB_M0B_C0N_2: 3GPP management system should have the capability to enable mobile IAB node to obtain IP configuration for OAM connectivity based on mobile IAB node location.

[0261] REQ_IAB_M0B_C0N_3: Mobile IAB node should meet the security requirement of PnC procedures to connect to OAM system during mobility.

[0262] Potential solutions

[0263] [x] 3GPP TS 28.315: “Management and orchestration; Plug and Connect; Procedure flows”.

[0264] [y] 3GPP TS 23.501: “System architecture for the 5G System (5GS)”.

[0265] The below description corresponds to proposed changes and / or added material to, for example, 3GPP TR 28.875.

[0266] 6.x Potential solutions #x PDU session based solution to support IAB node connectivity to OAM system.

[0267] According to TS 28.315 [x], the initial IP configuration of OAM system includes basic IP configuration information (e.g., IP address, netmask, default gateway, domain name, IP address(es) of DNS servers, time servers) or together with information such as IP address or FQDN of CA / RA server, IP address or FQDN of SeGW, IP address or FQDN of SCS, etc.

[0268] IAB node can get the initial IP configuration of OAM system via PDU session that setup between IAB-MT and 5GC, using this connectivity IAB node can obtain the initial IP configuration provided by IP autoconfiguration service (e.g., DHCP server), and additionally may perform DNS query depends on the operator’s deployment scenario. To use this solution to get initial IP configuration from DHCP server, SMF acts like DHCP relay agent, such capability is described in TS 23.501 [y] clause 5.8.2.2.

[0269] With initial IP configuration obtained as above, IAB node can proceed Plug and Connect procedures to connect to 0AM system.

[0270] Potential solutions

[0271] 6.x Potential solutions #x Configuration based solution to support IAB node connectivity

[0272] [x] 3GPP TS 38.401: “NG-RAN; Architecture description”.

[0273] [y] 3GPP TS 28.315: “Management and orchestration; Plug and Connect; Procedure flows”

[0274] The below description corresponds to proposed changes and / or added material to, for example, 3GPP TR 28.875.

[0275] IAB node needs to obtain the IP configuration of 0AM system before connecting to it. According to TS 28.315 [y], IP configuration of 0AM system may include IP address or FQDN of CA / RA server, SeGW and SCS, IP address of DNS servers depends on operator’ s deployment.

[0276] This solution requires CM configuration (NRM) to support the mapping of IP configuration of 0AM system with location. Such mapping is provisioned to IAB node after IAB node connects to 0AM system at power up or prior to mobility. Alternatively, such mapping can be manually configured in IAB node.

[0277] 1. The IP configuration of 0AM system can be mapped to location information such as TAC, TAI, gNBId of lAB-donor node and PLMN info. The table below illustrates an example of mapping:

[0278] Table 6.X.3-1 0AM system IP configuration mapping to location 2. IAB node can look up this mapping table to get IP configuration of OAM system with one or more of the following location information depends on its physical location or the mobility scenarios as specified in TS 38.401 [x] clause 8.12 and clause 8.23:

[0279] • TAC or TAI pertaining to the cells where IAB-MT is connected.

[0280] • TAC or TAI pertaining to the cells served by IAB -DU.

[0281] • The gNBId of the lAB-donor-CU and PLMN info that IAB -DU connects to.

[0282] • The gNBId of the lAB-donor-CU and PLMN info that serves the IAB-MT.

[0283] 3. With IP configuration of OAM system, IAB node can proceed Plug and Connect procedures to connect to OAM system.

[0284] As will be appreciated by one of skill in the art, the concepts described herein may be embodied as a method, data processing system, computer program product and / or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and / or functionality described herein may be performed by, and / or associated to, a corresponding module, which may be implemented in software and / or firmware and / or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.

[0285] Some embodiments are described herein with reference to flowchart illustrations and / or block diagrams of methods, systems and computer program products. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer (to thereby create a special purpose computer), special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0286] These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function / act specified in the flowchart and / or block diagram block or blocks.

[0287] The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0288] It is to be understood that the functions / acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality / acts involved. Although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

[0289] Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Python, Java® or C++. However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0290] Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments can be combined in any way and / or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them, and shall support claims to any such combination or subcombination.

[0291] Abbreviations that may be used in the preceding description include:

[0292] Abbreviation Explanation

[0293] CP IKE Configuration Payload

[0294] IAB Integrated Access and Backhaul

[0295] IKEv2 Internet Key Exchange protocol version 2

[0296] IPSec IP security

[0297] RAN Radio Access Network

[0298] UE User Equipment

[0299] It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings without departing from the scope of the following claims.

Claims

CLAIMS1. A method implemented by a network node (16), the method comprising: transmitting (S106) information associated with at least one of an integrated access and backhaul, IAB, type or location information associated with the network node (16); receiving (S108) a first operations, administration and Maintenance, 0AM, system address of a plurality of 0AM system addresses, the first 0AM system address being associated with: the information; and a first 0AM system that has a capability to configure the network node (16); and participating (SI 10) in an 0AM session with the first 0AM system using the 0AM system address.

2. The method of Claim 1, wherein the information is transmitted to a security gateway (19); and the first 0AM system address is received from the security gateway (19).

3. The method of Claims 1-2, wherein the information comprises one of: at least one internet engineering task force, IETF, attribute; or at least one third generation partnership project, 3 GPP, attribute.

4. The method of Claim 3, wherein the at least one IETF attribute or the at least one 3GPP attribute comprises one or more of: a parent network node identifier where a network node-mobile termination, -MT, of the network node (16) is attached; a parent network node donor-distributed unit, -DU, identity associated with the network node-MT; and at least one unique identifier in use by the network node (16), the at least one unique identifier comprising one or both of a trace area identity and a cell identifier.

5. The method of Claim 3, wherein the at least one 3 GPP attribute comprises one or both of: vendor name associated with the network node (16) ; andIAB function type associated with the network node (16).

6. The method of any one of Claims 1-5, further comprising at least in part establishing a security tunnel with a security gateway (19), the transmission of the information to the security gateway (19) being via the security tunnel.

7. The method of any one of Claims 1-6, wherein the network node (16) is an IAB network node; and the method further comprising: transmitting, to the first OAM system, the location information via the 0AM session; and receiving, from the first OAM system, an IAB configuration, the IAB configuration being associated with the location information.

8. The method of Claim 7, wherein the IAB configuration comprises at least one IAB -distributed unit, IAB -DU, instantiate configuration.

9. The method of any one of Claims 1-8, wherein the transmission of the information is associated with one of a startup procedure or power up procedure of the network node (16).

10. The method of any one of Claims 1-8, wherein the network node (16) is an IAB network node; and the transmission of the information is associated with mobility of the IAB network node.

11. A network node (16) configured to: transmit information associated with at least one of an integrated access and backhaul, IAB, type or location information associated with the network node (16); receive a first operations, administration and Maintenance, OAM, system address of a plurality of OAM system addresses, the first OAM system address being associated with: the information; anda first OAM system that has a capability to configure the network node(16); and participate in an OAM session with the first OAM system using the OAM system address.

12. The network node (16) of Claim 11, wherein the information is transmitted to a security gateway (19); and the first OAM system address is received from the security gateway (19).

13. The network node (16) of Claims 11-12, wherein the information comprises one of: at least one internet engineering task force, IETF, attribute; or at least one third generation partnership project, 3 GPP, attribute.

14. The network node (16) of Claim 13, wherein the at least one IETF attribute or the at least one 3 GPP attribute comprises one or more of: a parent network node identifier where a network node-mobile termination, -MT, of the network node (16) is attached; a parent network node donor-distributed unit, -DU, identity associated with the network node-MT; and at least one unique identifier in use by the network node (16), the at least one unique identifier comprising one or both of a trace area identity and a cell identifier.

15. The network node (16) of Claim 13, wherein the at least one 3GPP attribute comprises one or both of: vendor name associated with the network node (16); andIAB function type associated with the network node (16).

16. The network node (16) of any one of Claims 11-15, wherein the network node (16) is further configured to at least in part establish a security tunnel with a security gateway (19), the transmission of the information to the security gateway (19) being via the security tunnel.

17. The network node (16) of any one of Claims 11-16, wherein the network node (16) is an IAB network node; andthe IAB network node is further configured to: transmit, to the first OAM system, the location information via the 0AM session; and receive, from the first OAM system, an IAB configuration, the IAB configuration being associated with the location information.

18. The network node (16) of Claim 17, wherein the IAB configuration comprises at least one IAB -distributed unit, IAB-DU, instantiate configuration.

19. The network node (16) of any one of Claims 11-18, wherein the transmission of the information is associated with one of a startup procedure or power up procedure of the network node (16).

20. The network node (16) of any one of Claims 11-18, wherein the network node (16) is an IAB network node; and the transmission of the information is associated with mobility of the IAB network node.

21. A method implemented by a security gateway (19), the method comprising: receiving (S106) information from a network node (16), the information being associated with at least one of an integrated access and backhaul, IAB, type or location information associated with the network node (16); selecting (S108) a first operations, administration and Maintenance, OAM, system of a plurality of OAM systems based on the information, the first OAM system having a capability to configure the network node (16); and transmitting (SI 10), to the network node (16), an OAM system address of the first OAM system.

22. The method of Claim 21, wherein the information comprises one of: at least one internet engineering task force, IETF, attribute; or at least one third generation partnership project, 3 GPP, attribute.

23. The method of Claim 22, wherein the at least one IETF attribute or the at least one 3GPP attribute comprises one or more of:a parent network node identifier where a network node-mobile termination, -MT, of the network node (16) is attached; a parent network node donor-distributed unit, -DU, identity associated with the network node-MT; and at least one unique identifier in use by the network node (16), the at least one unique identifier comprising one or both of a trace area identity and a cell identifier.

24. The method of Claim 22, wherein the at least one 3GPP attribute comprises one or both of: vendor name associated with the network node (16); andIAB function type associated with the network node (16).

25. The method of any one of Claims 21-24, further comprising at least in part establishing a security tunnel with the network node (16), the information being received from the network node (16) via the security tunnel.

26. The method of any one of Claims 21-25, wherein the network node (16) is an IAB network node.

27. The method of any one of Claims 21-26, wherein the receiving of the information is associated with one of a startup procedure or power up procedure of the network node (16).

28. The method of any one of Claims 21-26, wherein the network node (16) is an IAB network node; and the receiving of the information is associated with mobility of the IAB network node.

29. A security gateway (19) configured to: receive information from a network node (16), the information being associated with at least one of an integrated access and backhaul, IAB, type or location information associated with the network node (16);select a first operations, administration and Maintenance, OAM, system of a plurality of OAM systems based on the information, the first OAM system having a capability to configure the network node (16); and transmit, to the network node (16), an OAM system address of the first OAM system.

30. The security gateway (19) of Claim 29, wherein the information comprises one of: at least one internet engineering task force, IETF, attribute; or at least one third generation partnership project, 3 GPP, attribute.

31. The security gateway (19) of Claim 30, wherein the at least one IETF attribute or the at least one 3GPP attribute comprises one or more of: a parent network node identifier where a network node-mobile termination, -MT, of the network node (16) is attached; a parent network node donor-distributed unit, -DU, identity associated with the network node-MT; and at least one unique identifier in use by the network node (16), the at least one unique identifier comprising one or both of a trace area identity and a cell identifier.

32. The security gateway (19) of Claim 30, wherein the at least one 3GPP attribute comprises one or both of: vendor name associated with the network node (16); andIAB function type associated with the network node (16).

33. The security gateway (19) of any one of Claims 29-32, wherein the security gateway (19) is further configured to at least in part establish a security tunnel with the network node (16), the information being received from the network node (16) via the security tunnel.

34. The security gateway (19) of any one of Claims 29-33, wherein the network node (16) is an IAB network node.

35. The security gateway (19) of any one of Claims 29-34, wherein the receiving of the information is associated with one of a startup procedure or power up procedure of the network node (16).

36. The security gateway (19) of any one of Claims 29-34, wherein the network node (16) is an IAB network node; and the receiving of the information is associated with mobility of the IAB network node.

Images