WO2022020043A1 - Edge computing applications for 5g systems - Google Patents

Abstract

An apparatus and system for edge server deployment are described. The service provider and management system can deploy edge applications servers, edge enable servers, edge configuration servers, and the 5G mobile networks to support edge computing for 3 GPP. In response to a request to install an edge computing (EC) network function (NF), a VNF is instantiated and connected to 5th generation core (5GC) NFs to send information over edge interfaces. In response to a request to terminate the EC NF, the EC NF associated with the EC NF identifier in the request is terminated and the EC NF disconnected from the 5GC NFs. An appropriate notification is sent to indicate successful installation or termination of the EC NF.

Description

EDGE COMPUTING APPLICATIONS FOR 5G SYSTEMS PRIORITY CLAIM

[0001] This application claims the benefit of priority to United States

Provisional Patent Application Serial No. 63/055,057, filed July 22, 2020, which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0002] Embodiments pertain to wireless communications in 5G, or new radio (NR), systems. Some embodiments related to a edge computing in 5G systems. BACKGROUND

[0003] The use and complexity of 3GPP LTE systems (including LTE and LTE- Advanced systems) has increased due to both an increase in the types of devices user equipment (UEs) using network resources as well as the amount of data and bandwidth being used by various applications, such as video streaming, operating on these UEs. With the vast increase in number and diversity of communication devices, the corresponding network environment, including routers, switches, bridges, gateways, firewalls, and load balancers, has become increasingly complicated, especially with the advent of next generation (NG) (or new radio (NR)/5^th generation (5G)) systems. As expected, a number of issues abound with the advent of any new' technology.

BRIEF DESCRIPTION OF THE FIGURES [0004] In the figures, which are not necessarily drawn to scale, like numerals may describe similar components in different views. Like numerals having different letter suffixes may represent different instances of similar components. The figures illustrate generally, by way of example, but not by way of limitation, various embodiments discussed in the present document.

[0005] FIG. 1 A illustrates an architecture of a. network, in accordance with some aspects. [0006] FIG. IB illustrates a non-roaming 5G system architecture in accordance with some aspects.

[0007] FIG. 1C illustrates a non-roaming 5G system architecture in accordance with some aspects. [0008] FIG. 2 illustrates a block diagram of a communication device in accordance with some embodiments.

[0009] FIG. 3 illustrates a 5G edge computing network in accordance with some embodiments.

[0010] FIG. 4 illustrates peer-to-peer (P2P) edge computing management deployment in accordance with some embodiments.

[0011] FIG. 5 illustrates architecture for enabling edge applications in accordance with some embodiments.

[0012] FIG. 6 illustrates an inter-Edge Detection Network (EDN) in accordance with some embodiments. [0013] FIG. 7 illustrates an intra-EDN in accordance with some embodiments.

[0014] FIG. 8 illustrates service provider relationship in an edge computing network deployment in accordance with some embodiments. DETAILED DESCRIPTION

[0015] The following description and the drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in, oi^¬ substituted for, those of other embodiments. Embodiments set forth in the claims encompass ail available equivalents of those claims.

[0016] FIG. 1 A illustrates an architecture of a network in accordance with some aspects. The network 140 A includes 3 GPP LTE/4G and NG network functions. A network function can be implemented as a discrete network element on a dedicated hardware, as a software instance running on dedicated hardware, and/or as a virtualized function instantiated on an appropriate platform, e.g., dedicated hardware or a cloud infrastructure.

[0017] The network 140 A is shown to include user equipment (UE) 101 and UE 102. The UEs 101 and 102 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks) but may also include any mobile or non-mobile computing device, such as portable (laptop) or desktop computers, wireless handsets, drones, or any other computing device including a wired and/or wireless communications interface. The UEs 101 and 102 can be collectively referred to herein as UE 101, and UE 101 can be used to perform one or more of the techniques disclosed herein.

[0018] Any of the radio links described herein (e.g., as used in the network 140 A or any other illustrated network) may operate according to any exemplary radio communication technology and/or standard. Any spectrum management scheme including, for example, dedicated licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (such as Licensed Shared Access (LSA) in 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz, and other frequencies and Spectrum Access System (SAS) in 3.55-3.7 GHz and other frequencies). Different Single Carrier or Orthogonal Frequency Domain Multiplexing (OFDM) modes (CP-QFDM, SC-FDMA, SC-OFDM, filter bank-based muiticarrier (FBMC), OFDMA, etc.), and in particular 3GPP NR, may be used by allocating the OFDM carrier data bit vectors to the corresponding symbol resources. [0019] In some aspects, any of the UEs 101 and 102 can comprise an

Intemet-of-Things (loT) UE or a Cellular loT (CIoT) UE, which can comprise a network access layer designed for low-power loT applications utilizing shortlived UE connections. In some aspects, any of the UEs 101 and 102 can include a narrowband (NB) loT UE (e.g., such as an enhanced NB-IoT (eNB-IoT) UE and Further Enhanced (FeNB-IoT) UE). An loT UE can utilize technologies such as machine-to-machine (M2M) or machine-type communications (MFC) for exchanging data with an MTC server or device via a public land mobile network (PLMN), Proximity-Based Service (ProSe) or device-to-device (D2D) communication, sensor networks, or loT networks. The M2M or MTC exchange of data may be a machine-initiated exchange of data. An loT network includes interconnecting loT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections. The loT UEs may execute background applications (e.g., keepalive messages, status updates, etc.) to facilitate the connections of the loT network, in some aspects, any of the UEs 101 and 102 can include enhanced MIC (eMTC) UEs or further enhanced MIC (FeMTC) UEs.

[0020] The UEs 101 and 102 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) 110. The RAN 110 may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), aNextGen RAN (NG RAN), or some other type of RAN.

[0021] The UEs 101 and 102 utilize connections 103 and 104, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections 103 and 104 are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, such as a Globa! System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push-to-Taik (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, a fifth- generation (5G) protocol, a New⁷ Radio (NR) protocol, and the like.

[0022] In an aspect, the UEs 101 and 102 may further directly exchange communication data via a ProSe interface 105. The ProSe interface 105 may alternatively be referred to as a sideiink (SL) interface comprising one or more logical channels, including but not limited to a Physical Sideiink Control Channel (PSCCH), a Physical Sideiink Shared Channel (PSSCH), a Physical Sideiink Discovery Channel (PSDCEI), a Physical Sideiink Broadcast Channel (PSBCH), and a Physical Sideiink Feedback Channel (PSFCH).

[0023] The UE 102 is shown to be configured to access an access point

(AP) 106 via connection 107. The connection 107 can comprise a local wareless connection, such as, for example, a connection consistent with any IEEE 802.11 protocol, according to which the AP 106 can comprise a wireless fidelity (WiFi®) router. In this example, the AP 106 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below⁷).

[0024] The RAN 110 can include one or more access nodes that enable the connections 103 and 104. These access nodes (ANs) can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), Next Generation NodeBs (gNBs), RAN nodes, and the like, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell), in some aspects, the communication nodes 111 and 112 can be transmission/reception points (TRPs). In instances when the communication nodes 111 and 112 are NodeBs (e.g., eNBs or gNBs), one or more TRPs can function within the communication cell of the NodeBs. The RAN 110 may include one or more RAN nodes for providing macrocells, e.g., macro RAN node 111, and one or more RAN nodes for providing femtoceils or picocells (e.g., ceils having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (UP) RAN node 112. [0025] Any of the RAN nodes 111 and 112 can terminate the air interface protocol and can be the first point of contact for the UEs 101 and 102. In some aspects, any of the RAN nodes 111 and 112 can fulfill various logical functions for the RAN 110 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management. In an example, any of the nodes 111 and/or 112 can be a gNB, an eNB, or another type of RAN node.

[0026] The RAN 110 is shown to be communicatively coupled to a core network (CN) 120 via an SI interface 113. In aspects, the CN 120 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN (e.g., as illustrated in reference to FIGS. IB- 1C). In this aspect, the SI interface 113 is split into two parts: the Sl-U interface 114, which carries traffic data between the RAN nodes 111 and 112 and the serving gateway (S-GW) 122, and the SI -mobility management entity (MME) interface 115, which is a signaling interface between the RAN nodes 111 and 112 and MMEs 121

[0027] In this aspect, the CN 120 comprises the MMEs 121, the S-GW

122, the Packet Data Network (PDN) Gateway (P-GW) 123, and a home subscriber server (HSS) 124. The MMEs 121 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN). The MMEs 121 may manage mobility aspects in access such as gateway selection and tracking area list management. The HSS 124 may comprise a database for network users, including subscription-related information to support the network entities' handling of communication sessions. The CN 120 may comprise one or several HSSs 124, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc. For example, the HSS 124 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.

[0028] The S-GW 122 may terminate the SI interface 113 towards the

RAN 110, and routes data packets between the RAN 110 and the CN 120. In addition, the S-GW 122 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3 GPP mobility. Other responsibilities of the S-GW 122 may include a lawful intercept, charging, and some policy enforcement.

