Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update MOM - 2020816.md #32

Merged
merged 1 commit into from
Aug 30, 2022
Merged

Update MOM - 2020816.md #32

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 7 additions & 6 deletions documentation/Minutes/MOM - 2020816.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,8 @@
* Jon Gainsley – (EdgeXR)
* Mahesh Chapalamadugu – (5GFF)
* Raghuram Parvataneni - (5GFF)
* Syed <span class="colour" style="color:var(--vscode-unotes-wysList)"><span class="font" style="font-family:var(--vscode-editor-font-family)"><span class="size" style="font-size:1em">Rehman – (5GFF)</span></span></span>
* Syed Rehman – (5GFF)
* Kevin Smith (5GFF)
* Urvika
* David Ferreira Antoniello (TEF)
* Aurelia Martinez Guerra (TEF)
Expand All @@ -28,8 +29,8 @@

| Item | Who | Description |
| ---- | --- | ----------- |
| EdgeXR API prosal <b>*<span class="font" style="font-family:Calibri, sans-serif"><span class="size" style="font-size:11pt">#26 &amp; #27</span></span>*</b> | EdgeXR | <span lang="EN-GB" style="mso-ansi-language:EN-GB">EdgeXR generated 2 API pull requests for thisgroup:</span><br><ul><li><span lang="EN-GB" style="mso-ansi-language:EN-GB">App APIs (#26)</span></li><li><span lang="EN-GB" style="mso-ansi-language:EN-GB">App session and Discovery APIs (#27)</span></li></ul><span lang="EN-GB" style="mso-ansi-language:EN-GB">Jon Gainsley made a general overview of eachone. During the session, the possibility of sharing the call flow or sequencediagram of the APIs was requested. EdgeXR will fetch this information and shareit.</span> |
| <span lang="EN-GB" style="mso-ansi-language:EN-GB">Comment -<span style="mso-spacerun:yes">&nbsp;</span>Pull Request #21</span> | 5GFF | #21 - Create EdgeCloudApi\_v0.0.5. yaml:Added a list of API questions today in the pull request. An additional specificsession is proposed to discuss the points and questions. It was asked who wouldbe interested in participating, the invitation will be sent to allparticipants. |
| ***<span class="font" style="font-family:Calibri, sans-serif"><span class="size" style="font-size:11pt"><span class="font" style="font-family:Calibri, sans-serif"><span class="size" style="font-size:11pt">Comment - Pull Request </span></span> #24</span></span>*** | 5GFF | #24 - UNI API: Comments from 5GFFabout removing or not the UNI API in this CAMERA group. Mahesh gives firstfeedback indicating that it will not be very easy for non-Telco users to usethe API. This argument is complemented with additional points in the pullrequest. On the part of Telefonica, it is internally evaluating to have ananswer as soon as possible. If necessary, a specific session can be establishedto discuss this point. |
| ***<span class="font" style="font-family:Calibri, sans-serif"><span class="size" style="font-size:11pt">DraftProposal for contributions and approval process in WG - Pull request by DT - #20</span></span>*** | DT | It is proposed to work with different subbranches. During the last two weeks, no comments have been received on what was proposed by DT, so it is assumed that all the members of this group agree with this proposal. The next step will be to move the 5GFF contribution to a subbranch and work on different branches in order to push the proposal to the master branch for approval. In parallel, the way to work to validate the 3 current proposals (MEC Contribution, 5GFF Contribution and EdgeXR Contribution) will be having technical meetings to discuss each point and have the final decision. EdgeXR is interested in managing and organizing these activities. The proposal is that Thomas Vits prepare and elaborate a first proposal for the next technical meeting during the next 2 weeks and have a status in the next bi-weekly session. Different technical activities will be worked on in parallel. |
| Next steps | EdgeXR & TEF | Telefonica and EdgeXR will discuss the next steps to follow will be discussed, beginning with the analysis with the superposition of each proposal and, as a second step, defining the Action Points to have the Edge Cloud API family with all the required functionalities, the discussion of adding or not the UNI API to the Edge Cloud API family |
| EdgeXR API proposal | EdgeXR | EdgeXR generated 2 API pull requests for thisgroup: *App APIs* [#26](https://github.com/camaraproject/EdgeCloud/pull/26) and *App session and Discovery APIs* [#27](https://github.com/camaraproject/EdgeCloud/pull/27). Jon Gainsley made a general overview of each one. During the session, the possibility of sharing the call flow or sequence diagram of the APIs was requested. EdgeXR will fetch this information and share it. |
| Comment - Pull Request [#21](https://github.com/camaraproject/EdgeCloud/pull/21)</span> | 5GFF | [#21](https://github.com/camaraproject/EdgeCloud/pull/26) - Create EdgeCloudApi\_v0.0.5. yaml: Added a list of API questions today in the pull request. An additional specific session is proposed to discuss the points and questions. It was asked who would be interested in participating, the invitation will be sent to all participants. |
| Comment - Pull Request [#24](https://github.com/camaraproject/EdgeCloud/pull/24) | 5GFF | [#24 - UNI API](https://github.com/camaraproject/EdgeCloud/pull/26): Comments from 5GFF about removing or not the UNI API in this CAMERA group. Mahesh gives first feedback indicating that it will not be very easy for non-Telco users to use the API. This argument is complemented with additional points in the pull request. On the part of Telefonica, it is internally evaluating to have an answer as soon as possible. If necessary, a specific session can be established to discuss this point. Kevin explained that the term 'UNI' is specifically defined in public GSMA materials as requiring a client SDK/middleware ('User Client') on the client UE; and that 5GFF does not require that User Client. 5GFF API allows an application in the UE to call HTTP(S) operator-hosted APIs directly without requiring any additional SDK to be on the UE. |
| Draft Proposal for contributions and approval process in WG - Pull request by DT - [#20](https://github.com/camaraproject/EdgeCloud/pull/26) | DT | It is proposed to work with different subbranches. During the last two weeks, no comments have been received on what was proposed by DT, so it is assumed that all the members of this group agree with this proposal. The next step will be to move the 5GFF contribution to a sub-branch and work on different branches in order to push the proposal to the master branch for approval. In parallel, the way to work to validate the 3 current proposals (MEC Contribution, 5GFF Contribution and EdgeXR Contribution) will be having technical meetings to discuss each point and have the final decision. EdgeXR is interested in managing and organizing these activities. The proposal is that Thomas Vits prepare and elaborate a first proposal for the next technical meeting during the next 2 weeks and have a status in the next bi-weekly session. Different technical activities will be worked on in parallel. |
| Next steps | EdgeXR & TEF | Telefonica and EdgeXR will discuss the next steps to follow will be discussed, beginning with the analysis with the superposition of each proposal and, as a second step, defining the Action Points to have the Edge Cloud API family with all the required functionalities, the discussion of adding or not the UNI API to the Edge Cloud API family |