Agenda

Antitrust Policy

• Action Items Review

  1. Edge Dicovery Services API

  2. Update Edge Application Mangement API

  3. TI API Planning

  4. AOB

Minutes

The evolution of Edge Discovery Service API:

1.Still pending to merge PR263, update old exposure and experience management API to Edge Discovery Services. Any news about the question to have an API for several Camara groups (Application Profiles )??

2.There are three issues created by Javier to update the new functionalities of EDS in the existing APIS, trying to avoid to create new APIs.

1.Issue 285, this issue proposes to combine AED with EDS:

¡GET /app-endpoints AED API: Returns the closest endpoint of the App Instance for an specific UE. Based on UEIdentity and AppID
This functionality can be merged to improve Application Endpoint Discovery capability, allowing endpoint discovery based on App Profile, Region, Subscriber Density, UEIdentity and AppId.

2.Issue 288, this issue proposes to combine EAM with EDS:

¡Improve Edge Cloud Zones discovery capability combining the functionalities, allowing developers to discover them based on Application Profile, Region, Subscriber, UEIdentity and Status.

¡There is a conflict with the Application Profiles capability of the EDS API and the requiredResources object of the EAM API, we need to combine them into one API.

3.Issue 286, EDS API: Application Endpoints functionality to be a new API.

Application Endpoint Discovery:

We have some PRs to update EAM:

Approval from Jon in the PR280 about the update of Required resources. All solved, one approval, Merge??

Four PRs to update the API:

1. PR252  Add the missing AppProvider to the AppManifest model. This is the oldest one, I think we can Merge it.

2. PR298  Add Get/Apps to retrieve created applications.

3. PR302 Removes appId from the appinstances path.

4. PR305  Change AppManifest version from int to string

Topic 1

• Comments

Action items