CN117426078A

CN117426078A - Method and apparatus for enhanced lifecycle management in a 5G edge computing server

Info

Publication number: CN117426078A
Application number: CN202280040226.7A
Authority: CN
Inventors: J·舒; 姚羿志
Original assignee: Intel Corp
Current assignee: Intel Corp
Priority date: 2021-08-11
Filing date: 2022-08-09
Publication date: 2024-01-19
Also published as: WO2023018727A1; EP4385184A1

Abstract

The present disclosure is directed to systems and methods for provisioning management service (MnS) producers at an Edge Computing Service Provider (ECSP) management system in a wireless network. The ECSP may detect a request to create a Managed Object Instance (MOI), the request received from an Application Service Provider (ASP), including a deployment requirement; encoding a response to the request, the response indicating that instantiation is in progress; selecting a number of Edge Data Network (EDN) and Edge Application Server (EAS) instances to instantiate based on the deployment requirements; detecting an EAS Virtualized Network Function (VNF) software image received based on a deployment requirement; requesting one or more EAS VNF instances of the software image to be instantiated by a Network Function Virtualization Orchestrator (NFVO); detecting an instantiated result; and encoding a notification based on the instantiation, the notification including an indication that the result is a deployment or failure.

Description

Method and apparatus for enhanced lifecycle management in a 5G edge computing server

Cross Reference to Related Applications

The present application claims the benefit of U.S. provisional application No. 63/232,066, filed 8/11 at 2021, the disclosure of which is incorporated herein by reference in its entirety.

Technical Field

The present disclosure relates generally to the field of wireless communications, and more particularly, to methods and apparatus related to lifecycle management in an edge computing server.

Background

Next generation mobile networks, particularly third generation partnership project (3 GPP) systems such as fifth generation (5G) and Long Term Evolution (LTE), and their evolution, are one of the latest cellular wireless technologies developed to deliver data rates ten times faster than LTE, and are deploying multiple carriers in the same area and across multiple spectral bands. 5G changes the network architecture of previous wireless networks by fundamentally converting network provisioning into an application-centric concept. To implement application-centric networks, the 5G New Radio (NR) introduces edge computing through a distributed computing framework that implements network slicing and combinable networks, providing faster, more thorough data processing and faster response times by bringing enterprise applications closer to data sources such as local edge servers. Improvements in network architecture enable data to be processed closer to where the data was created. What is needed is a system and method for provisioning an edge application server to take advantage of the data processing available in 5G edge computing.

Drawings

The detailed description is given below with reference to the accompanying drawings. The use of the same reference numbers may indicate similar or identical items. Various embodiments may utilize elements and/or components other than those illustrated in the figures, and some elements and/or components may not be present in the various embodiments. Elements and/or components in the figures are not necessarily drawn to scale. Throughout the present disclosure, singular and plural terms may be used interchangeably, depending on the context.

Fig. 1 illustrates an exemplary block diagram showing roles and relationships of service providers deploying edge computing services according to an embodiment of the present disclosure.

Fig. 2 illustrates a block diagram of a management system framework supporting lifecycle management, according to an embodiment of the present disclosure.

Fig. 3 is a timing flow diagram illustrating the deployment of an edge computing service according to an embodiment of the present disclosure.

Fig. 4 is a timing flow diagram illustrating termination of an edge computing service according to an embodiment of the present disclosure.

Fig. 5 illustrates a flow chart of a method according to an embodiment of the present disclosure.

Fig. 6 illustrates an exemplary network in accordance with various embodiments of the present disclosure.

Fig. 7 illustrates an exemplary wireless network in accordance with various embodiments of the present disclosure.

Fig. 8 illustrates a non-transitory machine-readable storage medium according to various embodiments of the disclosure.

Detailed Description

In general overview, the present disclosure generally relates to systems and methods for supporting provisioning of edge servers and Application Service Providers (ASPs) in 5G systems. 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 such as the particular architecture, interfaces, techniques, etc., in order to provide a thorough understanding of various aspects of the various embodiments. However, it will be apparent to one having ordinary skill in the art having had the benefit of the present disclosure that the various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In certain 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).

With the densification of millimeter wave small cells, fifth generation (5G) networks are becoming more and more complex, and various new services, such as eMBB (enhanced mobile broadband), URLLC (ultra reliable low latency communication), and emtc (large scale machine type communication), are characterized by high data volume at high speed, low speed, ultra low latency, and low data volume transmission from a large number of emerging smart devices, respectively. For 5G networks, it is a challenging task to dynamically and efficiently allocate resources among multiple network nodes to support various services. The allocation of resources is known as provisioning and becomes more important for edge servers such as Edge Application Servers (EAS) to fairly allocate and provision network services for each EAS.

In 5G communications defined by the 3GPP standards, an Application Service Provider (ASP) may be responsible for creating Edge Application Servers (EAS) and Application Clients (AC). EAS resides in an Edge Data Network (EDN) to perform server functions. The AC resides in a User Equipment (UE) device to perform client functions.

An Edge Computing Service Provider (ECSP) is responsible for the deployment of an EDN that includes EAS and an Edge Enabled Server (EES) that provides configuration information to Edge Enabled Clients (EECs) that enable AC in the UE to exchange application data traffic with the EAS. PLMN operators are responsible for deployment of 5G network functions such as 5GC (5G core) and 5G NR (5G new radio).

However, there is a need for enhanced systems and methods to support lifecycle management of EAS.

In one or more embodiments, the purpose of the present disclosure is to enable an ASP to deploy EAS in an EDN by requesting deployment requirements (e.g., topology or geographic service areas, software image information, and QoS) to provision MnS producers to deploy EAS. The supply MnS producer returns a response indicating that the operation is in progress to prevent the consumer from waiting, as deployment in the edge cloud may take a period of time. It then analyzes the deployment requirements to determine where multiple EAS VNF instances should be instantiated, and requests NFVO in ETSI NFV MANO to instantiate EAS VNF instances. Upon receiving a notification from the NFVO indicating the result of the instantiation operation, the provisioning MnS producer sends a notification to the ASP indicating the result of the instantiation (e.g., success, failure, or partial failure).

In one or more embodiments, the requirements may include the ability of the provisioning MnS producer to allow an authorized consumer to request deployment of EAS based on a given deployment requirement, the ability of the provisioning MnS producer to notify the authorized consumer of the progress of the instantiation in response to the deployment request, and the ability of the provisioning MnS producer to notify the authorized consumer of the outcome (e.g., success, failure, or partial failure) of the instantiation operation.

In one or more embodiments, an object of the present disclosure is to terminate EAS in EDNs by requesting the supply MnS producer to terminate EAS VNF instances. The provision MnS producer requests NFVO in ETSI NFV MANO to terminate EAS VNF instances. Upon receiving a notification from the NFVO indicating the start of the termination operation, the provision MnS producer sends a notification to the ASP indicating that termination is in progress. Upon receiving a notification from the NFVO indicating the termination operation result, the provision MnS producer sends another notification to the ASP indicating the termination result (e.g., success, failure, or partial failure).

In one or more embodiments, the requirements may include the ability of the provisioning MnS producer to allow the authorized consumer to request termination of the EAS VNF instance, the ability of the provisioning MnS producer to notify the authorized consumer of termination progress as a response to the termination request, and the ability of the provisioning MnS producer to notify the authorized consumer of the outcome (e.g., success, failure, partial failure) of the termination operation.

In one or more embodiments, a provisioning MnS (management service) producer at an ECSP management system may receive a createMOI request from an ASP that is a consumer of provisioning MnS with deployment requirements to request deployment of EAS; sending a createMOI response to the ASP, wherein the output parameter indicates that deployment is in progress; analyzing the deployment requirements to determine which EDN and how many EAS instances should be instantiated to meet the deployment requirements; downloading an EAS VNF software image from the software image location; requesting NFVO (NFV orchestration) instantiation of one or more EAS VNF instances; evaluating the results of the EAS VNF instantiation; and sending a notification to the ASP based on the result of the EAS VNF instantiation to indicate the result of the EAS deployment.

In one or more embodiments, deployment requirements are contained in an EASLcm IOC (information object class) and include (but are not limited to) the following attributes: the UE may access a service area (i.e., geographic or topological) of the edge computing service; software image information (e.g., software image location, minimum RAM, disk requirements); qoS requirements.

