Authorization of ran nodes with wireless backhaul

Abstract

According to some embodiments, a method is performed by a wireless access backhaul (WAB) network node. The WAB network node comprises a WAB-base station and a WAB-mobile terminal (WAB-MT). The method comprises: connecting, by the WAB-MT, to a backhaul (BH)-core network; establishing, by the WAB-MT, one or more protocol data unit sessions with the BH-core network to provide the WAB-base station with connectivity to one or more WAB-core network nodes; connecting, by the WAB-base station, to one of the one or more WAB-core network nodes; receiving, by the WAB-base station, a service authorization indication from the one of the one or more WAB-core network nodes; and serving, by the WAB-base station, one or more user equipment (UEs).

Description

Authorization of RAN Nodes with Wireless BackhaulTECHNICAL FIELD

[0001] The present disclosure generally relates to communication networks, and more specifically to authorization 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 onresource 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] The NG Application Protocol (NGAP) is the application protocol used in the communication between gNB and access and mobility management function (AMF). The NG interface supports (amongst others): procedures to establish, maintain and release NG-RAN part of PDU sessions; procedures to perform intra-radio access technology (RAT) handover and inter- RAT handover; the separation of each UE on the protocol level for user specific signaling management; and the transfer of non-access stratum (NAS) signaling messages between UE and AMF.

[0012] The AMF handles control plane functions like registration management, connection management, reachability management, mobility management and access authentication.

[0013] In Rel-18, 3GPP specified authorization handling for (mobile) integrated access and backhaul (lAB)-nodes, which is applicable to both static and mobile lAB-nodes (mlAB-nodes). The handling accounts for the scenarios where the (m)IAB-MT and (m)IAB-DU part of the IAB- node are served by either a different or by the same (m)IAB-donor. The handling consists of the following general steps:1. The authorization status of an IAB-MT changes from “authorized” to “not authorized.”2. The AMF informs the lAB-donor-CU (serving the (m)IAB-MT) and the IAB-MT of the new authorization status. a. If the IAB-MT and IAB-DU part of the lAB-node are served by different donors, the lAB-MT’s donor-CU informs the lAB-DU’s donor-CU.3. The UEs served by the lAB-node are handed over by the lAB-DU’s donor to other RAN nodes.4. The Fl connection between the IAB-DU and the donor-CU serving the IAB-DU is removed. a. If the IAB-MT and IAB-DU part of the lAB-node are served by different donors, the lAB-DU’s donor-CU requests the lAB-MT’s donor-CU to remove the backhaul connectivity towards the IAB-MT.5. The lAB-MT’s donor-CU informs the AMF that the above steps are complete, so that the AMF can de-register the IAB-MT from the network, if needed.

[0014] One inherent feature of the above handling, captured in steps 3-5, is that the handling is orderly, i.e., an unauthorized node is removed from the network in an orderly manner. In other words, the continuity of UE connectivity is ensured by first handing over the UEs to other (authorized) RAN nodes, followed by the removal of the Fl connection in an orderly manner.

[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] It is expected that the authorization status of WAB nodes will change frequently. For example, WAB nodes may be authorized to operate only during certain times of day or only in certain areas.

[0017] 3GPP has previously specified authorization handling framework for (mobile) IAB nodes, in which the authorization status formally pertains to the WAB-MT. The (mobile) IAB node authorization framework was described above, and the main principles followed therein are as follows. An unauthorized node should be prevented from serving the UEs. This requires the removal of the Fl interface between the donor and the (mobile) IAB-DU. The UEs served by the (mobile) lAB-node whose authorization status changed from “authorized” to “not authorized” are handled in an orderly manner, meaning that, prior to the removal of the Fl interface of the (m)IAB- DU, the network attempts to hand them over to other network nodes. If that is not feasible, the UEs may be released.

[0018] According to the Rel-19 SID, as shown in Figure 1, the AMF(s) serving the WAB- gNB and the BH-AMF serving the WAB-MT may be different (and these AMFs may be in the same or different PLMNs). Consequently, the (mobile) lAB-node authorization framework, in which the authorization status pertains to the MT part of the node, may not be suitable for WAB- nodes, for several reasons.The WAB-node and the UEs may be served by more than one WAB-AMF (e.g., several AMFs in an AMF set). Then, it is unclear: to which of the WAB-AMFs the BH-AMF should indicate that the WAB-MT is not authorized; how the BH-AMF should obtain the “contact details” of the WAB-AMF; and which N14 signaling should be used to deliver the indication. Current inter-AMF N14 signaling is UE-associated, while the indication would pertain to the entire WAB- node, rather than to any individual UE served by it. Another reason why UE-associated signaling may not be suitable is that the WAB-MT may not be formally associated to any WAB-AMFs.

[0019] Another problem is that in roaming scenarios, the WAB-MT and WAB-gNB may be connected to different PLMNs. In that sense, authorization of the WAB-MT and authorization of WAB-gNB in two PLMNs should not be linked, as these are two separate networks.

[0020] Another problem is that if the authorization status pertains to the WAB-MT, this implies that the BH link of the WAB-node shall use the 3 GPP radio interface. On the other hand, given that the PLMN coverage is not global, there exist benefits in allowing the BH link to use any of the available radio access technologies, even non-3GPP ones, such as, e.g., proprietary NTN IP connectivity or Wi-Fi. This is especially beneficial for providing coverage at desolate places, such as open seas.

[0021] Based on the above, WAB-nodes require an authorization handling framework different than the one specified for (mobile) lAB-nodes. For example, methods not relying on the authorization status pertaining to the MT part of the node.SUMMARY

[0022] As described above, certain challenges currently exist with authorization 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.

[0023] For example, particular embodiments include methods for authorization handling of wireless access backhaul (WAB)-nodes, and are appliable to any kind of moving base stations with wireless backhaul.

[0024] A first group of embodiments includes methods for WAB-gNB authorization when the WAB-gNB connects to the network. Herein, the operations, administration, and management (0AM) node is responsible for service authorization of the WAB-gNB.

[0025] A second group of embodiments includes methods for WAB-gNB authorization when the WAB-gNB connects to the network, where the core network is responsible for service authorization of the WAB-gNB.

[0026] A third group of embodiments includes methods for handling WAB-gNB authorization when the WAB-gNB authorization status changes from “authorized” to “not authorized,” where the 0 AM is responsible for service authorization of the WAB-gNB.

