Dynamic configuration of radio access network (RAN) nodes with wireless backhaul

Abstract

A method implemented by a radio access node, RAN, node that is configured to communicate at least via a wireless backhaul is provided. The RAN node indicates location information to an operations, administration and maintenance, OAM, system. The RAN node receives a RAN node configuration that is based on the location information. At least one action is performed based on the RAN node configuration.

Description

DYNAMIC CONFIGURATION OF RADIO ACCESS NETWORK (RAN) NODES WITH WIRELESS BACKHAULFIELD

[0001] The present disclosure relates to wireless communications, and in particular, to configurations for radio access (RAN) nodes with wireless backhaul.BACKGROUND

[0002] 3GPP Rel-19 Wireless Access and Backhaul (WAB) Overview

[0003] At the RAN#102 meeting, a Rel-19 Study Item Description (SID) for the Rel- 19 Study on additional topological enhancements for NR in RP-234041 was approved. The study consists of two parts:• Wireless Access Backhaul (WAB), which refers to a mobile gNB.• 5G Femto.

[0004] The justification of the WAB part of the SI is:

[0005] The legacy building blocks for 5G RAN topologies should be enhanced to provide a broader range of use cases, such as:

[0006] 5G access for UEs onboard aircrafts, cruise ships, helicopters, and vehicles in remote areas with limited sky visibility via an onboard gNB.

[0007] - B ackhauling of NG and Xn via TN and NTN, including support of NTN<-> TN handover for backhaul.

[0008] - Support for onboard / on-site MEC and local services.

[0009] - Support for backhauling without RAN-sharing or roaming agreements between access PLMN(s) and backhaul PLMN(s).

[0010] - Backhauling for local gNB deployed in public safety or disaster recovery scenarios.

[0011] It is assumed that Wireless Access Backhaul (WAB) is aligned with VMR use cases and with the SA2-endorsed SID on architectural enhancements for Rel-19 VMR. It is expected that single-hop backhauling is sufficient for Wireless Access Backhaul (WAB) and that there is no impact to UEs at this late stage of 5G deployment.

[0012] The objectives from the SID related to the WAB study are as follows:

[0013] - Study the support of WAB including [RAN3, RAN2]:

[0014] - Study the architecture and protocol stack of supporting a gNB with MT function providing PDU session backhaul.

[0015] - Study impact of WAB mobility within an existing RAN (e.g., inter-gNB neighbour relations).

[0016] - Identify necessary inter-gNB- and gNB-to-CN signalling to address the support of WAB.

[0017] - Study signalling enhancements on resource multiplexing for WAB.

[0018] NOTE 1: No impact on the UE.

[0019] NOTE 2: Coordination with other WGs (e.g. SA2) when needed.

[0020] The WAB study does not preclude any backhaul scenario (e.g. NTN or TN).

[0021] A potential WAB architecture, discussed in company contributions to the RAN# 102 meeting is shown in FIGURE 1.

[0022] The key feature of the WAB architecture is that a WAB node consists of a WAB-gNB and a WAB-MT. The WAB-gNB part of an WAB node serves UEs, while the WAB node uses its WAB-MT part to connect with the rest of the mobile network, i.e., to connect to the WAB-MT’ s serving gNB (the BH-gNB in Fig. 1). In this architecture, the PDU sessions established between the WAB-MT and the BH-UPF are used to carry the NGAP and XnAP connections of the WAB-gNB.

[0023] The 5G Core Network (5GC) serving the WAB-gNB with its connected UEs (i.e., the UE- 5GC, in Fig. 1) may be the same as or different from the 5G Core Network (5GC) serving the WAB-MT (i.e., the BH-5GC in Fig. 1).

[0024] Plug and connect procedure for OAM

[0025] Plug and connect (PnC) is the procedure that a network node uses to initiate an IP connection to OAM network. Plug and connect to OAM system includes the steps of initial IP autoconfiguration, Certificate enrollment, Establishing a secure connection to SeGW and Establishing a secure connection to Software configuration server (SCS). The initial IP autoconfiguration obtains client IP configuration and IP address or Fully Qualified Domain Names (FQDN) of CA / RA, SeGW and SCS via DHCP request. To perform CA / RA enrollment, the Network Element may be provisioned with operator’s root certificate if the root certificate is not obtained during CMPv2 protocol (TS 33.310 vl8.0.0). 3GPP TS 28.314, TS 28.315 and TS 28.315 specify stage 1 / 2 / 3 descriptions for the Plug and Connect.

[0026] TS 28.314 vl7.0.0: "plug and connect; Concepts and requirements".

[0027] TS 28.315 vl7.0.0: "plug and connect; Procedure flows".

[0028] TS 28.316 vl7.0.0: "plug and connect; Data formats".

[0029] Parameters configured at a gNB by the OAM

[0030] The TS 28.532 specifies operations and notifications for provisioning management service. The specification TS 28.541 defines the NR network resource model (NRM) that contains the information object class definitions, which describe the parameters configured by the OAM to the RAN and CN nodes. Below is an example of class definition used for providing the gNB with the IP address it should use for NG-C communication with the AMF.

[0031] »»»»»»>Start of excerpt from TS 28.541<<<<<<<<<<<<<<

[0032] 4.3.10 EP_NgC

[0033] 4.3.10.1 Definition

[0034] This IOC represents the local end point of the control plane interface (NG-C) between the gNB and AMF. The transport network layer is built on IP transport. For the reliable transport of signalling messages, SCTP is added on top of IP. The application layer signalling protocol is referred to as NG-AP (NG Application Protocol).

[0035] 3GPP TS 38.470 [7] noted that "one gNB-CU and a set of gNB-DUs are visible to other logical nodes as a gNB or an en-gNB where the gNB terminates the Xn and the NG interfaces, and the en-gNB terminates the X2 and the Sl-U interfaces".

[0036] 4.3.10.2 Attributes

[0037] The EP_NgC IOC includes attributes inherited from EP_RP IOC (defined in TS 28.622

[0030] ) and the following attributes:

[0038] 4.3.10.3 Attribute constraints

[0039] None.

[0040] 4.3.10.4 Notifications

[0041] The common notifications defined in subclause 4.5 are valid for this IOC, without exceptions or additions.

[0042] »»»»»»>End of excerpt from TS 28.541<<<<<<<<<<<<<<

[0043] There currently exist certain challenge(s). Fo example, it is unclear how the WAB node can be provisioned, as it moves across different areas and PLMNs.SUMMARY

[0044] According to the discussions so far, a WAB node will likely consist of a WAB- gNB and a WAB-MT (WAB-UE). The WAB-gNB part of an WAB node serves UEs, while the node uses its WAB-MT part to connect with a mobile network (the black BH-gNB in Fig. 1) and the WAB-MT’s PDU Session(s) provide IP connectivity for the WAB-gNB. In this architecture, the PDU session(s) established between the WAB-MT and the BH-UPF (see Fig. 1) are used to provide IP connectivity for NGAP and XnAP connections of the WAB-gNB, as well as its connectivity to the 0AM. The WAB-gNB may connect to the same AMF as the WAB-MT, or it may connect to other AMF(s).

[0045] According to the WAB architecture, the NG connection between the WAB node and the core network (CN) will be carried via the wireless backhaul link between the WAB- MT and the BH-gNB. Since the WAB node may move across large areas, and even roam to other PLMNs, at some point, it will likely be needed for the WAB node to establish an NG connection towards a (new, local) CN. In that respect, a WAB node needs to be provisioned with certain configuration parameters, e.g. (non-limiting example):• The parameters needed for the WAB node to select new CN and new CN nodes (e.g., AMF) to connect to.• The parameters needed for connection establishment towards these new AMF and CN nodes.• The configuration parameters that are necessary for the WAB node to serve UEs in its new area / location.• In case the WAB node is roaming to another PLMN, the parameters needed for the WAB node to select the new PLMN and the above parameters pertaining to the new PLMN.

[0046] As of today, it is unclear how the WAB node can be provisioned, as it moves across different areas and PLMNs, with the above parameters. Note that the problem is further exacerbated by the fact that the trajectory of WAB nodes may be random, and that the nodes may even roam to different PLMN.

[0047] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. The WAB node indicates its location to the 0AM and 0AM provides the necessary parameters or another layered 0AM which can support the provision of parameters needed by the WAB node. The invention proposes a set of methods for a WAB node that moves and enters a new region / PLMN / area, to obtain the configurationparameters needed for connecting to the CN in the new area and the configuration parameters that are necessary for the WAB node to serve UEs.

[0048] Certain embodiments may provide one or more of the following technical advantage(s). The proposed disclosure ensures that a WAB node is correctly configured as it moves, that it can connect to a new AMF and CN when needed, and that its configuration is updated with appropriate parameters when needed.