[0029] The P-GW 123 may terminate an SGi interface toward a PDN.

The P-GW 123 may route data packets between the EPC network 120 and external networks such as a network including the application server 184 (alternatively referred to as application function (AF)) via an internet Protocol (IP) interface 125. The P-GW 123 can also communicate data to other external networks 131 A, which can include the Internet, IP multimedia subsystem (IPS) network, and other networks. Generally, the application server 184 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Sendees (PS) domain, LTE PS data services, etc.). In this aspect, the P-GW 123 is shown to be communicatively coupled to an application server 184 via an IP interface 125. The application server 184 can also be configured to support one or more communication services (e.g., Voice-over- Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking sendees, etc.) for the UEs 101 and 102 via the CN 120.

[0030] The P-GW 123 may further be a node for policy enforcement and charging data collection. Policy and Charging Rules Function (PCRF) 126 is the policy and charging control element of the CN 120. In a non-roaming scenario, in some aspects, there may be a single PCRF in the Home Public Land Mobile Network (HPLMN) associated with a UE's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with a local breakout of traffic, there may be two PCRFs associated with a UE's IP-CAN session: a Home PCRF (H-PCRF) within an HPLMN and a Visited PCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN). The PCRF 126 may be communicatively coupled to the application server 184 via the P-GW 123. [0031] In some aspects, the communication network 140 A can be an ioT network or a 5G network, including 5G new radio network using communications in the licensed (5G NR) and the unlicensed (5G NR-U) spectrum. One of the current enablers of IoT is the narrowband-IoT (NB-IoT). Operation in the unlicensed spectrum may include dual connectivity (DC) operation and the standalone LIE system in the unlicensed spectrum, according to which LTE-based technology solely operates in unlicensed spectrum without the use of an ‘‘anchor” in the licensed spectrum, called MulteFire. Further enhanced operation of LTE systems in the licensed as well as unlicensed spectrum is expected in future releases and 5G systems. Such enhanced operations can include techniques for sidelink resource allocation and UE processing behaviors for NR sidelink V2X communications. [0032] An NG system architecture can include the RAN 1 10 and a 5G network core (5GC) 120. The NG-RAN 110 can include a plurality of nodes, such as gNBs and NG-eNBs. The core network 120 (e g., a 5G core network or 5GC) can include an access and mobility function (AMF) and/or a user plane function (UPF). The AMF and the UPF can be communicatively coupled to the gNBs and the NG-eNBs via NG interfaces. More specifically, in some aspects, the gNBs and the NG-eNBs can be connected to the AMF by NG-C interfaces, and to the UPF by NG-U interfaces. The gNBs and the NG-eNBs can be coupled to each other via Xn interfaces.

[0033] In some aspects, the NG system architecture can use reference points between various nodes as provided by 3GPP Technical Specification (TS) 23.501 (e.g., V15.4.0, 2018-12). In some aspects, each of the gNBs and the NG- eNBs can be implemented as a base station, a mobile edge server, a small cell, a home eNB, and so forth. In some aspects, a gNB can be a master node (MN) and NG-eNB can be a secondary node (SN) in a 5G architecture. [0034] FIG. IB illustrates a non-roaming 5G system architecture in accordance with some aspects. In particular, FIG. IB illustrates a 5G system architecture 140B in a reference point representation. More specifically, UE 102 can be in communication with RAN 110 as well as one or more other 5GC netwOrk entities. The 5G system architecture 140B includes a plurality of network functions (NFs), such as an AMF 132, session management function (SMF) 136, policy control function (PCF) 148, application function (AF) 150, UPF 134, network slice selection function (NSSF) 142, authentication server function (AUSF) 144, and unified data management (UDM)/home subscriber server (HSS) 146.

[0035] The UPF 134 can provide a connection to a data network (DN)

152, which can include, for example, operator services, Internet access, or third- party services. The AMF 132 can be used to manage access control and mobility and can also include network slice selection functionality. The AMF 132 may provide UE-based authentication, authorization, mobility management, etc., and may be independent of the access technologies. The SMF 136 can be configured to set up and manage various sessions according to network policy. The SMF 136 may thus be responsible for session management and allocation of IP addresses to UEs. The SMF 136 may also select and control the UPF 134 for data transfer. The SMF 136 may be associated with a single session of a UE 101 or multiple sessions of the UE 101. This is to say that the LJE 101 may have multiple 5G sessions. Different SMFs may be allocated to each session. The use of different SMFs may permit each session to be individually managed. As a consequence, the functionalities of each session may be independent of each other.

[0036] The UPF 134 can be deployed in one or more configurations according to the desired service type and may be connected with a data network. The PCF 148 can be configured to provide a policy framework using network slicing, mobility management, and roaming (similar to PCRF in a 4G communication system). The UDM can be configured to store subscriber profiles and data (similar to an HSS in a 4G communication system).

[0037] The AF 150 may provide information on the packet flow to the

PCF 148 responsible for policy control to support a desired QoS. The PCF 148 may set mobility and session management policies for the UE 101. To this end, the PCF 148 may use the packet flow information to determine the appropriate policies for proper operation of the AMF 132 and SMF 136. The AUSF 144 may store data for UE authentication.

[0038] In some aspects, the 5G system architecture 140B includes an IP multimedia subsystem (IMS) 168B as well as a plurality of IP multimedia core network subsystem entities, such as call session control functions (CSCFs).

More specifically, the IMS 168B includes a CSCF, which can act as a proxy C8CF (P-CSCF) 162BE, a serving CSCF (S-CSCF) 164B, an emergency CSCF (E-CSCF) (not illustrated in FIG. IB), or interrogating CSCF (I-CSCF) I66B. The P-CSCF 162B can be configured to be the first contact point for the UF. 102 within the IM subsystem (IMS) 168B. The S-CSCF 164B can be configured to handle the session states in the network, and the E-CSCF can be configured to handle certain aspects of emergency sessions such as routing an emergency request to the correct emergency center or PSAP. The I-CSCF I66B can be configured to function as the contact point, within an operator's network for all IMS connections destined to a subscriber of that network operator, or a roaming subscriber currently located within that network operator's sendee area. In some aspects, the I-CSCF 166B can be connected to another IP multimedia network 170E, e.g. an IMS operated by a different network operator.

[0039] In some aspects, the UDM/HSS 146 can be coupled to an application server 160E, which can include a telephony application server (TAS) or another application server (AS). The AS 160B can be coupled to the IMS 168B via the S-CSCF 164B or the I-CSCF 166B.

[0040] A reference point representation shows that interaction can exist between corresponding NF services. For example, FIG. IB illustrates the following reference points: N1 (between the UE 102 and the AMF 132), N2 (between the RAN 110 and the AMF 132), N3 (between the RAN 110 and the UPF 134), N4 (between the SMF 136 and the UPF 134), N5 (between the PCF 148 and the AF 150, not shown), N6 (between the UPF 134 and the DN 152),

N7 (between the SMF 136 and the PCF 148, not shown), N8 (between the UDM 146 and the AMF 132, not shown), N9 (between two IJPFs 134, not shown),

N10 (between the UDM 146 and the SMF 136, not shown), Ni 1 (between the AMF 132 and the SMF 136, not shown), N12 (between the AU8F 144 and the AMF 132, not shown), N13 (between the AUSF 144 and the UDM 146, not shown), N 14 (between two AMFs 132, not shown), N 15 (between the PCF 148 and the AMF 132 in case of a non-roaming scenario, or between the PCF 148 and a visited network and AMF 132 in case of a roaming scenario, not shown ), N16 (between two SMFs, not shown), and N22 (between AMF 132 and NSSF 142, not shown). Other reference point representations not shown in FIG. IB can also be used.

[0041] FIG. IC illustrates a 5G system architecture HOC and a service- based representation. In addition to the network entities illustrated in FIG. IB, system architecture HOC can also include a network exposure function (NET) 154 and a network repository' function (NRF) 156. In some aspects, 5G system architectures can be service-based and interaction between network functions can be represented by corresponding point-to-point reference points Ni or as service-based interfaces.

[0042] In some aspects, as illustrated in FIG. 1 C, service-based representations can be used to represent network functions within the control plane that enable other authorized network functions to access their services. In this regard, 5G system architecture HOC can include the following service- based interfaces: Namf 158H (a service-based interface exhibited by the AMF 132), Nsmf 1581 (a service-based interface exhibited by the SMF 136), Nnef 158B (a service-based interface exhibited by the NEF 154), Npcf 158D (a service-based interface exhibited by the PCF 148), aNudm 158E (a service- based interface exhibited by the UDM 146), Naf 158F (a service-based interface exhibited by the AF 150), Nnrf 158C (a service-based interface exhibited by the NRF 156), Nnssf 158A (a service-based interface exhibited by the NSSF 142), Nausf 158G (a service-based interface exhibited by the AUSF 144). Other service-based interfaces (e.g., Nudr, N5g-eir, and Nudsf) not shown in FIG. 1C can also be used.

