Dynamically configuring a network node for network access node operation

Abstract

Various aspects of the present disclosure relate to a network node for wireless communication. The network node may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the network node may transmit capability information to a first network entity in a first Public Land Mobile Network (PLMN), wherein the capability information indicates that the network node is capable of supporting network access node functionality. The network may receive, from the first network entity, a first configuration command to operate as a network access node for a second PLMN based at least in part on the transmitted capability information; and operate as the network access node that provides connectivity to the second PLMN based at least in part on the received first configuration command.

Description

DYNAMICALLY CONFIGURING A NETWORK NODE FOR NETWORK ACCESS NODE OPERATIONTECHNICAL FIELD

[0001] The present disclosure relates to wireless communications, and more specifically to enabling (e.g., configuring, reconfiguring) a network node supporting network access node functionality to operate a network access node.BACKGROUND

[0002] A wireless communications system may include one or multiple network communication devices, which may be otherwise known as network equipment NE) , supporting wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE), or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers, or the like). Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G)).SUMMARY

[0003] An article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” may be interchangeable. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of’ or “one or more of’ or “one or both of’) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that isdescribed as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be constmed in the same manner as the phrase “based at least in part on. Further, as used herein, including in the claims, a “set” may include one or more elements.

[0004] A network node for wireless communication is described. The network node may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the network node may comprise at least one memory, and at least one processor coupled with the at least one memory and configured to case the network node to: transmit capability information to a first network entity in a first Public Land Mobile Network (PLMN), wherein the capability information indicates that the network node is capable of supporting network access node functionality; receive, from the first network entity, a first configuration command to operate as a network access node for a second PLMN based at least in part on the transmitted capability information; and operate as the network access node that provides connectivity to the second PLMN based at least in part on the received first configuration command.

[0005] A processor for wireless communication is described. The processor may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the processor may comprise at least one controller coupled with at least one memory and configured to cause the processor to: output capability information of a network node to a first network entity in a first PLMN, wherein the capability information indicates that the network node is capable of supporting network access node functionality; obtain, from the first network entity, a first configuration command to operate as a network access node for a second PLMN based at least in part on the transmitted capability information; and configure the network node to operate as the network access node that provides connectivity to the second PLMN based at least in part on the received first configuration command.

[0006] A method performed or performable by a network node is described. The method may comprise transmitting capability information to a first network entity in a first PLMN, wherein the capability information indicates that the network node is capable of supporting network access node functionality; receiving, from the first network entity, a firstconfiguration command to operate as a network access node for a second PLMN based at least in part on the transmitted capability information; and operating as the network access node that provides connectivity to the second PLMN based at least in part on the received first configuration command.

[0007] In some implementations of the network node, processor, and method described herein, the network node may be a UE. In some implementations of the network node, processor, and method described herein, the capability information is transmitted to the first network entity in the first PLMN over a Uu interface.

[0008] In some implementations of the network node, processor, and method described herein, the capability information indicates a location of the network node.

[0009] Some implementations of the network node, processor, and method described herein may further include operations, means, or instructions for performing a registration procedure with the first PLMN; and establishing a first Protocol Data Unit (PDU) session with the first PLMN, wherein the first PDU session enables connectivity with the first network entity. In some implementations of the network node, processor, and method described herein, the capability information is transmitted to the first network entity in the first PLMN via the established first PDU session.

[0010] In some implementations of the network node, processor, and method described herein, the network access node functionality may comprise small cell functionality that includes a 3 GPP small cell functionality or a non-3GPP small cell functionality.

[0011] In some implementations of the network node, processor, and method described herein, the first configuration command may comprise one or more of: a type of small cell functionality, the type of small cell functionality comprising the 3GPP small cell functionality or the non-3GPP small cell functionality; an Internet Protocol (IP) address of a second network entity in the second PLMN for connecting to the second network entity via an Fl interface, wherein the second network entity comprises a base station-central unit (gNB-CU) or a Trusted Non-3GPP Gateway Function (TNGF); security information for connecting to the second network entity in the second PLMN; or application information for executing a small cell application or service.

[0012] Some implementations of the network node, processor, and method described herein may further include operations, means, or instructions for establishing a second PDU session with the first PLMN, wherein the second PDU session is for transferring traffic via the Fl interface. In some implementations of the network node, processor, and method described herein, one or more Quality of Service (QoS) flows are supported for the second PDU session for transporting control information or data information with different QoS parameters.

[0013] Some implementations of the network node, processor, and method described herein may further include operations, means, or instructions for transmitting an acknowledgment (ACK) that indicates small cell functionality is enabled at the network node. In some implementations of the network node, processor, and method described herein, the ACK is transmitted in response to the network node being operatable as a small cell.

[0014] Some implementations of the network node, processor, and method described herein may further include operations, means, or instructions for performing a security establishment procedure with the second network entity based at least in part on the first configuration command; and performing a first setup procedure with the second network entity, in response to (or based at least in part on) the security establishment procedure. In some implementations of the network node, processor, and method described herein, the first setup procedure is an Fl setup procedure when the small cell functionality is the 3GPP small cell functionality.

[0015] Some implementations of the network node, processor, and method described herein may further include operations, means, or instructions for transmitting a first request to join an orchestrated computing environment (OCE) in the first PLMN. In some implementations of the network node, processor, and method described herein, the first request to join the OCE indicates that the network node is capable of executing containerized applications. Some implementations of the network node, processor, and method described herein may further include operations, means, or instructions for receiving a second request to deploy a containerized application. In some implementations of the network node, processor, and method described herein, the containerized application can support the network access node functionality. In some implementations of the network node, processor,and method described herein, the second request is received based at least in part on the network node joining the OCE. In some implementations of the network node, processor, and method described herein, the network node is operated as the network access node in response to (or based at least in part on) deploying the containerized application.

[0016] Some implementations of the network node, processor, and method described herein may further include operations, means, or instructions for receiving, from the first network entity in the first PLMN, a second configuration command to cease (e.g., pause, terminate, stop) operating as the network access node; and in response to the second configuration command, cease operating as the network access node.

[0017] Some implementations of the network node, processor, and method described herein may further include operations, means, or instructions for transmitting to the first entity, an indication of a battery level of the network node. In some implementations of the network node, processor, and method described herein, the first configuration command or the second configuration command is received based at least in part on the battery level of the network node.

[0018] A network entity for wireless communication in a first PLMN is described. The network entity may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the network entity comprises at least one memory, and at least one processor coupled with the at least one memory and configured to cause the network entity to: receive capability information that indicates whether a network node is capable of supporting network access node functionality; and determine whether to enable the network access node functionality supported by the network node based at least in part on the received capability information.

[0019] A processor for wireless communication is described. The processor may be configured to, capable of, or operable to receive capability information that indicates whether a network node is capable of supporting network access node functionality; and determine whether to enable the network access node functionality supported by the network node based at least in part on the received capability information.

[0020] A method performed or performable by a network entity in a first PLMN is described. The method may include receiving capability information that indicates whether a network node is capable of supporting network access node functionality; and determining whether to enable the network access node functionality supported by the network node based at least in part on the received capability information.

[0021] Some implementations of the network node, processor, and method described herein may further include operations, means, or instructions for transmitting, to the network node, a first configuration command to operate as a network access node for a second PLMN based at least in part on the transmitted capability information.

