General Information:

  • Date and Time: 2020, Aug 31st, 9pm~10pm Beijing Time, 9am~10am US Eastern
  • Meeting Room: https://zoom.us/j/97595070639
  • Meeting Recording:  
  • Meeting Chat Log:  

Agenda:

  • Agenda bashing - 5 minutes
  • Model Proposals
    • ETSI alignment - 10 minutes
    • Geolocation - 20 minutes
    • allotted resource - 20 minutes？
    • 5G RAN service - 0 minutes
    • CNF - 0 minutes
    • PNF instance model - 0 minutes
    • CPS model driven PoC - 0 minutes？
  • Modeling Documentation - 0 minutes？

Material:

Minutes:

  • Agenda bashing
  • Model Proposals
    • ETSI alignment
      • Fred has updated the gendoc to resolve Thinh's comments 
      • for SDC, R7 will still use v2.5.1, R8 will use v2.7.1/3.3.1 (to be decided); SDC will support NS onboarding based on v2.5.1 (NS and VL node type)
        • TOSCA version to use for SDC: does SDC plan to use TOSCA 1.3? will discuss in R8.
      • no need for consensus on the DM part
      • the remote consensus for IM will end soon, please reply or comment if there are any
    • Geolocation/Place model
      • draft model available at: Proposed Location Model
      • Ben's summary:
        • the team has gone through the attributes from the complex object as well as existing specs
        • have agreed on some of the attributes to be included in the geolocation model and leave some out (reflected in the papyrus model)
        • lata and ctag-pools attributes are left for further discussion in modeling call
          • lata is US specific, but maybe no harm to add
      • Jacqueline's presentation:
        • Place class:
          • validFor attribute added by Kevin
          • geoCoordinates and civicAddress added by Jacqueline
          • most attributes are of string data type to ensure flexibility
        • comments:
          • altitude can be optional
          • placementCode → placementInfo
          • add lata under civicAddress
          • add FEET to AltitudeUnit
      • Jacqueline will update the wiki page and asking for poll tomorrow
    • allotted resource
      • postponed to next call
    • CPS model
      • postponed
    • 5G service model
      • Ben will present the Honolulu use case to the requirements subcommittee after this call (https://zoom.us/j/655429955)
  • Modeling Documentation
  • No labels