CN116648900A

CN116648900A - Support for lifecycle management for edge-enabled servers and edge configuration servers

Info

Publication number: CN116648900A
Application number: CN202180081836.7A
Authority: CN
Inventors: J·舒; 姚羿志
Original assignee: Intel Corp
Current assignee: Intel Corp
Priority date: 2021-01-12
Filing date: 2021-12-28
Publication date: 2023-08-25
Also published as: WO2022154961A1

Abstract

Various embodiments herein provide techniques related to: an Edge Computing Service Provider (ECSP) management system identifies that an ECSP consumer has consumed a management service (MnS) using an operation that instantiates an edge server. The ECSP management system can then enable the edge server. In some embodiments, mnS may be rationed MnS or lifecycle management (LCM) MnS. In some embodiments, the edge server may be an Edge Enabled Server (EES) or an Edge Configuration Server (ECS). Other embodiments may be described or claimed.

Description

Support for lifecycle management for edge-enabled servers and edge configuration servers

Cross Reference to Related Applications

The present application claims priority from U.S. provisional patent application No.63/136,541, filed 1/12/2021.

Technical Field

Various embodiments may relate generally to the field of wireless communications. For example, some embodiments may relate to servers of an edge computing network.

Background

Various embodiments may relate generally to the field of wireless communications.

Drawings

Embodiments will be readily understood by the following detailed description in conjunction with the accompanying drawings. To facilitate this description, like reference numerals designate like structural elements. Embodiments are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings.

FIG. 1 depicts an example edge computing network in accordance with various embodiments.

Fig. 2 depicts an example of Edge Enabled Server (EES) lifecycle management using a lifecycle management (LCM) management service (MnS), according to various embodiments.

Fig. 3 depicts an example of EES lifecycle management using dosing MnS, according to various embodiments.

Fig. 4 depicts an example of Edge Configuration Server (ECS) lifecycle management using LCM MnS, according to various embodiments.

Fig. 5 depicts an example of ECS lifecycle management using dosing MnS, according to various embodiments.

FIG. 6 depicts an example technique for instantiating an EES in accordance with various embodiments.

FIG. 7 depicts an example technique for instantiating an EES in accordance with various embodiments.

Fig. 8 depicts an example technique for instantiating an ECS in accordance with various embodiments.

Fig. 9 depicts an example technique for instantiating an ECS in accordance with various embodiments.

Fig. 10 schematically illustrates a wireless network in accordance with various embodiments.

Fig. 11 schematically illustrates components of a wireless network in accordance with various embodiments.

Fig. 12 schematically illustrates components of a wireless network in accordance with various embodiments.

Detailed Description

The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth (e.g., particular structures, architectures, interfaces, techniques, etc.) in order to provide a thorough understanding of the various aspects of the various embodiments. However, it will be apparent to one skilled in the art having the benefit of this disclosure that the various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In some instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of this document, the phrases "A or B" and "A/B" mean (A), (B) or (A and B).

FIG. 1 depicts an example edge computing network 100 in accordance with various embodiments. Specifically, FIG. 1 depicts a typical edge computing network 100 in which a mobile network 105 is connected to two Edge Data Networks (EDNs) 110a and 110b. EDNs 110a and 110b may each include an Edge Application Server (EAS) 115a and 115b. In EDN 110a, the EAS 115a and Edge Enabled Server (EES) 120a are trusted by the mobile operator of mobile network 105, so that the EAS 115a and EES 120a may be connected to Policy Control Function (PCF) 125 via Edge-7 interface and Edge-2 interface, respectively. In EDN 110b, EAS 115b and EES 120b may be trusted by the mobile operator of mobile network 105, so EAS 115b and EES 120b may be connected to a network open function (NEF) via Edge-7 interfaces and Edge-2 interfaces, respectively. ECS 135 may connect to NEF 130 via an Edge-8 interface.

Embodiments of the present disclosure relate to, among other things, deploying EES, ECS, and fifth generation (5G) mobile networks to support edge computing. Some embodiments relate to Mobile Robustness Optimization (MRO). Some embodiments may relate to the solutions and use cases shown below:

EES deployment

General rule

The sub-clause relates to a potential solution for use cases for EES deployment. Embodiments may be described with respect to two LCM solutions based on LCM MnS and dosing MnS, respectively.

EXAMPLE #1 EES lifecycle management Using LCM MnS

Fig. 2 depicts an example of EES lifecycle management using LCM MnS, according to various embodiments. Specifically, FIG. 2 illustrates an example in which an Edge Computing Service Provider (ECSP) consumer requests that an ECSP management system perform EES lifecycle management via LCM MnS. FIG. 2 depicts ECSP consumer 205 with MnS consumer (MnS-C) 210. FIG. 2 also depicts LCM MnS 215. FIG. 2 also depicts ECSP management system 220 with MnS provider (MnS-P) 225. The ECSP management system 220 is coupled with an EES Virtual Network Function (VNF) 230. ECSP management system 220 is also coupled via an OS-Ma-NFVO interface with European Telecommunications Standards Institute (ETSI) Network Function Virtualization (NFV) management and orchestration (MANO) 235, which includes NFV orchestrator (NFVO) 240.

EES instantiation

ECSP consumer 205 may consume LCM MnS 215 with an operation instatiateesreq through EES LCM IE to request ECSP management system 220 to instantiate EES, EES LCM IE including (but not limited to) the following attributes:

EES profile: including, but not limited to, information about EES.

EES topology service area: a list of cell IDs (or Tracking Area Identities (TAIs)) served by the EES.

EES geographic service area: the EES service is geographically located (geographical value).

EES VNF cells (IEs): information required to instantiate EES VNFs.

Software image information:

software image location: file locations where software images can be downloaded.

-minimum RAM: minimum RAM requirements for software mirroring.

-a minimum disk: minimum disk requirements for software mirroring

-virtual computing resources:

virtual CPU

Virtual memory

Virtual disk

The ECSP management system 220 can send an instataeeresp to inform the ECSP consumer 205 that EES instantiation is in progress.

The ECSP management system 220 may download the EES VNF 230 software image from the software image location and request the NFVO 240 to instantiate the EES VNF 230 instance via the Os-Ma-NFVO interface.

The ECSP management system 220 may send an insteateEesResp to inform the ECSP consumer 205 that the EES VNF 230 instance has been instantiated.

ECSP management system 220 can create the following Managed Object Instance (MOI):

the EES VNF MOI includes (but is not limited to) the following attributes:

EES LCM ID: indicating the EES LCM IE associated with the EES instance.

An EES profile cell.

The ECSP management system 220 may send notify MOICation to notify the ECSP consumer 205 that an EES VNF MOI has been created.

EES termination

ECSP consumer 205 may use the operation terminaeeesreq to consume LCM MnS215 to request ECSP management system 220 to terminate EES, terminateEesReq including, but not limited to, the following attributes:

-EES instance identifier: an identifier of the EES VNF 230 instance to be terminated.

The ECSP management system 220 can send a terminatee resresp to notify the ECSP consumer 205 that EES termination is in progress.

The ECSP management system 220 may perform the following operations to terminate EES instances;

-requesting NFVO to terminate VNF instance identified by EES instance ID.

-sending a terminaeeresresp to inform the consumer that the requested EES instance has been terminated.

-delete EES VNF MOI.

-sending a notify moistureletion to inform the consumer that EES VNF MOI has been deleted.

Example #2 EES lifecycle management Using ration MnS

Fig. 3 depicts an example of EES lifecycle management using dosing MnS 315, according to various embodiments. Specifically, FIG. 3 shows ECSP consumer 305 requesting ECSP management system 320 to perform EES lifecycle management via provisioning MnS 315. Generally, FIG. 3 depicts ECSP consumer 305 with MnS-C310. Fig. 3 also depicts dosing MnS 315. FIG. 3 also depicts ECSP management system 320 with MnS-P325. The ECSP management system 320 is coupled with the EES VNF 330. ECSP management system 320 is also coupled to ETSI NFV MANO 335, which includes NFVO 340, via an OS-Ma-NFVO interface.

To support EES deployment via provisioning MnS 315, the following Information Object Classes (IOCs) may be defined:

-EESLcm IOC containing requirements for EAS deployment;

EES profile: including, but not limited to, information about EES.

EES topology service area: a list of cell IDs (or TAIs) served by the EES.

EES geographic service area: geographic areas served by EES.

EES VNF information: information required to instantiate EES VNFs.

Software image information

-software image locations including locations for software image, minimum RAM and disk requirements.

-virtual computing resources including virtual CPUs, virtual memory and virtual disks.

EESFunction IOC, including (but not limited to) the following attributes:

EESLcm IOC ID: an identifier of EASLcm IOC.

An EES profile cell.

EES instantiation

ECSP consumer 305 may consume rationed MnS 320 using an operational createMOI for EESLcm IOC to request rationed MnS-P325 to instantiate the EES.

The ECSP management system 320 may download the EES VNF 330 software image from the software image location and request the NFVO 340 to instantiate the EES VNF 330 instance via the Os-Ma-NFVO interface.

ECSP management system 320 may create the following MOI:

the EES VNF MOI includes (but is not limited to) the following attributes:

EES LCM ID: indicating the EES LCM IE associated with the EES instance.

An EES profile cell.

The ECSP management system 320 may send a notify moisturation to inform the ECSP consumer 305 that an EES VNF MOI has been created.

EES termination

