WO2025210595A1

WO2025210595A1 - Configuration of ran nodes with wireless backhaul

Info

Publication number: WO2025210595A1
Application number: PCT/IB2025/053603
Authority: WO
Inventors: Junfeng Wang; Qiang ZU; Filip BARAC; Oskar Malm; Qian Chen
Original assignee: Telefonaktiebolaget LM Ericsson AB
Current assignee: Telefonaktiebolaget LM Ericsson AB
Priority date: 2024-04-05
Filing date: 2025-04-04
Publication date: 2025-10-09
Anticipated expiration: 2026-10-05

Abstract

According to some embodiments, a method is performed by a mobile network node. The method comprises transmitting a notification to a core network node. The notification comprises an indication of a location of the mobile network node. The method further comprises receiving a configuration from the core network node. The configuration is based on the location of the mobile network node. The method further comprises operating in a wireless network based on the received configuration.

Description

Configuration of RAN Nodes with Wireless Backhaul

TECHNICAL FIELD

[0001] The present disclosure generally relates to communication networks, and more specifically to configuration of radio access network (RAN) nodes with wireless backhaul.

BACKGROUND

[0002] The Third Generation Partnership Project (3GGP) Rel-19 Study Item Description (SID) for Study on Additional Topological Enhancements for New Radio (NR) in RP-234041 consists of two parts: wireless access backhaul (WAB), which refers to a mobile gNB, and fifth generation (5G) Femto.

[0003] The justification of the WAB part of the study item for the legacy building blocks is to enhance 5G radio access network (RAN) topologies to provide a broader range of use cases, such as:

• 5G access for user equipment (UEs) onboard aircrafts, cruise ships, helicopters, and vehicles in remote areas with limited sky visibility via an onboard gNB.

• Backhauling of NG and Xn interfaces via terrestrial network (TN) and non-terrestrial network (NTN), including support of handover between NTN and TN for backhaul.

• Support for onboard/on-site multiple-access edge computing (MEC) and local services.

• Support for backhauling without RAN-sharing or roaming agreements between access public land mobile networks (PLMN(s)) and backhaul PLMN(s).

• Backhauling for local gNB deployed in public safety or disaster recovery scenarios.

[0004] It is assumed that wireless access backhaul is aligned with vehicle mounted relay (VMR) use cases and with architectural enhancements for Rel-19 VMR. It is expected that singlehop backhauling is sufficient for WAB and that there is no impact to UEs at this late stage of 5G deployment.

[0005] The objectives from the SID related to the WAB study include studying the support of WAB including the architecture and protocol stack of supporting a gNB with mobile terminal (MT) function providing protocol data unit (PDU) session backhaul, the impact of WAB mobility within an existing RAN (e.g., inter-gNB neighbor relations), necessary inter-gNB- and gNB-to- core network (CN) signalling to address the support of WAB, and signalling enhancements on resource multiplexing for WAB. The WAB study does not preclude any backhaul scenario (e.g., NTN or TN).

[0006] Figure 1 illustrates a potential WAB architecture. A 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 node uses its WAB-MT part to connect with the rest of the mobile network, i.e., to connect to its serving gNB (the “BH-gNB” in Figure 1). In this architecture, the PDU session(s) established between the WAB-MT and BH-user plane function (UPF) are used to carry at least the traffic for the NG and Xn connections of the WAB-gNB. Should the WAB-node be equipped with a local user plane function (UPF), data across further point-to-point reference points also needs to be transmitted (e.g., N4 traffic to UPF-access and mobility management function (AMF), or N6 traffic to UPF-data network (DN)).

[0007] The PLMN that serves the WAB-gNB with its connected UEs may be the same as or different from the PLMN serving the WAB-MT. Figure 1 illustrates the scenario when the two PLMNs are different, and thus the nodes for the WAB-MT PLMN are filled in black in Figure 1. [0008] When the two PLMNs are different, the WAB-MT is served by the BH-gNB and the backhaul 5G Core Network (BH-5GC) that includes the BH-AMF, BH-UPF and other core network functions. The corresponding operations, administration, and maintenance (0AM) system is the BH-OAM.

[0009] The WAB-gNB is served by the access 5G Core Network (UE-5GC), comprising the WAB-AMF, WAB-UPF (depicted for short as AMF and UPF in the UE-5GC in Figure 1) and other core network functions. The corresponding 0AM system is the WAB-OAM. The UEs served by the WAB-gNB may be served by multiple AMFs, meaning that, for one WAB-node, there may exist more than on WAB-AMF.

[0010] Alternatively, the WAB-MT and WAB-gNB may be served by the same PLMN but different core network (CN) nodes, or by the same PLMN and same CN nodes (in which case, e.g., the BH-AMF and WAB-AMF may be the same).

[0011] 3GPP TS 28.532 vl8.1.0 specifies operations and notifications for the generic provisioning management service (TS 28.532 clause 11.1). The following operations and notification are relevant for the embodiments described herein:

• createMOI operation.

• modifyMOIAttributes operation.

• deleteMOI operation

• Notification notifyMOIChanges. • Notification notifyMOIAttributeValueChanges.