In one or more embodiments, to instantiate each EAS VNF instance, the ECSP provisioning MnS producer may invoke an instatatensrequest operation to request NFVO via the Os-Ma-NFVO interface to instantiate the EAS VNF instance; receiving an NS lifecycle change notification from the NFVO indicating the start of the instantiation procedure; and receive an NS lifecycle change notification from the NFVO indicating a result of the instantiation procedure.

In one or more embodiments, if the result of the NS periodic change notification is successful, the ECSP provisioning MnS producer may create an MOI for the easf section IOC; sending a notification to the ASP of notify MOICation to indicate that the EASFunit MOI has been created; and sends a notification notify to the ECSP to indicate that the easf section MOI has been created.

In one or more embodiments, if the result in the NS lifecycle change notification is not successful, the ECSP provisioning MnS producer may send a notification to the ASP indicating that the easf section MOI has not been created due to the failure; and sends a notification notify to the ECSP to indicate that the easf connection MOI has not been created due to the failure.

In one or more embodiments, the evaluation of EAS VNF instantiation may indicate one of the following results: all VNF instances have been successfully instantiated; not all VNF instances have been successfully instantiated; or no VNF instance is successfully instantiated.

In one or more embodiments, if all VNF instances have been successfully instantiated, the ECSP provisioning MnS producer may create an MOI for the EASLcm IOC; sending a notification to the ASP that the EASLcm MOI has been created; and sends a notification to ECSP to indicate that EASLcm MOI has been created.

In one or more embodiments, if not all VNF instances have been successfully instantiated, the ECSP provisioning MnS producer may create an MOI for the EASLcm IOC; sending a notification to the ASP of notify MOICation to indicate that the EASLcm MOI has been partially created; and sends a notification to ECSP that notify MOICation indicates that EASLcm MOI has been partially created.

In one or more embodiments, if no VNF instance is successfully instantiated, the ECSP provisioning MnS producer may send a notification to the ASP indicating that EASLcm MOI has not been created; and sends a notification to ECSP to indicate that EASLcm MOI has not been created.

In one or more embodiments, a provisioning MnS (management service) producer at an ECSP management system may receive a deleteMOI operation of an easf section MOI from an ASP that is a consumer of the provisioning MnS to terminate an EAS VNF instance; transmitting a deleteMOI response to the ASP, wherein the output parameter indicates that termination is in progress; invoking a terminatee nsrequest operation to request the NFVO to terminate the EAS VNF instance via the Os-Ma-NFVO interface; receiving an NS lifecycle change notification from the NFVO indicating the start of the termination procedure; receive an NS lifecycle change notification from the NFVO indicating a termination procedure result; and sending a notification to the ASP to indicate a result of the EAS deployment based on the result of the EAS VNF termination.

In one or more embodiments, if the result of the NS lifecycle change notification is successful, the ECSP provisioning MnS producer may delete the MOI of the easf section IOC; sending a notification to the ASP to indicate that the EASFunit MOI has been deleted; and sends a notification notify to the ECSP to indicate that the easf section MOI has been deleted.

In one or more embodiments, if the result in the NS lifecycle change notification is not successful, the ECSP provisioning MnS producer may send a notification to the ASP to indicate that deletion of the easf section MOI has failed; and sends a notification notify to the ECSP to indicate that the deletion of the easf section MOI has failed.

Referring now to FIG. 1, a block diagram illustrates the roles and relationships of service providers deploying edge computing services. As shown, a Public Land Mobile Network (PLMN) operator 102 is responsible for the deployment of 5G network functions, such as 5G core network functions 106 and 5G New Radios (NRs) 108. The PLMN operator 102 is coupled to an edge computing service provider 110 representing an edge data network 114, the edge data network 114 including an edge application server 116 and an Edge Enabling Server (EES) 118. Edge computing service provider 110 is shown connecting EAS server 116 to application service provider 120 via edge computing application programming 122. The application service provider 120 holds an edge application 124 represented by an EAS server and an Application Client (AC) 128.

An Application Service Provider (ASP) 120 is responsible for creating EAS servers that reside in an Edge Data Network (EDN) to perform server functions. An Application Client (AC) typically resides in a User Equipment (UE) and performs client functions.

Each Edge Computing Service Provider (ECSP) 110 is responsible for deployment if there is an edge data network that holds EAS and EES. The EAS and EES provide configuration information to Edge Enabled Clients (EECs) and enable application clients in the UE to exchange application data traffic with the EAS application client 128.

Referring now to FIG. 2, a block diagram illustrates a management system framework 200 that supports lifecycle management for edge computing. As shown, an Application Service Provider (ASP) 202 holds a management service consumer (MnS-C) 204, and an Edge Computing Service Provider (ECSP) 210 also holds a MnS-C214.

The Provisioning management service (MnS) 220 is shown as part of an ECSP management system 230, which ECSP management system 230 is responsible for Provisioning management services (MnS-P) 232 and MnS-P234. Edge application server virtual network functions (EAS VNFs) 240 and 242 are shown coupled to ECSP management system 230.

ECSP management system 230 is shown connected to ETSI network function virtualization management and orchestration (NFV MANO) 260, which hosts Network Function Virtualization Orchestrator (NFVO) 266. More specifically, ECSP management system 230 is coupled to NFVO 266 via an interface referred to as open source managed orchestrator network function virtualization orchestrator (Os-Ma-NFVO) interface 250.

Embodiments herein are directed to supporting lifecycle management for Edge Application Servers (EAS). More importantly, one or more embodiments of the present disclosure apply to 3gpp ts28.538, and embodiments are directed to Mobility Robustness Optimization (MRO).

One or more embodiments are directed to enabling an ASP to deploy edge application servers in an Edge Data Network (EDN) by requesting deployment requirements, such as topology and geographic service areas, software image information, and quality of service requirements (QoS), to a provisioning MnS (MnS-P) producer to deploy EAS.

For example, in FIG. 2, mnS-P232 and 234 producers return a response to ASP 202 indicating that the operation supply is in progress to prevent consumers from waiting, as deployment in the edge cloud may take some time. ECSP management system 230, including MnS-P232 and 234, analyzes the deployment requirements to determine where EAS VNF instances, such as EAS VNFs 240 and 242, should be instantiated and how many EAS VNF instances are instantiated, and requests NFVO 266 in ETSI NFV MANO 260 to instantiate EAS VNF instances, such as EAS VNFs 240 and 242. Upon receiving a notification from NFVO 266 indicating the result of the instantiation operation, a provisioning MnS producer, such as MnS-P232, sends a notification to ASP 202 indicating the result of the instantiation (success, failure, or partial failure).

In one or more embodiments, the command REQ-EAS-INST-FUN-1 from the supply MnS producer allows authorized consumers to request deployment of EAS based on given deployment requirements.

In one or more embodiments, the command REQ-EAS-INST-FUN-2 specifies to provision the MnS producer to inform the authorized consumer about the progress of the instantiation as a response to the deployment request.

In one or more embodiments, the command REQ-EAS-INST-FUN-3 specifies that the MnS producer be provisioned to notify authorized consumers of the result of the instantiation operation, such as success, failure, or partial failure.

In one or more embodiments, EAS in the edge data network is terminated by requesting the supply MnS producer to terminate an EAS VNF instance. More specifically, as shown in FIG. 2, supply MnS producers 232 and 234 request NFVO 266 to terminate EAS VNF instances 240 and 242 via an Os-Ma-NFVO interface 250 (ETSI NFV MANO). Upon receiving a notification from NFVO 266 indicating the start of a termination operation, a supplied MnS producer, such as MnS-P232, sends a notification to ASP 202 indicating that termination is in progress. Upon receiving a notification from NFVO 266 indicating the result of the termination operation, supply MnS producer 232 next sends another notification to ASP 202 indicating the result of the termination, such as success, failure, or partial failure.

There are three required commands for termination, similar to the command REQ-EAS-TERM-FUN-1 described above, that specifies that the supply MnS producer 232 allows authorized consumers, such as MnS-C204, to request termination of EAS VNF instances, such as 240 and 242. REQ-EAS-TERM-FUN-2 specifies that supply MnS producer 232 notify authorized consumers such as MnS-C204 of the progress of termination as a response to a termination request. REQ-EAS-TERM-FUN-3 specifies that supply MnS producer 232 notifies authorized consumers such as MnS-C204 of the result of terminating the operation, such as success, failure, partial failure.

