Page History

...

1. CSMF(eMBB Nationwide) => NSMF (eMBB Nationwide Service Profile)
2. NSMF => NSSMF (eMBB Nationwide Slice Profile)
3. NSSMF Matches eMBB Slice Profile 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)
4. 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)
5. NSSMF Instantiate Network Services:Slice Subnet Instances:
   1. NSSMF => NSSMF (C)
      1. NSSMF (C, Central) 
   2. NSSMF
      1. => SO (Central Network Slice Service (C Parameters)
      2. SO => NFVO (Central Network Slice Network Service)
         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. NSSMF configures Central VNFs(C eMBB data)
      5. NSSMF(C) registers C NSSI (Capacity Available, Capacity Allocated )
   3. NSSMF => NSSMF(NE, UP)
      1. NSSMF(NE, UP) => SO( UP Network Slice Service (NE Parameters))
   4. NSSMF => NSMF(NE, RAN)
      1. NSSMF(NE, RAN)  => SO (RAN Network Slice Service (NE Parameters)
   5. ...
6. Resulting Network Service Deployment:
   1.  

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

7. NSSMF 

Resulting Instance info:

NOTEs:

1) CST chain of objects and NST chain do not have any relation at DT. 

...