5 Edge Computing Management (ECM) capabilities
28.5383GPPEdge Computing ManagementManagement and orchestrationRelease 18TS
5.1 Lifecycle management
5.1.1 Description
The lifecycle management of the edge components is to be enabled by the 3GPP Management System. The lifecycle management includes instantiation, termination, modification and query of the edge components.
5.1.2 EAS deployment
The goal of this use case is to enable ASP to deploy the EAS in the EDN, by requesting the provisioning MnS producer with the deployment requirements (e.g. the topological or geographical service areas, software image information, QoS, affinity/anti-affinity with other EAS, etc.) to deploy the EAS. The provisioning MnS producer returns a response indicating the operation is in progress to prevent the consumer from waiting, as the deployment in the edge cloud may take a while. Since, there can be multiple Edge Data Network (EDN) present/serving a particular edge location. This makes it critical for application service provider to have their EAS deployed at appropriate EDN(s) to provide high performance services for the UE. Therefore, provisioning MnS producer analyses the deployment requirements to determine where (i.e. on which EDN) and how many EAS VNF instance(s) should be instantiated, and requests the NFVO in ETSI NFV MANO to instantiate the EAS VNF instance(s). The provisioning MnS producer sends a notification to ASP indicating the result of instantiation (e.g. success, failure) when a notification is received from NFVO indicating the result of instantiation operation.
5.1.3 EAS termination
The goal of this use case is to enable ASP to terminate the EAS in the EDN, by requesting the provisioning MnS producer to terminate the EAS VNF instance. The provisioning MnS producer requests the NFVO in ETSI NFV MANO to terminate the EAS VNF instances. The provisioning MnS producer sends a notification to ASP indicating the termination is in progress when a notification is received from NFVO indicating the start of termination operation. The provisioning MnS producer sends another notification to ASP indicating the result of termination (e.g. success, failure) when a notification is received from NFVO indicating the result of termination operation.
5.1.4 Query EAS information
The goal of this use case is to enable ASP to query the EAS information in the EDN, by requesting the provisioning MnS producer to query the EAS instance. Upon receiving the query request, the provisioning MnS producer sends the EAS instance information to ASP.
5.1.5 EAS modification
The goal of this use case is to enable ASP to modify the EAS in the EDN, by requesting the provisioning MnS producer to modify the EAS instance. If the modification requires the change (e.g. scale) for the virtualized resource of the EAS VNF instance, the provisioning MnS producer requests the NFVO in ETSI NFV MANO for the appropriate operation of the EAS VNF instances. The provisioning MnS producer sends a notification to ASP indicating the attribute(s) change of the EAS instance.
5.1.6 EES Deployment
The provisioning MnS producer is requested to instantiate the EES, as 3GPP network functions, aiming to server the particular location. The instantiated EES may serve one or multiple EAS.
A consumer request for EES(s) instantiation providing EES deployment requirements. The provisioning MnS producer determines the EDN where the EES(s) will be instantiated, instantiate the EES VNF and establish the connection with 5GC network functions. The provisioning MnS producer will accept the request and notify the consumer about the instantiation in-progress. Thereafter, the notification will be sent to indicate the successful EES instantiation.
5.1.7 EES Termination
The goal is to enable the termination of one or more EES(s) on the EDN. A consumer consumes the provisioning MnS to terminate the EES with the EES identifier. The provisioning MnS producer terminates the EES VNF based on the EES identifier, and disconnects the EES from the 5GC network functions. The provisioning MnS producer will accept the request and notify the consumer about the termination in-progress. Thereafter, the notification will be sent to indicate that the EES has been terminated successfully.
5.1.8 Query EES information
The goal of this use case is to enable a consumer to query the EES information in the EDN, by requesting the provisioning MnS producer to query the EES instance. Upon receiving the query request, the provisioning MnS producer sends the EES instance information to the consumer.
5.1.9 EES Modification
The goal of this use case is to enable a consumer to modify the EES in the EDN, by requesting the provisioning MnS producer to modify the EES instance. If the modification requires the change (e.g. scale) for the virtualized resource of the EES VNF instance, the provisioning MnS producer requests the NFVO in ETSI NFV MANO for the appropriate operation of the EES VNF instances. The provisioning MnS producer sends a notification to the consumer indicating the attribute(s) change of the EES instance.
5.1.10 ECS Deployment
The goal is to enable the instantiation of one or more ECS. To support deployed EDN, operator will deploy ECS serving one or multiple EES. A consumer request for ECS(s) instantiation providing ECS deployment requirements. The provisioning MnS producer instantiate the ECS VNF and establish the required connection with 5GC network functions. The notifications will be sent to indicate that the ECS has been instantiated successfully.
5.1.11 ECS Termination
The goal is to enable the termination of one or more ECS. A consumer consumes the provisioning service to terminate the ECS with the ECS identifier. The provisioning MnS producer terminates the ECS VNF based on the ECS identifier, and disconnects the ECS from the 5GC network functions. The notification will be sent to indicate that the ECS has been terminated successfully.
5.1.12 Query ECS information
The goal of this use case is to enable a consumer to query the ECS instance information, by requesting the provisioning MnS producer to query the ECS instance. Upon receiving the query request, the provisioning MnS producer sends the ECS instance information to the consumer.
5.1.13 ECS Modification
The goal of this use case is to enable a consumer to modify the ECS instance, by requesting the provisioning MnS producer to modify the ECS instance. If the modification requires the change (e.g. scale) for the virtualized resource of the ECS VNF instance, the provisioning MnS producer requests the NFVO in ETSI NFV MANO for the appropriate operation of the ECS VNF instances. The provisioning MnS producer sends a notification to the consumer indicating the attribute(s) change of the ECS instance.
5.1.13a Instantiation triggered by EAS discovery failure
EES may need to trigger dynamic EAS instantiation when EES fails to discover and select the EAS that matches the UE location and the requesting application characteristics EAS (see table 8.5.3.2-2 in TS 23.558 [2]) due to no available EAS during the EAS discovery (see clause 8.5 in TS 23.558 [2]).
A consumer would consume performance assurance MnS to request the ECSP management system to collect EAS discovery failure measurement that will be used to determine whether an EAS needs to be initiated, based on performance information, such as UE locations, application characteristics, and number of UEs that have failed in the EAS discovery.
5.1.14 Requirements
|
Requirement label |
Description |
Related use case(s) |
|---|---|---|
|
REQ-EAS-INST-FUN-1 |
Generic provisioning MnS producer should have a capability allowing an authorized consumer to request the deployment of EAS based on the given deployment requirements. |
EAS Deployment |
|
REQ-EAS-INST-FUN-2 |
Generic Provisioning MnS Producer should have the capability to deploy EAS at a suitable EDN which can support the EAS requirements e.g. serving location, required latency, affinity/anti-affinity with other EAS, service continuity. |
EAS Deployment |
|
REQ-EAS-INST-FUN-3 |
Generic provisioning MnS producer should have a capability to inform the authorized consumer about the progress of instantiation as the response to the deployment request. |
EAS Deployment |
|
REQ-EAS-INST-FUN-4 |
Generic provisioning MnS producer should have a capability to notify the authorized consumer the result (e.g. success, failure) of instantiation operation. |
EAS Deployment |
|
REQ-EAS-TERM-FUN-1 |
Generic provisioning MnS producer should have a capability allowing an authorized consumer to request the termination of the EAS VNF instance. |
EAS Termination |
|
REQ-EAS-TERM-FUN-2 |
Generic provisioning MnS producer should have a capability to inform the authorized consumer about the progress of termination as the response to the termination request. |
EAS Termination |
|
REQ-EAS-TERM-FUN-3 |
Generic provisioning MnS producer should have a capability to notify the authorized consumer the result (e.g. success, failure) of termination operation. |
EAS Termination |
|
REQ-EAS-QUERY-FUN-1 |
Generic provisioning MnS producer should have a capability allowing an authorized consumer to obtain the EAS instance information. |
Query EAS information |
|
REQ-EAS-MOD-FUN-1 |
Generic provisioning MnS producer should have a capability allowing an authorized consumer to request the modification of the EAS instance. |
EAS Modification |
|
REQ-EES-INST-FUN-1 |
Generic provisioning MnS producer should have the capability to instantiate the EES, as per request from authorized consumers. |
EES Deployment |
|
REQ-EES-INST-FUN-2 |
Generic provisioning MnS producer should have the capability to send the notification indicating the status of EES instantiation |
EES Deployment |
|
REQ-EES-INST-FUN-3 |
Generic provisioning MnS producer should have the capability to relate instantiated EES with one or multiple served EAS(s). |
EES Deployment |
|
REQ-EES-TERM-FUN-1 |
Generic provisioning MnS producer should have the capability to terminate the EES with the EES identifier, as per request from authorized consumers |
EES Termination |
|
REQ-EES-TERM-FUN-2 |
Generic provisioning MnS producer should have the capability to send the notification indicating the status of EES termination |
EES Termination |
|
REQ-EES-QUERY-FUN-1 |
Generic provisioning MnS producer should have a capability allowing an authorized consumer to obtain the EES instance information. |
Query EES information |
|
REQ-EES-MOD-FUN-1 |
Generic provisioning MnS producer should have a capability allowing an authorized consumer to request the modification of the EES instance. |
EES Modification |
|
REQ-EES-TERM-FUN-3 |
Generic provisioning MnS producer should have a capability to inform the authorized consumer about the progress of EES instantiation as the response to the deployment request. |
EES Deployment |
|
REQ-EES-TERM-FUN-4 |
Generic provisioning MnS producer should have a capability to inform the authorized consumer about the progress of EES termination as the response to the termination request. |
EES Termination |
|
REQ-ECS-INST-FUN-1 |
Generic provisioning MnS producer should have the capability to instantiate the ECS, as per request from authorized consumers. |
ECS Deployment |
|
REQ-ECS-INST-FUN-2 |
Generic provisioning MnS producer should have the capability to send the notification indicating the status of ECS Instantiation. |
ECS Deployment |
|
REQ-ECS-INST-FUN-3 |
Generic provisioning MnS producer should have the capability to relate instantiated ECS with one or multiple served EES(s). |
ECS Deployment |
|
REQ-ECS-TERM-FUN-1 |
Generic provisioning MnS producer should have the capability to terminate the ECS with the ECS identifier, as per request from authorized consumers. |
ECS Termination |
|
REQ-ECS-TERM-FUN-2 |
Generic provisioning MnS producer should have the capability to send the notification indicating the status of ECS termination. |
ECS Termination |
|
REQ-ECS-TERM-FUN-3 |
Generic provisioning MnS producer should have a capability to inform the authorized consumer about the progress of ECS instantiation as the response to the deployment request. |
ECS Termination |
|
REQ-ECS-TERM-FUN-4 |
Generic provisioning MnS producer should have a capability to inform the authorized consumer about the progress of ECS termination as the response to the termination request. |
ECS Termination |
|
REQ-ECS-QUERY-FUN-1 |
Generic provisioning MnS producer should have a capability allowing an authorized consumer to obtain the ECS instance information. |
Query ECS information |
|
REQ-ECS-MOD-FUN-1 |
Generic provisioning MnS producer should have a capability allowing an authorized consumer to request the modification of the ECS instance. |
ECS Modification |
|
REQ-EAS-DF-FUN-1 |
Performance assurance MnS producer should have a capability allowing an authorized consumer to request the collection of EAS discovery failure measurements that contain UE location and the requesting application characteristics information. |
Instantiation triggered by EAS discovery failure |
|
REQ-EAS-DF-FUN-2 |
3GPP Management system should have a capability allowing an EES to trigger or request for an EAS deployment. |
Instantiation triggered by EAS discovery failure |
5.2 Performance assurance
5.2.1 Description
The clause contains use cases associated with performance assurance.
5.2.2 EAS performance assurance
The goal of this use case is to provide a mechanism for EAS to publish KPIs or measurements, as per requirements shown in Table 5.2.2-1 (see clause 5.2.10.2 in TS 23.558 [2]).
Table 5.2.2-1: Edge Application Server Service KPIs
|
Information element |
Status |
Description |
|
Maximum Request rate |
O |
Maximum request rate from the Application Client supported by the server. |
|
Maximum Response time |
O |
The maximum response time advertised for the Application Client’s service requests. |
|
Availability |
O |
Advertised percentage of time the server is available for the Application Client’s use. |
|
Available Compute |
O |
The maximum compute resource available for the Application Client. |
|
Available Graphical Compute |
O |
The maximum graphical compute resource available for the Application Client. |
|
Available Memory |
O |
The maximum memory resource available for the Application Client. |
|
Available Storage |
O |
The maximum storage resource available for the Application Client. |
|
Connection Bandwidth |
O |
The connection bandwidth in Kbit/s advertised for the Application Client’s use. |
|
NOTE: The maximum response time includes the round-trip time of the request and response packet, the processing time at the server and the time required by the server to consume 3GPP Core Network capabilities, if any. |
||
A consumer, such as ASP, would consume performance assurance MnS to request the ECSP management system to collect EAS KPIs and measurements. The performance assurance MnS producer at ECSP management system will report the measurements to the consumer.
5.2.3 5GC NF measurements to evaluate EAS performance
The goal is to enable ECSP management system to collect the measurements of 5GC NFs (e.g. UPF, PCF, …) that are needed to evaluate the EAS performance. For example, the ECSP management system can correlate the 5GC NF and EAS measurements to determine the root cause of poor EAS performance. ECSP management system, as the consumer would consume performance assurance MnS to request the PLMN management system to collect 5GC NF measurements that are related to EAS performance. The performance assurance MnS producer at PLMN management system will report the measurements to the consumer.
Since an PLMN operator may not want to expose certain measurements (e.g. measurements for 5GC NF(s) not relevant to EAS) to 3rd party operators, like ECSP, the PLMN management system should be able to select specific measurements to be reported to the consumer.
5.2.4 ECS performance assurance
The goal of this use case is to provide a mechanism for ECS performance assurance. ECS performance can be based on various functionalities defined for ECS in (see clause 6.3.4 of [2]). The measurement/KPI should be defined for each functionality, that can be collected as and when required.
A consumer, such as ECSP Management system, would consume performance assurance MnS to request the PLMN management system to collect ECS KPIs and measurements. The performance assurance MnS producer at PLMN management system will report the measurements to the consumer.
5.2.5 EES performance assurance
The goal of this use case is to provide a mechanism for EES performance assurance. EES performance can be based on various functionalities defined for EES in (see clause 6.3.4 of [2]). The measurement/KPI should be defined for each functionality, that can be collected as and when required.
A consumer, such as ECSP Management system, would consume performance assurance MnS to request the PLMN management system to collect EES KPIs and measurements. The performance assurance MnS producer at PLMN management system will report the measurements to the consumer.
5.2.6 Requirements
|
Requirement label |
Description |
Related use case(s) |
|
REQ-EAS-PA-FUN-1 |
Performance assurance MnS producer should have a capability allowing an authorized consumer to request the collection of EAS KPIs and measurements. |
EAS performance assurance |
|
REQ-EAS-PA-FUN-2 |
Performance assurance MnS producer should have a capability to report EAS KPIs and measurements to authorized consumer(s). |
EAS performance assurance |
|
REQ-5GCNF-PA-FUN-1 |
Performance assurance MnS producer should have a capability allowing an authorized consumer to request the collection of 5GC NF(s) (e.g. UPF, PCF, …) measurements that may affect the EAS performance. |
5GC NF measurements to evaluate EAS performance |
|
REQ-EAS-5GCNF -FUN-2 |
Performance assurance MnS producer should have a capability allowing the selection of specific 5GC NF(s) (e.g. UPF, PCF, …) measurements to be reported to authorized consumer(s). |
5GC NF measurements to evaluate EAS performance |
|
REQ-ECS-PA-FUN-2 |
Performance assurance MnS producer should have a capability to report ECS KPIs and measurements to authorized consumer(s). |
ECS performance assurance |
|
REQ-EES-PA-FUN-2 |
Performance assurance MnS producer should have a capability to report EES KPIs and measurements to authorized consumer(s). |
EES performance assurance |
5.3 Fault supervision
5.3.1 Description
The clause contains use cases associated with fault supervision.
5.3.2 EDN NF performance impacted by 5GC NF alarms
The goal is to enable ECSP management system to receive 5GC NFs (e.g. UPF, PCF, NEF, SCEF, …) alarms that may impact the EDN NFs (e.g. EAS, EES) performance from PLMN management system. ECSP management system can correlate the 5GC NF alarms to determine the root causes for poor EDN NF performance. ECSP management system subscribes to receive 5GC NF alarms from PLMN management system. PLMN management system sends the NF alarm notification to ECSP management system when it detects 5GC NF alarms.
5.3.3 5GC NF issues resulted from EDN NF alarms
The goal is to enable PLMN management system to receive EDN NFs (e.g. EAS, EES, ECS) alarms that may generate issues in 5GC NFs (e.g. UPF, PCF, NEF, SCEF, …) that are supporting EDN from ECSP management system. PLMN management system can correlate the EDN NF alarms to determine the root causes for 5GC NF issues. PLMN management system subscribes to receive EDN NF alarms from ECSP management system. ECSP management system sends the NF alarm notification to PLMN management system when it detects EDN NF alarms.
5.3.4 Requirements
|
Requirement label |
Description |
Related use case(s) |
|
REQ-EDNNF-FS-FUN-1 |
Fault supervision MnS producer should have a capability allowing an authorized consumer to subscribe to receive alarms of 5GC NFs that are supporting edge computing applications. |
EDN NF performance impacted by 5GC NF alarms |
|
REQ-EDNNF-FS-FUN-2 |
Fault supervision MnS producer should have a capability to send the 5GC NF alarm notification to authorized consumer(s). |
EDN NF performance impacted by 5GC NF alarms |
|
REQ-5GCNF-FS-FUN-1 |
Fault supervision MnS producer should have a capability allowing an authorized consumer to subscribe to receive alarms of EDN NFs that may generate issues in 5GC NFs. |
5GC NF issues resulted from EDN NF alarms |
|
REQ-5GCNF-FS-FUN-2 |
Fault supervision MnS producer should have a capability to send the EDN NF alarm notification to authorized consumer(s). |
5GC NF issues resulted from EDN NF alarms |
5.4 5GC NF Provisioning
5.4.1 Description
The clause contains use cases associated with provisioning.
5.4.2 EDN NF 5GC connection provisioning
The goal is to enable ECSP management system to request PLMN management system to query the connection information of EDN NFs (i.e., EAS, EES, ECS) to 5GC NFs, as specified in clauses 6.3.2, 6.3.4, 6.4.6 in TS 23.558 [2], where EES, ECS, and EAS are interacting with 3GPP Core Network for accessing the capabilities of network functions either directly (e.g. via PCF) or indirectly (e.g. via SCEF/NEF/SCEF+NEF).
Figure 5.4.2-1 shows an example of edge computing networks. EDN #1 is trusted by PLMN operators; therefore, EAS #1 and EES #1 are acting as the trusted AF, and are authorized to interfaces to PCF directly in via the N5 reference point (see clause 4.2.3 in TS 23.501 [11]), or via Edge-7 and Edge-2 interfaces (see clause 6.2 in TS 23.558). EDN #2 is not trusted by PLMN operators; therefore, EAS #2 and EES #2 are acting as the untrusted AF, and are not authorized to interfaces to PCF directly (See clause 5.6.7.1 TS 23.501 [11]), and need to interface to NEF / SCEF via the N33 reference point (see Figure 4.2.3-5 in TS 23.501), or via Edge-7 and Edge-2 interfaces. ECS should be able to connect to NEF / SCEF via the edge-8 interface (see clause 6.3.4 in TS 23.558 [2]).
Figure 5.4.2-1: Edge computing networks
ECSP management system requests PLMN management system to identify the PCF, NEF, or SCEF to which the EDN NFs need to interface. The request should include the EDN identifier and the service area requirements (i.e., EDN service area, EES service area, and EAS service area (see clause 7.3.3 in TS 23.558 [2])). PLMN management system finds and returns the connection information (i.e., the IP addresses and DN of PCF, NEF, SCEF) to ECSP management system, based on the requirements. ECSP management system then connects EAS, ECS, and EES to 5GC NFs via the connection information given by PLMN management system, according to Figure 5.4.2-1.
5.4.3 Configuration needed for EAS registration
The goal is to enable a consumer to configure EASID and EES address for the EAS that are required as the pre-conditions of EAS registration procedure (see clause 8.4.3.2.1 in TS 23.558 [2]). A consumer (e.g. ASP, ECSP) requests ECSP management system to configure the EASID and EES address attributes in EASFunction IOC. ECSP management system configures the EASID and EES address attributes in EASFunction MOI, and returns the attribute change notification to the consumer.
5.4.4 EAS to connect with UPF
The goal is to enable ECSP management system to connect a newly deployed EAS to a UPF. Figure 5.4.4-1 shows that EASs are acting as local DN that are connected to UPF to carry the user traffic via the N6 interface (see clause 6.3.3 in TS 23.501 [11]). ECSP management system requests PLMN management system to connect a newly deployed EAS to a UPF with EAS IP address, EAS service area requirements (see clause 7.3.3.6 in TS 23.558 [2])), and list of DNAI and N6 traffic routing requirements ((see Table 8.2.4.1 in TS 23.558 [2])). PLMN management system finds a UPF among the UPF(s) being deployed that meets the service area requirements (e.g. UPF #2 is found to connect to EAS #2). In the case that no UPF can be found (e.g. EAS #3), PLMN management system will deploys a new UPF (e.g. UPF #3) and then configure the SMF to add the UPF to the list of available UPF(s) (see clause 6.3.3.2 in TS 23.501 [11]). PLMN management system connects the UPF to the EAS, and return the UPF information (e.g. IP addresses and DN of the UPF) the ECSP management system.
Figure 5.4.4-1: EASs to connect with UPFs
5.4.5 Requirements
|
Requirement label |
Description |
Related use case(s) |
|
REQ-PROV-FUN-1 |
Generic provisioning MnS producer should have the capability allowing authorized consumer to query the connection information of 5GC functions, such as the IP addresses and DN of PCF, NEF, SCEF, by providing EDN identifier and service area requirements. |
EDN NF to access 5GC NF |
|
REQ-PROV-FUN-2 |
Generic provisioning MnS producer should have the capability to return to the authorized consumer with the connection information of 5GC functions, such as the IP addresses and DN of PCF, NEF, SCEF, based on the requirements. |
EDN NF to access 5GC NF |
|
REQ-PROV-FUN-3 |
Generic provisioning MnS producer should have the capability to establish the connection relationship between EAS, EES, and ECS and 5GC NFs via PCF, NEF, or SCEF. |
EDN NF to access 5GC NF |
|
REQ-PROV-FUN-4 |
Generic provisioning MnS producer should have the capability allowing authorized consumer to configure the EASID and EES address attributes for EAS. |
Configuration needed for EAS registration |
|
REQ-PROV-FUN-5 |
Generic provisioning MnS producer should have the capability to send a notification to the consumer, indicating that the attributes have been changed. |
Configuration needed for EAS registration |
|
REQ-PROV-FUN-6 |
Generic provisioning MnS producer should have the capability allowing authorized consumer to provide information for connecting the EAS to UPF by providing EAS IP address, EAS service area requirements and list of DNAI and N6 traffic routing requirements. |
EAS to connect with UPF |
|
REQ-PROV-FUN-7 |
Generic provisioning MnS producer should have the capability to return to the authorized consumer with the UPF connection information of 5GC functions, such as the IP addresses and DN of UPF, based on the requirements. |
EAS to connect with UPF |
|
REQ-PROV-FUN-8 |
Generic provisioning MnS producer should have the capability to connect the EAS to UPF. |
EAS to connect with UPF |