ECSP consumer 305 may consume rations 315 using an operation deleteMOI to request rations MnS-P325 to terminate EES instances, the deleteMOI including, but not limited to, the following attributes:

EES VNF instance ID: the identifier of the MOI for the EESFUNtion IOC indicates the EES VNF 330 instance to terminate.

ECSP management system 320 may perform the following operations:

-requesting NFVO 340 to terminate VNF instance based on EES VNF instance ID.

-deleting the MOI for eesfaction IOC.

-sending a notify moistureletion to inform the consumer that the MOI for the eesfunit IOC has been deleted.

ECS deployment

General rule

The sub-clause provides a potential solution for use cases for ECS deployment. It includes two possible LCM solutions based on LCM MnS and dosing MnS, respectively.

Example #1 ECS lifecycle management Using LCM MnS

Fig. 4 depicts an example of ECS lifecycle management using LCM MnS, according to various embodiments. Specifically, fig. 4 shows ECSP consumer 405 requesting ECSP management system 420 to perform ECS lifecycle management via LCM MnS 415. FIG. 4 depicts ECSP consumer 405 with MnS-C410. Fig. 4 also depicts LCM MnS 415. FIG. 4 also depicts ECSP management system 420 with MnS-P425. ECSP management system 420 is coupled with ECS VNF 430. ECSP management system 420 is also coupled with ETSI NFV MANO 435, including NFVO 440, via an OS-Ma-NFVO interface.

ECS instantiation

ECSP consumer 405 may consume LCM MnS 415 with an operation instatiateecsreq through ECS LCM IE to request ECSP management system 420 to instantiate ECS VNF 430, ECS LCM IE including (but not limited to) the following attributes:

-ECS VNF IE: information required for instantiating the ECS VNF.

Software image information

-minimum RAM: minimum RAM requirements for software mirroring.

-a minimum disk: minimum disk requirements for software mirroring.

-virtual computing resources:

virtual CPU

Virtual memory

Virtual disk

The ECSP management system 420 can send an instatatecsrresp to inform the ECSP consumer 405 that ECS instantiation is in progress.

ECSP management system 420 may download ECS VNF 430 software images from the software image location and request NFVO 440 via the Os-Ma-NFVO interface to:

instantiate ECS VNF 430 instance.

Creating a virtual link to connect the ECS VNF 430 instance with the EAS VNF instance identified by the EAS ID.

The ECSP management system 420 may send an instatatecsrresp to inform the ECSP consumer 405 that the ECS VNF 430 instance has been instantiated.

ECSP management system 420 can create the following MOI:

The ECS VNF MOI includes (but is not limited to) the following attributes:

ECS LCM ID: indicating the ECS LCM IE associated with the ECS instance.

-an ECS profile cell.

The ECSP management system 420 may send a notify moisturation to inform the ECSP consumer 405 that an ECS VNF MOI has been created.

ECS termination

ECSP consumer 405 may use the operation terminatecsreq to consume LCM MnS415 to request ECSP management system 420 to terminate ECS, terminateEcsReq including, but not limited to, the following attributes:

-ECS instance identifier: an identifier of the ECS VNF 430 instance to be terminated.

The ECSP management system 420 can send a terminatecsrresp to inform the ECSP consumer 405 that ECS termination is in progress.

The ECSP management system 420 can perform the following operations to terminate the ECS instance:

requesting NFVO 440 to terminate the VNF instance identified by the EAS instance ID and disconnect the ECS VNF 430 instance from the EAS VNF instance.

-sending a terminatee ecsrest to inform the consumer that the requested ECS instance has been terminated.

-deleting ECS VNF MOI.

-sending a notify moistureletion to inform the consumer that the ECS VNF MOI has been deleted.

Example #2 ECS lifecycle management Using rationing MnS

Fig. 5 depicts an example of ECS lifecycle management using dosing MnS, according to various embodiments. Specifically, fig. 5 shows that ECSP consumer 505 may request ECSP management system 520 to perform ECS lifecycle management via provisioning MnS 515. FIG. 5 depicts ECSP consumer 505 with MnS-C510. Fig. 5 also depicts dosing MnS 515. FIG. 5 also depicts ECSP management system 520 with MnS-P525. The ECSP management system 520 is coupled with the ECS VNF 530. ECSP management system 520 is also coupled to ETSI NFV MANO 535, including NFVO 540, via an OS-Ma-NFVO interface.

For purposes of discussing fig. 5, assume that an EAS VNF has been instantiated based on the EAS deployment solution described above.

To support ECS deployment via rationing MnS, the following IOCs should be defined:

ECSLcm IOC containing requirements for EAS deployment.

ECS VNF information: information required to instantiate ECS VNFs:

software image information

Ecsfunctation IOC, including (but not limited to) the following attributes:

ECSLcm IOC ID: an identifier of EASLcm IOC.

-an ECS profile cell.

ECS instantiation

ECSP consumer 505 may consume the rationed MnS 515 and call an operation createMOI for the ECSLcm IOC to request the rationed MnS 515 to instantiate the ECS.

ECSP management system 520 may download ECS VNF 530 software images from the software image location and request NFVO 540 via the Os-Ma-NFVO interface to:

instantiate ECS VNF 530 instance.

Creating a virtual link to connect the ECS VNF 530 instance with the EAS VNF instance identified by the EAS ID.

The ECSP management system creates the following MOI:

the ECS VNF MOI includes (but is not limited to) the following attributes:

ECS LCM ID: indicating the ECS LCM IE associated with the ECS instance.

-an ECS profile cell.

The ECSP management system 520 sends notify moicalization to inform the consumer that the ECS VNF MOI has been created.

ECS termination

ECSP consumer 505 may consume rationed MnS 515 using an operation deleteMOI to request rationed MnS 515 and/or MnS-P525 to terminate the ECS instance, the deleteMOI including, but not limited to, the following attributes:

-ECS VNF instance ID: the identifier of the MOI for ECSFUNtion IOC indicates the ECS VNF instance to be terminated.

The ECSP management system 520 will perform the following operations:

-requesting the NFVO to terminate the VNF instance based on the ECS VNF instance ID and disconnect the ECS VNF instance from the EAS VNF instance.

-deleting the MOI for ecsfaction IOC.

-sending notify moistureletion to inform the consumer that the MOI for ecsfaction IOC has been deleted.

Example techniques

FIG. 6 depicts an example technique for EES instantiation in accordance with various embodiments. The technique of fig. 6 may be performed by, for example, ECSP management system 220 of fig. 2. The technique may include: at 605, it is recognized by the ECSP management system that an ECSP consumer (e.g., ECSP consumer 205) has consumed LCM MnS (e.g., LCM MnS 215) using an operation instatieeesreq with an EES LCM IE. The technique may further include: at 610, EES is instantiated by the ECSP management system based on the operation instatieeesreq.

FIG. 7 depicts an example technique for EES instantiation in accordance with various embodiments. The technique of fig. 7 may be performed by, for example, ECSP management system 320 of fig. 3. The technique may include: at 705, it is identified by the ECSP management system that the ECSP consumer (e.g., ECSP consumer 305) has consumed the rationed MnS (e.g., rationed MnS 315) using the operational createMOI for the EESLcm IOC. The technique may further include: at 710, the EES is instantiated by the MnS-P325 of the ECSP management system based on the operation createMOI.

Fig. 8 depicts an example technique for ECS instantiation in accordance with various embodiments. The technique of fig. 8 may be performed by, for example, ECSP management system 420 of fig. 4. The technique may include: at 805, it is recognized by the ECSP management system that an ECSP consumer (e.g., ECSP consumer 405) has consumed LCM MnS (e.g., LCM MnS 415) using an operation instatatecsreq with an ECS LCM IE. The technique may further include: at 810, the ECS is instantiated by the ECSP management system based on the operation instatiateecsreq.

Fig. 9 depicts an example technique for ECS instantiation in accordance with various embodiments. The technique of fig. 9 may be performed by, for example, ECSP management system 520 of fig. 5. The technique may include: at 905, it is recognized by the ECSP management system that the ECSP consumer (e.g., ECSP consumer 505) has consumed the rationed MnS (e.g., rationed MnS 515) using the operational createMOI for ECSLcm IOC. The technique may further include: at 910, the ECS is instantiated based on the operation createMOI by the MnS-P525 of the ECSP management system.

It will be appreciated that the above examples are example embodiments of the various techniques herein, and that other embodiments may include more or fewer elements, elements in a different order than depicted, etc. Other embodiments may vary.

System and implementation

Fig. 10-12 illustrate various systems, devices, and components that may implement aspects of the disclosed embodiments.

Fig. 10 illustrates a network architecture 1000 in accordance with various embodiments. The network 1000 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G/NR systems. However, the example embodiments are not so limited, and the described embodiments may be applied to other networks (e.g., future 3GPP systems, etc.) that benefit from the principles described herein.

Network 1000 may include a UE 1002, and UE 1002 may include any mobile or non-mobile computing device designed to communicate with RAN 1004 via an over-the-air connection. The UE 1002 may be communicatively coupled with the RAN 1004 via a Uu interface. The UE 1002 may be, but is not limited to, a smart phone, tablet computer, wearable computer device, desktop computer, laptop computer, in-vehicle infotainment system, in-vehicle entertainment device, dashboard, head mounted display device, on-board diagnostic device, dashboard mobile device, mobile data terminal, electronic engine management system, electronic/engine control unit, electronic/engine control module, embedded system, sensor, microcontroller, control module, engine management system, networking appliance, machine type communication device, M2M or D2D device, ioT device, etc.

