Hi Eric,
I did not see your reply until today and I would like to confirm whether you have suggestions and inputs for VoLTE Use Case. Any opinions and inputs would be appreciated. Looking forward to your reply. Thanks Yan 发件人: 杨艳 [mailto:[email protected]] 发送时间: 2017年5月25日 10:56 收件人: '[email protected]'; '[email protected]' 抄送: 'Lingli Deng'; 'Chengli Wang' 主题: 答复: [onap-discuss] [ONAP] Use Case: VoLTE (vIMS + vEPC) Hi Eric, Thanks for your questions and I will do some clarification. 1. The open source VNF you mentioned is open source VNF, or vendor VNF? who is responsible for maintaining in the integration test and if needs other VNFs in end-to-end testing? 2. The parser component in Instantiation figure is TOSCA parser which is included in the Modeling project. 3. User sends a request to Portal firstly and not to DCAE.it is just a mistake and we will correct it later. 4. Welcome to provide relevant workflow charts based app-c.For example,instantiation,termination and control loop. 5. Whether the minimum set of EPC scenes contains only two or three VNFs, and if so, it is no longer an end-to-end VoLTE Use Case, and whether need other VNFs.In this case how to do end-to-end business verification, or as a separate VNF to verify? Is there a closed loop control? Thanks, Yan 发件人: [email protected] [mailto:[email protected]] 代表 [email protected] 发送时间: 2017年5月24日 15:11 收件人: [email protected] 主题: [onap-discuss] [ONAP] Use Case: VoLTE (vIMS + vEPC) Hello I would like to clarify some points on the use-case on the mailing-list before clarification on the wiki. For VNF, I believe that we should add a column for open-source based solution. There is a parser component in the Instantiation figure. What is it ? I understand as a TOSCA parser, but it is not described. On the termination call flow, I do not understand why the user sends a request to the DCAE…Why not using the SO directly ? The various call flows are based on VF-C, but why not using APP-C ? The use-case should include minimal vEPC use-case as proposed in MiddleTown (with PGW, MME and HSS). Regards Eric ____________________________________________________________________________ _____________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