• Notification notifyMOICreation

• Notification notifyMOIDeletion

Meanwhile, TS 28.541 vl8.6.1 is an example of network resource model for the managed object instance (MOI) that is subject to the operations and notifications in TS 28.532 vl8. 1.0.

[0012] Plug and connect (PnC) is the procedure that a network node uses to initiate an Internet Protocol (IP) connection to the 0AM network. Plug and connect to the 0AM system includes the steps of initial IP autoconfiguration, certificate enrollment, establishing a secure connection to the security gateway (SeGW) and establishing a secure connection to software configuration server (SCS).

[0013] The initial IP autoconfiguration obtains client IP configuration and IP address or fully qualified domain names (FQDN) of certificate authority (CA)Zregistration authority (RA), SeGW and SCS via Dynamic Host Configuration Protocol (DHCP) request. To perform CA/RA enrollment, the network element may be provisioned with an 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.

• TS 28.314 vl7.0.0: "plug and connect; Concepts and requirements".

• TS 28.315 vl7.0.0: "plug and connect; Procedure flows".

• TS 28.316 vl7.0.0: "plug and connect; Data formats".

[0014] 3GPP 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 0AM to the RAN and CN nodes.

[0015] There currently exist certain challenges. For example, a WAB node will likely consist of a WAB-gNB and a WAB-MT. The WAB-gNB part of an WAB node serves UEs, while the node uses its WAB-MT part to connect with the mobile network, i.e., to connect to its serving gNB/network (the BH-gNB in Figure 1). In this architecture, the PDU sessions established between the WAB-MT and the network are used to provide Internet Protocol (IP) connectivity and carry the traffic for the 0AM, NGAP and XnAP connections of the WAB-gNB. The WAB-gNB may interact with the same AMF that manages access for the WAB-MT, or it may interact with other AMF(s).

[0016] According to the WAB architecture, the NG connection between the WAB node and the CN are carried via the wireless backhaul link between the WAB-MT and the BH-gNB. Because the WAB node may move across large areas, and even roam to other PLMNs, at some point, the configuration parameters of a WAB node will likely need to be updated.

[0017] In that respect, a WAB node needs to be provisioned with certain configuration parameters, e.g. (non -limiting examples):

• The parameters needed forthe WAB node to selectnew 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.

• If 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.

[0018] The new configuration parameters will likely depend on the node’s current location. Pre -configuring the WAB node with all possible combinations of location-dependent parameters in advance does not scale; moreover, because the WAB node movement may be random, and the WAB node may even roam to different PLMN.

[0019] One approach to the problem is to enable the WAB-node to indicate to the 0AM its current location and fetch the appropriate configuration parameters, which is de facto querying. However, the communication between the 0AM and the network nodes is not designed for the querying communication paradigm. The 0AM system only supports Create, Read, Update, Delete (CRUD) operations to provision the configuration of the managed node, but the 0AM system does not support the managed node to query the 0AM system forthe configurations. Thus, it is unclear how to support the location-dependent reconfiguration of WAB node without significantly impacting the current 0AM way of operating.

[0020] The same problem pertains to the mobile IAB (mlAB) nodes.

SUMMARY

[0021] As described above, certain challenges currently exist with configuration of radio access network (RAN) nodes with wireless backhaul. Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges.

[0022] For example, in particular embodiments the location-based (reconfiguration) of wireless access backhaul (WAB)-nodes and mobile integrated access and backhaul (mlAB)-nodes is enabled by enhancing the network resource model (NRM). The NRM is enhanced to support mapping of node configurations to potential node locations.

[0023] The query paradigm for configuring the moving nodes is mimicked by reusing “modify” and “notify” operations.

[0024] According to some embodiments, a method is performed by a mobile network node. The method comprises transmitting a first notification to a core network node. The first notification comprises an indication of a first location of the mobile network node. The method further comprises receiving a first configuration from the core network node. The first configuration is based on the first location of the mobile network node. The method further comprises operating in a first wireless network based on the received first configuration.

[0025] In particular embodiments, the method further comprises transmitting a second notification to the core network node. The second notification comprises an indication of a second location of the mobile network node. The method further comprises receiving a second configuration from the core network node. The second configuration is based on the second location of the mobile network node. The method further comprises operating in a second wireless network based on the received second configuration.

[0026] In particular embodiments, the first/second configuration comprises a configuration for one or more of: parameters that enable the mobile network node to communicate with one or more core network nodes; parameters to support mobility; parameters for authorization; parameters for serving wireless devices from the first location; and parameters associated with a mobile terminal portion of the mobile network node.

[0027] In particular embodiments, the indication of the first/second location of the mobile network node comprises one or more of: geographical coordinates; serving cell identifier for a mobile terminal portion of the mobile network node; serving base station identifier for a mobile terminal portion of the mobile network node; tracking area code or tracking area identifier for a mobile terminal portion of the mobile network node; serving public land mobile network identifier associated with a mobile terminal portion of the mobile network node; and registration area associated with a mobile terminal portion of the mobile network node.