Referring now to fig. 2 and 3, one or more embodiments relate to a procedure for EAS lifecycle management, and more particularly, to how an ASP consumes offerings, such as offerings from MnS-P232, to deploy EAS, such as EAS VNF 240 or 242.

FIG. 3 shows a timing diagram 300 and assumes that an ECSP consumer, such as ECSP 210, subscribes to receive notifications from MnS-P producers, such as MnS-P234. Fig. 3 shows ASP 302 as a consumer of supplied MnS, ECSP 304 as a consumer of supplied MnS, ECSP 306 as a producer of supplied MnS, and ETSI NFV MANO NFVO as a network function virtualization orchestrator.

As shown, the provisioning begins with a createMOI operation 310 as provided in clause 11.1.1.1 in TS28.532, for an EASLcm Information Object Class (IOC) request ECSP provisioning, and for a MnS producer to initiate an EAS VNF instantiation. Those skilled in the art will appreciate, with the benefit of this disclosure, that MnS component type a provides services to manage the lifecycle of IOC instances (IOC instances also referred to as Managed Object Instances (MOIs), or simply managed objects), and to set the attributes of the MOIs, as well as to provide performance guarantees and fault supervision for the MOIs. For provisioning, EASLcm IOC contains deployment requirements, including at least the following attributes: according to clause 7.3.3 in TS28.558, the ue may access the service area (e.g., geography or topology) of the edge computing service, software image information (such as software image location, minimum RAM, disk requirements), qoS requirements (such as bandwidth, end-to-end latency).

ECSP provisioning MnS producer 306 returns an output parameter to ASP 302 indicating that the instantiation operation is proceeding using createMOI output parameter 312.

Next, at 314, ecsp 306 analyzes the requirements to determine how many EAS VNFs should be instantiated and where. Thus, ECSP provisioning MnS producer 306 analyzes the deployment requirements to determine which EDN and how many EAS instances should be instantiated to meet the deployment requirements, and downloads the EAS VNF software image from the software image location.

Once completed, the looping process begins by instantiating one or more EAS VNFs at step 316. In step 318, ecsp provisioning MnS producer 306 invokes an instalatensrequest operation to request NFVO 308 to instantiate an EAS VNF instance via the Os-Ma-NFVO interface. To achieve this, an InstantiateNSRequest instantiates an EAS VNF. At step 320; nsLcmOperation OccurenceNotification is sent from NFVO 308 to ECSP 306 at step 320 to indicate the start of EAS instantiation. In other words, NFVO 308 sends an NS lifecycle change notification to ECSP provisioning MnS producer 306 indicating the start of the instantiation procedure. At step 322, an NsLcm operation OccurrenceNotification is sent at step 322 to indicate the result of the EAS instantiation. In other words, NFVO 308 sends an NS lifecycle change notification to ECSP provisioning MnS producer 306 indicating the result of the instantiation procedure.

If the VNF instantiation has been successful at 330, then creation of an MOI for the easf connection IOC 332 occurs, followed by notify of ASP EASFunction MOI that it has been created 334, which is sent from ECSP 306 to ASP 302.

Next, the ECSP producer 306 notifies the ECSP consumer 304 via notify moicration that the easf section has been created at step 338.

If the VNF instantiation fails at 340, then at step 342, ecsp producer 306 notifies ASP 302 that creation of the easf connection MOI has failed. The notification is that notify moicontrol has not been created due to failure.

The ECSP producer 306 then notifies 344 the ECSP consumer 304 via notify MOICation that the creation of the EASFunit MOI has failed.

The loop from step 316 may then be repeated by instantiating another EAS VNF.

If all VNF instances are successfully instantiated 350, then at step 352, ecsp producer 306 creates an MOI for the EASLCM IOC. ECSP producer 306 then notifies ASP 302 via notify mocalization to create an MOI for EASLcm IOC at 354.

Next, at 356, ECSP provisioning MnS producer 306 sends notification to ECSP consumer 304 that EASLcm MOI has been created.

If not all VNF instances are instantiated at 358, then at step 360 ECSP producer 306 creates an MOI for EASLCM IOC and ECSP producer 306 also notifies at 362 ASP 302 that EASLCM MOI has been partially created. The ECSP producer 306 also notifies the ECSP consumer 304 that the EASLcm MOI has been partially created via notify MOICRELATION at step 364.

If no VNF instance has been successfully instantiated at 366, then at step 368 ecsp provisioning MnS producer 306 sends a notification to ASP 302 to indicate that EASLcm MOI has not been created due to the failure. Next, at step 370, ecsp provisioning MnS producer 306 notifies ASP 302 with notify MOI that the easf section MOI has not been created at step 368. Finally, at step 370, ECSP Provisioning MnS producer 306 sends a notification to ECSP consumer 304 to indicate that EASLcm MOI has not been created due to the failure.

Referring now to fig. 4, a timing diagram 400 illustrates a procedure describing how an ASP consumes supplied MnS to terminate an EAS VNF. Assume that both the ASP and ECSP consumers have subscribed to the producer of supplied MnS to receive notifications.

As shown, the protocol includes interactions between an ASP 402 consumer of MnS, an ECSP 404 consumer of MnS, an ECSP 406 producer of MnS, and an NFVO 408ETS NFV MANO orchestrator.

Termination begins with a deleteMOI of EASFunit, step 410, where ASP 402 consumes the supplied MnS using a deleteMOI operation of the EASFunit MOI to request ECSP supplied MnS producer 406 to begin an EAS VNF termination.

In response, at step 412, ecsp provisioning MnS producer 406 returns an output parameter to ASP 402 indicating that a termination operation is in progress.

Next, at step 414, ecsp provisioning MnS producer 406 sends a terminatee nsrequest operation to NFVO 408 to request that NFVO terminate the EAS VNF instance via the Os-Ma-NFVO interface. As shown in FIG. 2, the Os-Ma-NFVO interface 250 is coupled to the NFVO 266 and the ECSP management system 230 to fulfill termination requests.

In response, NFVO 408 sends an NS lifecycle change notification to ECSP provisioning MnS producer 406 indicating the start of the termination procedure at step 416 using NsLcmOperation OccurrenceNotification to indicate the start of EAS termination and the result of EAS termination at step 418.

If the eas VNF termination is successful at 420, ecsp provisioning MnS producer 406 deletes the MOI of EASLcm IOC at 422. At step 424, ECSP Provisioning MnS producer 406 sends a notification to notify ASP 402 that the EASFunit MOI has been deleted.

Next, at step 426, ECSP provisioning MnS producer 406 notifies ECSP 404 of the provisioning MnS via notify consumer easf section MOI has been deleted.

If the EAS VNF termination fails at 430, step 432 specifies that ECSP provisioning MnS producer 406 send a notification to ASP 402 to indicate that the easf section MOI has not been deleted due to the failure.

Finally, at step 434, ECSP provisioning MnS producer 406 sends a notification to ECSP consumer provisioning MnS that easf connectionmoi has failed.

Referring now to fig. 5, a flow chart 500 is concurrent with an embodiment of a process for provisioning. As shown, at block 502, an ECSP may detect a request for ECSP provisioning received from an Application Service Provider (ASP) consumer that provisions managed services (MnS). For example, an ASP, which is a consumer of supplied MnS with deployment requirements, requests to deploy an EAS as an ECSP supply, as shown in FIG. 2, ASP 202 requests the supply from ECSP management system 230. The request for ECSP provisioning includes a request to create a Managed Object Instance (MOI) from an Application Service Provider (ASP) that acts as a consumer to provision MnS with deployment requirements to request deployment of EAS. The request may include a requirement for an Edge Application Server (EAS) virtualized network function. As shown in fig. 2, ECSP management system 230 receives the request and determines the requirements.

At block 504, the ecsp may encode the response to the request to indicate (e.g., to the requesting ASP) that instantiation is in progress.

At block 506, the ecsp may select the number of EDN and EAS instances to instantiate based on the deployment requirements.

At block 508, the ecsp may detect an EAS VNF software image received based on the deployment requirements.

