Versions Compared

Key

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

...

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

...

  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

...

  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 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)
        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.  
      Gliffy Diagram
      macroId64de5485-b7ac-406d-be81-f9c87eb4c00b
      nameSliceSubnet-NS Deployment
      pagePin1
  8. NSSMF registers Nationwide NSSI (Capacity Available, Capacity Allocated ) with A&AI
  9. NSMF registers Nationwide eMBB Slice
  10. CSMF completes

...