[0027] A fourth group of embodiments includes methods for handling WAB-gNB authorization when the WAB-gNB authorization status changes from “authorized” to “not authorized,” where the core network is responsible for service authorization of the WAB-gNB.

[0028] A fifth group of embodiments includes methods for handling WAB-gNB authorization when the WAB-gNB authorization status changes from “not authorized” to “authorized,” where the 0 AM is responsible for service authorization of the WAB-gNB.

[0029] A sixth group of embodiments includes methods for handling WAB-gNB authorization when the WAB-gNB authorization status changes from “not authorized” to “authorized,” where the core network is responsible for service authorization of the WAB-gNB.

[0030] According to some embodiments, a method is performed by a WAB network node. The WAB network node comprises a WAB-base station and a WAB-MT. The method comprises: connecting, by the WAB-MT, to a backhaul (BH)-core network; establishing, by the WAB-MT, one or more protocol data unit sessions with the BH-core network to provide the WAB-base stationwith connectivity to one or more WAB-core network nodes; connecting, by the WAB-base station, to one of the one or more WAB-core network nodes; receiving, by the WAB-base station, a service authorization indication from the one of the one or more WAB-core network nodes; and serving, by the WAB-base station, one or more user equipment (UEs).

[0031] In particular embodiments, connecting, by the WAB-base station, to one of the one or more WAB-core network nodes comprises connecting to a WAB- 0AM core network node; and receiving, by the WAB-base station, a service authorization indication from the one of the one or more WAB-core network nodes comprises receiving the service authorization indication from the WAB-OAM core network node.

[0032] In particular embodiments, the method further comprises transmitting, by the WAB- base station, a connection setup request to a WAB-access and mobility management (AMF) core network node.

[0033] In particular embodiments, connecting, by the WAB-base station, to one of the one or more WAB-core network nodes comprises connecting to a WAB-access and mobility management (AMF) core network node; and receiving, by the WAB-base station, a service authorization indication from one of the one or more WAB-core network nodes comprises receiving the service authorization indication from the WAB -AMF core network node.

[0034] In particular embodiments, the method further comprises transmitting, by the WAB- MT, an identifier of a BH-core network node and an identifier of the WAB-MT to the WAB-base station and transmitting, by the WAB-base station, the identifier of the BH-core network node and the identifier of the WAB-MT to the WAB-AMF core network node.

[0035] In particular embodiments, receiving, by the WAB-base station, the service authorization indication from the WAB-core network node further comprises receiving a service authorization configuration from the WAB-core network node, the service authorization configuration comprising one or more service authorization policies indicating conditions under which service authorization is valid. In particular embodiments, the service authorization policies comprise one or more of: a time-based policy; a location-based policy; an event-based policy; and a congestion-based policy.

[0036] In particular embodiments, the method further comprises: obtaining, by the WAB-base station, a service unauthorization indication; handing over or releasing, by the WAB-base station, the one or more served UEs; and removing, by the WAB-base station, one or more connections with one or more WAB-core network nodes.

[0037] In particular embodiments, obtaining the service unauthorization indication comprises receiving the service unauthorization indication from one of the one or more WAB-core network nodes or determining, based on one or more service authorization policies, that the WAB-base station is service unauthorized.

[0038] In particular embodiments, the method further comprises deregistering the WAB-MT.

[0039] In particular embodiments, the method further comprises obtaining, by the WAB-base station, a service authorization indication and establishing, by the WAB-MT, one or more protocol data unit sessions with the BH-core network to provide the WAB-base station with connectivity to one or more WAB-core network nodes.

[0040] In particular embodiments, obtaining the service authorization indication comprises receiving the service authorization indication from one of the one or more WAB-core network nodes or determining, based on one or more service authorization policies, that the WAB-base station is service authorized.

[0041] In particular embodiments, the method further comprises connecting, by the WAB- MT, to the BH-core network.

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

[0043] 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 network node described above.

[0044] Certain embodiments may provide one or more of the following technical advantages. For example, particular embodiments enable the authorization handling of WAB nodes, minimize the impact to core network (CN), e.g., by avoiding the need for communication between the BH- AMF and WAB-AMF(s) and ensure the continuity of UE connectivity when a WAB -node becomes unauthorized.BRIEF DESCRIPTION OF THE DRAWINGS

[0045] 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; andFigures 5A and 5B are a flowchart illustrating an example method in a WAB network node, according to certain embodiments.DETAILED DESCRIPTION

[0046] As described above, certain challenges currently exist with authorization 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, particular embodiments include methods for authorization handling of wireless access backhaul (WAB)- nodes, and are appliable to any kind of moving base stations with wireless backhaul.

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

[0048] Particular embodiments are presented with the example of WAB-nodes, but are applicable to any kind of moving base station with wireless backhaul.

[0049] Particular embodiments apply to both of the following cases: (a) the WAB-gNB and the gNB serving the WAB-mobile terminal (MT) are served by the same public land mobile network (PLMN) core network (CN) nodes; and (b) the WAB-gNB and the gNB serving the WAB- MT are served by different CN nodes, in the same or different PLMN.

[0050] Particular embodiments may apply to WAB-nodes with both single- and dualconnected WAB-MTs.

[0051] Particular embodiments apply to both the case when all user equipment (UEs) connected to the WAB-gNB are served by the same access and mobility management function (AMF), and the case where multiple AMFs serve the UEs.

[0052] Particular embodiments may be implemented by means of new procedures or by enhancing existing procedures.

[0053] The terms “UE-AMF” and “WAB-AMF”, as well as the “UE-5GC” and “WAB-5GC” are used interchangeably.

[0054] The terms “network” and “PLMN” are used interchangeably.

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

[0056] The terms “not authorized” and “unauthorized” are used interchangeably.

[0057] The meaning of “X served by Y” or “X is connected to Y” is that there exists a logical interface connection between network elements X and Y. When X is a UE, this means that nodeY and the radio access network (RAN) node serving the UE have a logical connection associated to the UE.

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

[0059] Particular embodiments are focused on authorization handling of a WAB-node, and may include the following scenarios: (a) service authorization of a WAB-node when the node connects to the network; (b) the service authorization status of the WAB-node changes from “authorized” to “not authorized;” and (c) the service authorization status of the WAB-node changes from “not authorized” to “authorized.”

[0060] The assumed architecture is the one from Figure 1 with an additional assumption in some embodiments that the AMF(s) serving the UEs (i.e., the WAB-AMFs, which are a part of the UE-5GC), and the AMF serving the WAB-MT (BH-AMF) may be the same, or different. If different, they may be in the same or in different PLMNs.