[0049] According to one aspect of the present disclosure, a method implemented by a radio access node, RAN, node that is configured to communicate at least via a wireless backhaul is provided. The RAN node indicates location information to an operations, administration and maintenance, 0AM, system. The RAN node receives a RAN node configuration that is based on the location information. At least one action is performed based on the RAN node configuration.

[0050] According to one or more embodiments of this aspect, the location information comprises one or more of: geographical coordinates associated with the RAN node; information, for the RAN node, associated with a global navigation system; and at least one parameter associated with a mobile terminated, MT, function of the RAN node.

[0051] According to one or more embodiments of this aspect, the at least one parameter comprises at least one of: a serving cell identifier, ID, associated with the MT function of the RAN node; a serving network node ID associated with the MT function of the RAN node; a tracking area code, TAC; and a serving public land mobile network, PLMN, associated with the MT function of the RAN node.

[0052] According to one or more embodiments of this aspect, the RAN node determines to obtain the RAN node configuration based on one or both of a pre-configuration and at least one trigger.

[0053] According to one or more embodiments of this aspect, the pre-configuration or at least one trigger comprise an indication of one or more of: a physical location of the RAN node; an elapsed time since the RAN node’s reception of a previous configuration; a time; a data delay on interface connections; a trigger event; a roaming event; reaching one or more waypoints on a preconfigured path; a cell identifier, ID, associated with a first connection; a tracking area code, TAC, associated with a second connection; a network node-ID associated with a third connection; and a public land mobile network, PLMN, associated with a fourth connection.

[0054] According to one or more embodiments of this aspect, the at least one action comprising one or more of: selecting a core network node to establish connections with;establishing interfaces with at least one core network node; communicating with the OAM system; serving at least one user equipment; and selecting a public land mobile network, PLMN.

[0055] According to one or more embodiments of this aspect, the OAM system inquires whether a new RAN node configuration is required; and the new RAN node configuration comprising to the RAN configuration that was received.

[0056] According to one or more embodiments of this aspect, the RAN node comprises: a mobile terminated, MT, portion; and a node B portion.

[0057] According to one or more embodiments of this aspect, the MT portion and the node portion of the RAN node are one of: connected to a same network during non-roaming; connected to different networks; or connected to a same network during roaming.

[0058] According to another aspect of the present disclosure, a radio access node, RAN, node that is configured to communicate at least via a wireless backhaul is provided. The RAN node is configured to: indicate location information to an operations, administration and maintenance, OAM, system; receive a RAN node configuration that is based on the location information; and perform at least one action based on the RAN node configuration.

[0059] According to one or more embodiments of this aspect, the location information comprises one or more of: geographical coordinates associated with the RAN node; information, for the RAN node, associated with a global navigation system; and at least one parameter associated with a mobile terminated, MT, function of the RAN node.

[0060] According to one or more embodiments of this aspect, the at least one parameter comprises at least one of: a serving cell identifier, ID, associated with the MT function of the RAN node; a serving network node ID associated with the MT function of the RAN node; a tracking area code, TAC; and a serving public land mobile network, PLMN, associated with the MT function of the RAN node.

[0061] According to one or more embodiments of this aspect, the RAN node is further configured to determine to obtain the RAN node configuration based on one or both of a pre-configuration and at least one trigger.

[0062] According to one or more embodiments of this aspect, the pre-configuration or at least one trigger comprise an indication of one or more of: a physical location of the RAN node; an elapsed time since the RAN node’s reception of a previous configuration; a time; a data delay on interface connections; a trigger event; a roaming event; reaching one or more waypoints on a preconfigured path; a cell identifier, ID, associated with a first connection; a tracking area code, TAC, associated with a second connection; a network node-IDassociated with a third connection; and a public land mobile network, PLMN, associated with a fourth connection.

[0063] According to one or more embodiments of this aspect, the at least one action comprising one or more of: selecting a core network node to establish connections with; establishing interfaces with at least one core network node; communicating with the 0AM system; serving at least one user equipment; and selecting a public land mobile network, PLMN.

[0064] According to one or more embodiments of this aspect, the RAN node is further configured to inquire the 0AM system whether a new RAN node configuration is required; and the new RAN node configuration comprising to the RAN configuration that was received.

[0065] According to one or more embodiments of this aspect, the RAN node comprises: a mobile terminated, MT, portion; and a node B portion.

[0066] According to one or more embodiments of this aspect, the MT portion and the node portion of the RAN node are one of: connected to a same network during non-roaming; connected to different networks; or connected to a same network during roaming.

[0067] According to another aspect of the present disclosure, a method implemented by an operations, administration and maintenance, 0AM, system that is configured to communicate with a radio access node, RAN, node via wireless backhaul communications is provided. The RAN node receives location information. A RAN node configuration is generated based on the location information. The RAN node transmits the RAN node configuration to configure the RAN node to perform at least one action.

[0068] According to one or more embodiments of this aspect, the location information comprises one or more of: geographical coordinates associated with the RAN node; information, for the RAN node, associated with a global navigation system; and at least one parameter associated with a mobile terminated, MT, function of the RAN node.

[0069] According to one or more embodiments of this aspect, the at least one parameter comprises at least one of: a serving cell identifier, ID, associated with the MT function of the RAN node; a serving network node ID associated with the MT function of the RAN node; a tracking area code, TAC; and a serving public land mobile network, PLMN, associated with the MT function of the RAN node.

[0070] According to one or more embodiments of this aspect, the at least one action comprising one or more of: selecting a core network node to establish connections with; establishing interfaces with at least one core network node; communicating with anoperations, administration and maintenance, OAM, system; serving at least one user equipment; and selecting a public land mobile network, PLMN.

[0071] According to one or more embodiments of this aspect, a determination is performed whether a new RAN node configuration is required by the RAN node based on the location information; and the generating of the RAN node configuration is in response to the determination that the RAN node requires the new RAN node configuration

[0072] According to one or more embodiments of this aspect, an inquiry is received from the RAN node as to whether a new RAN node configuration is required by the RAN node, the generating of the RAN node configuration being based on the inquiry.

[0073] According to another aspect of the present disclosure, an operations, administration and maintenance, OAM, system that is configured to communicate with a radio access node, RAN, node via wireless backhaul communications, the OAM system configured to: receive, from the RAN node, location information; generate a RAN node configuration based on the location information; and transmit, to the RAN node, the RAN node configuration to configure the RAN node to perform at least one action.

[0074] According to one or more embodiments of this aspect, the location information comprises one or more of: geographical coordinates associated with the RAN node; information, for the RAN node, associated with a global navigation system; and at least one parameter associated with a mobile terminated, MT, function of the RAN node.

[0075] According to one or more embodiments of this aspect, the at least one parameter comprises at least one of: a serving cell identifier, ID, associated with the MT function of the RAN node; a serving network node ID associated with the MT function of the RAN node; a tracking area code, TAC; and a serving public land mobile network, PLMN, associated with the MT function of the RAN node.

[0076] According to one or more embodiments of this aspect, the at least one action comprising one or more of: select a core network node to establish connections with; establish interfaces with at least one core network node; communicate with an operations, administration and maintenance, OAM, system; serve at least one user equipment; and select a public land mobile network, PLMN.

[0077] According to one or more embodiments of this aspect, the OAM system is further configured to determine whether a new RAN node configuration is required by the RAN node based on the location information; and the generating of the RAN node configuration is in response to the determination that the RAN node requires the new RAN node configuration

[0078] According to one or more embodiments of this aspect, the 0AM system is further configured to receive an inquiry, from the RAN node, as to whether a new RAN node configuration is required by the RAN node, where the generating of the RAN node configuration is based on the inquiry.BRIEF DESCRIPTION OF THE DRAWINGS

[0079] 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:

[0080] FIGURE 1 is a block diagram of a potential example WAB architecture;

[0081] FIGURE 2 is a flow chart of an example method for sending configuration information according to some embodiments of the present disclosure;

[0082] FIGURE 3 is a flow chart of an example method implemented by a RAN node according to some embodiments of the present disclosure;

[0083] FIGURE 4 is a flow chart of an example method implemented by an 0AM system according to some embodiments of the present disclosure;

[0084] FIGURE 5 is a flow chart of another example method for sending configuration information according to some embodiments of the present disclosure;

[0085] FIGURE 6 is is a flow chart of an example method for a roaming scenario according to some embodiments of the present disclosure;

[0086] FIGURE 7 is a block diagram of an example communication system according to some embodiments of the present disclosure;

[0087] FIGURE 8 is a block diagram of an example UE according to some embodiments of the present disclosure;

[0088] FIGURE 9 is a block diagram of a network node according to some embodiments of the present disclosure; and

[0089] FIGURE 10 is a block diagram of a virtualization environment according to some embodiments of the present disclosure.DETAILED DESCRIPTION

[0090] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0091] Disclaimers

[0092] The proposed solution is presented on a non-limiting example of WAB nodes, but it applies to any kind of moving RAN node.

[0093] The terms “NGAP connection” and “NG-C interface instance” are used interchangeably.

