Telco Cloud How operators are using the Cloud to unlock the core network and drive innovation, Adam Kalsey, Tropo
Download as PPTX, PDF5 likes3,280 views
The document discusses how telecommunications operators are using cloud computing to modernize their core networks and drive innovation. It mentions how operators are moving components of their networks to the cloud to reduce costs and gain more flexibility. This allows them to offer new services and applications to customers more quickly.
Telco Cloud How operators are using the Cloud to unlock the core network and drive innovation, Adam Kalsey, Tropo
- 1. Telco Cloud How operators are using the Cloud to unlock the core network and drive innovation
- 2. Adam Kalsey akalsey@tropo.com @akalsey www.Tropo.com @tropo
- 3. @akalsey
- 4. @akalsey
- 5. @akalsey
- 6. @akalsey
- 7. @akalsey
- 8. @akalsey
- 9. @akalsey
- 10. @akalsey
- 11. @akalsey
- 12. @akalsey
- 13. @akalsey
- 14. @akalsey
- 15. @akalsey
- 16. @akalsey
- 17. @akalsey
- 18. @akalsey
- 19. “Software is Eating the @akalsey World”
- 20. What about IMS? @akalsey
- 21. @akalsey
- 22. @akalsey
- 23. Javascript Python Ruby PHP REST HTTP Java JSON
- 25. Picture: sandbox https://www.flickr.com/photos/lcwilder/ @akalsey Safety http://www.flickr.com/photos/elsie/3267191956/
- 27. @akalsey
- 28. @akalsey
- 29. @akalsey
- 30. @akalsey
- 31. @akalsey
- 32. @akalsey
- 33. @akalsey
- 34. @akalsey
- 35. @akalsey
- 36. @akalsey
- 37. @akalsey
- 38. @akalsey
- 39. @akalsey
- 40. @akalsey
- 41. @akalsey
- 42. @akalsey
- 43. @akalsey
- 44. @akalsey
- 45. @akalsey
- 46. @akalsey
- 47. @akalsey
- 48. @akalsey
- 49. @akalsey
- 50. @akalsey
- 51. Adam Kalsey akalsey@tropo.com @akalsey www.Tropo.com @tropo
Editor's Notes
- #4: Tradisional telco Specialized HW/ SW Long build times Safety & security reviews Deep domain expertise
- #5: Calendar
- #6: Development
- #7: QA
- #8: security
- #9: Deployment & rollout
- #10: Architecture
- #11: Planning
- #12: Hardware procurement
- #13: Business case
- #22: Low level APIs are still for experts. And you can really screw things up
- #24: Beyond just simplifying the API, simplify the language Lose the domain-specific knowledge in both the platform, and the programming
- #25: Different breed of developer
- #26: Well defined API Pre-approved access
- #27: Quality of service Developers only need worry about their app Carriers control QOS
- #28: An example using Tropo
- #29: Developer code runs on PaaS, separated from core network
- #30: What happens to app cycles with these changes?
- #31: Reduce time for dev
- #32: QA / testing drops accordingly
- #33: Known risks, so security review shortens or goes away
- #34: Deployment shorter, controlled by app devs, maybe pushbutton
- #35: Architecture is reduced all about app, not how it connects to the network, or resources it consumes
- #36: Overall dev cycle shortened, less planning needed
- #37: Cloud resources mean instant procurement / provisioning of HW
- #38: Business case can be less robust, as project cost is less. Why spend a month predicting if an idea is viable when you can just test it?
- #39: Lean startup approach. If you can test an idea cheaply, why not test smaller iterations, and find out earlier?
- #40: What does THAT do to your timelines and resources?
- #41: Internal Product teams first ideas for value-add services
- #42: mobile call recording
- #43: compliance monitoring
- #44: parental control
- #45: Call management: who can call me and when?
- #46: pent up demand for new products and services
- #47: Once the platforms are proven and the provisioning and billing processes are understood, operators next open the platforms up to trusted third parties
- #48: enterprises
- #49: systems integrators who build custom comms products for enterprises
- #50: Existing product companies who can sign contracts, etc
- #51: Final phase: open the platform for open registration by any developer