<ol>
<li><ol>
<li><ol>
<li><font color="#e0121d"><b>Mapping ETSI NFV Model to SID</b></font></li></ol>
</li><br/></ol>
</li><br/></ol>
<font color="#29313b">In this section, we propose a mapping of some of the key artefacts of the ETSI NFV model to artefacts from the SID.</font><br/><font color="#29313b">Key references used in this proposal are listed below:</font><br/><font color="#29313b">From ETSI : </font><br/><ol>
<li><font color="#29313b">ETSI GS NFV 003, v1.3.1, 2018-01<br/>Terminology for Main Concepts in NFV</font></li><li><font color="#29313b">ETSI GS NFV-IFA 015, v2.1.1, 2017-01<br/>Report on NFV Information Model</font></li><li><font color="#29313b">ETSI GS NFV-IFA 011, v2.1.1, 2016-10<br/>VNF Packaging Specification </font></li><li><font color="#29313b">ETSI GS NFV-IFA 013, v2.1.1, 2016-10<br/>Interface and Information Model Specification </font></li><li><font color="#29313b">ETSI GS NFV-IFA 014, v2.1.1, 2016-10<br/>Network Service Templates Specification </font></li><li><font color="#29313b">ETSI IFA24<br/>TouchPoints with TM Forum Service Model</font></li></ol>
<font color="#29313b">From TM Forum: <br/></font><br/><ol>
<li><font color="#29313b">TR255 Resource Function – Activation and Configuration R17.5.0 <br/></font></li><li><font color="#29313b">TR255A Connectivity Patterns for Virtualized Management R17.5.0<br/></font></li></ol>
<font color="#29313b">Some aspects that have been taken into consideration to drive this work:</font><br/><br/><ul>
<li><font color="#29313b">As discussed in [7], the distinction between NS and NF was deemed to be artificial, and it was decided that the same functionality could be handled by one or the other.</font></li><li><font color="#29313b">There was an issue with the word “Network” as this limits the scope. Resource Function is more general as “Resource” can refer to “Network” but also other types of resources such as storage and compute.</font></li><li><font color="#29313b">Further, the concept of Resource Function was designed to cover VNF Forwarding Graph, and the SDN concepts of Service Function and Service Function Chain.</font></li></ul>
<font color="#29313b">Consequently, the term Resource Function (RF) has been used to replace Network Service (NS) and Network Function. Moreover, it was decided that RF composite would be used to replace NS (both atomic and composite) and composite NFs, and RF atomic would be used to replace atomic NFs. It was decided that having atomic and composite NS and NF is redundant.</font><br/><font color="#29313b">Sometimes the mapping cannot be represented one to one, as a concept used in the ETSI model may correspond to several concepts from the SID. Example: VNF is a “function” but also a “software”.</font><br/><font color="#29313b">It is one of the reasons, among others, why it was decided not to try to integrate the ETSI artefacts as specialization (using inheritance or other mechanisms) of SID artefacts in the model, but, instead use a table to capture the mapping information. </font><br/><font color="#29313b">This mapping tables are shown below.</font><br/>