[0022] In some implementations of the network node, processor, and method described herein, the network functionality comprises small cell functionality that includes a 3 GPP small cell functionality or a non-3GPP small cell functionality.

[0023] Some implementations of the network node, processor, and method described herein may further include operations, means, or instructions for determining whether to enable the network access node functionality supported by the network node based at least in part on a location of the network node.BRIEF DESCRIPTION OF THE DRAWINGS

[0024] Figures 1 through 3 illustrates examples of wireless communications systems in accordance with aspects of the present disclosure.

[0025] Figures 4(i) through 4(iii) illustrates a process flow that supports dynamically configuring a UE in accordance with aspects of the present disclosure.

[0026] Figures 5(i) through 5(iii) illustrates a process flow that supports dynamically configuring a UE in accordance with aspects of the present disclosure.

[0027] Figure 6 illustrates an example of a network node in accordance with aspects of the present disclosure.

[0028] Figure 7 illustrates an example of a processor in accordance with aspects of the present disclosure.

[0029] Figure 8 illustrates an example of a NE in accordance with aspects of the present disclosure.

[0030] Figure 9 illustrates a flowchart of a method performed by a UE in accordance with aspects of the present disclosure.

[0031] Figure 10 illustrates a flowchart of a method performed by a NE in accordance with aspects of the present disclosure.DETAILED DESCRIPTION

[0032] Modem mobile communication networks, including 4G / 5G systems, rely on a distributed network of base stations, such as eNodeBs (eNBs) and gNodeBs (gNBs), to provide wireless connectivity and ensure seamless communication for UEs. These networks are designed to offer robust coverage and high reliability across wide geographic areas. However, certain circumstances, such as unexpected radio outages, network congestion, or extreme weather conditions, may cause disruptions in radio coverage, leading to degraded service quality or a complete loss of communication for users in the affected areas.

[0033] In many cases, outages or congestion can arise either due to failures within a specific Public Land Mobile Network (PLMN) or from external factors beyond the control of network operators. For instance, a PLMN may experience a temporary radio outage due to equipment failure (e.g. gNB failure), software malfunctions, or backhaul issues, leaving users without radio access. Similarly, in densely populated areas or during special events, the installed radio resources may become insufficient to handle the high demand for data and voice services, leading to congestion and degraded service quality.

[0034] Traditionally, small cells, which are low-powered radio access points, have been deployed to augment network capacity and fill coverage gaps. However, these small cells require physical infrastructure, planning, and deployment, which can be both timeconsuming and costly. Additionally, deploying small cells on short notice in response to an unforeseen outage or surge in network traffic is logistically challenging, limiting the ability of mobile network operators (MNOs) to dynamically respond to such situations.

[0035] The present application proposes an innovative solution that leverages UEs connected to a PLMN to serve as temporary or supplementary network access points, such as temporary small cells, that provide access to the same PLMN or to a different PLMN. Bydynamically reconfiguring UEs to act as network access points, this approach enables mobile networks to provide temporary radio coverage or additional capacity in a targeted geographic area without requiring physical infrastructure deployment. These UEs can either serve subscribers of their own network (for example, to alleviate congestion) or be temporarily reconfigured to serve subscribers of a different PLMN that is experiencing a radio outage. The UEs, under the control of the Operations and Management (OAM) system of the network, can be dynamically activated or deactivated based on network conditions, available power, and user mobility. The UEs may implement a special module or run a special application which implements the functionality of a regular base station like transmission of radio broadcast signals. This novel approach offers mobile operators greater flexibility, scalability, and resilience in maintaining service continuity and managing network capacity.

[0036] Aspects of the present disclosure are described in the context of a wireless communications system.

[0037] Figure 1 illustrates an example of a wireless communications system 100 in accordance with aspects of the present disclosure. The wireless communications system 100 may include one or more NE 102, one or more UE 104, and a core network (CN) 106. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE -Advanced (LTE-A) network. In some other implementations, the wireless communications system 100 may be a NR network, such as a 5G network, a 5G- Advanced (5G-A) network, or a 5G ultrawideband (5G-UWB) network. In other implementations, the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20. The wireless communications system 100 may support radio access technologies beyond 5G, for example, 6G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA), etc.

[0038] The one or more NE 102 may be dispersed throughout a geographic region to form the wireless communications system 100. One or more of the NE 102 described hereinmay be or include or may be referred to as a network node, a base station, a network element, a network function, a network entity, a radio access network (RAN), a NodeB, an eNodeB (eNB), a next-generation NodeB (gNB), or other suitable terminology. An NE 102 and a UE 104 may communicate via a communication link, which may be a wireless or wired connection. For example, an NE 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.

[0039] An NE 102 may provide a geographic coverage area for which the NE 102 may support services for one or more UEs 104 within the geographic coverage area. For example, an NE 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or multiple radio access technologies. In some implementations, an NE 102 may be moveable, for example, a satellite associated with a non-terrestrial network (NTN). In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but the different geographic coverage areas may be associated with different NE 102.

[0040] The one or more UE 104 may be dispersed throughout a geographic region of the wireless communications system 100. A UE 104 may include or may be referred to as a remote unit, a mobile device, a wireless device, a remote device, a subscriber device, a transmitter device, a receiver device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an Internet-of- Things (loT) device, an Internet-of-Everything (loE) device, or machine-type communication (MTC) device, among other examples.

[0041] A UE 104 may be able to support wireless communication directly with other UEs 104 over a communication link. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link 114 may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.

[0042] An NE 102 may support communications with the CN 106, or with another NE 102, or both. For example, an NE 102 may interface with other NE 102 or the CN 106 through one or more backhaul links (e.g., SI, N2, N2, or network interface). In some implementations, the NE 102 may communicate with each other directly. In some other implementations, the NE 102 may communicate with each other or indirectly (e.g., via the CN 106. In some implementations, one or more NE 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC). An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs).

[0043] The CN 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The CN 106 may be an evolved packet core (EPC), or a 5G core (5GC), which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management functions (AMF)) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.) for the one or more UEs 104 served by the one or more NE 102 associated with the CN 106.

[0044] The CN 106 may communicate with a packet data network over one or more backhaul links (e.g., via an SI, N2, N2, or another network interface). The packet data network may include an application server. In some implementations, one or more UEs 104 may communicate with the application server. A UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the CN 106 via an NE 102. The CN 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server using the established session (e.g., the established PDU session). The PDU session may be an example of a logical connection between the UE 104 and the CN 106 (e.g., one or more network functions of the CN 106).

[0045] In the wireless communications system 100, the NEs 102 and the UEs 104 may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communications). In some implementations, the NEs 102 and the UEs 104 may support different resource structures. For example, the NEs 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the NEs 102 and the UEs 104 may support a single frame structure. In some other implementations, such as in 5G and among other suitable radio access technologies, the NEs 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures). The NEs 102 and the UEs 104 may support various frame structures based on one or more numerologies.

