1. SBC in NGN Architectures Jonathan Cumming

2. Copyright © 2006 Data Connection Limited All Rights Reserved.2 SBC in NGN Architectures NGN Standardisation 3GPP, ETSI, ITU, MSF Evolution of SBC in IMS architecture Deployment options Remaining areas for standardisation

3. Copyright © 2006 Data Connection Limited All Rights Reserved.3 NGN Standardisation Process Many organisations defining Next Generation Network Standards Bodies Industry Forums Implementation Agreements Trials and Interop Events Requirements Standards

4. Copyright © 2006 Data Connection Limited All Rights Reserved.4 3GPP – Third Generation Partnership Program Standardization body for GSM mobile Incorporated IMS in Release 5 Focused on 3G mobile phones Centrally managed Bandwidth plentiful except in radio access network P-CSCF provides some SBC features on UNI Access control Enforces routing Release 7 (in development) adds more SBC features Support for fixed-line and legacy equipment Non-IMS endpoints, e.g. PBX, Legacy Protocols IPv4 Topology hiding, NAT and Access control on NNI

5. Copyright © 2006 Data Connection Limited All Rights Reserved.5 ETSI TISPAN Charged with developing new architecture for fixed telephony networks Adopted IMS as underlying architecture Extending/adapting IMS for requirements of fixed networks TISPAN R1 requirements part of 3GPP Release 7 Planned releases R1 (2005) – Focused on DSL access R2 (2007) – Improved control of access resource usage R3 (2009) – Adds support for roaming (nomadicity)

6. Copyright © 2006 Data Connection Limited All Rights Reserved.6 ITU-T Overarching architecture for NGN Coordinated by SG-13 Working closely with ETSI, 3GPP and IETF Also concerned about “Internet” use End-to-end QoS without central control, i.e. no SBC

7. Copyright © 2006 Data Connection Limited All Rights Reserved.7 MSF Promotes deployment of open and interoperable equipment Develops interoperability agreements reusing existing standards where possible Organizes interoperability events MSF Architecture is based on fixed-line carrier requirements Bandwidth management within the core Migration of legacy services NAT Release 2 Architecture contains Session Border Gateway Security NAT Access Control Release 3 (in progress) migrates to IMS-based core

8. Copyright © 2006 Data Connection Limited All Rights Reserved.8 Evolution of SBC function SIP 3GPP R5/6 3GPP R7 MSF R2 MSF R3 P-CSCF provides Security Access Control Routing Control IBCF adds Protocol Conversion Legacy Devices Peering Control IPv4 / NAT IMS still lacks Core Bandwidth Management Explicit MPLS/VPN support Internet No borders SBG provides Security Access Control NAT Migration to IMS core

9. Copyright © 2006 Data Connection Limited All Rights Reserved.9 Proxy Evolution of SBC in IMS Architecture AS UE SBG-NE IBCF TrGW SBG-NC IETF SIPIMS R7 Proxy GGSN PDF GGSN IMS R5/6 P-CSCF S-CSCF P-CSCF

10. Copyright © 2006 Data Connection Limited All Rights Reserved.10 Each architecture gives SBCs different names Network Edge Network Core Access (CPE) S-SBG-CEA-MCFOut of scope D-SBG-CEA-MGF“ S-SBG-NEC-BCFP-CSCF D-SBG-NEC-BGFGGSN / BAS / PDG S-SBG-NCI-BCFIBCF D-SBG-NCI-BGFTrGW MSF R2TISPAN R1IMS

11. Copyright © 2006 Data Connection Limited All Rights Reserved.11 Deployment options Some SBC function covered by IMS architecture Real SBCs may incorporate additional function CAC (off-loading work from S-CSCF) Transcoding Gateway function – e.g. Protocol interworking Firewall and NAT traversal (where not handled by CPE) SBC function may be built into other devices Routers providing media SBC function Softswitches incorporating all CSCF and SBC signaling functions

12. Copyright © 2006 Data Connection Limited All Rights Reserved.12 Areas for further standardisation IMS assumes plentiful core network resources SBC function needs interfaces to central Bandwidth Manager S-CSCF P-CSCF UE IBCF TrGWGGSN SBG-NE SBG-NC BM

13. Copyright © 2006 Data Connection Limited All Rights Reserved.13 Areas for further standardisation IBCF BM TrGW Policy configuration Complex and only partially standardised

14. Copyright © 2006 Data Connection Limited All Rights Reserved.14 Summary Border Control is a requirement for carrier service An SBC is a device that provides the set of functions needed at the border These functions are now appearing in IMS and other standard architectures This work is ongoing Competing pressures for features An SBC is not always a separate device Parts of the function can be implemented by other devices: edge routers, access network or softswitch

15. Copyright © 2006 Data Connection Limited All Rights Reserved.15 Data Connection (DCL) Software technology since 1981 Portable network protocols VoIP: SIP, MGCP, Megaco, SBC MPLS, VPNs, IP Routing, ATM Messaging / Directory / Conferencing MetaSwitch Private and consistently profitable Effectively owned by employees People ~20 recruits from ~3000 applications Attrition rate <3% Number of Employees Revenue and Earnings

16. Thank you for listening Jonathan Cumming jonathan.cumming@dataconnection.com