Versions Compared

Key

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

...

Name (Original Name)User Email
Takayuki Nakamura(NTT-Group)
Lingli[email protected]
Xi Cao[email protected]
Ton Brand (ETSI)
Ishan Vaishnavi
Raymond Forbes rwx651084
James O Sullivan ~ Huawei (James O Sullivan j00396566)
klaus Martiny (DTAG)
Zoulan(Huawei) (Zoulan z00340018)
Dave Milham[email protected]
Alan Pope[email protected]
Yuval Stein (TEOCO)
Luigi Licciardi lwx426782
Thomas Tovinger (Ericsson) (Thomas Tovinger)
Xiahaitao x00398509
Diego
Li Hui (Huawei) (Li Hui l00246889)
Weihong Zhu (ZTE)
Johanne Mayer[email protected]
Dong Sun (Futurewei) (Dong Sun)[email protected]
Min He(Futurewei) (Min He)maxgogame@outlook

mhe@futurewei.com

Anatoly (Nokia)
Jean-Michel Cornily# Orange
Bruno Chatras
Cecilia Ortega Lagos[email protected]
Kevin McDonnell (Huawei) (Kevin McDonnell)

...

Meeting Agenda

  • Permission to record
  • Introduction 10 mins
    1. Recap on prior workshops #2 and #3
    2. Work organization See WP01 at Work Packages ( WP)
  • Work package sync up / kick-off
    1. Kick-off WP03 Business Vision & requirements: 25min
    2. Kick-off WP02 Roadmap and Landscape 25 mins
    3. open discussion on WP02 and WP03 50 mins
  • Schedule of discussion and call for Proposals and participant outreach 10 mins
  • Next steps

...

  • Permission to record Requested and granted
  • Introduction 10 mins
    • Recap on prior workshops #2 and #3
      • Initial workshop# 1 focused on sharing experiences and state of the programs in different organizations
      • Workshop #2 started to advance the definitions Identified in the Workshop #1 but there were concerns about the formal/administrative arrangements.
      • Workshop #3 was SDO representation  only  ( not notified on  the email exploder list) that reviewed a proposal WP01 to separate Multi SDO initiative discussions into two threads: one on formal administrative matters and the other open discussion workshop. It also proposed a schedule of meeting now recorded in page 
        Multi-SDO AN Meeting Schedules  
      • Future agenda topics can be put in the meeting list schedules listed above.
    • Work organization See WP01r1 at Work Packages ( WP)
    • Key elements of the updated proposal are:
      • Formal administration meeting notified to SDO using he  Formal SDO Liaison Contacts List and emailed invitation to formal contact points.
      • Open discussion meeting notified using Outlook invite using email list [email protected]  whose participants are listed at   List of Open Workshop Participants
      • Agenda topics are different and expect outputs are different.
      • Interval between formal meetings is longer than open meetings.
      • Much of the open meeting work can be conducted online on confluence and through email communications.
      • Where the open meeting identity activities that need formal liaison agreement these will be notified to the formal thread  for discussion 
      • Note that Open Discussion group are primarily to exchange and share information and there is no IPR cover.
  • Work package sync up / kick-off
    • Kick-off WP03 Business Vision & requirements: 25min
      • Dong Sun provided an overview of the work package WP03 
        • Primary goal is to cover open discussion of both AN business vision including use cases and sharing of information of information in order to develop a common view of AN from business perspective by interested SDOs and/or companies , the initial deliverable could be a joint whitepaper. 
        • this will lead to forging a common base and identifying more  specific technical / detailed topics.
        • (Note WP02 below provides a specific example of what is intended)
        • Belief is that by exchanging information participants  will naturally avoid overlapping other groups activities which will assist CSPs
    • Kick-off WP02 Roadmap and Landscape 25 mins
      • Lingli Denggave an overview of the challenge that Service Providers such as China Mobile are facing in adopting AN, and why a roadmap of current and planned activities with associated landscape diagrams will help the industry understand what needs to be done , which group need to coordinate with which other groups; and help CSP communicate the management challenges that they need to solve with vendors in order to successful adopt, deploy and operate Autonomous Networks. 
      • Key points arising from review of WP02 AN Roadmaps and Landscape
      • CSP requirements

        Background

        • Target architecture  for AN involves many management fields and complex technology spanning business, service, resource and infrastructure.
        • Requires the addition of a (network) AI management plane in addition to current operational Management Stack (Ed Note: FCAPS). The AI Management Plane relies on a systematic design for how Network data is collected, managed and distributed across and in multiple domains.
        • AN standardization is far more complicated than previous standards and is beyond scope of any single SDO (Ed Note: domain skills, scale and pace of work required).

        CSP perspectives on transformation

        The WP02 proposed Roadmap and Landscape is part of setting CSP goals for long term evolution of automation.

        • For most CSPs they are starting as journey towards to AN automation, and they are a long way from achieving their ultimate goal.
        • CSPs need a climbing ladder that provides a step by step strategy and roadmaps for practical autonomous levels and their benefits.  Specifically needs defining measures for Autonomous levels that allow CSP assess where they are and provide guidelines for them to climb up until where they wish to achieve step by step.
        • Various SDO working on different perspectives of AN and there are notable redundancies and potential inconsistencies due to lack of coordination or exchange of information between different working groups. And sometime there are divergences between working groups within single organizations.
        • Need Shared vision what people / SDO are doing, where they are heading to, and how they could be leveraged collectively in terms of AN evolution.

        CSP User Challenges

        Goal is to establish a platform and a channel for Multi SDO information sharing i.e. who is doing what, and who needs to coordinate with whom on AN topic.

        • Need industrial collaboration to create synergy between SDO work and support CSP procurement.
          A shared overall landscape of SDO activities assists CSP build collaborations with suppliers, and adopt functionality, interoperable reference points and specifications from various SDOs.

        CSP Requirements – User Stories

        Some key CSP use stories  are emerging from China Mobile studies.

...