7.1.2 EAS lifecycle management

28.5383GPPEdge Computing ManagementManagement and orchestrationRelease 18TS

7.1.2.1 EAS deployment

Figure 7.1.2.1-1 depicts a procedure that describes how an ASP can consume provisioning MnS to instantiate the EAS. It is assumed that both ASP and ECSP consumers have subscribed to the producer of provisioning MnS to receive notifications.

Figure 7.1.2.1-1: EAS deployment

1. ASP consumes the provisioning MnS with createMOI operation (see clause 11.1.1.1. in TS 28.532 [w]) for EASRequirements IOC to request ECSP provisioning MnS producer to start the EAS VNF instantiation, where the EASRequirements IOC contains the deployment requirements, including (but not limited to) the following attributes:

– the service areas (i.e., geographical, or topological) where the UEs can access the edge computing service (see clause 7.3.3 in TS 28.558 [2]).

– Software image information and virtual resource information (e.g. software image location, minimum RAM, disk requirements) (see clause 7.1.6.5 and 7.1.9 in ETSI NFV IFA-011 [7]).

– QoS requirements (e.g. bandwidth, end-to-end latency).

– service continuity requirements (e.g. whether service continuity is required).

– Affinity/Anti-affinity: The affinity and ant-affinity requirements for the EAS with other existing EAS on the target EDN.

2. ECSP provisioning MnS producer sends a response to the ASP indicating that the instantiation operation is in progress.

3. ECSP provisioning MnS producer analyses the deployment requirements to determine which EDN and how many EAS instance(s) should be instantiated to satisfy the deployment requirements, and downloads the EAS VNF software image from the software image location. The EDN can be selected either by considering the individual requirement or by grouping the multiple requirements as single selection criteria.

4. ECSP provisioning MnS producer invokes the InstantiateNsRequest or UpdateNsRequest operation (see clause 7.3.3 and 7.3.5 in ETSI GS NFV-IFA 013 [6]) to request NFVO via the Os-Ma-nfvo interface to instantiate a NS instance including the EAS VNF instance.

Editor’s note: which entity is responsible for creating VNFD based on the deployment requirement (e.g., softwareImageInfo and virtualResource) is FFS.

5. NFVO sends a notification to ECSP provisioning MnS producer indicating the result of instantiation procedure (see clause 7.3.3.4 and 7.3.5.4 of ETSI GS NFV-IFA 013 [6]).

6. If the VNF instantiation has been successful, ECSP provisioning MnS producer creates the MOI for EASFunction IOC.

7. If all VNF instance(s) have been successfully instantiated, then:

7.1. ECSP provisioning MnS producer creates the MOI for EASRequirements IOC.

7.2. ECSP provisioning MnS producer notifies ASP about the successful instantiation of EAS with the creation of MOIs for the EASRequirement IOC and EASFunction(s) IOC.

Otherwise:

7.3 ECSP provisioning MnS producer notifies ASP about the un-successful instantiation of the EAS.

7.1.2.2 EAS termination

Figure 7.1.2.2-1 depicts a procedure that describes how an ASP can consume provisioning MnS to terminate the EAS VNF. It is assumed that both ASP and ECSP consumers have subscribed to the producer of provisioning MnS to receive notifications.

Figure 7.1.2.2-1: EAS termination

1. ASP consumes the provisioning MnS with deleteMOI (see clause 11.1.1.4. in TS 28.532 [5]) operation for EASFunction MOI to request ECSP provisioning MnS producer to start the EAS VNF termination.

2. ECSP provisioning MnS producer sends a response to the ASP indicating that the termination operation is in progress.

3. ECSP provisioning MnS producer invokes the TerminateNsRequest or UpdateNsRequest operation (see clauses 7.3.7 and 7.3.5 in ETSI GS NFV-IFA 013 [6]) to request NFVO via the Os-Ma-nfvo interface to terminate EAS VNF instance.

4. NFVO sends the NS Lifecycle Change notification to ECSP provisioning MnS producer indicating the result of termination procedure (see clause 7.3.12 of ETSI GS NFV-IFA 013 [6]).

