...

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.

Design Time:

...

1. Onboard 5G Core NFs (NRF, PCF, UDM, AUSF, NEF, AMF, SMF, UPF, ...) into SDC
2. Onboard RAN NFs (vCU, vDU) into SDC
3. In SDC, design a "Central" Network Service composed of
   1. "Central" 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 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 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

...

New mIOT Slice

...