At block 510, the ecsp may request instantiation of a Network Function Virtualization Orchestrator (NFVO) based on the requirements of the EAS virtualized network function. For example, as shown in FIG. 2, ECSP management system 230 requests instantiation from NFVO 266 via os-ma-NFVO interface 250. In one embodiment, after determining the requirements, the ECSP provisioning system may send output parameters indicating that deployment is in progress. In one embodiment, determining the requirement may include analyzing the deployment requirement to determine a number of EAS instances that should be instantiated to meet the deployment requirement. Once the requirements are determined, embodiments include downloading an EAS Virtualization Network Function (VNF) software image from a software image location and requesting instantiation of one or more EAS VNF instances from the downloaded software image through a Network Function Virtualization Orchestrator (NFVO), such as NFVO 266.

At block 512, the ecsp may detect the result of the instantiation, which may be a deployment or failure. Deployment occurs only when all the requested instances have been instantiated. Alternatively, partial deployment may occur when a subset of the requested instances have been instantiated, while one or more other requested instances have not been instantiated.

At block 514, the ecsp may encode the result of instantiating the EAS VNF as a notification to the ASP consumer that is supplying MnS. For example, ECSP management system 230 sends notifications, such as instantiation results, to ASP 202. In one embodiment, sending the notification includes sending a response to the ASP 202 with an output parameter indicating that deployment is in progress. In one embodiment, sending the notification to the ASP includes a notification based on an EAS VNF instantiation indicating deployment, failure, or partial failure.

System and embodiment

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

Fig. 6 illustrates a network 600 in accordance with various embodiments. The network 600 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G/NR systems. However, the example embodiments are not limited in this regard and the described embodiments may be applied to other networks that benefit from the principles described herein, such as future 3GPP systems, and the like.

Network 600 may include a UE 602, and UE 602 may include any mobile or non-mobile computing device designed to communicate with RAN 604 via an over-the-air connection. The UE 602 may be communicatively coupled with the RAN 604 through a Uu interface. The UE 602 may be, but is not limited to, a smart phone, tablet, wearable computer device, desktop, laptop, in-vehicle infotainment device, in-vehicle entertainment device, instrument cluster, heads-up display device, in-vehicle diagnostic device, dashboard mobile equipment, 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, network 600 may include multiple UEs directly coupled to each other via a side link interface. The UE may be an M2M/D2D device that communicates using a physical side link channel such as, but not limited to PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.

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

RAN 604 may include one or more access nodes, such as AN 608.AN 608 may terminate the air interface protocol of UE 602 by providing access stratum protocols including RRC, PDCP, RLC, MAC and L1 protocols. In this way, the AN 608 may enable data/voice connectivity between the CN 620 and the UE 602. In some embodiments, AN 608 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 608 is referred to as BS, gNB, RAN node, eNB, ng-eNB, nodeB, RSU, TRxP, TRP, etc. AN 608 may be a macrocell base station or a low power base station for providing femto cells, pico cells, or other similar cells having a smaller coverage area, smaller user capacity, or higher bandwidth than a macrocell.

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

The ANs of the RAN 604 may each manage one or more cells, groups of cells, component carriers, etc. to provide AN air interface for network access to the UE 602. The UE 602 may be connected with multiple cells provided by the same or different ANs of the RAN 604 at the same time. For example, the UE 602 and the RAN 604 may use carrier aggregation to allow the UE 602 to connect with multiple component carriers, each component carrier corresponding to one 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 604 may provide the air interface over licensed spectrum or unlicensed spectrum. To operate in unlicensed spectrum, a node may use LAA, eLAA, and/or feLAA mechanisms based on CA technology with PCell/Scell. Before accessing the unlicensed spectrum, the node may perform media/carrier sense operations based on, for example, a Listen Before Talk (LBT) protocol.

In a V2X scenario, the UE 602 or AN 608 may be or act as AN RSU, which may refer to any transport infrastructure entity for V2X communications. The RSU may be implemented in or by a suitable AN or a fixed (or relatively fixed) UE. An RSU implemented in or by a UE may be referred to as a "UE-type RSU"; the eNB may be referred to as an "eNB RSU"; the gNB may be referred to as a "gNB type RSU" or the like. In one example, the RSU is a computing device coupled with radio frequency circuitry located at the roadside that provides connection support for the passing vehicle UE. The RSU may also include internal data storage circuitry that stores geometry, traffic statistics, media, and applications/software for the intersection map to sense and control ongoing vehicle and pedestrian traffic. The RSU may provide extremely low latency communications required for high speed events such as avoiding collisions, traffic alerts, and the like. Additionally or alternatively, the RSU may provide other cellular/WLAN network 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 to provide a wired connection (e.g., ethernet) to a traffic signal controller or backhaul network.

In some embodiments, the RAN 604 may be an LTE RAN 610 with an eNB, e.g., eNB 612.LTE RAN 610 may provide an LTE air interface with the following features: SCS of 16 kHz; a CP-OFDM waveform for DL and an SC-FDMA waveform for UL; turbo codes for data, TBCCs for control, etc. The LTE air interface can rely on the CSI-RS for CSI acquisition and beam management; PDSCH/PDCCH demodulation is performed in dependence on PDSCH/PDCCH DMRS; and cell search and initial acquisition depending on CRS, channel quality measurements, and channel estimation for coherent demodulation/detection at the UE. The LTE air interface may operate in the frequency band below 6 GHz.

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

In some embodiments, the NG interface may be split 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 614 and UPF 648, and a NG control plane (NG-C) interface that is a signaling interface (e.g., an N2 interface) between the node of NG-RAN 614 and AMF 4544.

NG-RAN 614 may provide a 5G-NR air interface with the following features: a variable SCS; CP-OFDM for DL and CP-OFDM and DFT-s-OFDM for UL; polar codes for control, repetition codes, unitary 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; phase tracking using PTRS for PDSCH; and using the tracking reference signal for time tracking. The 5G-NR air interface may operate on an FR1 band including a frequency band below 6GHz or an FR2 band including a frequency 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, the UE 602 may be configured with multiple BWP, where each BWP configuration has a different SCS. When a BWP change is indicated to the UE 602, the SCS of the transmission is also changed. Another example of use case of BWP relates to power saving. In particular, the UE 602 may be configured with multiple BWPs having different numbers of frequency resources (e.g., PRBs) to support data transmission under different traffic load conditions. BWP containing a smaller number of PRBs may be used for data transmission with small traffic load while allowing power saving at the UE 602 and in some cases at the gNB 616. BWP comprising a larger number of PRBs may be used for scenarios with higher traffic load.

The RAN 604 is communicatively coupled to a CN 620 that includes network elements to provide various functions to support data and telecommunications services to clients/users (e.g., users of the UE 602). The components of CN 620 may be implemented in one physical node or in a separate physical node. In some embodiments, NFV may be used to virtualize any or all of the functionality provided by the network elements of CN 620 onto physical computing/storage resources in servers, switches, and the like. The logical instance of CN 620 may be referred to as a network slice, and the logical instance of a portion of CN 620 may be referred to as a network sub-slice.

In some embodiments, CN 620 may be LTE CN 622, which may also be referred to as EPC. LTE CN 622 may include MME 624, SGW 626, SGSN 628, HSS 630, PGW 632, and PCRF 634 coupled to each other by interfaces (or "reference points"). The function of the elements of LTE CN 622 may be briefly described as follows.

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

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

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

HSS 630 may include a database of network users that includes subscription-related information to support communication session handling for network entities. HSS 630 may provide support for routing/roaming, authentication, authorization, naming/address resolution, location dependencies, and so on. The S6a reference point between HSS 630 and MME 4 624 may enable the transfer of subscription and authentication data to verify/authorize user access to LTE CN 620.

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

PCRF 634 is a policy and charging control element of LTE CN 622. PCRF 634 is communicatively coupled to application/content server 638 to determine appropriate QoS and charging parameters for the service flows. PCRF 632 may provide the relevant rules to the PCEF with the appropriate TFTs and QCIs (via Gx reference points).

In some embodiments, CN 620 may be 5gc 640. The 5gc 640 may include AUSF 642, AMF 644, SMF 646, UPF 648, NSSF 650, NEF 652, NRF 654, PCF 656, UDM 658, and AF 660 coupled to each other through interfaces (or "reference points") as shown. The function of the elements of the 5gc 640 may be briefly described as follows.

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

