Design Time Model Behind Vo LTE Use Case

Design Time Model Behind Vo. LTE Use Case Approach for R 1 vnfm. Info controllerinfo IMS(VNF) Vo. LTE E 2 E(Service) HSS(VNF) ID(invariant. UUID) IMS(Service) WAN(VNF) SBC(VNF) . . (VL) Service template For Network Service EPC(VNF) Service template For E 2 E CSCF(VNF) ID(invariant. UUID) ? ? ? 1. SDC, SO, VFC project have reached consensus on service model for volte use case as the diagram here Service template For Network Service 2. IMS, EPC, Vo. LTE E 2 E template is clear now, but x. GW(VNF) people have no idea of WAN template ID(invariant. UUID) 3. It should be TOSCA template, named as WANMME(VNF) EPC(Service) descriptor PCRF(VNF) 4. Need detail of content of WAN Descriptor, so that SDC could design it. . (VL) 1 Service template For Network Service

Questions about WAN modeling for Volte SDC TOSCA packages Distribution import What kind of information should WAN Descriptor contain? L 3 vpn info? DG name of SDN-C? Something else? Which project, SO or SDNC, parse the TOSCA template? Do we have the seed code of this part? Who will be responsible on this part of code? CSAR(Volte e 2 e) SO Rest conf API? Content: DG name? L 3 VPN parameters? SDN-C? CSAR? Use DG design workflow include L 3 VPN model and keep align with 3 rd Party controller embedded model ? Rest Conf API Content: 3 rd party define and implement in adaptor 3 rd party Controller L 3 VPN Model Topology Parameters key : value