[0028] In particular embodiments, the method further comprises determining one or more conditions under which the mobile network node is to transmit an indication to the core network node that a location of the mobile network node has changed is satisfied. [0029] In particular embodiments, the method further comprises receiving an indication of one or more conditions under which the mobile network node is to transmit an indication to the core network node that a location of the mobile network node has changed.

[0030] In particular embodiments, the condition comprises any one or more of: an indication of a geographical position of the mobile network node obtained from a location service has changed; a threshold amount of time has elapsed since receiving the first configuration; a mobility event for a mobile terminal portion of the mobile network node has occurred; a congestion-based policy triggers an indication; and a way point along a preconfigured travel path is reached.

[0031] In particular embodiments, the first/second notification comprises a notifyMOIChanges message and the first/second configuration comprises a notifyMOIAttributeValueChanges message.

[0032] In particular embodiments, the core network node comprises an operations, administration, and management (0AM) network node.

[0033] In particular embodiments, the mobile network node comprises one of a wireless access backhaul (WAB) network node or a mobile integrated access and backhaul (mlAB) network node.

[0034] According to some embodiments, a mobile network node comprises processing circuitry operable to perform any of the mobile network node methods described above.

[0035] Another computer program product comprises a non-transitory computer readable medium storing computer readable program code, the computer readable program code operable, when executed by processing circuitry to perform any of the methods performed by the mobile network node described above.

[0036] According to some embodiments, a method is performed by a core network node. The method comprises receiving a first notification from a mobile network node. The first notification comprises an indication of a first location of the mobile network node. The method further comprises transmitting a first configuration to the mobile network node. The first configuration is associated with the first location of the mobile network node.

[0037] In particular embodiments, the method further comprises receiving a second notification from the mobile network node. The second notification comprises an indication of a second location of the mobile network node. The method further comprises transmitting a second configuration to the mobile network node. The second configuration is associated with the second location of the mobile network node. [0038] In particular embodiments, the method further comprises transmitting to the mobile network node an indication of one or more conditions under which the mobile network node is to transmit an indication to the core network node that a location of the mobile network node has changed.

[0039] According to some embodiments, a core network node comprises processing circuitry operable to perform any of the core network node methods described above.

[0040] Another computer program product comprises a non-transitory computer readable medium storing computer readable program code, the computer readable program code operable, when executed by processing circuitry to perform any of the methods performed by the core network node described above.

[0041] Certain embodiments may provide one or more of the following technical advantages. For example, particular embodiments enable a moving RAN node (e.g., a WAB or mlAB node) to obtain the location-dependent configuration parameters from the 0AM system without having to introduce significant changes to the way that the 0AM system operates today.

BRIEF DESCRIPTION OF THE DRAWINGS

[0042] The present disclosure may be best understood by way of example with reference to the following description and accompanying drawings that are used to illustrate embodiments of the present disclosure. In the drawings:

Figure 1 illustrates a potential wireless access backhaul (WAB) architecture;

Figure 2 shows an example of a communication system, according to certain embodiments;

Figure 3 shows a user equipment (UE), according to certain embodiments;

Figure 4 shows a network node, according to certain embodiments;

Figure 5 is a flowchart illustrating an example method in a mobile network node, according to certain embodiments; and

Figure 6 is a flowchart illustrating an example method in a core network node, according to certain embodiments.

DETAILED DESCRIPTION

[0043] As described above, certain challenges currently exist with configuration of radio access network (RAN) nodes with wireless backhaul. Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. For example, in particular embodiments the location-based (reconfiguration) of wireless access backhaul (WAB)-nodes and mobile integrated access and backhaul (mlAB)-nodes is enabled by enhancing the network resource model (NRM). The NRM is enhanced to support mapping of node configurations to potential node locations.

[0044] Particular embodiments are 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.

[0045] Particular embodiments described herein are presented on a non-limiting example of WAB nodes, but they apply to any kind of moving or static RAN node, including mlAB nodes.

[0046] The terms “node” may refer to a WAB-node or an lAB-node, or both. The node may also be referred to as a mobile node.

[0047] Particular embodiments apply to both non-roaming (i.e., when the node is connected to its home public land mobile network (PLMN)) and roaming scenarios (i.e., when either the mobile terminal (MT) part or the WAB-gNB/IAB-DU part of the node, or both, are connected to a network other than their home PLMN).

[0048] The terms “CN nodes”, “core network nodes” and “CN functions” are used interchangeably without losing meaning, and they may refer to one or more of the following: access and mobility management function (AMF), user plane function (UPF), session management function (SMF), or any other fifth generation core (5GC) node/function.

[0049] The procedures used in particular embodiments may be class- 1 or class-2 procedures. They may be new procedures or enhancements of existing procedures.

[0050] 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. When X is a UE, this means that node X and the RAN node serving the UE have a logical connection associated to the UE.

[0051] Particular embodiments may apply to both single- and dual-connected WAB/mlAB nodes.

[0052] 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).

[0053] Particular embodiments apply to New Radio (NR) as well as future radio access technologies (RATs), such as beyond Third Generation Partnership Project (3GPP) Rel-19. [0054] The terms “0AM” and “0AM system” are used interchangeably. [0055] In the scenario of interest, the WAB/mlAB node connects to the network, obtains the configuration parameters, and starts to move. As the node moves, depending on the location, the node needs to be provisioned with the appropriate configuration parameters so that the node can connect with other network nodes, with the 0AM, and so that the node can serve UEs.