[0043] NR-V2X architectures may support high-reliability low latency sidelink communications with a variety of traffic patterns, including periodic and aperiodic communications with random packet arrival time and size.

Techniques disclosed herein can be used for supporting high reliability in distributed communication systems with dynamic topologies, including sidelink NR V2X communication systems.

[0044] FIG. 2 illustrates a block diagram of a communication device in accordance with some embodiments. The communication device 200 may be a UE such as a specialized computer, a. personal or laptop computer (PC), a. tablet PC, or a smart phone, dedicated network equipment such as an eNB, a server running software to configure the server to operate as a network device, a virtual device, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine. For example, the communication device 200 may be implemented as one or more of the devices shown in FIGS. 1A-1C. Note that communications described herein may be encoded before transmission by the transmitting entity (e.g., UE, gNB) for reception by the receiving entity (e.g., gNB, UE) and decoded after reception by the receiving entity,

[0045] Examples, as described herein, may include, or may operate on, logic or a number of components, modules, or mechanisms. Modules and components are tangible entities (e.g., hardware) capable of performing specified operations and may be configured or arranged in a certain manner. In an example, circuits may be arranged (e.g., internally or with respect to external entities such as other circuits) in a specified manner as a module. In an example, the whole or part of one or more computer systems (e.g., a standalone, client or server computer system) or one or more hardware processors may be configured by firmware or software (e.g., instructions, an application portion, or an application) as a module that operates to perform specified operations. In an example, the software may reside on a machine readable medium, in an example, the software, when executed by the underlying hardware of the module, causes the hardware to perform the specified operations.

[0046] Accordingly, the term “module” (and “component”) is understood to encompass a tangible entity, be that an entity that is physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., transitorily) configured (e.g., programmed) to operate in a specified manner or to perform part or all of any operation described herein. Considering examples in which modules are temporarily configured, each of the modules need not be instantiated at any one moment in time. For example, where the modules comprise a general-purpose hardware processor configured using software, the general-purpose hardware processor may be configured as respective different modules at different times. Software may accordingly configure a hardware processor, for example, to constitute a particular module at one instance of time and to constitute a different module at a different instance of time.

[0047] The communication device 200 may include a hardware processor (or equivalently processing circuitry) 202 (e.g., a central processing unit. (CPU), a GPU, a hardware processor core, or any combination thereof), a main memory 204 and a static memory' 206, some or all of which may communicate with each other via an interlink (e.g., bus) 208. Hie main memory 204 may contain any or all of removable storage and non-removable storage, volatile memory or non-volatile memory. The communication device 200 may further include a display unit 210 such as a video display, an alphanumeric input device 212 (e.g., a keyboard), and a user interface (UI) navigation device 214 (e.g., a mouse). In an example, the display unit 210, input device 212 and UI navigation device 214 may be a touch screen display. The communication device 200 may additionally include a storage device (e.g., drive unit) 216, a signal generation device 218 (e.g., a speaker), a network interface device 220, and one or more sensors, such as a global positioning system (GPS) sensor, compass, accelerometer, or other sensor. The communication device 200 may further include an output controller, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (III), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).

[0048] The storage device 216 may include a n on-transitory machine readable medium 222 (hereinafter simply referred to as machine readable medium) on which is stored one or more sets of data structures or instructions 224 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The instructions 224 may also reside, completely or at least partially, within the main memory' 204, within static memory 206, and/or within the hardware processor 202 during execution thereof by the communication device 200. While the machine readable medium 222 is illustrated as a single medium, the term "machine readable medium" may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instructions 224.

[0049] The term “machine readable medium” may include any medium that is capable of storing, encoding, or carrying instructions for execution by the communication device 200 and that cause the communication device 200 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions. Non-limiting machine readable medium examples may include solid-state memories, and optical and magnetic media. Specific examples of machine readable media may include: non-volatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory' devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; Radio access Memory (RAM); and CD-ROM: and DVD-ROM: disks.

[0050] The instructions 224 may further be transmitted or received over a communications network using a transmission medium 226 via the network interface device 220 utilizing any one of a number of wireless local area network (WLAN) transfer protocols (e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.). Example communication networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), mobile telephone networks (e.g., cellular networks), Plain Old Telephone (POTS) networks, and wireless data networks. Communications over the networks may include one or more different protocols, such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards known as Wi-Fi, IEEE 802.16 family of standards known as WiMax, IEEE 802.15.4 family of standards, a Long Term Evolution (LTE) family of standards, a Universal Mobile Telecommunications System (UMTS) family of standards, peer-to-peer (P2P) networks, a next generation (NG)/5^th generation (5G) standards among others. In an example, the network interface device 220 may include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or more antennas to connect to the transmission medium 226.

[0051] Note that the term “circuitry” as used herein refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and/or memory' (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), digital signal processors (DSPs), etc., that are configured to provide the described functionality. In some embodiments, the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality. The term “circuitry'” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry' out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.

[0052] The term “processor circuitry'” or “processor” as used herein thus refers to, is part of, or includes circuitry' capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, and/or transferring digital data. The term “processor circuitry” or “processor” may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single- or multi-core processor, and/or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, and/or functional processes.

[0053] As above, 5G networks extend beyond the traditional mobile broadband sendees to provide various new services such as internet of things (loT), industrial control, autonomous driving, mission critical communications, etc. that may have ultra-low latency, ultra-high reliability, and high data capacity requirements due to safety and performance concerns. Edge computing as a feature has been added in the 5G core (5GC) system architecture to support such sendees by hosting some applications closer in the local data network in order to reduce the end-to-end latency and the load on the transport network. FIG. 3 illustrates a 5G edge computing network in accordance with some embodiments, [0054] FIG. 4 illustrates P2P edge computing management deployment in accordance with some embodiments. In the deployment shown in FIG. 4, edge computing in 3 GPP networks involves communication among a 3 GPP management system, a non-3GPP management system, including an edge computing management system, and ETSI network function virtualization (NFV) management and orchestration (MANO).

[0055] The deployment of edge computing in 3GPP networks uses cooperation with other Standards Development Organizations (SDOs), as the application function (AF) and application server (AS) are not 3GPP defined nodes. The deployment of network functions in 3GPP networks and non-3GPP networks to support edge computing involves communication between 3 GPP management system and non-3GPP management systems.

[0056] In the example of FIG. 4, the 3 GPP management system can initiate the edge computing deployment by requesting the edge computing management system to deploy the local data network, and the Network Functions Virtualization Qrchestrator (NFVO) to connect the UPF and local data network with the quality of sendee (QoS) for N6 requirements for the connection (e.g. virtual link) between the UPF and local data network. The edge computing management system can initiate the edge computing deployment by requesting the 3 GPP management system to deploy the UPF and NFVO to connect the UPF and local data network with the QoS requirements for the connection between UPF and local data network.

[0057] FIG. 5 shows an architecture to enable the deploy ment of edge applications. In the architecture, the Application Client is an application resident in a LIE performing client function(s), and the Edge Application Server (EAS) is an application server resident in the Edge Data Network that is the local data network, performing server functions. The Application Client connects to the Edge Application Server to avail itself of (or obtain ) the services of the application with the benefits of Edge Computing.

[0058] FIG. 5 shows an application architecture for enabling Edge

Applications. The Edge Data Network is a local Data Network. Edge Application Server(s) and the Edge Enabler Server (EES) are contained within the EDN. The Edge Configuration Server (ECS) provides configurations related to the EES, including details of the Edge Data Network hosting the EES. The UE contains Application C!ient(s) and the Edge Enabler Client. The Edge Application Server(s), the Edge Enabler Server, and the Edge Configuration Server may interact with the 3GPP Core Network.

[0059] The interactions related to enabling Edge Computing, between the Edge Enabler Sewer and the Edge Enabler Client are supported by the EDGE- 1 reference point. The EDGE- 1 reference point supports: Registration and de-registration of the Edge Enabler Client to the Edge Enabler Server; Retrieval and provisioning of configuration information for the UE; and Discovery of Edge Application Servers available in the Edge Data Network. [0060] The interactions related to Edge Enabler Layer, between the Edge

Enabler Server and the 3 GPP Network are supported by the EDGE-2 reference point. The EDGE-2 reference point supports: Access to 3 GPP Network functions and Application Programming Interfaces (APIs) for retrieval of network capability information, e.g., via Service Capability Exposure Function (SCEF) and Network Exposure Function (NEF) APIs, and with the EES acting as a trusted AF in the 5GC. The EDGE-2 reference point reuses 8A2 defined 3GPP reference points, N33, or the interfaces of EPS or 5GS considering different deployment models. [0061] The interactions related to the Edge Enabler Layer, between the

