July 15, 2020 Project deliverable Open Access

Elian Kraja; Leonardo Agueci; Giada Landi; Arturo Azcorra-Salona; Gines Garcia-Aviles; Jaime Garcia-Reinoso; Luis Felix Gonzalez-Blazquez; Christos Ntogkas; Evangelos Kosmatos; Panagiotis Demestichas; Vera Stavroulaki; Nelly Giannopoulou; Ioannis Belikaidis; Vassilis Foteinos; Thanos Gkiolias

MARC21 XML Export

<?xml version='1.0' encoding='UTF-8'?>
<record xmlns="http://www.loc.gov/MARC21/slim">
  <leader>00000nam##2200000uu#4500</leader>
  <datafield tag="041" ind1=" " ind2=" ">
    <subfield code="a">eng</subfield>
  </datafield>
  <controlfield tag="005">20200715125920.0</controlfield>
  <controlfield tag="001">3946255</controlfield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">NEXTWORKS S.r.l.</subfield>
    <subfield code="a">Leonardo Agueci</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">NEXTWORKS S.r.l.</subfield>
    <subfield code="a">Giada Landi</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">Universidad Carlos III de Madrid</subfield>
    <subfield code="a">Arturo Azcorra-Salona</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">Universidad Carlos III de Madrid</subfield>
    <subfield code="a">Gines Garcia-Aviles</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">Universidad Carlos III de Madrid</subfield>
    <subfield code="a">Jaime Garcia-Reinoso</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">Universidad Carlos III de Madrid</subfield>
    <subfield code="a">Luis Felix Gonzalez-Blazquez</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">WINGS ICT SOLUTIONS Ltd.</subfield>
    <subfield code="a">Christos Ntogkas</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">WINGS ICT SOLUTIONS Ltd.</subfield>
    <subfield code="a">Evangelos Kosmatos</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">WINGS ICT SOLUTIONS Ltd.</subfield>
    <subfield code="a">Panagiotis Demestichas</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">WINGS ICT SOLUTIONS Ltd.</subfield>
    <subfield code="a">Vera Stavroulaki</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">WINGS ICT SOLUTIONS Ltd.</subfield>
    <subfield code="a">Nelly Giannopoulou</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">WINGS ICT SOLUTIONS Ltd.</subfield>
    <subfield code="a">Ioannis Belikaidis</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">WINGS ICT SOLUTIONS Ltd.</subfield>
    <subfield code="a">Vassilis Foteinos</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">WINGS ICT SOLUTIONS Ltd.</subfield>
    <subfield code="a">Thanos Gkiolias</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">2612820</subfield>
    <subfield code="z">md5:5473f963a3689e2d4f204ae2763a512e</subfield>
    <subfield code="u">https://zenodo.org/record/3946255/files/D5.5 Performance diagnosis mechanism and reporting methodology document.pdf</subfield>
  </datafield>
  <datafield tag="542" ind1=" " ind2=" ">
    <subfield code="l">open</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="c">2020-07-15</subfield>
  </datafield>
  <datafield tag="909" ind1="C" ind2="O">
    <subfield code="p">openaire</subfield>
    <subfield code="p">user-5g-ppp</subfield>
    <subfield code="o">oai:zenodo.org:3946255</subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="u">NEXTWORKS S.r.l.</subfield>
    <subfield code="a">Elian Kraja</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">D5.5 Performance diagnosis mechanism and reporting methodology document</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">user-5g-ppp</subfield>
  </datafield>
  <datafield tag="536" ind1=" " ind2=" ">
    <subfield code="c">815074</subfield>
    <subfield code="a">5G European Validation platform for Extensive trials</subfield>
  </datafield>
  <datafield tag="540" ind1=" " ind2=" ">
    <subfield code="u">https://creativecommons.org/licenses/by/4.0/legalcode</subfield>
    <subfield code="a">Creative Commons Attribution 4.0 International</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="7">
    <subfield code="a">cc-by</subfield>
    <subfield code="2">opendefinition.org</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">&lt;p&gt;The main objective of 5G EVE WP5 is the design and development of a testing and validation framework as part of the 5G EVE platform. The details of the testing and validation methodology as well as the different components implemented in order to realise this are presented in detail in D5.2 [1].&lt;br&gt;
In the testing and validation process, two features are of paramount importance for a practical and useful platform for the experimenters willing to run their experiments on top of 5G EVE infrastructure: a) the generation of a complete and instructive validation report; b) the provision of a tool for performance diagnosis and root cause analysis.&lt;br&gt;
Regarding the first aspect, the development of a complete and well-defined results analysis and validation report is of high importance because it provides experimenters with clear answers to their initial validation questions. In addition, this report gives a complete picture of the testing and validation process realised using the 5G EVE platform including, in addition to passed/failed results, information about the actual testing process, the environment in which the tests are executed, the different test cases executed to provide the results, a set of high level configuration information. All this information can be provided in a way that will ensure the transparency and repeatability of the entire testing and benchmarking process.&lt;br&gt;
This document presents the details of the approach adopted to build the experiment validation reports. According to the approach the final report can be consolidated in a composition of 4 separate reports created by the elements of the EVE Platform. This happens because, while the main focus of the experiments is the KPI validation, the information regarding the site, the conditions and the technologies used can be extremely useful and insightful to the experimenter as well.&lt;br&gt;
Regarding the second aspect, 5G EVE extends the functionalities of the testing and validation process described in D5.2 [1] with performance diagnosis functionalities. The main objectives of the developed performance diagnosis mechanism are: a) to provide insights on the execution and validation of the tests, b) to execute diagnostics and root cause analysis mechanisms in case of performance degradations.&lt;br&gt;
In this document the performance diagnosis mechanism designed and developed in the project is presented, with their main functionalities including to perform a deeper KPI analysis, to execute anomaly detection on the collected metrics, to perform Root Cause Analysis (RCA) and finally generate a set of proposed actions for alleviating any performance degradation. In addition, initial results from the application of the performance diagnosis mechanisms on emulated networks are presented and analysed.&lt;/p&gt;</subfield>
  </datafield>
  <datafield tag="773" ind1=" " ind2=" ">
    <subfield code="n">doi</subfield>
    <subfield code="i">isVersionOf</subfield>
    <subfield code="a">10.5281/zenodo.3946254</subfield>
  </datafield>
  <datafield tag="024" ind1=" " ind2=" ">
    <subfield code="a">10.5281/zenodo.3946255</subfield>
    <subfield code="2">doi</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">publication</subfield>
    <subfield code="b">deliverable</subfield>
  </datafield>
</record>