1 / 29

All-IP Evolution Paths Towards an All-IP network

All-IP Evolution Paths Towards an All-IP network. Ericsson. Presentation plan. 1- Evolution paths, starting from current standards step 0: Current situation with PS (TSB-115, 3GPP2 PS0001) step 1: Introduction of IP technology in Radio and CS network; PS domain independence

lemuel
Download Presentation

All-IP Evolution Paths Towards an All-IP network

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. All-IP Evolution Paths Towards an All-IP network Ericsson Ericsson

  2. Presentation plan • 1- Evolution paths, starting from current standards • step 0: Current situation with PS (TSB-115, 3GPP2 PS0001) • step 1: Introduction of IP technology in Radio and CS network; PS domain independence • step 2: The emerging all-IP solution • step 3: The all-IP target model • 2- Access Control Server • 3- Relation to other technologies & standards • 4- Conclusion Ericsson

  3. 1- Evolution paths Ericsson

  4. Evolution paths • Recognizing that already existing service providers : • inherit networks various in diverse conditions • operate networks under diverse traffic & commercial conditions • Recognizing that some service providers : • do not need/want to use legacy networks • We propose Voice and Packet migration paths • that can evolve at various speeds, function of the service providers needs Ericsson

  5. Evolution path, step 0Current situation for PS Ericsson

  6. Evolution path, step 1aTransition to IP transport in Radio network Ericsson

  7. Evolution path, step 1bTransition to IP transport in CS network Ericsson

  8. Evolution path, step 1cEmerging of PS domain independence Ericsson

  9. Evolution path, step 2The emerging all-IP solution Ericsson

  10. Evolution path, step 2Intermediate Reference Model Ericsson

  11. Evolution path, step 3The All-IP target Model Ericsson

  12. 2- Access Control Server Ericsson

  13. Access Control Server • MSC integrates all CS and PS control functionalities • Basic functionalities: • make the PS domain independent of the MSC. • an IP entity, which comprise the functionality to set up and maintaining packet data sessions (e.g. packet data registration, connection handling) • connect to the evolved HLR via the PLMN IP network. (e.g., PLMN IP Network: general: any suitable IP network. Specifics: could be an inter/intra PLMN IP network). Ericsson

  14. Access Control Server, step 0today Ericsson

  15. Access Control Server, step 1cPacket control functions extracted from the MSC Ericsson

  16. Access Control Server, step 2Increased ACS functionalities Ericsson

  17. Access Control Server, step 3ACS: cut MSC umbilical cord Ericsson

  18. Access Control Server, step 1cPacket control fnct. extracted from the MSC, signaling considerations Ericsson

  19. Access Control Server, step 1cPacket ctrl. fnct. extracted from the MSC, packet session set up Ericsson

  20. 3- Relation to other technologies & standards Ericsson

  21. Relation to other technologies & standards Ericsson

  22. 4- Conclusion Ericsson

  23. Conclusionstep-through-at-your-pace migration path • We proposed a migration path from today’s cdma2000 architecture to an advanced all-IP solution. • This path allows migration of circuit switched domain and packet switched domain to progress at different speeds. • Service providers can select the most appropriate speed, function of their business plans and local traffic contingencies. Ericsson

  24. Conclusionstep-through-at-your-pace migration path Ericsson

  25. Conclusionimportance of supporting legacy in an evolutionary way • We also emphasized the importance of supporting legacy services during the migration. • The goal is that the steps themselves are evolutionary and a carrier can decide to stop the evolution of its network at any step. Ericsson

  26. ConclusionAccess Control Server: helps migration • We propose a new logical entity: the Access Control Server. • ACS: • acts in the PS domain • will simplify the migration towards All-IP, by decoupling control functionalities from the MSC (legacy, 2G) Ericsson

  27. Conclusionreuse can be good • We should try to identify as much commonalties as possible in regards of: • protocol reuse, • IETF, • 3GPP Ericsson

  28. Conclusionreuse can be good Ericsson

  29. Conclusion • step-through-at-your-pace migration path • importance of supporting legacy in an evolutionary way • Access Control Server: helps migration • reuse can be good Ericsson

More Related