[0061] According to particular embodiments, the authorization status of the WAB-node pertains to the WAB-gNB. The authorization refers to service authorization, which determines whether the node has the mandate to serve UEs. This is different from security authorization, which determines whether it is secure to allow a device to access the network. However, the applicability of other meanings of authorization is not precluded.

[0062] The embodiments may be used individually or in a combination.

[0063] Some steps in particular embodiments may be executed in an order different than presented, and some steps may be optional, regardless of whether the optionality is explicitly indicated.

[0064] Some embodiments include service authorization when the WAB-node connects to the network. In a first group of embodiments, the 0AM is responsible for service authorization of the WAB-node. When the WAB-node connects to the network, the steps are as follows.

[0065] The WAB-MT connects to the backhaul (BH) network. This can be like a normal UE. The WAB-MT establishes one or more protocol data unit (PDU) sessions that can be used later to carry the traffic for the connections of the WAB-gNB to / from the security gateway, the 0 AM, and other network nodes.

[0066] In some embodiments, the network serving the WAB-MT, i.e., the BH network, can be the same as the network to which the WAB-gNB will connect. In some embodiments, the networks are different.

[0067] Security authentication and authorization of the WAB-gNB is performed, between the WAB-gNB and the security gateway (SecGW). If this step is executed successfully, the WAB- node is considered as trusted node and it is allowed to set up a session with the right 0AM server. In some embodiments, the security authentication and authorization may be done by the 0AM.

[0068] The WAB-gNB connects to the 0AM, which then configures the WAB-gNB.

[0069] In some embodiments, during configuration, the service authorization of the WAB node is performed. The service authorization may be provided by the 0AM server, e.g., as part of the configuration management (CM) data.

[0070] Service authorization implies a check of whether the WAB-node has the right to serve UEs, and the conditions under which such mandate is valid (i.e., policies).

[0071] In some embodiments, the 0AM system may provide service authorization that includes time-based, event-based and / or location-based policies to the WAB node.

[0072] The WAB-node implementation shall follow the configuration received from the 0AM server, including the policies.

[0073] A non-limiting example of a time-based policy is that configuration is valid only within or outside a certain period (one-time or recurring).

[0074] A non-limiting example of a location-based policy is that configuration is valid only within or outside a certain area (e.g., tracking area (TA) or group of cells).

[0075] A non-limiting example of event-based policy is that a WAB-node onboard an airplane may be enabled at takeoff and disabled at landing.

[0076] In some embodiments, policies based on other types of criteria (e.g., congestion) may be provided.

[0077] In some embodiments, different policies may be used jointly, e.g., a combination of time- and location-based policies.

[0078] A non-limiting example of a location-based policy is that configuration is valid only within or outside a certain geographical area (e.g., a harbor).

[0079] In some embodiments, the service authorization may be provided by the 0AM server, separately from the CM data.

[0080] In some embodiments, during service authorization, the policies for service authorization are optionally provided, i.e., the policies may or may not be provided.

[0081] In some embodiments, the positive / negative acknowledgement with respect to WAB- node service authorization sent to the WAB node is explicit, while, in some embodiments, it is implicit.

[0082] For example, if the 0AM does not provide the configuration to the node, that implicitly means that the service authorization of node failed, and vice versa.

[0083] In some embodiments, the service authorization may be provided by the SeGW.

[0084] The WAB-gNB initiates the NG connection setup by sending an NG SETUPREQUEST message to one or more WAB-AMFs. If accepted, the NG connection between the WAB-node and the AMF(s) is established. If rejected, the WAB-AMF replies with an NG SETUP FAILURE message, with an appropriate cause value.

[0085] In some embodiments, the WAB-gNB may optionally indicate its authorization status to the WAB-AMF(s), e.g., during NG connections setup or during RAN configuration update. In some embodiments, another network entity, such as, e.g., 0AM may optionally indicate the service authorization status to the WAB-AMF(s).

[0086] The WAB-node, from now on, is service -authorized and operates according to the policy as long as the conditions stipulated by the policy are satisfied.

[0087] For example, if the condition for service authorization stipulated by the policy that the node received is not fulfilled anymore, the WAB-gNB should hand over / release UEs and remove NG, if possible. So, the node is empowered to handle service authorization status change. The Xn connections of the WAB-gNB may also be removed.

[0088] In some embodiments that can be used in combination with other embodiments presented herein, the authorization of the WAB-MT may still be handled by reusing the legacy mechanism for UEs, but this is decoupled from authorization of WAB-gNB and handling of served UEs. In other words, the authorization status of the WAB-MT may not necessarily affect the authorization of the WAB-node as presented herein. If the authorization handling of WAB-MT and WAB-gNB are coupled, coordination between BH-AMF and WAB-AMF is needed.

[0089] In some embodiments, the radio technology used at the backhaul link, i.e., the wireless link between the WAB-node and the network, may be a non-3GPP radio technology. In this case, the WAB-MT PDU sessions are IP sessions, or other data sessions capable of transporting IP data.

[0090] In a second group of embodiments, the AMF or another entity in the CN is responsible for service authorization of the WAB-node (i.e., the WAB-gNB). When the WAB-node connects to the network, the steps are as follows.

[0091] The WAB-MT connects to the BH network. This can be like a normal UE. The WAB- MT establishes one or more PDU sessions which can be used later to carry the traffic for the connections of the WAB-gNB to / from the security gateway, the 0 AM, and other network nodes.

[0092] In some embodiments, the network serving the WAB-MT, i.e., the BH network, can be the same as the network to which the WAB-gNB will connect. In some embodiments, the networks are different.

[0093] The WAB-MT provides the BH-AMF information (e.g., globally unique AMF identifier (GUAMMI) of the BH-AMF and the global unique temporary identifier (GUTI) of the WAB-MT) to the WAB-gNB.

[0094] Security authentication and authorization of the WAB-gNB is performed, between the WAB-gNB and the SecGW. The WAB-gNB connects to the SecGW. If this step is executed successfully, the WAB-node is considered as trusted node and it is allowed to set up a session with the right 0AM server, which then configures the WAB-gNB. In some embodiments, the security authentication and authorization may be done by the 0AM.

[0095] Service authorization of the WAB-gNB is done by the WAB-AMF. This can be done, e.g., in conjunction with the NG connection setup. The WAB-gNB initiates the NG connection setup by sending an NG SETUP REQUEST message to one or more WAB-AMFs.