[0094] The terms “new AMF” and “target AMF” are used interchangeably.

[0095] The terms “CN nodes”, “core network nodes” and “CN functions” are used interchangeably without losing the meaning, and they may refer to one or more of the following: AMF, UPF, SMF, or any other 5GC node / function.

[0096] The procedures used in the solution may be class- 1 or class-2 procedures, they may be new procedures or enhancements of existing procedures.

[0097] The expressions “X served by Y” or “X is connected to Y” mean that there is a logical interface connection between network nodes X and Y. In case X is a UE, this means that node X and the RAN node serving the UE have a logical connection associated to this UE.

[0098] Unless stated otherwise, the WAB-MT and the WAB-gNB are co-located, i.e., they are a part of the same WAB node.

[0099] The proposed solution may apply to both single- and dual-connected WAB nodes.

[0100] The solution applies to both the case when all UEs connected to the WAB-gNB are served by the same AMF, and the case where multiple AMFs serve these UEs. The solution also applies to the case where the WAB-gNB has an NGAP connection with the AMF serving the WAB-MT, and when it does not.

[0101] The term “different core network” may refer to a core network of another PLMN, or it may apply to different part of a core network of the same PLMN (e.g., a different AMF or set of AMFs).

[0102] The proposed solution applies to NR as well as future RATs such as beyond 3GPP Rel-18.

[0103] The terms “0AM” and “0AM system” are used interchangeably.

[0104] The scenario of interest

[0105] In the scenario of interest, the WAB node is moving, and it enters or approaches a new area, or enters a new PLMN. At this point, the WAB-node should set up an NG interface with a new AMF. From this point onwards, the WAB node needs to be provisioned with the appropriate configuration parameters.

[0106] Solution description

[0107] One or more questions addressed by the solutions are as follows:

[0108] When WAB is moving, how does it set up SCTP association and NGAP connection to a new AMF and CN? How does the WAB get the “contact details” of the new AMF for NGAP connection setup?

[0109] How to populate the NGAP SETUP REQUEST with the appropriate information (e.g., supported TAs)? As of today, for static gNBs, the location of the gNB is known and these parameters are preconfigured at the gNB.

[0110] What is a trigger for setting up new a NG connection?

[0111] Parameters to be configured at the gNB / WAB-gNB (e.g., RAN node)

[0112] Specification TS 28.541 defines the parameters that can be configured by the0AM to various network nodes. In the context of the present invention, the configuration parameters obtained by the WAB node may include the applicable parameters from TS 28.541, as well as additional parameters that enable it to establish interfaces towards different network nodes, to enable it to serve UEs and to perform additional functionalities. Some (non-limiting) examples:

[0113] The parameters needed for the WAB node to select new CN and new CN nodes (e.g., AMF) to connect to.

[0114] The parameters that enable the WAB node to establish interfaces towards different network nodes (e.g., the CN nodes), e.g., the IP addresses of these network nodes, the addresses of relevant servers, the parameters needed to set up SCTP associations, CN node IDs (e.g., GUAMIs of the AMF, AMF Region ID, AMF set ID, AMF pointer as defined in TS 24.501 vl7.4.0)) etc.

[0115] The parameters that enable the RAN node to connect to and communicate with the 0AM system.

[0116] The configuration parameters that are necessary for the WAB node to serve UEs in its new area / location, for example:

[0117] The TAC(s), the cell ID(s), the PLMN ID(s) that the WAB-gNB should broadcast.

[0118] Some parameters can be to avoid interference and collision such as RACH configuration, PCI configuration, Time division duplex (TDD) pattern configurations.

[0119] Some parameters are related to tracking area code, Radio network area code configurations.

[0120] Some configurations can be transmission power for the coverage reach purposes.

[0121] In case the WAB node is roaming to another PLMN, the parameters needed for the WAB node to select the new PLMN and the above parameters pertaining to the new PLMN.

[0122] The messages used for communication can be the existing or enhanced messages defined in TS 28.532 vl8.0.0, or a newly defined messages to be included in this specification. Some non-limiting examples are "createMOI" and "changeMOI" messages defined therein.

[0123] The above parameters are referred herein as the WAB configuration.

[0124] Solution 1: Solution for the scenario when the WAB-gNB and the WAB- MT are connected to the same network

[0125] This solution pertains to the case when the WAB-gNB and the WAB -MT are connected to the same network (e.g., a home or visited network).

[0126] Step 1: In this solution, the WAB node indicates certain information to the 0AM, based on which the 0AM sends to the WAB node (e.g., via a PDU session of the WAB-MT) the WAB configuration.

[0127] In some embodiments, the WAB indicates to the 0AM the information about its location, for example, one or more of the following (herein referred to as the WAB location information):• WAB node’s geographical coordinates. o For example, the WAB-gNB may obtain the location information from one of the global navigation systems. o Alternatively, the WAB-gNB may acquire this info from the WAB-MT, which can then pass it to the WAB-gNB. For example:The WAB-MT may obtain the information from one of the global navigation systems.The WAB-MT may inquire the network to tell the WAB-MT the WAB-MT’ s location. For example, the MO-LR location request defined in TS 23.273 can be used.• One or more parameters related to the co-located WAB-MT: o Serving cell ID. o Serving gNB ID. o TAC.o Serving PLMN.

[0128] Step 2: Upon receiving the above information from the WAB-gNB, the 0AM sends the suitable configuration information to the WAB node, for example, by using the "notifyMOIAttributeValueChanges" and "notifyMOIChanges" notifications as specified in TS 28.532, possibly with enhancements or by introducing a new notification.

[0129] FIGURE 2 illustrates an example method for sending configuration information when the WAB-gNB and the WAB-MT are connected to the same network (e.g., PLMN), according to certain embodiments. As illustrated, the method includes two depicted steps, which are described in more detail above. It is recognized that the illustrated method includes steps performed by different entities (e.g., WAB node, 0AM, WAB-gNB, AMF, WAB-MT, etc.), and, thus, the methods performed by these entities individually may include fewer, more, and / or different steps than those illustrated. A WAB node is configured to indicates (Block S100) information to an 0AM. The 0AM is configured to send (Block S102) the WAB configuration to the WAB node.

[0130] FIGURE 3 is a flowchart of an example method implemented by a RAN node (e.g., WAB node) according to some embodiments of the present disclosure. The RAN node is configured to indicate (Block S104), by the RAN node, location information to an operations, administration and maintenance, 0AM, system, as described herein. The RAN node is configured to receive (Block S106), by the RAN node, a RAN node configuration that is based on the location information, as described herein. The RAN node is configured to perform (Block S108) at least one action based on the RAN node configuration, as described herein.

[0131] According to one or more embodiments, the location information comprises one or more of: geographical coordinates associated with the RAN node, information, for the RAN node, associated with a global navigation system, and at least one parameter associated with a mobile terminated, MT, function of the RAN node.

[0132] According to one or more embodiments, the at least one parameter comprises at least one of: a serving cell identifier, ID, associated with the MT function of the RAN node; a serving network node ID associated with the MT function of the RAN node; a tracking area code, TAC; and a serving public land mobile network, PLMN, associated with the MT function of the RAN node.

[0133] According to one or more embodiments, the RAN node is further configured to determine to obtain the RAN node configuration based on one or both of a pre-configuration and at least one trigger.

[0134] According to one or more embodiments, the pre-configuration or at least one trigger comprise an indication of one or more of: a physical location of the RAN node; an elapsed time since the RAN node’s reception of a previous configuration; a time; a data delay on interface connections; a trigger event; a roaming event; reaching one or more waypoints on a preconfigured path; a cell identifier, ID, associated with a first connection; a tracking area code, TAC, associated with a second connection; a network node-ID associated with a third connection; and a public land mobile network, PLMN, associated with a fourth connection.

[0135] According to one or more embodiments, the at least one action comprising one or more of: selecting a core network node to establish connections with; establishing interfaces with at least one core network node; communicating with the 0AM system; serving at least one user equipment; and selecting a public land mobile network, PLMN.

[0136] According to one or more embodiments, the RAN node is further configured to inquire the 0AM system whether a new RAN node configuration is required; and the new RAN node configuration comprising to the RAN configuration that was received.

[0137] According to one or more embodiments, the RAN node comprises: a mobile terminated, MT, portion; and a node B portion.

[0138] According to one or more embodiments, the MT portion and the node portion of the RAN node are one of: connected to a same network during non-roaming; connected to different networks; or connected to a same network during roaming.

[0139] FIGURE 4 is a flowchart of an example method implemented by an 0AM system according to some embodiments of the present disclosure. The 0AM system is configured to receive (Block S 110), from the RAN node, location information, as described herein. The 0AM system is configured to generate (Block S 112) a RAN node configuration based on the location information, as described herein. The 0AM system is configured to transmit (Block S 114), to the RAN node, the RAN node configuration to configure the RAN node to perform at least one action, as described herein.