[0056] A question addressed by particular embodiments is how to enable the communication paradigm between a mobile network node and the 0AM system, where the network node can query the 0AM system and obtain configuration parameters based on its location.

[0057] Particular embodiments include the following steps.

[0058] (STEP 1) In particular embodiments, the network resource model (NRM) is enhanced to support mapping between configurations of the node and possible locations of the node.

[0059] Non-limiting examples of configuration parameters that may change depending on the location (some of these parameters may be applicable only to WAB-nodes, some may apply only to lAB-nodes, and some may apply to both):

• The parameters that enable the RAN node to connect to and communicate with the 0AM system, e.g., IP configuration of 0AM system for connectivity (IP/FQDN of CA/RA, SeGW, SCS, etc.).

• Configuration for the WAB/IAB to support mobility (e.g., NRCellDU).

• Policy configuration for WAB authorization, etc.

• 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 Stream Control Transport Protocol (SCTP) associations, CN node IDs (e.g., globally unique AMF identifiers (GUAMIs) of the AMF, AMF Region ID, AMF set ID, AMF pointer as defined in TS 24.501 vl8.6.0)), etc.

• The configuration parameters that are needed for the WAB node to serve UEs in its new area/location, for example: o The tracking area code(s) (TAC(s)), the cell ID(s), and the PLMN ID(s) that the WAB-gNB should broadcast. o Some parameters may be to avoid interference and collision such, as random access channel (RACH) configuration, physical cell identifier (PCI) configuration, and time division duplex (TDD) pattern configurations. o Some parameters are related to tracking area code and/or radio network area code configurations. o Some configurations may include transmission power for coverage reach purposes.

• The configuration parameters specified in TS 28.541 vl8.6.1, as well as any additional parameters.

[0060] The following are non-limiting examples of location information to which the above configuration parameters are mapped:

• WAB node’s geographical coordinates. o The WAB-gNB may obtain the location information from one of the global navigation systems.

■ Alternatively, the WAB-gNB may acquire this information from the WAB- MT, which may then pass it to the WAB-gNB. For example, the WAB-MT may obtain the information from one of the global navigation systems, or the WAB-MT may query the network to tell the WAB-MT the WAB-MT’s location. For example, the mobile originated location request (MO-LR) location request defined in TS 23.273 may be used.

• One or more parameters related to the co-located WAB-MT: o Serving cell ID. o Serving gNB ID. o TAC/tracking area identity (TAI). o Serving PLMN information (e.g., PLMN ID). o Registration area.

[0061] (STEP 2) The above mapping may be stored in the 0AM configuration server.

[0062] (STEP 3) When the mobile node powers up and connects to the 0AM system for the first time, the mobile node provides its location information to the 0AM system by sending the “notifyMOIChanges” notification, or other notification to the 0AM system, following the format specified in TS 28.532 vl8.1.0, based on the NRM model. Herein, the mobile node sends an indication of the new location x to the 0AM. [0063] In some embodiments, the conditions, based on which the mobile node determines that a new configuration is needed and which trigger the mobile node to send a query to the 0AM, may be preconfigured at the mobile node.

[0064] In some embodiments, the mobile node may query the 0AM based on its own autonomous determination.

[0065] Then the software configuration server (SCS) may provision the initial configuration via createMOI operation for the WAB/IAB (i.e., mobile node) for its current location (e.g., location x).

[0066] The mobile node receives and applies the configuration parameters, and continues to operate, if applicable.

[0067] In some embodiments, the mobile node may also be configured with respect to when to query the 0AM system again and ask for a new configuration.

[0068] (STEP 4) The mobile node moves to a location y, and the mobile node sends the “notifyMOIChanges” notification, or the “notifyMOIAttributeValueChanges” notification or other notifications to the 0AM system, following the format specified in TS 28.532 vl 8. 1.0, based on the NRM model. Herein, the mobile node sends an indication of the new location y to the 0 AM. In some embodiments, the conditions, based on which the mobile node determines that a new configuration is needed, and which trigger the mobile node to send a query to the 0AM, may be preconfigured at the mobile node.

[0069] In some embodiments, the mobile node may query the 0AM based on its own autonomous determination.

[0070] (STEP 5) Upon reception of notifications from the mobile node, 0AM may send modifyMOIAttributes operation or other operations to provide the new configuration to the mobile node based on location y.

[0071] (STEP 6) The mobile node receives and applies the configuration parameters, and continues to operate, if applicable.

[0072] Some embodiments include triggers for fetching a new WAB/IAB configuration. These aspects are applicable to all embodiments described herein.

[0073] In some embodiments, the WAB node (i.e., mobile node) may be configured that, upon fulfilment of certain conditions, it sends notifications to the 0AM indicating its location, as elaborated in the embodiments herein. [0074] In some embodiments, the WAB node may be configured that, upon fulfilment of certain conditions, it contacts the 0AM for fetching a new WAB configuration, as elaborated in the embodiments herein.