[0046] The wireless communication system 100 may support configuring and / or reconfiguring a network node, for example a NE 102 and / or a UE 104 to operate as a network access node (e.g., a small cell, or other type of network AP). In some cases, the wireless communication system 100 may support configuring and / or reconfiguring the network node in response to (or based at least in part on) network outage, network congestion, or service requests. By enabling the wireless communication system 100 to configure and / or reconfigure the network node to operate (e.g., function) as a network access node, the wireless communication system 100 including one or more of the NE 102 or the UE 104 may experience higher reliability and lower latency communication or services, higher system capacity. In other words, the wireless communication system 100 may utilize the NE 102 and / or the UE 104 to provide radio access in coverage areas experiencing temporary service disruption (e.g., network outage) or increased traffic demand to manage wireless communication and services within the wireless communication system 100.

[0047] In particular, UEs that are registered and authenticated in a given Public Land Mobile Network (PLMN-a) can be reconfigured to provide small cell functionality, thereby extending coverage or augmenting capacity in specific geographic areas, such as Area XYZ. Although, the application refers to small cells, any other type of network access point could be configured instead. The Operations and Management (0AM) system of PLMN-a has the ability to identify and track UEs located in the affected area and determine which UEs are capable of acting as small cells based on factors such as battery life, location, and networkcapabilities. UEs that meet the criteria may be triggered to download and execute a "small cell" application that transforms them into small cells capable of providing radio access.

[0048] The present method can be applied in several scenarios, including but not limited to:

[0049] Scenario 1: Radio Outage in a Neighboring PLMN (PLMN-b). In the event that PLMN-b experiences a radio outage in a particular area (e.g., Area XYZ), the PLMN-b may request PLMN-a to provide assistance, i.e. to provide radio access coverage in this area for subscribers of PLMN-b. The 0AM of PLMN-a may configure one or more UEs connected to PLMN-a to act as small cells that provide radio access to PLMN-b subscribers. The UEs configured as small cells establish a connection with the radio access network (RAN) of PLMN-b via an Fl interface (which may also be referred to as a function split (Fl) interface that which facilitates communication between a gNB-CU and a gNB-Distributed Unit (DU) (gNB-DU)), allowing PLMN-b subscribers to register and continue receiving service.

[0050] The 0AM of PLMN-a may decide to configure one or more UEs connected to PLMN-a to act as a small cell(s) for PLMN-b because e.g. it received a request from the network operator or another platform, such as “Activate Temporary Service Restoration for PLMN-b in Area XYZ” or “Provide Temporary Service in Area XYZ. ’’ Based on this request, the 0AM system can identify UEs in the target area and dynamically activate them as small cells to fulfill the service restoration request.

[0051] Scenario 2: Temporary Congestion in PLMN-a. In the case of increased demand or congestion within PLMN-a itself in a specific area (e.g. due to an event taking place in this area), the 0AM system may identify UEs in this area that are capable of functioning as small cells. By activating these UEs as small cells, the network can provide additional radio resources to alleviate congestion and ensure continued service for PLMN-a subscribers.

[0052] The method takes into account the power and resource constraints of regular UEs (e.g. smartphones). Special UEs, such as those mounted on vehicles with external power sources, may be prioritized for longer-term small cell operation. Regular smartphones, on the other hand, may only operate as small cells when plugged into a power source or when their battery charge exceeds a predefined threshold. UEs with insufficient battery levels may senda notification to indicate that they can no longer function as small cells, allowing the OAM to reconfigure other UEs or deactivate the small cell functionality.

[0053] This dynamic UE-to-small cell transformation allows for rapid response to network outages or capacity demands, ensuring continuity of service while minimizing the need for costly and time-consuming infrastructure deployments. The invention enhances the operational efficiency of mobile networks by providing a flexible and scalable solution to address temporary service disruptions and capacity challenges.

[0054] Two types of UE network access points are considered:

[0055] A "3 GPP" network access point, wherein the UE is configured to provide the functionality of a gNB Radio Unit (gNB-RU) and the functionality of a gNB Distributed Unit (gNB-DU). A system diagram for this type of network access point is depicted in Figure 2.

[0056] A "Non-3GPP" network access point, wherein the UE is configured to provide the functionality of a Trusted Non-3GPP Access Point (TNAP) as defined in TS 23.501. A system diagram for this type of network access point is depicted in Figure 3.

[0057] Figure 2 illustrates an example of a wireless communication system in accordance with aspects of the present disclosure. The wireless communication system may include two PLMNs, such as a PLMN-a and PLMN-b. The PLMN-a may include a next-generation radio access network (NG-RAN) 200, a UPF 210, an AMF 220, and a Session Management Function (SMF) 230. The PLMN-b may include a gNB Central Unit (gNB-CU) 240, a UPF 250, and an AMF 260. Additionally, the wireless communication system may include a plurality of UEs 280 and one or more UEs 270 that may be configured to (or reconfigured to) operate as network APs. The plurality of UEs 280 may be connected to one or more of the PLMN-a or the PLMN-b via the one or more UEs 270 configured to (or reconfigured to) operate as network APs. The one or more UEs 270 configured to (or reconfigured to) operate as network APs may establish an Fl connection with the gNB-CU 240 of the PLMN-b.

[0058] Figure 3 illustrates an example of a wireless communication system in accordance with aspects of the present disclosure. The wireless communication system may be configurable to include a "Non-3GPP" network access point in accordance with aspects of the present disclosure. A PLMN-a may include a next-generation radio access network (NG- RAN) 200, a UPF 210, an AMF 220, and a Session Management Function (SMF) 230. APLMN-b may include a Trusted Non-3GPP Gateway Function (TNGF) 300, a UPF 250, and an AMF 260. Additionally, the wireless communication system may include a plurality of UEs 280 and one or more UEs 310 that may be configured (or reconfigured) to operate as a TNAP. The plurality of UEs 280 may be connected to the PLMN-b via the plurality of UEs configured to operate as a TNAP 310. The UEs configured (or reconfigured) to operate as a TNAP may establish an Fl connection with the TNGH 230 of PLMN-b.

[0059] Figures 4(i) through (iii) illustrates a process flow that supports dynamically configuring (or reconfiguring) a UE in accordance with aspects of the present disclosure. The process flow may implement or be implemented by aspects of the wireless communication systems as described with reference to Figures 1 through 3. For example, the process flow may include one or more of a UE-a 441, an access network 442, an AMF 443, an SMF 444, a UPF 445, an AF 446, an 0AM 447, a gNB-CU 448, a further AMF 449 and a UE-b 450 which may be examples of UE and NE as described with reference to Figures 1 through 3.

[0060] The process flow may include one or more operations or signaling performed by one or more of the UE-a 441, the access network 442, the AMF 443, the SMF 444, the UPF 445, the AF 446, the 0AM 447, the gNB-CU 448, the AMF 449 and the UE-b 450. In the following description of the process flow, the operations or signaling performed between one or more of the UE-a 441, the access network 442, the AMF 443, the SMF 444, the UPF 445, the AF 446, the 0AM 447 the gNB-CU 448, the AMF 449 and the UE-b 450 may be performed or signaled (e.g., transmitted, received) in a different order than the example order shown, or the operations or signaling performed by one or more of the UE-a 441, the access network 442, the AMF 443, the SMF 444, the UPF 445, the AF 446, the 0AM 447 the gNB- CU 448, the AMF 449 and the UE-b 450 may be performed or signaled (e.g., transmitted, received) in different orders or at different times. Some operations or signaling may also be omitted from the process flow. Additionally, although some operations or signaling may be shown to occur at different times, these operations or signaling may occur at the same time or in overlapping time periods.