[0140] According to one or more embodiments, the location information comprises one or more of: geographical coordinates associated with the RAN node; information, for the RAN node, associated with a global navigation system; and at least one parameter associated with a mobile terminated, MT, function of the RAN node.

[0141] According to one or more embodiments, the at least one parameter comprises at least one of: a serving cell identifier, ID, associated with the MT function of the RAN node; a serving network node ID associated with the MT function of the RAN node; a trackingarea code, TAC; and a serving public land mobile network, PLMN, associated with the MT function of the RAN node.

[0142] According to one or more embodiments, the at least one action comprising one or more of: select a core network node to establish connections with; establish interfaces with at least one core network node; communicate with an operations, administration and maintenance, 0AM, system; serve at least one user equipment; and select a public land mobile network, PLMN.

[0143] According to one or more embodiments, the 0AM system is further configured to determine whether a new RAN node configuration is required by the RAN node based on the location information, and the generating of the RAN node configuration is in response to the determination that the RAN node requires the new RAN node configuration

[0144] According to one or more embodiments, the 0AM system is further configured to receive an inquiry, from the RAN node, as to whether a new RAN node configuration is required by the RAN node, where the generating of the RAN node configuration is based on the inquiry.Solutions for roaming scenarios

[0145] The term “roaming scenario” means that a WAB node has physically moved outside of the coverage of its home PLMN (HPLMN), and that, either the WAB-MT, or both the WAB-gNB and the WAB-MT, are connected to a network different than their home network (the VPLMN). Several solutions for roaming scenarios are proposed, where the roaming can be to a network inside the same country (i.e., national) or to a network in a different country (i.e., international).

[0146] Solution 2-1

[0147] In this solution, the WAB-MT is registered in, and connected to, a VPLMN. The WAB-gNB remains connected to the HPLMN, by using an IP tunnel provided by the PDU sessions of the WAB-MT. The steps can be described as follows (any step can be optional):1) Step 1: Based on pre-configuration, or on some trigger (as described herein), the WAB node determines that it should fetch a new WAB configuration (as described herein).2) Step 2: The WAB node can indicate the WAB location information to the OAM (as defined and / or described herein) and can (Step 3) request a new WAB configuration. a) In some embodiments, the request may be a check of whether a new WAB configuration is needed, and it is up to OAM to decide whether this is the case and indicate to the WAB node.) The OAM replies to the WAB node. a) Step 3: Based on the reported WAB location information, the OAM can send the WAB configuration to the WAB node. The configuration parameters may include one or more of the information as described herein, e.g. (non-limiting examples), the TAC, cell ID and PLMNs that the WAB-gNB should broadcast. i) Alternatively, the OAM may update only some of the parameters, or, in some cases, none of them (and indicate that the current configuration can continue to be used). b) Step 5: If needed, the OAM can also send the parameters needed to establish an NG connection to a new AMF and connections to other CN nodes (e.g., the IP addresses, parameters needed for setting up SCTP associations, CN node IDs (e.g., GUAMIs of the AMF, AMF Region ID, AMF set ID, AMF pointer as defined in TS 24.501 vl7.4.0)) Herein, we referred to these parameters as “contact details”. It is also possible to group multiple AMFs which are operating in a pool (AMF pool) and provide the preconfiguration for AMFs in pool rather than for a single AMF. In such case, WAB node may connect to any one of the AMFs from the pool. i) Alternatively, if there is no need to change the connection towards the AMF and CN nodes, the connections towards the current AMF(s) and / or CN nodes can continue to be used. c) Step 6: In some embodiments, the OAM can also send the indication of validity of WAB configuration, which stipulates the under which the configuration is valid or when its validity expires. i) The validity indication can include one or more of the following (non-limiting examples):(1) Time duration of validity of the WAB configuration, or time of seizure of validity.(2) An indication of area in which the WAB configuration is valid, expressed in e.g., geocoordinates, list of cells, TAs, PLMNs, AMFs, AMF sets to which the WAB-gNB and / or WAB -MT connects to.(3) Any of the criteria (e.g., conditions) described herein. d) Step 7: In some embodiments, the OAM can indicate to the WAB contact details of another OAM, which oversees the present region, or is a part of the VPLMN. Then, the WAB-gNB should contact the said another OAM, to fetch the configurations.e) In some embodiments, only some of the constituents of the WAB configuration may change, while some others may keep their previous values. i) For example, in some cases, the WAB-gNB may be instructed to connect to another AMF, but without OAM updating cell TAC / cell ID. In this case, for the sake of AMF change, the OAM would only indicate the “contact details” of the new AMF to the WAB-gNB, and, optionally indication of validity etc. f) In some embodiments, the action of OAM node can be performed by another Network Function such as Network repository function (NRF) or OAM node can send request to NRF which can perform the discovery of the suitable AMF. ) Depending on the received new WAB configuration, and its content: a) Step 8: If the WAB-gNB is to continue being connected to the current AMF and / or CN nodes, the WAB-gNB needs to inform these node(s) about any updated configuration parameters. i) For example, if the current AMFs will continue to be used, an NGAP RAN CONFIGURATION UPDATE is sent to the AMF(s) with the updated information, e.g., the supported PLMNs, TAC, etc. b) Step 9: If the WAB-gNB is to connect to new AMF(s), based on the received WAB configuration, the WAB-gNB establishes the connections to these CN nodes and indicates to them the necessary parameters from the WAB configuration. i) For example, the NG connection (e.g., establish the SCTP associations and set up the NGAP connection) towards the new AMF is established. c) For some parameters, the AMF and / or CN nodes may need to indicate some of these new / updates WAB configuration parameters to other nodes. i) For example, the new / current AMF needs to propagate the new / updated info about the TAC, cell ID and PLMN to other CN nodes / functions. For example, the AMF should indicate to the NRF that the WAB-gNB supports one or more new TACs. d) The WAB node may connect to a new PLMN, the OAM and CN nodes therein.) Step 10: In some embodiments, if the WAB-gNB is to connect to new CN nodes, the WAB-gNB can remove the connections towards the “old” CN nodes. a) For example, NGAP removal towards one or more AMFs can be done. ) Step 11: In some embodiments, the change of some WAB configuration parameters requires also handling of this change that impact the UEs (e.g., handover).7) If the WAB-MT, later, roams into yet another network other than its HPLMN, the solution described herein applies is well, and it also applies to all subsequent VPLMNs.

[0148] FIGURE 5 illustrates an example method for sending configuration information when the WAB-gNB and the WAB-MT are connected to the different PLMNS, according to certain embodiments. As illustrated, the method includes eleven depicted steps, which are described in more detail above. It is recognized that the illustrated method includes steps performed by different entities (e.g., WAB node, 0AM, WAB-gNB, AMF, WAB-MT, etc.), and, thus, the methods performed by these entities individually may include fewer, more, and / or different steps than those illustrated.

[0149] In particular, a WAB node is configured to determine (Block SI 16) to obtain a new WAB configuration based on at least one of a pre-configuration and a trigger. The WAB node is configured to indicate (Block SI 18) the WAB location information to the 0AM. The WAB node is configured to request (Block S 120) a new WAB configuration. The 0AM is configured to send (Block S122) the new WAB configuration to the WAB node. The 0AM is configured to send (Block S 124) one or more parameters associated with establishing one or more connections. The 0AM is configured to send (Block S126) a validity indication associated with the new WAB configuration.

[0150] The 0AM is configured to send (Block S128) an indication comprising contact details associate with a second 0AM. The WAB-gNB is configured to inform (Block S 130) one or more nodes about updated configuration parameters associated with the new WAB configuration. The WAB-gNB is configured to establish (Block S132) one or more connections based on the new WAB configuration. The WAB-gNB is configured to remove (Block S134) one or more previous connections. One or more UEs are informed (Block S136) of the new WAB configuration. The dashed or broken lines in FIGURE 5 may represent optional steps.

[0151] Solution 2-2

[0152] This solution pertains to the roaming scenario where the WAB-MT is registered at and connected to the VPLMN. Meanwhile, the WAB-gNB has connected to CN nodes in the same VPEMN. For example, the WAB-gNB has set up an NG connected to an AMF in the VPLMN. Hence, the WAB-gNB becomes a resource of the VPLMN and broadcasts a PLMN ID of the VPLMN. The steps can be described as follows (any step can be optional):1) The WAB-gNB contacts the OAM in its home PLMN (HPLMN) and indicates that it is, or is about to be, roaming into another PLMN (the VPLMN). This can be before orafter the WAB-MT has registered to and connected to the VPLMN. Alternatively, the OAM in HPLMN determines that the roaming is bound to happen a) This can be done by using the indication in Solution 2-1, or another indication.2) The OAM in the HPLMN (referred to as the H-OAM) indicates to the WAB-gNB the “contact details” of the OAM in the VPLMN (the V-OAM). This may be made possible by, e.g., inter-operator agreements. a) In some embodiments, the WAB-gNB communicates with the V-OAM directly (e.g., via a PDU session of the WAB-MT). In some embodiments, the WAB-gNB communicates with the V-OAM via the H-OAM, or via another network node.3) Further on, the steps from Solution 2-1 can be reused, with the appropriate adjustments. For example, one such adjustment is that the OAM that the WAB-gNB communicates with for fetching the configurations is the V-OAM. Another adjustment is that the AMF serving the WAB-gNB is in the VPLMN.