In some embodiments, the network 1000 may include multiple UEs directly coupled to each other via a side link interface. These UEs may be M2M/D2D devices that communicate using physical side link channels (e.g., without limitation, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.).

In some embodiments, UE 1002 may additionally communicate with AP 1006 via an over-the-air connection. The AP 1006 may manage WLAN connections that may be used to offload some/all network traffic from the RAN 1004. The connection between the UE 1002 and the AP 1006 may conform to any IEEE 802.11 protocol, where the AP 1006 may be wireless fidelityAnd a router. In some embodiments, UE 1002, RAN 1004, and AP 1006 may utilize cellular-WLAN aggregation (e.g., LWA/LWIP). cellular-WLAN aggregation may involve: the UE 1002 is configured by the RAN 1004 to utilize both cellular radio resources and WLAN resources.

RAN 1004 may include one or more access nodes (e.g., AN 1008). AN 1008 may terminate the air interface protocol for UE 1002 by providing AN access stratum protocol that includes RRC, PDCP, RLC, MAC and L1 protocols. In this way, the AN 1008 may enable data/voice connectivity between the CN 1020 and the UE 1002. In some embodiments, AN 1008 may be implemented in a separate device or as one or more software entities running on a server computer as part of, for example, a virtual network (which may be referred to as a CRAN or virtual baseband unit pool). AN 1008 may be referred to as a BS, gNB, RAN node, eNB, ng-eNB, nodeB, RSU, TRxP, TRP, etc. AN 1008 may be a macrocell base station or a low power base station for providing a femtocell, picocell, or other similar cell having a smaller coverage area, smaller user capacity, or higher bandwidth than a macrocell.

In embodiments where the RAN 1004 includes multiple ANs, they may be coupled to each other via AN X2 interface (if the RAN 1004 is AN LTE RAN) or AN Xn interface (if the RAN 1004 is a 5G RAN). The X2/Xn interfaces (which may be separated into control/user plane interfaces in some embodiments) may allow the AN to communicate information related to handoff, data/context transfer, mobility, load management, interference coordination, etc.

The ANs of the RAN 1004 may each manage one or more cells, groups of cells, component carriers, etc. to provide AN air interface for network access to the UE 1002. The UE 1002 may be simultaneously connected with multiple cells provided by the same or different ANs of the RAN 1004. For example, the UE 1002 and the RAN 1004 may use carrier aggregation to allow the UE 1002 to connect with multiple component carriers (each corresponding to a Pcell or Scell). In a dual connectivity scenario, the first AN may be a primary node providing AN MCG and the second AN may be a secondary node providing AN SCG. The first/second AN may be any combination of eNB, gNB, ng-enbs, etc.

RAN 1004 may provide the air interface on licensed spectrum or unlicensed spectrum. To operate in unlicensed spectrum, nodes may use LAA, eLAA, and/or feLAA mechanisms based on CA technology with PCells/scells. Prior to accessing the unlicensed spectrum, the node may perform medium/carrier sense operations based on, for example, a Listen Before Talk (LBT) protocol.

In a V2X scenario, the UE 1002 or AN 1008 may be or act as AN RSU, which may refer to any traffic infrastructure entity for V2X communications. The RSU may be implemented in or by a suitable AN or stationary (or relatively stationary) UE. RSUs implemented in or by: for a UE, it may be referred to as "UE-type RSU"; for enbs, it may be referred to as "eNB-type RSUs"; for a gNB, it may be referred to as a "gNB-type RSU"; etc. In one example, the RSU is a computing device coupled with a radio frequency circuit located at the roadside that provides connectivity support to the passing vehicle UE. The RSU may further include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, and applications/software to sense and control ongoing vehicle and pedestrian traffic. The RSU may provide extremely low latency communications required for high speed events (e.g., avoiding collisions, traffic alerts, etc.). Additionally or alternatively, the RSU may provide other cellular/WLAN communication services. The components of the RSU may be enclosed in a weather-proof enclosure suitable for outdoor installation, and may include a network interface controller for providing a wired connection (e.g., ethernet) to a traffic signal controller or backhaul network.

In some embodiments, the RAN 1004 may be an LTE RAN 1010 with an eNB (e.g., eNB 1012). The LTE RAN 1010 may provide an LTE air interface with the following characteristics: SCS of 15 kHz; a CP-OFDM waveform for DL and an SC-FDMA waveform for UL; a turbo code for data and a TBCC for control; etc. The LTE air interface may rely on: CSI-RS for CSI acquisition and beam management; PDSCH/PDCCH DMRS for PDSCH/PDCCH demodulation; and CRS for cell search and initial acquisition, channel quality measurement and channel estimation with respect to coherent demodulation/detection at the UE. The LTE air interface may operate over the sub-6GHz band.

In some embodiments, RAN 1004 may be a NG-RAN 1014 with a gNB (e.g., gNB 1016) and/or a NG-eNB (e.g., NG-eNB 1018). The gNB 1016 may connect with 5G enabled UEs using a 5G NR interface. The gNB 1016 may connect with the 5G core through a NG interface, which may include an N2 interface or an N3 interface. The NG-eNB 1018 may also connect with the 5G core over the NG interface, but may connect with the UE via the LTE air interface. The gNB 1016 and the ng-eNB 1018 may be connected to each other through an Xn interface.

In some embodiments, the NG interface may be divided into two parts: a NG user plane (NG-U) interface that carries traffic data (e.g., an N3 interface) between the node of NG-RAN 1014 and UPF 1048; and a NG control plane (NG-C) interface, which is a signaling interface (e.g., an N2 interface) between the node of NG-RAN 1014 and AMF 1044.

The NG-RAN 1014 may provide a 5G-NR air interface with the following characteristics: a variable SCS; CP-OFDM for DL, CP-OFDM for UL, and DFT-s-OFDM; polarization codes for control, repetition codes, simplex codes, and Reed-Muller codes, and LDPC codes for data. Similar to the LTE air interface, the 5G-NR air interface may rely on CSI-RS, PDSCH/PDCCH DMRS. The 5G-NR air interface may not use CRS, but may use: PBCH DMRS for PBCH demodulation; PTRS for phase tracking of PDSCH; and tracking the reference signal for time tracking. The 5G-NR air interface may operate on an FR1 band including a sub-6GHz band or an FR2 band including a band from 24.25GHz to 52.6 GHz. The 5G-NR air interface may comprise an SSB, which is an area of the downlink resource grid comprising PSS/SSS/PBCH.

In some embodiments, the 5G-NR air interface may utilize BWP for various purposes. For example, BWP may be used for dynamic adaptation of SCS. For example, UE 1002 may be configured with multiple BWP's, where each BWP configuration has a different SCS. When a BWP change is indicated to the UE 1002, the SCS of the transmission is also changed. Another example of use of BWP relates to power saving. In particular, the UE 1002 may be configured with multiple BWPs having different amounts of frequency resources (e.g., PRBs) to support data transmission in different traffic load scenarios. BWP containing a smaller number of PRBs may be used for data transmission with small traffic load while allowing power saving at the UE 1002 and in some cases at the gNB 1016. BWP containing a larger number of PRBs may be used for scenarios with higher traffic load.

The RAN 1004 is communicatively coupled with a CN 1020 including network elements to provide various functions to support data and telecommunications services for clients/subscribers (e.g., users of the UE 1002). The components of CN 1020 may be implemented in one physical node or in a separate physical node. In some embodiments, NFV may be utilized to virtualize any or all of the functionality provided by the network elements of CN 1020 onto physical computing/storage resources in servers, switches, and the like. The logical instantiation of the CN 1020 may be referred to as a network slice, while the logical instantiation of a portion of the CN 1020 may be referred to as a network sub-slice.

In some embodiments, the CN 1020 may be an LTE CN 1022 (which may also be referred to as EPC). LTE CN 1022 may include MME 1024, SGW 1026, SGSN 1028, HSS 1030, PGW 1032, and PCRF 1034, which are coupled to each other through interfaces (or "reference points"), as shown. The functions of the elements of the LTE CN 1022 may be briefly described as follows.

MME 1024 may implement mobility management functions to track the current location of UE 1002 to facilitate paging, bearer activation/deactivation, handover, gateway selection, authentication, and the like.

The SGW 1026 may terminate the S1 interface towards the RAN and route data packets between the RAN and the LTE CN 1022. SGW 1026 may be a local mobility anchor for inter-RAN node handover and may also provide anchoring for inter-3 GPP mobility. Other responsibilities may include lawful interception, charging and some policy enforcement.

SGSN 1028 can track the location of UE 1002 and perform security functions and access control. Furthermore, SGSN 1028 may perform EPC inter-node signaling for mobility between different RAT networks; PDN and S-GW selection specified by MME 1024; MME selection for handover; etc. The S3 reference point between MME 1024 and SGSN 1028 may enable user and bearer information exchange for inter-3 GPP access network mobility in idle/active state.

HSS 1030 may include a database for network users (which includes subscription-related information) to support the processing of communication sessions by network entities. HSS 1030 may provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, and the like. The S6a reference point between HSS 1030 and MME 1024 may enable the transfer of subscription and authentication data for authenticating/authorizing user access to LTE CN 1020.

