Distributed computing network in a wireless communication network

Abstract

Various aspects of the present disclosure relate to a user equipment 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 user equipment to: send, to a first network entity in a mobile communication network, a first request message comprising an indication of a request for join data, wherein the join data comprises information for integrating computing resources of the user equipment into a distributed computing network; and receive, from the first network entity, a first response message comprising the join data.

Description

DISTRIBUTED COMPUTING NETWORK IN A WIRELESS COMMUNICATION NETWORKTECHNICAL FIELD

[0001] The subject matter disclosed herein relates generally to the field of implementing a distributed computing network. In particular, this document defines apparatus, processors and methods for a user equipment, a first network entity and a second network entity.BACKGROUND

[0002] A wireless communications system may include one or multiple network communication devices, such as base stations, which may support 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 is described 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 construed 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] There is provided a user equipment 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 user equipment to: send, to a first network entity in a mobile communication network, a first request message comprising an indication of a request for join data, wherein the join data comprises information for integrating computing resources of the user equipment into a distributed computing network; and receive, from the first network entity, a first response message comprising the join data.

[0005] There is provided a processor for wireless communication, comprising: at least one controller coupled with at least one memory and configured to cause the processor to: sending, to a first network entity in a mobile communication network, a first request message comprising an indication of a request for join data, wherein the join data comprises information for integrating computing resources of the user equipment into a distributed computing network; and receiving, from the first network entity, a first response message comprising the join data.

[0006] There is provided a method performed by a user equipment, the method comprising: sending, to a first network entity in a mobile communication network, a first request message comprising an indication of a request for join data, wherein the join data comprises information for integrating computing resources of the user equipment into a distributed computing network; and receiving, from the first network entity, a first response message comprising the join data.

[0007] There is provided a first network entity 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 first network entity to: receive, from the user equipment, a first request message comprising an indication of a request for join data,wherein the join data comprises information for integrating computing resources of the user equipment into a distributed computing network; and sending, to the user equipment, a first response message comprising the join data.

[0008] There provided a processor for wireless communication, comprising: at least one controller coupled with at least one memory and configured to cause the processor to: receive, from the user equipment, a first request message comprising an indication of a request for join data, wherein the join data comprises information for integrating computing resources of the user equipment into a distributed computing network; and send, to the user equipment, a first response message comprising the join data.

[0009] There is provided a method performed by a first network entity in a mobile communication network, the method comprising: receiving, from the user equipment, a first request message comprising an indication of a request for join data, wherein the join data comprises information for integrating computing resources of the user equipment into a distributed computing network; and sending, to the user equipment, a first response message comprising the join data.

[0010] There is provided a second network entity 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 second network entity to: receive, from a first network entity, a second request message comprising an indication of a request for join data, wherein the join data comprises information for integrating computing resources of a user equipment into a distributed computing network; and send, to the first network entity, a second response message comprising the join data.

[0011] There provided a processor for wireless communication, comprising: at least one controller coupled with at least one memory and configured to cause the processor to: receive, from a first network entity, a second request message comprising an indication of a request for join data, wherein the join data comprises information for integrating computing resources of a user equipment into a distributed computing network; and send, to the first network entity, a second response message comprising the join data.

[0012] There is provided a method performed by a second network entity, the method comprising: receiving, from a first network entity, a second request message comprising an indication of a request for join data, wherein the join data comprises information for integrating computing resources of a user equipment into a distributed computing network; and sending, to the first network entity, a second response message comprising the join data.BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Figure 1 illustrates an example of a wireless communications system in accordance with aspects of the present disclosure.

[0014] Figure 2 illustrates an example of a distributed computing network in a wireless communication network in accordance with aspects of the present disclosure.

[0015] Figure 3 illustrates an example of a distributed computing network in a wireless communication network in accordance with aspects of the present disclosure.

[0016] Figure 4 illustrates an example of a method for a distributed computing network in a wireless communication network in accordance with aspects of the present disclosure.

[0017] Figure 5 illustrates an example of a method for a distributed computing network in a wireless communication network in accordance with aspects of the present disclosure.

[0018] Figure 6 illustrates an example of a user equipment (UE) 600 in accordance with aspects of the present disclosure.

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

[0020] Figure 8 illustrates an example of a network equipment (NE) 800 in accordance with aspects of the present disclosure.

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

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

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

[0024] A distributed computing network in a wireless communication network may comprise computing resources from various network entities. The computing resources may be managed and controlled by a Management and Orchestration (MANO) system of the mobile network. In the past, the computing resources have traditionally been confined to dedicated network entities (or network functions) situated at the edge, within the access network, or dispersed throughout the core network infrastructure.

[0025] One or more User Equipment(s) (UEs) may serve as endpoints in the network for data transmission and reception, In the past, UEs have not been configured to offer computing resources that can be managed and controlled by the MANO system of the network. The UEs may be at the extreme edge of the network. The UEs may be advanced mobile handsets, Internet of Things (loT) devices, residential gateways, or other connected technologies that are increasingly becoming more powerful.

[0026] There is an ongoing need to improve distributed computing networks in wireless communication networks. For example, this is an ongoing need to reduce latency; in particular for real-time applications.

[0027] Examples disclosed herein may generally relate to extending computing resources of a distributed computing network in a wireless communication network to UEs in the wireless communication network. The wireless communication network may be a mobile communication network (hereinafter referred to as mobile network or network). The mobile network may be a 5G network. Extending such computing resources to UEs tends to enable the deployment of extreme edge services directly on the devices (e.g., one or more UEs). Further it tends to allow immediate data processing and response without the latency associated with data transmission to centralized network locations. This capability tends to be beneficial for applications requiring real-time decision-making and tends to enhance the overall user experience by providing faster and more efficient services.

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

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

[0030] 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 herein may 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 signalling, transmit signalling) over a Uu interface.

[0031] 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 ormultiple 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 associated with the same or different radio access technologies may overlap, but the different geographic coverage areas may be associated with different NE 102.

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

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

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

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

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

[0037] 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 5 G 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.

[0038] One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., / r=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., / r=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., / r=l) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., / r=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., / r=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., / r=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0039] A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames). Each frame may have a duration, for example, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.

[0040] Additionally, or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. The number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100. For instance, the first, second, third, fourth, and fifth numerologies (i.e., / r=0, jU=l, / r=2, jU=3, / r=4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively.# Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing), a slot may include 12symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., / r=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

[0041] In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4 (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and FR5 (114.25 GHz - 300 GHz). In some implementations, the NEs 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the NEs 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data). In some implementations, FR2 may be used by the NEs 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.

[0042] FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies). For example, FR1 may be associated with a first numerology (e.g., / r=0), which includes 15 kHz subcarrier spacing; a second numerology (e.g., / r=l), which includes 30 kHz subcarrier spacing; and a third numerology (e.g., / r=2), which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies). For example, FR2 may be associated with a third numerology (e.g., / r=2), which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., / r=3), which includes 120 kHz subcarrier spacing.

[0043] Examples described herein generally relate to mobile communications technology and network architecture, particularly to a method for leveraging one or more UEs as computational resources within a mobile network’s management and orchestration layer.

[0044] With the ongoing evolution of computing, UEs are increasingly equipped with robust resources such as high-performance processors, extensive memory capacities, and sophisticated graphics processing units. In the past, these resources have predominantly been harnessed for local operations and native applications. A growing variety of UEs offer advanced computing platforms, featuring an array of virtualization and containerization capabilities. Such capabilities may be leveraged by the network infrastructure. The computing resources of UEs may be integrated in the management and orchestration layer of the network. This tends to enable the network to support distributed computing resources at the extreme edge and deploy a vast range of containerized services on the UEs.

