User Tools

Site Tools


ip_multimedia_subsystem

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
ip_multimedia_subsystem [2014/11/14 12:15]
Martin Taylor [Subsequent Phases of vIMS Testing]
ip_multimedia_subsystem [2014/11/14 12:22]
Martin Taylor [Subsequent Phases of vIMS Testing]
Line 57: Line 57:
 The vIMS test case can be progressively expanded by adding more and more of the distinct functions defined by the IMS architecture. ​ A logical next step beyond vSBC testing would be to add a virtualized IMS core.  The VNF implementation proposed for this purpose is Clearwater Core, an open source implementation of the IMS core functions from Metaswitch Networks. ​ See [[http://​www.projectclearwater.org/​]]. The vIMS test case can be progressively expanded by adding more and more of the distinct functions defined by the IMS architecture. ​ A logical next step beyond vSBC testing would be to add a virtualized IMS core.  The VNF implementation proposed for this purpose is Clearwater Core, an open source implementation of the IMS core functions from Metaswitch Networks. ​ See [[http://​www.projectclearwater.org/​]].
  
-Clearwater is implemented with a scale-out architecture using stateless SIP processing elements allied with a distributed,​ scalable, fault-tolerant state store based on well-known open source elements. ​ With Perimeta SBC providing a virtualized P-CSCF and Clearwater Core providing virtualized S-CSCF, I-CSCF, BGCF and (optionally) AS, all the key call processing functions of a vIMS could be tested. ​ The same SIP traffic generation capabilities used to test vSBC would also be needed to test this more complete implementation of vIMS. +Clearwater is implemented with a scale-out architecture using stateless SIP processing elements allied with a distributed,​ scalable, fault-tolerant state store based on well-known open source elements. ​ With Perimeta SBC providing a virtualized P-CSCF and Clearwater Core providing virtualized S-CSCF, I-CSCF, BGCF and (optionally) AS, all the key call processing functions of a vIMS could be tested. ​ The same SIP traffic generation capabilities used to test vSBC would also be needed to test this more complete implementation of vIMS. With this test setup, the performance of OPNFV could be characterized in the context of vIMS in both control plane and user plane.
- +
-With this test setup, ​not only could the performance of OPNFV be characterized in the context of vIMS in both control plane and user plane, but some other aspects of OPNFV functionality such as support for dynamic scale-out could be explored. ​ Given that the current scope of OPNFV does not include the NFV Orchestrator function, it would not be possible to test automatic scale-out, but scale-out (and scale-in) functionality could be verified by means of manual operations invoked on the Virtual Infrastructure Manager (e.g. via the Horizon console of OpenStack).+
  
 An even more complete test of vIMS on OPNFV could be accomplished by adding further functional elements such as vHSS, vPCRF etc.  Also, the vIMS could be layered on top of vEPC to enable the testing of a complete virtualized VoLTE solution. An even more complete test of vIMS on OPNFV could be accomplished by adding further functional elements such as vHSS, vPCRF etc.  Also, the vIMS could be layered on top of vEPC to enable the testing of a complete virtualized VoLTE solution.
  
ip_multimedia_subsystem.txt · Last modified: 2014/11/14 12:22 by Martin Taylor