PGW 1032 may terminate the SGi interface towards a Data Network (DN) 1036, which may include an application/content server 1038. PGW 1032 may route data packets between LTE CN 1022 and data network 1036. PGW 1032 may be coupled to SGW 1026 via an S5 reference point to facilitate user plane tunneling and tunnel management. PGW 1032 may further include nodes (e.g., PCEFs) for policy enforcement and charging data collection. Furthermore, the SGi reference point between PGW 1032 and data network 1036 may be an operator external public, private PDN or an operator internal packet data network, for example, for providing IMS services. PGW 1032 may be coupled with PCRF 1034 via a Gx reference point.

PCRF 1034 is a policy and charging control element of LTE CN 1022. PCRF 1034 may be communicatively coupled to app/content server 1038 to determine appropriate QoS and charging parameters for the service flows. PCRF 1032 may assign the association rules (via the Gx reference point) into the PCEF with the appropriate TFTs and QCIs.

In some embodiments, CN 1020 may be 5gc 1040. The 5gc 1040 may include AUSF 1042, AMF 1044, SMF 1046, UPF 1048, NSSF 1050, NEF 1052, NRF 1054, PCF 1056, UDM 1058, and AF 1060, coupled to each other through interfaces (or "reference points"), as shown. The function of the elements of the 5gc 1040 may be briefly described as follows.

The AUSF 1042 may store data for authentication of the UE 1002 and process authentication related functions. AUSF 1042 may facilitate a generic authentication framework for various access types. In addition to communicating with other elements of the 5gc 1040 through a reference point as shown, the AUSF 1042 may present an interface based on the Nausf service.

The AMF 1044 may allow other functions of the 5gc 1040 to communicate with the UE 1002 and the RAN 1004 and subscribe to notifications about mobility events for the UE 1002. The AMF 1044 may be responsible for registration management (e.g., for registering the UE 1002), connection management, reachability management, mobility management, and lawful interception of AMF related events, as well as access authentication and authorization. The AMF 1044 may provide transport for SM messages between the UE 1002 and the SMF 1046 and act as a transparent proxy for routing SM messages. The AMF 1044 may also provide for transmission of SMS messages between the UE 1002 and the SMSF. The AMF 1044 may interact with the AUSF 1042 and the UE 1002 to perform various security anchoring and context management functions. Furthermore, the AMF 1044 may be an end point of the RAN-CP interface, which may include or be an N2 reference point between the RAN 1004 and the AMF 1044; and the AMF 1044 may be the termination point of NAS (N1) signaling and perform NAS ciphering and integrity protection. The AMF 1044 may also support NAS signaling with the UE 1002 over the N3IWF interface.

The SMF 1046 may be responsible for SM (e.g., session establishment, tunnel management between UPF 1048 and AN 1008); UE IP address allocation and management (including optional authorization); selection and control of the UP function; configuring traffic steering at UPF 1048 to route traffic to the correct destination; terminating the interface towards the policy control function; control policy enforcement, charging, and a portion of QoS; lawful interception (for SM events and interfaces to LI systems); terminating the SM portion of the NAS message; downlink data notification; initiate AN specific SM information sent to the AN 1008 on N2 via the AMF 1044; and determining the SSC mode of the session. SM may refer to the management of PDU sessions, while PDU sessions or "sessions" may refer to PDU connectivity services that provide or enable the exchange of PDUs between UE 1002 and data network 1036.

The UPF 1048 may serve as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point for interconnection to the data network 1036, and a branching point for supporting multi-homing PDU sessions. The UPF 1048 may also perform packet routing and forwarding, perform packet inspection, implement policy rules user plane parts, lawful intercept packets (UP collection), perform traffic usage reporting, perform QoS processing for the user plane (e.g., packet filtering, gating, UL/DL rate enforcement), perform uplink traffic authentication (e.g., SDF to QoS flow mapping), transport layer packet tagging in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. The UPF 1048 may include an uplink classifier to support routing traffic flows to the data network.

NSSF 1050 may select a set of network slice instances to serve UE 1002. NSSF 1050 can also determine allowed NSSAIs and mappings to subscribed S-NSSAIs, if desired. NSSF 1050 may also determine a set of AMFs or a list of candidate AMFs to use to serve UE 1002 based on the appropriate configuration and possibly by querying NRF 1054. The selection of a set of network slice instances for the UE 1002 may be triggered by the AMF 1044 to which the UE 1002 is registered by interacting with the NSSF 1050, which may result in a change in AMF. NSSF 1050 may interact with AMF 1044 via an N22 reference point; and may communicate with another NSSF in the visited network via an N31 reference point (not shown). In addition, NSSF 1050 may expose an interface based on the Nnssf service.

The NEF 1052 may securely open services and capabilities provided by 3GPP network functions for third parties, internal openness/reopening, AF (e.g., AF 1060), edge computing or fog computing systems, etc. In these embodiments, NEF 1052 may authenticate, authorize, or restrict AF. NEF 1052 can also translate information exchanged with AF 1060 as well as information exchanged with internal network functions. For example, the NEF 1052 may translate between AF service identifiers and internal 5GC information. The NEF 1052 may also receive information from other NFs based on the capabilities of the other NFs that are open. This information may be stored as structured data at NEF 1052 or at data store NF using a standardized interface. The stored information may then be re-opened by the NEF 1052 to other NFs and AFs, or for other purposes (e.g., analysis). Furthermore, NEF 1052 may expose an interface based on Nnef services.

NRF 1054 may support a service discovery function, receive NF discovery requests from NF instances, and provide information of the discovered NF instances to the NF instances. NRF 1054 also maintains information of available NF instances and services supported by them. As used herein, the terms "instantiation," "instantiation," and the like may refer to the creation of an instance, and "instance" may refer to a specific occurrence of an object that may occur, for example, during execution of program code. Furthermore, NRF 1054 may expose an interface based on Nnrf services.

PCF 1056 may provide policy rules to control plane functions to implement them and may also support a unified policy framework to regulate network behavior. PCF 1056 may also implement a front end to access subscription information related to policy decisions in the UDR of UDM 1058. In addition to communicating with functions through reference points as shown, PCF 1056 also presents an interface based on the Npcf service.

The UDM 1058 may process subscription related information to support network entities in handling communication sessions and may store subscription data for the UE 1002. For example, subscription data may be communicated via an N8 reference point between the UDM 1058 and the AMF 1044. UDM 1058 may include two parts: application front-end and UDR. The UDR may store subscription data and policy data for the UDM 1058 and PCF 1056, and/or structured data for the open and application data for the NEF 1052 (including PFD for application detection, application request information for multiple UEs 1002). The UDR may expose an interface based on Nudr services to allow UDM 1058, PCF 1056, and NEF 1052 to access a particular set of stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notifications of related data changes in the UDR. The UDM may include a UDM-FE that hosts process credentials, location management, subscription management, and the like. Several different front ends may serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification processing, access authorization, registration/mobility management, and subscription management. In addition to communicating with other NFs through reference points as shown, UDM 1058 may also expose Nudm service-based interfaces.

AF 1060 may provide application impact on traffic routing, provide access to the NEF, and interact with the policy framework for policy control.

In some embodiments, the 5gc 1040 may enable edge computation by selecting an operator/third party service to be geographically close to the point where the UE 1002 attaches to the network. This may reduce latency and load on the network. To provide edge computing implementations, the 5gc 1040 may select the UPF 1048 near the UE 1002 and perform traffic steering from the UPF 1048 to the data network 1036 via the N6 interface. This may be based on the UE subscription data, the UE location, and the information provided by AF 1060. In this way, AF 1060 can affect UPF (re) selection and traffic routing. Based on the operator deployment, the network operator may allow the AF 1060 to interact directly with the associated NF when the AF 1060 is considered a trusted entity. In addition, AF 1060 may expose an interface based on Naf services.

Data network 1036 may represent various network operator services, internet access, or third party services that may be provided by one or more servers, including, for example, application/content server 1038.

Fig. 11 schematically illustrates a wireless network 1100 in accordance with various embodiments. The wireless network 1100 may include a UE 1102, the UE 1102 in wireless communication with AN 1104. The UE 1102 and AN 1104 may be similar to, and substantially interchangeable with, the components of the same name described elsewhere.

UE 1102 may be communicatively coupled with AN 1104 via a connection 1106. Connection 1106 is shown as an air interface to enable communicative coupling and may conform to a cellular communication protocol (e.g., an LTE protocol or a 5G NR protocol operating at mmWave or sub-6GHz frequencies).

The UE 1102 may include a host platform 1108, the host platform 1108 coupled with a modem platform 1110. Host platform 1108 may include application processing circuitry 1112, and application processing circuitry 1112 may be coupled with protocol processing circuitry 1114 of modem platform 1110. Application processing circuitry 1112 may run various applications for giving/absorbing application data for UE 1102. Application processing circuitry 1112 may also implement one or more layer operations to send and receive application data to and from a data network. These layer operations may include transport (e.g., UDP) and internet (e.g., IP) operations.

Protocol processing circuitry 1114 may implement one or more layers of operations to facilitate sending or receiving data over connection 1106. Layer operations implemented by the protocol processing circuitry 1114 may include, for example, MAC, RLC, PDCP, RRC and NAS operations.

Modem platform 1110 may further include digital baseband circuitry 1116, and digital baseband circuitry 1116 may implement one or more layer operations as "lower" layer operations performed by protocol processing circuitry 1114 in a network protocol stack. These operations may include, for example: PHY operation, including one or more of: HARQ-ACK functions, scrambling/descrambling, encoding/decoding, layer mapping/demapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna port precoding/decoding (which may include one or more of space-time, space-frequency, or spatial coding), reference signal generation/detection, preamble sequence generation and/or decoding, synchronization sequence generation/detection, control channel signal blind decoding, and other related functions.