[0045] UEs continue to evolve, with each new generation offering more substantial computational capabilities. There is an increasing demand for services to be deployed closer to users, at the extreme edge of the network (e.g., on UEs), to take advantage of lower latency and higher bandwidth utilization. The computing resources of UEs may be integrated into the MANO architecture of the network. By doing so, mobile networks can transition from a model that views UEs solely as endpoints to one where they are active computational participants, thereby bringing computing power to the periphery of the network.

[0046] Integrating the computing resources of UEs into the MANO system of the network tends to allow for a more efficient and dynamic allocation of computational tasks, particularly for applications that require real-time processing and quick responsiveness. This tends to be beneficial for latency-sensitive applications such as augmented reality or local content caching. Integrating the computing resources of UEs into the MANO system of the network tends to lead to enhanced scalability and flexibility in managing network load, as these devices can provide supplementary computing power during peak times. Integrating the computing resources of UEs into the MANO system of the network tends to achieve higher degrees of resilience and redundancy for the network, as the distributed nature of these resources may allow for continued service provision even when certain network segments are compromised. Integrating the computing resources of UEs into the MANO system of the network tends to improve the overall network efficiency byharnessing idle or underused computational resources within UEs; this tends to reduce energy consumption and reduce operational costs.

[0047] Examples described herein generally enable one or more UEs to integrate their computing resources into the MANO system of a mobile network and then receive commands from the MANO system to deploy and run workloads (apps).

[0048] Figure 2 illustrates an example of a distributed computing network 200 in a wireless communication network in accordance with aspects of the present disclosure.

[0049] The distributed computing network 200 comprises a Management and Orchestration (MANO) 250. The MANO 250 may be a MANO system. The MANO 250 may be a MANO domain. The MANO 250 comprises a container orchestration and management system 255. The container orchestration and management system 255 may be a Kubernetes Cluster. The container orchestration and management system 255 may be a control plane.

[0050] The container orchestration and management system 255 is connected to an Access Network 220. The Access Network 220 may comprise one or more worker nodes. Each of the one or more worker nodes may run one or more containers. The one or more containers may realise one or more access network functions. The Access Network 220 may be a Radio Access Network (RAN).

[0051] The container orchestration and management system 255 is connected to a 5G / Beyond 5G (B5G) Core Network 230. The 5G / B5G Core Network 230 may comprise one or more worker nodes. Each of the one or more worker nodes may run one or more containers. The one or more containers may realise one or more core network functions. At least one of the one or more core network functions may be an Access & Mobility Management Function (AMF). At least one of the one or more core network functions may be a Session Management Function (SMF). At least one of the one or more core network functions may be a User Plane Function (UPF). At least one of the one or more core network functions may be an Application Function (AF). At least one of the one or more core network functions may be a Policy Control Function (PCF).

[0052] The Access Network 220 and 5G / B5G Core Network 230 are connected via an N2 / N3 interface. The 5G / B5G Core Network 230 is connected to a Data Network 240 via an N6 interface.

[0053] The Access Network 220 connects to one or more UEs 210. The one or more UEs 210 typically runs one or more applications for its own use. At least one of the one or more UEs 210 may be an extreme edge device. At least one of the one or more UEs 210 may be a residential gateway. At least one of the one or more UEs 210 may be a mobile hotspot. At least one of the one or more UEs 210 may be a robot.

[0054] Examples described herein may relate generally to the operational principles of Kubernetes. Kubernetes may be a Kubernetes Cluster. Kubernetes may be a Kubernetes environment. Kubernetes relate to a leading open-source platform for automating the deployment, scaling, and management of containerized applications. In mobile networks, Kubernetes may support cloud-native functional components (such as AMF, SMF, PCF, etc.) through its robust and scalable architecture.

[0055] In a Kubernetes environment, a cluster may be a collection of computers (which may be called nodes) that work together to run containerized applications. Each cluster may comprise a control plane, which may be referred to as the master node. The master node may maintain a global view of the cluster and manage its state and configuration. Each cluster may also comprise one or more worker nodes, which are responsible for actually running the containerized applications.

[0056] The distributed computing network 200 may be an example of a Kubernetes cluster deployed within a 5G mobile network to orchestrate containerized network functions. The control plane (master node) resides in the MANO domain 250 of the network, while the worker nodes are deployed in the access network 220 to run containerized network functions, like general Node Bs (gNBs), and within the 5G core network 230 to run containerized network functions, like AMF, SMF, PCF, etc. Worker nodes may be deployed in edge networks within the mobile network infrastructure.

[0057] A worker node in the access network 220 or in the core network 230 may receive and run containerized network functions (apps) from the control plane only after itis integrated into the Kubernetes cluster; for example, after the worker node joins the Kubernetes cluster. For this purpose, a worker node may establish a secure Transport Layer Security (TLS) connection with the master node and exchange some information. To successfully establish this connection and join the cluster, the worker node requires “join data”:

[0058] The join data may comprise the contact address of the master node. The master node may comprise an Application Programming Interface (API) server. The contact address of the master node may comprise a port number. The contact address of the master node may comprise a Fully Qualified Domain Name (FQDN). The contact address of the master node may comprise an IP address.

[0059] The join data may comprise a Discovery Token Certificate Authority (CA) Certificate (Cert) Hash. The Discovery Token CA Cert Hash may comprise a hash representing the master node's Certificate Authority certificate. The Discovery Token CA Cert Hash may allow the worker node to verify the authenticity of the master's certificate during the TLS connection. The Discovery Token CA Cert Hash may ensure that the worker node is joining the correct cluster. The Discovery Token CA Cert Hash may ensure that the worker node has not been intercepted by a man-in-the-middle attack.

[0060] The join data may comprise a bootstrap token. The bootstrap token may be a token generated by the master node. A worker node may use the bootstrap token to join the cluster. The bootstrap token may provide a form of authorization such that only worker nodes that possess the bootstrap token may join the cluster.

[0061] Each machine in the access network 220 or in the core network 230 that wants to join the Kubernetes cluster and operate as a worker node, may be provisioned with the join data by an administrator; for example, when typing a command to trigger the join procedure. For example, the administrator can type the following command in a machine to join this machine to a Kubernetes cluster: “kubeadm join <master node address> :<master node port> —token token vcdue -discovery-token-ca-cert-hash <hash yalue>” (see https: / / kubernetes.io / docs / reference / setup-tools / kubeadm / kubeadm-join / ).

[0062] Figure 3 illustrates an example of a distributed computing network 300 in a wireless communication network in accordance with aspects of the present disclosure.

[0063] The distributed computing network 300 comprises a MANO 350. The MANO 350 may be a MANO system. The MANO 350 may be a MANO domain. The MANO 350 comprises a container orchestration and management system 355. The container orchestration and management system 355 may be a Kubernetes Cluster. The container orchestration and management system 355 may be a control plane.

[0064] The container orchestration and management system 355 is connected to an Access Network 320. The Access Network 320 may comprise one or more worker nodes. Each of the one or more worker nodes may run one or more containers. The one or more containers may realise one or more access network functions. The Access Network 320 may be a RAN.

[0065] The container orchestration and management system 355 is connected to a 5G / B5G Core Network 330. The 5G / B5G Core Network 330 may comprise one or more worker nodes. Each of the one or more worker nodes may run one or more containers. The one or more containers may realise one or more core network functions. At least one of the one or more core network functions may be an AMF. At least one of the one or more core network functions may be an SMF. At least one of the one or more core network functions may be a UPF. At least one of the one or more core network functions may be an AF. At least one of the one or more core network functions may be a PCF.

