Far-edge computing in wireless communication system
The framework addresses the challenges of integrating UE as compute nodes in far-edge computing by enabling secure on-demand cluster joining and workload deployment, enhancing resource utilization and scalability in edge computing systems.
Patent Information
- Application Number
- PCT/EP2025/065977
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-09
- Filing Date
- 2025-06-09
- Publication Date
- 2026-11-12
AI Technical Summary
Existing wireless communication systems face challenges in seamlessly integrating user equipment (UE) as compute nodes for far-edge computing due to issues with dynamic availability, security, and orchestration, leading to underutilization of UE processing and memory resources.
A framework is provided that enables UE to securely join a far-edge compute cluster on-demand, allowing workload deployment and execution, leveraging network coordination for dynamic and secure participation in edge computing tasks, turning UE into an extension of the edge cloud for low-latency and scalable services.
The framework enhances resource utilization and scalability by enabling UE to dynamically participate in edge computing, providing low-latency and ultra-low latency services through secure integration into the edge cloud infrastructure.
Smart Images

Figure EP2025065977_12112026_PF_FP_ABST
Abstract
Description
FAR- EDGE COMPUTING IN WIRELESS COMMUNICATION SYSTEMTECHNICAL FIELD
[0001] The present disclosure relates to wireless communications, and more specifically to far-edge computing in wireless communication system.BACKGROUND
[0002] A wireless communication 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 communication 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 communication 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 Attorney Docket No. [PC934549WO]14737543-1used 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] In a first aspect, some implementations of the methods, systems, and apparatuses described herein may be performed or implemented by a user equipment (UE). The UE may include at least one memory and at least one processor coupled with the at least one memory. The at least one processor may be configured to cause (e.g., enable) the UE to perform various steps, operations, functions, etc.
[0005] Some implementations of the methods, devices, and apparatuses described herein in the first aspect may include obtaining information for joining a far-edge compute cluster, the information may comprise at least one of a token or an address of a managing entity of the far-edge compute cluster, transmitting a request to join the far-edge compute cluster as a far-edge compute node based at least in part on the token and / or the address, and receiving a response indicating that the request is accepted.
[0006] In some implementations of the methods, devices, and apparatuses described herein in the first aspect, the request to join the far-edge compute cluster may comprise the token and may be transmitted to the managing entity of the far-edge compute cluster based on the address. In some implementations of the methods, devices, and apparatuses described herein in the first aspect, the response may be received from the managing entity of the far-edge compute cluster.
[0007] In some implementations of the methods, devices, and apparatuses described herein in the first aspect, the token is a single-use token, a time-limited token, and / or a unique token for the UE.
[0008] In some implementations of the methods, devices, and apparatuses described herein in the first aspect, the information for joining the far-edge compute cluster may further comprise at least one of: address or identifier information of at least one workload repository associated with the far-edge compute cluster, or security credentials for accessing the at least one workload repository.Attorney Docket No. [PC934549WO]14737543-1
[0009] Some implementations of the methods, devices, and apparatuses described herein in the first aspect may include transmitting, to a network node, a request to provide information of one or more available far-edge compute clusters, and receiving, from the network node, a list comprising one or more far-edge compute cluster identities. The list may include an identity of the far-edge compute cluster.
[0010] Some implementations of the methods, devices, and apparatuses described herein in the first aspect may obtain the information for joining the far-edge compute cluster at least in part by transmitting, to a network node, a request for information for joining the far-edge compute cluster, the request for information may comprise at least one of: an identity of the UE, credential information of the UE, or an identity of the far-edge compute cluster, and receiving, from the network node, the information for joining the far-edge compute cluster. In some implementations of the methods, devices, and apparatuses described herein in the first aspect, the request for information may further comprise capability information of the UE, which may comprise at least one of: a processing capability of the UE, a memory capability of the UE, or a power status of the UE.
[0011] In some implementations of the methods, devices, and apparatuses described herein in the first aspect, the request to join the far-edge compute cluster may comprise capability information of the UE, which may comprise at least one of: a processing capability of the UE, a memory capability of the UE, or a power status of the UE.
[0012] Some implementations of the methods, devices, and apparatuses described herein in the first aspect may include receiving a request associated with initiation of workload deployment, the request may comprise an identifier of a workload to be deployed, obtaining the workload based at least in part on the identifier of the workload, deploying the workload, and outputting an indication to indicate success or completion of deployment of the workload. In some implementations of the methods, devices, and apparatuses described herein in the first aspect, the identifier of the workload to be deployed may include address or identifier of at least one workload repository associated with the workload to be deployed.
[0013] In some implementations of the methods, devices, and apparatuses described herein in the first aspect, the request associated with initiation of workload deployment may Attorney Docket No. [PC934549WO]14737543-1comprise at least one of: address or identifier information of at least one workload repository associated with the far-edge compute cluster, or security credentials for accessing the at least one workload repository.
[0014] Some implementations of the methods, devices, and apparatuses described herein in the first aspect may include executing the workload. In some implementations of the methods, devices, and apparatuses described herein in the first aspect, the workload, when executed, may be operable to access at least one hardware component of the UE. The at least one hardware components may comprise an imaging device, a sensor, or a communication device.
[0015] In some implementations of the methods, devices, and apparatuses described herein in the first aspect, the request associated with initiation of workload deployment may comprise configuration data associated with the workload. The configuration data may comprise environmental variable associated with the workload. For example, the configuration data may include an address of an application server for application layer communication with the workload.
[0016] Some implementations of the methods, devices, and apparatuses described herein in the first aspect may include establishing (optionally initiating) a connection with an application server, based at least in part on the configuration data, to enable application layer communication between the deployed workload and the application server.
[0017] In some implementations of the methods, devices, and apparatuses described herein in the first aspect, the UE may be configured to implement a far-edge computing enabler client, a far-edge computing client, or a combination thereof.
[0018] In a second aspect, some implementations of the methods, systems, and apparatuses described herein may be performed or implemented by a network node such as an edge network node. The network node may include at least one memory and at least one processor coupled with the at least one memory. The at least one processor may be configured to cause (e.g., enable) the network node to perform various steps, operations, functions, etc.Attorney Docket No. [PC934549WO]14737543-1
[0019] Some implementations of the methods, devices, and apparatuses described herein in the second aspect may include: receiving a request for information for joining a far-edge compute cluster, the request for information may comprise at least one of: an identity of a UE, credential information of the UE, or an identity of the far-edge compute cluster; generating and / or retrieving the information for joining the far-edge compute cluster, the information may comprise at least one of a token or an address of a managing entity of the far-edge compute cluster; and outputting the information for joining the far-edge compute cluster.
[0020] In some implementations of the methods, devices, and apparatuses described herein in the first aspect, the request for information may further comprise capability information of the UE which may comprise at least one of: a processing capability of the UE, a memory capability of the UE, or a power status of the UE.
[0021] In some implementations of the methods, devices, and apparatuses described herein in the first aspect, the information for joining the far-edge compute cluster may further comprise at least one of: address or identifier information of at least one workload repository associated with the far-edge compute cluster, or security credentials for accessing the at least one workload repository.
[0022] Some implementations of the methods, devices, and apparatuses described herein in the second aspect may include: receiving a request to provide information of one or more available far-edge compute clusters, and outputting a list comprising one or more far-edge compute cluster identities, including an identity of the far-edge compute cluster.
[0023] Some implementations of the methods, devices, and apparatuses described herein in the second aspect may include: receiving, from an application server, a request to deploy a workload in the far-edge compute cluster, the request may comprise an identifier of the workload and at least one of: an identifier associated with a UE of the far-edge compute cluster for deploying the workload or one or more criteria for selecting a UE from the far-edge compute cluster for deploying the workload; generating a workload deployment command based at least in part on the request to deploy the workload in the far-edge compute cluster, the workload deployment command may comprise the identifier of the workload and one of: the identifier associated with the UE or an identifier of a UE Attorney Docket No. [PC934549WO]14737543-1selected based on the one or more criteria, and outputting the workload deployment command to the managing entity of the far-edge compute cluster. In some implementations of the methods, devices, and apparatuses described herein in the second aspect, the one or more criteria for selecting the UE may include at least one of: a location criteria associated with UE location or a capability criteria associated with UE capability (e.g., processing capability, memory capability, power status, etc.).
[0024] In some implementations of the methods, devices, and apparatuses described herein in the second aspect, the request to deploy the workload in the far-edge compute cluster may comprise configuration data associated with the workload. In some implementations of the methods, devices, and apparatuses described herein in the second aspect, the workload deployment command may comprise the configuration data associated with the workload. The configuration data may comprise environmental variable associated with the workload. For example, the configuration data may include an address of an application server for application layer communication with the workload.
[0025] Some implementations of the methods, devices, and apparatuses described herein in the second aspect may include receiving, from the managing entity of the far-edge compute cluster, a response indicating success or completion of the workload deployment at the UE of the far-edge compute cluster.
[0026] Some implementations of the methods, devices, and apparatuses described herein in the second aspect may include: receiving, from an application server, a request to onboard a workload in at least one workload repository, the request may comprise metadata of the workload to be onboarded; facilitating onboarding of the workload in the at least one workload repository based at least in part on the metadata; and transmitting, to the application server, a response indicating success or completion of the workload onboarding, the response may comprise an identifier for the workload.
[0027] In some implementations of the methods, devices, and apparatuses described herein in the second aspect, the metadata of the workload to be onboarded may comprise at least one of: an identifier of the workload, a name of the workload, a description of the workload, resource requirement of the workload, an application artifact of the workload, or a reference to the application artifact of the workload.Attorney Docket No. [PC934549WO]14737543-1
[0028] In some implementations of the methods, devices, and apparatuses described herein in the second aspect, the network node may be configured to implement a far-edge computing enabler server.
[0029] In a third aspect, some implementations of the methods, systems, and apparatuses described herein may be performed or implemented by an application server, such as a vertical application layer (VAL) server. The application server may include at least one memory and at least one processor coupled with the at least one memory. The at least one processor may be configured to cause (e.g., enable) the application server to perform various steps, operations, functions, etc.
[0030] Some implementations of the methods, devices, and apparatuses described herein in the third aspect may include: outputting a request to deploy a workload in a far-edge compute cluster, the request may comprise an identifier of the workload and at least one of: an identifier associated with a UE of the far-edge compute cluster for deploying the workload or one or more criteria for selecting a UE from the far-edge compute cluster for deploying the workload; and receiving at least one of: a response indicating initiation of the workload deployment at a UE of the far-edge compute cluster, or a response indicating success or completion of the workload deployment at a UE of the far-edge compute cluster. In some implementations of the methods, devices, and apparatuses described herein in the third aspect, the one or more criteria for selecting the UE may include at least one of: a location criteria associated with UE location or a capability criteria associated with UE capability (e.g., processing capability, memory capability, power status, etc.).
[0031] In some implementations of the methods, devices, and apparatuses described herein in the third aspect, the request to deploy the workload in the far-edge compute cluster may comprise configuration data associated with the workload. The configuration data may comprise environmental variable associated with the workload. For example, the configuration data may include an address of an application server for application layer communication with the workload.
[0032] Some implementations of the methods, devices, and apparatuses described herein in the third aspect may include, prior to outputting the request to deploy the workload in the far-edge compute cluster: obtaining a list of devices, including one or more Attorney Docket No. [PC934549WO]14737543-1UE, that have joined the far-edge compute cluster; retrieving a list of available workloads; and selecting the workload from the list of available workloads for deployment in at least one UE in the list of devices.
[0033] Some implementations of the methods, devices, and apparatuses described herein in the third aspect may include: connecting (or establishing connection) with the UE to enable application layer communication between the application server and the deployed workload running on the UE, and receiving at least one application-layer report from the deployed workload running on the UE.
[0034] Some implementations of the methods, devices, and apparatuses described herein in the third aspect may include: transmitting, to a network node, a request to onboard the workload in a workload repository, the request may comprise metadata of the workload to be onboarded; and receiving, from the network node, a response indicating success or completion of the workload onboarding, the response comprises an identifier for the workload.
[0035] In some implementations of the methods, devices, and apparatuses described herein in the third aspect, the metadata of the workload to be onboarded may comprise at least one of: an identifier of the workload, a name of the workload, a description of the workload, resource requirement of the workload, an application artifact of the workload, or a reference to the application artifact of the workload.BRIEF DESCRIPTION OF THE DRAWINGS
[0036] Figure 1 illustrates an example of a wireless communication system for supporting far-edge computing in accordance with aspects of the present disclosure.
[0037] Figure 2 illustrates an example of a far-edge computing enablement framework in accordance with aspects of the present disclosure.
[0038] Figure 3 illustrates an example of a far-edge computing enablement framework in accordance with aspects of the present disclosure.
[0039] Figure 4 illustrates signaling flow of an example of an operation of a far-edge computing enablement framework in accordance with aspects of the present disclosure.Attorney Docket No. [PC934549WO]14737543-1
[0040] Figure 5 illustrates signaling flow of an example of an operation of a far-edge computing enablement framework in accordance with aspects of the present disclosure.
[0041] Figure 6 illustrates signaling flow of an example of an operation of a far-edge computing enablement framework in accordance with aspects of the present disclosure.
[0042] Figure 7 illustrates an example of a user equipment in accordance with aspects of the present disclosure.
[0043] Figure 8 illustrates an example of a processor in accordance with aspects of the present disclosure.
[0044] Figure 9 illustrates an example of a network equipment in accordance with aspects of the present disclosure.
[0045] Figure 10 illustrates a flowchart of a method performed by a user equipment in accordance with aspects of the present disclosure.
[0046] Figure 11 illustrates a flowchart of a method performed by a user equipment in accordance with aspects of the present disclosure.
[0047] Figure 12 illustrates a flowchart of a method performed by a network node in accordance with aspects of the present disclosure.
[0048] Figure 13 illustrates a flowchart of a method performed by a network node in accordance with aspects of the present disclosure.
[0049] Figure 14 illustrates a flowchart of a method performed by a network node in accordance with aspects of the present disclosure.
[0050] Figure 15 illustrates a flowchart of a method performed by an application server in accordance with aspects of the present disclosure.
[0051] Figure 16 illustrates a flowchart of a method performed by an application server in accordance with aspects of the present disclosure.DETAILED DESCRIPTIONAttorney Docket No. [PC934549WO]14737543-1
[0052] Edge computing is a distributed computing approach that can bring data processing and workload execution closer to an end user (e.g., where data is generated or consumed) to reduce latency and network load. For example, multi-access edge computing (MEC) may rely on servers located at the network edge (such as base stations or cloudlets) to host applications. Far-edge computing further extends the concept of edge computing by leveraging the computing resources at the far-edge, i.e., at the UE such as smartphones, loT devices, or vehicles, as part of the distributed computing infrastructure. These UE may possess processing and / or memory resources that are underutilized. Despite the capabilities of the UE, UE may not be easily and / or seamlessly integrated as compute nodes for far-edge computing due to challenges associated with dynamic availability, security, and orchestration.
[0053] Some aspects of the present disclosure provide a framework that may allow UE to join, or securely join, a far-edge compute cluster on-demand and execute workloads for network applications. In the framework, various operations may be coordinated by the network. The framework may effectively turn the UE into extension of the edge cloud, thereby enabling new services with low or ultra-low latency, improved resource utilization, and / or greater scalability (e.g., by exploiting a large number of UE). Some aspects of the present disclosure provide a far-edge computing enablement (FCE) framework that may allow UE to dynamically and / or securely participate in edge computing tasks under network control.
[0054] Some aspects of the present disclosure provide techniques for enabling a UE to join a far-edge compute cluster. Some aspects of the present disclosure provide techniques for enabling workload deployment and / or execution in a UE of a far-edge compute cluster. Some aspects of the present disclosure provide techniques for enabling workload onboarding for a far-edge compute cluster.
[0055] Aspects of the present disclosure are described in the context of a wireless communication system. Aspects of the present disclosure concern far-edge computing in wireless communication system.
[0056] Figure 1 illustrates an example of a wireless communication system 100 in accordance with aspects of the present disclosure. The wireless communication system 100 Attorney Docket No. [PC934549WO]14737543-1is configured to support far-edge computing. The wireless communication system 100 may include one or more NE 102, one or more UE 104, a core network (CN) 106, and an edge data network 108. The wireless communication system 100 may support various radio access technologies. In some implementations, the wireless communication system 100 may be a 4G network, such as a Long Term Evolution (LTE) network or an LTE-Advanced (LTE-A) network. In some other implementations, the wireless communication system 100 may be a NR network, such as a 5 G network, a 5 G- Advanced (5G-A) network, or a 5G ultrawideband (5G-UWB) network. In some other implementations, the wireless communication system 100 may be a beyond 5G network. In some other implementations, the wireless communication system 100 may be a combination of a 4G network and a 5G network, a combination of a 5G network and a beyond 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 communication system 100 may support radio access technologies beyond 5G, for example, 6G. Additionally, the wireless communication system 100 may support technologies such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA), etc.
[0057] The NE 102 may be dispersed throughout a geographic region to form the wireless communication 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. A NE 102 and a UE 104 may communicate via a communication link, which may be a wireless or wired connection. For example, a NE 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.
[0058] A NE 102 may provide a geographic coverage area for which the NE 102 may support services for one or more UE 104 within the geographic coverage area. For example, a NE 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or multiple radio access technologies. In some implementations, a NE 102 may be moveable, forAttorney Docket No. [PC934549WO]14737543-1example, 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.
[0059] The one or more UE 104 may be dispersed throughout a geographic region of the wireless communication 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.
[0060] A UE 104 may be able to support wireless communication directly with other UE 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.
[0061] A NE 102 may support communications with the CN 106, or with another NE 102, or both. For example, a 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 UE 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).Attorney Docket No. [PC934549WO]14737543-1
[0062] 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 UE 104 served by the one or more NE 102 associated with the CN 106. The CN 106 may support communication with the edge data network 108.
[0063] 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 UE 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 a 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).
[0064] In the wireless communication system 100, the NE 102 and the UE 104 may use resources of the wireless communication 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 NE 102 and the UE 104 may support different resource structures. For example, the NE 102 and the UE 104 may support different frame structures. In some implementations, such as in 4G, the NE 102 and the UE 104 may support a single frame structure. In some other implementations, such as in 5G and among other suitable radio access technologies, the NE 102 and the UE 104 may support various frame structures (i.e., multiple frame structures).Attorney Docket No. [PC934549WO]14737543-1The NE 102 and the UE 104 may support various frame structures based on one or more numerologies.
[0065] One or more numerologies may be supported in the wireless communication 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.
[0066] 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.
[0067] 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 communication 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 Attorney Docket No. [PC934549WO]14737543-1numerology. 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 12 symbols. 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.
[0068] In the wireless communication 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 communication 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 NE 102 and the UE 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the NE 102 and the UE 104, among other equipment or devices for cellular communications traffic (e.g., control information, data). In some implementations, FR2 may be used by the NE 102 and the UE 104, among other equipment or devices for short-range, high data rate capabilities.
[0069] 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.
[0070] Figure 2 illustrates an example of a far-edge computing enablement framework 200 in accordance with aspects of the present disclosure. For simplicity and ease of presentation, framework 200 includes only one UE 204. However, it should be noted thatAttorney Docket No. [PC934549WO]14737543-1the framework 200 can include more than one UE. For simplicity and ease of presentation, the framework 200 includes only one edge data network 208. However, it should be noted that the framework 200 can include more than one edge data network. The UE 204 and the edge data network 208 may be operably connected via a network such as a 5G network or a beyond- 5 G network.
[0071] As shown in Figure 2, the framework 200 may include various entities in the edge data network 208 and in the UE 204 and various interfaces arranged to facilitate communication among the entities. The edge data network 208 may include a Vertical Application Layer (VAL) server 208A, a far-edge computing enabler server (FCES) 208B, a far-edge computing manager 208C, and a workload registry 208D. The UE 204 may include a far-edge computing enabler client (FCEC) 204A and a far-edge computing client 204B (compute runtime on the UE 204). The FCES 208B and the far-edge computing manager 208C may communicate (e.g., receive signaling, transmit signaling) over a FEC-1 interface. The FCES 208B and the workload registry 208D may communicate (e.g., receive signaling, transmit signaling) over a FEC-2 interface. The FCES 208B and the VAL server 208A may communicate (e.g., receive signaling, transmit signaling) over a FEC-3 interface. The far-edge computing client 204B and the far-edge computing manager 208C may communicate (e.g., receive signaling, transmit signaling) over a FEC-4 interface. The far-edge computing client 204B and the workload registry 208D may communicate (e.g., receive signaling, transmit signaling) over a FEC-5 interface. The FCEC 204A and the far-edge computing client 204B may communicate (e.g., receive signaling, transmit signaling) over a FEC-6 interface. The FCES 208B and the FCEC 204A may communicate (e.g., receive signaling, transmit signaling) over a FEC-uu interface. The VAL server 208A and a dynamically deployed workload in the UE 204 may communicate (e.g., receive signaling, transmit signaling) over a FEC-U interface.
[0072] The VAL server 208A of the edge data network 208 may be an application server operated by a service provider. The VAL server 208A may utilize the far-edge computing capabilities offered by one or more UE (e.g., UE 204). The VAL server 208A may reside in the application layer (e.g., outside or on top of the mobile network) and may generate workload deployment requests. For example, the VAL server 208A may beAttorney Docket No. [PC934549WO]14737543-1operated by a service provider that needs or wants to offload tasks to edge devices (one or more UE). One example would be a gaming server that needs or wants to offload computations to player devices (devices of the players). In some implementations, the VAL server 208A may interact with the FCES 208B via interface FCE-3 to discover available far-edge UE, to request deployment of workloads on far-edge UE, and to communicate with the deployed workloads (application layer traffic).
[0073] The FCES 208B of the edge data network 208 may be a network-side component (e.g., network node) and may be operable as an orchestrator and broker for far-edge computing services. The FCES 208B may expose an API or interface to VAL servers (e.g., VAL server 208A) to receive requests for deploying and / or managing workloads on one or more far-edge UE (e.g., UE 204) and may coordinate with other network components, such as the far-edge computing manager 208C and the workload registry 208D, to fulfill the requests. The FCES 208B may handle control-plane logic such as authenticating and onboarding one or more UE into the far-edge computing system, distributing join information to one or more UE, and / or relaying deployment commands. The FCES 208B may effectively enable the far-edge computing service by linking an external application layer (e.g., VAL) with the internal edge infrastructure.
[0074] The far-edge computing manager 208C of the edge data network 208 may be operable to manage the pool of far-edge computing resources (e.g., one or more UE that has joined as far-edge compute nodes). The far-edge computing manager 208C may operate as a manager and / or orchestrator for the far-edge compute cluster. The far-edge computing manager 208C may maintain the state of which one or more UE is part of the cluster, capabilities of the one or more UE, and information of workloads and location of running of the workloads. The far-edge computing manager 208C may be responsible for accepting new compute nodes (e.g., UE) into the cluster and for initiating the deployment of workload onto the appropriate compute nodes. In some implementations, the far-edge computing manager 208C may be implemented using orchestration technologies (such as Docker Swarm manager or Kubernetes master for containers) or a custom management server. The far-edge computing manager 208C may interact with the FCES 208B for receiving high-level instructions (e.g., an instruction to deploy a particular workload on aAttorney Docket No. [PC934549WO]14737543-1particular UE (compute node)). The far-edge computing manager 208C may interact with the one or more UE (via FCEC 204A associated with each of the one or more UE) to carry out those instructions (e.g., e.g., an instruction to instruct a specific UE to download and run a workload).
[0075] The workload registry (workload repository) 208D of the edge data network 208 may operate as a repository or database for storing workload packages (e.g., application codes, container images, and / or other artifacts associated with the workloads) and their metadata. The workload registry 208D may be accessible to the network side and the one or more UE (e.g., UE 204) for retrieving workloads. In one example, if a new application or service is introduced by a VAL server (e.g., VAL server 208A), the workload (or a reference to the workload) may be onboarded into the workload registry 208D to enable deployment of the workload to one or more UE (e.g., UE 204) on demand. In some implementations, the workload registry 208D may include a container image registry arranged to store Docker and / or Open Container Initiative (OCI) container images. The workload registry 208D may ensure that one or more UE (e.g., UE 204) can download the exact version of the code that the VAL server (e.g., VAL server 208A) wants to run. The workload registry 208D may hold metadata of the workloads, such as required resources, versioning, and security signatures for one or more workloads.
[0076] The FCEC 204A of the UE 204 may be a client-side component that runs on the UE 204 and enables the UE 204 to interface with the far-edge computing framework such as the edge data network 208. The FCEC 204 A may be an agent or application on the UE 204 for communication with the FCES 208B of the edge data network 208. The FCEC 204A may coordinate local actions on the UE 204. In some implementations, the FCEC 204A may handle control signaling on behalf of the UE 204. For example, the FCEC 204A may discover and contact the FCES 208B of the edge data network 208 to initiate the participation of the UE 204. For example, the FCEC 204A may receive join instructions (e.g., instructions for joining a far-edge compute cluster, which may include cluster credentials, configuration) from the network. For example, the FCEC 204A may trigger the local environment associated with the UE 204 to join the cluster. In some implementations, the FCEC 204A may receive deployment commands (and optionally configuration data) forAttorney Docket No. [PC934549WO]14737543-1workloads and may orchestrate the local launch of the workload (i.e., launch in the UE 204). In some implementations, the FCEC 204A may operate as an ambassador for the UE 204 in the far-edge compute system, e.g., to ensure that the UE 204 follows the protocol to join and operate within the far-edge cloud securely. The FCEC 204A may run with appropriate privileges on the UE 204 to manage containers and / or other processes. The FCEC 204A may sandbox and / or control the deployed workload (and its operation), for providing security on the device (UE) side.
[0077] The far-edge computing client 204B of the UE 204 may correspond to a compute runtime on the UE 204, and may operate to execute the workloads. The far-edge computing client 204B may provide a runtime environment, such as a container engine, a virtual machine monitor, or a native execution sandbox. In some implementations, the far-edge computing client 204B may be a lightweight container runtime that can run application code isolated from the rest of the UE 204 and / or in the background. The FCEC 204A may instruct the far-edge computing client 204B to perform operations such as joining the far-edge compute cluster (e.g., connecting to the far-edge computing manager 208C using given or obtained credentials), starting workloads, or stopping workloads. In some implementations using Docker, the far-edge computing client 204B may include a Docker Engine or daemon running on the UE 204, which is capable of joining a Docker Swarm or pulling and running containers. The far-edge computing client 204B may communicate with the far-edge computing manager 208C to become part of the far-edge compute cluster. The far-edge computing client 204B may communicate with the workload registry 208D to fetch the actual workload content when needed. This may ensure the workload is executed in an isolated manner on the UE 204, for security and / or stability.
[0078] In the framework 200, the interactions among these entities in the edge data network 208 and in the UE 204 may occur over various defined interfaces FEC-1 to FEC-6, FEC-U, and FEC-uu. In some implementations, each of the interfaces may correspond to a link between associated components and may carry certain types of messages and / or traffic.
[0079] The FCE-1 interface may be arranged to interface between the FCES 208B and the far-edge computing manager 208C for operably connecting the FCES 208B and the far-edge computing manager 208C. The FCE-1 interface may support capabilities such asAttorney Docket No. [PC934549WO]14737543-1secure cluster coordination (e.g., delivering join authorization data from the FCES 208B to the far-edge computing manager 208C), workload deployment control (e.g., transmitting deployment requests for scheduling on one or more UE), etc. For example, if a UE (e.g., UE 204) wants to join the cluster, the FCES 208B may use the FCE-1 interface to ask the far-edge computing manager 208C to generate join credentials for the UE. For example, if a VAL server (e.g., VAL server 208A) requests a workload deployment, the FCES 208B may use the FCE-1 interface to instruct the far-edge computing manager 208C to deploy the workload to a specific UE or to select an appropriate UE.
[0080] The FCE-2 interface may be arranged to interface between the FCES 208B and the workload registry 208D for operably connecting the FCES 208B and the workload registry 208D. The FCE-2 interface may allow the FCES 208B (and thus the far-edge system) to access workload metadata and packages in the workload registry 208D. The FCE-2 interface may be used for workload discovery and / or workload onboarding. For instance, if a VAL server (e.g., VAL server 208A) introduces a new workload, the FCES 208B may communicate with the workload registry 208D over the FCE-2 interface to store the workload (onboarding) or to retrieve metadata (e.g., to check if a requested workload identifier (ID) exists and / or to obtain a download path or requirements associated with the workload). In some implementations, the FCE-2 interface may be used to fetch a workload package on behalf of a UE (e.g., UE 204) (although in some other implementations the UE may fetch the workload package directly, as described with reference to the FCE-5 interface below). The FCE-2 interface may support capabilities that may ensure the network side has knowledge of available workloads and their details. This may effectively allow the FCES 208B and / or the far-edge computing manager 208C to, e.g., discover workloads can be deployed and / or register new ones into the system.
[0081] The FCE-3 interface may be arranged to interface between the VAL server 208A and the FCES 208B for operably connecting the VAL server 208A and the FCES 208B. The FCE-3 interface may be an application-layer control interface (which may be realized as a service API) through which the VAL server 208A may interact with the far-edge enablement framework. Over the FCE-3 interface, the VAL server 208A may send requests such as far-edge workload onboarding requests (for registering a new workload orAttorney Docket No. [PC934549WO]14737543-1for updating an existing workload), far-edge deploy requests (for instantiating a workload on a far-edge UE), etc. Over the FCE-3 interface, the VAL server 208A may receive responses (e.g., confirmation that a UE has joined the cluster, confirmation that a deployment is successful, along with any identifiers or errors, etc.). The FCE-3 interface may be the service interface that exposes far-edge computing capabilities to external applications. It may be implemented as a secure API (e.g., REST or RPC) that can be called by the VAL server 208A. The FCE-3 interface may include security and authentication to ensure that only authorized application servers may request deployments. The FCE-3 interface may be where workload selection or discovery from the application perspective may occur (e.g., the VAL server 208A may enquire about far-edge resources or pre-existing workloads available, if such query is allowed by the system).
[0082] The FCE-4 interface may be arranged to interface between the far-edge computing manager 208C and the far-edge computing client 204B for operably connecting the far-edge computing manager 208C and the far-edge computing client 204B. The FCE-4 interface may represent a control channel that can be used by the far-edge computing manager (cluster manager) 208C to communicate with the runtime of the UE 204. The FCE-4 interface may carry messages to facilitate secure swarm join and / or workload deployment at the UE. For example, if a UE has the credentials, the operation for joining the cluster may involve the far-edge computing client 204B of the UE 204 establishing a connection with the far-edge computing manager 208C over the FCE-4 interface (e.g., using appropriate cluster protocol, such as a Docker swarm join protocol or a custom protocol). After the UE becomes or joins as part of the cluster, the FCE-4 interface may be used by the far-edge computing manager 208C to send deployment instructions to the UE 204 (e.g., an instruction to “deploy workload X with configuration Y” to the UE). The FCE-4 interface may be useful for delivering commands from the far-edge computing manager 208C, i.e. the orchestrator, to the UE 204, i.e., the node. The FCE-4 interface may be a secure connection (e.g., it may be mutually authenticated using the credentials given when the UE joins the cluster) to prevent unauthorized control. The FCE-4 interface may support capabilities that may enable the UE 204 to join the cluster (the FCE-4 interface may carry the join request / response) and may enable the transmission of deployment instructions to the UE 204 in real time.Attorney Docket No. [PC934549WO]14737543-1
[0083] The FCE-5 interface may be arranged to interface between the workload registry 208D and the far-edge computing client 204B for operably connecting the workload registry 208D and the far-edge computing client 204B. The FCE-5 interface may represent a channel through which the UE 204 may obtain the actual workload data (e.g., through which the UE 204 may download a container image or code package associated with a workload). In one example, when the far-edge computing client 204B is instructed to or otherwise wants to deploy a workload, the far-edge computing client 204B may use the FCE-5 interface to fetch the workload (and / or related data) from the workload registry 208D, e.g., if the workload is not cached locally in the UE 204. The FCE-5 interface may handle registry access from the UE side. In some implementations, the FCE-5 interface maybe, for example, an HTTP(S) connection to a container registry to download an image, or any appropriate data transfer protocol. The FCE-5 interface may ensure that the UE 204 has the necessary data (e.g., code) to run the workload. The FCE-4 interface may support capabilities for allowing the UE 204 to retrieve the workload artifact from the workload registry 208D on-demand. In some implementations, this may decouple code distribution from control signaling. As a result, for example, the far-edge computing manager 208C, i.e. the orchestrator, does not need to push large payloads through itself and instead, the far-edge computing manager 208C simple informs the UE the workload-related data to obtain and the location for obtaining such workload-related data. This arrangement may improve scalability and efficiency, e.g. because the workload registry 208D may be more suitable for or optimized for content distribution.
[0084] The FCE-6 interface may be arranged to interface between the FCEC 204A and the far-edge computing client 204B for operably connecting the FCEC 204A and the far-edge computing client 204B (i.e., between the control agent of the UE 204 and the local runtime of the UE 204). The FCE-6 interface may be an internal interface on the UE 204, which can be used for local coordination. The FCEC 204A may use the FCE-6 interface to command or configure the local computing client of the UE 204. In one example, when the UE 204 receives join parameters (e.g., parameters to join a far-edge compute cluster) from the FCEC 204A, the FCEC 204 A may instruct the far-edge computing client 204B (over the FCE-6 interface) to initiate a cluster join procedure (e.g., by invoking appropriate system or API calls on the container engine). In one example, when a deployment Attorney Docket No. [PC934549WO]14737543-1command arrives (e.g., via the FCEC 204A or provided directly to the computing client), the FCEC 204A may pass configuration data and / or environment setup instructions via the FCE-6 interface. The FCE-6 interface may relate to how the FCEC 204A, i.e., the agent program, controls the execution environment on the UE 204. The FCE-6 interface may be implemented via local inter-process communication, APIs, and / or command-line calls. The secure operation of the UE 204 may rely on at least the FCE-6 interface. For example, the FCEC 204A may enforce policies associated with what far-edge computing client 204B may run (e.g., for ensuring only signed containers are run, for limiting resource usage, etc.). The FCE-6 interface may enable the automation of UE-side actions (e.g., cluster joining, hosting workloads) under the guidance of the FCEC 204A.
[0085] The FCE-U interface may be arranged to interface between the VAL server 208A and the dynamically deployed workload in the UE 204, for operably connecting the VAL server 208A and the dynamically deployed workload in the UE 204. The FCE-U interface may support application-layer user traffic between the VAL server 208A and the dynamically deployed workload in the UE 204. In some implementations, after a workload is successfully running on the UE 204, the VAL server 208A may needs to communicate with the workload (e.g., to send task to the workload, to receive results from the workload, to allow the workload to access backend service, etc.). The FCE-U interface may provide a communication path for these communications. In some implementations, the FCE-U interface may be an IP connection established over the network (e.g., 5G or beyond 5G) between the VAL server 208A and the workload in the UE 204 (same as or similar to client-server communication). The FCE-U interface is labeled in the framework 200 to emphasize that the framework 200 may support direct data exchange between the VAL server 208A and the workload in the UE 204 (e.g., the far-edge-hosted application). The FCE-U interface may include, e.g., a TCP / IP socket or a HTTP connection from the VAL server 208A to the IP address or port of the application (or more generally workload) in the UE 204. As the UE 204 may be part of a mobile network, the traffic may go through the normal user plane of the network (in some implementations, with edge routing, if the VAL server is within the network of an operator, or through the internet, if the VAL server is external to the network of an operator). The FCE-U interface may support security (e.g., encryption, authentication) at the application layer (e.g., TLS) as needed. Traffic in the Attorney Docket No. [PC934549WO]14737543-1FCE-U interface may only flow after the workload is deployed and running in the UE 204, and the traffic may the distributed application (or more generally workload) to operate (e.g., a micro-service deployed on the UE 204 communicating with a central server).
[0086] The FCE-uu interface may be arranged to interface between the FCEC 204 A and the FCES 208B, for operably connecting the FCEC 204A and the FCES 208B. The FCE-uu interface may denote the use of an underlying radio interface (e.g., 5G or beyond 5G radio interface) for far-edge communications. For the FCE-uu interface, the communications between the UE 204 and the network 208 (e.g., control-plane messages such as join requests or user-plane data such as workload traffic) may be carried over the radio network (e.g., cellular network). In some implementations, interactions such as FCEC 204A contacting the FCES 208B, the UE 204 fetching a workload from the workload registry 208D, or the VAL server 208A communicating with the workload in the UE 204, may traverse the wireless link of the radio network. The FCE-uu interface may indicate that the far-edge framework is designed to operate over the mobile network connectivity, leveraging the reliability and security features of the radio network (e.g., 5G or beyond 5G). In one example, the join procedure that enables the UE 204 to join a cluster may use a secure connection over the data bearer of the UE 204, and the deployment traffic may be prioritized by network QoS. The use of FCE-uu interface may account for optimizations and / or specific behaviors on the radio link for far-edge computing traffic (e.g., dedicated bearers or edge-optimized routing). The FCE-uu interface indicates that, from the perspective of the UE 204, various far-edge computing signaling and data may go through the cellular network.
[0087] The framework 200 illustrated in Figure 2 provides an overview of how one or more UE (e.g., UE 204), the mobile network, and the application servers may interact in some implementations. Generally, in the framework 200, the UE 204 may run or operate the FCEC 204A and a far-edge computing client 204B, and may host the dynamically deployed workload when one is assigned. Generally, in the framework 200, the network (e.g., 5G or beyond 5F) may enable connection between the one or more UE (e.g., UE 204) and one or more edge data network (e.g., edge data network 208). Generally, in the framework 200, the edge data network 208 may include the FCES 208B, the far-edgeAttorney Docket No. [PC934549WO]14737543-1computing manager 208C, the workload registry 208D, and the VAL server 208A (which may be the source and / or destination of application traffic). Generally, in the framework 200, the various entities in the edge data network 208 and in the UE 204 may be operably connected via interfaces FEC-1 to FEC-6, FEC-U, and FEC-uu.
[0088] It should be noted that the framework 200 described herein describes a possible implementation, and that the framework 200 may be altered or otherwise modified and that other implementations are possible. For example, the edge data network 208 may include additional components or modules not specifically illustrated and described with reference to framework 200. For example, the UE 204 may include additional components or modules not specifically illustrated and described with reference to framework 200. For example, one or more alternative interfaces or one or more additional interfaces may be present.
[0089] Figure 3 illustrates an example of a far-edge computing enablement framework 300 in accordance with aspects of the present disclosure. The framework 300 can be considered as an implementation or prototype of the framework 200. In this example, standard container orchestration technology is utilized to implement the framework. As shown in Figure 3 the framework 300 is implemented using Docker Swarm as the underlying mechanism.
[0090] As shown in Figure 3, the framework 300 may include various entities in the edge data network 308 and in the UE 304 and various interfaces arranged to facilitate communication among the entities. The edge data network 308 may include a VAL server 308A, a FCES 308B, a far-edge computing manager implemented using a Docker Swarm manager 308C, and a workload registry implemented using a container registry 308D. The function of the edge data network 308 and its entities may be similar to or the same as the edge data network 208. The UE 304 may include a FCEC 304 A and a far-edge computing client implemented using a Docker Swarm client or agent 304B. The function of the UE 304 and its entities may be similar to or the same as the UE 204. The entities of the UE 304 and the entities of the edge data network 308 may be operably connected via interfaces FEC-1 to FEC-6, FEC-U, and FEC-uu, which are similar to or the same as those in the framework 200.Attorney Docket No. [PC934549WO]14737543-1
[0091] In the framework 300, the Docker Swarm manager (node) 308C implements a far-edge computing manager (which may correspond to the far-edge computing manager 208C). The Docker Swarm manager 308C may be run in the edge data network (e.g., on an edge cloud server). Docker Swarm may provide a built-in mechanism for worker nodes (e.g., UE) to join a far-edge compute cluster using join tokens and for the manager to deploy containerized services to the worker nodes.
[0092] In the framework 300, the Docker Swarm client or agent 304B (which may essentially be the Docker Engine running on the UE 304, configured as a swarm mode worker) implements a far-edge computing client (which may correspond to the far-edge computing client 204B. The Docker Swarm client or agent 304B, once provided with the address of the Docker Swarm manager (node) 308C and a join token, may be capable of joining the swarm cluster and may be capable of accepting tasks (e.g., containers) scheduled by the Docker Swarm manager (node) 308C.
[0093] In the framework 300, the container registry 308D implements the workload registry (which may correspond to the workload registry 208D). The container registry 308D may be, e.g., a Docker Hub, an on-premises Docker registry, or any OCI-compliant registry. Container images for workloads may be stored in the container registry 308D. In some implementations, onboarding a workload may involve pushing a Docker image to the container registry 308D. When deploying the workload, the Docker engine of the UE 304 may pull the required image from the container registry 308D.
[0094] In the framework 300, the FCE-4 interface may be the Docker Swarm protocol that can be used by the Docker Swarm manager (node) 308C (manager) and the Docker Swarm client or agent 304B to maintain cluster state and to send tasks.
[0095] In the framework 300, the FCE-5 interface may enable standard container image pull (e.g., an HTTPS fetch from the container registry 308D by the Docker Swarm client or agent 304B on the UE 304).
[0096] In the framework 300, the FCE-6 interface may be implemented by the FCEC 304A invoking Docker Engine APIs or commands on the UE 304, e.g., using a DockerAttorney Docket No. [PC934549WO]14737543-1command-line interface (CLI) or a remote API call to join the swarm (e.g., Docker swarm join token [token]).
[0097] In some implementations, the join credentials may include the Swarm join token and the network address of the Docker Swarm manager (node) 308C (manager). These may be provided by the FCES 308B to the FCEC 304A (e.g., via the FCE-3 and FCE-uu interfaces) and then used locally (via the FCE-6 interface) to have the Docker client join the swarm (via the FCE-4 interface).
[0098] In some implementations, once the UE 304 is or after the UE 304 becomes part of the Docker Swarm, the deployment of the workload may include the Docker Swarm Manager issue a service or task to the UE 304. The Docker engine of the UE 304 may (e.g., automatically) pull the required container image from the container registry 308D (if the container image is not already cached at the UE 304) and may start the container.Throughout, the FCEC 304A may monitor and report status. For example, the FCEC 304A may inform the FCES 308B when the container (workload) is operational and running. The VAL server 308A may then communicate with the containerized application (i.e., the workload) in the UE 304, e.g., via a REST API, over data connection that may correspond to the FCE-U interface).
[0099] The framework 300 demonstrates that the framework 200 can be implemented or built on suitable technologies, which may be advantageous for practicality and interoperability.
[0100] It should be noted that the framework 300 described herein describes a possible implementation, and that the framework 300 may be altered or otherwise modified and that other implementations are possible. For example, the edge data network 308 may include additional components or modules not specifically illustrated and described with reference to framework 300. For example, the UE 304 may include additional components or modules not specifically illustrated and described with reference to framework 300. For example, one or more alternative interfaces or one or more additional interfaces may be present. For example, the implementation of the framework 200 or 300 may not be limited to Docker Swarm. For example, other orchestration framework (e.g., Kubernetes, Mesos, custom solutions) or even non-container based approaches (e.g., running binary Attorney Docket No. [PC934549WO]14737543-1executables, server-less function containers, etc.) could be used to implement the framework 200 or 300. The framework 200, 300 relates to the orchestrated involvement of one or more UE as execution node with a network-mediated control plane, and is not limited in its implementation to specific brand or type of orchestration tool.
[0101] Figures 4 to 6 illustrate examples of operations of a far-edge computing enablement framework in accordance with aspects of the present disclosure. These example operations relate to a process of a UE joining a far-edge computing infrastructure and subsequently having a workload deployed and run on the UE. Specifically, the example operation 400 in Figure 4 relates to operation for enabling a UE to join a far-edge compute cluster, the example operation 500 in Figure 5 relates to operations for enabling workload onboarding for a far-edge compute cluster, and the example operation 600 in Figure 6 relates to operations for enabling workload deployment and / or execution in a UE of a far-edge compute cluster. For simplicity and ease of presentation, the operations 400, 500, 600 are described with reference to the framework 200, 300. In other words, in some implementations, the various entities of the UE and the edge data network illustrated in Figures 4 to 6 may correspond to the corresponding entities of the UE and the edge data network illustrated in Figures 2 and 3.
[0102] Turning now to the operation 400 in Figure 4. The operation 400 may include, in 402, the UE, in particular the FCEC of the UE, discovering the FCES in the edge data network. In some implementations, before any messaging can occur, the FCEC of the UE may need to know how to contact the FCES in the edge data network. In 402, the UE may discover or otherwise obtain the address (e.g., URL or IP and port) of the FCES. This may be accomplished, for example, via a 5G or beyond 5G core network function (e.g., the network may provide the UE with service endpoints), a domain name system (DNS) lookup, a configuration file, a broadcast, or a known and / or fixed address (if the operator has one). The UE may learn or determine where the join request (for joining the far-edge compute cluster as a far-edge compute node) should be sent.
[0103] The operation 400 may include, in 404, the UE, in particular the FCEC of the UE, transmitting a request for information for joining the far-edge compute cluster to the FCES of the edge data network. Stated another way, the operation 400 may include, in 404,Attorney Docket No. [PC934549WO]14737543-1the FCES of the edge data network receiving a request for information for joining the far-edge compute cluster from the UE, in particular the FCEC of the UE. The request may include one or more of: an identity of the UE, credential information of the UE, an identity of the far-edge compute cluster (if the UE already has obtained it), or capability information of the UE (e.g., processing capability of the UE, memory capability of the UE, or a power status of the UE). In some implementations, 404 may be considered as a join information request operation. In some implementations, in 404, the FCEC of the UE may initiate the onboarding by transmitting a far-edge join information request message to the FCES of the edge data network (e.g., over the FCE-uu interface and then the FCE-3 interface on the network side). The message may indicate that the UE is interested in joining the far-edge computing infrastructure. The message may include identity and credentials of the UE, which may be used for authenticating the eligibility of the UE. Optionally, the message may further include capability information of the UE (e.g., information on resources that the UE can offer, e.g., processing capability (e.g., CPU), memory capability (e.g., memory), power (e.g., battery) status, etc.). The request in 404 is used for requesting the FCES for information (e.g., parameters, authorization, etc.) necessary to join the far-edge computing infrastructure as a far-edge compute node.
[0104] The operation 400 may include, in 406, the FCES of the edge data network generating and / or retrieving the information for joining the far-edge compute cluster from the far-edge computing manager of the edge data network. In some implementations, 406 may be considered as a join information (e.g., parameters) retrieval operation. In some implementations, the FCES, upon receiving the join request, processes the join request. In some implementations, the FCES may communicate with the far-edge computing manager to obtain information for joining the far-edge compute cluster (e.g., join parameters) for the UE from which the request is received. The join parameters may include a token, a cluster node identifier, security credentials (certificates or keys), configuration associated with the address / URL for the cluster manager, etc. The token may be single-use, time-limited, and / or unique for the UE. In some implementations, in 406, the FCES may communicate with the far-edge computing manager (e.g., via the FCE-1 interface) to obtain and / or create the necessary join information. The far-edge computing manager may generate a fresh join token or prepare its system to expect a new node. In some implementations, in 406, the Attorney Docket No. [PC934549WO]14737543-1FCES may involve (e.g., communicate with) other entities, such as an authentication server, if needed to verify the UE’s authenticity or subscription for the service. In these implementations, if the authenticity or subscription is verified, the far-edge computing manager may provide the necessary join data to the FCES.
[0105] The operation 400 may include, in 408, the FCES of the edge data network transmitting information for joining a far-edge compute cluster to the UE, in particular the FCEC of the UE. Stated another way, the operation 400 may include, in 408, the UE, in particular the FCEC of the UE, obtaining the information for joining a far-edge compute cluster. The information may include the token and an address of the far-edge computing manager. In some implementations, 408 may be considered as a join information response operation. In some implementations, the FCES may transmit a far-edge join information response back to the FCEC of the UE. The response may include the join parameters needed by the UE to join the far-edge compute cluster. For example, in some implementations using Docker (e.g., framework 300), the response may include the swarm join token and the IP address (or hostname) of the Docker swarm manager. In some implementations, the response may include the address (e.g., URL) of the workload registry and security credentials (if required) for pulling images from the workload registry. The response may provide the FCEC, or more generally the UE, with information (e.g., address, token, etc.) required for proceeding with cluster joining.
[0106] In some implementations, the exchange or communication in 404 to 408 may be secured. For example, the join token may be protected in transit (e.g., encrypted) and / or may be specific to or bound to a specific UE (hence not usable by other UE), to ensure that only authorized UE can join.
[0107] The operation 400 may include, in 410, the FCEC of the UE transmitting a command to joining a far-edge compute cluster to the far-edge computing client of the UE. Stated another way, the operation 400 may include, in 418. the far-edge computing client of the UE receiving a command to joining a far-edge compute cluster from the FCEC of the UE. In some implementations, 408 may be considered as a far-edge join command operation. In some implementations, the FCEC of the UE, upon receiving the join information from the FCES of the edge data network, may issue a far-edge join commandAttorney Docket No. [PC934549WO]14737543-1to the far-edge computing client internally in the UE over the FCE-6 interface. This may be considered as the FCEC informing or requesting the local runtime of the UE to join the cluster using the obtained join information. For example, the FCEC of the UE may invoke a command to the local Docker engine. This might entail configuring the Docker client with the address of the far-edge computing manager and the join token. The FCEC may set up necessary local environment (e.g., opening any needed ports, ensuring the container runtime is running, etc.) prior to issuing the far-edge join command.
[0108] The operation 400 may include, in 412, the UE, in particular the far-edge computing client of the UE, transmitting a request to join the far-edge compute cluster as a far-edge compute node to the far-edge computing manager based at least in part on the token and / or the address of the far-edge computing manager. Stated another way, the operation 400 may include, in 412, the far-edge computing manager of the edge data network receiving a request to join the far-edge compute cluster as a far-edge compute node from the UE, in particular the far-edge computing client of the UE. In some implementations, 412 may be considered as providing the UE join request to the far-edge computing manager. In some implementations, the far-edge computing client of the UE (the runtime of the UE), following the command in 410, may initiate the cluster joining process by sending a far-edge join request to the far-edge computing manager. The request may be transmitted over the FCE-4 interface (e.g., via the data connection of the UE). In 412, the UE may present the credentials (e.g., token) received to the far-edge computing manager and may attempt to register itself as a new node (far-edge compute node). The far-edge computing manager may validate the request (e.g., check the token, check with FCES to determine whether the UE is allowed, etc.). If the request is successfully validated, the far-edge computing manager may integrate the UE into the cluster (i.e., the UE is acknowledged or registered as a compute node within the far-edge system).
[0109] The operation 400 may include, in 414, the UE, in particular the far-edge computing client of the UE, receiving a response indicating that the request (for the UE to join the far-edge compute cluster as a far-edge compute node) is accepted from the far-edge computing manager of the edge data network. Stated another way, the operation 400 may include, in 414, the far-edge computing manager of the edge data network transmitting aAttorney Docket No. [PC934549WO]14737543-1response indicating that the request (for the UE to join the far-edge compute cluster as a far-edge compute node) is accepted to the UE, in particular the far-edge computing client of the UE. The operation 400 may include, in 416, the UE, in particular the far-edge computing client of the UE, providing the response indicating that the request (for the UE to join the far-edge compute cluster as a far-edge compute node) is accepted to the FCEC. Stated another way, the operation 400 may include, in 416, the FCEC receiving a response indicating that the request (for the UE to join the far-edge compute cluster as a far-edge compute node) is accepted from the far-edge computing client of the UE. In some implementations, 414 and 416 may be considered as join acceptance and acknowledge operation. In some implementations, in 414, the far-edge computing manager of the edge data network may transmit a far-edge join accept message back to the UE, in particular the far-edge computing client of the UE, to confirm that the UE has been admitted as a far-edge compute node of the far-edge compute cluster. In some implementations, in 416, the far-edge computing client may then notify the FCEC (or the FCEC may detect the successful joining). Accordingly, the UE becomes part of the far-edge compute cluster. In some implementations, the FCEC may inform the FCES that the UE has successfully joined the far-edge compute cluster. In some implementations, the far-edge computing manager may inform the FCES directly that the UE has successfully joined the far-edge compute cluster. In either case, the system may now be aware that the UE is available for hosting workloads. After 416, the join phase is complete. The UE may be idle in the cluster, awaiting workloads / tasks.
[0110] In some implementations, throughout the cluster join procedure of operation 400, security measures may be applied to ensure the process is robust. In some implementations, the join token may be single-use or time-limited. In some implementations, the communications may be encrypted. In some implementations, the UE may authenticate the network (FCES and far-edge computing manager) to ensure the UE is joining a legitimate cluster (e.g., using certificates). In some implementations, the network may ensure the UE is trusted (e.g., the UE may have a secure element or attestation mechanism to prove that the UE can run workloads safely). These details can be implemented as needed to meet security requirements, and the framework 200, 300 may include such authentication.Attorney Docket No. [PC934549WO]14737543-1
[0111] After a UE (or more than one UE) has joined the far-edge compute cluster, the system may be ready to deploy workloads on one or more of the UE as requested by one or more application servers. The deployment process may generally involve the VAL server requesting a service, the network orchestrating the placement of that service on a UE, and the UE fetching and running the workload.
[0112] It should be noted that the operation 400 described herein describes a possible implementation, and that the operation 400 may be rearranged or otherwise modified and that other implementations are possible.
[0113] Turning now to the operation 500 in Figure 5. The operation 500 may include, in 502, the VAL server of the edge data network transmitting a request to onboard a workload in at least one workload repository to the FCES. Stated another way, the operation 500 may include, in 502, the FCES receiving a request to onboard a workload in at least one workload repository from the VAL server of the edge data network. The request may include metadata of the workload to be onboarded, such as an identifier of the workload, a name of the workload, a description of the workload, resource requirement of the workload, an application artifact of the workload, or a reference to the application artifact of the workload, or any combinations thereof. In some implementations, 502 may be related to a workload onboarding request. In some implementations, before deploying a workload, the VAL server may ensure that the workload is known to the far-edge system. In some implementations, if the VAL server has a new workload that is not previously registered in the workload registry, the VAL server may first perform an onboarding. For example, the VAL server may transmit a far-edge workload onboarding request to the FCES (e.g., over the FCE-3 interface). The request may carry or include workload metadata, i.e., information about the new workload, such as an identifier or name, a description, resource requirements, or the actual code package or a reference to it. For example, the VAL server may inform the FCES that the VAL server has a container image with name X (or the image file) intended for deployment. The FCES may receive this request and may coordinate the onboarding.
[0114] The operation 500 may include, in 504, the FCES facilitating onboarding of the workload to the workload registry based at least in part on the metadata. In someAttorney Docket No. [PC934549WO]14737543-1implementations, 504 may relate to onboarding the workload to workload registry. In some implementations, the FCES (optionally in conjunction with the far-edge computing manager) may onboard the workload to the workload registry. The FCES may communicate with the workload registry (e.g., over the FCE-2 interface), to store the new workload. In some implementations, this may involve uploading a container image, or registering metadata and a pointer to the location or address that the actual binary can be retrieved. In some implementations, the VAL server may directly provide the code to the workload registry (e.g., push the container image to the workload registry), and the FCES may ensure that an entry is created. In some implementations, the far-edge computing manager may store some information associated with the workload (for scheduling purposes), but primarily the workload registry is updated so that any node (e.g., UE) that needs to obtain the workload may obtain it.
[0115] The operation 500 may include, in 506, the FCES transmitting a response indicating success or completion of the workload onboarding to the VAL server. Stated another way, the operation 500 may include, in 506, the VAL server receiving a response indicating success or completion of the workload onboarding from the FCES. The response may include an identifier created for the workload. In some implementations, 506 relates to workload onboarding response. In some implementations, after successful registration and onboarding, the FCES may transmit a far-edge workload onboarding response back to the VAL server to indicate or confirm that the workload is now available in the system. The response may include a unique workload ID (or handle) for the workload, which may be used by the VAL server in subsequent deployment requests. The workload ID may reference the newly onboarded application.
[0116] In some implementations, if the workload is already onboarded, operation 500 may be skipped. In some implementations, if the workload is already onboarded, operation 500 may result in a response indicating the workload is already present (or already onboarded) and providing the workload ID.
[0117] It should be noted that the operation 500 described herein describes a possible implementation, and that the operation 500 may be rearranged or otherwise modified and that other implementations are possible.Attorney Docket No. [PC934549WO]14737543-1
[0118] Turning now to the operation 600 in Figure 6. The operation 600 may include, in 602, the VAL server transmitting a request to deploy a workload in a far-edge compute cluster to the FCES. Stated another way, the operation 600 may include, in 602, the FCES receiving a request to deploy a workload in a far-edge compute cluster from the VAL server. The request may include an identifier of the workload and at least one of: an identifier associated with a UE of the far-edge compute cluster for deploying the workload or one or more criteria for selecting a UE from the far-edge compute cluster for deploying the workload. The one or more criteria for selecting the UE may include at least one of: a location criteria associated with UE location or a capability criteria associated with UE capability (e.g., processing capability, memory capability, power status, etc.). The request may also include configuration data associated with the workload. The configuration data may include environmental variable associated with the workload, such as address of an application server for application layer communication with the workload. In in some implementations, 602 relates to a far-edge deploy request. In some implementations, with the workload already onboarded, the VAL server may issue a far-edge deploy request to the FCES (e.g., via the FCE-3 interface). The request may indicate that the VAL server wants to instantiate the workload on the far-edge. The request may include the workload ID (which may be obtained from the onboarding or known from prior knowledge) and configuration data or parameters needed by the workload. It may include an indication of where or to whom the workload should be deployed. In some implementations, the VAL server may want the workload deployed on a specific UE (e.g., if the workload is userspecific or location-specific, and the VAL server knows the UE or the user (of the UE) that needs it). In that case, the request may include a target UE identifier (e.g., a device ID or subscription ID). In some implementations, the request may specify one or more criteria and the FCE system (e.g., FCES) may determine or select the appropriate UE. In some implementations, the one or more criteria may include at least one of: a location criteria associated with UE location (e.g., criteria to deploy a workload to any UE in a certain area) or a capability criteria associated with UE capability (e.g., criteria to deploy a workload to any UE with at least 4 CPU cores). In some implementations, the request may include a UE ID, e.g., if the VAL server has designated a particular UE for deployment of the workload. This may be because the UE has initiated certain action or operation, or the VAL serverAttorney Docket No. [PC934549WO]14737543-1knows that the UE is available (and suitable). The FCES may receive this deploy request and begin the orchestration of the deployment of the workload.
[0119] The operation 600 may include, in 604, the FCES generating a workload deployment command (a command to deploy workload at a far-edge UE) based at least in part on the request to deploy the workload in the far-edge compute cluster, and the FCES outputting the workload deployment command to the far-edge computing manager. Stated another way, the operation 600 may include, in 604, the far-edge computing manager receiving a workload deployment command from the FCES. The workload deployment command may include the identifier of the workload and one of: the identifier associated with the UE or an identifier of a UE selected based on the one or more criteria. The workload deployment command may also include configuration data associated with the workload. The configuration data may include environmental variable associated with the workload, such as address of an application server for application layer communication with the workload. In some implementations, 604 may relate to a far-edge deploy command, in some implementations, the FCES may translate the request received from the VAL server in 602 into a cluster-specific command to the far-edge computing manager. The FCES may transmit a far-edge deploy command to the far-edge computing manager (over the FCE-1 interface). The far-edge deploy command may include the workload ID, the configuration data, and the UE ID or the UE selection. The far-edge deploy command may instruct far-edge computing manager to deploy workload [ID] with a particular configuration on a specified UE. In some implementations, if the VAL server does not specify a UE for deployment of the workload, the FCES and the far-edge computing manager together decide which UE should host the workload. The decision may be based on one or more of: availability of UE, capability of UE, network conditions, etc. In some implementations, the VAL server specifies a UE for deployment of the workload, i.e., the VAL server identifies the target UE. In 604, the far-edge computing manager, upon receiving the command, may prepare to deploy the workload on the UE. In some implementations, the far-edge computing manager may perform checks (e.g., to determine whether the UE has sufficient resource or capability, whether the UE is online and connected, etc.) to facilitate subsequent operations.Attorney Docket No. [PC934549WO]14737543-1
[0120] The operation 600 may include, in 606, the far-edge computing manager of the edge data network transmitting a request associated with initiation of workload deployment to the far-edge computing client of the UE. Stated another way, the operation 600 may include, in 606, the far-edge computing client of the UE receiving a request associated with initiation of workload deployment from the far-edge computing manager of the edge data network. The request may include an identifier of a workload to be deployed (which may include address or identifier of the one workload repository associated with the workload to be deployed). The request may optionally further include at least one of: address or identifier information of the workload repository associated with the far-edge compute cluster, security credentials for accessing the workload repository, or configuration data associated with the workload (which may include environmental variable associated with the workload, such as an address of an application server for application layer communication with the workload). In some implementations, 606 may relate to a far-edge initiate deployment request. In some implementations, the far-edge computing manager may communicate with the target UE to initiate the deployment of the workload. For example, the far-edge computing manager may transmit a far-edge initiate deployment request to the UE (e.g., addressed to the FCEC of the UE or directly to the far-edge computing client of the UE, over the FCE-4 interface). The message may include at least the workload ID. The request may also include at least one of: the configuration data or a generated deployment ID (which may be an identifier for a specific instance of the workload). The configuration data may include specific data such as environment variables for the application / workload, an indication of the data to process, or any input the application or workload may require at startup. On receiving the request, the UE (FCEC and / or far-edge computing client) may determine that it has to fetch and run the specified workload.
[0121] The operation 600 may include, in 608, the far-edge computing client of the UE obtaining (e.g., retrieving) the workload from the workload registry in the edge data network based at least in part on the identifier of the workload. In some implementations, 608 may relate to retrieving workload from registry. In some implementations, upon the initiation of workload deployment, the far-edge computing client of the UE may use the workload ID to obtain the workload (e.g., the workload artifact) from the workload registry, Attorney Docket No. [PC934549WO]14737543-1e.g., over the FCE-5 interface. In some implementations, if the workload ID corresponds to a container image, the UE may perform a container image pull from the workload registry (e.g., using the URL and credentials obtained previously, e.g., included in the join information or known via configuration). The workload registry, on receiving the request from the UE, may deliver or other provide the necessary files (e.g., layers of the container image, etc.) to the UE. This may ensure that the UE has the code it needs to run the workload. In some implementations, the retrieval may be performed efficiently. For example, if the workload image is large, it may take some time to retrieve. However, once retrieved (or downloaded to the UE), the workload image can be cached for future use. In some implementations, for improved security, the UE and the workload registry nay use secure communication channels, and the workload package may be verified (e.g., via cryptographic signature) to ensure that it is not tampered with.
[0122] The operation 600 may include, in 610, the far-edge computing client of the UE deploying the workload. In some implementations, 610 may be considered as instantiating and configuring the workload. In some implementations, the UE, after obtaining the workload package, may instantiate the workload using the configuration data. This means that the far-edge computing client (e.g., the container runtime) may launch the application (workload). In some implementations using Docker, the Docker engine may create and start a new container from the image, passing in the configuration (which could be commandline arguments, environment variables, etc.). The FCEC of the UE may assist by providing additional setup and / or by monitoring the process. The workload may run on the UE as an isolated process and / or in the background. During this step, the FCEC may apply suitable configurations to the network stack (e.g., ensuring the networking of the container is configured so that the VAL server can reach it, optionally by assigning it an IP or by setting up port forwarding if needed, although in some cases, the container may use the IP of the host UE with a specific port.
[0123] The operation 600 may include, in 612, the UE, in particular the far-edge computing client of the UE, outputting an indication to indicate success or completion of deployment of the workload, to the far-edge computing manager of the edge data network. Stated another way, the operation 600 may include, in 612, the far-edge computingAttorney Docket No. [PC934549WO]14737543-1manager of the edge data network receiving an indication that indicates success or completion of deployment of the workload from the UE, in particular the far-edge computing client of the UE. The operation 600 may include, in 614, the far-edge computing manager of the edge data network outputting an indication to indicate success or completion of deployment of the workload to the FCES of the edge data network. Stated another way, the operation 600 may include, in 614, the FCES of the edge data network receiving an indication that indicates success or completion of deployment of the workload from the far-edge computing manager of the edge data network. In some implementations, 612 and 614 may relate to deployment complete notification. In some implementations, after (e.g., once) the workload is deployed and running, the UE may signal back to the far-edge computing manager that the deployment is complete. In 612, the UE, may transmit a far-edge initiate deployment complete message (e.g., from the FCEC to the far-edge computing manager, over the FCE-4 interface) to indicate successful deployment and optionally to provide the deployment ID or runtime information (e.g., the IP / port of the service on the UE). In 614, the far-edge computing manager may then inform the FCES (e.g., via a message) that the deployment has been completed on the UE. The message may be sent from the far-edge computing manager to the FCES over the FCE-1 interface. The message may contain a confirmation that workload ID X is now deployed on UE Y, along with a deployment ID for reference.
[0124] The operation 600 may include, in 616, the FCES transmitting a response indicating success or completion of the workload deployment at the UE to the VAL server. Stated another way, the operation 600 may include, in 616, the VAL server receiving a response indicating success or completion of the workload deployment at the UE from the FCES. In some implementations, 616 may relate to far-edge deploy response. In some implementations, the FCES may transmit a response back to the originating VAL server to confirm that the deployment request has been fulfilled. In some implementations, the far-edge deploy response may, via the FCE-3 interface, carry the status (success or failure) of the deployment and the deployment ID (and optionally a network address to contact the new instance). If the workload deployment is successful, the response indicates to the VAL server that the workload is now running on the UE. If any failure occurs (e.g., if the UEAttorney Docket No. [PC934549WO]14737543-1goes offline, the UE has or will have insufficient resources, etc.), an error status (optionally with reason) may be returned.
[0125] The operation 600 may include, in 618, the workload running in the UE establishing (e.g., initiating) a connection with the VAL server, based at least in part on the configuration data (which may include the address of the VAL server), to enable application layer communication between the deployed workload in the UE and the VAL server. Stated another way, the operation 600 may include, in 618, the VAL server connecting (or establishing connection) with the UE to enable application layer communication between the VAL server and the deployed workload running on the UE. In some implementations, 618 relates to application layer (app-layer) communication. In some implementations, with the workload running in the UE and with the VAL server notified, the VAL server and the newly deployed application (workload) may communicate at the application layer. This may correspond to the FCE-U interface. For instance, if the workload is a microservice offloaded by the VAL server, the VAL server may start transmitting requests to the workload (e.g., via HTTP or another protocol) and the workload may then process the requests and return results. This traffic may flow over the network (e.g., 5G or beyond 5G network) user plane between the UE and the VAL server. From the perspective of the application, as one endpoint is a dynamically deployed, UE service is abstracted away, that is, it operates like a normal client-server interaction. In some implementations the far-edge framework may keep track of the performance or manage the lifecycle. For example, if the VAL server later requests to terminate the workload, or if the conditions of the UE has changed, the FCES or far-edge computing manager of the edge data network may transmit a command to stop the workload and may cause the UE leave the cluster, etc.
[0126] Although not specifically illustrated, in Figure 6 the operation 600 may include executing the workload. The workload, when executed, may be operable to access at least one hardware component of the UE. The at least one hardware components may include an imaging device (e.g., camera), a sensor (e.g., location sensor), or a communication device (e.g., Wi-Fi).Attorney Docket No. [PC934549WO]14737543-1
[0127] It should be noted that the operation 600 described herein describes a possible implementation, and that the operation 600 may be rearranged or otherwise modified and that other implementations are possible. For example, the operation 600 may include, prior to 602, obtaining a list of devices, including one or more UE, that have joined the far-edge compute cluster; retrieving a list of available workloads; and selecting the workload from the list of available workloads for deployment in at least one UE in the list of devices. For example, the operation 600 may include the VAL server receiving at least one applicationlayer report from the deployed workload running on the UE (e.g., after establishing the connection to enable application layer communication between the VAL server and the deployed workload running on the UE.
[0128] The operations 400, 500, 600 have demonstrated the secure and dynamic joining of UE to an edge compute cluster and the seamless deployment of workloads onto them by the network. In some implementations, in the operations, the UE may not require annual intervention. In some implementations, the entire process from the UE joining the far-edge compute cluster to running an application or workload may be orchestrated by the network and may be triggered by a remote application (e.g., VAL server). In some implementations, the role or operations of the UE is largely automated via the FCE client components, which may ensure ease of use. In some implementations, the network may make all the decisions behind the scenes (authenticating the UE, selecting UE for workload deployment, providing the correct workload, etc.), which may be particularly useful for scalability (e.g., when dealing with thousands of UE).
[0129] As mentioned, various modifications or rearrangements may be made to the example operations 400, 500, 600.
[0130] For example, in some implementations, in relation to workload discovery and / or UE selection, although some embodiments may assume the VAL server specifies the target UE for workload deployment, some embodiments may support a more network-driven selection of UE for workload deployment. For example, the VAL server may request a workload to be deployed near a particular location. In this case, the FCES and far-edge computing manager of the edge data network may cooperate to discover a suitable UE that is currently available (joined the cluster) and can meet the criteria. In someAttorney Docket No. [PC934549WO]14737543-1implementations, the far-edge computing manager may keep an inventory of one or more UE with their location and capabilities, to enable a resource discovery mechanism. In some implementations, the FCE-1 interface may carry information about candidate selection or queries for available UE. This capability may highlight that the framework is not only deployed to known UE but may also find the best UE (or multiple best UE) for a job if needed, which is a form of workload placement optimization in far-edge context.
[0131] For example, in some implementations, in relation to security and trust, one or more interfaces in the system may be secured according to its role. In some implementations, the join procedure (the UE joining the cluster) may use secure tokens and authentication to prevent unauthorized cluster access. In one implementation using Docker, secure swarm join may be achieved through the FCE-1, FCE-4, and FCE-6 interfaces, all of which may be protected by encryption and authentication at multiple layers. The deployment commands and registry access may likewise be secure. In some implementations, the registry may require the UE to present a token to download the image (for preventing arbitrary parties from pulling images). In some implementations, the FCEC of the UE may act as a guardian. For example, if a workload or command appears (is suspected) to be unauthorized or harmful, the UE may refuse or ignore the workload or comment. For example, if the workload is not signed by a trusted authority, the FCEC may not launch it. Furthermore, the network can enforce that only certain VAL servers (e.g., those that are authorized clients of the operator’s edge computing service) may invoke the FCE APIs, thereby sandboxing this powerful capability to trusted partners.
[0132] For example, in some implementations, in relation to lifecycle management, the framework may support the full lifecycle, including, e.g., the VAL server may later send a request to terminate the workload, or the UE may voluntarily leave the cluster (e.g., due to low battery). In either case, similar signaling may occur (e.g., a far-edge teardown request from VAL server or a far-edge leave request from the UE, and the FCES and the far-edge computing manager may coordinate safe removal of the workload or the node. The dynamic nature may mean that UE can come and go and workloads can migrate or be redeployed as needed, all orchestrated by the central manager.Attorney Docket No. [PC934549WO]14737543-1
[0133] For example, in some implementations, in terms of deployment, there may be multiple far-edge clusters available, each with its own managing entity and its own one or more workload repositories. In some implementations, a UE may be preconfigured with an identity of a far-edge cluster. The UE may include this identity in the request in 404 to obtain join information for the far-edge cluster. In some implementations, a UE may need to discover which far-edge compute clusters are available for selecting one to join. For example, in some implementations, after 402, the UE may transmit a discovery request (a request to provide information of one or more available far-edge compute clusters) to the FCES, and may, in response, receive a discovery response including a list of one or more far-edge cluster identities. The UE may select one far-edge cluster to join based on its implementation or the configuration data.
[0134] The far-edge computing enablement framework disclosed herein may provide a comprehensive solution to turn UE into manageable edge compute nodes. The framework may be flexible to accommodate different technologies and use cases. The framework may ensure that one or more UE can be efficiently leveraged for computing tasks while the integrity of both network and the devices (UE) is maintained.
[0135] The far-edge computing enablement framework disclosed herein may include one or more features and / or one or more advantages.
[0136] In some embodiments, the framework may incorporate UE as edge compute nodes. For example, unlike conventional edge computing that relies on fixed edge servers, the framework disclosed herein treats end-user devices as part of the compute infrastructure in a managed way. This may be a new paradigm, in which one or more UE (which traditionally only consume services) may provide computational services on demand. This may be enabled by the various entities of the framework.
[0137] In some embodiments, the framework may enable secure and dynamic onboarding of devices (UE). In some embodiments, the framework may provide a way (with dedicated signaling and interfaces) for dynamically recruiting UE into the edge compute cluster, and may include security measures to authenticate devices and authorize their participation. In some embodiments the use of join tokens and an enabler client may ensure that the process is automated and secure. The dynamic onboarding may be far more Attorney Docket No. [PC934549WO]14737543-1flexible than static pre-configuration and may allow the edge cluster composition to change in real-time (devices (UE) may join and leave based on demand, context, policy, etc.
[0138] In some embodiments, the framework may enable seamless workload deployment and orchestration. In some embodiments, the framework may enable an end-to-end pipeline in which an application provider may deploy a workload to a UE as easily as deploying to a cloud server, with the network handling the orchestration and management. The VAL server may issue a request, and the system may takes care of finding the right device, transferring the code, and running it, then linking it back to the application. This level of seamless orchestration on heterogeneous user devices may be unique. The approach may abstract the complexity of dealing with various device types, connectivity issues, and so on.
[0139] In some embodiments, the framework may provide defined Interfaces for far-edge computing. In some embodiments, the framework may provide defined reference interfaces (FCE-1 to FCE-6, FCE-U, FCE-uu) specifically tailored for far-edge computing operations. The framework may provide a blueprint that could be standardized, enabling interoperability. Each interface may have defined responsibilities (e.g., FCE-5 for workload data transfer, FCE-4 for cluster control, etc.).
[0140] In some embodiments, the framework may support the use of standardized workload formats (containers) and registries. In some embodiments, the framework may leverage containerization (or similar portable formats) to package workloads. This may be advantageous as it may allow reusing existing DevOps tools and may ensure consistency of application environment on different UE. The introduction of a workload registry may be advantageous in that it may act as a bridge between application deployment and mobile devices (UE). The workload registry may be a network-managed repository operable to push code to devices (UE) for ephemeral execution. This may represent a new way to deliver software to devices (UE) on the fly. In some implementations, the workload registry may also enable the same workload to be easily reused on multiple devices. In some implementations, the updates to the workload can be managed centrally.
[0141] In some embodiments, the framework may provide a network-centric control. For example, in some implementations, various critical decisions (such as the decision of Attorney Docket No. [PC934549WO]14737543-1which workload to run, where to run the workload, when to onboard a device, etc.) may be made by network-side components (e.g., FCES and far-edge computing manager), not by the devices (UE). This may be advantageous as it may offload complexity from UE (which may be power- and / or user-constrained) to the network, which may have a more global view. In some implementations, the FCEC of the UE may be lightweight and may be mostly reactive to network instructions. This design may ensure that the addition of far-edge capabilities may not heavily tax the UE or may not require users to manage anything. The network may also optimize across multiple UE (which cannot be performed by an individual UE).
[0142] In some embodiments, the framework may enable scalability and elastic resource expansion. In some implementations, by recruiting multiple UE, the available pool of edge compute resources may scale with the number of devices in the network. The framework may effectively provide an elastic extension of edge computing capacity.During peak times or special events, many devices may be invited to join whereas during low demand, fewer or no UE may need to participate. The elasticity may be cost-efficient (using existing hardware) and may adapt to dynamic geographic demand (e.g., edge compute follows the crowd). Far-edge nodes may be anywhere the users (UE) are.
[0143] In some embodiments, the framework may be compatible with 5G or beyond 5G networks. In some embodiments, the framework may be designed with 5G or beyond 5G in mind. The framework may work over existing network protocols (using normal data connections, secure APIs, etc.), without requiring a fundamentally new network stack. This may represent an advantage for deployment. Moreover, the framework may complement other 5G or beyond 5G features (e.g., network exposure functions, which could distribute the FCES address or help with policy control). The framework may be readily implementable in existing mobile networks and may be adaptable to future mobile network evolutions which may further decentralize computing.
[0144] In some embodiments, the framework may provide device owner control and incentives. In some implementations the framework may incorporate mechanisms for device (UE) owners to grant permission or be incentivized to participate (e.g., a user may opt-in via an FCEC app to allow their UE (e.g., phone) to be used when idle, e.g., for aAttorney Docket No. [PC934549WO]14737543-1direct or indirect reward). In some embodiments, the framework may support this by having the FCEC on the device, which may present such controls. This social aspect, enabled by the technical framework in some embodiments, may envision a marketplace or collaborative model of edge computing, mediated by the operator or service provider safely.
[0145] The far-edge computing enablement framework disclosed herein may provide a new layer of computing that is integrated with the wireless communication network, securely utilizing end-user devices. The far-edge computing enablement framework disclosed herein may help to turn the network of subscribers into a distributed cloud, with clear technical means to do so, and may yield advantages in terms of performance, scalability, and / or resource utilization that are highly desirable in 5G and more particularly in beyond 5G.
[0146] The far-edge computing enablement framework disclosed herein may enable user equipment devices (e.g., smartphones, loT nodes, connected vehicles, etc.) to become part of a far-edge compute infrastructure orchestrated by the mobile network. The framework may include a set of functional entities and interfaces that coordinate the secure onboarding of one or more UE as compute nodes and the seamless deployment of workloads (such as containerized applications) onto those UE. IN some implementations, the framework may include an application server, which may be referred to as a Vertical Application Layer (VAL) server, and which may be a server in a vertical application layer or any application provider. The VAL server may request from the FCE framework to deploy a workload on a UE. In response, the FCE framework may handle various aspects associated with finding a suitable UE (if not provided) that has joined the far-edge cluster and instructing the UE to retrieve and execute the workload, after which the VAL server may communicate with the workload as if the workload is hosted on any edge / cloud server. In some implementations, the framework includes, in the edge network, a far-edge computing enabler server (FCES), a far-edge computing manager to manage the cluster of far-edge nodes, and a workload registry to store or locate workload packages In some implementations, the framework includes, in the UE, a far-edge computing enabler client (FCEC) and a far-edge computing client (the runtime environment on the UE for executingAttorney Docket No. [PC934549WO]14737543-1tasks). These components may interact over defined interfaces to achieve secure device onboarding and workload delivery. In one example operation, when a UE comes online or is needed, it can dynamically join the far-edge compute cluster through an authenticated procedure. When a VAL server needs to deploy an application workload (for example, a Docker container or other portable workload) at the far-edge, it may invoke the FCE system to deploy it onto one or more participating UE. The network may orchestrate this deployment seamlessly. For example, the VAL server may request the service, and the FCE framework may handle resource selection, secure setup, and execution in the background.
[0147] Some example implementations of the framework are based on existing technologies such as containerization and 5G network capabilities. The framework may ensure that the process is secure (e.g., only authorized UEs with valid credentials can join and execute code / workloads) and efficient (e / g / . using standardized workloads and registry for rapid deployment). This approach may transform ordinarily passive user devices (UE) into active edge computing nodes, expanding the edge cloud to the far-edge and enabling new use cases that benefit from ultra-distributed computing close to end users.
[0148] Some embodiments disclosed herein may provide an application-layer solution (e.g., suitable for 3GPP SA6) that may give the VAL servers direct workload orchestration capabilities through the FCES. This may align with application-driven orchestration and may introduce various roles (e.g., VAL instructing FCES to deploy workloads across UEs dynamically). Some embodiments disclosed herein may provide a self-initiated join mechanism by UE, e.g., over a RESTful interface (the FCE-uu interface), mediated by a dedicated FCES component and may optionally be implemented using Docker Swarm join tokens.
[0149] Figure 7 illustrates an example of a UE 700 in accordance with aspects of the present disclosure. The UE 700 may support far-edge computing in wireless communication system. The UE 700 may include a processor 702, a memory 704, a controller 706, and a transceiver 708. The processor 702, the memory 704, the controller 706, or the transceiver 708, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure asAttorney Docket No. [PC934549WO]14737543-1described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.
[0150] The processor 702, the memory 704, the controller 706, or the transceiver 708, 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.
[0151] The processor 702 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 702 may be configured to operate the memory 704. In some other implementations, the memory 704 may be integrated into the processor 702. The processor 702 may be configured to execute computer-readable instructions stored in the memory 704 to cause the UE 700 to perform various functions of the present disclosure.
[0152] The memory 704 may include volatile or non-volatile memory. The memory 704 may store computer-readable, computer-executable code including instructions when executed by the processor 702 cause the UE 700 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 704 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.
[0153] In some implementations, the processor 702 and the memory 704 coupled with the processor 702 may be configured to cause the UE 700 to perform one or more of the functions described herein (e.g., executing, by the processor 702, instructions stored in the memory 704). For example, the processor 702 may support wireless communication at the UE 700 in accordance with examples as disclosed herein.Attorney Docket No. [PC934549WO]14737543-1
[0154] In some implementations, the UE 700 may be configured to: obtain information for joining a far-edge compute cluster, the information may include at least one of a token or an address of a managing entity of the far-edge compute cluster, transmit a request to join the far-edge compute cluster as a far-edge compute node based at least in part on the token and / or the address, and receive a response indicating that the request is accepted. In some implementations, the request to join the far-edge compute cluster may include the token and may be transmitted to the managing entity of the far-edge compute cluster based on the address. In some implementations, the response may be received from the managing entity of the far-edge compute cluster. Optionally, the token may be a single-use token, a time-limited token, and / or a unique token for the UE. Optionally, the information for joining the far-edge compute cluster may further include at least one of: address or identifier information of at least one workload repository associated with the far-edge compute cluster, or security credentials for accessing the at least one workload repository.
[0155] In some implementations, the UE 700 may be configured to: transmit, to a network node, a request to provide information of one or more available far-edge compute clusters, and receive, from the network node, a list including one or more far-edge compute cluster identities. The list may include an identity of the far-edge compute cluster.
[0156] In some implementations, the UE 700 may be configured to: transmit, to a network node, a request for information for joining the far-edge compute cluster, the request for information may include at least one of: an identity of the UE, credential information of the UE, or an identity of the far-edge compute cluster. In some implementations, the UE 700 may be configured to: receive, from the network node, the information for joining the far-edge compute cluster. Optionally, the request for information may further include capability information of the UE, which may include at least one of: a processing capability of the UE, a memory capability of the UE, or a power status of the UE.
[0157] In some implementations, the UE 700 may be configured to: receive a request associated with initiation of workload deployment, the request may include an identifier of a workload to be deployed, obtain the workload based at least in part on the identifier of the workload, deploy the workload, and output an indication to indicate success or completionAttorney Docket No. [PC934549WO]14737543-1of deployment of the workload. Optionally, the identifier of the workload to be deployed may include address or identifier of at least one workload repository associated with the workload to be deployed. Optionally, the request associated with initiation of workload deployment may include at least one of: address or identifier information of at least one workload repository associated with the far-edge compute cluster, or security credentials for accessing the at least one workload repository. Optionally, the request associated with initiation of workload deployment may further include configuration data associated with the workload. The configuration data may include environmental variable associated with the workload. For example, the configuration data may include an address of an application server for application layer communication with the workload.
[0158] In some implementations, the UE 700 may be configured to: execute the workload. In some implementations, the workload, when executed, may be operable to access at least one hardware component of the UE 700 such as an imaging device, a sensor, or a communication device of the UE 700.
[0159] In some implementations, the UE 700 may be configured to: establish (optionally initiating) a connection with an application server, based at least in part on the configuration data, to enable application layer communication between the deployed workload and the application server.
[0160] In some implementations, the UE 700 may be configured to implement a far-edge computing enabler client, a far-edge computing client, or a combination thereof.
[0161] The controller 706 may manage input and output signals for the UE 700. The controller 706 may also manage peripherals not integrated into the UE 700. In some implementations, the controller 706 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 706 may be implemented as part of the processor 702.
[0162] In some implementations, the UE 700 may include at least one transceiver 708. In some other implementations, the UE 700 may have more than one transceiver 708. The transceiver 708 may represent a wireless transceiver. The transceiver 708 may include one or more receiver chains 710, one or more transmitter chains 712, or a combination thereof.Attorney Docket No. [PC934549WO]14737543-1
[0163] A receiver chain 710 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 710 may include one or more antennas for receive the signal over the air or wireless medium. The receiver chain 710 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 710 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 710 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.
[0164] A transmitter chain 712 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 712 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 712 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 712 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.
[0165] Figure 8 illustrates an example of a processor 800 in accordance with aspects of the present disclosure. The processor 800 may support far-edge computing in wireless communication system. The processor 800 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 800 may include a controller 802 configured to perform various operations in accordance with examples as described herein. The processor 800 may optionally include at least one memory 804, which may be, for example, an L1 / L2 / L3 cache. Additionally, or alternatively, the processor 800 may optionally include one or more arithmetic-logic units (ALUs) 806. 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).Attorney Docket No. [PC934549WO]14737543-1
[0166] The processor 800 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 800) 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).
[0167] The controller 802 may be configured to manage and coordinate various operations (e.g., signaling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 800 to cause the processor 800 to support various operations in accordance with examples as described herein. For example, the controller 802 may operate as a control unit of the processor 800, generating control signals that manage the operation of various components of the processor 800. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.
[0168] The controller 802 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 804 and determine subsequent instruction(s) to be executed to cause the processor 800 to support various operations in accordance with examples as described herein. The controller 802 may be configured to track memory address of instructions associated with the memory 804. The controller 802 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 802 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 800 to cause the processor 800 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 802 may be configured to manage flow of data within the processor 800. The controller 802 may be configured to control transferAttorney Docket No. [PC934549WO]14737543-1of data between registers, arithmetic logic units (ALUs), and other functional units of the processor 800.
[0169] The memory 804 may include one or more caches (e.g., memory local to or included in the processor 800 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, the memory 804 may reside within or on a processor chipset (e.g., local to the processor 800). In some other implementations, the memory 804 may reside external to the processor chipset (e.g., remote to the processor 800).
[0170] The memory 804 may store computer-readable, computer-executable code including instructions that, when executed by the processor 800, cause the processor 800 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 802 and / or the processor 800 may be configured to execute computer-readable instructions stored in the memory 804 to cause the processor 800 to perform various functions. For example, the processor 800 and / or the controller 802 may be coupled with or to the memory 804, the processor 800, the controller 802, and the memory 804 may be configured to perform various functions described herein. In some examples, the processor 800 may include multiple processors and the memory 804 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.
[0171] The one or more ALUs 806 may be configured to support various operations in accordance with examples as described herein. In some implementations, the one or more ALUs 806 may reside within or on a processor chipset (e.g., the processor 800). In some other implementations, the one or more ALUs 806 may reside external to the processor chipset (e.g., the processor 800). One or more ALUs 806 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 806 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 806 be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logicAttorney Docket No. [PC934549WO]14737543-1gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 806 may support logical operations such as AND, OR, exclusive-OR (XOR), not-OR (NOR), and not- AND (NAND), enabling the one or more ALUs 806 to handle conditional operations, comparisons, and bitwise operations.
[0172] The processor 800 may support wireless communication in accordance with examples as disclosed herein.
[0173] In some implementations of a first aspect, the processor 800 may be operable to support a means for or may be configured to: obtain information for joining a far-edge compute cluster, the information may include at least one of a token or an address of a managing entity of the far-edge compute cluster, transmit a request to join the far-edge compute cluster as a far-edge compute node based at least in part on the token and / or the address, and receive a response indicating that the request is accepted. In some implementations of the first aspect, the request to join the far-edge compute cluster may include the token and may be transmitted to the managing entity of the far-edge compute cluster based on the address. In some implementations of the first aspect, the response may be received from the managing entity of the far-edge compute cluster. Optionally, the token may be a single-use token, a time-limited token, and / or a unique token for the UE.Optionally, the information for joining the far-edge compute cluster may further include at least one of: address or identifier information of at least one workload repository associated with the far-edge compute cluster, or security credentials for accessing the at least one workload repository.
[0174] In some implementations of the first aspect, the processor 800 may be operable to support a means for or may be configured to: transmit, to a network node, a request to provide information of one or more available far-edge compute clusters, and receive, from the network node, a list including one or more far-edge compute cluster identities. The list may include an identity of the far-edge compute cluster.
[0175] In some implementations of the first aspect, the processor 800 may be operable to support a means for or may be configured to: transmit, to a network node, a request for information for joining the far-edge compute cluster, the request for information may include at least one of: an identity of the UE, credential information of the UE, or an Attorney Docket No. [PC934549WO]14737543-1identity of the far-edge compute cluster. In some implementations of the first aspect, the processor 800 may be operable to support a means for or may be configured to: receive, from the network node, the information for joining the far-edge compute cluster.Optionally, the request for information may further include capability information of the UE, which may include at least one of: a processing capability of the UE, a memory capability of the UE, or a power status of the UE.
[0176] In some implementations of the first aspect, the processor 800 may be operable to support a means for or may be configured to: receive a request associated with initiation of workload deployment, the request may include an identifier of a workload to be deployed, obtain the workload based at least in part on the identifier of the workload, deploy the workload, and output an indication to indicate success or completion of deployment of the workload. Optionally, the identifier of the workload to be deployed may include address or identifier of at least one workload repository associated with the workload to be deployed. Optionally, the request associated with initiation of workload deployment may include at least one of: address or identifier information of at least one workload repository associated with the far-edge compute cluster, or security credentials for accessing the at least one workload repository. Optionally, the request associated with initiation of workload deployment may further include configuration data associated with the workload. The configuration data may include environmental variable associated with the workload. For example, the configuration data may include an address of an application server for application layer communication with the workload.
[0177] In some implementations of the first aspect, the processor 800 may be operable to support a means for or may be configured to: execute the workload. In some implementations of the first aspect, the workload, when executed, may be operable to access at least one hardware component of the UE such as an imaging device, a sensor, or a communication device of the UE.
[0178] In some implementations of the first aspect, the processor 800 may be operable to support a means for or may be configured to: establish (optionally initiating) a connection with an application server, based at least in part on the configuration data, toAttorney Docket No. [PC934549WO]14737543-1enable application layer communication between the deployed workload and the application server.
[0179] In some implementations of the first aspect, the processor 800 may be operable to support a means for or may be configured to implement a far-edge computing enabler client, a far-edge computing client, or a combination thereof.
[0180] In some implementations of a second aspect, the processor 800 may be operable to support a means for or may be configured to: receive a request for information for joining a far-edge compute cluster, the request for information may include at least one of: an identity of a UE, credential information of the UE, or an identity of the far-edge compute cluster; generate and / or retrieve the information for joining the far-edge compute cluster, the information may include at least one of a token or an address of a managing entity of the far-edge compute cluster; and output the information for joining the far-edge compute cluster. Optionally, the request for information may further include capability information of the UE which may include at least one of: a processing capability of the UE, a memory capability of the UE, or a power status of the UE. Optionally, the information for joining the far-edge compute cluster may further include at least one of: address or identifier information of at least one workload repository associated with the far-edge compute cluster, or security credentials for accessing the at least one workload repository.
[0181] In some implementations of the second aspect, the processor 800 may be operable to support a means for or may be configured to: receive a request to provide information of one or more available far-edge compute clusters, and output a list including one or more far-edge compute cluster identities, including an identity of the far-edge compute cluster.
[0182] In some implementations of the second aspect, the processor 800 may be operable to support a means for or may be configured to: receive, from an application server, a request to deploy a workload in the far-edge compute cluster, the request may include an identifier of the workload and at least one of: an identifier associated with a UE of the far-edge compute cluster for deploying the workload or one or more criteria for selecting a UE from the far-edge compute cluster for deploying the workload; generate a workload deployment command based at least in part on the request to deploy the workload Attorney Docket No. [PC934549WO]14737543-1in the far-edge compute cluster, the workload deployment command may include the identifier of the workload and one of: the identifier associated with the UE or an identifier of a UE selected based on the one or more criteria, and output the workload deployment command to the managing entity of the far-edge compute cluster. The one or more criteria for selecting the UE may include at least one of: a location criteria associated with UE location or a capability criteria associated with UE capability (e.g., processing capability, memory capability, power status, etc.). Optionally, the request to deploy the workload in the far-edge compute cluster may include configuration data associated with the workload. The workload deployment command may include the configuration data associated with the workload. The configuration data may include environmental variable associated with the workload. For example, the configuration data may include an address of an application server for application layer communication with the workload.
[0183] In some implementations of the second aspect, the processor 800 may be operable to support a means for or may be configured to: receive, from the managing entity of the far-edge compute cluster, a response indicating success or completion of the workload deployment at the UE of the far-edge compute cluster.
[0184] In some implementations of the second aspect, the processor 800 may be operable to support a means for or may be configured to: receive, from an application server, a request to onboard a workload in at least one workload repository, the request may include metadata of the workload to be onboarded; facilitating onboarding of the workload in the at least one workload repository based at least in part on the metadata; and transmitting, to the application server, a response indicating success or completion of the workload onboarding, the response may include an identifier for the workload. Optionally, the metadata of the workload to be onboarded may include at least one of: an identifier of the workload, a name of the workload, a description of the workload, resource requirement of the workload, an application artifact of the workload, or a reference to the application artifact of the workload.
[0185] In some implementations of a third aspect, the processor 800 may be operable to support a means for or may be configured to: output a request to deploy a workload in a far-edge compute cluster, the request may include an identifier of the workload and at least oneAttorney Docket No. [PC934549WO]14737543-1of: an identifier associated with a UE of the far-edge compute cluster for deploying the workload or one or more criteria for selecting a UE from the far-edge compute cluster for deploying the workload; and receive at least one of: a response indicating initiation of the workload deployment at a UE of the far-edge compute cluster, or a response indicating success or completion of the workload deployment at a UE of the far-edge compute cluster. For example, the one or more criteria for selecting the UE may include at least one of: a location criteria associated with UE location or a capability criteria associated with UE capability (e.g., processing capability, memory capability, power status, etc.). Optionally, the request to deploy the workload in the far-edge compute cluster may include configuration data associated with the workload. The configuration data may include environmental variable associated with the workload. For example, the configuration data may include an address of an application server for application layer communication with the workload.
[0186] In some implementations of the third aspect, the processor 800 may be operable to support a means for or may be configured to: obtain a list of devices, including one or more UE, that have joined the far-edge compute cluster; retrieve a list of available workloads; and select the workload from the list of available workloads for deployment in at least one UE in the list of devices.
[0187] In some implementations of the third aspect, the processor 800 may be operable to support a means for or may be configured to: connect (or establish connection) with the UE to enable application layer communication between the application server and the deployed workload running on the UE, and receive at least one application-layer report from the deployed workload running on the UE.
[0188] In some implementations of the third aspect, the processor 800 may be operable to support a means for or may be configured to: transmit, to a network node, a request to onboard the workload in a workload repository, the request may include metadata of the workload to be onboarded; and receive, from the network node, a response indicating success or completion of the workload onboarding, the response may include an identifier for the workload. For example, the metadata of the workload to be onboarded may include at least one of: an identifier of the workload, a name of the workload, a description of theAttorney Docket No. [PC934549WO]14737543-1workload, resource requirement of the workload, an application artifact of the workload, or a reference to the application artifact of the workload.
[0189] Figure 9 illustrates an example of a NE 900 in accordance with aspects of the present disclosure. The NE 900 may support far-edge computing in wireless communication system. The NE 900 may include a processor 902, a memory 904, a controller 906, and a transceiver 908. The processor 902, the memory 904, the controller 906, or the transceiver 908, 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.
[0190] The processor 902, the memory 904, the controller 906, or the transceiver 908, 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.
[0191] The processor 902 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 902 may be configured to operate the memory 904. In some other implementations, the memory 904 may be integrated into the processor 902. The processor 902 may be configured to execute computer-readable instructions stored in the memory 904 to cause the NE 900 to perform various functions of the present disclosure.
[0192] The memory 904 may include volatile or non-volatile memory. The memory 904 may store computer-readable, computer-executable code including instructions when executed by the processor 902 cause the NE 900 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 904 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-transitoryAttorney Docket No. [PC934549WO]14737543-1storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.
[0193] In some implementations, the processor 902 and the memory 904 coupled with the processor 902 may be configured to cause the NE 900 to perform one or more of the functions described herein (e.g., executing, by the processor 902, instructions stored in the memory 904). For example, the processor 902 may support wireless communication at the NE 900 in accordance with examples as disclosed herein.
[0194] In some implementations, the NE 900 may be configured to: receive a request for information for joining a far-edge compute cluster, the request for information may include at least one of: an identity of a UE, credential information of the UE, or an identity of the far-edge compute cluster; generate and / or retrieve the information for joining the far-edge compute cluster, the information may include at least one of a token or an address of a managing entity of the far-edge compute cluster; and output the information for joining the far-edge compute cluster. Optionally, the request for information may further include capability information of the UE which may include at least one of: a processing capability of the UE, a memory capability of the UE, or a power status of the UE. Optionally, the information for joining the far-edge compute cluster may further include at least one of: address or identifier information of at least one workload repository associated with the far-edge compute cluster, or security credentials for accessing the at least one workload repository.
[0195] In some implementations, the NE 900 may be configured to: receive a request to provide information of one or more available far-edge compute clusters, and output a list including one or more far-edge compute cluster identities, including an identity of the far-edge compute cluster.
[0196] In some implementations, the NE 900 may be configured to: receive, from an application server, a request to deploy a workload in the far-edge compute cluster, the request may include an identifier of the workload and at least one of: an identifier associated with a UE of the far-edge compute cluster for deploying the workload or one or more criteria for selecting a UE from the far-edge compute cluster for deploying the workload; generate a workload deployment command based at least in part on the request Attorney Docket No. [PC934549WO]14737543-1to deploy the workload in the far-edge compute cluster, the workload deployment command may include the identifier of the workload and one of: the identifier associated with the UE or an identifier of a UE selected based on the one or more criteria, and output the workload deployment command to the managing entity of the far-edge compute cluster. For example, the one or more criteria for selecting the UE may include at least one of: a location criteria associated with UE location or a capability criteria associated with UE capability (e.g., processing capability, memory capability, power status, etc.). Optionally, the request to deploy the workload in the far-edge compute cluster may include configuration data associated with the workload. The workload deployment command may include the configuration data associated with the workload. The configuration data may include environmental variable associated with the workload. For example, the configuration data may include an address of an application server for application layer communication with the workload.
[0197] In some implementations, the NE 900 may be configured to: receive, from the managing entity of the far-edge compute cluster, a response indicating success or completion of the workload deployment at the UE of the far-edge compute cluster.
[0198] In some implementations, the NE 900 may be configured to: receive, from an application server, a request to onboard a workload in at least one workload repository, the request may include metadata of the workload to be onboarded; facilitating onboarding of the workload in the at least one workload repository based at least in part on the metadata; and transmitting, to the application server, a response indicating success or completion of the workload onboarding, the response may include an identifier for the workload.Optionally, the metadata of the workload to be onboarded may include at least one of: an identifier of the workload, a name of the workload, a description of the workload, resource requirement of the workload, an application artifact of the workload, or a reference to the application artifact of the workload.
[0199] The controller 906 may manage input and output signals for the NE 900. The controller 906 may also manage peripherals not integrated into the NE 900. In some implementations, the controller 906 may utilize an operating system such as iOS®,Attorney Docket No. [PC934549WO]14737543-1ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 906 may be implemented as part of the processor 902.
[0200] In some implementations, the NE 900 may include at least one transceiver 908. In some other implementations, the NE 900 may have more than one transceiver 908. The transceiver 908 may represent a wireless transceiver. The transceiver 908 may include one or more receiver chains 910, one or more transmitter chains 912, or a combination thereof.
[0201] A receiver chain 910 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 910 may include one or more antennas for receive the signal over the air or wireless medium. The receiver chain 910 may include at least one amplifier (e.g., a low-noise amplifier (LN A)) configured to amplify the received signal. The receiver chain 910 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 910 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.
[0202] A transmitter chain 912 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 912 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 912 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 912 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.
[0203] Figure 10 illustrates a flowchart of a method in accordance with aspects of the present disclosure. The operations of the method may be implemented by a UE as described herein or a processor 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 describedAttorney Docket No. [PC934549WO]14737543-1functions. The method in Figure 10 may relate to enabling a UE to join a far-edge compute cluster.
[0204] At 1002, the method may include obtaining information for joining a far-edge compute cluster. The information may include at least one of a token or an address of a managing entity of the far-edge compute cluster. Optionally, the token may be a single-use token, a time-limited token, and / or a unique token for the UE. Optionally, the information may further include at least one of: address or identifier information of at least one workload repository associated with the far-edge compute cluster, or security credentials for accessing the at least one workload repository. Optionally, the obtaining of the information may include: transmitting, to a network node, a request for information for joining the far-edge compute cluster, the request for information may include at least one of: an identity of the UE, credential information of the UE, or an identity of the far-edge compute cluster, and receiving, from the network node, the information for joining the far-edge compute cluster. Optionally, the request for information may further include capability information of the UE, which may include at least one of: a processing capability of the UE, a memory capability of the UE, or a power status of the UE. 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 UE as described with reference to Figure 7 or a processor as described with reference to Figure 8.
[0205] At 1004, the method may include transmitting a request to join the far-edge compute cluster as a far-edge compute node based at least in part on the token and / or the address. For example, the request to join the far-edge compute cluster may include the token and the request may be transmitted to the managing entity of the far-edge compute cluster based on the address. Optionally, the request to join the far-edge compute cluster may further include capability information of the UE, which may include at least one of: a processing capability of the UE, a memory capability of the UE, or a power status of the UE. 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 UE as described with reference to Figure 7 or a processor as described with reference to Figure 8.Attorney Docket No. [PC934549WO]14737543-1
[0206] At 1006, the method may include receiving a response indicating that the request is accepted. The response may be received from the managing entity of the far-edge compute cluster. The operations of 1006 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1006 may be performed a UE as described with reference to Figure 7 or a processor as described with reference to Figure 8.
[0207] In some implementations, the method of Figure 10 may further include transmitting, to a network node, a request to provide information of one or more available far-edge compute clusters, and receiving, from the network node, a list including one or more far-edge compute cluster identities. The list may include an identity of the far-edge compute cluster.
[0208] It should be noted that the method described herein with reference to Figure 10 describes a possible implementation, and that the operations and the steps with reference to Figure 10 may be rearranged or otherwise modified and that other implementations are possible.
[0209] Figure 11 illustrates a flowchart of a method in accordance with aspects of the present disclosure. The operations of the method may be implemented by a UE as described herein or a processor 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. The method in Figure 11 may relate to enabling workload deployment and / or execution in a UE of a far-edge compute cluster.
[0210] At 1102, the method may include receiving a request associated with initiation of workload deployment. The request may include an identifier of a workload to be deployed. Optionally, the identifier of the workload to be deployed may include address or identifier of at least one workload repository associated with the workload to be deployed. Optionally, the request may further include at least one of: address or identifier information of at least one workload repository associated with the far-edge compute cluster, or security credentials for accessing the at least one workload repository. Optionally, the request may further include configuration data associated with the workload such as environmental variable associated with the workload. For example, the configuration data may include an Attorney Docket No. [PC934549WO]14737543-1address of an application server for application layer communication with the workload. 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 UE as described with reference to Figure 7 or a processor as described with reference to Figure 8.
[0211] At 1104, the method may include obtaining the workload based at least in part on the identifier of the workload. 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 UE as described with reference to Figure 7 or a processor as described with reference to Figure 8.
[0212] At 1106, the method may include deploying the workload. The operations of 1106 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1106 may be performed a UE as described with reference to Figure 7 or a processor as described with reference to Figure 8.
[0213] At 1108, the method may include outputting an indication to indicate success or completion of deployment of the workload. The operations of 1108 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1108 may be performed a UE as described with reference to Figure 7 or a processor as described with reference to Figure 8.
[0214] In some implementations, the method of Figure 11 may further include executing the workload. Optionally, the workload, when executed, may be operable to access at least one hardware component of the UE (e.g., an imaging device, a sensor, or a communication device of the UE). In some implementations, the method of Figure 11 may further include establishing (optionally initiating) a connection with an application server, based at least in part on the configuration data, to enable application layer communication between the deployed workload and the application server.
[0215] It should be noted that the method described herein with reference to Figure 11 describes a possible implementation, and that the operations and the steps with reference toAttorney Docket No. [PC934549WO]14737543-1Figure 11 may be rearranged or otherwise modified and that other implementations are possible.
[0216] Figure 12 illustrates a flowchart of a method in accordance with aspects of the present disclosure. The operations of the method may be implemented by a NE or an edge network node 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. In some implementations, the edge network node may execute a set of instructions to control the function elements of the edge network node to perform the described functions. The method in Figure 12 may relate to enabling a UE to join a far-edge compute cluster.
[0217] At 1202, the method may include receiving (e.g., from a UE) a request for information for joining a far-edge compute cluster. The request may include at least one of: an identity of a UE, credential information of the UE, or an identity of the far-edge compute cluster. Optionally the request may further include capability information of the UE, which may include at least one of: a processing capability of the UE, a memory capability of the UE, or a power status of the UE. The operations of 1202 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1202 may be performed by a NE as described with reference to Figure 9 or an edge network node.
[0218] At 1204, the method may include generating and / or retrieving the information for joining the far-edge compute cluster. The information may include at least one of a token or an address of a managing entity of the far-edge compute cluster. Optionally, the information for joining the far-edge compute cluster may further include at least one of: address or identifier information of at least one workload repository associated with the far-edge compute cluster, or security credentials for accessing the at least one workload repository. The operations of 1204 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1204 may be performed by a NE as described with reference to Figure 9 or an edge network node.
[0219] At 1206, the method may include outputting the information for joining the far-edge compute cluster. For example, the information for joining the far-edge compute cluster may be output for transmission to the UE. The operations of 1206 may be performed Attorney Docket No. [PC934549WO]14737543-1in accordance with examples as described herein. In some implementations, aspects of the operations of 1206 may be performed a NE as described with reference to Figure 9 or an edge network node.
[0220] In some implementations, the method of Figure 12 may further include receiving (e.g., from a UE) a request to provide information of one or more available far-edge compute clusters, and outputting a list including one or more far-edge compute cluster identities, including an identity of the far-edge compute cluster. For example, the list may be output to the UE.
[0221] It should be noted that the method described herein with reference to Figure 12 describes a possible implementation, and that the operations and the steps with reference to Figure 12 may be rearranged or otherwise modified and that other implementations are possible.
[0222] Figure 13 illustrates a flowchart of a method in accordance with aspects of the present disclosure. The operations of the method may be implemented by a NE or an edge network node 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. In some implementations, the edge network node may execute a set of instructions to control the function elements of the edge network node to perform the described functions. The method in Figure 13 may relate to enabling workload deployment and / or execution in a UE of a far-edge compute cluster.
[0223] At 1302, the method may include receiving (e.g., from an application server) a request to deploy a workload in the far-edge compute cluster. The request may include an identifier of the workload and at least one of: an identifier associated with a UE of the far-edge compute cluster for deploying the workload or one or more criteria for selecting a UE from the far-edge compute cluster for deploying the workload. For example, the one or more criteria for selecting the UE may include at least one of: a location criteria associated with UE location or a capability criteria associated with UE capability (e.g., processing capability, memory capability, power status, etc.). Optionally, the request may further include configuration data associated with the workload, which may include environmental variable associated with the workload. For example, the configuration data may include an Attorney Docket No. [PC934549WO]14737543-1address of an application server for application layer communication with the workload. The operations of 1302 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1302 may be performed by a NE as described with reference to Figure 9 or an edge network node.
[0224] At 1304, the method may include generating a workload deployment command based at least in part on the request to deploy the workload in the far-edge compute cluster. The workload deployment command may include the identifier of the workload and one of: the identifier associated with the UE or an identifier of a UE selected based on the one or more criteria. Optionally, the workload deployment command may include the configuration data associated with the workload. The operations of 1304 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1304 may be performed by a NE as described with reference to Figure 9 or an edge network node.
[0225] At 1306, the method may include outputting the workload deployment command to the managing entity of the far-edge compute cluster. The operations of 1306 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1306 may be performed a NE as described with reference to Figure 9 or an edge network node.
[0226] In some implementations, the method of Figure 13 may further include receiving, from the managing entity of the far-edge compute cluster, a response indicating success or completion of the workload deployment at the UE of the far-edge compute cluster.
[0227] It should be noted that the method described herein with reference to Figure 13 describes a possible implementation, and that the operations and the steps with reference to Figure 13 may be rearranged or otherwise modified and that other implementations are possible.
[0228] Figure 14 illustrates a flowchart of a method in accordance with aspects of the present disclosure. The operations of the method may be implemented by a NE or an edge network node as described herein. In some implementations, the NE may execute a set ofAttorney Docket No. [PC934549WO]14737543-1instructions to control the function elements of the NE to perform the described functions. In some implementations, the edge network node may execute a set of instructions to control the function elements of the edge network node to perform the described functions. The method in Figure 14 may relate to enabling workload onboarding for a far-edge compute cluster.
[0229] At 1402, the method may include receiving (e.g., from an application server) a request to onboard a workload in at least one workload repository. The request may include metadata of the workload to be onboarded. For example, the metadata of the workload to be onboarded may include at least one of: an identifier of the workload, a name of the workload, a description of the workload, resource requirement of the workload, an application artifact of the workload, or a reference to the application artifact of the workload. The operations of 1402 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1402 may be performed by a NE as described with reference to Figure 9 or an edge network node.
[0230] At 1404, the method may include facilitating onboarding of the workload in the at least one workload repository based at least in part on the metadata. The operations of 1404 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1404 may be performed by a NE as described with reference to Figure 9 or an edge network node.
[0231] At 1406, the method may include outputting a response indicating success or completion of the workload onboarding. The response may include an identifier for the workload. The response may be output for transmission to the application server. The operations of 1406 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1306 may be performed a NE as described with reference to Figure 9 or an edge network node.
[0232] It should be noted that the method described herein with reference to Figure 14 describes a possible implementation, and that the operations and the steps with reference to Figure 14 may be rearranged or otherwise modified and that other implementations are possible.Attorney Docket No. [PC934549WO]14737543-1
[0233] Figure 15 illustrates a flowchart of a method in accordance with aspects of the present disclosure. The operations of the method may be implemented by an application server as described herein. In some implementations, the application server may execute a set of instructions to control the function elements of the application server to perform the described functions. In some implementations, the application server may execute a set of instructions to control the function elements of the application server to perform the described functions. The method in Figure 15 may relate to enabling workload deployment and / or execution in a UE of a far-edge compute cluster.
[0234] At 1502, the method may include outputting a request to deploy a workload in a far-edge compute cluster. The request may include an identifier of the workload and at least one of: an identifier associated with a UE of the far-edge compute cluster for deploying the workload or one or more criteria for selecting a UE from the far-edge compute cluster for deploying the workload. For example, the one or more criteria for selecting the UE may include at least one of: a location criteria associated with UE location or a capability criteria associated with UE capability (e.g., processing capability, memory capability, power status, etc.). For example, the request to deploy may be output for transmission to a network node. Optionally, the request may further include configuration data associated with the workload, which may include environmental variable associated with the workload. For example, the configuration data may include an address of an application server for application layer communication with the workload. The operations of 1502 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1502 may be performed by an application server as disclosed herein.
[0235] At 1504, the method may include receiving at least one of: a response indicating initiation of the workload deployment at a UE of the far-edge compute cluster, or a response indicating success or completion of the workload deployment at a UE of the far-edge compute cluster. For example, the response indicating initiation and / or the response indicating success or completion of the workload deployment may be received from the network node. In some implementations, both response are received, and the response indicating initiation is received before the response indicating success or completion of theAttorney Docket No. [PC934549WO]14737543-1workload deployment. The operations of 1504 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1504 may be performed by an application server as disclosed herein.
[0236] In some implementations, the method of Figure 15 may include, prior to 1502: obtaining a list of devices, including one or more UE, that have joined the far-edge compute cluster, retrieving a list of available workloads, and selecting the workload from the list of available workloads for deployment in at least one UE in the list of devices. In some implementations, the method of Figure 15 may include connecting (or establishing connection) with the UE to enable application layer communication between the application server and the deployed workload running on the UE, and receiving at least one application-layer report from the deployed workload running on the UE.
[0237] It should be noted that the method described herein with reference to Figure 15 describes a possible implementation, and that the operations and the steps with reference to Figure 15 may be rearranged or otherwise modified and that other implementations are possible.
[0238] Figure 16 illustrates a flowchart of a method in accordance with aspects of the present disclosure. The operations of the method may be implemented by an application server as described herein. In some implementations, the application server may execute a set of instructions to control the function elements of the application server to perform the described functions. In some implementations, the application server may execute a set of instructions to control the function elements of the application server to perform the described functions. The method in Figure 16 may relate to enabling workload onboarding for a far-edge compute cluster.
[0239] At 1602, the method may include transmitting (e.g., to a network node) a request to onboard the workload in a workload repository. The request may include metadata of the workload to be onboarded. The metadata of the workload to be onboarded may include at least one of: an identifier of the workload, a name of the workload, a description of the workload, resource requirement of the workload, an application artifact of the workload, or a reference to the application artifact of the workload. The operations of 1602 may be performed in accordance with examples as described herein. In some Attorney Docket No. [PC934549WO]14737543-1implementations, aspects of the operations of 1602 may be performed by an application server as disclosed herein.
[0240] At 1604, the method may include receiving (e.g., from the network node) a response indicating success or completion of the workload onboarding. The response may include an identifier for the workload. The operations of 1604 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1604 may be performed by an application server as disclosed herein.
[0241] It should be noted that the method described herein with reference to Figure 16 describes a possible implementation, and that the operations and the steps with reference to Figure 16 may be rearranged or otherwise modified and that other implementations are possible.
[0242] 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.Attorney Docket No. [PC934549WO]14737543-1
Claims
73CLAIMSWhat is claimed is:
1. An UE for wireless communication, comprising:at least one memory; andat least one processor coupled with the at least one memory and configured to cause the UE to:obtain information for joining a far-edge compute cluster, the information comprises at least one of a token or an address of a managing entity of the far-edge compute cluster;transmit a request to join the far-edge compute cluster as a far-edge compute node based at least in part on the token and / or the address; and receive a response indicating that the request is accepted.
2. The UE of claim 1 ,wherein the request to join the far-edge compute cluster comprises the token and is transmitted to the managing entity of the far-edge compute cluster based on the address; andwherein the response is received from the managing entity of the far- edge compute cluster.
3. The UE of claim 1 or 2, wherein the token is a single-use token, a time-limited token, and / or a unique token for the UE.
4. The UE of any one of claims 1 to 3, wherein the at least one processor is configured to cause the UE to:transmit, to a network node, a request to provide information of one or more available far-edge compute clusters; andreceive, from the network node, a list comprising one or more far- edge compute cluster identities, including an identity of the far-edge compute cluster.Attorney Docket No. [PC934549WO]14737543-1745. The UE of any one of claims 1 to 4, wherein to obtain the information for joining the far-edge compute cluster, the at least one processor is configured to cause the UE to:transmit, to a network node, a request for information for joining the far-edge compute cluster, wherein the request for information comprises at least one of: an identity of the UE, credential information of the UE, or an identity of the far-edge compute cluster; andreceive, from the network node, the information for joining the far- edge compute cluster.
6. The UE of any one of claims 1 to 5, wherein the request to join the far-edge compute cluster comprises capability information of the UE, which comprises at least one of: a processing capability of the UE, a memory capability of the UE, or a power status of the UE.
7. The UE of any one of claims 1 to 6, wherein the at least one processor is configured to cause the UE to:receive a request associated with initiation of workload deployment, the request comprises an identifier of a workload to be deployed;obtain the workload based at least in part on the identifier of the workload;deploy the workload; andoutput an indication to indicate success or completion of deployment of the workload.
8. The UE of claim 7, wherein the at least one processor is configured to cause the UE to:execute the workload;wherein the workload, when executed, is operable to access at least one hardware component of the UE, the at least one hardware components comprises an imaging device, a sensor, or a communication device.Attorney Docket No. [PC934549WO]14737543-1759. The UE of claim 7 or 8, wherein the request associated with initiation of workload deployment comprises configuration data associated with the workload, the configuration data comprises an address of an application server for application layer communication with the workload.
10. The UE of claim 9, wherein the at least one processor is configured to cause the UE to:establish a connection with an application server, based at least in part on the configuration data, to enable application layer communication between the deployed workload and the application server.
11. A network node for wireless communication, comprising:at least one memory; andat least one processor coupled with the at least one memory and configured to cause the network node to:receive a request for information for joining a far-edge compute cluster, the request for information comprises at least one of: an identity of a UE, credential information of the UE, or an identity of the far-edge compute cluster;generate and / or retrieve the information for joining the far-edge compute cluster, the information comprises at least one of a token or an address of a managing entity of the far-edge compute cluster; and output the information for joining the far-edge compute cluster.
12. The network node of claim 11, wherein the at least one processor is configured to cause the network node to:receive a request to provide information of one or more available far- edge compute clusters; andoutput a list comprising one or more far-edge compute cluster identities, including an identity of the far-edge compute cluster.Attorney Docket No. [PC934549WO]14737543-113. The network node of claim 11 or 12, wherein the at least one processor is configured to cause the network node to:receive, from an application server, a request to deploy a workload in the far-edge compute cluster, the request comprises an identifier of the workload and at least one of: an identifier associated with a UE of the far- edge compute cluster for deploying the workload or one or more criteria for selecting a UE from the far-edge compute cluster for deploying the workload;generate a workload deployment command based at least in part on the request to deploy the workload in the far-edge compute cluster, the workload deployment command comprises the identifier of the workload and one of: the identifier associated with the UE or an identifier of a UE selected based on the one or more criteria; andoutput the workload deployment command to the managing entity of the far-edge compute cluster.
14. The network node of claim 13,wherein the request to deploy the workload in the far-edge compute cluster comprises configuration data associated with the workload; andwherein the workload deployment command comprises the configuration data associated with the workload.
15. The network node of claim 13 or 14, wherein the at least one processor is configured to cause the network node to:receive, from the managing entity of the far-edge compute cluster, a response indicating success or completion of the workload deployment at the UE of the far-edge compute cluster.
16. The network node of any one of claims 11 to 15, wherein the at least one processor is configured to cause the network node to:Attorney Docket No. [PC934549WO]14737543-1receive, from an application server, a request to onboard a workload in at least one workload repository, the request comprises metadata of the workload to be onboarded;facilitate onboarding of the workload in the at least one workload repository based at least in part on the metadata; andtransmit, to the application server, a response indicating success or completion of the workload onboarding, the response comprises an identifier for the workload.
17. An application server for wireless communication, comprising:at least one memory; andat least one processor coupled with the at least one memory and configured to cause the application server to:output a request to deploy a workload in a far-edge compute cluster, the request comprises an identifier of the workload and at least one of: an identifier associated with a UE of the far-edge compute cluster for deploying the workload or one or more criteria for selecting a UE from the far-edge compute cluster for deploying the workload; andreceive at least one of:a response indicating initiation of the workload deployment at a UE of the far-edge compute cluster, ora response indicating success or completion of the workload deployment at a UE of the far-edge compute cluster.
18. The application server of claim 17, wherein the at least one processor is configured to cause the application server to, prior to outputting the request to deploy the workload in the far-edge compute cluster:obtain a list of devices, including one or more UE, that have joined the far-edge compute cluster;retrieve a list of available workloads; andselect the workload from the list of available workloads for deployment in at least one UE in the list of devices.Attorney Docket No. [PC934549WO]14737543-17819. The application server of claim 17 or 18, wherein the at least one processor is configured to cause the application server to:connect with the UE to enable application layer communication between the application server and the deployed workload running on the UE; and receive at least one application-layer report from the deployed workload running on the UE.
20. The application server of any one of claims 17 to 19, wherein the at least one processor is configured to cause the application server to:transmit, to a network node, a request to onboard the workload in a workload repository, the request comprises metadata of the workload to be onboarded; and receive, from the network node, a response indicating success or completion of the workload onboarding, the response comprises an identifier for the workload.Attorney Docket No. [PC934549WO]14737543-1