[0153] FIGURE 6 illustrates an example method for a roaming scenario where the WAB-MT is registered at and connected to the VPLMN and the WAB-gNB is connected to CN nodes in the VPLMN, according to certain embodiments. As illustrated, the method includes three depicted steps, which are described in more detail above. It is recognized that the illustrated method includes steps performed by different entities (e.g., WAB node, OAM, WAB-gNB, AMF, WAB-MT, etc.), and, thus, the methods performed by these entities individually may include fewer, more, and / or different steps than those illustrated.

[0154] In particular, with respect to FIGURE 6, the WAB-gNB is configured to contact (Block S138) an OAM associated with a PLMN. The WAB-gNB is configured to inform (Block S140) the OAM that the WAB-gNB is roaming into a second PLMN or is about to roam into the second PLMN. The OAM is configured to indicate (Block S142) the WAB- gNB one or more contact details for a second OAM associated with the second PLMN.

[0155] Solution 2-3

[0156] The UEs served by a WAB-gNB, e.g., in a roaming scenario, can have different home PLMNs. Each of these home PLMNs configured the UE subscription with different lists of preferred PLMNs to connect to in both home and roaming scenarios. Similarly, in the WAB-MT subscription data, the WAB-MT is configured which VPLMN is preferred list to select.

[0157] For the (onboard) UEs that do not have in the VPLMN, that the WAB node broadcasts and connects to, in their preferred PLMN list may lose connection (the WAB- gNB may also push certain UEs away to other PLMNs based on MRL, if such cell exists.The WAB-gNB may also push UE to RRC_IDLE mode and UE applies PLMN selection procedure as specified in TS 23.122). These different preferences are because onboard UEs may have SIM cards from different operators than the one owning the WAB node.• In case the WAB-gNB is currently in an isolated environment, e.g., onboard aircrafts, these UEs may not have any other network connects to choose from than the VPLMN where the WAB node is connected.• Otherwise, these UEs may have the possibility to connect to surrounding fixed PLMNs.

[0158] In the scenario of interest, the WAB-MT registers and connects to VPLMN-1, and the WAB-gNB may connect to an AMF in VPLMN-2 if this VPLMN-2 can continue to serve the most of the onboard UEs.

[0159] The steps of Solution 2-2 (i.e., the adjusted steps of Solution 2-1) apply here as well, with the difference that the H-OAM instructs the WAB-gNB to connect to V-OAM-2 in VPLMN-2.

[0160] Solution 3

[0161] In this solution, the WAB node is preconfigured with one or more WAB configurations to use, depending on location. Hence, depending on its own location, it activates the appropriate WAB configuration.

[0162] Triggers for fetching a new WAB configuration

[0163] These aspects applicable to all solutions proposed herein.

[0164] The WAB node can be configured that, upon fulfilment of certain conditions, it contacts the 0AM for fetching a new WAB configuration, as elaborated in the solutions herein. Upon receiving the request, the 0AM sends the configuration parameters to the WAB-gNB.

[0165] The conditions may include one or more of the following:• Physical location (e.g., expressed in geo-coordinates).• Time or time since the last configuration is received.• Data delay on interface connections (e.g.: SCTP delay, timeouts).• Trigger event.• Roaming (national or international).• The cell ID and / or the TAC and / or the gNB-ID, or the PLMN to which the WAB-MT connects.• Based upon (preconfigured / configured) flight or path planning, i.e., when certain way points (geographical coordinates) have been reached.

[0166] FIGURE 7 shows an example of a communication system 100 in accordance with some embodiments.

[0167] In the example, the communication system 100 includes a telecommunication network 102 that includes an access network 104, such as a radio access network (RAN), and a core network 106, which includes one or more core network nodes 108. The access network 104 includes one or more access network nodes, such as network nodes 110a and 110b (one or more of which may be generally referred to as network nodes 110), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network 102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 102 that supports an ORAN specification (e.g., a specification published by the O- 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 network 102, including one or more network nodes 110 and / or core network nodes 108.

[0168] Examples of an ORAN network node 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 O-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes 110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 112a, 112b, 112c, and 112d (one or more of which may be generally referred to as UEs 112) to the core network 106 over one or more wireless connections.

[0169] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0170] The UEs 112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 110 and other communication devices. Similarly, the network nodes 110 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 112 and / or with other network nodes or equipment in the telecommunication network 102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 102.

[0171] In the depicted example, the core network 106 connects the network nodes 110 to one or more hosts, such as host 116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 106 includes one more core network nodes (e.g., core network node 108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 108. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDE), UnifiedData Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0172] As a whole, the communication system 100 of FIGURE 7 enables connectivity between the UEs, network nodes, and other entities. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Fong Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0173] In some examples, the telecommunication network 102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 102. For example, the telecommunications network 102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.

[0174] In some examples, the UEs 112 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 104. Additionally, a UE may be configured for operating in single- or multi-RAT or multistandard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0175] In the example, the hub 114 communicates with the access network 104 to facilitate indirect communication between one or more UEs (e.g., UE 112c and / or 112d) and network nodes (e.g., network node 110b). In some examples, the hub 114 may be acontroller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 114 may be a broadband router enabling access to the core network 106 for the UEs. As another example, the hub 114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 110, or by executable code, script, process, or other instructions in the hub 114. As another example, the hub 114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0176] The hub 114 may have a constant / persistent or intermittent connection to the network node 110b. The hub 114 may also allow for a different communication scheme and / or schedule between the hub 114 and UEs (e.g., UE 112c and / or 112d), and between the hub 114 and the core network 106. In other examples, the hub 114 is connected to the core network 106 and / or one or more UEs via a wired connection. Moreover, the hub 114 may be configured to connect to an M2M service provider over the access network 104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 110 while still connected via the hub 114 via a wired or wireless connection. In some embodiments, the hub 114 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 110b. In other embodiments, the hub 114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 110b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0177] FIGURE 8 shows a UE 200 in accordance with some embodiments.

[0178] As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant(PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB- loT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0179] A UE may support device-to-device (D2D) communication, for example by implementing a 3 GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0180] The UE 200 includes processing circuitry 202 that is operatively coupled via a bus 204 to an input / output interface 206, a power source 208, a memory 210, a communication interface 212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in FIGURE 8. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0181] The processing circuitry 202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 210. The processing circuitry 202 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or anycombination of the above. For example, the processing circuitry 202 may include multiple central processing units (CPUs).

[0182] In the example, the input / output interface 206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 200. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0183] In some embodiments, the power source 208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 208 may further include power circuitry for delivering power from the power source 208 itself, and / or an external power source, to the various parts of the UE 200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 208 to make the power suitable for the respective components of the UE 200 to which power is supplied.

[0184] The memory 210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 210 includes one or more application programs 214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 216. The memory 210 may store, for use by the UE 200, any of a variety of various operating systems or combinations of operating systems.

[0185] The memory 210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 210 may allow the UE 200 to access instructions, application programs and the like, stored on transitory or non- transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 210, which may be or comprise a device-readable storage medium.

[0186] The processing circuitry 202 may be configured to communicate with an access network or other network using the communication interface 212. The communication interface 212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 222. The communication interface 212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 218 and / or a receiver 220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 218 and receiver 220 may be coupled to one or more antennas (e.g., antenna 222) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0187] In the illustrated embodiment, communication functions of the communication interface 212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access(CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / intemet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0188] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0189] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0190] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / orsoftware in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 200 shown in FIGURE 8.

[0191] As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0192] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’ s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0193] FIGURE 9 shows a network node 300 in accordance with some embodiments.

[0194] As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O- RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0195] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antennaas an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0196] Other examples of network nodes include multiple transmission point (multi- TRP) 5G access nodes, multi- standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi- cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0197] The network node 300 includes a processing circuitry 302, a memory 304, a communication interface 306, and a power source 308. The network node 300 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 300 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeB s. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 304 for different RATs) and some components may be reused (e.g., a same antenna 310 may be shared by different RATs). The network node 300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 300.

[0198] The processing circuitry 302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node 300 components, such as the memory 304, to provide network node 300 functionality.

[0199] In some embodiments, the processing circuitry 302 includes a system on a chip (SOC). In some embodiments, the processing circuitry 302 includes one or more of radio frequency (RF) transceiver circuitry 312 and baseband processing circuitry 314. In some embodiments, the radio frequency (RF) transceiver circuitry 312 and the baseband processing circuitry 314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 312 and baseband processing circuitry 314 may be on the same chip or set of chips, boards, or units.