The modem platform 1110 may further include transmit circuitry 1118, receive circuitry 1120, RF circuitry 1122, and an RF front end (RFFE) 1124, which may include or be connected to one or more antenna panels 1126. Briefly, the transmit circuit 1118 may include digital-to-analog converters, mixers, intermediate Frequency (IF) components, and the like; the receive circuitry 1120 may include analog-to-digital converters, mixers, IF components, etc.; the RF circuitry 1122 may include low noise amplifiers, power tracking components, and the like; RFFE 1124 may include filters (e.g., surface/bulk acoustic wave filters), switches, antenna tuners, beam forming components (e.g., phased array antenna components), and so forth. The selection and arrangement of the components of the transmit circuit 1118, receive circuit 1120, RF circuit 1122, RFFE 1124, and antenna panel 1126 (commonly referred to as "transmit/receive components") may be specific to the specifics of the particular implementation (e.g., whether the communication is TDM or FDM, in mmWave or sub-6gHz frequencies, etc.). In some embodiments, the transmit/receive components may be arranged in multiple parallel transmit/receive chains, may be provided in the same or different chips/modules, etc.

In some embodiments, the protocol processing circuit 1114 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit/receive components.

UE reception may be established through and via antenna panel 1126, RFFE 1124, RF circuitry 1122, receive circuitry 1120, digital baseband circuitry 1116, and protocol processing circuitry 1114. In some embodiments, the antenna panel 1126 may receive transmissions from the AN 1104 through receive beamformed signals received by multiple antennas/antenna elements of one or more antenna panels 1126.

UE transmissions may be established through and via the protocol processing circuitry 1114, digital baseband circuitry 1116, transmit circuitry 1118, RF circuitry 1122, RFFE 1124, and antenna panel 1126. In some embodiments, the transmit component of the UE 1102 may apply a spatial filter to the data to be transmitted to form a transmit beam that is transmitted by the antenna elements of the antenna panel 1126.

Similar to UE 1102, AN 1104 may include a host platform 1128, host platform 1128 coupled with a modem platform 1130. Host platform 1128 may include application processing circuitry 1132, with application processing circuitry 1132 coupled with protocol processing circuitry 1134 of modem platform 1130. The modem platform may further include digital baseband circuitry 1136, transmit circuitry 1138, receive circuitry 1140, RF circuitry 1142, RFFE circuitry 1144, and antenna panel 1146. The components of AN 1104 may be similar to, and substantially interchangeable with, the like-named components of UE 1102. In addition to performing data transmission/reception as described above, components of AN 1108 may perform various logical functions including, for example, RNC functions (e.g., radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling).

Fig. 12 is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methods discussed herein, according to some example embodiments. In particular, fig. 12 shows a diagrammatic representation of a hardware resource 1200, the hardware resource 1200 including one or more processors (or processor cores) 1210, one or more memory/storage devices 1220, and one or more communication resources 1230, each of which may be communicatively coupled via a bus 1240 or other interface circuitry. For embodiments that utilize node virtualization (e.g., NFV), the hypervisor 1202 can be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 1200.

Processor 1210 includes, for example, a processor 1212 and a processor 1214. Processor 1210 may be, for example, a Central Processing Unit (CPU), a Reduced Instruction Set Computing (RISC) processor, a Complex Instruction Set Computing (CISC) processor, a Graphics Processing Unit (GPU), a DSP (e.g., baseband processor), an ASI), an FPGA, a Radio Frequency Integrated Circuit (RFIC), another processor (including the processors discussed herein), or any suitable combination thereof.

