1 / 11

3GPP2 Workshop MMD IMS Architecture

3GPP2 Workshop MMD IMS Architecture. June 28, 2005. Anne Y. Lee IMS Systems Engineering Lucent Technologies aylee@lucent.com (630)713-1257. Agenda:. Operator MMD/IMS – Deployment Challenges Proposal to Address Challenges Standards Implications. Operator MMD / IMS Deployment Challenges.

adonia
Télécharger la présentation

3GPP2 Workshop MMD IMS Architecture

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. 3GPP2 WorkshopMMD IMS Architecture June 28, 2005 Anne Y. Lee IMS Systems Engineering Lucent Technologies aylee@lucent.com (630)713-1257 Lucent Technologies – ProprietaryUse pursuant to company instruction

  2. Agenda: • Operator MMD/IMS – Deployment Challenges • Proposal to Address Challenges • Standards Implications Lucent Technologies – ProprietaryUse pursuant to company instruction

  3. Operator MMD / IMS Deployment Challenges • MMD/IMS standards definition has: • Many functional entities • Many interfaces • Some operators may find that for deployment of their MMD/IMS solution, they will need: • Aggregation of functional entities into small number of platforms : • Allow for easy mixing & matching of MMD/IMS “boxes” from multiple vendors • Minimizes operations costs • Regional allocation/assignment of IMS servers: • Optimizes performance for “roamers” • Reduces bearer & signalling paths Lucent Technologies – ProprietaryUse pursuant to company instruction

  4. Solution: Aggregation • Currently, no industry convention for aggregation • Currently, every vendor is developing a different combination of MMD/IMS functional entities on their platform(s). • Advantages of an industry convention for product aggregation of MMD/IMS functional entities • Reduces interoperability testing to manageable number or scenarios • Reduces operations costs by: • Minimizing number of platforms to maintain • Minimizing number of interfaces to monitor • Next slides show proposal for one view of aggregation Lucent Technologies – ProprietaryUse pursuant to company instruction

  5. Example Proposal for Aggregation: Functional Clusters • ACP (application control point): Includes session control and management, data management for service execution, interworking with other MMD, enterprise, and legacy networks. • (P-CSCF, S-CSCF, BGCF, SCIM+, SBC/I-CSCF, Enterprise Telephony Server) • BSCP (bearer services control point): Includes resource management and mobility mgmt functions, charging functions, filtering and security functions • (BCP+, Security, Filtering, Charging, S-MM) • Security center (SC) – Includes management of multi-layer authentication and encryption for user services • (KDC, security services) • All security keys in SC • Services Data Management Center (SDMC) – Includes routing, accounting. • (SDB, AA Server) Lucent Technologies – ProprietaryUse pursuant to company instruction

  6. Proposal for Aggregation of Std IMS Entities: Minimizes Platforms & Interfaces PSTN/ PLMN IP PSTN GW Regulatory server Media Svr Appl svr SIP Other MMD Services Data Mgmt Center (SDMC) Application Control Point (ACP) diameter Provisioning and Billing diameter Legacy Domains IP diameter diameter SIP IP diameter Security Center (SC) Bearer Services Control Point (BSCP) Provisioning Operator IP Ntwk IP diameter SIP RAN UE Lucent Technologies – ProprietaryUse pursuant to company instruction

  7. (2) Solution: Regional Allocation of IMS Servers • Develop industry guidelines for implementing procedures to support assignment of IMS session servers in region of subscriber access • Current deployment thinking assumes assignment of IMS session servers to those in a fixed geographic location per subscriber regardless of location of subscriber. • Regional assignment does NOT radically change IMS model; need to ensure that vendors implement the standards options that allow for regional allocation • Regional Allocation Benefits: • Reduces signalling path distance minimizing NATs/ALGs, routers, firewalls traversed. Minimizes potential signalling delay. • Reduces bearer path distances for applications with a real-time bearer component such as for conferencing: MRF. (not addressed in standards) • Can easily support access of local services (e.g. local applications referring to local businesses such as restaurants) • Intended to still allow access to subscribed-to applications regardless of location of subscriber Lucent Technologies – ProprietaryUse pursuant to company instruction

  8. ACP ACP BSCP BSCP RAN RAN Regional Site Regional Site App Server App Server SDMC SDMC SC SC Central Site Central Site ACP ACP ACP ACP ACP ACP BSCP BSCP BSCP BSCP BSCP BSCP RAN RAN RAN RAN RAN RAN Regional Site Regional Site Regional Site Regional Site Regional Site Regional Site Geographic Distribution of MMD/IMS Core Elements Lucent Technologies – ProprietaryUse pursuant to company instruction

  9. IMS Home Network AS AS AS AS AS AAA AAA HSS AS AS AS HSS AS S,I-CSCF S,I-CSCF P-CSCF P-CSCF PDSN PCRF PCRF PDSN RNC RNC IMS Network Topologies Proposed Intra-Operator MMD/IMS Topology 3GPP2 MMD/IMS Multi-Network View Centralized IMS Components Multi-operator scenario Single operator scenario IMS Home Network BTS BTS Access Network Access Network Lucent Technologies – ProprietaryUse pursuant to company instruction

  10. Standards Impacts & Approach • Multi-Vendor environment will require vendors developing • to common set of requirements • Aggregation Impacts • SC • 3GPP GAA / Liberty Alliance equivalent need standardization completion in 3GPP2 • ACP • New registration procedures or interface between SDMC and SC if move all security keys in SC • BSCP • New functionality and/or framework; may need standardization if more than re-packaging existing standardized capabilities. • Regional Allocation Impacts • SDMC • Adopt SLF from 3GPP or standardize full duplication of all subscriber data in all SDMCs. • ACP • Enhancements for procedures to support regional allocation Lucent Technologies – ProprietaryUse pursuant to company instruction

  11. Conclusion / Summary / Next Steps • Aggregation • Reduces interoperability testing to manageable number or scenarios • Reduces operations costs by: • Minimizing number of platforms to maintain • Minimizing number of interfaces to monitor • Regional Allocation • Reduces signalling path distance minimizing NATs/ALGs, routers, firewalls traversed. Minimizes potential signalling delay. • Reduces bearer path distances for applications with a bearer component such as for conferencing: MRF. (not addressed in standards) • Can easily support access of local services (e.g. local applications referring to local businesses such as restaurants) • Intended to still allow access to subscribed-to applications regardless of location of subscriber • Both deployment challenges can be solved independently • CDMA2000 industry should consider program to ensure multi-vendor interoperability of MMD/IMS “boxes”. Lucent Technologies – ProprietaryUse pursuant to company instruction

More Related