Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x
Top   in Index   Prev   Next

TR 28.903
Study on alignment with ETSI MEC for edge computing management

V19.0.0 (PDF)  2025/09  28 p.
V18.0.1  2023/06  28 p.
Rapporteur:
Mr. Li, Shitao
Huawei Tech.(UK) Co.. Ltd

full Table of Contents for  TR 28.903  Word version:  19.0.0

each clause number in 'red' refers to the equivalent title in the Partial Content
Here   Top
1Scope  p. 7
2References  p. 7
3Definitions of terms, symbols and abbreviations  p. 8
3.1Terms  p. 8
3.2Symbols  p. 8
3.3Abbreviations  p. 8
4Related Work in Other SDOs  p. 8
4.1ETSI MEC  p. 8
4.2GSMA OPG  p. 9
5Issue investigations and potential solutions for alignment with ETSI MEC  p. 11
5.1Key Issue# 1: Management of collocated platforms for EES and MEC platform  p. 11
5.1.1Description  p. 11
5.1.2Potential Requirements  p. 12
5.1.3Potential solutions  p. 12
5.1.3.1Potential solution#1  p. 12
5.1.3.2Solution evaluation  p. 12
5.2Key Issue# 2: Application lifecycle management  p. 12
5.2.1Description  p. 12
5.2.2Potential solutions  p. 12
5.2.2.1Potential solution#1  p. 12
5.2.2.1.1Description  p. 12
5.2.2.1.2Solution evaluation  p. 13
5.2.2.2Potential solution# mapping application lifecycle management operation produced by MEO/MEAO with EAS LCM requirements  p. 13
5.2.2.2.1Description  p. 13
5.2.2.2.2Solution evaluation  p. 14
6Issue investigations and potential solutions for alignment with GSMA OPG  p. 14
6.1Key Issue# 1: Issue for resource reservation  p. 14
6.1.1Description  p. 14
6.1.2Potential Requirements  p. 15
6.1.3Potential solutions  p. 15
6.1.3.1Potential solution#1  p. 15
6.1.3.2Solution evaluation  p. 16
6.2Key Issue#2: Issue for federation management  p. 16
6.2.1Description  p. 16
6.2.2Potential Requirements  p. 17
6.2.3Potential Solutions  p. 17
6.3Key Issue#3: EDN Sharing  p. 18
6.3.1Description  p. 18
6.3.2Potential Requirements  p. 18
6.3.3Potential Solutions  p. 18
6.4Key Issue#4: Federated EAS resource reservation management  p. 18
6.4.1Description  p. 18
6.4.2Potential Requirements  p. 19
6.4.3Potential Solutions  p. 19
6.5Key Issue#5: Federated EAS deployment and termination  p. 19
6.5.1Description  p. 19
6.5.2Potential Requirements  p. 19
6.5.3Potential Solutions  p. 19
6.6Key Issue# 6: Virtual Infrastructure Resource Requirements  p. 20
6.6.1Description  p. 20
6.6.2Potential Requirements  p. 20
6.6.3Potential Solution  p. 20
6.7Key Issue# 7: Querying Available Edge Services  p. 20
6.7.1Description  p. 20
6.7.2Potential Requirements  p. 20
6.7.3Potential Solution  p. 20
6.8Key Issue# 8: SLA Requirements Key Issue  p. 21
6.8.1Description  p. 21
6.8.2Potential Requirements  p. 21
6.8.3Potential Solution  p. 21
6.9Key Issue# 9: EAS relocation policies Key Issue  p. 21
6.9.1Description  p. 21
6.9.2Potential Requirements  p. 22
6.9.3Potential Solution  p. 22
6.10Key Issue# 10: Application Resource Catalogue  p. 23
6.10.1Description  p. 23
6.10.2Potential Requirements  p. 23
6.10.3Potential Solution  p. 23
7Conclusion and recommendation  p. 24
7.1Conclusion and recommendation for alignment with ETSI MEC  p. 24
7.1.1Issue#1: Management of collocated platforms for EES and MEC platform  p. 24
7.1.2Issue#2: Application lifecycle management  p. 24
7.2Conclusion and recommendation for alignment with GSMA OPG  p. 24
7.2.1Issue#1: Issue for resource reservation  p. 24
7.2.2Issue#2: EAS federation management  p. 24
7.2.3Issue#3: EDN Sharing  p. 24
7.2.4Issue#4: Federated EAS resource reservation management  p. 24
7.2.5Issue#5: Federated EAS deployment and termination  p. 25
7.2.6Issue#6: Virtual Infrastructure Resource Requirements  p. 25
7.2.7Issue#7: Querying Available Edge Services  p. 25
7.2.8Issue#8: SLA Requirements key issue  p. 25
7.2.9Issue#9: EAS relocation policies  p. 25
7.2.10Issue#10: Application Resource Catalogue  p. 25
$Change history  p. 26

Up   Top