2024-04-30: SP-EDC Minutes

Attendees & Representation

Type @ and your name to indicate your attendance

LF Staff:

Community:

Agenda

• Roll Call
• Action Items Review
• Agenda Bashing

  • 1.API current Situation

    
    

    
    

    
    

    Traffic Influence.

    • Minor changes may be needed to comply with conformance in API guidelines ( Issue 191). Closed
    • PR 231 To update spectral.yml v19.03.2024: Corrected camara-http-methods rule. Merged.
    • Changes done in documentation to include EdgeCloudZone (Discussion 196 to be closed.)
    • PR 167 TI API v0.9.3 for approval and merger. Once spectral.yml has been updated.
    • New Discussion 230 Potential requirement: Device Source IP Port

    Life Cycle Management.

    • PR 208 merged
    • Implementation of Consent Management (3Legs) and X-Correlator to be included. New PR Will be created.

    New API to Discovery App Endpoint

    • New API based on Discussion 212 raised by Thomas Vits 
    • A first draft will be presented at the next meeting by TEF 

Simple Edge Discovery.

• • • PR 228 SED API v1.0.0 to be merged.

Edge Cloud Family.

• • • E2E Use case/User Story first draft based on Discussion 206 to be contributed by TEF
    • Repository Maintance
      • Releases in Discussion 227
      • New way of documenting APIs in Discussion 229
      • Organize Folder Structure
      • Review pending PRs, Issues and Discussions

2.Changes on Traffic Influence API

New requirements 

Automatic Mobility – Discussion 218

• • • Intent: “Always provide the optimal routing from the Device to an existing EAS instance”
    • Output: "Routing optimization performed due to Device mobility"

UE Mobility Notification – Discussion 217

• • • Currently under discussion in GSMA OPAG. Definition: “Notification from the TI API to an API Consumer to alert when an UE is in a region/zone where the conditions to have use the TI API are met (e.g. presence of an EAS Instance and an available UPF)“
    • "UE mobility notification" can provide the API Consumer information about the Network topology.
    • Proposal from Fabrizio: keep it simple, for us and for the API Developer, just providing the TI API with two Options:

1.As it is right now. It is a task from the API Consumer to decide when to invoke the API. To support user mobility, the AP Consumer needs to invoke the API many times, every time the user moves in a different Zone.

2.Adding just “Automatic mobility”, in this case the API Consumer invokes the API once and what happen in the network to guarantee the Intent is transparent to the API Consumer

• • • Currently In Frozen State

Device Source IP Port - Discussion 230 

3.Changes on LCM API

• • • How to enable computing resources selection: Flavors or dynamically (Discussion 220)
      • Agree on dynamically approach
      • LCM API v0.9.3 contains the selection of resources based on parameters
      • Implementation of an orchestrated deployment based on files to be defined
    • Discuss on the usage of Unique Identifiers

4.Criteria to release the 1st stable version

Next Steps:

• • • Clean the repository and organize the folders per API - Kevin Smith will help.
    • Review Pending's PRs, Issues and Discussions - Actions created to close/update PR/Issue/Discussion
    • Meet CAMARA Commonalities to pass MegaLinter and Spectral tests for each API Yaml. Modify the following line to pass specific files.
    • spectral.yml:
    •  
    • As the structure folder will be changed there is no needed to change the spectral.yml
    • To check if there is a Tool in CAMARA to find common parameters across APIs by Deepak
    • Consent Management addition in LCM API by Jhon Javier Loza Lluco 
    • Check Common datatypes in LCM API byJhon Javier Loza Lluco and confirm it for TI API by Fabrizio Moggio 
    • Create the new API to cover intent 21 by Telefónica
    • User Story for the 4 APIs by Telefónica

5.Repository Maintance

Pull Requests

Issues

Repository Structure Folder - Kevin Smith will help with this work

Agreed to have the following structure:

The old files will be moved to a new folder under /EdgeCloud/Documentation/SupportingDocuments/Archive*

We also need to check how to manage meetings minutes, currently two folders are referring to that topic. Kevin Smith to ask at Commonalities how to manage the proceedings

6.Other topics

• Any Other Topics

Minutes

Action Item Review

Topic 1

• Comments

Action items