...
Gliffy | ||||||
---|---|---|---|---|---|---|
|
Gliffy | ||||
---|---|---|---|---|
|
Gliffy | ||||||
---|---|---|---|---|---|---|
|
Gliffy | ||||||
---|---|---|---|---|---|---|
|
...
- CSMF(eMBB Nationwide) => NSMF (eMBB Nationwide Service Profile)
- NSMF creates eMBB Nationwide Slice Profile
- NSMF => NSSMF (eMBB Nationwide Slice Profile)
- NSSMF Matches eMBB Slice Profile to:
- NE (UP Network Slice Subnet Service, RAN Network Slice Subnet Service)
- SE (UP Network Slice Subnet Service, RAN Network Slice Subnet Service)
- S (UP Network Slice Subnet Service, RAN Network Slice Subnet Service)
- C (Central Network Slice Subnet Service)
- N (UP Network Slice Subnet Service, RAN Network Slice Subnet Service)
- NW (UP Network Slice Subnet Service, RAN Network Slice Subnet Service)
- SW (UP Network Slice Subnet Service, RAN Network Slice Subnet Service)
- NSSMF create Configuration data and Slice Profile for each instance:
- NE (UP, RAN)
- SE (UP, RAN)
- S (UP, RAN)
- C (Central)
- N (UP, RAN)
- NW (UP, RAN)
- SW (UP, RAN)
- NSSMF Instantiate Network Slice Subnet Instances:
- NSSMF => NSSMF (C)
- NSSMF (C, Central) => SO (Central Network Slice Service (C Parameters)
- SO => NFVO (Central Network Slice Network Service)
- NFVO Instantiates VNFs
- NFVO registers Central VNFs with A&AI
- NFVO registers Central Network Service instance with A&AI
- SO registers Central Service instance
- NSSMF configures Central VNFs(C eMBB data)
- NSSMF(C) registers C NSSI (Capacity Available, Capacity Allocated )
- NSSMF => NSSMF(NE, UP)
- NSSMF(NE, UP) => SO( UP Network Slice Service (NE Parameters))
- NSSMF => NSMF(NE, RAN)
- NSSMF(NE, RAN) => SO (RAN Network Slice Service (NE Parameters)
- ...
- NSSMF => NSSMF (C)
- Resulting Network Service Deployment:
-
Gliffy macroId 64de5485-b7ac-406d-be81-f9c87eb4c00b name SliceSubnet-NS Deployment pagePin 1
-
- NSSMF NSSMF registers Nationwide NSSI (Capacity Available, Capacity Allocated )
- NSMF registers Nationwide eMBB Slice
- CSMF completes
Resulting Instance info:
Gliffy | ||||||
---|---|---|---|---|---|---|
|
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 but NOT filled in at DT, 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 ?
Answer: allottedresource_providing_service_uuids
Question #3: the fact that for the realization of a CST, it will be required a NST at run time, it seems it is NOT indicated at Design Time so I was wondering where it will be indicated to ensure the orchestrator will look for a NST instead of ANY other type of object (i.e. a NSST or a generic Service or even a Resource).
Question #4: I was also trying to prepare a similar representation from a resource/service instances prospective. Do you have any picture you can share ?