Edge Enabler Server and the Edge Application Servers are supported by the EDGE-3 reference point. The EDGE-3 reference point supports: Registration of Edge Application Servers with availability information (e.g., time constraints, location constraints); De-registration of Edge Application Servers from the Edge Enabler Server; and Providing access to network capability information (e.g., location information). The following cardinality rules apply for EDGE-3 (Between EAS and EES): a) One EAS may communicate with only one EES; b) One EES may communicate with one or more EAS(s) concurrently.

[0062] The interactions related to the Edge Enabler Layer, between the Edge Data Network Configuration Seryer and the Edge Enabler Client are supported by the EDGE-4 reference point. The EDGE-4 reference point, supports: Provisioning of Edge Data Network configuration information to the Edge Enabler Client in the UE.

[0063] The interactions between the Application Client(s) and the Edge Enabler Client in the UE are supported by the EDGE-5 reference point. The EDGE-5 reference point supports: Obtaining information about Edge Application Servers that the Application Client uses to connect; Notifications about events related to the eonneetion between Application Clients and their corresponding Edge Application Seryers, such as: when an Application Client needs to reconnect to a different. Edge Application Server; Providing Application Client information (such as its profile) to be used for various tasks such as, identifying the appropriate Edge Application Server instance to connect to; and Provide the identity of the desired Edge Application Server to the Edge Enabler Client to enable it to use that identity as a filter when requesting information about Edge Application Servers.

[0064] The interactions related to the Edge Enabler Layer, between the

Edge Data Network Configuration Server and the Edge Enabler Server are supported by the EDGE-6 reference point. The EDGE-6 reference point supports: Registration of Edge Enabler Server information to the Edge Enabler Network Configuration Server,

[0065] The interactions related to the Edge Enabler Layer, between the

Edge Enabler Server and the 3 GPP Network are supported by the EDGE-2 (or EDGE-7) reference point. The EDGE-7reference point supports: Access to 3 GPP Network functions and APIs for retrieval of network capability information, e.g., via SCEF and NET APIs, and with the EAS acting as a trusted AF in the 5GC. The EDGE-7 reference point reuses SA2 defined 3GPP reference points, N6, or interfaces of the EPS or 5GS considering different deployment models.

[0066] The interactions between the Edge Data Network Configuration

Server and the 3GPP Network are supported by the EDGE-8 reference point.

The EDGE-8 reference point supports: Edge Data Network configurations provisioning to the 3 GPP network utilizing network exposure services. [0067] The EDGE-9 reference point enables interactions between two

Edge Enabler Servers. The EDGE-9 reference point may be provided between the EES within different EDNs and within the same EDN.

[0068] The Edge Enabler Server (EES) provides supporting functions for

Edge Application Servers and the Edge Enabler Client. Functionalities of the Edge Enabler Server are: a) provisioning of configuration information to the

Edge Enabler Client, enabling exchange of application data traffic with the Edge Application Server; b) supporting the functionalities of the API invoker and API exposing function; c) interacting with the 3 GPP Core Network for accessing the capabilities of network functions either directly (e.g., via PCF) or indirectly (e.g., via SCEF/NEF/SCEF+NEF); and d) support the functionalities of application context transfer.

[0069] The following cardinality rules apply for the Edge Enabler

Server: a) One or more EES(s) may be located in an EDN; b) One or more EES(s) may be located in an EDN per Edge Computing Service Provider

(ECSP).

[0070] The EAS is the application server resident in the Edge Data

Network, performing the server functions. The Application Client connects to the Edge Application Server in order to take advantage of the sendees of the application with the benefits of Edge Computing. It is possible that the server functions of an application are available only as the Edge Application Server. However, if the sender functions of the application are available as both an Edge Application Server and an Application Server resident in the cloud, it is possible that the functions of the Edge Application Server and the Application Server are not the same. In addition, if the functions of the Edge Application Server and the Application Server are different, the Application Data Traffic may also be different.

[0071] The Edge Application Server may consume the 3GPP Core Network capabilities in different ways, such as: a) it may invoke 3GPP Core Network function APIs directly, if it is an entity trusted by the 3 GPP Core Network; b) it may invoke 3GPP Core Network capabilities through the Edge Enabler Server; and c) it may invoke the 3GPP Core Network capability through the capability exposure functions (e.g., SCEF or NEF). [0072] The following cardinality rules apply for Edge Application

Servers: a) One or more EASfs) may be located in an EDN. The EAS(s) belonging to the same EAS ID can be provided by multiple ECSP(s) in an EDN. [0073] The Edge Enabler Server ID (EESID) is the Fully Qualified

Domain Name (FQDN) of the Edge Enabler Server and each Edge Enabler Server ID is unique within a PLMN domain.

[0074] The Edge Application Server ID (EASID) identifies a particular application for e.g., SA6Video, SA6Game etc. For example, ail Edge SA6Video Servers share the same Edge Application Server ID. The format for the EAS ID is out of scope of this specification. Table E28.2.4-1 shows Edge Application Server Profile IBs.

Table E28.2.4-1; Edge Application Server Profile

[0075] Edge Application Server Service key performance indicators

(KPIs) provide information about service characteristics provided by the Edge Application Server (see e.g., table E28.2.5-1).

[0076] The Edge Enabler Server profile includes information about the

EES and the services it provides (see e.g., table E28.2.6-I). Table E28.2.6-1: Edge Enabler Server Profile

[0077] The network capability exposure to Edge Application Server(s) depends on the deployment scenarios and the business relationship of the ASP/EC SP with the PLMN operator. The following mechanisms are supported: Direct network capability exposure and/or Network capability exposure via Edge Enabler Server.

[0078] In some implementations, the network capability exposure to

EAS(s) depends on the deployment scenarios and the business relationship of the ASP/EC SP with the PLMN operator. The following mechanisms are supported: Direct network capability exposure and/or Network capability exposure via Edge Enabler Server. In some implementations, the charging functionalities with different deployment options depending on business relationships among Edge Application Service Provider, Edge Computing Service Provider, and SFC service provider are out of scope of the present disclosure (SA5 study). [0079] FIG. 6 illustrates an inter-EDN in accordance with some embodiments. FIG. 7 illustrates an intra-EDN in accordance with some embodiments. The EDGE-9 reference point enables interactions between two Edge Enabler Servers. The EDGE-9 reference point may be provided between EES within different EDNs as shown by Figure E3 and within the same EDN as shown by FIG. 7.

[0080] FIG. 8 illustrates service provider relationship in an edge computing network deployment in accordance with some embodiments. FIG. 8 show^?s the roles and relationship of service providers involved in the deployment of edge computing services. The application service provider (ASP) is responsible for the creation of EAS and application clients (AC). The ECSP is responsible for the deployment of EDNs that contain the EAS and EES that provides the configuration information to the EEC, enabling the AC to exchange application data traffic with the EAS. The PL.MN operator is responsible for the deployment of 5G network functions, such as the 5GC and 5G NR.

[0081] The end user is the consumer of the applications/services provided by the ASP and can have an ASP service agreement with a single application service provider or multiple application service providers. The end user has a PLAIN subscription arrangement with the PLAIN operator. The UE used by the end user is allowed to be registered on the PLMN operator network. The ASP consumes the edge services (e.g., infrastructure, platform, etc.) provided by the ECSP and can have an ECSP service agreement(s) with a single ECSP or multiple ECSPs. The ECSP may be a mobile network operator or a 3rd party service provider offering Edge Computing services. A single PLAIN operator can have the PLAIN operator service agreement with a single computing service provider or multiple edge computing sendee providers. A single ECSP can have PLMN operator service agreement with a single PLMN operator or multiple PLMN operators that provide edge computing support. The ECSP and the PLAIN operator can be part of the same organization or different organizations.

[0082] As above, the 3 GPP management system manages the 3 GPP defined network functions (e.g. UPF, PCF, EES, ECS, EAS, ...), and services.

To support the edge computing management, the 3GPP management system includes both a PLMN management system that is responsible for the orchestration and management of the mobile networks and an ECSP management system that is responsible for the orchestration and management of the EDN. The ECSP and the PLMN operator can be part of the same organization

[0083] The mechanisms to deploy the edge applications servers, edge enable servers, edge configuration servers, and the 5G mobile networks to support edge computing for 3GPP TR 28.814 are disclosed herein. The embodiments herein also include business level and specification level use cases and requirements, including various deployments. The deployments include: the EAS on the EDN by the PLMN/EC service provider; the EAS on the EDN by the ECSP: the EES on the EDN by the PLMN/EC service provider; the EES on the EDN by the ECSP; the ECS by the PLMN/EC service provider; and the ECS by the ECSP, where the PLMN/EC sendee provider indicates that the operator owns both the PLMN and EDN.

[0084] 5 Use cases

[0085] 5.1 Business level use cases

[0086] 5.1.x The deployment of edge application server(s)

[0087] 5.1.X.1 The deployment of EAS on EDN by PLMN/EC service provider

[0088] 5.1.X.1.1 Goal

[0089] A goal is to enable the ASP to install or terminate one or more