[0075] In some embodiments, the WAB node, based on its own logic (e.g., entering an area with a new TAC), determines that it should contact the 0AM for fetching a new configuration.

[0076] In some embodiments, the WAB node may query the 0AM about whether it needs a configuration update.

[0077] Upon receiving the request, the 0AM sends the configuration parameters to the WAB- gNB.

[0078] The conditions may include one or more of the following: physical location (e.g., expressed in geo-coordinates); time, or time elapsed since the last configuration is received; data delay on interface connections (e.g., SCTP delay, timeouts); traffic congestion; trigger event; roaming (national or international); the cell ID and/or the TAC and/or the gNB-ID, or the PLMN to which the MT connects; MT handover; based upon (preconfigured/configured) flight or path planning, i.e., when certain way points (geographical coordinates) have been reached; PLMN information; and/or registration area.

[0079] Some embodiments apply to roaming scenarios. 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 visited PLMN (VPLMN)). Several embodiments for roaming scenarios are described, where the roaming may be to a network inside the same country (i.e., national) or to a network in a different country (i.e., international).

[0080] In some roaming scenarios, 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 protocol data unit (PDU) sessions of the WAB-MT. In this case, the mobile node may query the 0AM and obtain the configuration as described in the examples for the non-roaming scenario. [0081] In some roaming scenarios, the WAB-MT is registered at, and connected to, the VPLMN. Meanwhile, the WAB-gNB has connected to CN nodes in the same VPLMN. In this case, the WAB-gNB is redirected by HPLMN to an 0AM located in the VPLMN to receive additional local configuration data. While communicating with the VPLMN 0AM, the embodiments described above apply, whereas the mobile node queries the 0AM in the VPLMN to obtain the configuration parameters. [0082] If the mobile node, later, roams into yet another network other than its HPLMN, the embodiments described herein apply as well, and also apply to all subsequent VPLMNs.

[0083] Figure 2 shows an example of a communication system 100 in accordance with some embodiments. 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 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point. 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.

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

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

[0086] 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 (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).

[0087] The host 116 may be under the ownership or control of a service provider other than an operator or provider of the access network 104 and/or the telecommunication network 102 and may be operated by the service provider or on behalf of the service provider. The host 116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio/video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0088] As a whole, the communication system 100 of Figure 2 enables connectivity between the UEs, network nodes, and hosts. 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); Long 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.

[0089] 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)ZMassive loT services to yet further UEs.

[0090] 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 multi -standard 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).

[0091] 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 a controller, 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 in if one or more of the UEs are low energy loT devices.

[0092] 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 nondedicated 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.

[0093] Figure 3 shows a UE 200 in accordance with some embodiments. 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-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-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.

[0094] 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).

[0095] 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 2. 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. [0096] 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 any combination of the above. For example, the processing circuitry 202 may include multiple central processing units (CPUs).

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

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

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

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

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

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

[0103] 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). [0104] 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.

[0105] 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/or software 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 2.

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

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

[0108] Figure 4 shows a network node 300 in accordance with some embodiments. 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 NRNodeBs (gNBs)).

[0109] 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 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 antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0110] 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).

[oni] 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 NodeBs. 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.

[0112] 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. [0113] 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.

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

[0115] 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 front-end 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 a combination 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.

[0116] 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).

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

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

[0119] 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, the network 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.

[0120] Embodiments of the network node 300 may include additional components beyond those shown in Figure 4 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.

[0121] 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 a non-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.

[0122] FIGURE 5 is a flowchart illustrating an example method 500 in a mobile network node, according to certain embodiments. In particular embodiments, one or more steps of FIGURE 5 may be performed by network node 300 described with respect to FIGURE 3. In particular embodiments, the mobile network node comprises one of a wireless access backhaul (WAB) network node or a mobile integrated access and backhaul (mlAB) network node.

[0123] The method 500 may begin at step 512, where the mobile network node (e.g., network node 300) transmits a notification to a core network node (e.g., 0AM network node). The notification comprises an indication of a location of the mobile network node.

[0124] In particular embodiments, the indication of the location of the mobile network node comprises one or more of: geographical coordinates (e.g., obtaining from GNSS, mobile originated location request, etc.); serving cell identifier for a mobile terminal portion of the mobile network node (e.g., physical cell identifier of serving cell); serving base station identifier for a mobile terminal portion of the mobile network node (e.g., serving gNB identifier); tracking area code or tracking area identifier for a mobile terminal portion of the mobile network node; serving public land mobile network identifier associated with a mobile terminal portion of the mobile network node; and registration area associated with a mobile terminal portion of the mobile network node. [0125] In particular embodiments, the notification comprises a notifyMOIChanges message. [0126] Additional examples are described with respect to the embodiments and examples described herein.

[0127] At step 514, the mobile network node receives a configuration from the core network node. The configuration is based on the location of the mobile network node. For example, the core network node maintains a mapping of configurations and locations. In response to the notification from the mobile network node, the core network node is able to select an appropriate configuration based on the location of the mobile network node and transmit the configuration to the core network node.