[0096] In some embodiments, the WAB-AMF is informed about the authorization status of the WAB-gNB, and, optionally, about the policies, by another entity (e.g., it is informed by the 0AM or an entity in the CN), or it is provided with the information based on which it can derive and manage the authorization and / or the policies.

[0097] In some embodiments, the WAB-gNB provides the BH-AMF information (e.g., GUAMMI of the BH-AMF and GUTI of the WAB-MT) to one or more WAB-AMFs. The WAB- AMF identifies the BH-AMF (e.g., based on GUAMMI) and communicates with the BH-AMF to retrieve the authorization status of the WAB-MT (e.g., based on GUTI of the WAB-MT). New service or new service operation (e.g., as part of the Namf_Communication service) is defined to retrieve the WAB-MT authorization status.

[0098] If the authorization by the WAB-AMF is successful (e.g., considering the authorization status from the BH-AMF and the current time and location of the WAB node), the WAB-AMF approves the NG connection setup request and indicates to the WAB node that it is authorized.

[0099] In some embodiments, together with the authorization status, the WAB-AMF may provide to the WAB-gNB, e.g., time-based, event-based and / or location-based policies for service authorization.

[0100] The WAB-node implementation shall follow the configuration received from the WAB-AMF server, including the policies.

[0101] A non-limiting example of a time-based policy is that configuration is valid only within or outside a certain period (one-time or recurring).

[0102] A non-limiting example of a location-based policy is that configuration is valid only within or outside a certain area (e.g., TA or group of cells).

[0103] A non-limiting example of event-based policy is that a WAB-node onboard an airplane may be enabled at takeoff and disabled at landing.

[0104] In some embodiments, policies based on other types of criteria (e.g., congestion) may be provided.

[0105] In some embodiments, different policy types may be used jointly, e.g., a combination of time- and location-based policies.

[0106] A non-limiting example of a location-based policy is that configuration is valid only within or outside a certain geographical area (e.g., a harbor).

[0107] In some embodiments, during service authorization, the policies for service authorization are optionally provided, i.e., the policies may or may not be provided.

[0108] In some embodiments, the positive / negative acknowledgement with respect to WAB- node authorization sent to the WAB node is explicit, while, in some embodiments, it is implicit. For example, if NG connection setup is rejected, the WAB-AMF replies with an NG SETUP FAILURE message, with an appropriate cause value.

[0109] In some embodiments, the WAB-gNB initiates the NG connection setup towards more than one WAB-AMFs, but only one WAB-AMF is responsible for authorization.

[0110] In some embodiments, which WAB-AMF is responsible for authorization may be configured at the WAB-AMF by the 0AM or by some other entity.[oni] In some embodiments, the WAB-gNB may be configured (e.g., by 0AM) with the information about which of the WAB-AMFs it is connecting to is responsible for service authorization.

[0112] In some embodiments, the authorization may be done separately from the NG setup procedure, e.g., during RAN configuration update.

[0113] In some embodiments, the WAB-AMF is involved in the service authorization by assisting another entity that is the main responsible entity for service authorization, e.g., another CN function.

[0114] In some embodiments, the service authorization may be provided by the SeGW.

[0115] In some embodiments, the service authorization policies are provided by the 0AM, but the WAB-AMF provides service authorization and enforces the policies.

[0116] The WAB-node, from now on, is service -authorized and operates according to the policy as long as the conditions stipulated by the policy are satisfied.

[0117] In some embodiments, the WAB-node is responsible for enforcing the policies, i.e., for determining and changing its service authorization status based on the policies.

[0118] For example, if the condition for service authorization stipulated by the policy that the node received with the configuration is not fulfilled anymore, the WAB-gNB should hand over / release UEs and, optionally, remove its NG connections. The Xn connections of the WAB- gNB may also be removed. So, the node is empowered to handle service authorization status change.

[0119] In some embodiments, the WAB-AMF is responsible for enforcing the policies, i.e., for determining and changing the service authorization status of the WAB-gNB based on the policies, and for informing and handling the WAB-gNB accordingly.

[0120] In some embodiments, the BH-AMF may also be (one of the) WAB-AMFs. In some embodiments, these can be two different AMFs.

[0121] In some embodiments, that may be used in the combination with other embodiments presented herein, the authorization of the WAB-MT may still be handled by reusing the legacy mechanism for UEs, but this is decoupled from authorization of WAB-gNB and handling of served UEs. In other words, the authorization status of the WAB-MT may not necessarily affect the authorization of the WAB-node as presented herein. When the authorization handling of WAB- MT and WAB-gNB are coupled, coordination between BH-AMF and WAB-AMF is needed.

[0122] In some embodiments, the radio technology used at the backhaul link, i.e., the wireless link between the WAB-node and the network, may be a non-3GPP radio technology. In this case, the WAB-MT PDU sessions are IP sessions, or other data sessions capable of transporting IP data.

[0123] Some embodiments include service authorization status of the WAB-node changes from “authorized” to “not authorized.” In a third group of embodiments, when the WAB-gNB is responsible for enforcing the policies related to service authorization, when the service authorization status of WAB-node changes from “authorized” to “not authorized,” the steps are as follows.

[0124] If / when the condition(s) for service authorization, e.g., stipulated by a policy, is (are) not fulfilled anymore, proper handling is needed. For example, based on a preconfigured policy, the WAB-gNB determines that the authorization status is about to / has become “not authorized.”

[0125] The WAB-gNB attempts to hand over the served UEs. The UEs that cannot be handed over can be released.

[0126] The removal of the NG connection(s) of the WAB-gNB is initiated.

[0127] In some embodiments, the WAB-gNB initiates NG removal towards the WAB- AMF(s). Optionally, the cause for removal may be indicated. The WAB-AMF(s) confirm the NG connection removal.

[0128] In some embodiments, one or more WAB-AMF(s) is / are informed (e.g., by the 0AM) about the authorization status change to “not authorized”. The WAB-AMF(s) then initiate the removal of NG connection(s).

[0129] In some embodiments, the Xn connections of the WAB-gNB may also be removed.

[0130] Optionally, after the above steps have been completed, the WAB-gNB and / or the WAB-MT may be de-registered from the network.

[0131] In some embodiments for WAB-gNB, after the NG connection(s) of the WAB-gNB have been removed, the WAB-gNB may be de-registered by the network.