[0061] Figures 4(i) to 4 (iii) illustrate a process flow that enables PLMN-a to dynamically configure UEs (e.g. UE-a 441) connected to this PLMN to operate as small cells for PLMN- b according to a first embodiment. The flow shown in Figures 4 (i) to 4(iii) may be used in a scenario in which a second network, PLMN-b, experiences radio outage in a particular areaand PLMN-a configures UEs in this area to provide radio access to PLMN-b. However, a similar method can be applied in a scenario where there is no second network, but the method is used to address a temporary congestion situation in PLMN-a, as discussed above.

[0062] Figures 4 (i) to (iii) show two Public Land Mobile Networks (PLMN-a and PLMN-b), each consisting of standard components such as an Access Network 441 (e.g., NG-RAN), AMF 443, SMF 444, UPF 445, and 0AM (Operations and Management System) 447. PLMN-a is responsible for managing its UEs, including those that are reconfigured to function as network access points. The 0AM system 447 in PLMN-a and a new Application Function (AF) 446 assist in identifying, tracking, and configuring UEs as network access points when necessary.

[0063] The UEs shown in Figure 4 are divided into two categories:(i) UE-a 441 refers to a UE connected to PLMN-a, which can be dynamically configured to operate as a network access point for PLMN-b. In the example shown in Figure 4, UE-a 441 is configured to operate as a "3GPP" small cell, i.e. to provide the functionality of a gNB-RU / DU. However, the same method can also be used to configure UE-a 441 to operate as a "non-3GPP" small cell.(ii) UE-b 450 refers to a subscriber of PLMN-b, which uses the network access point provided by UE-a 441 to establish and maintain connectivity to PLMN-b during network disruptions.

[0064] In step 401 , a UE-a 441 registers with PLMN-a. A standard mutual authentication procedure is executed between UE-a 441 and the network, ensuring that the UE is authenticated to access the PLMN-a network. After authentication, in step 402, UE-a 441 establishes a PDU session with PLMN-a, allowing it to participate in regular communication activities, such as internet access and other services.

[0065] Upon successful registration, in step 403 a, UE-a 441 may indicate its capability to operate as a "3 GPP" and / or a "non-3GPP" network access point. This capability is reported through a request sent to the Application Function (AF) 446 in PLMN-a. The AF is a new type of application function in a PLMN that is used specifically for enabling the activation / deactivation of UEs in a particular area to operate as network access points. UE-a 441 is either preconfigured with the address information of AF (e.g. with an IP address) or it candiscover this address information e.g. via a DNS query. The preconfigured information in UE-a 441 may be stored in its USIM module or in another appropriate storage. It is assumed that existing security measures (as those specified in 3 GPP TS 33.501 and in other 3 GPP specifications) are applied to secure the communication between UE-a and AF and to perform mutual authentication.

[0066] The request transmitted by UE-a 441 to AF 446 could include specific information such as UE hardware capabilities, power status, present location, type of small cell supported (3 GPP and / or non-3GPP), etc. UEs capable of acting as small cells may be equipped with additional resources and hardware modules, such as the UEs mounted on vehicles with extended power supplies.

[0067] In cases where UE-a 441 is a regular smartphone, this request is only triggered if the device is connected to a power source or has a sufficiently charged battery. This ensures that only UEs with enough power resources are considered for the small cell operation.

[0068] In step 404, after receiving the capability report from UE-a 441 , the AF 446 begins tracking the UE’s location by using existing location services in PLMN-a. Alternatively, UE-a 441 may periodically send a location update message to AF 446 to update its own location. Location tracking is used to determine whether UE-a is in the target area (e.g., Area XYZ) where temporary radio coverage or additional capacity is required.

[0069] In step 405, the 0AM system 447 may decide to activate one or more UEs located in Area XYZ as small cells for several reasons:- The 0AM 447 may receive an indication that PLMN-b is experiencing a radio outage in Area XYZ and requests PLMN-a to provide temporary radio access for PLMN-b subscribers.- The 0AM may receive a request (from the network operator or another platform) such as "Activate Temporary Service Restoration for PLMN-b in Area XYZ." This could be a proactive or reactive request to provide radio coverage in a specific area.- The 0AM may also detect temporary congestion within its own network (PLMN-a) and determine that additional radio resources are needed to handle the increased traffic demand in Area XYZ. This is a different scenario from the one depicted in Figure 4.

[0070] In step 406a, once the 0AM 447 has identified the need for small cells in area XYZ, it sends a second request to AF 446 to activate one or more small cells in this area. This request contains configuration data for small cell operation, such as:- The type of the small cells (3 GPP or non-3GPP) to be activated.- The target area wherein small cells should be activated.- A time indication of when the 3 GPP small cells are to be activated:- The IP address of the gNB-CU in the radio access network of PLMN-b, which the 3GPP small cells will be connected to (see Figure 2).- Digital certificates and other security information required to establish a secure connection with the gNB-CU in the radio access network of PLMN-b.- A time indication of when the non-3GPP small cells are to be activated:- The IP address of the TNGF in the radio access network of PLMN-b, which the non-3GPP small cells will be connected to (see Figure 2).- WiFi parameters such as SSID, security mode (e.g. WPA2 / WP A3 -Enterprise), etc.- App metadata, in case UEs need to download and run a small cell application. This metadata includes information that enables UEs to securely connect with an application repository (maintained or trusted by the operator of PLMN-a) to download and run an application that transforms them into small cells.- Information for UE selection: The 0AM may provide some information that assists the AF to decide how many UEs will select in the target area and instruct them to operate as small cells.

[0071] After receiving the request in step 406a, in step 406b the AF 446 selects one or more UEs in the target area and sends a third request to each of them. The third request is sent to UE-a 441 and contains at least some of the configuration data received by the AF 446 in step 6a.

[0072] In step 407a, if required, UE-a 441 pulls the small cell application from a trusted repository based on the app metadata received in step 406b. Once the application is downloaded, in step 407b, UE-a 441 establishes a new PDU Session, which is used for the small cell operation, i.e. for communicating with the gNB-CU 448 in PLMN-b using the Fl interface (or for communicating with a TNGF in PLMN-b using the Ta interface, in the caseof non-3GPP small cell). Separate Quality of Service (QoS) flows are configured on this PDU Session for transporting Fl signaling and Fl data traffic between the UE-a 441 and the gNB-CU 448 in PLMN-b.

[0073] The small cell application download is optional because UE-a 441 may have already downloaded this application or may have this application pre-installed. When UE-a 441 is instructed to operate as a non-3GPP small cell, UE-a 441 essentially activates the "WiFi hotspot" functionality, which is already supported by most smartphones, and operates as a WiFi access point using WPA2 -Enterprise or WP A3 -Enterprise security. In this case, UE-a 441 may not need to download a small cell application.

[0074] In step 408a, after running the small cell application, UE-a 441 starts operating as a 3GPP small cell (or, in other scenarios, as a non-3GPP small cell), providing radio access to other UEs in the area, e.g., UE-b 450, which is a subscriber of PLMN-b. In response, in step 408b, UE-a 441 sends a third response message to the AF 446, which is a response to the third request received in step 406b. This message confirms that UE-a 441 has started to operate as a small cell. After receiving the third response message from UE-a 441 and, possibly, from other UEs, in step 408c the AF 446 sends a second response to 0AM 447 to indicate that one or more UEs operate as small cells for PLMN-b.