[0128] In particular embodiments, the configuration comprises a configuration for one or more of: parameters that enable the mobile network node to communicate with one or more core network nodes (e.g., IP configuration of 0AM system for connectivity (IP/FQDN of CA/RA, SeGW, SCS, GUAMIs of the AMF, AMF Region ID, AMF set ID, AMF pointer, etc.); parameters to support mobility; parameters for authorization; parameters for serving wireless devices from the location (e.g., cell identifier, RACH configuration, TDD configuration, tracking area code, transmission power, etc.); and parameters associated with a mobile terminal portion of the mobile network node.

[0129] In particular embodiments, the configuration comprises a notifyMOIAttributeValueChanges message.

[0130] Additional examples are described with respect to the embodiments and examples described herein.

[0131] At step 516, the mobile network node operates in a wireless network based on the received configuration. For example, the received configuration enables the mobile network node to connect with other network nodes, with the 0AM, and to serve UEs.

[0132] At step 518, the mobile network node may determine one or more conditions under which the mobile network node is to transmit an indication to the core network node that a location of the mobile network node has changed is satisfied.

[0133] In particular embodiments, the condition comprises any one or more of: an indication of a geographical position of the mobile network node obtained from a location service has changed; a threshold amount of time has elapsed since receiving the first configuration; a mobility event for a mobile terminal portion of the mobile network node has occurred; a congestion-based policy triggers an indication; and a way point along a preconfigured travel path is reached. Other examples are described with respect to the embodiments and examples described herein.

[0134] In some embodiments, instead of the mobile network node determining the criteria for reporting a location change, the mobile network node may receive the information from the core network node, such as in step 520.

[0135] At step 520, the mobile network node may receive an indication of one or more conditions under which the mobile network node is to transmit an indication to the core network node that a location of the mobile network node has changed.

[0136] Upon determining one of the conditions is fulfilled, the method may return to step 512, where the mobile network node sends a second notification to the core network node.

[0137] Modifications, additions, or omissions may be made to method 500 of FIGURE 5. Additionally, one or more steps in the method of FIGURE 5 may be performed in parallel or in any suitable order. For example, steps 516 and/or 518 may be performed before step 512.

[0138] FIGURE 6 is a flowchart illustrating an example method 600 in a core network node, according to certain embodiments. In particular embodiments, one or more steps of FIGURE 6 may be performed by network node 300 described with respect to FIGURE 4. The core network node may comprise an 0AM network node.

[0139] The method 600 may begin at step 612, where the core network node (e.g., network node 300) receives a notification from a mobile network node. The notification comprises an indication of a location of the mobile network node. The notification is described in more detail with respect to Figure 5 and with respect to the embodiments and examples described herein.

[0140] At step 614, the core network node transmits a configuration to the mobile network node. The configuration is associated with the location of the mobile network node. The configuration is described in more detail with respect to Figure 5 and with respect to the embodiments and examples described herein.

[0141] At step 616, the core network node may transmit to the mobile network node an indication of one or more conditions under which the mobile network node is to transmit an indication to the core network node that a location of the mobile network node has changed. The indication is described in more detail with respect to Figure 5 and with respect to the embodiments and examples described herein. [0142] Modifications, additions, or omissions may be made to method 600 of FIGURE 6. Additionally, one or more steps in the method of FIGURE 6 may be performed in parallel or in any suitable order. For example, step 616 may be performed before step 612.

[0143] The foregoing description sets forth numerous specific details. It is understood, however, that embodiments may be practiced without these specific details. In other instances, well-known circuits, structures and techniques have not been shown in detail in order not to obscure the understanding of this description. Those of ordinary skill in the art, with the included descriptions, will be able to implement appropriate functionality without undue experimentation.

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

[0145] Although this disclosure has been described in terms of certain embodiments, alterations and permutations of the embodiments will be apparent to those skilled in the art. Accordingly, the above description of the embodiments does not constrain this disclosure. Other changes, substitutions, and alterations are possible without departing from the scope of this disclosure, as defined by the claims below.

[0146] Some example embodiments are described below.

1. A method performed by an operations and management network node, the method comprising:

- associating a configuration for a mobile base station with a location in a network resource model;

- receiving a notification from a mobile base station, the notification including a location of the mobile base station;

- transmitting to the mobile base station the associated configuration based on the location of the mobile base station.

Group A Embodiments 2. A method performed by a wireless device, the method comprising:

- any of the wireless device steps, features, or functions described above, either alone or in combination with other steps, features, or functions described above.

3. The method of the previous embodiment, further comprising one or more additional wireless device steps, features or functions described above.

4. The method of any of the previous two embodiments, further comprising:

- providing user data; and

- forwarding the user data to a host computer via the transmission to the base station.

>up B Embodiments

5. A method performed by a mobile base station, the method comprising:

- transmitting a notification to an operations and management (0AM) network node, the notification comprising a location of the mobile base station;

- receiving a configuration from the 0AM network node, the configuration based on the location of the mobile base station; and

- accessing a wireless network using the received configuration.

6. A method performed by a base station, the method comprising:

- any of the steps, features, or functions described above with respect to base stations, either alone or in combination with other steps, features, or functions described above.

7. The method of the previous embodiment, further comprising one or more additional base station steps, features or functions described above.

8. The method of any of the previous embodiments, further comprising:

- obtaining user data; and

- forwarding the user data to a host computer or a wireless device. bodiments obile terminal comprising:

- processing circuitry configured to perform any of the steps of any of the Group A embodiments; and

- power supply circuitry configured to supply power to the wireless device. ase station comprising:

- processing circuitry configured to perform any of the steps of any of the Group B embodiments;

- power supply circuitry configured to supply power to the wireless device. ser equipment (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 embodiments;

- 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.

Claims

1. A method performed by a mobile network node, the method comprising: transmitting (512) a first notification to a core network node, the first notification comprising an indication of a first location of the mobile network node; receiving (514) a first configuration from the core network node, the first configuration based on the first location of the mobile network node; and operating (516) in a first wireless network based on the received first configuration.

2. The method of claim 1, further comprising: transmitting (512) a second notification to the core network node, the second notification comprising an indication of a second location of the mobile network node; receiving (514) a second configuration from the core network node, the second configuration based on the second location of the mobile network node; and operating (516) in a second wireless network based on the received second configuration.

3. The method of any one of claims 1-2, wherein the first configuration comprises a configuration for one or more of: parameters that enable the mobile network node to communicate with one or more core network nodes; parameters to support mobility; parameters for authorization; parameters for serving wireless devices from the first location; and parameters associated with a mobile terminal portion of the mobile network node.

4. The method of any one of claims 1-3, wherein the indication of the first location of the mobile network node comprises one or more of: geographical coordinates; serving cell identifier for a mobile terminal portion of the mobile network node; serving base station identifier for a mobile terminal portion of the mobile network node; tracking area code or tracking area identifier for a mobile terminal portion of the mobile network node; serving public land mobile network identifier associated with a mobile terminal portion of the mobile network node; and registration area associated with a mobile terminal portion of the mobile network node.

5. The method of any one of claims 1-4, further comprising: determining (520) one or more conditions under which the mobile network node is to transmit an indication to the core network node that a location of the mobile network node has changed is satisfied.

6. The method of any one of claims 1-5, further comprising: receiving (518) an indication of one or more conditions under which the mobile network node is to transmit an indication to the core network node that a location of the mobile network node has changed.

7. The method of any one of claims 5-6, wherein the condition comprises any one or more of: an indication of a geographical position of the mobile network node obtained from a location service has changed; a threshold amount of time has elapsed since receiving the first configuration; a mobility event for a mobile terminal portion of the mobile network node has occurred; a congestion-based policy triggers an indication; and a way point along a preconfigured travel path is reached.

8. The method of any one of claims 1-7, wherein the first notification comprises a notifyMOIChanges message and the first configuration comprises a notifyMOIAttributeValueChanges message.

9. The method of any one of claims 1-8, wherein the core network node comprises an operations, administration, and management (0AM) network node.

10. The method of any one of claims 1-9, wherein the mobile network node comprises one of a wireless access backhaul (WAB) network node or a mobile integrated access and backhaul (mlAB) network node.

11. A mobile network node (300) comprising processing circuitry (302) operable to: transmit a first notification to a core network node, the first notification comprising an indication of a first location of the mobile network node; receive a first configuration from the core network node, the first configuration based on the first location of the mobile network node; and operate in a first wireless network based on the received first configuration.

12. The mobile network node of claim 11, the processing circuitry further operable to: transmit a second notification to the core network node, the second notification comprising an indication of a second location of the mobile network node; receive a second configuration from the core network node, the second configuration based on the second location of the mobile network node; and operate in a second wireless network based on the received second configuration.

13. The mobile network node of any one of claims 11-12, wherein the first configuration comprises a configuration for one or more of: parameters that enable the mobile network node to communicate with one or more core network nodes; parameters to support mobility; parameters for authorization; parameters for serving wireless devices from the first location; and parameters associated with a mobile terminal portion of the mobile network node.

14. The mobile network node of any one of claims 11-13, wherein the indication of the first location of the mobile network node comprises one or more of: geographical coordinates; serving cell identifier for a mobile terminal portion of the mobile network node; serving base station identifier for a mobile terminal portion of the mobile network node; tracking area code or tracking area identifier for a mobile terminal portion of the mobile network node; serving public land mobile network identifier associated with a mobile terminal portion of the mobile network node; and registration area associated with a mobile terminal portion of the mobile network node.

15. The mobile network node of any one of claims 11-14, the processing circuitry further operable to: determine one or more conditions under which the mobile network node is to transmit an indication to the core network node that a location of the mobile network node has changed is satisfied.

16. The mobile network node of any one of claims 11-15, the processing circuitry further operable to: receive an indication of one or more conditions under which the mobile network node is to transmit an indication to the core network node that a location of the mobile network node has changed.

17. The mobile network node of any one of claims 15-16, wherein the condition comprises any one or more of: an indication of a geographical position of the mobile network node obtained from a location service has changed; a threshold amount of time has elapsed since receiving the first configuration; a mobility event for a mobile terminal portion of the mobile network node has occurred; a congestion-based policy triggers an indication; and a way point along a preconfigured travel path is reached.

18. The mobile network node of any one of claims 11-17, wherein the first notification comprises a notifyMOIChanges message and the first configuration comprises a notifyMOIAttributeValueChanges message.

19. The mobile network node of any one of claims 11-18, wherein the core network node comprises an operations, administration, and management (OAM) network node.

20. The mobile network node of any one of claims 11-19, wherein the mobile network node comprises one of a wireless access backhaul (WAB) network node or a mobile integrated access and backhaul (mlAB) network node.

21. A method performed by a core network node, the method comprising: receiving (612) a first notification from a mobile network node, the first notification comprising an indication of a first location of the mobile network node; and transmitting (614) a first configuration to the mobile network node, the first configuration associated with the first location of the mobile network node.

22. The method of claim 21, further comprising: receiving (612) a second notification from the mobile network node, the second notification comprising an indication of a second location of the mobile network node; and transmitting (614) a second configuration to the mobile network node, the second configuration associated with the second location of the mobile network node.

23. The method of any one of claims 21-22, wherein the first configuration comprises a configuration for one or more of: parameters that enable the mobile network node to communicate with one or more core network nodes; parameters to support mobility; parameters for authorization; parameters for serving wireless devices from the first location; and parameters associated with a mobile terminal portion of the mobile network node.

24. The method of any one of claims 21-23, wherein the indication of the first location of the mobile network node comprises one or more of: geographical coordinates; serving cell identifier for a mobile terminal portion of the mobile network node; serving base station identifier for a mobile terminal portion of the mobile network node; tracking area code or tracking area identifier for a mobile terminal portion of the mobile network node; serving public land mobile network identifier associated with a mobile terminal portion of the mobile network node; and registration area associated with a mobile terminal portion of the mobile network node.

25. The method of any one of claims 21-24, further comprising: transmitting (616) to the mobile network node an indication of one or more conditions under which the mobile network node is to transmit an indication to the core network node that a location of the mobile network node has changed.

26. The method of claim 25, wherein the condition comprises any one or more of: an indication of a geographical position of the mobile network node obtained from a location service has changed; a threshold amount of time has elapsed since receiving the first configuration; a mobility event for a mobile terminal portion of the mobile network node has occurred; a congestion-based policy triggers an indication; and a way point along a preconfigured travel path is reached.

27. The method of any one of claims 21-26, wherein the first notification comprises a notifyMOIChanges message and the first configuration comprises a notifyMOIAttributeValueChanges message.

28. The method of any one of claims 21-27, wherein the core network node comprises an operations, administration, and management (OAM) network node.

29. The method of any one of claims 21-28, wherein the mobile network node comprises one of a wireless access backhaul (WAB) network node or a mobile integrated access and backhaul (mlAB) network node.

30. A core network node (300) comprising processing circuitry (302) operable to: receive a first notification from a mobile network node, the first notification comprising an indication of a first location of the mobile network node; and transmit a first configuration to the mobile network node, the first configuration associated with the first location of the mobile network node.

31. The core network node of claim 30, the processing circuitry further operable to: receive a second notification from the mobile network node, the second notification comprising an indication of a second location of the mobile network node; and transmit a second configuration to the mobile network node, the second configuration associated with the second location of the mobile network node.

32. The core network node of any one of claims 30-31, wherein the first configuration comprises a configuration for one or more of: parameters that enable the mobile network node to communicate with one or more core network nodes; parameters to support mobility; parameters for authorization; parameters for serving wireless devices from the first location; and parameters associated with a mobile terminal portion of the mobile network node.

33. The core network node of any one of claims 30-32, wherein the indication of the first location of the mobile network node comprises one or more of: geographical coordinates; serving cell identifier for a mobile terminal portion of the mobile network node; serving base station identifier for a mobile terminal portion of the mobile network node; tracking area code or tracking area identifier for a mobile terminal portion of the mobile network node; serving public land mobile network identifier associated with a mobile terminal portion of the mobile network node; and registration area associated with a mobile terminal portion of the mobile network node.

34. The core network node of any one of claims 30-33, the processing circuitry further operable to: transmit to the mobile network node an indication of one or more conditions under which the mobile network node is to transmit an indication to the core network node that a location of the mobile network node has changed.

35. The core network node of claim 34, wherein the condition comprises any one or more of: an indication of a geographical position of the mobile network node obtained from a location service has changed; a threshold amount of time has elapsed since receiving the first configuration; a mobility event for a mobile terminal portion of the mobile network node has occurred; a congestion-based policy triggers an indication; and a way point along a preconfigured travel path is reached.

36. The core network node of any one of claims 30-35, wherein the first notification comprises a notifyMOIChanges message and the first configuration comprises a notifyMOIAttributeValueChanges message.

37. The core network node of any one of claims 30-36, wherein the core network node comprises an operations, administration, and management (0AM) network node.

38. The core network node of any one of claims 30-37, wherein the mobile network node comprises one of a wireless access backhaul (WAB) network node or a mobile integrated access and backhaul (mlAB) network node.