Memory/storage 1220 may include main memory, disk storage, or any suitable combination thereof. Memory/storage 1220 may include, but is not limited to, any type of volatile, nonvolatile, or semi-volatile memory (e.g., dynamic Random Access Memory (DRAM), static Random Access Memory (SRAM), erasable Programmable Read Only Memory (EPROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory, solid state storage.

The communication resources 1230 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 1204 or one or more databases 1206 or other network elements via the network 1208. For example, communication resources 1230 may include wired communication components (e.g., for coupling via USB, ethernet, etc.), beesCellular communication component, NFC component,(or->Low power consumption) component->Components and other communication components.

The instructions 1250 may include software, programs, applications (applications), applets (applets), applications (apps), or other executable code for at least causing any processor 1210 to perform any one or more of the methods discussed herein. The instructions 1250 may reside, completely or partially, within at least one of the processor 1210 (e.g., within a cache memory of the processor), the memory/storage device 1220, or any suitable combination thereof. Further, any portion of instructions 1250 may be transferred from any combination of peripherals 1204 or databases 1206 to hardware resource 1200. Thus, the memory of processor 1210, memory/storage 1220, peripherals 1204, and database 1206 are examples of computer readable and machine readable media.

For one or more embodiments, at least one component set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, procedures, and/or methods set forth in the examples section below. For example, the baseband circuitry described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more examples set forth below. For another example, circuitry associated with a UE, base station, network element, etc., as described above in connection with one or more of the preceding figures, may be configured to operate in accordance with one or more of the examples set forth in the examples section below.

Example

Example 1 may include a method of operating a wireless network, wherein a consumer consumes a LCM management service (MnS) using an operational instantaneesreq with an EES LCM IE to request an ECSP management system to instantiate EES (edge enabled server).

Example 2 may include the method according to example 1 or some other examples herein, wherein the EES LCM IE includes: EES profile: the system comprises an EES topology service area and an EES geographic service area; and EES VNF IE: the system comprises software mirror image information, a software mirror image position, a minimum memory and a minimum disk; virtual computing resources: the system comprises a virtual CPU, a virtual memory and a virtual disk.

Example 3 may include the method according to examples 1 and 2 or some other examples herein, wherein upon receiving a request to install the EES via the operation instatiateereq, the ECSP management system is configured to: sending an instatateeeresp to inform the consumer that EES instantiation is in progress; downloading the EES VNF software image from the software image position in the EES LCM IE; request NFVO to instantiate EES via Os-Ma-NFVO interface; sending an instatateeeresp to inform the consumer that EES has been instantiated; creating an EES VNF MOI from the EES VNF IOC; and sending a notify moisturation to inform the consumer that the EES VNF MOI has been created.

Example 4 may include an apparatus of a management system, comprising: a memory; and processing circuitry configured to: the operation is that the consumer consumes LCM MnS using an operation terminateeresreq with EES instance identifier to request the ECSP management system to terminate EES.

Example 5 may include the apparatus of example 4 or some other examples herein, wherein, upon receiving a request to terminate the EES via the operation terminatee ereq, the ECSP management system is configured to: sending a terminaeeresresp to inform the consumer that EES termination is in progress; requesting the NFVO to terminate EES via the Os-Ma-NFVO interface; sending a terminaeeresresp to inform the consumer that EES has been terminated; deleting EES VNF MOI; and sending a notify moistureletion to inform the consumer that the EES VNF MOI has been deleted.

Example 6 may include an apparatus of a management system, comprising: a memory; and processing circuitry configured to: operation CreateMOI consumes the rationed MnS for the consumer using the operation for EESLcm IOC to request that the rationed MnS producer instantiate the EES.

Example 7 may include the apparatus of example 6 or some other example herein, wherein the EESLcm IOC comprises: EES profile: the system comprises an EES topology service area and an EES geographic service area; and EES VNF IE: the system comprises software mirror image information, a software mirror image position, a minimum memory and a minimum disk; virtual computing resources: the system comprises a virtual CPU, a virtual memory and a virtual disk.

Example 8 may include the apparatus of examples 6 and 7 or some other examples herein, wherein, upon receiving the request to install the EES via the operational createMOI, the ECSP management system is configured to: downloading an EES VNF software image from a software image location in the EESLcm IOC; request NFVO to instantiate EES via Os-Ma-NFVO interface; creating EESLcm MOI; and sending a notify moicontrol to inform the consumer that the EESLcm MOI has been created.

Example 9 may include an apparatus of a management system, comprising: a memory; and processing circuitry configured to: the operation is to consume the allocated MnS for the consumer using an operation deleteMOI with an EES instance identifier to request the ECSP management system to terminate EES.

Example 10 may include the apparatus of example 9 or some other example herein, wherein, upon receiving a request to terminate the EES via an operation deleteMOI, the ECSP management system is configured to: requesting the NFVO to terminate EES via the Os-Ma-NFVO interface; deleting EESLcm MOI; and sending a notify moistureletion to inform the consumer that the EESLcm MOI has been deleted.

Example 11 may include an apparatus to manage a system, comprising: a memory; and processing circuitry configured to: the operation is consuming LCM management service (MnS) with an operation instataeeesreq with ECS LCM IE to request the ECSP management system to instantiate ECS (edge configuration server).

Example 12 may include the apparatus of example 11 or some other example herein, wherein the ECS LCM IE comprises: ECS VNF IE: the system comprises software mirror image information, a software mirror image position, a minimum RAM and a minimum disk; virtual computing resources: the system comprises a virtual CPU, a virtual memory and a virtual disk.

Example 13 may include the apparatus of examples 11 and 12 or some other example herein, wherein, upon receiving the request to install the ECS via the operation instatiateecsreq, the ECSP management system is configured to: sending an instatateecssresp to inform the consumer that ECS instantiation is in progress; downloading the ECS VNF software image from the software image position in the ECS LCM IE; requesting NFVO instantiation of the ECS via the Os-Ma-NFVO interface; sending an instatatecsresp to inform the consumer that the ECS has been instantiated; creating an ECS VNF MOI from the ECS VNF IOC; and sending a notify moisturation to inform the consumer that the ECS VNF MOI has been created.

Example 14 may include an apparatus to manage a system, comprising: a memory; and processing circuitry configured to: the operation is that the consumer consumes LCM MnS using an operation terminateECSReq with ECS instance identifier to request the ECSP management system to terminate the ECS.

Example 15 may include the apparatus of example 14 or some other example herein, wherein, upon receiving a request to terminate the ECS via the operation terminatecsreq, the ECSP management system is configured to: sending a terminatecssresp to inform the consumer that ECS termination is in progress; requesting the NFVO to terminate the ECS via the Os-Ma-NFVO interface; sending a terminatecssresp to inform the consumer that the ECS has been terminated; deleting ECS VNF MOI; and sending a notify moistureletion to inform the consumer that the ECS VNF MOI has been deleted.

Example 16 may include an apparatus to manage a system, comprising: a memory; and processing circuitry configured to: operations are to consume the rationed MnS for the consumer using an operation createMOI for the ECSLcm IOC to request that the rationed MnS producer instantiate the ECS.

Example 17 may include the apparatus of example 16 or some other example herein, wherein the ECSLcm IOC includes: ECS VNF IE: the system comprises software mirror image information, a software mirror image position, a minimum RAM and a minimum disk; virtual computing resources: the system comprises a virtual CPU, a virtual memory and a virtual disk.

Example 18 may include the apparatus of examples 16 and 17 or some other examples herein, wherein, upon receiving the request to install the ECS via the operational createMOI, the ECSP management system is configured to: downloading an ECS VNF software image from a software image position in the ECSLcm IOC; requesting NFVO instantiation of the ECS via the Os-Ma-NFVO interface; creating ECSLcm MOI; and sending a notify moicontrol to inform the consumer that the ECSLcm MOI has been created.

Example 19 may include an apparatus to manage a system, comprising: a memory; and processing circuitry configured to: the operation is to consume the allocated MnS for the consumer using an operation deleteMOI with an ECS instance identifier to request the ECSP management system to terminate the ECS.

Example 20 may include the apparatus of example 19 or some other example herein, wherein, upon receiving the request to terminate the ECS via the operation deleteMOI, the ECSP management system is configured to: requesting the NFVO to terminate the ECS via the Os-Ma-NFVO interface; deleting ECSLcm MOI; and sending a notify moistureletion to inform the consumer that the ECSLcm MOI has been deleted.

Example 21 includes a method comprising: receiving, by an Edge Computing Service Provider (ECSP), a request to instantiate an EES (edge enabled server); and in response to receiving a request to install the EES: sending an instatateeeresp to inform the consumer that EES instantiation is in progress; downloading an EES Virtual Network Function (VNF) software image from a software image location indicated in an EES lifecycle management (LCM) Information Element (IE); request a network virtualization function orchestrator (NFVO) to instantiate EES via the Os-Ma-NFVO interface; sending an instatateeeresp to inform the consumer that EES has been instantiated; creating EES VNF Management Object Instances (MOIs) from EES VNF Information Object Classes (IOCs); and sending a notify moisturation to inform the consumer that the EES VNF MOI has been created.

Example 22 includes the method of example 21 or some other example herein, wherein the EES LCM IE includes: EES profiles, including EES topology service areas or EES geographic service areas.

Example 23 includes the method of example 21 or some other example herein, wherein the EES LCM IE includes: EES VNF IE including software image information, software image location, minimum RAM or minimum disk.

Example 23 includes the method of example 21 or some other example herein, wherein the EES LCM IE includes: virtual computing resources, including virtual CPUs, virtual memory, or virtual disks.

Example 24 includes a method, comprising: identifying, by an Edge Computing Service Provider (ECSP) management system, that an ECSP consumer has consumed a lifecycle management (LCM) management service (MnS) using an operational insteateeesreq with an Edge Enabled Server (EES) LCM cell (IE); and instantiating, by the ECSP management system, the EES based on the operation instatieeesreq.

Example 25 includes the method of example 24 or some other example herein, wherein the EES LCM IE includes an EES profile, an EES Virtual Network Function (VNF) IE, and an indication of one or more virtual computing resources.

Example 26 includes the method of example 24 or 25 or some other example herein, wherein instantiating the EES comprises: sending, by the ECSP management system, an instatieeresp notification to the ECSP consumer; acquiring, by the ECSP management system, an EES Virtual Network Function (VNF) software image from a software image location in the EES LCM IE; sending, by the ECSP management system, a request to instantiate the EES to a Network Function Virtualization Orchestrator (NFVO) via an Os-Ma-NFVO interface; sending, by the ECSP management system, an instatieeresp to the ECSP consumer to inform the ECSP consumer that the EES has been instantiated; creating, by the ECSP management system, EES VNF Management Object Instances (MOIs) from EES VNF Information Object Classes (IOCs); and sending, by the ECSP management system, the notify moiction to the ECSP consumer to notify the ECSP consumer that the EES VNF MOI has been created.

Example 27 includes the method of example 26 or some other example herein, further comprising: identifying, by the ECSP management system, that the ECSP consumer has consumed LCM MnS using an operation terminaeeesreq with an EES instance identifier associated with the EES; and terminating, by the ECSP management system, the EES based on the operation terminatee ereq.

Example 28 includes the method of example 27 or some other example herein, wherein terminating the EES comprises: sending, by the ECSP management system, a terminateeeresresp to the ECSP consumer; sending, by the ECSP management system, a request to terminate the EES to the NFVO via the Os-Ma-NFVO interface; sending, by the ECSP management system, a notification to the ECSP consumer that the EES has been terminated; deleting the EES VNF MOI by the ECSP management system; and sending, by the ECSP management system, the notify moistureideltion to the ECSP consumer to notify the ECSP consumer that the EES VNF MOI has been deleted.

Example 29 includes a method, comprising: identifying, by an Edge Computing Service Provider (ECSP) management system, that an ECSP consumer has consumed a rationing management service (MnS) using an operational createMOI for an EESLcm Information Object Class (IOC); and instantiating, by an MnS producer (MnS-P) of the ECSP management system, an Edge Enabled Server (EES) based on the operation createMOI.

Example 30 includes the method of example 29 or some other example herein, wherein the EESlcm IOC includes an EES profile, an EES Virtual Network Function (VNF) IE, and an indication of one or more virtual computing resources.

Example 31 includes the method of example 29 or 30 or some other example herein, wherein instantiating the EES comprises: acquiring, by an ECSP management system, an EES Virtual Network Function (VNF) software image from a software image location in an EESLcm IOC; sending, by the ECSP management system, a request to instantiate the EES to a Network Function Virtualization Orchestrator (NFVO) via an Os-Ma-NFVO interface; creating an EESLcm MOI by an ECSP management system; and sending, by the ECSP management system, the notfymoicalization to the ECSP consumer to notify the ECSP consumer that the EESLcm MOI has been created.

Example 32 includes the method of example 31 or some other example herein, further comprising: identifying, by the ECSP management system, that the ECSP consumer has consumed the rationed MnS using an operation deleteMOI having an EES instance identifier associated with the EES; and terminating, by the ECSP management system, the EES based on the operation deleteMOI.

Example 33 includes the method of example 32 or some other example herein, wherein terminating the EES comprises: sending, by the ECSP management system, a request to terminate the EES to the NFVO via the Os-Ma-NFVO interface; deleting the EESLcm MOI by the ECSP management system; and sending, by the ECSP management system, the notify moistureletion to the ECSP consumer to notify the ECSP consumer that the EESLcm MOI has been deleted.

Example 34 includes a method, comprising: identifying, by an Edge Computing Service Provider (ECSP) management system, that an ECSP consumer has consumed a lifecycle management (LCM) management service (MnS) using an operational instatiateecsreq having an Edge Configuration Server (ECS) LCM cell (IE); and instantiating, by the ECSP management system, the ECS based on the operation instatatecsreq.

Example 35 includes the method of example 34 or some other example herein, wherein the ECS LCM IE includes an ECS Virtual Network Function (VNF) IE and an indication of one or more virtual computing resources.

Example 36 includes the method of example 34 or 35 or some other example herein, wherein instantiating the ECS comprises: sending, by the ECSP management system, an instatiateEcsResp notification to the ECSP consumer; acquiring, by the ECSP management system, an ECS Virtual Network Function (VNF) software image from a software image location in the ECS LCM IE; sending, by the ECSP management system, a request to instantiate the ECS to a Network Function Virtualization Orchestrator (NFVO) via an Os-Ma-NFVO interface; sending, by the ECSP management system, an instatiateecsrep to the ECSP consumer to notify the ECSP consumer that the ECS has been instantiated; creating, by the ECSP management system, ECS VNF Management Object Instances (MOIs) from ECS VNF Information Object Classes (IOCs); and sending, by the ECSP management system, the notify moiction to the ECSP consumer to inform the ECSP consumer that the ECS VNF MOI has been created.

Example 37 includes the method of example 36 or some other example herein, further comprising: identifying, by the ECSP management system, that the ECSP consumer has consumed LCM MnS using an operational terminatee ecsreq having an ECS instance identifier associated with the ECS; and terminating, by the ECSP management system, the ECS based on the operational terminatee ecsreq.

Example 38 includes the method of example 37 or some other example herein, wherein terminating the ECS comprises: sending, by the ECSP management system, a terminateEcsResp to the ECSP consumer; sending, by the ECSP management system, a request to terminate the ECS to the NFVO via the Os-Ma-NFVO interface; sending, by the ECSP management system, a notification to the ECSP consumer that the ECS has been terminated; deleting the ECS VNF MOI by the ECSP management system; and sending, by the ECSP management system, the notify moistureidelion to the ECSP consumer to notify the ECSP consumer that the ECS VNF MOI has been deleted.

Example 39 includes a method, comprising: identifying, by an Edge Computing Service Provider (ECSP) management system, that an ECSP consumer has consumed a rationing management service (MnS) using an operational createMOI for an ECSLcm Information Object Class (IOC); and instantiating, by a MnS producer (MnS-P) of the ECSP management system, an Edge Configuration Server (ECS) based on the operation createMOI.

Example 40 includes the method of example 39 or some other example herein, wherein the ECSlcm IOC includes an ECS Virtual Network Function (VNF) IE and an indication of one or more virtual computing resources.

Example 41 includes the method of example 39 or 40, or some other example herein, wherein instantiating the ECS comprises: acquiring, by an ECSP management system, an ECS Virtual Network Function (VNF) software image from a software image location in an ECSLcm IOC; sending, by the ECSP management system, a request to instantiate the ECS to a Network Function Virtualization Orchestrator (NFVO) via an Os-Ma-NFVO interface; creating an ECSLcm MOI by an ECSP management system; and sending, by the ECSP management system, the notify MOI to the ECSP consumer to notify the ECSP consumer that the ECSLcm MOI has been created.

Example 42 includes the method of example 41 or some other example herein, further comprising: identifying, by the ECSP management system, that the ECSP consumer has consumed the rationed MnS using an operation deleteMOI having an ECS instance identifier associated with the ECS; and terminating, by the ECSP management system, the ECS based on the operation deleteMOI.

Example 43 includes the method of example 42 or some other example herein, wherein terminating the ECS comprises: sending, by the ECSP management system, a request to terminate the ECS to the NFVO via the Os-Ma-NFVO interface; deleting the ECSLcm MOI by the ECSP management system; and sending, by the ECSP management system, the notify moistureletion to the ECSP consumer to notify the ECSP consumer that the ECSLcm MOI has been deleted.

Example 44 may include an apparatus comprising means for performing one or more elements of any of examples 1-43, or any other method or process described herein.

Example 45 may include one or more non-transitory computer-readable media comprising instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of the methods described in or associated with any of examples 1-43, or any other method or process described herein.

Example 46 may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of any of the methods described in or associated with examples 1-43, or any other method or process described herein.

Example 47 may include a method, technique, or process as described in or associated with any of examples 1-43, or portions thereof.

Example 48 may include an apparatus comprising: one or more processors; and one or more computer-readable media comprising instructions that, when executed by one or more processors, cause the one or more processors to perform a method, technique, or process as described in or related to any one of examples 1-43 or portions thereof.

Example 49 may include a signal as described in or associated with any of examples 1-43 or a portion or portion thereof.

Example 50 may include a datagram, packet, frame, segment, protocol Data Unit (PDU), or message as described in or associated with any one of examples 1-43, or portions thereof, or otherwise described in this disclosure.

Example 51 may include signals encoded with data as described in or related to any of examples 1-43, or portions thereof, or otherwise described in this disclosure.

Example 52 may include signals encoded with datagrams, packets, frames, segments, protocol Data Units (PDUs), or messages as described in or associated with any of examples 1-43, or portions thereof, or otherwise described in this disclosure.

Example 53 may include electromagnetic signals carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors causes the one or more processors to perform the methods, techniques, or processes as described in or related to any one of examples 1-43, or portions thereof.

Example 54 may include a computer program comprising instructions, wherein execution of the program by a processing element causes the processing element to perform a method, technique, or process as described in or in connection with any one or portions of examples 1-43.

Example 55 may include signals in a wireless network as shown and described herein.

Example 56 may include a method of communicating in a wireless network as shown and described herein.

Example 57 may include a system for providing wireless communications as shown and described herein.

Example 58 may include a device for providing wireless communication as shown and described herein.

Any of the above examples may be combined with any other example (or combination of examples) unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

Terminology

For purposes of this document, the following terms and definitions may be applied to the examples and embodiments discussed herein.

The term "circuitry" as used herein refers to, as part of, or including the following hardware components configured to provide the described functionality: such as electronic circuitry, logic circuitry, 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), a Digital Signal Processor (DSP), etc. 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 circuitry for use in an electrical or electronic system) and program code for performing the functions of the program code. In these embodiments, a combination of hardware elements and program code may be referred to as a particular type of circuit.