The AMF 644 may allow other functions of the 5gc 640 to communicate with the UE 602 and the RAN 604 and subscribe to notifications of mobility events related to the UE 602. The AMF 644 may be responsible for registration management (e.g., registering the UE 602), connection management, reachability management, mobility management, lawful intercept AMF related events, and access authentication and authorization. The AMF 644 may provide transport for SM messages between the UE 602 and the SMF 646 and act as a transparent proxy for routing SM messages. The AMF 644 may also provide for transmission of SMS messages between the UE 602 and the SMSF. The AMF 644 may interact with the AUSF 642 and the UE 602 to perform various security anchors and context management functions. Furthermore, the AMF 644 may be an end point of the RAN CP interface, which may include or may be an N2 reference point between the RAN 604 and the AMF 644; and the AMF 644 may be the termination point for NAS (N1) signaling and perform NAS ciphering and integrity protection. The AMF 644 may also support NAS signaling with the UE 602 over the N3 IWF interface.

The SMF 646 may be responsible for SM (e.g., session establishment, tunnel management between UPF 648 and AN 608); UE IP address assignment and management (including optional authorization); selection and control of the UP function; configuring traffic steering at UPF 648 to route traffic to the appropriate destination; terminating the interface facing the policy control function; a portion controlling policy enforcement, charging, and QoS; lawful interception (for SM events and interfaces to LI systems); terminating the SM portion of the NAS message; downlink data notification; AN-specific SM information is initiated and sent to AN 608 via AMF 644 over N2; 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 PDU exchanges between the UE 602 and the data network 636.

The UPF 648 may serve as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point interconnected with the data network 636, and a branching point to support multi-homing PDU sessions. The UPF 648 may also perform packet routing and forwarding, perform packet inspection, implement policy-rule 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 ratio enforcement), perform uplink traffic verification (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 648 may include an uplink classifier to support routing traffic to the data network.

NSSF 650 may select a set of network tile instances to serve UE 602. NSSF 650 may also determine allowed NSSAIs and mappings to subscribed S-NSSAIs, if desired. NSSF 650 may also determine, based on the appropriate configuration and possibly by querying NRF 654, a set of AMFs, or a list of candidate AMFs, for serving UE 602. The selection of the network tile instance set for the UE 602 may be triggered by the AMF 644 registered by the UE 602 by interacting with the NSSF 650, which may result in a change of AMF. NSSF 650 may interact with AMF 644 via an N22 reference point; and may communicate with another NSSF in the visited network via an N31 reference point (not shown). Furthermore, NSSF 650 may exhibit an interface based on the Nnssf service.

NEF 652 may securely expose services and capabilities provided by 3GPP network functions for third parties, internal exposure/re-exposure, AF (e.g., AF 660), edge computing or fog computing systems, and the like. In such embodiments, NEF 652 may authenticate, authorize, or throttle AF. NEF 652 can also translate information exchanged with AF 560 and with internal network functions. For example, NEF 652 may translate between AF-service-identifiers and internal 5GC information. The NEF 652 may also receive information from other NF's based on their exposure capabilities. This information may be stored as structured data at NEF 652 or at data store NF using a standardized interface. The stored information may then be re-exposed by the NEF 652 to other NFs and AFs, or used for other purposes, such as analysis. Furthermore, NEF 652 may exhibit an interface based on Nnef services.

NRF 654 may support service discovery functions, receive NF discovery requests from NF instances, and provide NF instances with information of discovered NF instances. NRF 654 also maintains information of available NF instances and services supported by them. As used herein, the terms "instantiate," "instantiate," and the like may refer to creating an instance, while "instance" may refer to a specific occurrence of an object, e.g., that may occur during execution of program code. Furthermore, NRF 554 may exhibit an Nnrf based service interface.

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

The UDM 658 may process subscription-related information to support communication session handling for network entities and may store subscription data for the UE 602. For example, subscription data may be communicated via an N8 reference point between UDM 658 and AMF 644. The UDM 658 may include two parts, an application front end and a UDR. The UDR may store subscription data and policy data for UDM 658 and PCF 656, and/or structured data for exposure and application data for NEF 652 (including PFD for application detection, application request information for multiple UEs 602). An interface based on Nudr services may be exposed by UDR 221 to allow UDM 658, PCF 656, and NEF 652 to access specific sets of stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notifications of related data changes in UDR. The UDM may include a UDM-FE responsible for handling credentials, location management, subscription management, etc. 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 658 may also present an interface based on Nudm services.

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

In some embodiments, the 5gc 640 may enable edge computation by selecting an operator/third party service to be geographically close to the point where the UE 602 attaches to the network. This may reduce delay and load on the network. To provide edge computing implementations, the 5gc 640 may select the UPF 648 in close proximity to the UE 602 and perform traffic steering from the UPF 648 to the data network 636 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by AF 660. In this way, AF 660 may affect UPF (re) selection and traffic routing. Based on the operator's deployment, the network operator may allow AF 660 to interact directly with the associated NF when AF 660 is considered a trusted entity. Furthermore, AF 660 may show an interface based on Naf services.

The data network 636 may represent various network operator services, internet access, or third party services that may be provided by one or more servers including, for example, the application/content server 638.

Referring now to fig. 7, a wireless network 700 in accordance with various embodiments is illustrated. The wireless network 700 may include a UE 702 in wireless communication with AN 704. The UE 702 and the AN 704 may be similar to and substantially interchangeable with the synonym components described elsewhere herein.

UE 702 may be communicatively coupled to AN 704 via connection 707. Connection 706 is shown as an air interface implementing a communicative coupling and may conform to a cellular communication protocol, such as the LTE protocol or the 5G NR protocol operating at millimeter wave or below 5 GHz.

UE 702 may include a primary platform 708 coupled to a modem platform 710. Host platform 708 may include application processing circuitry 712, which may be coupled with protocol processing circuitry 714 of modem platform 710. The application processing circuitry 712 may run various applications for the UE 702 that source/sink application data. The application processing circuit 712 may further implement one or more layer operations to transmit/receive application data to/from a data network. These layer operations may include transport (e.g., UDP) operations and internet (e.g., IP) operations.

Protocol processing circuitry 714 may implement one or more of the layer operations to facilitate the transmission or reception of data over connection 706. Layer operations implemented by the protocol processing circuit 714 may include, for example, MAC operations, RLC operations, PDCP operations, RRC operations, and NAS operations.

Modem stage 710 may further include digital baseband circuitry 716 that may implement one or more layer operations "below" the layer operations performed by protocol processing circuitry 714 in the network protocol stack. These operations may include, for example, PHY operations 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 space coding, reference signal generation/detection, preamble sequence generation and/or decoding, synchronization sequence generation/detection, control channel signal blind decoding, and other related functions.

Modem stage 710 may further include transmission circuitry 718, reception circuitry 720, radio frequency circuitry 722, and Radio Frequency Front End (RFFE) 724, which may include or be connected to one or more antenna panels 726. Briefly, the transmission circuit 718 may include digital-to-analog converters, mixers, intermediate Frequency (IF) components, and the like; the receive circuitry 720 may include analog-to-digital converters, mixers, IF components, etc.; the radio frequency circuit 722 may include a low noise amplifier, a power tracking component, and the like; RFFE 724 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 transmission circuit 718, the reception circuit 720, the radio frequency circuit 722, the RFFE 724, and the antenna panel 726 (commonly referred to as "transmission/reception components") may be specific to the specifics of the particular implementation, such as, for example, whether the communication is TDM or FDM, frequencies below millimeter waves or 5GHz, and so forth. 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 714 may include one or more control circuit instances (not shown) to provide control functions of the transmit/receive components.

UE reception may be established by and via antenna panel 726, RFFE 724, RF circuitry 722, receive circuitry 720, digital baseband circuitry 716, and protocol processing circuitry 714. In some embodiments, the antenna panel 726 may receive transmissions from the AN 704 through receive beamformed signals received by multiple antennas/antenna elements of one or more antenna panels 726.

UE transmissions may be established by and via protocol processing circuitry 714, digital baseband circuitry 716, transmission circuitry 718, RF circuitry 722, RFFE 724, and antenna panel 726. In some embodiments, the transmission component of the UE 704 may apply a spatial filter to the data to be transmitted to form a transmission beam that is transmitted by the antenna elements of the antenna panel 726.

Similar to UE 702, an 704 may include a host platform 728 coupled to a modem platform 730. The main platform 728 may include an application processing circuit 732 coupled with the protocol processing circuit 734 of the modem platform 730. The modem platform may further include digital baseband circuitry 736, transmit circuitry 738, receive circuitry 740, radio frequency circuitry 742, RFFE circuitry 744, and antenna panel 746. The components of the AN 704 may be similar to, and substantially interchangeable with, the same name components of the UE 702. In addition to performing data transmission/reception as described above, the components of the AN 708 may also perform various logical functions including, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.

Fig. 8 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. 8 shows a diagrammatic representation of a hardware resource 800 that includes one or more processors (or processor cores) 810, one or more memory/storage devices 820, and one or more communication resources 830, each of which may be communicatively coupled via a bus 840 or other interface circuitry. For embodiments that utilize node virtualization (e.g., NFV), hypervisor 802 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize hardware resources 800.

Processor 810 may include, for example, a processor 812 and a processor 814. The processor 810 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), DSP, ASIC, FPGA such as a baseband processor, etc., a Radio Frequency Integrated Circuit (RFIC), other processors (including those discussed herein), or any suitable combination thereof.

