Attendees

• Tina Tsou (Deactivated)
• Oleg Berzin
• Suzy Gu
• cmti CA
• Tianji Jiang
• Wei Chen
• gao chen
• Frank Wang

Agenda

• Review comments on the proposed architecture
• Review reference points
• Review PCEI Enabler components
• Release 3 preparation

Minutes

• Discussion about adopting PCEI Architecture and Interface Reference Points as per the proposal captured in the PCEI Documentation → PCEI Files → PCEI-Arch-1-1 file (slide #2).
  
  • The goal is for the PCEI Enabler layer to facilitate all interworking / interfaces between the Mobile Network Operator (MNO) functions, Public Cloud Edge and Core Functions as well as the 3rd Party Edge Functions
  • Based on a comment from gao chen China Unicom, there was a discussion on the need for an Interface Reference Point (IRP) between the PCEI Enabler and the NFVI layer (P9 in the Architecture diagram) of the MNO Domain. After the discussion, the consensus was that this capability may be considered in general (e.g.  P9 between PCEI Enabler and the 3rd Party NFVI stack), but it was not clear that this capability will be exposed to PCEI by MNOs (based on comments from China Mobile). The decision was to keep P9 but only show in the architecture between PCEI Enabler and 3rg Party NFVI.
  • Comment by Suzy Gu China Mobile that the overall architecture has a broad scope. Oleg Berzin suggested that the argument in support of a more comprehensive architectural view is to reflect as much of the stack and interfaces as reasonably possible based on the need for specific capabilities to achieve the intended use cases (UPF distribution, local traffic break-out, network slicing, QoS, etc). Every use case has requirements for components in the archirecture including DC infrastructure, interconnecting and transport networks / capabilities, compute hardware / orchestration, NFVi and edge functions). The decision was to
    • Keep the broader architecture
    • Implement only specific functions / interfaces as required by the uses cases / control / data flows that are under implementation in a given release (i.e. not implement all at once)
    • Pick a starting flow. The consensus was that the Mobile to Public Cloud Edge will be the first flow to detail.
  • Oleg Berzin agreed to update the PCEI Architecture Document based on the discussed slides
• Release 3 preparation.
  • Tina Tsou (Deactivated) suggested that the team create a plan for R3 that planned for June 15, 2020.
  • cmti CA proposed to use the ETSI MEC API for the first release of PCEI. This involves creating a Docker image and the Installation documentation
  • Oleg Berzin suggested that the first PCEI release with the ETSI MEC API can be aligned with the PCEI Architecture to show continuity between the architecture and the software release