The term "processor circuit" as used herein refers to, is part of, or includes circuitry capable of sequentially and automatically performing a series of arithmetic or logical operations or recording, storing, and/or transmitting digital data. The processing circuitry may include one or more processing cores for executing instructions and one or more memory structures for storing program and data information. The term "processor circuitry" may refer to one or more application processors, one or more baseband processors, a physical Central Processing Unit (CPU), a single core processor, a dual core processor, a tri-core processor, a quad-core processor, and/or any other device capable of executing or otherwise operating computer-executable instructions (e.g., program code, software modules, and/or functional processes). The processing circuitry may include further hardware accelerators, which may be microprocessors, programmable processing devices, or the like. The one or more accelerators may include, for example, computer vision and/or deep learning accelerators. The terms "application circuitry" and/or "baseband circuitry" may be considered synonymous with and may be referred to as "processor circuitry".

The term "interface circuit" as used herein refers to, is part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term "interface circuitry" may refer to one or more hardware interfaces (e.g., a bus, an I/O interface, a peripheral component interface, a network interface card, etc.).

The term "user equipment" or "UE" as used herein refers to a device having radio communication capabilities and may describe a remote user of network resources in a communication network. The term "user equipment" or "UE" may be considered synonymous to and may be referred to as a client, mobile station, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio, reconfigurable mobile, etc. Furthermore, the term "user equipment" or "UE" may include any type of wireless/wired device or any computing device that includes a wireless communication interface.

The term "network element" as used herein refers to a physical or virtualized device and/or infrastructure to provide wired or wireless communication network services. The term "network element" may be considered synonymous to and/or refer to a networked computer, networking hardware, network device, network node, router, switch, hub, bridge, radio network controller, RAN device, RAN node, gateway, server, virtualized VNF, NFVI, etc.

The term "computer system" as used herein refers to any type of interconnected electronic device, computer device, or component thereof. Furthermore, the terms "computer system" and/or "system" may refer to various components of a computer that are communicatively coupled to one another. Furthermore, the terms "computer system" and/or "system" may refer to a plurality of computer devices and/or a plurality of computing systems communicatively coupled to each other and configured to share computing and/or networking resources.

The terms "appliance," "computer appliance," and the like as used herein refer to a computer device or computer system having program code (e.g., software or firmware) specifically designed to provide a particular computing resource. A "virtual device" is a virtual machine image to be implemented by a hypervisor-equipped device that virtualizes or emulates a computer appliance or is otherwise dedicated to providing specific computing resources.

The term "resource" as used herein refers to a physical or virtual device, a physical or virtual component within a computing environment, and/or a physical or virtual component within a particular device, such as a computer device, a mechanical device, a memory space, processor/CPU time, processor/CPU usage, processor and accelerator load, hardware time or usage, power, input/output operations, ports or network sockets, channel/link assignments, throughput, memory usage, storage, networks, databases and applications, workload units, and the like. "hardware resources" may refer to computing, storage, and/or network resources provided by physical hardware elements. "virtualized resources" may refer to computing, storage, and/or network resources provided by the virtualization infrastructure to applications, devices, systems, etc. The term "network resource" or "communication resource" may refer to a resource that is accessible to a computer device/system via a communication network. The term "system resource" may refer to any kind of shared entity for providing a service and may include computing and/or network resources. System resources may be viewed as a collection of coherent functions, network data objects, or services that are accessible through a server, where the system resources reside on a single host or multiple hosts and are clearly identifiable.

The term "channel" as used herein refers to any tangible or intangible transmission medium to communicate data or data streams. The term "channel" may be synonymous and/or equivalent to "communication channel," data communication channel, "" transmission channel, "" data transmission channel, "" access channel, "" data access channel, "" link, "data link," "carrier," "radio frequency carrier," and/or any other similar term that refers to a path or medium through which data is communicated. Furthermore, the term "link" as used herein refers to a connection between two devices through a RAT that is aimed at transmitting and receiving information.

The terms "instantiation", "instantiation" and the like as used herein refer to the creation of an instance. "instance" also refers to a specific occurrence of an object, which may occur, for example, during execution of program code.

The terms "coupled," "communicatively coupled," and their derivatives are used herein. The term "coupled" may mean that two or more elements are in direct physical or electrical contact with each other, may mean that two or more elements are in indirect contact with each other but still cooperate or interact with each other, and/or may mean that one or more other elements are coupled or connected between elements referred to as being coupled to each other. The term "directly coupled" may mean that two or more elements are in direct contact with each other. The term "communicatively coupled" may mean that two or more elements may be in contact with each other through communication (including through wired or other interconnection connections, through wireless communication channels or links, etc.).