[0075] In step 409, secure communication between the UE-a 441 and gNB-CU 448 is established using IKEv2 signaling (as specified in 3GPP TS 33.501) to set up a Security Association (SA). This step ensures that all subsequent communication between UE-a 441 and the gNB-CU 448 in PLMN-b is encrypted and authenticated. Once the SA is established, the regular Fl Setup procedure is executed. In step 410a, the UE-a 441 sends a setup request to the gNB-CU 448 of PLMN-b, and in step 410b, the gNB-CU 448 of PLMN-b sends a setup response to UE-a 441. The Fl Response message includes information (such as radio parameters, frequencies, cell id, etc.) which are used by UE-a 441 to operate as a 3 GPP small cell for PLMN-b.

[0076] When UE-a 441 operates as a non-3GPP small cell, steps 410a and 410b may not be executed, if UE-a 441 received the required operating parameters (SSID, security mode, etc.) in step 406b. However, if UE-a 441 did not receive these parameters in step 406b, then a Ta Setup procedure may be used to retrieve these parameters from the TNGF in PLMN-a.

[0077] In step 411, once the small cell functionality in UE-a is activated, UE-b, a subscriber of PLMN-b, discovers and connects to the small cell provided by UE-a. UE-b can now register with its home PLMN (PLMN-b) and continue normal communication activities, such as voice calls and data sessions, through the small cell provided by UE-a. Existing procedures for network registration and service access apply to UE-b, as it would connect to any other small cell or base station.

[0078] According to an embodiment, if UE-a is a regular smartphone operating as a small cell and its battery level drops below a predefined threshold, the UE sends a request to the AF to indicate that it can no longer function as a small cell. In response, the AF may find an alternative UE to take over the small cell function and deactivate the small cell operation in UE-a, returning UE-a to its normal mode of operation (it functions only as a UE connected to PLMN-a).

[0079] The above description outlines a method by which UEs can be dynamically reconfigured to operate as small cells (or as network access points), providing temporary radio access or augmenting network capacity in response to outages or congestion. The system’s flexibility allows for a wide range of applications, including inter-PLMN service continuity and intra-PLMN congestion management, while ensuring that the UEs are only utilized within their available power and processing constraints.

[0080] Figures 5(i) to (iii) illustrate a process flow according to a second embodiment that supports dynamically configuring (or reconfiguring) a UE in accordance with aspects of the present disclosure. The process flow may implement or be implemented by aspects of the wireless communication systems as described with reference to Figures 1 through 3. For example, the process flow may include one or more of a UE-a 441, an access network 442, an AMF 443, an SMF 444, a UPF 445, an AF 446, an 0AM 447, a gNB-CU 448, a further AMF 449, a UE-b 450 and a MANO 547, which may be examples of UE and NE as described with reference to Figures 1 through 3.

[0081] The process flow may include one or more operations or signaling performed by one or more of the UE-a 441, the access network 442, the AMF 443, the SMF 444, the UPF 445, the AF 446, the 0AM 447, the gNB-CU 448, the AMF 449, the UE-b 450 and the MANO 547. In the following description of the process flow, the operations or signaling performed between one or more of the UE-a 441, the access network 442, the AMF 443, theSMF 444, the UPF 445, the AF 446, the OAM 447, the gNB-CU 448, the AMF 449, the UE- b 450 and the MANO 547 may be performed or signaled (e.g., transmitted, received) in a different order than the example order shown, or the operations or signaling performed by one or more of the UE-a 441, the access network 442, the AMF 443, the SMF 444, the UPF 445, the AF 446, the OAM 447, the gNB-CU 448, the AMF 449, the UE-b 450 and the MANO 547 may be performed or signaled (e.g., transmitted, received) in different orders or at different times. Some operations or signaling may also be omitted from the process flow. Additionally, although some operations or signaling may be shown to occur at different times, these operations or signaling may occur at the same time or in overlapping time periods

[0082] As shown in Figures 5 (i) to (iii), a UE-a 441 not only connects to PLMN-a as a regular mobile device but also becomes part of a container orchestration system, such as a Kubernetes cluster, managed by the PLMN-a's Operations and Management (OAM) system 447 or a Mobile Network Orchestrator (MANO) system 547. The container orchestration system cluster is used to orchestrate the deployment of small cell applications, which are executed in the form of containers or pods on UE-a 441, when necessary.

[0083] The major components involved in this embodiment include:- UE-a 441 : AUE that connects to PLMN-a and is capable of joining a Kubernetes cluster as a worker node. UE-a 441 can dynamically host containerized applications, such as a 3 GPP small cell pod or a non-3GPP small cell pod.- Kubernetes Cluster: The orchestrator in PLMN-a that schedules, manages, and monitors containerized services running on its worker nodes (including UE-a 441).- PLMN-a OAM / Orchestrator (MANO) 547: The management system that determines the need for small cell activation in Area XYZ, orchestrates the activation process, and interfaces with the Kubernetes API for workload scheduling.- UE-b 450: A UE connected to PLMN-b that relies on the small cell provided by UE-a 441 to maintain service continuity during a network outage.

[0084] It will be appreciated that a Kubernetes cluster is an example of a more general orchestrated computing environment (OCE) and the approach described may be implemented using any suitable OCE.

[0085] As with the previous embodiment, in step 501, UE-a 441 first registers with PLMN-a through standard authentication mechanisms. In step 502, UE-a 441 establishes afirst PDU session with the mobile network PLMN-a. In step 503, following successful authentication and PDU session establishment, UE-a 441 receives additional information from the AF 446 in PLMN-a that enables it to join a Kubernetes cluster managed by PLMN- a’s OAM / Orchestrator and operate as a worker node allowing it to run containerized workloads (such as a “small cell” workload).

[0086] In step 504, after joining, UE-a 441 periodically sends NodeStatus messages to the Kubernetes API server 547, reporting the resources it can provide (CPU, memory, storage), the health of the node, and other operational metrics (as defined in https: / / kubernetes.io / docs / reference / node / node-status / ). Importantly, this message also includes the current location of the UE 441, which can be used to make location-aware scheduling decisions by the Kubernetes cluster. In this scenario, the location information is needed so that the Kubernetes API server can schedule containerized “small cell” workloads (pods) to run only in UEs located in a specific area (Areas XYZ).

[0087] In step 505, the PLMN-a’s 0AM 447 determines that small cell functionality is required (for instance, due to congestion in PLMN-a or a radio outage in PLMN-b) in Area XYZ. In step 506a, the 0AM 447 sends a request to the Kubernetes cluster to schedule the small cell application on one or more UEs in Area XYZ. This request includes the configuration data discussed in the previous embodiment, such as digital certificates, the address of the gNB-CU 448 in PLMN-b, and other security details.