Memory/storage 820 may include main memory, disk storage, or any suitable combination thereof. Memory/storage 820 may include, but is not limited to, any type of volatile, nonvolatile, or semi-volatile memory such as 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, and the like.

Communication resources 830 may include interconnection or network interface controllers, components, or other suitable devices that communicate with one or more peripheral devices 804 or one or more databases 806 or other network elements via network 808. Communication resources 830 may include, for example, wired communication components (e.g., for coupling via USB, ethernet, etc.), cellular communication component, NFC component,(or->Low power consumption) component->Components and other communication components.

The instructions 850 may include software, programs, applications, applets, applications, or other executable code that causes at least any of the processors 810 to perform any one or more of the methods discussed herein. The instructions 850 may reside, completely or partially, within at least one of the processors 810 (e.g., within a cache memory of the processor), the memory/storage device 820, or any suitable combination thereof. Further, any portion of the instructions 850 may be transferred from any combination of the peripheral 804 or the database 806 to the hardware resource 800. Thus, the memory of processor 810, memory/storage 820, peripherals 804, and database 806 are examples of computer readable and machine readable media.

The following examples relate to further embodiments.

Example 1 may be an apparatus of an Edge Computing Service Provider (ECSP) for provisioning a management service (MnS) producer at the ECSP in a wireless network, the apparatus comprising: a memory; processing circuitry coupled to the memory, the processing circuitry configured to: detecting a request to create a Managed Object Instance (MOI), the request received from an Application Service Provider (ASP), the request including deployment requirements; encoding a response to the request for transmission to the ASP, the response indicating that instantiation is in progress; selecting a number of Edge Data Network (EDN) and Edge Application Server (EAS) instances to instantiate based on the deployment requirements; detecting an EAS Virtualized Network Function (VNF) software image received based on a deployment requirement; requesting one or more EAS VNF instances of the software image to be instantiated by a Network Function Virtualization Orchestrator (NFVO); detecting an instantiated result; and encoding a notification for transmission to the ASP based on the instantiation, the notification including an indication of whether the result is deployment or failure.

Example 2 may include the apparatus of example 1 and/or some other examples herein, wherein the deployment requirement is included in a requested EAS lifecycle management information object class (EASLcm IOC), and wherein the deployment requirement includes at least one of a service area, software image data, or quality of service (QoS) requirement for one or more User Equipment (UEs) accessible to the EDN.

Example 3 may include the apparatus of example 1 or example 2, and/or some other example herein, wherein the processing circuitry is further configured to: invoking an InstantiateNSRequest operation to request instantiation via an open source managed orchestrator network function virtualization orchestrator (Os-Ma-nfvo) interface; and detecting a network service lifecycle change notification received from the NFVO indicating the instantiated state.

Example 4 may include the apparatus of example 1 and/or some other examples herein, wherein the configured processing circuitry is further configured to: detecting that all of the one or more EAS VNF instances are successfully instantiated, wherein the result is deployment only when all of the one or more EAS VNF instances are successfully instantiated.

Example 5 may include the apparatus of example 4 and/or some other examples herein, wherein the configured processing circuitry is further configured to: an MOI is created for an EASFunit Information Object Class (IOC) based on the deployment result.

Example 6 may include the apparatus of example 5 and/or some other examples herein, wherein the notification further indicates that an MOI is created.

Example 7 may include the apparatus of example 1 and/or some other examples herein, wherein the processing circuitry is further configured to: detecting an EAS VNF instance of the one or more EAS VNF instances is not successfully instantiated.

Example 8 may include the apparatus of example 7 and/or some other examples herein, wherein the notification indicates that the result is a failure based on detection that the EAS VNF instance was not successfully instantiated.

Example 9 may include the apparatus of example 7 and/or some other examples herein, wherein the processing circuitry is further configured to: a second EAS VNF instance that detects one or more EAS VNF instances is successfully instantiated, wherein the notification indicates that the result is a partial deployment.

Example 10 may include a computer-readable storage medium containing instructions that, when executed by processing circuitry of an Application Service Provider (ASP), cause the processing circuitry to: encoding a request to create a Managed Object Instance (MOI) for transmission to an Edge Computing Service Provider (ECSP), the request including deployment requirements associated with one or more Virtual Network Function (VNF) instances that instantiate a software image of an edge application server; detecting a response received from the ECSP after the request, the response indicating that instantiation is in progress, and the ECSP to send a notification containing an indication of whether the instantiation result is deployment or failure; and detects a notification received from the ECSP after the response.

Example 11 may include the computer-readable medium of example 10 and/or some other examples herein, wherein the deployment requirement is included in a requested EAS lifecycle management information object class (EASLcm IOC), and wherein the deployment requirement includes at least one of a service area, software image data, or quality of service (QoS) requirement for one or more User Equipment (UEs) accessible to an Edge Data Network (EDN).

Example 12 may include the computer-readable medium of example 10 and/or some other examples herein, wherein the request is further associated with invoking an instantaneity nsrequest operation to request instantiation via an open source managed orchestration network function virtualization orchestrator (Os-Ma-nfvo) interface.

Example 13 may include the computer-readable medium of example 10 and/or some other example herein, wherein the instantiation result is a deployment only when all of the one or more EAS VNF instances are successfully instantiated.

Example 14 may include the computer-readable medium of example 13 and/or some other example herein, wherein the request is further associated with creating an MOI for an easf unit Information Object Class (IOC) based on the instantiation result being a deployment.

Example 15 may include the non-transitory computer-readable medium of example 14 and/or some other example herein, wherein the notification further indicates that an MOI was created.

Example 16 may include the computer-readable medium of example 10 and/or some other examples herein, the instantiation result indicating a failure when any of the one or more EAS VNF instances is not successfully instantiated.

Example 17 may include a method for provisioning a management service (MnS) producer at an Edge Computing Service Provider (ECSP) in a wireless network, the method comprising: detecting, by processing circuitry of the ECSP, a request to create a Managed Object Instance (MOI), the request received from an Application Service Provider (ASP), the request including a deployment requirement; encoding, by the processing circuitry, a response to the request for transmission to the ASP, the response indicating that instantiation is in progress; selecting, by the processing circuitry, a number of Edge Data Network (EDN) and Edge Application Server (EAS) instances to instantiate based on the deployment requirements; detecting, by the processing circuitry, an EAS Virtualized Network Function (VNF) software image received based on the deployment requirement; requesting, by processing circuitry, one or more EAS VNF instances of an instantiation software image by a Network Function Virtualization Orchestrator (NFVO); detecting, by the processing circuitry, the instantiated result; and encoding, by the processing circuitry, a notification for transmission to the ASP based on the instantiation, the notification including an indication of whether the result is deployment or failure.