[0132] In some embodiments for WAB-MT, after the NG connection(s) of the WAB-gNB have been removed, the BH-AMF may be informed accordingly by the WAB-MT, by the WAB- AMF(s) or by another entity in the network, and the WAB-MT may be de-registered.

[0133] In some embodiments, after the status of the WAB-gNB is changed to “not authorized,” some or all the PDU sessions of the WAB-MT used for carrying the traffic to / from WAB-gNB may be removed.

[0134] In some embodiments, the BH-AMF may also be (one of the) WAB-AMFs. In some embodiments, these may be two different AMFs.

[0135] In some embodiments, that can be used in combination with other embodiments presented herein, the authorization of the WAB-MT may still be handled by reusing the legacy mechanism for UEs, but this is decoupled from authorization of WAB-gNB and handling of served UEs. In other words, the authorization status of the WAB-MT may not necessarily affect the authorization of the WAB-node as presented herein. When the authorization handling of WAB- MT and WAB-gNB are coupled, coordination between BH-AMF and WAB-AMF is needed.

[0136] In some embodiments, the radio technology used at the backhaul link, i.e., the wireless link between the WAB-node and the network, may be a non-3GPP radio technology. In this case, the WAB-MT PDU sessions are IP sessions, or other data sessions capable of transporting IP data.

[0137] In some embodiments, when the service authorization status of WAB-node changes from “authorized” to “not authorized,” the node may retain its SecGW connection for 0AM and the connection to the 0AM itself. The 0AM may be informed about service authorization change of the WAB-node.

[0138] In a fourth group of embodiments, when the WAB-AMF or another CN entity is responsible for enforcing the policies related to service authorization, when the service authorization status of WAB-node changes from “authorized” to “not authorized,” the steps are as follows (a non-limiting example when WAB-AMF is handling authorization):

[0139] If / when the condition(s) for service authorization stipulated by the policy is (are) not fulfilled anymore, proper handling is needed. Based on the preconfigured policy, the WAB-AMF determines that the authorization status is about to / has become “not authorized.”

[0140] The WAB-AMF informs the WAB-gNB about authorization status change.

[0141] The WAB-gNB attempts to hand over the served UEs. The UEs that cannot be handed over may be released.

[0142] The removal of the NG connection(s) of the WAB-gNB is initiated.

[0143] In some embodiments, once all UEs have been handed over or released, the WAB- gNB initiates NG removal towards the WAB-AMF(s). Optionally, the cause for removal may be indicated. The WAB-AMF(s) confirm the NG connection removal.

[0144] In some embodiments, once all UEs have been handed over or released, the WAB- gNB informs the WAB-AMF(s), which then initiate the removal of NG connection(s).

[0145] In some embodiments, the Xn connections of the WAB-gNB may also be removed.

[0146] Optionally, in some embodiments, after the above steps have been completed, the WAB-gNB and / or the WAB-MT may be de-registered from the network.

[0147] In some embodiments for WAB-gNB, after the NG connection(s) of the WAB-gNB have been removed, the WAB-gNB may be de-registered by the network.

[0148] In some embodiments for WAB-MT, after the NG connection(s) of the WAB-gNB have been removed, the BH-AMF may be informed accordingly by the WAB-MT, by the WAB- AMF(s) or by another entity in the network, and the WAB-MT may be de-registered.

[0149] In some embodiments, after the status of the WAB-gNB is changed to “not authorized,” some or all the PDU sessions of the WAB-MT used for carrying the traffic to / from WAB-gNB may be removed.

[0150] In some embodiments, the BH-AMF may also be (one of the) WAB-AMFs. In some embodiments, these can be two different AMFs.

[0151] To enable the BH-AMF and the WAB-AMF to communicate, in some embodiments, the WAB-gNB provides the BH-AMF information (e.g., GUAMMI of the BH-AMF and GUTI of the WAB-MT) to one or more WAB-AMFs. The WAB-AMF identifies the BH-AMF (e.g., based on GUAMMI) and communicates with the BH-AMF to retrieve the authorization status of theWAB-MT (e.g., based on GUTI of the WAB-MT). New service or new service operation (e.g., as part of the Namf_Communication service) is defined to retrieve the WAB-MT authorization status.

[0152] In some embodiments, that may be used in combination with other embodiments presented herein, the authorization of the WAB-MT may still be handled by reusing the legacy mechanism for UEs, but this is decoupled from authorization ofWAB-gNB and handling of served UEs. In other words, the authorization status of the WAB-MT may not necessarily affect the authorization of the WAB-node as presented herein. If the authorization handling of WAB-MT and WAB-gNB are coupled, coordination between BH-AMF and WAB-AMF is needed.

[0153] In some embodiments, the radio technology used at the backhaul link, i.e., the wireless link between the WAB-node and the network, may be a non-3GPP radio technology. In this case, the WAB-MT PDU sessions are IP sessions, or other data sessions capable of transporting IP data.

[0154] Some embodiments include handling of service authorization status change from “not authorized” to “authorized.” In a fifth group of embodiments, when, based on the policy, the WAB- gNB determines that its authorization status should be changed from “not authorized” to “authorized,” the node acts depending on how the handling was done when the status previously changed from “authorized” to “not authorized.”

[0155] If the WAB-MT has previously been de-registered due to WAB-gNB authorization status change to “not authorized,” once the status becomes “authorized” the WAB-MT connects to the network, the WAB-gNB establishes connection to the 0AM system, undergoes (service) authorization and establishes NG connection(s).

[0156] If the WAB-MT has not been de-registered due to WAB-gNB authorization status change to “not authorized” (but, instead, remained in the network), once the status becomes “authorized” the steps are as follows.

[0157] In some embodiments, the WAB-gNB may inform the WAB-MT about WAB-gNB authorization status change, and the WAB-MT may set up one or more PDU sessions of WAB- gNB traffic. The WAB-gNB may then use the PDU sessions to connect to the SecGW, the 0AM, WAB-AMF(s) and other relevant nodes.

[0158] In some embodiments, e.g., when the previous authorization status change of the WAB-gNB did not affect the WAB-MT (i.e., the WAB-MT remained registered and kept its PDU sessions), no action is required from the WAB-MT. The WAB-gNB can then use the PDU sessions to connect to the SecGW, the 0AM, WAB-AMF(s) and other relevant nodes. In some embodiments, it may be so that the SecGW connection for connecting 0AM has been kept even when the service authorization status of the WAB node became “not authorized.”