EAS on the EDN. It is assumed that the both the PLMN networks and EDN are owned by the same organization, called the PLMN/EC service provider.

[0090] 5.1.X.1.2 Pre-conditions

[0091] The ASP has a service agreement with the PLMN/EC sendee provider.

[0092] The PLMN/EC service provider has deployed EDN(s).

[0093] 5.1.X.L3 Description

[0094] 5.1.X.1.3.1 EAS installation

[0095] 1. The ASP requests the PLMN/EC service provider to install one or more EAS with deployment requirements.

[0096] 2. The PLMN/EC service provider selects the EDN to host, the EAS, based on the deployment requirements. [0097] 3. The PLMN/EC service provider installs the EAS at the

EDN that meets the deployment requirements.

[0098] 4. The PLMN/EC service provider notifies the ASP that the

EAS has been installed successfully.

[0099] 5. Lx, 1.3.2 EAS termination

[00100] 1. The ASP requests the PLMN/EC service provider to terminate one or more EAS with the EAS identifier(s).

[00101] 2. The PLMN/EC service provider terminates the EAS based on the identifier at the EDN.

[00102] 3. The PLMN/EC service provider notifies the ASP that the

EAS has been terminated successfully.

[00103] 5.1.x.2 The deployment of EAS on EDN by ECSP

[00104] 5.1.X.2.1 Goal

[00105] The goal is to enable the ASP to install or terminate one or more EAS on EDN in the ECSP (Edge Computing Sendee Provider).

[00106] 5.1.X.2.2 Pre-conditions

[00107] The ASP has a sendee agreement with the ECSP.

[00108] The ECSP provider has deployed EDN(s)

[00109] S.l.x.2.3 Description

[00110] 5.1.X.2.3.1 EAS installation

[00111] 1. The ASP requests the ECSP to install one or more EAS with deployment requirements.

[00112] 2. The ECSP selects the EDN to host the EAS, based on the deployment requirements.

[00113] 3. The ECSP installs EAS at the selected edge data network,

[00114] 4. The ECSP notifies the ASP that the EAS has been install successfully.

[00115] 5.1.X.2.3.2 EAS termination

[00116] 1. The ASP requests the EC SP to terminate one or more

EAS with EAS identifier(s).

[00117] 2. The ECSP terminates the EAS based on the identifier at the EDN.

[00118] 3. The ECSP notifies the ASP that the EAS has been terminated successfully. [00119] S.l.y The deployment of edge enabler server(s)

[00120] 5.1.y.l The deployment of EES on EDN by PLMN/EC service provider

[00121] S.l.y, 1.1 Goal [00122] The goal is to enable the installation and termination of one or more EES on the EDN. It is assumed that the edge computing service provider and the PLMN operator can be part of the same organization, called the PLMN/EC sendee provider.

[00123] S.l.y.1.2 Pre-conditions [00124] The PLMN/EC service provider is in operation.

[00125] S.l.y.1.3 Description

[00126] S.l.y, 1.3.1 EES installation

[00127] 1. The PLMN/EC sendee provider received a request to install one or more EES with deployment requirements. [00128] 2. The PLMN/EC sendee provider selects EDN to host the

EES,

[00129] 3. The PLMN/EC sendee provider installs the EES.

[00130] 4, The PLMN/EC sendee provider sends a notification to indicate that the EES has been installed successfully. [00131] S.l.y.1.3.2 EES termination

[00132] 1. The PLMN/EC service provider received a request to terminate one or more EES with the EES identifier.

[00133] 2. The PLMN/EC service provider terminates the EES, based on the EES identifier. [00134] 3. The PLMN/EC service provider sends a notification to indicate that the EES has been terminated successfully.

[00135] 5.1.y,2 The deployment of EES on the EDN by ECSP

[00136] S.l.y.2.1 Goaf

[00137] The goal is to enable the installation and termination of one or more EES on the EDN in the ECSP.

[00138] S.l.y, 2.2 Pre-conditions

[00139] The ECSP is in operation.

[00140] S.l.y.2.3 Description

[00141] S.l.y, 2.3.1 EES installation [00142] 1. The ECSP received a request to install one or more EES with deployment requirements.

[00143] 2. The ECSP selects the EDN to host the EES.

[00144] 3. The ECSP installs EES at the selected edge data network.

[00145] 4. The ECSP sends a notification to indicate that the EES has been installed successfully.

[00146] 5.1.V.2.3.2 EES termination

[00147] 1. The ECSP received a request to terminate one or more

EES with the EES identifier.

[00148] 2. The ECSP terminates the EES, based on the EES identifier.

[00149] 3. The ECSP sends a notification to indicate that, the EES has been terminated successfully.

[00150] 5.1.Z The deployment of edge configuration server(s)

[00151] S.Lz.l The deployment of ECS by PLMN operator

[00152] 5.1.Z.L1 Goal

[00153] The goal is to enable the installation and termination of one or more ECS in the PLMN operator.

[00154] S.Lz.l.2 Pre-conditions

[00155] The PLMN operator is in operation.

[00156] S.l.z.1.3 Description

[00157] S.Lz.l.3.1 ECS installation

[00158] 1. The PLMN operator receives a request to install one or more ECS.

[00159] 2. The PLMN operator installs the ECS.

[00160] 3. The PLMN operator sends a notification to indicate that the ECS has been installed successfully.

[00161] 5.1.Z.1.3.2 ECS termination

[00162] 1. The PLMN operator receives a request to termination one or more ECS with the ECS identifier.

[00163] 2. The PLMN operator terminates the ECS based on the ECS identifier.

[00164] 3. The PLMN operator sends a notification to indicate that the ECS has been terminated successfully. [00165] 5.1.Z.2 The deployment of ECS by ECSP

[00166] S.l.z.2.1 Goal

[00167] The goal is to enable the installation and termination of one or more ECS in the ECSP.

[00168] S.l.z.2.2 Pre-conditions

[00169] The ECSP is in operation.

[00170] 5.1.Z.2.3 Description

[00171] S.l.z.2.3.1 ECS installation

[00172] I . The ECSP receives a request to install one or more

ECS(s).

[00173] 2. The ECSP selects the EDN to the ECS.

[00174] 3. The ECSP installs the ECS.

[00175] 3. The ECSP sends a notification to indicate that the ECS has been installed successfully.

[00176] 5.1.Z.2.3.2 ECS termination

[00177] 1. The EC8P receives a request to terminate one or more

ECS(s) with the ECS identifiers(s).

[00178] 2, The EC8P terminate the ECS(s) based on the ECS identifiers(s).

[00179] 3. The ECSP sends a notification to indicate that the ECS has been terminated successfully

[00180] 5.2 Specification level nse cases

[00181] 5.2.x The deployment of edge application server(s)

[00182] 5.2.x.1 The deployment of EAS on EDN by PLMN/EC service provider

[00183] 5.2.X.1.1 Goal

[00184] The goal is to enable the ASP to install or terminate the EAS on the EDN.

[00185] 5.2.X.1.2 Pre-conditions [00186] The ASP has a service agreement with the PLMN/EC sendee provider. [00187] The EES(s) have been deployed in the EDN. [00188] The 5GC networks have been deployed. [00189] 5.2.x.1.3 Description [00190] 5.2.X.2.3.1 EAS installation

[00191] 1. A consumer consumes the management service of

PLMN/EC management system to install the EAS with application packages (e.g., VNF, VNFD, etc.) and deployment requirements (e.g., virtualized resources requirements (e.g., compute, memory, etc.), QoS requirements (e.g., latency, bandwidth), and geographical service areas, etc.)).

[00192] 2. The PLMN/EC management system determines in which

EDN the EAS will be deployed, based on the deployment requirements. For example, the selection of EDN in which the EAS will be installed may be determined by the QoS and geographical service areas requirements.

[00193] 3. The PLMN/EC management system consumes the management service of ETSINFV MANO to perform the following operations: [00194] Instantiate the EAS VNF

[00195] Connect the EAS to the EES. [00196] Connect the EAS to the 5GC network functions for sending the information over N6 and Edge 7-interfaces

[00197] 4. The PLMN/EC management system notifies the ASP management system that the EAS has been installed successfully.

[00198] 5.2.X.2.3.1 EAS termination [00199] 1. A consumer consumes the management service of

PLMN/EC management system to terminate the EAS with the EAS identifier. [00200] 2. The PLMN/EC management system terminates the EAS

VNF based on the EAS identifier, and disconnects the EAS from the 5GC network functions. [00201] 3. The PLMN/EC management system notifies the ASP management system that the EAS has been terminated successfully.

[00202] 5.2.X.2 The deployment of EAS on EDN by ECSP

[00203] 5.2.X.2.1 Goaf

[00204] The goal is to enable the ASP to install or terminate the EAS on EDN in the ECSP.

[00205] 5.2.x, 2.2 Pre-conditions

[00206] The ASP has a sendee agreement with the ECSP.

[00207] The EES(s) have been deployed in the EDN.