[0200] The memory 304 may comprise any form of volatile or non-volatile computer- readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device- readable and / or computer- executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 302. The memory 304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 302 and utilized by the network node 300. The memory 304 may be used to store any calculations made by the processing circuitry 302 and / or any data received via the communication interface 306. In some embodiments, the processing circuitry 302 and memory 304 is integrated.

[0201] The communication interface 306 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface 306 comprises port(s) / terminal(s) 316 to send and receive data, for example to and from a network over a wired connection. The communication interface 306 also includes radio front-end circuitry 318 that may be coupled to, or in certain embodiments a part of, the antenna 310. Radio front-end circuitry 318 comprises filters 320 and amplifiers 322. The radio front-end circuitry 318 may be connected to an antenna 310 and processing circuitry 302. The radio front-end circuitry may be configured to condition signals communicated between antenna 310 and processing circuitry 302. The radio frontend circuitry 318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using acombination of filters 320 and / or amplifiers 322. The radio signal may then be transmitted via the antenna 310. Similarly, when receiving data, the antenna 310 may collect radio signals which are then converted into digital data by the radio front-end circuitry 318. The digital data may be passed to the processing circuitry 302. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0202] In certain alternative embodiments, the network node 300 does not include separate radio front-end circuitry 318, instead, the processing circuitry 302 includes radio front-end circuitry and is connected to the antenna 310. Similarly, in some embodiments, all or some of the RF transceiver circuitry 312 is part of the communication interface 306. In still other embodiments, the communication interface 306 includes one or more ports or terminals 316, the radio front-end circuitry 318, and the RF transceiver circuitry 312, as part of a radio unit (not shown), and the communication interface 306 communicates with the baseband processing circuitry 314, which is part of a digital unit (not shown).

[0203] The antenna 310 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 310 may be coupled to the radio front-end circuitry 318 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 310 is separate from the network node 300 and connectable to the network node 300 through an interface or port.

[0204] The antenna 310, communication interface 306, and / or the processing circuitry 302 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 310, the communication interface 306, and / or the processing circuitry 302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0205] The power source 308 provides power to the various components of network node 300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 300 with power for performing the functionality described herein. For example, thenetwork node 300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 308. As a further example, the power source 308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0206] Embodiments of the network node 300 may include additional components beyond those shown in FIGURE 9 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 300 may include user interface equipment to allow input of information into the network node 300 and to allow output of information from the network node 300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 300.

[0207] FIGURE 10 is a block diagram illustrating a virtualization environment 500 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.

[0208] 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 500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, etc. 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 500 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface.

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

[0210] Hardware 504 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 506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 508a and 508b (one or more of which may be generally referred to as VMs 508), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 506 may present a virtual operating platform that appears like networking hardware to the VMs 508.

[0211] The VMs 508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 506. Different embodiments of the instance of a virtual appliance 502 may be implemented on one or more of VMs 508, 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.

[0212] In the context of NFV, a VM 508 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 508, and that part of hardware 504 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 508 on top of the hardware 504 and corresponds to the application 502.

[0213] Hardware 504 may be implemented in a standalone network node with generic or specific components. Hardware 504 may implement some functions via virtualization. Alternatively, hardware 504 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 510, which, among others, oversees lifecycle management of applications 502. In some embodiments, hardware 504 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 512 which may alternatively be used for communication between hardware nodes and radio units.

[0214] Some Examples

[0215] Group A Examples

[0216] Al. A method performed by a user equipment for dynamic configuration of RAN nodes with wireless backhaul, the method comprising:- any of the user equipment steps, features, or functions described above, either alone or in combination with other steps, features, or functions described above.

[0217] A2. The method of the previous example, further comprising one or more additional user equipment steps, features, or functions described above.

[0218] A3. The method of any of the previous examples, further comprising: providing user data; and forwarding the user data to a host via the transmission to the network node.

[0219] Group B Examples

[0220] B l. A method performed by a network node for dynamic configuration of RAN nodes with wireless backhaul, the method comprising:- any of the network node steps, features, or functions described above, either alone or in combination with other steps, features, or functions described above.

[0221] B2. The method of the previous example, further comprising one or more additional network node steps, features, or functions described above

[0222] B3. The method of any of the previous examples, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment.

[0223] Group C Examples

[0224] Cl. A method performed for dynamic configuration of RAN nodes with wireless backhaul, the method comprising: indicating, by a WAB node, information to an 0AM; and sending, by the 0AM, the WAB configuration to the WAB node.

[0225] C2. The method of the previous example, wherein the information comprises location information.

[0226] C3. The method of any of the previous examples, wherein the information comprises at least one of: geographical coordinates associated with the WAB node;location information for the WAB node associated with a global navigation system; and one or more parameters associated with a WAB-MT.

[0227] C4. The method of any of the previous examples, further comprising: receiving, at a WAB-MT, location information associated with the WAB node; and sending, from the WAB-MT, the location information to the WAB node.

[0228] C5. The method of any of the previous examples, wherein the one or more parameters comprise at least one of: a serving cell ID associated with the WAB-MT; a serving gNB ID associated with the WAB-MT; a TAC; and a serving PLMN associated with the WAB-MT.

[0229] C6. A method performed for dynamic configuration of RAN nodes with wireless backhaul, the method comprising: determining, by a WAB Node, to obtain a new WAB configuration based on at least one of a pre-configuration and a trigger; indicating, by the WAB node, WAB location information to an 0AM; requesting, by the WAB node, a new WAB configuration; and sending the new WAB configuration to the WAB node.

[0230] C7. The method of the previous example, further comprising: sending, by the 0AM, one or more parameters associated with establishing one or more connections.

[0231] C8. The method of any of the previous examples, further comprising: sending, by the 0AM, a validity indication associated with the new WAB configuration.

[0232] C9. The method of any of the previous examples, further comprising:

[0233] sending, by the 0AM, an indication comprising contact details associated with a second 0AM.

[0234] CIO. The method of any of the previous examples, further comprising: informing, by a WAB-gNB, one or more nodes about updated configuration parameters associated with the new WAB configuration.

[0235] Cl 1. The method of any of the previous examples, further comprising: establishing, by the WAB-gNB, one or more connections based on the new WAB configuration.31

[0236] C12. The method of any of the previous examples, further comprising: removing, by the WAB-gNB, one or more previous connections.

[0237] C13. The method of any of the previous examples, further comprising: informing one or more UEs of the new WAB configuration.

[0238] C14. The method of any of the previous examples, wherein the preconfiguration and / or the trigger comprise at least one of: a physical location; an elapsed time since reception of a previous configuration; a time; a data delay on interface connections; a trigger event; a roaming event; reaching one or more waypoints on a preconfigured path; a cell ID associated with a first connection; a TAC associated with a second connection; a gNB-ID associated with a third connection; and a PLMN associated with a fourth connection.

[0239] C15. The method of any of the previous examples, wherein the new WAB configuration comprises at least one of: a first set of parameters configured to enable the WAB node to select new CN and / or new CN nodes to establish connections with; a second set of parameters configured to enable the WAB node to establish interfaces with one or more CN nodes; a third set of parameters configured to enable the RAN node to connect and / or communicate with an 0AM system; a fourth set of parameters configured to enable the WAB node to serve one or more UEs; and a fifth set of parameters configured to enable the WAB node to select a new PLMN.

[0240] Cl 6. The method of any of the previous examples, further comprising: determining, by the 0AM, whether the WAB node requires a new WAB configuration.

[0241] C17. The method of any of the previous examples, wherein the validity indication comprises at least one of: a time duration of validity associated with the new WAB configuration;a time of validity seizure associated with the new WAB configuration; and an indication of a geographic area associated with validity of the new WAB configuration.

[0242] Cl 8. The method of any of the previous examples, further comprising: requesting, by the WAB node, the new WAB configuration from the second 0AM; and sending, by the second 0AM, the new WAB configuration to the WAB node.

[0243] Cl 9. The method of any of the previous examples, further comprising at least one of: sending, to an AMF, an NGAP RAN CONFIGURATION UPDATE associated with the new WAB configuration;

[0244] Group D Examples

[0245] DI. A method performed for dynamic configuration of RAN nodes with wireless backhaul, the method comprising: contacting, by the WAB-gNB, an 0AM associated with a PLMN; informing, by the WAB-gNB, the 0AM that the WAB-gNB is roaming into a second PLMN or is about to roam into the second PLMN; and indicating, by the 0AM, to the WAB-gNB one or more contact details for a second 0AM associated with the second PLMN.

[0246] D2. The method of any of the previous examples, further comprising: determining, by the 0AM, that the WAB-gNB is roaming into the second PLMN or is about to roam into the second PLMN.