The term "cell" refers to a structural element that contains one or more fields. The term "field" refers to the individual content of a cell, or a data element containing content.

The term "SMTC" refers to an SSB-based measurement timing configuration configured by SSB-measurementtiming configuration.

The term "SSB" refers to an SS/PBCH block.

The term "primary cell" refers to an MCG cell operating on a primary frequency in which a UE performs an initial connection establishment procedure or initiates a connection re-establishment procedure.

The term "primary SCG cell" refers to an SCG cell for DC operation in which the UE performs random access when performing reconfiguration with the synchronization procedure.

The term "secondary cell" refers to a cell providing additional radio resources on top of a special cell for a UE configured with CA.

The term "secondary cell group" refers to a subset of serving cells including PSCell and zero or more secondary cells for a UE configured with DC.

The term "serving cell" refers to a primary cell for a UE under rrc_connected that is not configured with CA/DC, and there is only one serving cell including the primary cell.

The term "serving cell" or "plurality of serving cells" refers to a cell set including a special cell and all secondary cells for a UE under rrc_connected configured with CA.

The term "special cell" refers to the PCell of an MCG or the PSCell of an SCG for DC operation; otherwise, the term "special cell" refers to a Pcell.

Claims

1. One or more non-transitory computer-readable media comprising instructions that, when executed by at least one processor of an electronic device, cause an Edge Computing Service Provider (ECSP) management system of the electronic device to:

identifying, by the ECSP management system, that an ECSP consumer has consumed an Edge Enabled Server (EES) lifecycle management (LCM) management service (MnS) using an operation instataeeesreq with an LCM cell (IE); and

the EES is instantiated by the ECSP management system based on the operation instatieeesreq.

2. The one or more non-transitory computer-readable media of claim 1, wherein the EES LCM IE comprises an EES profile, an EES Virtual Network Function (VNF) IE, and an indication of one or more virtual computing resources.

3. The one or more non-transitory computer-readable media of claim 1 or 2, wherein instantiating the EES comprises:

sending, by the ECSP management system, an instatieeresp notification to the ECSP consumer;

acquiring, by the ECSP management system, an EES Virtual Network Function (VNF) software image from a software image location in the EES LCM IE;

Sending, by the ECSP management system, a request to instantiate the EES to a Network Function Virtualization Orchestrator (NFVO) via an Os-Ma-NFVO interface;

sending, by the ECSP management system, an instatiateesresp to the ECSP consumer to notify the ECSP consumer that the EES has been instantiated;

creating, by the ECSP management system, EES VNF Management Object Instances (MOIs) from EES VNF Information Object Classes (IOCs); and

sending, by the ECSP management system, a notify MOI to the ECSP consumer to notify the ECSP consumer that the EES VNF MOI has been created.

4. The one or more non-transitory computer-readable media of claim 3, wherein the instructions are further to:

identifying, by the ECSP management system, that the ECSP consumer has consumed the LCM MnS using an operation terminaeeesreq having an EES instance identifier associated with the EES; and

the EES is terminated by the ECSP management system based on an operation terminatee ereq.

5. The one or more non-transitory computer-readable media of claim 4, wherein terminating the EES comprises:

sending, by the ECSP management system, a terminatee eiesresp to the ECSP consumer;

Sending, by the ECSP management system, a request to terminate the EES to the NFVO via the Os-Ma-NFVO interface;

sending, by the ECSP management system, a notification to the ECSP consumer that the EES has been terminated;

deleting the EES VNF MOI by the ECSP management system; and

sending, by the ECSP management system, a notify moistureletion to the ECSP consumer to notify the ECSP consumer that the EES VNF MOI has been deleted.

6. One or more non-transitory computer-readable media comprising instructions that, when executed by at least one processor of an electronic device, cause an Edge Computing Service Provider (ECSP) management system of the electronic device to:

identifying, by the ECSP management system, that an ECSP consumer has consumed a rationing management service (MnS) using an operational createMOI for an EESLcm Information Object Class (IOC); and

an Edge Enabled Server (EES) is instantiated by an MnS producer (MnS-P) of the ECSP management system based on the operational createMOI.

7. The one or more non-transitory computer-readable media of claim 6, wherein the EESlcm IOC comprises an EES profile, an EES Virtual Network Function (VNF) IE, and an indication of one or more virtual computing resources.

8. The one or more non-transitory computer-readable media of claim 6 or 7, wherein instantiating the EES comprises:

acquiring, by the ECSP management system, an EES Virtual Network Function (VNF) software image from a software image location in the EESLcm IOC;

creating the EESLcm MOI by the ECSP management system; and

sending, by the ECSP management system, a notify MOI to the ECSP consumer to notify the ECSP consumer that the EESLcm MOI has been created.

9. The one or more non-transitory computer-readable media of claim 8, wherein the instructions are further to:

identifying, by the ECSP management system, that the ECSP consumer has consumed the rationed MnS using an operation deleteMOI having an EES instance identifier associated with the EES; and

terminating, by the ECSP management system, the EES based on an operation deleteMOI.

10. The one or more non-transitory computer-readable media of claim 9, wherein terminating the EES comprises:

Deleting the EESLcm MOI by the ECSP management system; and

sending, by the ECSP management system, a notify moistureletion to the ECSP consumer to notify the ECSP consumer that the EESLcm MOI has been deleted.

11. One or more non-transitory computer-readable media comprising instructions that, when executed by at least one processor of an electronic device, cause an Edge Computing Service Provider (ECSP) management system of the electronic device to:

identifying, by the ECSP management system, that an ECSP consumer has consumed an Edge Configuration Server (ECS) lifecycle management (LCM) management service (MnS) using an operational instatatecsreq having an LCM cell (IE); and

the ECS is instantiated by the ECSP management system based on the operation instatatecsreq.

12. The one or more non-transitory computer-readable media of claim 11, wherein the ECS LCM IE comprises an ECS Virtual Network Function (VNF) IE and an indication of one or more virtual computing resources.

13. The one or more non-transitory computer-readable media of claim 11 or 12, wherein instantiating the ECS comprises:

sending, by the ECSP management system, an instatateecsreq notification to an ECSP consumer;

Acquiring, by the ECSP management system, an ECS Virtual Network Function (VNF) software image from a software image location in the ECS LCM IE;

sending, by the ECSP management system, a request to instantiate the ECS to a Network Function Virtualization Orchestrator (NFVO) via an Os-Ma-NFVO interface;

sending, by the ECSP management system, an instatiateecsrresp to the ECSP consumer to notify the ECSP consumer that the ECS has been instantiated;

creating, by the ECSP management system, ECS VNF Management Object Instances (MOIs) from an ECS VNF Information Object Class (IOC); and

sending, by the ECSP management system, a notify MOI to the ECSP consumer to inform the ECSP consumer that the ECS VNF MOI has been created.

14. The one or more non-transitory computer-readable media of claim 13, wherein the instructions are further to:

identifying, by the ECSP management system, that the ECSP consumer has consumed the LCM MnS using an operational terminaeecsreq with an ECS instance identifier associated with the ECS; and

the ECS is terminated by the ECSP management system based on the operation terminatee ecsreq.

15. The one or more non-transitory computer-readable media of claim 14, wherein terminating the ECS comprises:

Sending, by the ECSP management system, a terminateecsrresp to the ECSP consumer;

sending, by the ECSP management system, a request to terminate the ECS to the NFVO via the Os-Ma-NFVO interface;

sending, by the ECSP management system, a notification to the ECSP consumer that the ECS has been terminated;

deleting the ECS VNF MOI by the ECSP management system; and

sending, by the ECSP management system, a notify moistureletion to the ECSP consumer to notify the ECSP consumer that the ECS VNF MOI has been deleted.

16. One or more non-transitory computer-readable media comprising instructions that, when executed by at least one processor of an electronic device, cause an Edge Computing Service Provider (ECSP) management system of the electronic device to:

identifying, by the ECSP management system, that an ECSP consumer has consumed a rationing management service (MnS) using an operational createMOI for an ECSLcm Information Object Class (IOC); and

an Edge Configuration Server (ECS) is instantiated by an MnS producer (MnS-P) of the ECSP management system based on the operational createMOI.

17. The one or more non-transitory computer-readable media of claim 16, wherein the ECSlcm IOC includes an ECS Virtual Network Function (VNF) IE and an indication of one or more virtual computing resources.

18. The one or more non-transitory computer-readable media of claim 16 or 17, wherein instantiating the ECS comprises:

obtaining, by the ECSP management system, an ECS Virtual Network Function (VNF) software image from a software image location in the ECSLcm IOC;

creating the ECSLcm MOI by the ECSP management system; and

sending, by the ECSP management system, a notify MOI to the ECSP consumer to notify the ECSP consumer that the ECSLcm MOI has been created.

19. The one or more non-transitory computer-readable media of claim 18, wherein the instructions are further to:

identifying, by the ECSP management system, that the ECSP consumer has consumed the rationed MnS using an operation deleteMOI having an ECS instance identifier associated with the ECS; and

terminating, by the ECSP management system, the ECS based on the operation deleteMOI.

20. The one or more non-transitory computer-readable media of claim 19, wherein terminating the ECS comprises:

Deleting the ECSLcm MOI by the ECSP management system; and

sending, by the ECSP management system, a notify moistureletion to the ECSP consumer to notify the ECSP consumer that the ECSLcm MOI has been deleted.