...

The scope of this page is to explore the use of ETSI  (Nested) Network Services model at Design Time and Run Time in the context of the 5G Network Slicing. 

The Guilin Service IM allows for a (nested) Network Service (NS) model that is referenced from an ONAP Service.  Multiple ONAP Services may reference the same NS Descriptor and multiple ONAP Service Instances may reference an NS Instance.

Since the NS can be composed VNFs, CNFs, PNFs and nested NSs, the ETSI NS model is well suited to describe the hierarchical structure of 3GPP Network Slice Subnets.

Image ModifiedImage RemovedImage Added

Design Time:

Design Sequence:

1. Onboard 5G Core NFs (NRF, PCF, UDM, AUSF, NEF, AMF, SMF, UPF, ...) into SDC
2. Onboard RAN NFs (vCU, vDU) insto into SDC
3. In SDC, design a "Central" Network Service composed of
   1. "centralCentral" NFs (NRF, PCF, UDM, AUSF, NEF)
   2. Virtual Link (Control Network) for the SBA interface
   3. SAP(s) for all of the exposed entry points
4. SDC distribute the resulting SOL007 NS package to the ETSI Catalog (and any one else interested, SO??)
5. In SDC, design a "User Plane" Network Service composed of:
   1. "user plane" NFs (AMF, SMF, UPF)
   2. Virtual Link (Control Network) for the SBA interface
   3. Virtual Link (RAN Network) for the interface to the RAN components
   4. Virtual Link (Data Network) for the (external) data/internet interface
   5. SAP(s) for all of the exposed entry points
6. SDC distribute the resulting SOL007 NS package to the ETSI Catalog (and any one else interested, SO??)
7. In SDC, design a "RAN" Network Service composed of:
   1. "RAN" NFs (CU, DU)
   2. Virtual Link (Control Network) for the SBA OAM interface
   3. Virtual Link (RAN Network) for the interface to the RAN components
   4. Virtual Link (Front-Haul) for the radio interface
   5. SAP(s) for all of the exposed entry points
8. SDC distribute the resulting SOL007 NS package to the ETSI Catalog (and any one else interested, SO??)
9. In SDC, design a "Complete" Network Service composed of:
   1. Scalable reference to the RAN Central NS
   2. Scalable reference to the UP NS
   3. Scalable reference to the RAN NS
   4. Virtual Link (Control Network) for the OAM interface
   5. Virtual Link (Data Network) for the (external) data/internet interface
   6. Virtual Link (RAN Network) for the interface to the RAN components
   7. SAP(s) for all of the exposed entry points
10. SDC distribute the resulting SOL007 NS package to the ETSI Catalog (and any one else interested)
11. In SDC, Design a "Central" Service composed of
    1. A reference to the "Central" Network Service
    2. A CDS blueprint (CBA) for configuring the "Central" Service
    3. Behavioral policies for the "Central" Service
12. SDC distribute the resulting "Central" Service package
13. In SDC, Design a "User Plane" Service composed of
    1. A reference to the "UP" Network Service
    2. A CDS blueprint (CBA) for configuring the "UP" Service
    3. Behavioral policies for the "UP" Service
14. SDC distribute the resulting "UP" Service package
15. In SDC, Design a "RAN" Service composed of
    1. A reference to the "RAN" Network Service
    2. A CDS blueprint (CBA) for configuring the "RAN" Service
    3. Behavioral policies for the "RAN" Service
16. SDC distribute the resulting "RAN" Service package
17. In SDC, Design a "Complete" Service composed of
    1. A reference to the "Complete" Network Service
    2. A CDS blueprint (CBA) for configuring the "Complete" Service
    3. Behavioral policies for the "Complete" Service
18. SDC distribute the resulting "Complete" Service package

Runtime

Starting state:

1. SOL004 Packages for Central, UP and RAN NFs in the ETSI Catalog
2. SOL007 Packages for Central, UP, RAN and Complete NSs in the ETSI Catalog
3. Service Packages for Central, UP, RAN, and Complete NSs in SO Catalog
4. Policies available in DCAE
5. CBAs in CDS
6. VIM & CISM regions (NE, SE, S, C, N, NW, SW) registered in A&AI
7. 6 RAN/UP Sites and one Central Site available and registered in A&AI