[0088] In response to the 0AM’ s request, in step 506ai, the Kubernetes cluster schedules a containerized app to run on UE-a 441, which implements the small cell functionality. The scheduling is done in a manner similar to standard Kubernetes workloads, where UE-a 441 receives an event notification in step 506b containing a PodSpec that includes details to deploy the pod, including the container image, digital certificates, and references to configuration secrets required for the small cell operation. However, in this case, the scheduling is location-aware. As mentioned above, the Kubernetes API server schedule containerized “small cell” workloads to run only in UEs located in a specific area (Areas XYZ).

[0089] Once the pod is scheduled, in step 507a, UE-a 441 initiates actions to instantiate the small cell pod. This includes pulling the container image from the appropriate repository(if not already available in UE-a), retrieving configuration data, and setting up the necessary runtime environment.

[0090] In step 507b, UE-a 441 establishes a new PDU Session, which is dedicated to the small cell traffic (e.g., Fl interface signaling and data). This session ensures that the small cell function is logically separated from UE-a's regular mobile network operations. Separate QoS flows may be used to distinguish between Fl signaling traffic and Fl data traffic.

[0091] After instantiation, in step 508a, the small cell pod begins operating, allowing UE-a441 to function as a 3GPP small cell, i.e. gNB-RU / DU (or, in other scenarios, as a non- 3GPP small cell, i.e. TNAP). In step 508b, the pod communicates its operational status back to the Kubernetes API server through a PodStatus message, indicating that the small cell functionality is active. After receiving the third response message from UE-a 441 and, possibly, from other UEs, in step 508c the Kubernetes cluster / MANO layer 547 sends a second response to 0AM 447 to indicate that one or more UEs operate as small cells for PLMN-b.

[0092] As with the previous embodiment, in steps 509, 510a and 510b, secure communication between UE-a 441 and the gNB-CU in the radio access network of PLMN- b is established using IKEv2 signaling for security association (SA) setup. Once the SA is established, the regular Fl Setup procedure is executed. The Fl Response message includes information (such as radio parameters, frequencies, etc.) which are needed by UE-a to operate as a small cell for PLMN-b.

[0093] In step 511, once the small cell is active, UE-b 450, a subscriber of PLMN-b, can discover and connect to the small cell hosted by UE-a 441. UE-b 450 then registers with PLMN-b and continues to receive service through the small cell, following the normal network procedures for service registration and access.

[0094] This embodiment introduces a cloud-native approach to deploying small cells by integrating UEs into a Kubernetes cluster. The dynamic scheduling and orchestration capabilities of Kubernetes enhance the flexibility of PLMN-a, allowing it to rapidly respond to network outages or congestion by transforming UEs into small cells. By using containers, this approach ensures that the small cell functionality is lightweight, modular, and easy to manage, making it suitable for modern mobile network environments that require agile and scalable solutions.

[0095] The use of Kubernetes allows PLMN-a 441 to automate the deployment and scaling of small cell functionality across a large number of UEs. Kubernetes’ scheduling capabilities ensure that only UEs with sufficient resources are selected, and the platform’s monitoring tools can continuously track the health and status of small cell operations.

[0096] The containerized nature of the small cell application enables easy updates, rollbacks, and deployment of different small cell configurations. This flexibility can be used to tailor small cell behavior depending on the scenario, such as outage restoration, congestion management, or temporary service enhancements.

[0097] Kubernetes continuously monitors the resource availability on UE-a 441 and other worker nodes, ensuring that the small cell pod is only scheduled if there are sufficient resources to run it. Additionally, it can prioritize UEs with external power sources (such as those mounted on vehicles) for long-term small cell operation, while regular smartphones may be limited to short-term activation based on battery status.

[0098] The following methods may be implemented according to the present disclosure:

[0099] A method for dynamically reconfiguring UE connected to a mobile network(PLMN-a) to operate as a small cell may comprise: registering the UE with the mobile network (PLMN-a) and executing mutual authentication; establishing a PDU session between the UE and PLMN-a; detecting a requirement for temporary radio access or network capacity enhancement in a geographic area (XYZ) by the Operations and Management (0AM) system of PLMN-a; configuring the UE to operate as a small cell based on its capability to act as such, which includes sending a request to an Application Function (AF) with UE’s location, hardware capabilities, and battery status; activating the small cell application on the UE if the UE is in the affected area (XYZ), and optionally downloading a small cell application if required; providing temporary radio access to other UEs in PLMN- a or in another network (PLMN-b) by routing traffic through the UE acting as a small cell.

[0100] A method for service restoration in a neighboring PLMN Using UEs in PLMN-a is also disclosed. A method for using UEs from a first network (PLMN-a) to provide radio coverage for a neighboring network (PLMN-b) during a radio outage in a target area (XYZ), may comprise: identifying UEs in PLMN-a located in the affected area (XYZ) based on location information reported by the UEs; sending a configuration request to UEs capable of operating as small cells, containing data such as the IP address of the gNB-CU of PLMN-band digital certificates for secure communication; establishing an Fl interface between the UEs (acting as gNB-RU / DUs) and the core network (gNB-CU) of PLMN-b to allow PLMN- b subscribers to register and receive service through the temporary small cells; handling the radio traffic of PLMN-b’s subscribers through UEs of PLMN-a acting as temporary small cells, maintaining secure communication with the core network of PLMN-b.

[0101] A method of dynamic deactivation of small cells in UEs based on battery levels is also disclosed. A method for dynamically deactivating the small cell functionality in a UE operating as a small cell for a mobile network may comprise: monitoring the battery level of the UE operating as a small cell; sending a notification to the Application Function (AF) or 0 AM when the battery level of the UE falls below a predefined threshold, indicating that the UE can no longer support small cell functionality; deactivating the small cell operation in the UE based on the notification and returning the UE to its normal mode of operation; optionally configuring or reconfiguring another UE in the area to take over small cell responsibilities to ensure continued coverage or service restoration.

[0102] A Kubernetes-Based method for orchestrating small cell functions in UEs is also disclosed. A method for dynamically orchestrating small cell functions in UEs connected to a mobile network (PLMN-a) using a Kubernetes cluster may comprise: joining a UE to a Kubernetes cluster managed by PLMN-a’ s Operations and Management (0AM) system; periodically reporting node status, including resource availability and location, to the Kubernetes API server; scheduling a containerized small cell application (pod) to run on the UE based on the UE’s location in a target area (XYZ) and available resources; deploying the small cell pod on the UE, including retrieving the required container images, configuration data, and digital certificates; establishing a newPDU session dedicated to transporting small cell traffic between the UE and the core network of PLMN-a or PLMN-b.

[0103] A system for dynamically configuring UEs as temporary small cells is also disclosed. A system for dynamically configuring user equipment (UE) to operate as temporary small cells may comprise: an Application Function (AF) in a mobile network (PLMN-a) that identifies UEs capable of operating as small cells based on location and hardware capabilities; a means for downloading and executing a small cell application on UEs capable of serving as small cells; a mechanism for securely establishing an Fl interface between the UE and a core network (gNB-CU) to route traffic for subscribers of PLMN-a orPLMN-b; a system for deactivating the small cell function whenUE resources (e.g., battery) fall below predefined thresholds.

[0104] It should be noted that, while the term 'small cell' is used throughout this document to refer to base stations with limited coverage, this should not be viewed as limiting the applicability of the approach. The dynamic reconfiguration of UEs described herein is intended to be flexible and adaptable to a wide range of deployment scenarios, whether the UE operate as a traditional small cell or as any other type of access node providing temporary or supplementary radio access.

