The scope of this page is to explore the use of the Allotted Resource model at Design Time and Run Time in the context of the Network Slicing. 

This analysis is based on a Presentation, User Operation Guidance for E2E Network Slicing Use case, from 

LIN MENG,  Swaminathan S,  Chuanyu Chen shared during the latest LFNetworking virtual Event in Aprile 2020 (https://wiki.lfnetworking.org/display/LN/2020+April+Technical+Event+Schedule)

The best understanding of the model today is reported :

NOTEs:

1) CST chain of objects and NST chain do not have any relation at DT. 

• Alloted resource is used to tell the relationship that will be defined at Run Time. The NST will be selected at runtime.

2) The VF:NSTAR is defined as an allotted Resource (see step 3) and it is composed by the Allotted Resource v1.0 template. 

Allotted Resource v1.0 is a default template already present in ONAP SDC, it is NOT an object created by a user.

----

Only relevant slides for the modeling discussion have been capture in the next pages.

Design EmbbCn Service Template

Design EmbbNst Service Template

Design Allotted Resource

Observation #1: The VF:NSTAR is defined as an allotted Resource (see step 3) and it is composed by the Allotted Resource v1.0 template. 

Allotted Resource v1.0 is a default template already present in ONAP SDC, it is NOT an object created by a user.

Question #1 : Are the providing_service_uuids (variant and invariant) defined at DT  ?

Answer: Providing_service_invariant_uuid and providing_service_uuid are declared input in SDC, which will be filled in the runtime with the selected NST service invariant id and service id.

CST and NST has NO relation at Design Time

Design Service Profile Template

Question #2 : Are the allottedresource_providing_service_uuids (variant and invariant) defined at DT  ?