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; | |
Application Onboarding | The Application Provider uses the NBI to provide application images and metadata to the OP Federation Broker/Manager Role | ||
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; | ||
Application Resource Consumption Monitoring | The Application Provider observes resource consumption of application instances, using the resource data model | ||
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) |
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); | |
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. | ||
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 |
Interface | Scenario | Mapping to 3GPP EDGEAPP |
---|---|---|
EWBI | Federation Interconnection Management | |
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 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.
|