PRs

Opened by

Action

Application Endpoint Discovery First Contribution

TEF – Cristina (May 20 2024)

To be reviewed by the Edge Cloud Community

TI API Rel 0.9.4 new Documentation

TIM - Fabrizio (May 16 2024)

To be reviewed by the Edge Cloud Community

More descriptive resource names in MEC Exposure and Experience Management

Leo Chely (Dec 6 2023)

@Mahesh Chapalamadugu to update the PR to comply with Commonalities.

Update README.MD to reflect new folder structure

5GFF-Kevin (Aug 24 2023)

To be closed - @Kevin Smith 

Draft models for GSMA/EdgeXR and 5GFF

5GFF-Kevin (Aug 8 2023)

Move it to Discussions – @Kevin Smith 

Create Simple_Edge_Discovery_User_story.md

5GFF-Kevin (Jul 18 2023)

To have a final conclusion and close the PR. Move the conclusion to Device Identifiers in Edge Cloud APIs where a common Device Object for the Edge Cloud APIs needs to be agreed.

Edge cloud developer journey proposal

Mahesh (Feb 21 2023)

@Mahesh Chapalamadugu  to check it and close it.

Issues

Opened by

Action

TI API: 3Legs for optional parameter

Fabrizio Mogio (May 23 2024)

To be consider

Rename traffic Influence in .yaml file line 7

Mark Cornall (May 20 2024)

To be reviewed

TI API Readiness Checklist

Fabrizio (May 20 2024)

To be implemented

MEC Exposure & Experience Management ressource names don't follow naming conventions or are not descriptive enough

Leo Chely (Nov 10 2023)

@Mahesh Chapalamadugu to check it and close it.

README for code folder needs updating

5GFF-Kevin (Aug 24 2023)

Keep it opened

Usage of IP Address to identify a Device in Traffic Influence API

Capgemini-Deepak (Aug 7 2023)

To have a final conclusion and close the PR. Move the conclusion to Device Identifiers in Edge Cloud APIs where a common Device Object for the Edge Cloud APIs needs to be agreed.

[Exposure & Experience Management API] Unused definitions in the specification

Carlos Lozano (Oct 6 2022)

@Mahesh Chapalamadugu to check it and close it.