[0066] The Access Network 320 and 5G / B5G Core Network 330 are connected via an N2 / N3 interface. The 5G / B5G Core Network 330 is connected to a Data Network 340 via an N6 interface.

[0067] The Access Network 320 connects to one or more UEs 310. At least one of the one or more UEs 310, may be a worker node. At least one of the one or more UEs 310, may run one or more containers that provide one or more extreme edge services. At least one of the one or more UEs 310 may be an extreme edge device. At least one of the one or more UEs 310 may be a residential gateway. At least one of the one or more UEs 310 may be a mobile hotspot. At least one of the one or more UEs 310 may be a robot.

[0068] One or more end devices(s) 315 may be in the vicinity of at least one of the one or more UEs 310. At least one of the one or more end device(s) 315 may be configured to use the one or more extreme edge services.

[0069] Examples described herein generally relate to a method with which the one or more UEs 310 may receive the join data required to join a Kubernetes cluster when it establishes a data connection (for example, a Packet Data Unit (PDU) Session) with the mobile network. This enables the one or more UEs 310 to be integrated into a Kubernetes cluster in the mobile network and operate as a worker node. In turn, the mobile network may schedule and deploy directly on the one or more UEs 310 containerized apps. For example, containerized apps may be apps that offer services at the extreme edge of the network and can be utilized by one or more end device(s) 315 in the vicinity of the at least one of the one or more UEs 310. An example of this setup is illustrated in the distributed computing network 300 in Figure 3 and, effectively, turns the one or more UEs 310 into a distributed, crowd-sourced computing network that tends to extend the capabilities of the mobile network.

[0070] The one or more UEs 310 may be at least one of: a smartphone, an Internet of Things (loT) device, a vehicle, a residential gateway, a robot. Integrating the one or more UEs 310 into a Kubernetes cluster in a mobile network infrastructure tends to leverage the power of Kubernetes for orchestration and container management directly at the extreme edge of the network. This approach tends to enhance the functionality of mobile networks by enabling the deployment of containerized applications directly onto the one or more UEs 310 and tends to offer significant advantages, particularly in terms of responsiveness, data privacy, and network efficiency.

[0071] Containerized applications deployed on the one or more UEs 310 may act as local caching nodes for popular content (videos, music, web pages), which tends to reduce latency and network traffic by serving this content to nearby devices.

[0072] The one or more UEs 310 may run containerized applications that process data from surrounding loT devices locally, before sending processed data or insights back to the central system. This tends to enable immediate processing of loT data, which may be crucial for time-sensitive applications.

[0073] The one or more UEs 310 may run containerized Artificial Intelligence (Al) models that perform inference tasks, such as object recognition on static pictures or video. This tends to enable at least one of the one or more end devices 315 to detect specific objects in pictures or video by utilizing the Al models offered by the one or more UEs 310.

[0074] The one or more UEs 310 in vehicles may run containerized applications that communicate with other vehicles and infrastructure which tends to optimize traffic management, route planning, and safety features.

[0075] Examples described herein may empowers the one or more UEs 310 to be integrated into the orchestration layer of the mobile network and operate as worker nodes. Examples described herein may enable the one or more UEs 310 to be integrated into a Kubernetes cluster in a mobile network and operate as worker nodes. Hence, worker nodes may be deployed at user devices, not only within the network infrastructure, and create a distributed, crowd-sourced computing network that extends the capabilities of the mobile network.

[0076] The one or more UEs 310 that want to be integrated into a Kubernetes cluster, request and receive the data required to join the Kubernetes cluster (the join data) in a secure manner. For example, the one or more UEs 310 may be configured to receive join data during establishment of a data connection with the mobile network. In another example, the one or more UEs 310 may be configured to receive join data during establishment of a PDU session with the mobile network. In another example, the one or more UEs 310 may be configured to receive join data after establishing a data connection with the mobile network. In another example, the one or more UEs 310 may be configured to receive join data after establishing a PDU session with the mobile network.

[0077] Figure 4 illustrates an example of a method 400 for a distributed computing network in a wireless communication network in accordance with aspects of the present disclosure.

[0078] The method 400 is performed by one or more UE(s) 410, an Access Network 420, an AMF 434, an SMF 436, a UPF 438 and a MANO system 450. The MANO system 450 may comprise one or more Kubernetes clusters.

[0079] Generally, the method 400 enables the one or more UE(s) 410 to request and receive the join data required to join a Kubernetes cluster in a mobile network.

[0080] The method 400 starts at step 471 in which the one or more UE(s) 410 register with the mobile network as normal. During the registration, a successfully mutual authentication procedure takes place.

[0081] At step 472, each of the one or more UE(s) 410 send a first request message. The UE 410 may send the first request message to the Access Network 420. The Access Network 420 may send the first request message to the AMF 434. The AMF 434 may send the first request message to the SMF 436.

[0082] The first request message comprises an indication of a request for join data. The indication of a request for join data may comprise an indication to provide the UE 410 with join data. The first request message may comprise an identifier for the UE 410. The indication of a request for join data may comprise an indication that the UE 410 wants to receive join data for joining a Kubernetes cluster. The indication of a request for join data may comprise an indication that the UE 410 wants to join a Kubernetes cluster in the mobile network. The indication of a request for join data may comprise an indication that the UE 410 is capable of providing its computing resources to the network. The indication of a request for join data may comprise an indication that the network may deploy one or more containerized applications to the UE 410. The indication of a request for join data may comprise an indication that the network may deploy one or more workloads to the UE 410.

[0083] The first request message may be a Packet Data Unit (PDU) Session Establishment Request message. The PDU Session Establishment Request message may comprise an indication of a request for join data. The indication of a request for join data may comprise an indication that the UE 410 wants to join a Kubernetes cluster in the mobile network. The first request message goes through the access network 420 and the AMF 434 and is terminated at the SMF 436 in the core network.

[0084] In step 473, the SMF 436 determines whether the UE 410 is allowed to join a Kubernetes cluster in the network. This may be determined based on UE subscription datathat is retrieved from a Unified Data Management (UDM) function. If the UE 410 is not allowed to join a Kubernetes cluster, the SMF 436 may ignore the UE’s 410 request for join data and steps 474 to 480 may not be performed. The UE may not be allowed to join any Kubernetes cluster. The SMF 436 may ignore the UE’s 410 request to join a Kubernetes cluster and steps 474 to 480 may not be performed. If the UE 410 is allowed to join a Kubernetes cluster, the steps 474 to 480 are performed.

[0085] Alternatively, the determination of whether the UE 410 is allowed to join a Kubernetes cluster in the network may be made by the MANO system 450 in the next step.

[0086] In step 474, in response to determining that the UE 410 is allowed to join a Kubernetes cluster in the network, or in response to receiving the indication of a request for join data (see the alternative in step 473), the SMF 436 sends a second request message to the MANO 450 system in the mobile network to retrieve join data for a Kubernetes cluster. The second request message may be a Join Data Request message. The second request message may contain the identifier for the UE 410. The second request message may comprise a Kubernetes cluster identifier. The Kubernetes cluster identifier may be a Kubernetes cluster identity. The Kubernetes cluster identified may be provided to the SMF 436 in the UE subscription data that was retrieved from the UDM in step 473. If the message contains the identifier for the UE 410, then the Kubernetes cluster identifier may be determined by the MANO 450 system. For example, the MANO 450 system may determine the Kubernetes cluster identifier based on preconfigured policy or other information. The identifier for the UE may be a UE identity.