[0247] D3. The method of any of the previous examples, further comprising: communicating, by the WAB-gNB, with the second 0AM based on the one or more contact details.

[0248] D4. The method of any of the previous examples, further comprising: communicating, by the WAB-gNB, with the second 0AM via the first 0AM.

[0249] Group E Examples

[0250] EL A user equipment for dynamic configuration of RAN nodes with wireless backhaul, comprising: processing circuitry configured to perform any of the steps of any of the Group A and C examples; and power supply circuitry configured to supply power to the processing circuitry.

[0251] E2. A network node for dynamic configuration of RAN nodes with wireless backhaul, the network node comprising: processing circuitry configured to perform any of the steps of any of the Group B, C, and D examples; power supply circuitry configured to supply power to the processing circuitry.

[0252] E3. A user equipment (UE) for dynamic configuration of RAN nodes with wireless backhaul, the UE comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the Group A and C examples; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.

[0253] E4. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B, C, and D examples to transmit the user data from the host to the UE.

[0254] E5. The host of the previous example, wherein: the processing circuitry of the host is configured to execute a host application that provides the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application to receive the transmission of user data from the host.

[0255] E6. A method implemented in a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the network node performs any of the operations of any of the Group B, C, and D examples to transmit the user data from the host to the UE.

[0256] E7. The method of the previous example, further comprising, at the network node, transmitting the user data provided by the host for the UE.

[0257] E8. The method of any of the previous 2 examples, wherein the user data is provided at the host by executing a host application that interacts with a client application executing on the UE, the client application being associated with the host application.

[0258] E9. A communication system configured to provide an over-the-top (OTT) service, the communication system comprising: a host comprising: processing circuitry configured to provide user data for a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B, C, and D examples to transmit the user data from the host to the UE.

[0259] E10. The communication system of the previous example, further comprising: the network node; and / or the UE.

[0260] ABBREVIATIONS

[0261] At least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s).

[0262] Abbreviation Explanation

[0263] 3GPP 3rd Generation Partnership Project

[0264] 5G 5th Generation

[0265] 5GCN 5G Core Network

[0266] 5GS 5G System

[0267] 6G 6th Generation

[0268] ABS Almost Blank Subframe

[0269] AF Application Function

[0270] AMF Access and Mobility Management Function

[0271] AN Access Network

[0272] API Application Programming Interface

[0273] ARQ Automatic Repeat Request

[0274] AS Access Stratum

[0275] ASN.l Abstract Syntax Notation One

[0276] AWGN Additive White Gaussian Noise

[0277] BCH Broadcast Channel

[0278] BCCH Broadcast Control Channel

[0279] BH Backhaul

[0280] CA Certificate Authority

[0281] CC Carrier Component

[0282] CCCH SDU Common Control Channel SDU

[0283] CDMA Code Division Multiplexing Access

[0284] CE Control Element

[0285] CGI Cell Global Identity

[0286] CIR Channel Impulse Response

[0287] CN Core Network

[0288] CP Control Plane

[0289] CPICH Common Pilot Channel

[0290] CPICH Ec / No CPICH Received energy per chip divided by the power density inband

[0291] CQI Channel Quality information

[0292] C-RNTI Cell RNTI

[0293] CSI Channel State Information

[0294] CU Central Unit

[0295] DC Dual Connectivity

[0296] DCCH Dedicated Control Channel

[0297] DHCP Dynamic Host Configuration Protocol

[0298] DL Downlink

[0299] DM Demodulation

[0300] DMRS Demodulation Reference Signal

[0301] DRB Data Radio Bearer

[0302] DRX Discontinuous Reception

[0303] DTX Discontinuous Transmission

[0304] DTCH Dedicated Traffic Channel

[0305] DU Distributed Unit

[0306] DUT Device Under Test

[0307] E-CID Enhanced Cell-ID (positioning method)

[0308] eMBMS evolved Multimedia Broadcast Multicast Services

[0309] E-SMLC Evolved-Serving Mobile Location Centre

[0310] ECGI Evolved CGI

[0311] eNB E-UTRAN NodeB

[0312] ePDCCH Enhanced Physical Downlink Control Channel

[0313] E-SMLC Evolved Serving Mobile Location Center

[0314] E-UTRA Evolved UTRA

[0315] E-UTRAN Evolved UTRAN

[0316] FDD Frequency Division Duplex

[0317] FFS For Further Study

[0318] FQDN Fully Qualified Domain Name

[0319] gNB Radio base station in NR

[0320] GNSS Global Navigation Satellite System

[0321] GPS Global Positioning System

[0322] HARQ Hybrid Automatic Repeat Request

[0323] HO Handover

[0324] HPLMN Home Public Land Mobile Network

[0325] HSPA High Speed Packet Access

[0326] HSS Home Subscriber Server

[0327] HRPD High Rate Packet Data

[0328] ID Identifier / Identity

[0329] IAB Integrated Access and Backhaul

[0330] IE Information Element

[0331] LOS Line of Sight

[0332] LPP LTE Positioning Protocol

[0333] LTE Long-Term Evolution

[0334] MAC Medium Access Control

[0335] MAC Message Authentication Code

[0336] MBSFN Multimedia Broadcast multicast service SingleFrequency Network

[0337] MBSFN ABS MBSFN Almost Blank Subframe

[0338] MCC Mobile Country Code

[0339] MCG Master Cell Group

[0340] MDT Minimization of Drive Tests

[0341] MIB Master Information Block

[0342] MME Mobility Management Entity

[0343] MN Master Node

[0344] MNC Mobile Network Code

[0345] MR-DC Multi-Radio Dual Connectivity

[0346] MSC Mobile Switching Center

[0347] MT Mobile Termination

[0348] NAS Non-Access Stratum

[0349] NEF Network Exposure Function

[0350] NG The interface between a gNB and an AMF

[0351] NGAP NG Application Protocol

[0352] NG-RAN NG Radio Access Network

[0353] NPDCCH Narrowband Physical Downlink Control Channel

[0354] NR New Radio

[0355] 0AM Operations, Administration and Maintenance

[0356] OCNG OFDMA Channel Noise Generator

[0357] OFDM Orthogonal Frequency Division Multiplexing

[0358] OFDMA Orthogonal Frequency Division Multiple Access

[0359] OSS Operations Support System

[0360] OTDOA Observed Time Difference of Arrival

[0361] O&M Operation and Maintenance

[0362] PBCH Physical Broadcast Channel

[0363] P-CCPCH Primary Common Control Physical Channel

[0364] PCell Primary Cell

[0365] PCF Policy Control Function

[0366] PCFICH Physical Control Format Indicator Channel

[0367] PDCCH Physical Downlink Control Channel

[0368] PDCP Packet Data Convergence Protocol

[0369] PDP Profile Delay Profile

[0370] PDSCH Physical Downlink Shared Channel

[0371] PDU Protocol Data Unit

[0372] PGW Packet Gateway

[0373] PHICH Physical Hybrid- ARQ Indicator Channel

[0374] PLMN Public Land Mobile Network

[0375] PMI Precoder Matrix Indicator

[0376] PRACH Physical Random Access Channel

[0377] PRS Positioning Reference Signal

[0378] PSS Primary Synchronization Signal

[0379] PTM Point to Multipoint

[0380] PTP Point to Point

[0381] PUCCH Physical Uplink Control Channel

[0382] PUSCH Physical Uplink Shared Channel

[0383] QAM Quadrature Amplitude Modulation

[0384] QCI QoS Class Identifier

[0385] QFI QoS Flow Identifier

[0386] QoS Quality of Service

[0387] RA Registration Authority

[0388] RACH Random Access Channel

[0389] RAN Radio Access Network

[0390] RAT Radio Access Technology

[0391] RLC Radio Link Control

[0392] RLF Rdio Link Failure

[0393] RLM Radio Link Management

[0394] RNC Radio Network Controller

[0395] RNTI Radio Network Temporary Identifier

[0396] RRC Radio Resource Control

[0397] RRM Radio Resource Management

[0398] RS Reference Signal

[0399] RSCP Received Signal Code Power

[0400] RSRP Reference Signal Received Power

[0401] RSRQ Reference Signal Received Quality

[0402] RSTD Reference Signal Time Difference

[0403] RSSI Received Signal Strength Indicator

[0404] SCH Synchronization Channel

[0405] SCell Secondary Cell

[0406] SCTP Stream Control Transmission Protocol

[0407] SDAP Service Data Adaptation Protocol

[0408] SDU Service Data Unit

[0409] SeGW Security Gateway

[0410] SFN System Frame Number

[0411] SGW Serving Gateway

[0412] SI System Information

[0413] SIB System Information Block

[0414] SINR Signal to Interference and Noise Ratio

[0415] SMF Session Management Function

[0416] SMO Service Management and Orchestration

[0417] SN Secondary Node

[0418] SNR Signal to Noise Ratio

[0419] SON Self Optimized Network

[0420] SS Synchronization Signal

