Method and apparatus for edge enabler server lifecycle management
In embodiments of the present disclosure, a method and apparatus for managing the lifecycle of edge enabler server (EES) are disclosed. SA6 has defined EAS and EES is a 3GPP network function deployed on the operators edge data network (EDN) being managed by the operator's management system. The lifecycle management of edge components and the lifecycle of EES, as 3GPP network function are managed which includes instantiation, termination, scaling, etc. Thus, 3GPP management system have the capability to provide EES lifecycle management including but not limited to instantiation, termination, scaling.
1. A method by a first network node, the method comprising:
receiving, from a second network node, a request for creating a managed object instance (MOI), the request including one or more requirements related to an edge enabler server (EES); and
creating the MOI for an EESfunction information object class (IOC) based on the one or more requirements included in the request,
wherein the created MOI includes one or more attributes indicated in the EESfunction IOC, and
wherein the one or more attributes include an identifier of the EES, serving location information for the EES, and information indicating whether the EES supports service continuity.
2. The method of claim 1 , wherein the one or more requirements include at least one of an edge data network (EDN) identifier that identifies a host EDN to instantiate the EES and an edge application server (EAS) identifier that identifies a list of EASs registered with the EES.
3. The method of claim 1 , further comprising:
transmitting, to the second network node, a response including an identifier of the created MOI, in response to the request.
4. The method of claim 1 , wherein the first network node is a service provider device and the second network node is a service consumer device.
5. The method of the claim 1 , further comprising:
prior to the creating of the MOI, determining if an EES instance to be created contains a virtualized part;
if the EES instance to be created contains the virtualized part, deriving requirements for an EES virtual network function (VNF) instance based on an EES network function related requirements;
determining if a VNF package of the virtualized part needs to be on-boarded or changed;
if the VNF package needs to be on-boarded or changed, invoking a VNF package management procedure; and
invoking a VNF lifecycle management with the requirements for the EES VNF instance.
6. A first network node, the first network node comprising:
a transceiver; and
at least one processor coupled to the transceiver, wherein the at least one processor is configured to:
control the transceiver to receive, from a second network node, a request for creating a managed object instance (MOI), the request including one or more requirements related to an edge enabler server (EES), and
create the MOI for an EESfunction information object class (IOC) based on the one or more requirements included in the request,
wherein the created MOI includes one or more attributes indicated in the EESfunction IOC, and
wherein the one or more attributes include an identifier of the EES, serving location information for the EES, and information indicating whether the EES supports service continuity.
7. The first network node of claim 6 , wherein the one or more requirements include at least one of an edge data network (EDN) identifier that identifies a host EDN to instantiate the EES and an edge application server (EAS) identifier that identifies a list of EASs registered with the EES.
8. The first network node of claim 6 , wherein the at least one processor is further configured to control the transceiver to transmit, to the second network node, a response including an identifier of the created MOI, in response to the request.
9. The first network node of claim 6 , wherein the first network node is a service provider device and the second network node is a service consumer device.
10. The first network node of claim 6 , wherein the at least one processor is further configured to:
prior to the creating of the MOI, determine if an EES instance to be created contains a virtualized part,
if the EES instance to be created contains the virtualized part, derive requirements for an EES virtual network function (VNF) instance based on an EES network function related requirements,
determine if a VNF package of the virtualized part needs to be on-boarded or changed,
if the VNF package needs to be on-boarded or changed, invoke a VNF package management procedure, and
invoke a VNF lifecycle management with the requirements for the EES VNF instance.