[0087] In step 475. the MANO 450 system obtains the join data or generates the join data after receiving the second request message. The join data may comprise one or more of the address and port of the master node, the Discovery Token CA Cert Hash, and / or the Bootstrap token. The address and port of the master node, as well as the Discovery Token CA Cert Hash, may be known and fixed for each Kubernetes cluster. However, the Bootstrap token may be dynamically generated mainly for security reasons (for example, to avoid using the same Bootstrap token more than once). The Bootstrap token may be generated by existing mechanisms.

[0088] In step 476, the MANO 450 system responds with a second response message and returns to SMF 436 the join data for the Kubernetes cluster for the UE 410 to join. The second response message may be a Join Data Response message.

[0089] In step 477, the SMF 436 responds to UE 410 by sending a first response message that contains the join data received from the MANO 450 system. The first response message may be a PDU Session Establishment Accept message that accepts the PDU Session requested by the UE 410 in step 472.

[0090] In step 478, via the established PDU Session, the UE 410 creates a secure connection with the master node (or API server) in a Kubernetes cluster in the MANO 450 system. The UE 410 establishes this connection to the address and port received within the join data. The UE 410 also validates the certificate provided by the master node using the received Discovery Token CA Cert Hash.

[0091] In step 479, the UE 410 provides to master node the bootstrap token that was received within the join data. The master node authorizes the UE 410 to join the Kubernetes cluster if the bootstrap token is valid. The bootstrap token may be a join token.Subsequently, the master node registers the UE 410 in the Kubernetes cluster and receives information from the UE 410 regarding its computing resources.

[0092] In step 480, the master node deploys one or more containerized applications in the UE 410. The master node monitors these applications; for example, based on existing mechanisms. The master node may execute lifecycle management operations. The master node may modify the resources allocated for the one or more containerized applications. The master node may scale up the resources allocated for the one or more containerized applications. The master node may scale down the resources allocated for the one or more containerized applications. The master node may delete the one or more containerized applications in the UE 410; for example, the master node may delete the one or more containerized applications which are no longer needed.

[0093] The method 400 relates specifically to a UE 410 configured to join a Kubernetes cluster. However, it will be understood that principles and features in the method 400 and herein discussed can be applied to other types of distributed computing networks. Forexample, the method 400 may relate to UE 410 configured to join a container orchestration network. Furthermore, it will be understood that principles and features in the method 400 and herein discussed can be applied more broadly to any type of networked computing system that manages distributed resources.

[0094] Figure 5 illustrates an example of a method 500 for a distributed computing network in a wireless communication network in accordance with aspects of the present disclosure.

[0095] The method 500 is performed by one or more UE(s) 510, an Access Network 520, an AMF 534, an SMF 536, a UPF 538, an AF 539 and a MANO system 550. The MANO system 550 may comprise one or more Kubernetes clusters.

[0096] The method 500 is an alternative method to method 400. In the method 500, the one or more UE(s) 510 may request and receive the data required to join the Kubernetes cluster (the join data) in a mobile network. The method 500 tends not to impact the PDU Session establishment procedure. The method 500 also tends not to impact the SMF 536 in the 5G network. Instead, it introduces a new Application Function (AF) 539 via which the one or more UE(s) 510 receive the join data. Method 500 may be an application-layer method.

[0097] The method 500 starts at step 517a in which the one or more UE(s) 510 register with the mobile network. The one or more UE(s) 510 and mobile network then execute a mutual authentication.

[0098] In step 571b, the one or more UE(s) 510 establishes a PDU Session with the mobile network. The one or more UE(s) 510 then obtain IP connectivity.

[0099] In step 572, each of the one or more UE(s) 510 send a first request message. The UE 510 may send the first request message to the Access Network 520. The Access Network 520 may send the first request message to the UPF 538. The UPF 538 may send the first request message to the AF 539.

[0100] The first request message may be an application-layer first request message. The first request message may comprise an indication of a request for join data. The indicationof a request for join data may comprise an indication to provide the UE 510 with join data. The first request message may comprise an identifier for the UE 510. The indication of a request for join data may comprise an indication that the UE 510 wants to receive join data for joining a Kubernetes cluster. The indication of a request for join data may comprise an indication that the UE 510 wants to join a Kubernetes cluster in the mobile network. The indication of a request for join data may comprise an indication that the UE 510 is capable of providing its computing resources to the network. The indication of a request for join data may comprise an indication that the network may deploy one or more containerized applications to the UE 510. The indication of a request for join data may comprise an indication that the network may deploy one or more workloads to the UE 510.

[0101] In step 573, the AF 536 determines whether the UE 510 is allowed to join a Kubernetes cluster in the network. This may be determined based on UE subscription data that is retrieved from a Unified Data Management (UDM) function. If the UE 510 is not allowed to join a Kubernetes cluster, the AF 536 may ignore the UE’s 510 request for join data and steps 574 to 580 may not be performed. The UE may not be allowed to join any Kubernetes cluster. If the UE 510 is allowed to join a Kubernetes cluster, the steps 574 to 580 are performed.

[0102] Alternatively, the determination of whether the UE 510 is allowed to join a Kubernetes cluster in the network may be made by the MANO system 550 in the next step.

[0103] In step 574, in response to determining that the UE 510 is allowed to join a Kubernetes cluster in the network, or in response to receiving the indication of a request for join data (see the alternative in step 573), the AF 439 sends a second request message to the MANO 550 system in the mobile network. The second request message comprises an indication of a request for join data. The indication of a request for join data may comprise an indication of a request to retrieve join data for a Kubernetes cluster. The second request message may be a Join Data Request message. The second request message may contain the identifier for the UE 510. The second request message may comprise a Kubernetes cluster identifier. The Kubernetes cluster identified may be provided to the AF 439 in the UE subscription data that was retrieved from the UDM in step 573. If the message contains the identifier for the UE 510, then a Kubernetes cluster identifier may be determined by theMANO 550 system. For example, the MANO 550 system may determine a Kubernetes cluster identifier based on preconfigured policy or other information.

[0104] In step 575. the MANO 550 system obtains the join data or generates the join data after receiving the second request message. The join data may comprise one or more of the address and port of the master node, the Discovery Token CA Cert Hash, and / or the Bootstrap token. The address and port of the master node, as well as the Discovery Token CA Cert Hash, may be known and fixed for each Kubernetes cluster. However, the Bootstrap token may be dynamically generated mainly for security reasons (for example, to avoid using the same Bootstrap token more than once). The Bootstrap token may be generated by existing mechanisms.

[0105] In step 576, the MANO 550 system responds with a second response message and returns to AF 539 the join data for a Kubernetes cluster for the UE 510 to join. The second response message may be a Join Data Response message.

[0106] In step 577, the AF 539 responds to UE 510 by sending a first response message that contains the join data received from the MANO 550 system. The first response message may be an application-layer first response message.

[0107] In step 578, the UE 510 creates a secure connection with the master node (or API server) in a Kubernetes cluster in the MANO 550 system. The UE 510 may establish this connection to the address and port received within the join data. The UE 510 may also validate the certificate provided by the master node using the received Discovery Token CA Cert Hash.

[0108] In step 579, the UE 510 provides to master node the bootstrap token that was received within the join data. The master node authorizes the UE 510 to join the Kubernetes cluster if the bootstrap token is valid. The bootstrap token may be a join token.Subsequently, the master node may register the UE 510 in the Kubernetes cluster and receives information from the UE 510 regarding its computing resources.