5. If the VNF termination has been successful then:

5.1. ECSP provisioning MnS producer deletes the MOI for EASFunction IOC ,if all the related EASFunction MOIs have been deleted, the EASRequirement IOC shall also be deleted.

5.2. ECSP provisioning MnS producer notifies ASP about the successful termination of the EAS.

Otherwise :

5.3. ECSP provisioning MnS producer notifies ASP about the un-successful termination of the EAS.

7.1.2.3 EAS VNF modification

Figure 7.1.2.3 -1 depicts a procedure that describes how an ASP can consume provisioning MnS to modify the EAS. It is assumed that both ASP and ECSP consumers have subscribed to the producer of provisioning MnS to receive notifications.

Figure 7.1.2.3-1: EAS modification procedure

1. ASP consumes the provisioning MnS with modifyMOIAttributes operation (see clause 11.1.1.3. in TS 28.532 [5]) for EASFunction MOI to request ECSP management system provisioning MnS producer to modify the EAS VNF instance.

2. ECSP management system provisioning MnS producer sends a response to the consumer indicating that the modification operation is in progress.

3. If EAS instance to be modification contains virtualized part, checks whether corresponding VNF instance needs to be modified to satisfy the modification related requirements.

4. If corresponding VNF instance needs to be modified, ECSP provisioning MnS producer invokes theUpdateNsRequest operation (see clause 7.3.5 in ETSI GS NFV-IFA 013 [6]) to request NFVO via the Os-Ma-nfvo interface to modify the virtualized resource of the EAS VNF instance.

5. NFVO sends the NS Lifecycle Change notification to ECSP provisioning MnS producer indicating the result of modification procedure (see clause 7.3.12 of ETSI GS NFV-IFA 013 [6]).

6. ECSP provisioning MnS producer modifies the MOI for EASFunction IOC.

7. ECSP management system provisioning MnS producer response the consumer about the modification of the EAS.

7.1.2.4 EAS VNF query

Figure 7.1.2.4-1 depicts a procedure that describes how an ASP can consume provisioning MnS query the EAS. It is assumed that both ASP and ECSP consumers have subscribed to the producer of provisioning MnS to receive notifications.

Figure 7.1.2.4-1: EAS query procedure

1. ECSP provisioning MnS Producer receives a query request (this will use getMOIAttributes operation defined in 3GPP TS 28.532[5]) with objectInstance of the existing EASFunction MOI, scope, and list of attributes of EASFunction IOC. The list of attributes identifies the attributes to be returned by this operation.

2. Based on the request, ECSP provisioning MnS producer queries the concrete EASFunction MOI

3. MnS Producer sends a response to the MnS consumer with objectClass, objectInstance, status (e.g. succeed or failed), and list of [Attribute, Value] related to EAS instance as defined in clause 6.4 (e.g. eASAddress).

7.1.2.5 EAS instantiation triggered by measurement data

Figure 7.1.2.5-1 depicts a procedure to support the use case described in clause 5.2.6 EAS discovery failure that utilized measurement data to trigger EAS instantiation.

Figure 7.1.2.5-1: EAS instantiation triggered by measurement data

1. The consumer utilizes the procedure described in clause 7.2.2 to request MnF for performance assurance for EES to request MnF for performance assurance for EES to collect EAS discovery failure measurements from the EES (see clause 5.15.3.3 in TS 28.552 [10], containing subcounters of UE location and EAS type.

2. The consumer determines whether an EAS VNF needs to be instantiated, based on the information in the measurement data, including UE locations (i.e., cell ID), EAS types, and the number of UEs in a cell.

3. If a new EAS VNF should be instantiated, then

3.a The consumer utilizes the procedure described in clause 7.1.2.1 to instantiate the new VNF instance.

4. The consumer utilizes the procedure described in clause 7.4.2 to configure the EAS with the information needed for EAS to register to EES.

5. ECSP MnF of provisioning, acting as the consumer, utilizes the procedures described in clause 7.4.3 and 7.4.4 to request PLMN MnF of provisioning, acting as the producer, to connect the EAS to 5GC NFs.