Example 18 may include the method of example 17 and/or some other examples herein, wherein the deployment requirement is included in a requested EAS lifecycle management information object class (EASLcm IOC), and wherein the deployment requirement comprises at least one of a service area, software image data, or quality of service (QoS) requirement for one or more User Equipment (UE) accessible EDNs.

Example 19 may include the method of example 17 and/or some other examples herein, additionally comprising: invoking an InstantiateNSRequest operation to request instantiation via an open source managed orchestrator network function virtualization orchestrator (Os-Ma-nfvo) interface; and detecting a network service lifecycle change notification received from the NFVO indicating the instantiated state.

Example 20 may include the method of example 17 and/or some other examples herein, additionally comprising: all of the one or more EAS VNF instances are detected as successfully instantiated, wherein the result is deployment only when all of the one or more EAS VNF instances are successfully instantiated.

Example 21 may include the method of example 20 and/or some other examples herein, additionally comprising: an MOI is created for an EASFunit Information Object Class (IOC) based on the deployment result.

Example 22 may include the method of example 21 and/or some other example herein, wherein the notification further indicates that an MOI is created.

Example 23 may include the method of example 17 and/or some other examples herein, further comprising detecting that an EAS VNF instance of the one or more EAS VNF instances is not successfully instantiated.

Example 24 may include an apparatus comprising means for: detecting an ECSP, creating a request for a Managed Object Instance (MOI), the request received from an Application Service Provider (ASP), the request including deployment requirements; encoding a response to the request transmitted to the ASP, the response indicating that instantiation is in progress; selecting a number of Edge Data Network (EDN) and Edge Application Server (EAS) instances to instantiate based on the deployment requirements; detecting an EAS Virtualized Network Function (VNF) software image received based on a deployment requirement; requesting one or more EAS VNF instances of the software image to be instantiated by a Network Function Virtualization Orchestrator (NFVO); detecting an instantiated result; and encoding a notification for transmission to the ASP based on the instantiating, the notification containing an indication of whether the result is deployment or failure.

Example 25 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-24, or any other method or process described herein.

Example 26 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 ECSP and ASP to perform one or more elements of the methods described in or associated with any of examples 1-24, or any other method or process described herein.

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

Example 28 may include the method, technique, or process described in or associated with any one of examples 1 to 24, or a portion or component thereof.

Example 29 may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, technique, or process described in or associated with any one of examples 1-24, or portions thereof.

For one or more embodiments, at least one of the components 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.

Abbreviations (abbreviations)

Unless used differently herein, terms, definitions and abbreviations may be consistent with terms, definitions and abbreviations defined in 3GPP TR 21.905v16.0.0 (2019-06). For the purposes of this document, the following abbreviations may apply to the examples and embodiments discussed herein.

Table 1 abbreviation:

/>

in the above disclosure, reference has been made to the accompanying drawings, which form a part hereof, and which illustrate specific embodiments in which the disclosure may be practiced. It is to be understood that other embodiments may be utilized and structural changes may be made without departing from the scope of the present disclosure. References in the specification to "one embodiment," "an example implementation," etc., indicate that the embodiment or implementation described may include a particular feature, structure, or characteristic, but every embodiment or implementation may not necessarily include the particular feature, structure, or characteristic. Moreover, these phrases are not necessarily referring to the same embodiment or implementation. Furthermore, when a particular feature, structure, or characteristic is described in connection with an embodiment or implementation, it is submitted that it is within the knowledge of one skilled in the art to effect such feature, structure, or characteristic in connection with other embodiments or implementations whether or not explicitly described. For example, the various features, aspects and actions described above with respect to autonomous parking maneuvers apply to various other autonomous maneuvers and must be interpreted accordingly.

Embodiments of the systems, apparatuses, devices, and methods disclosed herein may include or utilize one or more devices including hardware, such as one or more processors and system memory, as described herein. Embodiments of the devices, systems, and methods disclosed herein may communicate over a computer network. A "network" is defined as one or more data links capable of transporting electronic data between computer systems and/or modules and/or other electronic devices. When information is transferred or provided over a network or another communications connection (either hardwired, wireless, or any combination of hardwired or wireless) to a computer, the computer properly views the connection as a transmission medium. The transmission media can include networks and/or data links, which can be used to carry desired program code means in the form of computer-executable instructions or data structures, and which can be accessed by a general purpose or special purpose computer. Combinations of the above should also be included within the scope of non-transitory computer-readable media.

Computer-executable instructions comprise, for example, instructions and data which, when executed on a processor, cause the processor to perform a function or group of functions. The computer-executable instructions may be, for example, binary, intermediate format instructions such as assembly language, or even source code. Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the features or acts described above. Rather, the described features and acts are disclosed as example forms of implementing the claims.

A memory device may include any one or combination of volatile memory elements (e.g., random access memory (RAM, such as DRAM, SRAM, SDRAM, etc.)) and nonvolatile memory elements (e.g., ROM, hard drive, tape, CDROM, etc.). Furthermore, the storage devices may incorporate electronic, magnetic, optical, and/or other types of storage media. In the context of this document, a "non-transitory computer readable medium" can be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device. More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: portable computer magnetic disk (magnetic), random Access Memory (RAM) (electronic), read-only memory (ROM) (electronic), erasable programmable read-only memory (EPROM, EEPROM, or flash memory) (electronic), and portable compact disc read-only memory (CD ROM) (optical). Note that the computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via, for instance, optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner, if necessary, and then stored in a computer memory.

Those skilled in the art will appreciate that the disclosure may be practiced in network computing environments with many types of computer system configurations, including embedded vehicle computers, personal computers, desktop computers, laptop computers, message processors, nomadic devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, mobile telephones, PDAs, tablet computers, pagers, routers, switches, various storage devices, and the like. The disclosure may also be practiced in distributed system environments where local and remote computer systems, which are linked (either by hardwired data links, wireless data links, or by any combination of hardwired and wireless data links) through a network, both perform tasks. In a distributed system environment, program modules may be located in both local and remote memory storage devices.

Furthermore, where appropriate, the functions described herein may be performed in one or more of hardware, software, firmware, digital components, or analog components. For example, one or more Application Specific Integrated Circuits (ASICs) may be programmed to perform one or more of the systems and procedures described herein. Certain terms are used throughout the description and the claims refer to particular system components. As will be appreciated by those skilled in the art, components may be referred to by different names. This document does not intend to distinguish between components that differ in name but not function.

At least some embodiments of the present disclosure are directed to computer program products comprising such logic (e.g., in the form of software) stored on any computer usable medium. Such software, when executed in one or more data processing devices, causes the devices to operate as described herein.

While various embodiments of the present disclosure have been described above, it should be understood that they have been presented by way of example only, and not limitation. It will be apparent to persons skilled in the relevant art that various changes in form and detail can be made therein without departing from the spirit and scope of the disclosure. Thus, the breadth and scope of the present disclosure should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents. The foregoing description has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the disclosure to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. Further, it should be noted that any or all of the above-described alternative embodiments may be used in any desired combination to form additional hybrid embodiments of the present disclosure. For example, any of the functions described for a particular device or component may be performed by another device or component. Furthermore, while specific device characteristics have been described, embodiments of the present disclosure may relate to many other device characteristics. Furthermore, although embodiments have been described in language specific to structural features and/or methodological acts, it is to be understood that the disclosure is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as illustrative forms of embodiment. Conditional language such as "may," "may," or "perhaps," unless specifically stated otherwise or otherwise understood in the context of use, is generally intended to convey that certain embodiments may include, while other embodiments may not include, certain features, elements, and/or steps. Thus, such conditional language is not generally intended to imply that one or more embodiments require features, elements, and/or steps in any way.

Terminology

For purposes of this document, the following terms and definitions apply to the examples and embodiments described herein.

The term "circuitry" as used herein refers to, is part of, or includes, a hardware component, such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a Field Programmable Device (FPD) (e.g., a Field Programmable Gate Array (FPGA), a Programmable Logic Device (PLD), a Complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), a Digital Signal Processor (DSP), or the like, that is configured to provide the described functionality. In some embodiments, the circuitry may implement 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, the 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 a circuit, or a portion of a circuit, or including a circuit, 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 to carry out instructions and one or more memory structures to store program and data information. The term "processor circuit" 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 hardware accelerators may include, for example, computer Vision (CV) and/or Deep Learning (DL) accelerators. The terms "application circuitry" and/or "baseband circuitry" may be considered synonymous with "processor circuitry" and may be referred to as "processor circuitry"