[0421] SSS Secondary Synchronization Signal

[0422] TA Terminal Adaptor

[0423] TDD Time Division Duplex

[0424] TDOA Time Difference of Arrival

[0425] TOA Time of Arrival

[0426] TE Terminal Equipment

[0427] TS Technical Specification

[0428] TSS Tertiary Synchronization Signal

[0429] TTI Transmission Time Interval

[0430] UDM User Data Management

[0431] UE User Equipment

[0432] UL Uplink

[0433] UPF User Plane Function

[0434] USIM Universal Subscriber Identity Module

[0435] UTDOA Uplink Time Difference of Arrival

[0436] VPLMN Visited Public Land Mobile Network

[0437] WAB Wireless Access and Backhaullx RTTCDMA2000 lx Radio Transmission Technology

[0438] WCDMA Wide CDMA

[0439] WLAN Wide Local Area Network

[0440] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0441] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on anon-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

[0442] 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 radio access node, RAN, node (110) that is configured to communicate at least via a wireless backhaul, the method comprising: indicating (S104), by the RAN node (110), location information to an operations, administration and maintenance, 0AM, system; receiving (S106), by the RAN node (110), a RAN node configuration that is based on the location information; and performing (S108) at least one action based on the RAN node configuration.

2. The method of Claim 1, wherein the location information comprises one or more of: geographical coordinates associated with the RAN node (110); information, for the RAN node (110), associated with a global navigation system; and at least one parameter associated with a mobile terminated, MT, function of the RAN node (110).

3. The method of Claim 2, wherein the at least one parameter comprises at least one of: a serving cell identifier, ID, associated with the MT function of the RAN node (110); a serving network node ID associated with the MT function of the RAN node (110); a tracking area code, TAC; and a serving public land mobile network, PLMN, associated with the MT function of the RAN node (110).

4. The method of any one of Claims 1-3, further comprising determining, by the RAN node (110), to obtain the RAN node configuration based on one or both of a preconfiguration and at least one trigger.

5. The method of Claim 4, wherein the pre-configuration or at least one trigger comprise an indication of one or more of: a physical location of the RAN node (110); an elapsed time since the RAN node’s reception of a previous configuration;a time; a data delay on interface connections; a trigger event; a roaming event; reaching one or more waypoints on a preconfigured path; a cell identifier, ID, associated with a first connection; a tracking area code, TAC, associated with a second connection; a network node-ID associated with a third connection; and a public land mobile network, PLMN, associated with a fourth connection.

6. The method of any one of Claims 1-5, wherein the at least one action comprising one or more of: selecting a core network node (108) to establish connections with; establishing interfaces with at least one core network node (108); communicating with the 0AM system; serving at least one user equipment; and selecting a public land mobile network, PLMN.

7. The method of any one of Claims 1-6, further comprising inquiring the 0AM system whether a new RAN node configuration is required; and the new RAN node configuration comprising to the RAN configuration that was received.

8. The method of any one of Claims 1-7, wherein the RAN node (110) comprises: a mobile terminated, MT, portion; and a node B portion.

9. The method of Claim 8, wherein the MT portion and the node portion of the RAN node (110) are one of: connected to a same network during non-roaming; connected to different networks; or connected to a same network during roaming.

10. A radio access node, RAN, node (110) that is configured to communicate at least via a wireless backhaul, the RAN node (110) configured to: indicate location information to an operations, administration and maintenance, 0AM, system; receive a RAN node configuration that is based on the location information; and perform at least one action based on the RAN node configuration.

11. The RAN node (110) of Claim 1, wherein the location information comprises one or more of: geographical coordinates associated with the RAN node (110); information, for the RAN node (110), associated with a global navigation system; and at least one parameter associated with a mobile terminated, MT, function of the RAN node (110).

12. The RAN node (110) of Claim 11, wherein the at least one parameter comprises at least one of: a serving cell identifier, ID, associated with the MT function of the RAN node (110); a serving network node ID associated with the MT function of the RAN node (110); a tracking area code, TAC; and a serving public land mobile network, PLMN, associated with the MT function of the RAN node (110).

13. The RAN node (110) of any one of Claims 10-12, wherein the RAN node (110) is further configured to determine to obtain the RAN node configuration based on one or both of a pre-configuration and at least one trigger.

14. The RAN node (110) of Claim 13, wherein the pre-configuration or at least one trigger comprise an indication of one or more of: a physical location of the RAN node (110); an elapsed time since the RAN node’s reception of a previous configuration; a time; a data delay on interface connections; a trigger event;a roaming event; reaching one or more waypoints on a preconfigured path; a cell identifier, ID, associated with a first connection; a tracking area code, TAC, associated with a second connection; a network node-ID associated with a third connection; and a public land mobile network, PLMN, associated with a fourth connection.

15. The RAN node (110) of any one of Claims 10-14, wherein the at least one action comprising one or more of: selecting a core network node (108) to establish connections with; establishing interfaces with at least one core network node (108); communicating with the 0AM system; serving at least one user equipment (112); and selecting a public land mobile network, PLMN.

16. The RAN node (110) of any one of Claims 10-15, wherein the RAN node (110) is further configured to inquire the 0AM system whether a new RAN node configuration is required; and the new RAN node configuration comprising to the RAN configuration that was received.

17. The RAN node (110) of any one of Claims 10-16, wherein the RAN node (110) comprises: a mobile terminated, MT, portion; and a node B portion.

18. The RAN node (110) of Claim 17, wherein the MT portion and the node portion of the RAN node (110) are one of: connected to a same network during non-roaming; connected to different networks; or connected to a same network during roaming.

19. A method implemented by an operations, administration and maintenance, OAM, system that is configured to communicate with a radio access node, RAN, node (110) via wireless backhaul communications, the method comprising: receiving (SI 10), from the RAN node (110), location information; generate (S 112) a RAN node configuration based on the location information; and transmitting (SI 14), to the RAN node (110), the RAN node configuration to configure the RAN node (110) to perform at least one action.

20. The method of Claim 19, wherein the location information comprises one or more of: geographical coordinates associated with the RAN node (110); information, for the RAN node (110), associated with a global navigation system; and at least one parameter associated with a mobile terminated, MT, function of the RAN node (110).

21. The method of Claim 20, wherein the at least one parameter comprises at least one of: a serving cell identifier, ID, associated with the MT function of the RAN node (110); a serving network node ID associated with the MT function of the RAN node (110); a tracking area code, TAC; and a serving public land mobile network, PLMN, associated with the MT function of the RAN node (110).

22. The method of any one of Claims 19-21, wherein the at least one action comprising one or more of: selecting a core network node (108) to establish connections with; establishing interfaces with at least one core network node (108); communicating with an operations, administration and maintenance, OAM, system; serving at least one user equipment (112); and selecting a public land mobile network, PLMN.

23. The method of any one of Claims 19-22, further comprising determining whether a new RAN node configuration is required by the RAN node (110) based on the location information; and the generating of the RAN node configuration is in response to the determination that the RAN node (110) requires the new RAN node configuration24. The method of any one of Claims 19-23, further comprising receiving an inquiry, from the RAN node (110), as to whether a new RAN node configuration is required by the RAN node (110), the generating of the RAN node configuration being based on the inquiry.

25. An operations, administration and maintenance, 0AM, system that is configured to communicate with a radio access node, RAN, node (110) via wireless backhaul communications, the 0AM system configured to: receive, from the RAN node (110), location information; generate a RAN node configuration based on the location information; and transmit, to the RAN node (110), the RAN node configuration to configure the RAN node (110) to perform at least one action.

26. The 0AM system of Claim 25, wherein the location information comprises one or more of: geographical coordinates associated with the RAN node (110); information, for the RAN node (110), associated with a global navigation system; and at least one parameter associated with a mobile terminated, MT, function of the RAN node (110).

27. The 0AM system of Claim 26, wherein the at least one parameter comprises at least one of: a serving cell identifier, ID, associated with the MT function of the RAN node (110); a serving network node ID associated with the MT function of the RAN node (110); a tracking area code, TAC; and a serving public land mobile network, PLMN, associated with the MT function of the RAN node (110).

28. The OAM system of any one of Claims 25-27, wherein the at least one action comprising one or more of: select a core network node (108) to establish connections with; establish interfaces with at least one core network node (108); communicate with an operations, administration and maintenance, OAM, system; serve at least one user equipment (112); and select a public land mobile network, PLMN.

29. The OAM system of any one of Claims 25-28, wherein the OAM system is further configured to determine whether a new RAN node configuration is required by the RAN node (110) based on the location information; and the generating of the RAN node configuration is in response to the determination that the RAN node (110) requires the new RAN node configuration30. The OAM system of any one of Claims 25-29, wherein the OAM system is further configured to receive an inquiry, from the RAN node (110), as to whether a new RAN node configuration is required by the RAN node (110), the generating of the RAN node configuration being based on the inquiry.

Images