[00208] The 5GC networks have been deployed. [00209] 5.2.X.2.3 Description

[00210] 5.2.X.2.3.1 EAS installation

[00211] 1. A consumer consumes the management service of ECSP management system to install the EAS with application packages (e.g., VNF, VNFD, etc) and deployment requirements (e.g,, virtualized resources requirements (e.g., compute, memory, ...), QoS requirements (e.g., latency, bandwidth), and geographical service areas, ... etc)).

[00212] 2. The ECSP management system determines in which EDN the EAS will be deployed, based on the deployment requirements. For example, the selection of EDN in which the EA S will be installed may be determined by the QoS and geographical sendee areas requirements.

[00213] 3. The ECSP management system consumes the management service of ETSINFV MANO to perform the following operations: [00214] Instantiate the EAS VNF. [00215] Connect the EAS to the EES.

[00216] Connect the EAS to the 5GC network functions for sending the information over N 6 and Edge 7-interfaces

[00217] 4, The ECSP management system notifies the ASP management system that the EAS has been installed successfully [00218] 5.2.X.2.3.2 EAS mstallatio

[00219] 1. A consumer consumes the management service of ECSP management system to terminate the EAS with the EAS identifier.

[00220] 2. The ECSP management system terminates the EAS VNF based on the EAS identifier, and disconnect the EAS from the 5GC network functions,

[00221] 3. The ECSP management system notifies the ASP management system that the EAS has been terminated successfully.

[00222] 5.2.x The deployment of edge enabler server(s)

[00223] 5.2.y The deployment of edge enabler server(s) [00224] 5.2.y.l The deployment of EES on EDN by PLMN/EC service

[00225] 5.2.V.1.1 Goaf

[00226] The goal is to enable the installation and termination of one or more EES on the EDN. [00227] 5.2.V.1.2 Pre-conditions

[00228] The PLMN/EC management system in the PLMN/EC service provider is in operation.

[00229] The 5GC networks have been deployed. [00230] 5.2.y,1.3 Description

[00231] 5.2.y.1.3.1 EES installation

[00232] 1. A consumer consumes the management service of

PLMN/EC management system to install the EES with EES packages (e.g., VNF, VNF package, ,,, etc) and deployment requirements (e.g., virtualized resources requirements (e.g., compute, memory, ...).

[00233] 2. The PLMN/EC management system determines the EDN where the EES will be installed.

[00234] 3. The PLMN/EC management system performs the following operations to install the EES: [00235] Instantiate the EES VNF.

[00236] Connect the EES to the 5GC network functions for sending the information over the edge-2 interfaces.

[00237] 4. The PLMN/EC management system sends a notification to indicate that the EES has been installed successfully. [00238] 5.2.Y.1.3.2 EES termination

[00239] 1. A consumer consumes the management service of

PLMN/EC management system to terminate the EES with the EES identifier. [00240] 2. The PLMN/EC management system terminates the EES

VNF based on the EES identifier, and disconnects the EES from the 5GC network functions.

[00241] 3. The PLMN/EC management system sends a notification to indicate that the EES has been terminated successfully.

[00242] 5.2.y.2 The deployment of EES on EDN by ECSP

[00243] 5.2.y.2.1 Goal [00244] The goal is to enable the installation and termination of one or more EES on the EDN in the ECSP.

[00245] 5.2.V.2.2 Pre-conditions

[00246] The ECSP management system in the ECSP is in operation. [00247] The EES(s) have been deployed in the EDN. [00248] The 5GC networks have been deployed.

[00249] 5.2.y.2.3 Description

[00250] 5.2.y.2.3.1 EES installation

[00251] 1. A consumer consumes the management service of ECSP management system to install the EES with application packages (e.g., VNF, VNF package, etc) and deployment requirements.

[00252] 2. The ECSP management system determines the EDN in which

EDN the EES will be deployed.

[00253] 3. The ECSP management system performs the following operations to install the EES:

[00254] Instantiate the EES VNE.

[00255] Connect the EES to the 5GC network functions for sending the information over the edge-2 interfaces.

[00256] 4. The ECSP management system sends a notification to indicate that the EES has been installed successfully.

[00257] 5.2.y.2.3.2 EES termination

[00258] 1. A consumer consumes the management sendee of ECSP management system to terminate the EES with the EES identifier.

[00259] 2. The ECSP management system determines the EDN in which EDN the EES will be deployed.

[00260] 3. The ECSP management system terminates the EES VNF based on the EES identifier, and disconnects the EES from the 5GC network functions [00261] 4. The ECSP management system sends a notification to indicate that the EES has been terminated successfully [00262] 5.2.z The deployment of edge configuration server(s)

[00263] 5.2.Z.1 The deployment of ECS by PLMN operator

[00264] 5.2.Z.1.1 Goal

[00265] The goal is to enable the installation and termination of one or more ECS in PLMN operator. [00266] 5.2.Z.1.2 Pre-conditions

[00267] The PLAIN management system in PLAIN operator is in operation.

[00268] The 5GC networks have been deployed.

[00269] 5.2.Z.1.3 Description S.l.z.1.3 ECS installation

[00271] 1. A consumer consumes the management service of PLMN management system to install the ECS with application packages (e.g., VNF, VNF package, ,„ etc).

[00272] 2, The PLMN management system performs the following operations to install the ECS:

[00273] Instantiate the ECS VNF.

[00274] Connect the ECS to the 5GC network functions for sending the information over the edge-8 interfaces.

[00275] 3. The PLMN management system sends a notification to indicate that the ECS has been installed successfully.

[00276] 5.1.Z.1.3 ECS termination

[00277] I . A consumer consumes the management service of PLAIN management system to terminate the ECS with the ECS identifier.

[00278] 2. The PLMN management system terminates the ECS VNF based on the ECS identifier, and disconnect the ECS from the 5GC network functions.

[00279] 3. The PLMN management system sends a notification to indicate that the ECS has been terminated successfully .

[00280] 5.2.Z.2 The deployment of ECS by ECSP

[00281] 5.2.Z.2.1 Goal

[00282] The goal is to enable the installation and termination of one or more ECS in the ECSP.

[00283] 5.2.Z.2.2 Pre-conditions

[00284] The ECSP management system in the ECSP is in operation. [00285] The 5GC networks have been deployed.

[00286] 5.2.Z.2.3 Description

[00287] 5.1.Z.2.3.1 ECS installation

[00288] 1. A consumer consumes the management service of EC SP management system to install the ECS with application packages (e.g., VNF, VNF package, ,„ etc).

[00289] 2. The ECSP management system selects the EDN to install the ECS. [00290] 3. The ECSP management system performs the following operations to install the EES:

[00291] Instantiate the ECS VNR

[00292] Connect the ECS to the 5GC network functions for sending the information over the Edge-8 interfaces,

[00293] 4, The ECSP management system sends a notification to indicate that the ECS has been deployed successfully.

[00294] S.l.z.2.3.2 ECS termination

[00295] I . A consumer consumes the management service of ECSP management system to terminate the ECS with the ECS identifier.

[00296] 2. The ECSP management system terminates the ECS VNF based on the ECS identifier, and disconnect the ECS from the 5GC network functions.

[00297] 3. The ECSP management system sends a notification to indicate that the ECS has been deployed successfully [00298] 6 Potential requirements

[00299] 6.1 Business level requirements

[00300] 6.1.x Edge application server

[00301] REQ-EAS-DEPLOY-CON-a The management system of the PLMN/EC sendee provider should allow a consumer to request the installation of one or more EAS on the EDN with the deployment requirements.

[00302] REQ-EAS-DEPLOY-CON-b The management system of the PLMN/EC sendee provider should allow' a consumer to request, the termination of one or more EAS on the EDN with the EAS identifier. [00303] REQ-EAS-DEPLOY-CON-c The management system of the

PLMN/EC sendee provider should be able to send the notification indicating the status of EA S installation and termination,

[00304] REQ-EAS-DEPLOY-CON-d The management system of ECSP should allow a consumer to request the installation of one or more EAS on the EDN with the deployment requirements.

[00305] REQ-EAS-DEPLOY-CON-e The management system of ECSP should allow a consumer to request the installation and termination of one or more EAS on the EDN with the EAS identifier. [00306] REQ-EAS-DEPLOY-CON-f The management system of ECSP should be able to send the notification indicating the status of EAS installation and termination.

[00307] 6.1.y Edge enabler server [00308] REQ-EES-DEPLOY-CON-a The management system of the

PLMN/EC service provider should allow a consumer to request the installation of the EES with deployment requirements.

[00309] REQ-EES-DEPLOY-CON-b The management system of the PLMN/EC service provider should allow a consumer to request the termination of the EES with the EES identifier.

[00310] REQ-EES-DEPLOY-CON-c The management system of the PLMN/EC service provider should be able to send the notification indicating the status of EES installation and termination.

[00311] REQ-EES-DEPLOY-CON-d The ECSP should allow a consumer to request the installation of the EES on the EDN with deployment requirements.

[00312] REQ-EES-DEPLOY-CON-c The ECSP should allow a consumer to request the termination of the EES on the EDN with the EES identifier. [00313] REQ-EES-DEPLOY-CON-f The ECSP should be able to send the notification indicating the status of EES installation and termination.

[00314] 6.1.Z Edge configuration server

[00315] REQ-ECS-DEPLOY-CON-a The management sy stem of the PLMN operator should allow the PLMN provider to request the installation of the ECS.

[00316] REQ-ECS-DEPLOY-CON-b The management system of the PLMN operator should allow the PLMN provider to request the termination of the ECS with the ECS identifier.

[00317] REQ-ECS-DEPLOY-CON-c The management system of the PLMN operator should be able to send the notification indicating the status of ECS installation and termination.

[00318] REQ-ECS-DEPLOY-CON-d The management system of the

ECSP should allow the PLAIN provider to request the installation of the ECS. [00319] REQ-ECS-DEPLOY-CON-e The management system of the ECSP should allow the PLMN provider to request the termination of the ECS with the ECS identifier.

[00320] REQ-ECS-DEPLOY-CON-f The management system of the ECSP should be able to send the notification indicating the status of ECS installation and termination.

[00321] 6.2 Specification level requirements

[00322] 6o2.x Edge application server

[00323] REQ-EAS-DEPLOY-FUN-a PLMN/EC management system should provide management services to allow consumers to request the installation of EAS with application packages (e.g., VNF, VNFD, ,,, etc) and deployment requirements (e.g., virtualized resources requirements (e.g., compute, memory, ...), QoS requirements (e.g., latency, bandwidth), and geographical sendee areas, ... etc)). [00324] REQ-EAS-DEPLOY-FUN-b PLMN/EC management system should provide management sendees to allow consumers to request the termination of EAS with the EAS identifier.

