You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

June 28, 2017

Chengli Wang and Lingli Deng from China Mobile presented VoLTE use case. They went through the work flow for service design, instantiation, auto healing/auto scaling and termination. 31 Participants joined the meeting and discussion. The meeting recording can be accessed here: https://zoom.us/recording/play/zClGuWa2cFq-g3YEWC-sZ74V9iJaHAx2Iw7ePKuhh1q1ttjSSFXRyoJhYxpmk8bC

Meeting minutes:

At high level, there are edge and core data centers in the use case. EPC components split between edge and core data centers. Similarly IMS components also split between edge and core. A WAN network with underlay and overlay connects the two data center. 

At design time SDC design network service and closed loop policy. The output will be distributed to SO, VFC, SDNC and Policy.

At runtime, we will simulate alarm and verify the closed loop with auto healing/auto scaling feature.

Specifically, each related module and its function in the use case is described below:

VF-C: collect data from EMS and report the data to DCAE

Model: provide e2e VoLTE template for IMS, EPS and WAN

SDC: design e2e template for VoLTE use case

SO: Parse service template, and VFC and SDNC orchestrate service

SDNC: Orchestrate WAN connectivity service

DCAE: Receive resource layer and service layer telemetry data, do data analysis, and publish event through event bus

VFC: Provide northbound interface for network service layer life cycle management, and southbound interface to EMS and S-VNFM for service configuration and service provision

A&AI: Create/Update/Delete service related records

Policy: Design and support closed loop related rules for VoLTE. Policy will interact with VFC for auto healing and auto scaling operations

Multi-VIM: Create and delete virtual network between VNFs.

Holmes: Alarm correlation for service and resource layer, and publish event to event bus

Clamp: Design closed loop related policy


The 2nd half of the meeting discussion covered the following topics:

EPA support is too early to decide because it’s VNF and hardware dependent, and no specific requirement is given right now. Further discussion will be held for the more requirement and lab availability.

Telemetry data from VoLTE VNF is in JSON format, but not in VES format.  DCAE team will provide example and guidance on how to integrate with VES in Java and C. A separate call will be setup later. DCAE will also support SNMP polling.

More details need to be added for work flow 1.0 in SDC, like policy input from Clamp.

SDNC provisions connection between 2 data center - Provision hardware router, and set up L3VPN as underlay and VXLAN as overlay. Right now there is no SDN Agent to do the job. SDNC team will discuss the use case requirements internally and get back to integration team.

Need to talk to OOM and MSB teams to see if we need those modules in the use case.

  • No labels