[0109] In step 580, the master node deploys one or more containerized applications in the UE 510. The master node monitors these applications; for example, based on existing mechanisms. The master node may execute lifecycle management operations. The masternode may modify the resources allocated for the one or more containerized applications. The master node may scale up the resources allocated for the one or more containerized applications. The master node may scale down the resources allocated for the one or more containerized applications. The master node may delete the one or more containerized applications in the UE 510; for example, the master node may delete the one or more containerized applications which are no longer needed.

[0110] Any step in method 500 may be the same or similar to any step in method 400. Generally, one or more steps performed by the SMF 436 in method 400 may be performed by the AF 539 in method 500. The UE 510 may be provisioned with the IP address or Fully Qualified Domain Name (FQDN) of the AF 539. The UE 510 may discover the IP address or FQDN of the AF 539; for example, using Domain Name System (DNS) procedures.

[0111] In method 500, the First Request Message may be an HTTP POST request message. The HTTP POST request message may include the indication that UE want to join a Kubernetes cluster. In method 500, the First Request Message may be an HTTP GET request message. The HTTP GET request message may include the indication that UE want to join a Kubernetes cluster. In method 500, the First Response Message may be a 200 OK response message including the requested join data.

[0112] The UE 510 and AF 539 may be mutually authenticated using an existing security procedure. The existing security procedure may be an Authentication and Key Management for Applications (AKMA) procedure, as defined in 3GPP TS 33.353 VI 8.3.0.

[0113] Method 500 may not impact the 5G network. Method 500 may be more easily implemented in practice compared to method 400.

[0114] The method 500 relates specifically to a UE 510 configured to join a Kubernetes cluster. However, it will be understood that principles and features in the method 500 and herein discussed can be applied to other types of distributed computing networks. For example, the method 500 may relate to UE 510 configured to join a container orchestration network. Furthermore, it will be understood that principles and features in the method 500and herein discussed can be applied more broadly to any type of networked computing system that manages distributed resources.

[0115] Figure 6 illustrates an example of a UE 600 in accordance with aspects of the present disclosure. The UE 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.

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

[0117] 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 UE 600 to perform various functions of the present disclosure.

[0118] 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 UE 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 special-purpose computer.

[0119] In some implementations, the processor 602 and the memory 604 coupled with the processor 602 may be configured to cause the UE 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 UE 600 in accordance with examples as disclosed herein. The UE 600 may be configured to support a means for sending, to a first network entity in a mobile communication network, a first request message comprising an indication of a request for join data, wherein the join data comprises information for integrating computing resources of the user equipment into a distributed computing network; and receiving, from the first network entity, a first response message comprising the join data.

[0120] The controller 606 may manage input and output signals for the UE 600. The controller 606 may also manage peripherals not integrated into the UE 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.

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

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

[0123] 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 onemodulator 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.

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

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