Gliffy
size 600 name VIM-CISM-Networks pagePin 1

Instantiate nationwide eMBB Slice :

1. CSMF(eMBB Nationwide) => NSMF (eMBB Nationwide Service Profile)
2. NSMF creates/selects eMBB Nationwide Slice Profile
3. NSMF => NSSMF (eMBB Nationwide Slice Profile, Complete Network Slice Subnet Service Template)
4. NSSMF Matches eMBB Nationwide Slice Profile and decomposes it to:
   1. NE (UP Network Slice Subnet Service, RAN Network Slice Subnet Service)
   2. SE (UP Network Slice Subnet Service, RAN Network Slice Subnet Service)
   3. S (UP Network Slice Subnet Service, RAN Network Slice Subnet Service)
   4. C (Central Network Slice Subnet Service)
   5. N (UP Network Slice Subnet Service, RAN Network Slice Subnet Service)
   6. NW (UP Network Slice Subnet Service, RAN Network Slice Subnet Service)
   7. SW (UP Network Slice Subnet Service, RAN Network Slice Subnet Service)
5. NSSMF create creates Configuration data and Slice Profile for each instance:
1. NE (UP, RAN)
2. SE (UP, RAN)
3. S (UP, RAN)
4. C (Central)
5. N (UP, RAN)
6. NW (UP, RAN)
7. SW (UP, RAN)
6. NSSMF Instantiate Instantiates Network Slice Subnet Instances:
   1. NSSMF => NSSMF (C, Central)
      1. NSSMF (C, Central)  => SO (Central Network Slice Service (C Parameters)
      2. SO => NFVO (Central Network Slice Network Service)NSSMF configures Central VNFs
         1. NFVO Instantiates VNFs
         2. NFVO registers Central VNFs with A&AI
         3. NFVO registers Central Network Service instance with A&AI
      3. SO registers Central Service instance 
      4. 1. sets up network connection points to appropriate networks and works with VNFM(s) to Instantiate VNFs and CNFs
      5. NSSMF configures Central VNF/CNF/PNFs(C eMBB data)
      6. NSSMF(C) registers C NSSI (Capacity Available, Capacity Allocated ) in A&AI
   2. NSSMF => NSSMF(NE, UP)
      1. NSSMF(NE, UP) => SO( UP Network Slice Service (NE Parameters))
   3. NSSMF => NSMF(NE, RAN)
      1. NSSMF(NE, RAN)  => SO (RAN Network Slice Service (NE Parameters)
   4. ...
7. Resulting Network Service Deployment:
   1.  

      Gliffy
      64de5485-b7ac-406d-be81-f9c87eb4c00b macroId size 600 name SliceSubnet-NS Deployment pagePin 1

   NSSMF 

   1. 3

8. NSSMF registers Nationwide NSSI (Capacity Available, Capacity Allocated ) with A&AI
9. NSMF registers Nationwide eMBB Slice
10. CSMF completes

Resulting Instance info:

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 ?

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.

Image Removed

Design EmbbCn Service Template

Image Removed

Image Removed

Image Removed

Image Removed

Design EmbbNst Service Template

Image Removed

Image Removed

Image Removed

Image Removed

Design Allotted Resource

Image Removed

Image Removed

Image Removed

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.

Image Removed

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

Image Removed

Image Removed

Image Removed

Image Removed

Image Removed

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). 

New Slice Request (NE Enterprise):

1. CSMF(NE Enterprise) => NSMF (NE Enterprise Service Profile)
2. NSMF creates NE Enterprise Slice Profile
3. NSMF => NSSMF (NE Enterprise Slice Profile)
4. NSSMF Matches NE Enterprise Slice Profile to:
   1. NE (UP Network Slice Subnet Service, RAN Network Slice Subnet Service)
   2. C (Central Network Slice Subnet Service)
5. NSSMF create Configuration data and Slice Profile for each instance:
1. NE (UP, RAN) Slice Profiles
2. C (Central) Slice Profile
6. NSSMF Identifies existing Network Slice Subnet Instances with enough capacity for NE Enterprise Slice Profile:
   1. NE RAN NSSI
   2. NE UP NSSI
   3. C Central NSSI
7. NSSMF => NSSMF (C)
   1. NSSMF(C) configures Central VNFs(C NE Enterprise data)
   2. NSSMF(C) update C NSSI (Capacity Available, Capacity Allocated )
8. NSSMF => NSSMF(NE, UP)
   1. NSSMF(NE, UP)  configures NE, UP VNFs(UP NE Enterprise data)
   2. NSSMF(NE, RAN) updates NE RAN NSSI (Capacity Available, Capacity Allocated )
9. NSSMF => NSMF(NE, RAN)
   1. NSSMF(NE, UP)  configures NE, UP VNFs(UP NE Enterprise data)
   2. NSSMF(NE, RAN) updates NE UP NSSI (Capacity Available, Capacity Allocated )
10. NSSMF registers NE Enterprise NSSI (Capacity Available, Capacity Allocated ) with A&AI
11. NSMF registers NE Enterprise Slice
12. CSMF completes

Resulting Instance info:

New mIOT Slice

Example of adding a new URLLC Slice including Transport

1. CSMF(SFO URLLC) => NSMF (SFO URLLC Service Profile)
2. NSMF creates SFO URLLC Slice Profile
3. NSMF => NSSMF (SFO URLLC Slice Profile)
4. NSSMF Matches SFO URLLC Slice Profile to:
   1. SFO Site (Edge Network Slice Subnet Service)
   2. C (Central Network Slice Subnet Service)
   3. Nationwide Slice Subnet Service ("Data Network" and "Control Network")
   4. SFO Site Radio Links
5. NSSMF create Configuration data and Slice Profile for each instance:
1. SFO (Edge) Slice Profile
2. C (Central SFO URLLC) Slice Profile
3. Nationwide SFO URLLC Slice Profile
6. NSSMF Identifies existing Nationwide NSSI and C NSSI with enough capacity for SFO URLLC Slice Profile but needs to instantiate new Edge NSSI:
   1. Existing Nationwide NSSI (Data Network and Control Network)
   2. Existing C NSSI
   3. New SFO URLLC NSSI
7. NSSMF => NSSMF (C, Central SFO URLLC Slice Profile)
   1. NSSMF(C) configures Central VNFs(C Central SFO URLLC data)
   2. NSSMF(C) update C NSSI (Capacity Available, Capacity Allocated )
8. NSSMF => NSSMF(Nationwide, Nationwide SFO URLLC Slice Profile)
   1. NSSMF(Nationwide, Complete)  configures Nationwide SFO URLLC Data Network and Control Network
   2. NSSMF(Nationwide, Complete) updates Nationwide NSSI (Capacity Available, Capacity Allocated )
9. NSSMF => NSMF(SFO, Edge)
   1.  NSSMF (SFO, Edge)  => SO (Edge Network Slice Service (SFO Parameters)
   2. SO => NFVO (Edge Network Slice Network Service)
      1. NFVO Configures "internal RAN Network"
      2. NFVO => NFVO (RAN NS)
         1. NFVO (RAN) sets up network connection points (FH Links, Internal RAN and Control networks) and works with VNFM(s) to Instantiate VNFs and CNFs
      3. NFVO => NFVO (UP NS)
         1. NFVO (UP) sets up network connection points (Internal RAN, Control and Data networks) and works with VNFM(s) to Instantiate VNFs and CNFs
   3. NSSMF configures SFO Edge VNF/CNF/PNFs(SFO,  SFO URLLC data)
   4. NSSMF registers SFO Edge NSSI (Capacity Available, Capacity Allocated ) in A&AI
10. NSSMF registers SFO URLLC NSSI (Capacity Available, Capacity Allocated ) with A&AI
11. NSMF registers SFO URLLC Slice
12. CSMF completes