Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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.

Gliffy
size300
displayName3GPP NST-NSST-NSD
name3GPP NST-NSST-NSD
pagePin4

Design Time:

Gliffy
macroId456c09dd-3291-460c-8224-5d153a608d89
nameCentral 5G Service and Network Service Descriptors
pagePin8
  
Gliffy
nameUP Service and Network Service Descriptors
pagePin3
Gliffy
macroIdd2d7af96-01a3-4d55-950c-3d86c4206e1e
nameRAN Service and Network Service Descriptor
pagePin5

...

  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

Gliffy
size600
nameNSMF-NSSMF-NFVO-VNFM
pagePin3

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
macroId3cbd8d35-99ae-4a26-8db3-d224e12e2821
nameeMBB Network Slice Instance
pagePin810

New Slice Request (NE Enterprise):

...

Gliffy
macroIdee395fbb-c168-4e11-9dd6-ea24470a10b2
nameeMBB and NE Enterprise Network Slice
pagePin45

New mIOT Slice

Gliffy
macroId22885eaa-5a4d-40b6-9d8a-cb56aa56aa81
nameeMBB-mIOT-NE Enterprise Slice Instances
pagePin2

...

  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

Gliffy
size6001200
nameAdded Edge NS
pagePin1

Gliffy
macroIdc3431ef3-a2f3-40c4-8f01-73df557c49d2
nameSFO URLLC Edge
pagePin12