[0159] In some embodiments, the WAB-MT is informed about WAB-gNB authorization status change by the BH-AMF, which, may have received this information from another entity, e.g., the OAM or the WAB-AMF(s). Based on this information, the WAB-MT may set up one or more PDU sessions for the traffic of WAB-gNB, and the WAB-gNB may then use the PDU sessions to connect to the SecGW, the OAM, WAB-AMF(s) and other relevant nodes.

[0160] In some embodiments, the BH-AMF may also be (one of the) WAB-AMFs. In some embodiments, these may be two different AMFs.

[0161] To enable the BH-AMF and the WAB-AMF to communicate, in some embodiments, the WAB-gNB provides the BH-AMF information (e.g., GUAMMI of the BH-AMF and GUTI of the WAB-MT) to one or more WAB-AMFs. The WAB-AMF identifies the BH-AMF (e.g., based on GUAMMI) and communicates with the BH-AMF to retrieve the authorization status of the WAB-MT (e.g., based on GUTI of the WAB-MT). New service or new service operation (e.g., as part of the Namf_Communication service) is defined to retrieve the WAB-MT authorization status.

[0162] In a sixth group of embodiments, when, based on the policy, the WAB-AMF or anotherCN entity determines that its service authorization status should be changed from “not authorized” to “authorized,” the node is handled depending on how the handling was done when the status previously changed from “authorized” to “not authorized.”

[0163] If the WAB-MT has not been de-registered due to WAB-gNB authorization status change to “not authorized” (but, instead, remained in the network), once the status becomes “authorized” the steps are as follows:

[0164] In some embodiments, the WAB-AMF may inform the BH-AMF about WAB-gNB authorization status change, and the BH-AMF may inform the WAB-MT. Then the WAB-MT can, if needed, set up one or more PDU sessions for WAB-gNB’s traffic, and inform the WAB-gNB about the WAB-gNB authorization status change. The WAB-gNB can then use the PDU sessions to connect to the SecGW, the OAM, WAB-AMF(s) and other relevant nodes.

[0165] In some embodiments, the WAB-AMF may receive the information about WAB-gNB authorization status change from another entity, e.g., the OAM or a CN entity.

[0166] In some embodiments, the BH-AMF may also be (one of the) WAB-AMFs. In some embodiments, these may be two different AMFs.

[0167] To enable the BH-AMF and the WAB-AMF to communicate, in some embodiments, the WAB-gNB provides the BH-AMF information (e.g., GUAMMI of the BH-AMF and GUTI of the WAB-MT) to one or more WAB-AMFs. The WAB-AMF identifies the BH-AMF (e.g., based on GUAMMI) and communicates with the BH-AMF to retrieve the authorization status of theWAB-MT (e.g., based on GUTI of the WAB-MT). New service or new service operation (e.g., as part of the Namf_Communication service) is defined to retrieve the WAB-MT authorization status.

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

[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 besubstantially 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).

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

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

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

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

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

[0177] 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 stillconnected 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.

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

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

[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 any combination 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), erasableprogrammable 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, LPWANcommunication, 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 / 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.

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

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

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

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

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

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

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

[0200] 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 maycollect 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.

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

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

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

[0204] 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 maycomprise 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.

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

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

[0207] Figures 5A and 5B are a flowchart illustrating an example method 500 in a WAB network node, according to certain embodiments. In particular embodiments, one or more steps of Figures 5A and 5B may be performed by network node 300 described with respect to Figure 3. The WAB network node comprises a WAB-base station and a WAB-MT.

[0208] In general steps 512-526 illustrate an example of service authorization of the WAB network node when the WAB network node connects to the network. Steps 528-534 illustrate an example of when the service authorization status of the WAB network node changes from authorized to unauthorized. Steps 536-540 illustrate an example of when the service authorization status of the WAB network node changes from unauthorized to authorized.

[0209] The method 500 begins at step 512, where the WAB network node (e.g., network node 300) connects, by the WAB-MT, to a backhaul (BH)-core network. As described above, this is similar to a regular UE connecting to the network.

[0210] At step 514, the WAB network nodes establishes, by the WAB-MT, one or more protocol data unit sessions with the BH-core network to provide the WAB-base station with connectivity to one or more WAB-core network nodes. For example, one or more PDU sessions may be used later to carry the traffic for the connections of the WAB-base station to / from the security gateway, the 0AM, and other network nodes.

[0211] In some embodiments, the network serving the WAB-MT, i.e., the BH network, may be the same as the network to which the WAB-base station will connect. In some embodiments, the networks are different.

[0212] At step 516, the WAB network node may transmit, by the WAB-MT, an identifier of a BH-core network node and an identifier of the WAB-MT to the WAB-base station. For example, as described above, in some embodiments the WAB-base station may connect to an 0AM server for service authorization (e.g., first group of embodiments), and in some embodiments the WAB- base station may connect to a WAB-AMF for service authorization (e.g., second group of embodiments). When connecting to a WAB-AMF, the WAB-base station may want to send the identifier of a BH-core network node and an identifier of the WAB-MT so that the WAB-AMF may communicate with those entities.

[0213] As used herein, because the WAB-MT and WAB-base station may coexist on the same network node, “transmitting” between the WAB-MT and WAB-base station may be through internal messaging within the WAB network node.

[0214] At step 518, the WAB network node connects, by the WAB-base station, to one of the one or more WAB-core network nodes.

[0215] In particular embodiments, connecting, by the WAB-base station, to one of the one or more WAB-core network nodes comprises connecting to a WAB-OAM core network node. Connecting to the WAB-OAM core network node is described in more detail above with respect to the first group of embodiments.

[0216] In particular embodiments, connecting, by the WAB-base station, to one of the one or more WAB-core network nodes comprises connecting to a WAB-AMF core network node. Connecting to the WAB-AMF core network node is described in more detail above with respect to the second group of embodiments.

[0217] At step 520, the WAB network node may transmit, by the WAB-base station, the identifier of the BH-core network node and the identifier of the WAB-MT to the WAB-AMF core network node. A described above with respect to optional step 516, the WAB-base station maywant to send the identifier of a BH-core network node and an identifier of the WAB-MT so that the WAB-AMF may communicate with those entities.

[0218] At step 522, the WAB network node may transmit, by the WAB-base station, a connection setup request to a WAB-AMF core network node. For example, regarding the first group of embodiments where the WAB-base station connects to an 0AM server for service authorization, the WAB base station then connects to the WAB-AMF. In other embodiments, such as the second group of embodiments where the WAB-base station connects to an AMF for service authorization, step 522 may be skipped because the WAB-base station already connected to the WAB-AMF at step 518.