[0105] Figure 6 illustrates an example of a network node 600 in accordance with aspects of the present disclosure. The network node 600 may be a UE and may be similar to the UE 104 and UE 441 described herein. The network node 600 may also operate as a base station. The network node 600 may include a processor 602, a memory 604, a controller 606, and a transceiver 608. The processor 602, the memory 604, the controller 606, or the transceiver 608, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0106] The processor 602, the memory 604, the controller 606, or the transceiver 608, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

[0107] The processor 602 may include an intelligent hardware device (e.g., a general- purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 602 may be configured to operate the memory 604. In some other implementations, the memory 604 may be integrated into the processor 602. The processor 602 may be configured to execute computer-readable instructions stored in the memory 604 to cause the network node 600 to perform various functions of the present disclosure.

[0108] The memory 604 may include volatile or non-volatile memory. The memory 604 may store computer-readable, computer-executable code including instructions when executed by the processor 602 cause the network node 600 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 604 or another type of memory. Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or specialpurpose computer.

[0109] In some implementations, the processor 602 and the memory 604 coupled with the processor 602 may be configured to cause the network node 600 to perform one or more of the functions described herein (e.g., executing, by the processor 602, instructions stored in the memory 604). For example, the processor 602 may support wireless communication at the network node 600 in accordance with examples as disclosed herein. The network node 600 may be configured to support a means for transmitting capability information to a first network entity in a PLMN, wherein the capability information indicates that the network node 600 is capable of supporting network access node functionality; receiving, from the first network entity, a first configuration command to operate as a network access node for a second PLMN based at least in part on the transmitted capability information; and operating as the network access node that provides connectivity to the second PLMN based at least in part on the received first configuration command.

[0110] The controller 606 may manage input and output signals for the network node 600. The controller 606 may also manage peripherals not integrated into the network node 600. In some implementations, the controller 606 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 606 may be implemented as part of the processor 602.

[0111] In some implementations, the network node 600 may include at least one transceiver 608. In some other implementations, the network node 600 may have more than one transceiver 608. The transceiver 608 may represent a wireless transceiver. Thetransceiver 608 may include one or more receiver chains 610, one or more transmitter chains 612, or a combination thereof.

[0112] A receiver chain 610 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 610 may include one or more antennas for receive the signal over the air or wireless medium. The receiver chain 610 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 610 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 610 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.

[0113] A transmitter chain 612 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 612 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 612 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 612 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0114] Figure 7 illustrates an example of a processor 700 in accordance with aspects of the present disclosure. The processor 700 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 700 may include a controller 702 configured to perform various operations in accordance with examples as described herein. The processor 700 may optionally include at least one memory 704, which may be, for example, an L1 / L2 / L3 cache. Additionally, or alternatively, the processor 700 may optionally include one or more arithmetic-logic units (ALUs) 706. One or more of these components may be in electronic communication or otherwise coupled(e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0115] The processor 700 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 700) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase change memory (PCM), and others).

[0116] The controller 702 may be configured to manage and coordinate various operations (e.g., signaling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 700 to cause the processor 700 to support various operations in accordance with examples as described herein. For example, the controller 702 may operate as a control unit of the processor 700, generating control signals that manage the operation of various components of the processor 700. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.

[0117] The controller 702 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 704 and determine subsequent instruction(s) to be executed to cause the processor 700 to support various operations in accordance with examples as described herein. The controller 702 may be configured to track memory address of instructions associated with the memory 704. The controller 702 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 702 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 700 to cause the processor 700 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 702 may be configured to manage flow of datawithin the processor 700. The controller 702 may be configured to control transfer of data between registers, arithmetic logic units (ALUs), and other functional units of the processor 700.

[0118] The memory 704 may include one or more caches (e.g., memory local to or included in the processor 700 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, the memory 704 may reside within or on a processor chipset (e.g., local to the processor 700). In some other implementations, the memory 704 may reside external to the processor chipset (e.g., remote to the processor 700).

[0119] The memory 704 may store computer-readable, computer-executable code including instructions that, when executed by the processor 700, cause the processor 700 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. The controller 702 and / or the processor 700 may be configured to execute computer-readable instructions stored in the memory 704 to cause the processor 700 to perform various functions. For example, the processor 700 and / or the controller 702 may be coupled with or to the memory 704, the processor 700, the controller 702, and the memory 704 may be configured to perform various functions described herein. In some examples, the processor 700 may include multiple processors and the memory 704 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.

[0120] The one or more ALUs 706 may be configured to support various operations in accordance with examples as described herein. In some implementations, the one or more ALUs 706 may reside within or on a processor chipset (e.g., the processor 700). In some other implementations, the one or more ALUs 706 may reside external to the processor chipset (e.g., the processor 700). One or more ALUs 706 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 706 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 706 be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process andmanipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 706 may support logical operations such as AND, OR, exclusive-OR (XOR), not-OR (NOR), and not-AND (NAND), enabling the one or more ALUs 706 to handle conditional operations, comparisons, and bitwise operations.

[0121] The processor 700 may support wireless communication in accordance with examples as disclosed herein. The processor 700 may be configured to or operable to support a means for outputting capability information from a network node to a first network entity in a first PLMN, wherein the capability information indicates that the network node is capable of supporting network access node functionality; obtaining, from the first network entity, a first configuration command to operate as a network access node for a second PLMN based at least in part on the transmitted capability information; and configuring the network node to operate as the network access node that provides connectivity to the second PLMN based at least in part on the received first configuration command.

[0122] Figure 8 illustrates an example of a NE 800 in accordance with aspects of the present disclosure. The network entity 800 may comprise one or more of the AF 446, 0AM 447 and MANO 547. The NE 800 may include a processor 802, a memory 804, a controller 806, and a transceiver 808. The processor 802, the memory 804, the controller 806, or the transceiver 808, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0123] The processor 802, the memory 804, the controller 806, or the transceiver 808, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

[0124] The processor 802 may include an intelligent hardware device (e.g., a general- purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 802 may be configured to operate the memory 804. In someother implementations, the memory 804 may be integrated into the processor 802. The processor 802 may be configured to execute computer-readable instructions stored in the memory 804 to cause the NE 800 to perform various functions of the present disclosure.

[0125] The memory 804 may include volatile or non-volatile memory. The memory 804 may store computer-readable, computer-executable code including instructions when executed by the processor 802 cause the NE 800 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 804 or another type of memory. Computer-readable media includes both non- transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or specialpurpose computer.

[0126] In some implementations, the processor 802 and the memory 804 coupled with the processor 802 may be configured to cause the NE 800 to perform one or more of the functions described herein (e.g., executing, by the processor 802, instructions stored in the memory 804). For example, the processor 802 may support wireless communication at the NE 800 in accordance with examples as disclosed herein. The NE 800 may be configured to support a means for receiving capability information that indicates whether a network node is capable of supporting network access node functionality; and determining whether to enable the network access node functionality supported by the network node based at least in part on the received capability information.

[0127] The controller 806 may manage input and output signals for the NE 800. The controller 806 may also manage peripherals not integrated into the NE 800. In some implementations, the controller 806 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 806 may be implemented as part of the processor 802.

[0128] In some implementations, the NE 800 may include at least one transceiver 808. In some other implementations, the NE 800 may have more than one transceiver 808. The transceiver 808 may represent a wireless transceiver. The transceiver 808 may include one or more receiver chains 810, one or more transmitter chains 812, or a combination thereof.

[0129] A receiver chain 810 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 810 may include one or more antennas for receive the signal over the air or wireless medium. The receiver chain 810 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 810 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 810 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.

[0130] A transmitter chain 812 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 812 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 812 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 812 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0131] Figure 9 illustrates a flowchart of a method in accordance with aspects of the present disclosure. The operations of the method may be implemented by a UE or a NE as described herein. In some implementations, the UE or the NE may execute a set of instructions to control the function elements of the UE or the NE to perform the described functions.

[0132] At 902, the method may include transmitting capability information to a first network entity in a first PLMN, wherein the capability information indicates that the network node is capable of supporting network access node functionality. The operations of 902 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 902 may be performed by a network node as described with reference to Figure 6.

[0133] At 904, the method may include receiving, from the first network entity, a first configuration command to operate as a network access node for a second PLMN based at least in part on the transmitted capability information. The operations of 904 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 904 may be performed by a network node as described with reference to Figure 6.

[0134] At 906, the method may include operating as the network access node that provides connectivity to the second PLMN based at least in part on the received first configuration command. The operations of 906 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 906 may be performed by a network node as described with reference to Figure 6.

[0135] It should be noted that the method described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0136] Figure 10 illustrates a flowchart of a method in accordance with aspects of the present disclosure. The operations of the method may be implemented by a NE as described herein. In some implementations, the NE may execute a set of instructions to control the function elements of the NE to perform the described functions.

