Agenda:

  • Agenda review
  • Root Proposal
  • Allotted Resource / Network Slicing (updated presentation is here - slides 19-22)
  • VES model

Material:

Minutes:

  • Root Proposal:
    • revisit the proposal last week and on the resource/service IM calls
    • no concerns are raised
    • would like to call for consensus on Tuesday's call
  • Network Slice Model:
    • Q: what's the addtions for supporting network slice?
      • ServiceProfile/SliceProfile for design and instanceProfile for runtime model
      • filters to select shared (subnet) slices for design model
      • instanceSharingNumber for instance model
    • service can be considered as proxy of resource
    • configuration information (day 0,1,2, ...) would be stored in CDS
      • there will be different templates (portions of information) for day 0 and day 1/2
      • are these configuration only consumed by APP-C? not sure
    • RIC: realtime interface controller, handle realtime interaction with ONAP, related to ORAN
    • Is DU sharing means DUaaS can be configured? or DUaaS shared by different network slice? (regarding to email discussions)
      • intend to be the latter one
      • according to 3GPP, one DU can only be connected to one CU
        • CU could be virtualised (or partitioned)
        • DUaaS in the proposal (or say, ONAP view) may be different with the DU concept (PNF) in 3GPP
    • filter
      • for service selection (to find a shared (subnet) slice)
      • different from the service profile
      • not included in 3GPP/ETSI NS
      • examples can be found in the slides (see material, page 24)
      • alternative way: declare the needs, let the orchestration to select (not using filters)
    • no expected actions for resource model currently, will wait for concrete (not conceptial) design
  • VES:
    • impact from root proposal
    • plan to start updating the model from this week