Content for TR 23.958 Word version: 18.2.0
A Mapping roles between EDGEAPP architecture and GSMA OPG architecture p. 20
GSMA Operator Platform Group has published their edge requirements in Operator Platform Telco Edge Requirements [3].
Clause 3 of Operator Platform Telco Edge Requirements [3] provides the OP Roles and Interfaces Reference Architecture. Clause 3.2 of Operator Platform Telco Edge Requirements [3] defines roles along with their key functions.
The three main roles in the GSMA OP architecture and their mapping with EDGEAPP architecture entity is as follows:
1)
Capabilities Exposure Role: It enables an Application Provider to operate their applications. Table A-1 shows the scenarios enabled by Capabilities exposure role as indicated in Operator Platform Telco Edge Requirements [3] and their mapping with 3GPP EDGEAPP architecture.
| Interface | Scenario | Description | Mapping to 3GPP EDGEAPP |
|---|---|---|---|
| NBI | Edge Cloud Infrastructure Endpoint Exposure | The Application Provider uses an authenticated and authorized endpoint to carry out scenarios involving application instances on edge clouds; | ASP interacts with 3GPP Management system using Management Service for Edge Computing, as defined in Clause 8 of TS 28.538, to carry out scenarios involving application instances on Edge Data Network. |
| Application Onboarding | The Application Provider uses the NBI to provide application images and metadata to the OP Federation Broker/Manager Role | Application instances are managed by 3GPP Management System as VNFs. VNF on boarding is defined in ETSI GS NFV IFA-013. This may require additional functionality to be defined between ASP and ECSP Management System. | |
| Application Metadata/Manifest Submission | The Application Provider uses the NBI and the metadata model to submit application metadata to the OP and follows defined procedures to extend the metadata model specification | ||
| Application CI/CD Management DevOps | The Application Provider integrates the CI/CD framework used to create an application with the OP via NBI APIs (which implies an integration between a CI/CD framework and Application Onboarding and Lifecycle Management) | ||
| Application Lifecycle Management | The Application Provider observes and changes the operational state of application instances, including the geographical/network extent of the OP on which application instances may run; | Clause 7.1 of TS 28.538 "Lifecycle management". | |
| Application Resource Consumption Monitoring | The Application Provider observes resource consumption of application instances, using the resource data model | Defined in clause 8.2.1 of TS 28.538 "EAS performance assurance". The virtual resource usage can be monitored by collecting the respective performance measurements as defined in clause 8.2.1.2 of TS 28.538. | |
| Edge Cloud Resource Catalogue exposure | The Application Provider inventories edge cloud resources nominally available to application instances | ||
| Network Capabilities exposure | The Application Provider inventories network capabilities, like Network Analytics, nominally available to application instances | EES (as per clause 8.7.3) |
2)
Service Resource Manager Role: The Service Resource Manager role in the OP is responsible for managing Cloud and Network resources from the Edge Cloud(s) via the SBI and UNI interfaces. Table A-2 shows typical scenarios enabled by the Service Resource Manager role towards the different interfaces as indicated in Operator Platform Telco Edge Requirements [3] and their mapping with 3GPP EDGEAPP architecture.
| Interface | Scenario | Mapping to 3GPP EDGEAPP |
|---|---|---|
| SBI | Inventory, Allocation and Monitoring of Compute resources from Edge Cloud Infrastructure via the Southbound Interface - Cloud Resources (SBI-CR); | Application instances are managed by 3GPP Management System as VNFs. VNF resource orchestration, including reservation, is defined in ETSI NFV IFA013. |
| Orchestration of Application instances on the Edge Cloud Infrastructure via the SBI-CR interface | ||
| Cloud resource reservation managed by the OP | ||
| Configuring UE traffic management policies to accomplish the application's requirements, or the UE's IP address shall be maintained | ||
| Exposure of usage and monitoring information to operator's charging engine via the Southbound Interface - Charging functions (SBI-CHF) to enable operators to charge for the OP's services. | The charging for edge is defined in TS 32.257. | |
| Southbound Interface - Network Resources (SBI-NR) | Fetch Cloudlet locations based on the mobile network data-plane breakout location | |
| Subscribe and receive notifications on UE Mobility events from the network to assist applications | UE mobility events are exposed by NEF (TS 23.502) and EES and ECS subscribes to receive UE mobility notification to assist applications for ACR | |
| Configure traffic steering in the Mobile Network towards Applications orchestrated in Edge Clouds | NEF exposes TrafficInfluence service (TS 23.502), EES uses the TrafficInfluence service to steer the traffic (related to traffic influence) | |
| Receive statistics/analytics, e.g. to influence Application placement or mobility decisions | ||
| Receive information related to the network capabilities, such as QoS, policy, network information, etc | NEF exposes events related to network capabilities, EES and ECS subscribes to receive network capability related information. | |
| UNI | Application Instantiation/Termination, e.g. based on triggers from the UNI | |
| Application Endpoint exposure towards User Clients (UC) via the UNI | EES (clause 8.4.2 and clause 8.5) | |
| Application Placement decisions, e.g. based on measurements/triggers from the UNI |
3)
Federation Broker and Federation Manager Roles: The Federation Broker and Manager Roles in the OP are responsible for interfacing with other OPs via the East-West Bound Interface. Table A-3 shows typical scenarios enabled by the Federation Broker and Federation Manager Roles as indicated in Operator Platform Telco Edge Requirements [3] and their mapping with 3GPP EDGEAPP architecture.
| Interface | Scenario | Mapping to 3GPP EDGEAPP |
|---|---|---|
| EWBI | Federation Interconnection Management | Clause 7.5.2 of TS 28.538 "Edge Federation Establishment". |
| Edge Cloud Resource Exposure and Monitoring towards partner OPs | ||
| Network and Analytics Capabilities Exposure towards partner OPs | ||
| Application Images and Application metadata transfer towards partner OPs | Application instances are managed by 3GPP Management System as VNFs. Application Image and metadata management is considered part of VNF onboarding. VNF onboarding is defined in ETSI NFV IFA013. | |
| Application Instantiation/Termination towards partner OPs | ||
| Application Monitoring towards partner OPs | ||
| Edge Cloud Resource Catalogue exposure | EES (Exposing EAS profile) (See NOTE 1) | |
| Service Availability in visited networks |
ECS (Table 8.3.3.3.3-2 and clause 8.17.2.4 of TS 23.558)
(See NOTE 2) | |
|
NOTE 1:
Edge Cloud Resource Catalogue may contain information other than EAS profile which is within scope of SA5.
NOTE 2:
EASIDs are considered as available services in partner ECSP and are exchanged between ECSs of home ECSP and partner ECSP.
|
||
Based on the mapping tables in this clause, EES and ECS of 3GPP EDGEAPP architecture can be mapped to take responsibilities of the some roles as defined in GSMA OPG reference architecture.
$ Change history p. 24