[0137] At 1002, the method may include receiving capability information that indicates whether a network node is capable of supporting network access node functionality. The operations of 1002 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1002 may be performed by a NE as described with reference to Figure 8.

[0138] At 1004, the method may include determining whether to enable the network access node functionality supported by the network node based at least in part on the received capability information. The operations of 1004 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1004 may be performed by a NE as described with reference to Figure 8.

[0139] It should be noted that the method described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0140] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims

CLAIMS:

1. A network node for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the network node to: transmit capability information to a first network entity in a first Public Land Mobile Network (PLMN), wherein the capability information indicates that the network node is capable of supporting network access node functionality; receive, from the first network entity, a first configuration command to operate as a network access node for a second PLMN based at least in part on the transmitted capability information; and operate as the network access node that provides connectivity to the second PLMN based at least in part on the received first configuration command.

2. The network node of claim 1, wherein the network node comprises a User Equipment (UE), and wherein the capability information is transmitted to the first network entity in the first PLMN over a Uu interface.

3. The network node of claim 1 or 2, wherein the capability information indicates a location of the network node.

4. The network node of clam 1, 2 or 3, wherein the at least one processor is further configured to cause the network node to: perform a registration procedure with the first PLMN; and establish a first Protocol Data Unit (PDU) session with the first PLMN, wherein the first PDU Session enables connectivity with the first network entity, wherein the capability information is transmitted to the first network entity in the first PLMN via the established first PDU Session.

5. The network node of any preceding claim, wherein the network access node functionality comprises small cell functionality that includes a 3 GPP small cell functionality or a non-3GPP small cell functionality.

6. The network node of claim 5, wherein the first configuration command comprises one or more of: a type of small cell functionality, the type of small cell functionality comprising the 3 GPP small cell functionality or the non-3GPP small cell functionality; an Internet Protocol (IP) address of a second network entity in the second PLMN for connecting to the second network entity via an Fl interface, wherein the second network entity comprises a base station-central unit (gNB-CU) or a Trusted Non-3GPP Gateway Function (TNGF); security information for connecting to the second network entity in the second PLMN; or application information for executing a small cell application or service.

7. The network node of claim 6, wherein the at least one processor is further configured to cause the network node to: establish a second PDU session with the first PLMN, wherein the second PDU session is for transferring traffic via the Fl interface; and wherein one or more Quality of Service (QoS) flows are supported for the second PDU session for transporting control information or data information with different QoS parameters.

8. The network node of any of claims 5 to 7, wherein the at least one processor is further configured to cause the network node to: transmit an acknowledgment that indicates small cell functionality is enabled at the network node, wherein the acknowledgment is transmitted in response to the network node being operable as a small cell.

9. The network node of any of claims 5 to 8, wherein the at least one processor is further configured to cause the network node to: perform a security establishment procedure with the second network entity based at least in part on the first configuration command; and perform a first setup procedure with the second network entity, in response to the the security establishment procedure, wherein the first setup procedure is an Fl setup procedure when the small cell functionality is the 3 GPP small cell functionality.

10. The network node of any preceding claim, wherein the at least one processor is further configured to cause the network node to: transmit a first request to join an orchestrated computing environment (OCE) in the first PLMN, wherein the first request to join the OCE indicates that the network node is capable of executing containerized applications; and receive a second request to deploy a containerized application, wherein the containerized application can support the network access node functionality, wherein the second request is received based at least in part on the network node joining the OCE; wherein the network node is operated as the network access node in response to deploying the containerized application.

11. The network node of any preceding claim, wherein the processor is further configured to cause the network node to: receive, from the first network entity in the first PLMN, a second configuration command to cease operating as the network access node; and in response to the second configuration command, cease operating as the network access node.

12. The network node of claim 11 , wherein the at least one processor is further configured to cause the network node to:transmit, to the first network entity, an indication of a battery level of the network node, wherein the first configuration command or the second configuration command received is based at least in part on the battery level of the network node.

13. A processor for wireless communication, comprising: at least one controller coupled with at least one memory and configured to cause the processor to: output capability information from a network node to a first network entity in a first PLMN, wherein the capability information indicates that the network node is capable of supporting network access node functionality; obtain, from the first network entity, a first configuration command to operate as a network access node for a second PLMN based at least in part on the transmitted capability information; and configure the network node to operate as a network access node that provides connectivity to the second PLMN based at least in part on the received first configuration command.

14. A method performed by a network node, the method comprising: transmitting capability information to a first network entity in a first Public Land Mobile Network (PLMN), wherein the capability information indicates that the network node is capable of supporting network access node functionality; receiving, from the first network entity, a first configuration command to operate as a network access node for a second PLMN based at least in part on the transmitted capability information; and operate as a network access node that provides connectivity to the second PLMN based at least in part on the received first configuration command.

15. A network entity in a first Public Land Mobile Network (PLMN), comprising: at least one memory; andat least one processor coupled with the at least one memory and configured to cause the network entity to: receive capability information that indicates whether a network node is capable of supporting network access node functionality; and determine whether to enable the network access node functionality supported by the network node based at least in part on the received capability information.

16. The network entity of claim 15, wherein the processor is further configured to cause the network entity to transmit, to the network node, a first configuration command to operate as a network access node for a second PLMN based at least in part on the transmitted capability information.

17. The network entity of claim 15 or 16, wherein the network functionality comprises small cell functionality that includes a 3 GPP small cell functionality or a non- 3 GPP small cell functionality.

18. The network entity of claim 15, 16 or 17, wherein the processor is further configured to cause the network entity to determine whether to enable the network access node functionality supported by the network node based at least in part on a location of the network node.

Images