[00325] REQ-EAS-DEPLQY-FUN-c PLMN/EC management system should be able to instantiate the EAS VNF at the EDN, connect the EAS to the EES, and connect the EAS to the 5GC network functions for sending the information over N6 and edge-7 interfaces.

[00326] REQ-EAS-DEPLOY-FUN-d PLMN/EC management system should be able to terminate the EAS VNF based on the EAS identifier, and disconnect the EAS from the 5GC network functions. [00327] REQ-EAS-DEPLOY-FUN-e PLMN/EC management system should be able to send the notification indicating the status of EAS installation and termination.

[00328] REQ-EAS-DEPLOY-FUN-f ECSP management system should provide management services to allow consumers to request the installation of EAS with application packages (e.g., VNF, VNFD, ,„ etc) and deployment requirements (e.g., virtualized resources requirements (e.g., compute, memory, ...), QoS requirements (e.g., latency, bandwidth), and geographical service areas, ... etc)). [00329] REQ-EAS-DEPLOY-FUN-g ECSP management system should provide management services to allow consumers to request the termination of EAS with the EAS identifier.

[00330] REQ-EAS-DEPLOY-FUN-h ECSP management system should be able to instantiate the EAS VNF at the EDN, connect the EAS to the EES, and connect the EAS to the 5GC network functions for sending the information over N 6 and Edge-7 interfaces,

[00331] REQ-EAS-DEPLOY-FUN-i ECSP management system should be able to terminate the EAS VNF based on the EAS identifier, and disconnect the EAS from the 5GC network functions.

[00332] REQ-EAS-DEPLOY-FUN-j ECSP management system should be able to send the notification indicating the status of EAS installation and termination.