[0219] At step 524, the WAB network node receives, by the WAB-base station, a service authorization indication from the one of the one or more WAB-core network nodes.

[0220] In particular embodiments, receiving, by the WAB-base station, a service authorization indication from the one of the one or more WAB-core network nodes comprises receiving the service authorization indication from the WAB-OAM core network node (e.g., first group of embodiments described above).

[0221] In particular embodiments, receiving, by the WAB-base station, the service authorization indication from the WAB-core network node further comprises receiving a service authorization configuration from the WAB-core network node, the service authorization configuration comprising one or more service authorization policies indicating conditions under which service authorization is valid. In particular embodiments, the service authorization policies comprise one or more of: a time-based policy; a location-based policy; an event-based policy; and a congestion-based policy.

[0222] In particular embodiments, receiving, by the WAB-base station, a service authorization indication from the one of the one or more WAB-core network nodes comprises receiving the service authorization indication from the WAB-AMF core network node (e.g., second group of embodiments described above).

[0223] At step 526, the WAB network node serves, by the WAB-base station, one or more UEs. At this point, the WAB network node is service authorized. The WAB network node may continue serving UEs until the service authorization status of the WAB network node changes from authorized to unauthorized.

[0224] At step 528, the WAB network node may obtain, by the WAB-base station, a service unauthorization indication. In particular embodiments, obtaining the service unauthorization indication comprises receiving the service unauthorization indication from one of the one or moreWAB-core network nodes (e.g., fourth group of embodiments where receiving the indication comprises receiving the indication from the WAB-AMF) or determining, based on one or more service authorization policies, that the WAB-base station is service unauthorized (e.g., third group of embodiments where WAB network node receives policies from the OAM server or other network node and determines its own authorization status based on the policies).

[0225] At step 530, the WAB network node may hand over or release, by the WAB-base station, the one or more served UEs. For example, in preparation for an orderly transition to service unauthorized, the WAB-base station stops serving the UEs.

[0226] At step 532, the WAB network node may remove, by the WAB-base station, one or more connections with one or more WAB-core network nodes.

[0227] At step 534, the WAB network node may deregister the WAB-MT. In other embodiments this step is skipped, and the WAB-MT may remain registered so that it is readily available when the WAB network node service authorization status changes from unauthorized to authorized.

[0228] The WAB network node refrains from serving UEs until the service authorization status of the WAB network node changes from unauthorized to authorized.

[0229] At step 536, the WAB network node may obtain, by the WAB-base station, a service authorization indication.

[0230] In particular embodiments, obtaining the service authorization indication comprises receiving the service authorization indication from one of the one or more WAB-core network nodes (e.g., sixth group of embodiments described above) or determining, based on one or more service authorization policies, that the WAB-base station is service authorized (e.g., fifth group of embodiments described above).

[0231] At step 538, the WAB network node may connect, by the WAB-MT, to the BH-core network. For example, if the WAB-MT deregistered in step 534, then the WAB-MT connects and registers at step 538.

[0232] At step 540, the WAB network node may establish, by the WAB-MT, one or more protocol data unit sessions with the BH-core network to provide the WAB-base station with connectivity to one or more WAB-core network nodes.

[0233] Modifications, additions, or omissions may be made to method 500 of Figures 5A and 5B. Additionally, one or more steps in the method of Figures 5A and 5B may be performed in parallel or in any suitable order.

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

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

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

[0237] Some example embodiments are described below.Group A Embodiments1. 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.2. The method of the previous embodiment, further comprising one or more additional wireless device steps, features or functions described above.3. 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.Group B EmbodimentsA method performed by a wireless access and backhaul (WAB) base station, the method comprising:- receiving service authorization from a network node; and- serving one or more wireless devices. The method of the previous embodiment, further comprising:- transitioning to a service unauthorized state; and- handing over one or more served wireless devices to another network node. The method of any one of the previous embodiments, wherein the service authorization is received from an operations and management (OAM) network node or an access and mobility management (AMF) network node. The method of any one of the previous three embodiments, wherein the service authorization is associated with one or more of a time-based policy, a location-based policy, and an event-triggered policy. The method of any one of the previous four embodiments, wherein the context information comprises any of the context information described in the embodiments and examples listed herein. A method performed by a wireless access and backhaul (WAB) base station, the method comprising any of the steps described with respect to the first group of embodiments above. A method performed by a wireless access and backhaul (WAB) base station, the method comprising any of the steps described with respect to the second group of embodiments above. A method performed by a wireless access and backhaul (WAB) base station, the method comprising any of the steps described with respect to the third group of embodiments above. A method performed by a wireless access and backhaul (WAB) base station, the methodcomprising any of the steps described with respect to the fourth group of embodiments above.10. A method performed by a wireless access and backhaul (WAB) base station, the method comprising any of the steps described with respect to the fifth group of embodiments above.11. A method performed by a wireless access and backhaul (WAB) base station, the method comprising any of the steps described with respect to the sixth group of embodiments above.12. 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.13. The method of the previous embodiment, further comprising one or more additional base station steps, features or functions described above.14. 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. up C Embodiments15. A mobile 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.16. A base 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

CLAIMS1. A method performed by a wireless access backhaul (WAB) network node, the WAB network node comprising a WAB-base station and a WAB-mobile terminal (WAB-MT), the method comprising: connecting (512), by the WAB-MT, to a backhaul (BH)-core network; establishing (514), by the WAB-MT, one or more protocol data unit sessions with the BH- core network to provide the WAB-base station with connectivity to one or more WAB-core network nodes; connecting (518), by the WAB-base station, to one of the one or more WAB-core network nodes; receiving (524), by the WAB-base station, a service authorization indication from the one of the one or more WAB-core network nodes; and serving (526), by the WAB-base station, one or more user equipment (UEs).

2. The method of claim 1, wherein: connecting, by the WAB-base station, to one of the one or more WAB-core network nodes comprises connecting to a WAB-operations, administration, and maintenance (0AM) core network node; and receiving, by the WAB-base station, a service authorization indication from the one of the one or more WAB-core network nodes comprises receiving the service authorization indication from the WAB-OAM core network node.

3. The method of claim 2, further comprising transmitting (522), by the WAB-base station, a connection setup request to a WAB-access and mobility management (AMF) core network node.