The term "interface circuit" as used herein refers to, is part of, or includes circuitry capable of exchanging information between two or more components or devices. The term "interface circuit" may refer to one or more hardware interfaces, such as a bus, an I/O interface, a peripheral component interface, a network interface card, and the like.

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 with, and may be referred to as, a client, a mobile device, a mobile terminal, a user terminal, a mobile unit, a mobile station, a mobile user, a subscriber, a user, a remote station, an access agent, a user agent, a receiver, radio equipment, reconfigurable mobile equipment, and the like. 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 physical or virtual equipment and/or infrastructure for providing wired or wireless communication network services. The term "network element" may be considered synonymous with and/or referred to as a networked computer, networking hardware, network equipment, 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 each other. 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 network resources.

The terms "device," "computer device," and the like as used herein refer to a computer device or computer system with program code (e.g., software or firmware) specifically designed to provide specific computing resources. A "virtual device" is a virtual machine image implemented by a hypervisor-equipped device that virtualizes or emulates a computer appliance, or is 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, a processor/CPU time, a processor/CPU usage, a processor and accelerator load, a hardware time or usage, power, input/output operations, a port or network socket, channel/link allocation, throughput, memory usage, storage, a network, a database, and application, a workload unit, and/or 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 type of shared entity for providing services and may include computing resources and/or network resources. System resources may be considered as a set of coherent functions, network data objects, or services, accessible through a server, that 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 used to convey data or a data stream. The term "channel" may be synonymous and/or equivalent of "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier wave," "radio frequency carrier wave," and/or any other similar term, representing a path or medium through which data is communicated. Furthermore, the term "link" as used herein refers to a connection between two devices by RAT for the purpose of transmitting and receiving information.

The terms "instantiate", 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 as 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 communication with each other, including through wired or other interconnection connections, through wireless communication channels or links, and so forth.

The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual content of an information element 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, wherein the UE either performs an initial connection establishment procedure or initiates a connection re-establishment procedure.

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

The term "secondary cell" refers to a cell providing additional radio resources over a special cell of 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 of a UE in rrc_connected that is not configured with CA/DC, and only one serving cell includes the primary cell.

The term "serving cell" refers to a set of cells including a special cell and all secondary cells for UEs in rrc_connected configured with CA/s.

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. An apparatus of an Edge Computing Service Provider (ECSP) for provisioning a management service (MnS) producer at the ECSP in a wireless network, the apparatus comprising:

a memory;

processing circuitry coupled to the memory, the processing circuitry configured to:

detecting a request to create a Managed Object Instance (MOI), the request received from an Application Service Provider (ASP), the request including a deployment requirement;

encoding a response to the request for transmission to the ASP, the response indicating that instantiation is in progress;

selecting a number of Edge Data Network (EDN) and Edge Application Server (EAS) instances to instantiate based on the deployment requirements;

detecting an EAS Virtualized Network Function (VNF) software image received based on the deployment requirement;

requesting instantiation of one or more EAS VNF instances of the software image by a Network Function Virtualization Orchestrator (NFVO);

detecting the result of the instantiation; and

a notification for transmission to the ASP is encoded based on the instantiation, the notification including an indication of whether the result is deployment or failure.

2. The apparatus of claim 1, wherein the deployment requirement is included in an EAS lifecycle management information object class (EASLcm IOC) of the request, and wherein the deployment requirement comprises at least one of a service area, software image data, or quality of service (QoS) requirement for one or more User Equipment (UEs) capable of accessing the EDN.

3. The apparatus of claim 1 or claim 2, wherein the processing circuit is further configured to:

invoking an InstantiateNSRequest operation to request the instantiation via an open source managed orchestrator network function virtualization orchestrator (Os-Ma-nfvo) interface; and

a network service lifecycle change notification received from the NFVO indicating the instantiated state is detected.

4. The apparatus of claim 1, wherein the configured processing circuitry is further configured to:

detecting that all of the one or more EAS VNF instances are successfully instantiated, wherein the result is deployment only when all of the one or more EAS VNF instances are successfully instantiated.

5. The apparatus of claim 4, wherein the configured processing circuitry is further configured to:

the MOI is created for an EASFunit Information Object Class (IOC) based on the result being a deployment.

6. The apparatus of claim 5, wherein the notification further indicates that the MOI was created.

7. The apparatus of claim 1, wherein the processing circuit is further configured to:

detecting that an EAS VNF instance of the one or more EAS VNF instances is not successfully instantiated.

8. The apparatus of claim 7, wherein the notification indicates that the result is a failure based on detecting that the EAS VNF instance was not successfully instantiated.

9. The apparatus of claim 7, wherein the processing circuit is further configured to:

detecting that a second EAS VNF instance of the one or more EAS VNF instances is successfully instantiated,

wherein the notification indicates that the result is a partial deployment.

10. A computer-readable storage medium comprising instructions that, when executed by processing circuitry of an Application Service Provider (ASP), cause the processing circuitry to:

encoding a request to create a Managed Object Instance (MOI) for transmission to an Edge Computing Service Provider (ECSP), the request including deployment requirements associated with one or more Virtual Network Function (VNF) instances that instantiate a software image of an edge application server;

Detecting a response received from the ECSP after the request, the response indicating that instantiation is in progress and that the ECSP is to send a notification including an indication of whether the instantiation result is deployment or failure; and is also provided with

The notification received from the ECSP is detected after the response.

11. The computer-readable storage medium of claim 10, wherein the deployment requirement is included in an EAS lifecycle management information object class (EASLcm IOC) of the request, and wherein the deployment requirement comprises at least one of a service area, software image data, or quality of service (QoS) requirement for one or more User Equipment (UEs) capable of accessing an Edge Data Network (EDN).

12. The computer-readable storage medium of claim 10, wherein the request is further associated with invoking an instatatensrequest operation to request the instantiation via an open source managed orchestration network function virtualization orchestrator (Os-Ma-nfvo) interface.

13. The computer-readable storage medium of claim 10, wherein the instantiation result is a deployment only when all of the one or more EAS VNF instances are successfully instantiated.

14. The computer-readable storage medium of claim 13, wherein the request is further associated with creating the MOI for an easf unit Information Object Class (IOC) based on the instantiation result being a deployment.

15. The computer-readable storage medium of claim 14, wherein the notification further indicates that the MOI was created.

16. The computer-readable storage medium of claim 10, wherein the instantiation result indicates a failure when any of the one or more EAS VNF instances is not successfully instantiated.

17. A method for provisioning a management service (MnS) producer at an Edge Computing Service Provider (ECSP) in a wireless network, the method comprising:

detecting, by processing circuitry of the ECSP, a request to create a Managed Object Instance (MOI), the request received from an Application Service Provider (ASP), the request including a deployment requirement;

encoding, by the processing circuitry, a response to the request for transmission to the ASP, the response indicating that instantiation is in progress;

selecting, by the processing circuitry, a number of Edge Data Network (EDN) and Edge Application Server (EAS) instances to instantiate based on the deployment requirement;

detecting, by the processing circuitry, an EAS Virtualized Network Function (VNF) software image received based on the deployment requirement;

requesting, by the processing circuitry, instantiation of one or more EAS VNF instances of the software image by a Network Function Virtualization Orchestrator (NFVO);

Detecting, by the processing circuitry, a result of the instantiating; and

a notification for transmission to the ASP is encoded by the processing circuitry based on the instantiation, the notification including an indication of whether the result is a deployment or failure.

18. The method of claim 17, wherein the deployment requirement is included in an EAS lifecycle management information object class (EASLcm IOC) of the request, and wherein the deployment requirement comprises at least one of a service area, software image data, or quality of service (QoS) requirement for one or more User Equipment (UEs) capable of accessing the EDN.

19. The method of claim 17, further comprising:

20. The method of claim 17, further comprising:

21. The method of claim 20, further comprising:

22. The method of claim 21, wherein the notification further indicates that the MOI was created.

23. The method of claim 17, further comprising:

24. A computer readable storage medium comprising instructions to perform the method of any one of claims 16-23.

25. An apparatus comprising means for performing the method of any one of claims 16-23.