[00333] 6.2.y Edge enabler server [00334] REQ-EES-DEPLOY-FUN-a PLMN/EC management system should provide management sendees to allow consumers to request the installation of EES with EES packages (e.g., VNF, VNF package, ,„ etc) and deployment requirements (e.g,, virtualized resources requirements (e.g,, compute, memory', ...). [00335] REQ-EES-DEPLOY-FUN-b PLMN/EC management system should provide management sendees to allow consumers to request the termination of EES with the EES identifier.

[00336] REQ- E E S- DEPLOY - F UN-c PLMN/EC management system should be able to instantiate the EES VNF at the EDN, and connect the EES to the 5GC network functions for sending the information over edge-2 interfaces. [00337] REQ-EES-DEPLOY-FUN-d PLMN/EC management system should be able to terminate the EES VNF based on the EES identifier, and disconnect the EES to the 5GC network functions.

[00338] REQ-EES-DEPLOY-FUN-e PLMN/EC management system should be able to send the notification indicating the status of EES installation and termination.

[00339] REQ-EES-DEPLOY-FUN-f ECSP management system should provide management services to allow' consumers to request the installation of EES with EES packages (e.g., VNF, VNF package, ,„ etc) and deployment requirements (e.g., virtualized resources requirements (e.g., compute, memory, ...).

[00340] RE Q-E E S-D E P LO Y-FU N-g ECSP management system should provide management sendees to allow consumers to request the termination of EES with the EES identifier

[00341] REQ-EES-DEPLOY-FUN-h EC SP management system should be able to terminate the EES VNF at the EDN, and disconnect the EES to the 5GC network functions for sending the information over the edge-2 interfaces. [00342] REQ-EES-DEPLOY-FUN-i ECSP management system should be able to terminate the EES VNF based on the EES identifier, and disconnect the EES to the 5GC network functions

[00343] RE Q-E E S-D E P LO Y-FU N -j ECSP management system should be able to send the notification indicating the status of EES installation and termination . [00344] 6.2.z Edge configuration server

[00345] REQ-ECS-DEPLOY-FUN-a The PLMN management system should provide management services to allow⁷ consumers to request the installation of ECS with application packages (e.g., VNF, VNF package, etc), [00346] REQ- E C S-D E PLO Y-FU N -b The PLMN management system should provide management sendees to allow consumers to request the termination of ECS with the ECS identifier.

[00347] REQ-ECS-DEPLOY-FUN-c The PLMN management system should be able to instantiate the ECS VNF at the ISDN, and connect, the ECS to the 5GC network functions for sending the information over edge-8 interfaces. [00348] REQ-ECS-DEPLOY-FUN-d The PLMN management system should be able to terminate the ECS VNF baed on the ECS identifier, and disconnect the ECS from the 5GC network functions.

[00349] REQ-ECS-DEPLOY-FUN-e The PLMN management system should be able to send the notification indicating the status of EAS installation and termination.

[00350] REQ-ECS-DEPLOY-FUN-f The ECSP management system should provide management services to allow consumers to request the installation of ECS application packages (e.g., VNF, VNF package, etc). [00351] REQ-ECS-DEPLOY-FUN-g The ECSP management system should provide management sendees to allow consumers to request the termination of ECS with the ECS identifier.

[00352] REQ-ECS-DEPLOY~FUN-h The ECSP management system should be able to instantiate the ECS VNF at the EDN, and connect the ECS to the 5GC network functions for sending the information over edge-8 interfaces. [00353] REQ-ECS-DEPLOY-FUN-i The PLMN management system should he able to terminate the ECS VNF baed on the ECS identifier, and disconnect the ECS from the 5GC network functions. [00354] REQ- E C S-DE PLO Y-FU N -j The ECSP management system should be able to send the notification indicating the status of EAS installation and termination.

[00355] The EAS is an application server resident in the Edge DataNetwork, performing the server functions. This use case pertains to the case when the EAS is to he deployed on the operators EDN being managed by the operator's management system. The lifecycle of EAS (instantiation, termination, scaling, etc) is to be managed and there can be multiple EDNs serving a particular edge location. To deploy a EDN as local data network, the serving location and constituent edge entities (EAS and EES) are defined for each EDN. The ECSP management system is requested to instantiate the entities, as 3GPP netwOrk functions, aiming to server the particular location. The instantiated EES may serve one or multiple EAS.

[00356] Although an embodiment has been described with reference to specific example embodiments, it will he evident that various modifications and changes may be made to these embodiments without departing from the broader scope of the present disclosure. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense. The accompanying drawings that form a part hereof showy by way of illustration, and not of limitation, specific embodiments in which the subject matter may be practiced. The embodiments illustrated are described in sufficient, detail to enable those skilled in the art to practice the teachings disclosed herein. Other embodiments may be utilized and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. This Detailed Description, therefore, is not to be taken in a limiting sense, and the scope of various embodiments is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled.

[00357] The subject matter may be referred to herein, individually and/or collectively, by the term ‘‘embodiment” merely for convenience and without intending to voluntarily limit the scope of this application to any single inventive concept if more than one is in fact disclosed. Thus, although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement calculated to achieve the same purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those of skill in the art upon reviewing the above description. [00358] In this document, the terms "a" or "an" are used, as is common in patent documents, to include one or more than one, independent of any other instances or usages of "at least one" or "one or more." In this document, the term "or" is used to refer to a nonexclusive or, such that "A or B" includes "A but not B," “B but not A," and “A and B," unless otherwise indicated. In this document, the terms "including" and "in which" are used as the plain-English equivalents of the respective terms "comprising" and "wherein." Also, in the following claims, the terms "including" and "comprising" are open-ended, that is, a system, LIE, article, composition, formulation, or process that includes elements in addition to those listed after such a term in a claim are still deemed to fall within the scope of that claim. Moreover, in the following claims, the terms "first," "second," and "third," etc. are used merely as labels, and are not intended to impose numerical requirements on their objects.

[00359] The Abstract of the Disclosure is provided to comply with 37 C.F.R. §1.72(b), requiring an abstract that will allow⁷ the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, it can be seen that various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus, the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment.

Claims

CLAIMS What is claimed is:

1. An apparatus configured to operate as a service provider in a new radio 5 (NR) network, the apparatus comprising: processing circuitry configured to: receive, from an application service provider (ASP), a first request to install an Edge Computing (EC) Network Function (NF) to support EC, the EC NF selected from a set of EC NFs that include an It) Edge Application Server (EAS); or receive, from another entity, a first request to install an Edge Computing (EC) Network Function (NF) to support EC, the EC NF selected from a set of EC NFs that include: an Edge Enabler Server (EES), and Edge Configuration Server (ECS) NF;

15 in response to the first request, install the EC NF and send a first notification to the ASP or other entity to indicate installation of the EC NF; receive, from the ASP or other entity, a second request to terminate the EC NF after installation of the EC NF, the second request 20 comprising an identifier of the EC NF; and in response to the second request, terminate the EC NF and send a second notification to the ASP or other entity to indicate termination of the EC NF; and a memory configured to store the first and second request.

25

2. The apparatus of claim I, wherein the processing circuitry is configured to, in response to the first request select, based on deployment conditions, one of a plurality of Edge Data Networks (EDNs) to host the EC NF.

30 3. The apparatus of claim 2, wherein the deployment conditions comprise

Quality of Service (QoS), geographical service area conditions and virtualized resources to be used.

4. The apparatus of claim 1, wherein the service provider is an Edge Computing Service Provider (ECSP) that comprises an ECSP management system.

5. The apparatus of claim 4, wherein: the first request is a request to install an EAS and the second request is a request to terminate the EAS, in response to reception of the first request, the ECSP management system is configured to: instantiate an EAS virtual network function (VNF), and after instantiation of the EAS VNF: connect the EAS to the EES, and connect the EAS to 5^th generation core (5GC) NFs to send information over N6 and Edge 7-interfaces, and in response to reception of the second request, which has an EAS identifier of the EAS to terminate, the ECSP management system is configured to: terminate the EAS VNF with the EAS identifier, and disconnect the EAS from the 5GC NFs.

6. The apparatus of claim 4, wherein: the first request is a request to install an EES and the second request is a request to terminate the EES, in response to reception of the first request, the ECSP management system is configured to: instantiate an EES virtual network function (VNF), and after instantiation of the EES VNF connect the EES to 5^th generation core (5GC) NFs to send information over N6 and Edge 2- interfaces, and in response to reception of the second request, which has an EES identifier of the EES to terminate, the ECSP management system is configured to: terminate the EES VNF with the EES identifier, and disconnect the EES from the 5GC NFs.

7. The apparatus of claim 4, wherein: the first request is a request to install an ECS and the second request is a request to terminate the ECS, in response to reception of the first request, the EC8P management system is configured to: instantiate an ECS virtual network function (VNF), and after instantiation of the ECS VNF connect the EES to 5^tk generation core (5GC) NFs to send information over N6 and Edge 8- interfaces, and in response to reception of the second request, which has an ECS identifier of the ECS to terminate, the ECSP management system is configured to: terminate the ECS VNF with the ECS identifier, and disconnect the ECS from the 5GC NFs.

8. The apparatus of claim 1, wherein the sendee provider is at least one of a public land mobile network (PLMN) or EC service provider that respectively comprises a PLMN or EC management system.

9. The apparatus of claim 8, wherein: the first request is a request to install an EAS and the second request is a request to terminate the EAS, in response to reception of the first request, the PLMN or EC management system is configured to: instantiate an EAS virtual network function (VNF), and after instantiation of the EAS VNF: connect the EAS to the EES, and connect the EAS to 5^th generation core (5GC) NFs to send information overN6 and Edge 7-interfaces, and in response to reception of the second request, which has an EAS identifier of the EAS to terminate, the PLMN or EC management system is configured to: terminate the EAS VNF with the EAS identifier, and disconnect the EAS from the 5GC NFs.

10. The apparatus of claim 8, wherein: the first request is a request to install an EES and the second request is a request to terminate the EES, in response to reception of the first request, the PLMN or EC management system is configured to: instantiate an EES virtual network function (VNF), and after instantiation of the EES VNF connect the EES to 5^th generation core (5GC) NFs to send information over N6 and Edge 2- interfaces, and in response to reception of the second request, which has an EES identifier of the EES to terminate, the PLMN or EC management system is configured to: terminate the EES VNF with the EES identifier, and disconnect the EES from the 5GC NFs,

11. The apparatus of claim 8, wherein: the first request is a request to install an ECS and the second request is a request to terminate the ECS, in response to reception of the first request, the PLMN or EC management system is configured to: instantiate an ECS virtual network function (VNF), and after instantiation of the ECS VNF connect the EES to 5^th generation core (5GC) NFs to send information over N6 and Edge 8~ interfaces, and in response to reception of the second request, which has an ECS identifier of the ECS to terminate, the PLMN or EC management system is configured to: terminate the ECS VNF with the ECS identifier, and disconnect the ECS from the 5GC NFs.

12. The apparatus of claim 1, wherein the processing circuitry is configured to, in response to the first request: select, based on deployment conditions, one of a plurality of Edge Data Networks (EDNs) to host the EC NF, and install the EC NF in the one of the EDNs.

13. The apparatus of claim 1, wherein the EC NF is: a first EES in an Edge Data Network (EDN) to provide configuration information to an Edge Enabler Client (EEC) and enable exchange of application data traffic between a first EAS and an application client (AC) in a user equipment (UE), or a second EES to provide the configuration information to the EEC and enable exchange of the application data traffic between the first EAS and the AC in the UE.

14. The apparatus of claim 1, wherein the processing circuitry is further configured to create: in an Edge Data Network (EDN), an EAS NF configured to perform server functions, and in a user equipment (LJE), an application client (AC) NF configured to perform client functions.

15. An apparatus configured to operate as a management system of a service provider, the apparatus comprising: processing circuitry configured to: receive a first request to install an Edge Computing (EC) Network Function (NF) to support EC, the EC NF selected from a set of EC NFs that include: an Edge Application Server (EAS), Edge Enabler Server (EES), and Edge Configuration Server (ECS); in response to reception of the first request: instantiate an EC virtual network function (VNF) of the EC NF, and after instantiation of the EC VNE: connect the EC NF to 5^th generation core (5GC) NFs to send information over Edge interfaces, and send a first notification to indicate installation of the EC NF, receive a second request to terminate the EC NF after installation of the EC NF, the second request comprising an EC NF identifier of the EC NF; and in response to reception of the second request: terminate the EC NF associated with the EC NF identifier, disconnect the EC NF from the 5GC NTs, and send a second notification to indicate termination of the EC NF; and a memory configured to store the first and second request.

16. The apparatus of claim 15, wherein the service provider is at least one of a public land mobile network (PLMN) or EC service provider and the management system respectively comprises a PLMN or EC management system.

17. The apparatus of claim 15, wherein the service provider is an Edge Computing Service Provider (ECSP) and the management system comprises an ECSP management system.

18. The apparatus of claim 15, wherein the processing circuitry is configured to, in response to the first request: select, based on deployment conditions, one of a plurality of Edge Data Networks (EDNs) to host the EC NF, and install the EC NF in the one of the EDNs.

19. A non-transitory computer-readable storage medium that stores instructions for execution by one or more processors of a service provider in a next generation (NG) network, the one or more processors to configure the sendee to, when the instructions are executed: receive a first request to install an Edge Computing (EC) Network Function (NF) to support EC, the EC NF selected from a set of EC NFs that include: an Edge Application Server (EAS), Edge Enabler Server (EES), and Edge Configuration Server (ECS); in response to reception of the first request: instantiate an EC virtual network function (VNF) of the EC NF, and after instantiation of the EC VNF: connect the EC NF to 5^th generation core (5GC) NFs to send information over Edge interfaces, and send a first notification to indicate installation of the EC NF; receive a second request to terminate the EC NF after installation of the EC NF, the second request comprising an EC NF identifier of the EC NF; and in response to reception of the second request: terminate the EC NF associated with the EC NF identifier, disconnect the EC NF from the 5GC NFs, and send a second notification to indicate termination of the EC NF.

20. The medium of claim 19, wherein in response to the first request: select, based on deployment conditions, one of a plurality of Edge Data Networks (EDNs) to host the EC NF, and install the EC NF in the one of the EDNs.