[0126] The controller 702 may be configured to manage and coordinate various operations (e.g., signalling, 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.

[0127] The controller 702 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 704 and determine subsequent instruct! on(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 data within 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.

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

[0129] 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-readableinstructions 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.

[0130] 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 and manipulate 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.

[0131] 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 sending, to a first network entity in a mobile communication network, a first request message comprising an indication of a request for join data, wherein the join data comprises information for integrating computing resources of the user equipment into a distributed computing network; and receiving, from the first network entity, a first response message comprising the join data.

[0132] Alternatively, the processor 700 may be configured to or operable to support a means for receiving, from the user equipment, a first request message comprising anindication of a request for join data, wherein the join data comprises information for integrating computing resources of the user equipment into a distributed computing network; and sending, to the user equipment, a first response message comprising the join data.

[0133] Alternatively, the processor 700 may be configured to or operable to support a means for receiving, from a first network entity, a second request message comprising an indication of a request for join data, wherein the join data comprises information for integrating computing resources of a user equipment into a distributed computing network; and sending, to the first network entity, a second response message comprising the join data.

[0134] Figure 8 illustrates an example of a NE 800 in accordance with aspects of the present disclosure. 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.

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

[0136] 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 some other 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.

[0137] 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 special-purpose computer.

[0138] 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, from the user equipment, a first request message comprising an indication of a request for join data, wherein the join data comprises information for integrating computing resources of the user equipment into a distributed computing network; and sending, to the user equipment, a first response message comprising the join data. Alternatively, the NE 800 may be configured to support a means for receiving, from a first network entity, a second request message comprising an indication of a request for join data, wherein the join data comprises information for integrating computing resources of a user equipment into a distributed computing network; and sending, to the first network entity, a second response message comprising the join data.

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

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

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

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

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

[0144] At 902, the method 900 may include sending, to a first network entity in a mobile communication network, a first request message comprising an indication of a request for join data, wherein the join data comprises information for integrating computingresources of the user equipment into a distributed computing network. 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 UE as described with reference to Figure 6.

[0145] At 904, the method 900 may include receiving, from the first network entity, a first response message comprising the join data. 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 UE as described with reference to Figure 6.

[0146] It should be noted that the method 900 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.

[0147] Figure 10 illustrates a flowchart of a method 1000 in accordance with aspects of the present disclosure. The operations of the method 1000 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.

[0148] At 1002, the method 1000 may include receiving, from the user equipment, a first request message comprising an indication of a request for join data, wherein the join data comprises information for integrating computing resources of the user equipment into a distributed computing network. 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.

[0149] At 1004, the method 1000 may include sending, to the user equipment, a first response message comprising the join data. 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.

[0150] Figure 11 illustrates a flowchart of a method 1100 in accordance with aspects of the present disclosure. The operations of the method 1100 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.

[0151] At 1102, the method 1100 may include receiving, from a first network entity, a second request message comprising an indication of a request for join data, wherein the join data comprises information for integrating computing resources of a user equipment into a distributed computing network. The operations of 1102 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1102 may be performed by a NE as described with reference to Figure 8.

[0152] At 1104, the method 1100 may include sending, to the first network entity, a second response message comprising the join data. The operations of 1104 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1104 may be performed by a NE as described with reference to Figure 8.

[0153] There is provided a user equipment 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 user equipment to: send, to a first network entity in a mobile communication network, a first request message comprising an indication of a request for join data, wherein the join data comprises information for integrating computing resources of the user equipment into a distributed computing network; and receive, from the first network entity, a first response message comprising the join data.

[0154] Such a user equipment tends to improve the efficiency and dynamic allocation of computational tasks in the distributed computing network. The improved efficiency of the distributed computing network tends to improve energy consumption and reduce operational costs of the distributed computing network. In addition, the user equipment tends to provide additional computing power to the distributed computing network which tends to enhance scalability and flexibility in managing network load and tends to improve resilience and redundancy in the distributed computing network.

[0155] The first network entity may be a worker node in the distributed computing network. The first network entity may comprise a first network function. The first network function may be a Session Management Function, SMF. The first network function may be application Function, AF. The first network entity may comprise a master node. A Management and Orchestration System, MANO may comprise the first network entity.

[0156] The at least one processor coupled with the at least one memory being configured to cause the user equipment to send, to the first network entity, the first request message may comprise the at least one processor coupled with the at least one memory being further configured to cause the user equipment to send the first request message to the first network entity via an access network. The at least one processor coupled with the at least one memory being configured to cause the user equipment to send, to the first network entity, the first request message may comprise the at least one processor coupled with the at least one memory being further configured to cause the user equipment to send the first request message to the first network entity via a Radio Access Network, RAN. The at least one processor coupled with the at least one memory being configured to cause the user equipment to sending, to the first network entity, the first request message may comprise the at least one processor coupled with the at least one memory being further configured to cause the user equipment to send the first request message to the first network entity via an Access & Mobility Management Function, AMF. The at least one processor coupled with the at least one memory being configured to cause the user equipment to send, to the first network entity, the first request message may comprise the at least one processor coupled with the at least one memory being further configured to cause the user equipment to send the first request message to the first network entity via a Session Management Function, SMF. The at least one processor coupled with the at least one memory being configured to cause the user equipment to send, to the first network entity, the first request message may comprise the at least one processor coupled with the at least one memory being further configured to cause the user equipment to send the first request message to the first network entity via a User Plane Function, UPF. The at least one processor coupled with the at least one memory being configured to cause the user equipment to send, to the first network entity, the first request message may comprise the at least one processor coupled with the at least one memory being further configured to cause the user equipment to send the first request message to the first network entity via an Application Function, AF.

[0157] The at least one processor coupled with the at least one memory being configured to cause the user equipment to receive, from the first network entity, the first response message may comprise the at least one processor coupled with the at least onememory being further configured to cause the user equipment to receive the first response message from the first network entity via an access network. The at least one processor coupled with the at least one memory being configured to cause the user equipment to receive, from the first network entity, the first response message may comprise the at least one processor coupled with the at least one memory being further configured to cause the user equipment to receive the first response message from the first network entity via a Radio Access Network, RAN. The at least one processor coupled with the at least one memory being configured to cause the user equipment to receive, from the first network entity, the first response message may comprise the at least one processor coupled with the at least one memory being further configured to cause the user equipment to receive the first response message from the first network entity via an Access & Mobility Management Function, AMF. The at least one processor coupled with the at least one memory being configured to cause the user equipment to receive, from the first network entity, the first response message may comprise the at least one processor coupled with the at least one memory being further configured to cause the user equipment to receive the first response message from the first network entity via a Session Management Function, SMF. The at least one processor coupled with the at least one memory being configured to cause the user equipment to receive, from the first network entity, the first response message may comprise the at least one processor coupled with the at least one memory being configured to cause the user equipment to receive the first response message from the first network entity via a User Plane Function, UPF. The at least one processor coupled with the at least one memory being configured to cause the user equipment to receive, from the first network entity, the first response message may comprise the at least one processor coupled with the at least one memory being configured to cause the user equipment to receive the first response message from the first network entity via an Application Function, AF.

[0158] The request for join data may indicate a need for join data. The request for join data may comprise one or more bit(s) indicating the request for join data. The request for join data may comprise one or more bit(s) indicating the need for join data.

[0159] The distributed computing network may be part of the mobile communication network. The distributed computing network may comprise a Kubernetes cluster. Thedistributed computing network may comprise a container orchestration network. The distributed computing network may be part of the mobile communication network. The mobile communication network may comprise a 5G mobile network. The distributed computing network may comprise a plurality of nodes that work together to run one or more containerized applications. The distributed computing network may comprise a control plane. The control plane may be a master node. The distributed computing network may comprise one or more worker nodes. The one or more worker nodes may be computational nodes. The mobile communication network may be a wireless communication network.

[0160] The first network entity may comprise a session management function, SMF. The first request message may be a packet data unit, PDU, session establishment request message. The first response message may be a packet data unit, PDU, session establishment accept message.

[0161] The first network entity may comprise an application function. The first request message may be an application-layer request message. The application-layer request message may be sent over an established packet data unit, PDU, session.

[0162] The established packet data unit, PDU, session may be established between the user equipment and the mobile communication network. The established packet data unit, PDU, session may be established between the user equipment and the access network. The established packet data unit, PDU, session may be established between the user equipment and the AMF. The established packet data unit, PDU, session may be established between the user equipment and the SMF. The established packet data unit, PDU, session may be established between the user equipment and the UPF. The first response message may be an application-layer response message. The application-layer response message may be sent over the established PDU session.

[0163] The at least one processor coupled with the at least one memory may be further configured to cause the user equipment to: use the join data to integrate the user equipment into the distributed computing network as a worker node. The worker node may be a computational node.

[0164] The join data may comprise one or more of: a contact address of a master node of the distributed computing network; a first token for verifying the master node; and / or a second token for authorizing the user equipment as a worker node. The first token may be a discovery token. The second token may be a bootstrap token. A Management and Orchestration System, MANO of the distributed computing network may comprise the master node. The master node may comprise an Application Programming Interface, API, server. The contact address of the master node may comprise a port number. The contact address of the master node may comprise a Fully Qualified Domain Name, FQDN. The contact address of the master node may comprise an Internet Protocol, IP, address. The first token may be a discovery token Certificate Authority, CA, certificate hash. The second token may be generated by the master node. The second token may indicate an authorization for computing resources of the user equipment to join the distributed computing network.

[0165] The at least one processor coupled with the at least one memory may be further configured to cause the user equipment to: establish a secure connection with the master node using the contact address of the master node of the distributed computing network. The secure connection may be established over an established PDU session. The established packet data unit, PDU, session may be established between the user equipment and the mobile communication network. The at least one processor coupled with the at least one memory may be further configured to cause the user equipment to: send the second token to the master node over the established secure connection.

[0166] The at least one processor coupled with the at least one memory being configured to cause the user equipment to send the second token to the master node may comprise the at least one processor coupled with the at least one memory being further configured to cause the user equipment to send the second token to the master node via an access network. The at least one processor coupled with the at least one memory being configured to cause the user equipment to send the second token to the master node may comprise the at least one processor coupled with the at least one memory being further configured to cause the user equipment to send the second token to the master node via a User Plane Function, UPF.

[0167] The at least one processor coupled with the at least one memory may be further configured to cause the user equipment to: receive, from the master node, an authorization for integrating the computing resources of the user equipment into the distributed computing network.

[0168] The at least one processor coupled with the at least one memory being configured to cause the user equipment to receive, from the master node, the authorization for integrating the computing resources of the user equipment into the distributed computing network may comprise the at least one processor coupled with the at least one memory being further configured to cause the user equipment to receive, from the master node, the authorization for integrating the computing resources of the user equipment into the distributed computing network via an access network. The at least one processor coupled with the at least one memory being configured to cause the user equipment to receive, from the master node, the authorization for integrating the computing resources of the user equipment into the distributed computing network may comprise the at least one processor coupled with the at least one memory being further configured to cause the user equipment to receive, from the master node, the authorization for integrating the computing resources of the user equipment into the distributed computing network via a User Plane Function, UPF.

[0169] The at least one processor coupled with the at least one memory may be further configured to cause the user equipment to receive, from the master node, a management message with respect to one or more workloads on the user equipment. The management message may comprise an indication to install one or more workloads on the user equipment. The management message may comprise an indication to delete one or more workloads on the user equipment.

[0170] At least one of the one or more workloads may comprise a containerized application. At least one of the one or more workloads may comprise an application requiring low-latency data processing.

[0171] The at least one processor coupled with the at least one memory being configured to cause the user equipment to receive, from the master node, a management message with respect to one or more workloads on the user equipment may comprise the atleast one processor coupled with the at least one memory being configured to cause the user equipment to receive, from the master node, the management message via an access network. The at least one processor coupled with the at least one memory being configured to cause the user equipment to receive, from the master node, a management message with respect to one or more workloads on the user equipment may comprise the at least one processor coupled with the at least one memory being further configured to cause the user equipment to receive, from the master node, the management message via a User Plane Function, UPF.

[0172] There is provided a processor for wireless communication, comprising: at least one controller coupled with at least one memory and configured to cause the processor to: sending, to a first network entity in a mobile communication network, a first request message comprising an indication of a request for join data, wherein the join data comprises information for integrating computing resources of the user equipment into a distributed computing network; and receiving, from the first network entity, a first response message comprising the join data.

[0173] Such a processor tends to improve the efficiency and dynamic allocation of computational tasks in the distributed computing network. The improved efficiency of the distributed computing network tends to improve energy consumption and reduce operational costs of the distributed computing network. In addition, the processor tends to provide additional computing power to the distributed computing network which tends to enhance scalability and flexibility in managing network load and tends to improve resilience and redundancy in the distributed computing network.

[0174] There is provided a method performed by a user equipment, the method comprising: sending, to a first network entity in a mobile communication network, a first request message comprising an indication of a request for join data, wherein the join data comprises information for integrating computing resources of the user equipment into a distributed computing network; and receiving, from the first network entity, a first response message comprising the join data.

[0175] Such a method tends to improve the efficiency and dynamic allocation of computational tasks in the distributed computing network. The improved efficiency of thedistributed computing network tends to improve energy consumption and reduce operational costs of the distributed computing network. In addition, the method tends to provide additional computing power to the distributed computing network which tends to enhance scalability and flexibility in managing network load and tends to improve resilience and redundancy in the distributed computing network.

[0176] The first network entity may comprise a session management function, SMF. The first request message may be a packet data unit, PDU, session establishment request message. The first response message may be a packet data unit, PDU, session establishment accept message. The first network entity may comprise an application function. The first request message may be an application-layer request message. The application-layer request message may be sent over an established packet data unit, PDU, session. The first response message may be an application-layer response message.

[0177] The method may further comprise using the join data to integrate the user equipment into the distributed computing network as a worker node. The join data may comprise one or more of: a contact address of a master node of the distributed computing network; a first token for verifying the master node; and / or a second token for authorizing the user equipment as a worker node.

[0178] The method may further comprise establishing a secure connection with the master node using the contact address of the master node of the distributed computing network. The method may further comprise sending the second token to the master node over the established secure connection. The method may further comprise receiving, from the master node, an authorization for integrating the computing resources of the user equipment into the distributed computing network.

[0179] There is provided a first network entity 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 first network entity to: receive, from the user equipment, a first request message comprising an indication of a request for join data, wherein the join data comprises information for integrating computing resources of the user equipment into a distributed computing network; and sending, to the user equipment, a first response message comprising the join data.

[0180] Such a first network entity tends to improve the efficiency and dynamic allocation of computational tasks in the distributed computing network. The improved efficiency of the distributed computing network tends to improve energy consumption and reduce operational costs of the distributed computing network. In addition, the first network entity tends to provide additional computing power to the distributed computing network which tends to enhance scalability and flexibility in managing network load and tends to improve resilience and redundancy in the distributed computing network.

[0181] The first network entity may be a Session Management Function, SMF. The first network entity may be an Application Function, AF. The first request message may be a packet data unit, PDU, session establishment request message. The first response message may be a packet data unit, PDU, session establishment accept message.

[0182] The first network entity may comprise an application function. The first request message may be an application-layer request message. The application-layer request message may be sent over an established packet data unit, PDU, session. The first response message may be an application-layer response message.

[0183] The join data may comprise one or more of: a contact address of a master node of the distributed computing network; a first token for verifying the master node; and / or a second token for authorizing the user equipment as a worker node. The at least one processor coupled with the at least one memory may be further configured to cause the first network entity to establish a secure connection with the user equipment using the contact address of the master node of the distributed computing network. The at least one processor coupled with the at least one memory may be further configured to cause the first network entity to: send, to the user equipment, an authorization for integrating the computing resources of the user equipment into the distributed computing network.

[0184] The at least one processor coupled with the at least one memory may be further configured to cause the first network entity to: receive the second token to the master node over the established secure connection.

[0185] The at least one processor coupled with the at least one memory may be further configured to cause the first network entity to determine whether the computer resources ofthe user equipment is allowed to be integrated into the distributed computing network. The at least one processor coupled with the at least one memory being configured to cause the first network entity to determine whether the computer resources of the user equipment is allowed to be integrated into the distributed computing network may comprise the at least one processor coupled with the at least one memory being further configured to cause the first network entity to receive user equipment subscription data from a third network entity. The third network entity may comprise a Unified Data Management, UDM, function.

[0186] The at least one processor coupled with the at least one memory may be further configured to cause the first network entity to send, to a second network entity, a second request message comprising an indication of a request for join data. The at least one processor coupled with the at least one memory may be further configured to cause the first network entity to receive, from the second network entity, a second response message comprising the join data.

[0187] There provided a processor for wireless communication, comprising: at least one controller coupled with at least one memory and configured to cause the processor to: receive, from the user equipment, a first request message comprising an indication of a request for join data, wherein the join data comprises information for integrating computing resources of the user equipment into a distributed computing network; and send, to the user equipment, a first response message comprising the join data.

[0188] Such a processor tends to improve the efficiency and dynamic allocation of computational tasks in the distributed computing network. The improved efficiency of the distributed computing network tends to improve energy consumption and reduce operational costs of the distributed computing network. In addition, the processor tends to provide additional computing power to the distributed computing network which tends to enhance scalability and flexibility in managing network load and tends to improve resilience and redundancy in the distributed computing network.

[0189] There is provided a method performed by a first network entity in a mobile communication network, the method comprising: receiving, from the user equipment, a first request message comprising an indication of a request for join data, wherein the join data comprises information for integrating computing resources of the user equipment into adistributed computing network; and sending, to the user equipment, a first response message comprising the join data.

[0190] Such a method tends to improve the efficiency and dynamic allocation of computational tasks in the distributed computing network. The improved efficiency of the distributed computing network tends to improve energy consumption and reduce operational costs of the distributed computing network. In addition, the method tends to provide additional computing power to the distributed computing network which tends to enhance scalability and flexibility in managing network load and tends to improve resilience and redundancy in the distributed computing network.

[0191] The first network entity may be a Session Management Function, SMF. The first network entity may be an Application Function, AF.

[0192] The method may further comprise determining whether the computer resources of the user equipment is allowed to be integrated into the distributed computing network. Determining whether the computer resources of the user equipment is allowed to be integrated into the distributed computing network may comprise receiving user equipment subscription data from a third network entity. The third network entity may comprise a Unified Data Management, UDM, function.

[0193] The method may further comprise sending, to a second network entity, a second request message comprising an indication of a request for join data. The method may further comprise receiving, from the second network entity, a second response message comprising the join data.

[0194] There is provided a second network entity 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 second network entity to: receive, from a first network entity, a second request message comprising an indication of a request for join data, wherein the join data comprises information for integrating computing resources of a user equipment into a distributed computing network; and send, to the first network entity, a second response message comprising the join data.

[0195] Such a second network entity tends to improve the efficiency and dynamic allocation of computational tasks in the distributed computing network. The improved efficiency of the distributed computing network tends to improve energy consumption and reduce operational costs of the distributed computing network. In addition, the second network entity tends to provide additional computing power to the distributed computing network which tends to enhance scalability and flexibility in managing network load and tends to improve resilience and redundancy in the distributed computing network.

[0196] The second network entity may be a Management and Orchestration System, MANO. The method may further comprise obtaining the join data. The method may further comprise generating the join data. The method may further comprise determining whether the computer resources of the user equipment is allowed to be integrated into the distributed computing network.

[0197] There provided a processor for wireless communication, comprising: at least one controller coupled with at least one memory and configured to cause the processor to: receive, from a first network entity, a second request message comprising an indication of a request for join data, wherein the join data comprises information for integrating computing resources of a user equipment into a distributed computing network; and send, to the first network entity, a second response message comprising the join data.

[0198] Such a processor tends to improve the efficiency and dynamic allocation of computational tasks in the distributed computing network. The improved efficiency of the distributed computing network tends to improve energy consumption and reduce operational costs of the distributed computing network. In addition, the processor tends to provide additional computing power to the distributed computing network which tends to enhance scalability and flexibility in managing network load and tends to improve resilience and redundancy in the distributed computing network.

[0199] There is provided a method performed by a second network entity, the method comprising: receiving, from a first network entity, a second request message comprising an indication of a request for join data, wherein the join data comprises information for integrating computing resources of a user equipment into a distributed computing network;and sending, to the first network entity, a second response message comprising the join data.

[0200] Such a method tends to improve the efficiency and dynamic allocation of computational tasks in the distributed computing network. The improved efficiency of the distributed computing network tends to improve energy consumption and reduce operational costs of the distributed computing network. In addition, the method tends to provide additional computing power to the distributed computing network which tends to enhance scalability and flexibility in managing network load and tends to improve resilience and redundancy in the distributed computing network.

[0201] The user equipment may be in the mobile communication network. The first network entity may be in the mobile communication network. The second network entity may be in the mobile communication network. The user equipment may be part of the mobile communication network. The first network entity may be part of the mobile communication network. The second network entity may be part of the mobile communication network.

[0202] Examples described herein generally relate to a method with an enhanced Protocol Data Unit (PDU) Session Establishment process within mobile networks. This tends to allow a UE to seamlessly join and function as part of a container orchestration and management system, akin to a worker node in a Kubernetes cluster.

[0203] The method tends to provide Dynamic Integration by enabling UEs to dynamically request and receive the necessary data for integration with the management system during the establishment of a data connection. This process tends to be fully automated and tends not to require manual intervention. The process tends to represent a significant departure from the current practices where such configurations are preprovisioned or manually set up by network administrators.

[0204] The method tends to provide Secure Provisioning of Join Data. The join data for the integration of the UE into the network is transmitted securely during the PDU session establishment. The method may leverage existing Non Access Stratum (NAS) security protocols which tends to ensure the confidentiality and integrity of the join data.

[0205] Th method tends to provide an Extension to the Extreme Edge. By enabling UEs, which reside at the extreme edge of the network, to operate as computational resources, the method tends to expand the reach of the network's computational framework. This extension tends to bring the processing power directly to the proximity of end-users and devices, enabling a new realm of ultra-low latency applications.

[0206] The method tends to provide Resource Optimization. Examples described herein tend to promote optimal use of computational resources by allowing the network to tap into the underutilized power of UEs. This approach tends to enhance network efficiency and tends to open up new opportunities for energy saving and cost reduction.

[0207] The method tends to provide Enhanced Edge Services. The method provides a way for deploying a variety of containerized applications directly onto the UEs. These could range from local content caches to Al-driven data analysis tools, which tends to significantly enhance the network's service capabilities at the edge.

[0208] The method tends to enable mobile networks to transition from a model that predominantly perceives UEs as terminal devices to a more versatile architecture where UEs become integral, active components of network computation and service delivery. The method tends to bring a transformative shift in how mobile networks are architected and how computational tasks are distributed and executed within them.

[0209] There is provided a method for integrating User Equipment (UE) as computational nodes in a mobile network, comprising: Initiating a Protocol Data Unit (PDU) Session Establishment between the UE and a mobile network; Transmitting a request from the UE to the network indicating the UE's willingness to join a container orchestration and management system; Receiving, at the UE, join data necessary for integration into the container orchestration and management system, where the join data includes the address of a master node, a Discovery Token CA Cert Hash, and a bootstrap token; Joining the UE to the container orchestration and management system as a computational node using the received join data.

[0210] The request from the UE to the network indicating the UE's willingness to join a container orchestration and management system may be a PDU Session Establishment Request message.

[0211] The join data may be transmitted to the UE with a PDU Session Establishment Access message.

[0212] The method may further comprise Authenticating the UE to the container orchestration and management system using the bootstrap token; and Configuring the UE as a worker node within the container orchestration and management system.

[0213] The container orchestration and management system may manage workloads on the UE and schedule tasks based on the computational resources available on the UE.

[0214] The workloads may include applications requiring low-latency data processing, thereby providing services at the network edge closer to end-users.

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

[0216] 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

CLAIMSWhat is claimed is:

1. A user equipment 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 user equipment to: send, to a first network entity in a mobile communication network, a first request message comprising an indication of a request for join data, wherein the join data comprises information for integrating computing resources of the user equipment into a distributed computing network; and receive, from the first network entity, a first response message comprising the join data.

2. The user equipment of claim 1, wherein the first network entity comprises a session management function, SMF.

3. The user equipment of any one of claims 1 to 2, wherein the first request message is a packet data unit, PDU, session establishment request message.

4. The user equipment of any one of claims 1 to 3, wherein the first response message is a packet data unit, PDU, session establishment accept message.

5. The user equipment of claim 1, wherein the first network entity comprises an application function.

6. The user equipment of claim 5, wherein the first request message is an applicationlayer request message and wherein the application-layer request message is sent over an established packet data unit, PDU, session.

7. The user equipment of any one of claims 5 to 6, wherein the first response message is an application-layer response message.

8. The user equipment of any one of claims 1 to 7, wherein the at least one processor coupled with the at least one memory is further configured to cause the user equipment to: use the join data to integrate the user equipment into the distributed computing network as a worker node.

9. The user equipment of any one of claims 1 to 8, wherein the join data comprises one or more of: a contact address of a master node of the distributed computing network; a first token for verifying the master node; and / or a second token for authorizing the user equipment as a worker node.

10. The user equipment of claim 9, wherein the at least one processor coupled with the at least one memory is further configured to cause the user equipment to: establish a secure connection with the master node using the contact address of the master node of the distributed computing network.

11. The user equipment of claim 10, wherein the at least one processor coupled with the at least one memory is further configured to cause the user equipment to: send the second token to the master node over the established secure connection.

12. The user equipment of claim 11, wherein the at least one processor coupled with the at least one memory is further configured to cause the user equipment to: receive, from the master node, an authorization for integrating the computing resources of the user equipment into the distributed computing network.

13. A processor for wireless communication, comprising: at least one controller coupled with at least one memory and configured to cause the processor to: sending, to a first network entity in a mobile communication network, a first request message comprising an indication of a request for join data, wherein the join datacomprises information for integrating computing resources of the user equipment into a distributed computing network; and receiving, from the first network entity, a first response message comprising the join data.

14. A method performed by a user equipment, the method comprising: sending, to a first network entity in a mobile communication network, a first request message comprising an indication of a request for join data, wherein the join data comprises information for integrating computing resources of the user equipment into a distributed computing network; and receiving, from the first network entity, a first response message comprising the join data.

15. A first network entity 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 first network entity to: receive, from the user equipment, a first request message comprising an indication of a request for join data, wherein the join data comprises information for integrating computing resources of the user equipment into a distributed computing network; and sending, to the user equipment, a first response message comprising the join data.

Images