4. The method of claim 1, wherein: connecting, by the WAB-base station, to one of the one or more WAB-core network nodes comprises connecting to a WAB-access and mobility management (AMF) core network node; and receiving, by the WAB-base station, a service authorization indication from one of the one or more WAB-core network nodes comprises receiving the service authorization indication fromthe WAB-AMF core network node.

5. The method of claim 4, further comprising: transmitting (516), by the WAB-MT, an identifier of a BH-core network node and an identifier of the WAB-MT to the WAB-base station; and transmitting (520), by the WAB-base station, the identifier of the BH-core network node and the identifier of the WAB-MT to the WAB-AMF core network node.

6. The method of any one of claims 1-5, wherein receiving, by the WAB-base station, the service authorization indication from the WAB-core network node further comprises receiving a service authorization configuration from the WAB-core network node, the service authorization configuration comprising one or more service authorization policies indicating conditions under which service authorization is valid.

7. The method of claim 6, wherein the service authorization policies comprise one or more of: a time-based policy; a location-based policy; an event-based policy; and a congestion-based policy.

8. The method of any one of claims 1-7, further comprising: obtaining (528), by the WAB-base station, a service unauthorization indication; handing over or releasing (530), by the WAB-base station, the one or more served UEs; and removing (532), by the WAB-base station, one or more connections with one or more WAB-core network nodes.

9. The method of claim 8, wherein obtaining the service unauthorization indication comprises: receiving the service unauthorization indication from one of the one or more WAB-core network nodes; or determining, based on one or more service authorization policies, that the WAB-basestation is service unauthorized.

10. The method of any one of claims 8-9, further comprising deregistering (534) the WAB- MT.

11. The method of any one of claims 1-10, further comprising: obtaining (536), by the WAB-base station, a service authorization indication; and establishing (540), by the WAB-MT, one or more protocol data unit sessions with the BH- core network to provide the WAB-base station with connectivity to one or more WAB-core network nodes.

12. The method of claim 11, wherein obtaining the service authorization indication comprises: receiving the service authorization indication from one of the one or more WAB-core network nodes; or determining, based on one or more service authorization policies, that the WAB-base station is service authorized.

13. The method of any one of claims 11-12, further comprising connecting (538), by the WAB-MT, to the BH-core network.

14. A wireless access backhaul (WAB) network node (300) comprising a WAB-base station and a WAB-mobile terminal (WAB-MT), the WAB network node comprising processing circuitry (302) operable to: connect, by the WAB-MT, to a backhaul (BH)-core network; establish, by the WAB-MT, one or more protocol data unit sessions with the BH-core network to provide the WAB-base station with connectivity to one or more WAB-core network nodes; connect, by the WAB-base station, to one of the one or more WAB-core network nodes; receive, by the WAB-base station, a service authorization indication from the one of the one or more WAB-core network nodes; and serve, by the WAB-base station, one or more user equipment (UEs).

15. The WAB network node of claim 14, wherein the processing circuitry is operable to: connect, by the WAB-base station, to one of the one or more WAB-core network nodes by connecting to a WAB-operations, administration, and maintenance (0AM) core network node; and receive, by the WAB-base station, a service authorization indication from the one of the one or more WAB-core network nodes by receiving the service authorization indication from the WAB-OAM core network node.

16. The WAB network node of claim 15, the processing circuitry further operable to transmit, by the WAB-base station, a connection setup request to a WAB-access and mobility management (AMF) core network node.

17. The WAB network node of claim 14, wherein the processing circuitry is operable to: connect, by the WAB-base station, to one of the one or more WAB-core network nodes by connecting to a WAB-access and mobility management (AMF) core network node; and receive, by the WAB-base station, a service authorization indication from one of the one or more WAB-core network nodes by receiving the service authorization indication from the WAB -AMF core network node.

18. The WAB network node of claim 17, the processing circuitry further operable to: transmit, by the WAB-MT, an identifier of a BH-core network node and an identifier of the WAB-MT to the WAB-base station; and transmit, by the WAB-base station, the identifier of the BH-core network node and the identifier of the WAB-MT to the WAB-AMF core network node.

19. The WAB network node of any one of claims 14-18, wherein the processing circuitry is operable to receive, by the WAB-base station, the service authorization indication from the WAB-core network node by receiving a service authorization configuration from the WAB-core network node, the service authorization configuration comprising one or more service authorization policies indicating conditions under which service authorization is valid.

20. The WAB network node of claim 19, wherein the service authorization policies comprise one or more of:a time-based policy; a location-based policy; an event-based policy; and a congestion-based policy.

21. The WAB network node of any one of claims 14-20, the processing circuitry further operable to: obtain, by the WAB-base station, a service unauthorization indication; hand over or release, by the WAB-base station, the one or more served UEs; and remove, by the WAB-base station, one or more connections with one or more WAB-core network nodes.

22. The WAB network node of claim 21, wherein the processing circuitry is operable to obtain the service unauthorization indication by: receiving the service unauthorization indication from one of the one or more WAB-core network nodes; or determining, based on one or more service authorization policies, that the WAB-base station is service unauthorized.

23. The WAB network node of any one of claims 21-22, the processing circuitry further operable to deregister the WAB-MT.

24. The WAB network node of any one of claims 14-23, the processing circuitry further operable to: obtain, by the WAB-base station, a service authorization indication; and establish, by the WAB-MT, one or more protocol data unit sessions with the BH-core network to provide the WAB-base station with connectivity to one or more WAB-core network nodes.

25. The WAB network node of claim 24, wherein the processing circuitry is operable to obtain the service authorization indication by: receiving the service authorization indication from one of the one or more WAB-core network nodes; ordetermining, based on one or more service authorization policies, that the WAB-base station is service authorized.

26. The WAB network node of any one of claims 24-25, the processing circuitry further operable to connect, by the WAB-MT, to the BH-core network.

27. A 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 cause a wireless access backhaul (WAB) network node comprising a WAB-base station and a WAB-mobile terminal (WAB-MT) to: connect, by the WAB-MT, to a backhaul (BH)-core network; establish, by the WAB-MT, one or more protocol data unit sessions with the BH-core network to provide the WAB-base station with connectivity to one or more WAB-core network nodes; connect, by the WAB-base station, to one of the one or more WAB-core network nodes; receive, by the WAB-base station, a service authorization indication from the one of the one or more WAB-core network nodes; and serve, by the WAB-base station, one or more user equipment (UEs).

Images