Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 23 Next »





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 Network Slicing. 


The Guilin Service IM allows for a (nested) Network Service (NS) model that is referenced from an ONAP Service.

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:

  



Design Sequence:

  1. Onboard 5G Core NFs (NRF, PCF, UDM, AUSF, NEF, AMF, SMF, UPF) into SDC
  2. Onboard RAN NFs (vCU, vDU) insto 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 SBA interface
    3. Virtual Link (RAN Network) for the interface to the RAN components
    4. 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
  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 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) in A&AI
  7. 6 RAN/UP Sites and one Central Site available and registered in A&AI

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 decomposes  and 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 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 Network Slice Subnet Instances:
    1. NSSMF => NSSMF (C)
      1. NSSMF (C, Central)  => SO (Central Network Slice Service (C Parameters)
      2. SO => NFVO (Central Network Slice Network Service)
        1. NFVO works with VNFM(s) to Instantiate VNFs
      3. NSSMF configures Central VNFs(C eMBB data)
      4. 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.  
  8. NSSMF registers Nationwide NSSI (Capacity Available, Capacity Allocated ) with A&AI
  9. NSMF registers Nationwide eMBB Slice
  10. CSMF completes


Resulting Instance info:

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




  • No labels