What Operators need from NGN Standardisation

1. What Operators need from NGN Standardisation Stewart Alexander ITU Standards Manager, BT Group WTSA

2. Summary • Business drivers for NGN • Requirements for NGN • Technical view of NGN • What standards do we need for NGN? • What do we want from ITU?

3. What’s the Current situation? • Telecom winter exaggerating the cost of multiple standards – e.g. multiple networks in mobile • All telcos under pressure to reduce expenditure on standards • Cost of interworking is killing us • More and more uses are global (mobile, WLAN, Internet etc) with more and more users travelling. • Standards must be global • Growing complexity from multiple fora as groups become frustrated with speed of traditional standards bodies • Need for a radical drive to the NGN – speed is essential.

4. Why do we need an NGN? • Make it easier to create new services • Faster • More people can create services • Make it easier to buy and use services • Give customers greater choice • Make it simpler to deliver and maintain services • Process automation • 30-40% cost reduction

5. What does it mean? • New services • Open APIs and applications platforms • Mobile enabled • Re-usable components/capabilities • Build on broadband capability • Cost reduction • Not enough to do efficiencies and automation • Radical network convergence to fewer networks and systems carrying more services

6. Cost Reduction • Efficiencies and automation not enough • need to enable customers and partners in the service management processes • Radical steps required • need closure of legacy networks and systems • Have to include future of PSTN (voice) • More important to converge in access and backhaul than in core • because opex and capex centred there

7. 21st Century Services Vision “A world where all our customers feel empowered and are treated as individuals”

8. Cost C B Today’s Networks • Built on “service=technology” stove pipes. • Every network service has its own network platform: • FR, ATM, MPLS IP VPN, Internet, PSTN etc. • We want a converged multi-service platform to deliver all services. Internet Frame Relay ATM SDH

9. ~1000 + Voice Switches and Data Cross Connects ~80,000 PCPs in the Access Network ~170 Core Switches (DMSU / NGS) ~100,000 Remote Concs, DLAMS and Data Muxes Logical Nodes Data Centre Today International Networks Internet Peering End Customer ~30,000 Multi- Service Access Devices ~100 Metro Routers ~10 Core Routers Data Centre Begin Fibre to the PCP Logical Nodes Aggregation Service Edge Core 21st Century Network Vision

10. Provide a common Intelligence Layer Intelligence layer Application layer – Web Services .Net J2EE Intelligence Layer Intelligence Layer Control Accounting Monitor Authentication Presence Authorisation Common Data Model – LDAP interface Flexible user interface Web, DTMF,Voice Interface Protocols – INAP, MGCP, SNMP, CORBA, GMPLS, etc Mediation and Billing Transmission Layer PSTN and Data Internet 3rd party new generation networks backbone networks PSTN Intelligent Service Layer – controlling IP and PSTN - and allowing controlled 3rd party access

11. Overall Architecture ExternalInterfaces Enterprise Management Commercial & Customer Management Partners & OLOs Selling, Customer & Channel Management Supplier Management Billing Proposition Creation & Handling ICT Contract Handling Trading Gateways Front Office functions Portfolio Management Customers and users Outsourcing Management Business Intelligence Portal Functions Service Management Service Execution Authentication & Authorisation Service Assurance Application Content BT People Profile Directory Knowledge Management & Collaboration Network location Service Fulfillment Application exposure Session control Network Resource Model Finance Presence Mediation & Pricing 3rd party APs Messaging Business Support Service Management agents Connectivity resources Media Resources Personal Comms Devices Resource Management on-demand Computing (application hosting) Network Management Network Engineering Enterprise & Premises Access, Aggregate & Backhaul Metro Core Optics & MPLS Workforce Management & Professional Services Technology Management 21C Network Integration & application development framework

12. Highest Priority NGN Standards Requirements • Multi-service carrier-scale core • enabled by underlying ‘MPLSv2’ network • 3GPP Architecture • extended to Wi-Fi and fixed Broadband access • Session based QoS • Session Control • extensions to SIP with full multimedia capability • Billing and charging (data interchange billing) between operators • Manageability • commoditised componentised OSS • Security • authentication across networks / operators • Home Gateways/Networks

13. What do we need to do generally..? • Prioritise. • Position fora, regional bodies and ITU into a consistent approach to lead to global standards – an architecture of standards bodies. • Support the NGN architecture – will require us to merge over traditional boundaries. • Give equal weight to systems and networks

14. ITU is important to NGN for: • Access Networks – SG15 • Core Networks – SG13 • Optical Networking – SG15 • Spectrum – ITU-R • Numbering & Addressing – SG2 • Signalling for QoS across multiple networks – SG11 • Services and applications – SG16 • Security – SG17 • NGN Focus Group – to get it started and bring it all together

15. Other Important Bodies for NGN • 3GPP/TISPAN – IMS • ATIS – US carrier requirements • DSL Forum – remote management of CPE • IETF – IPv6, SIP extensions, MPLS, etc • TMF – standardised OSS components • Open Mobile Alliance (OMA) – (Mobile) Applications, DRM • Metro Ethernet Forum (MEF) – role of Ethernet in transport network • IEEE 802.11x – Wi-Fi hotspots

16. What do we want from ITU? • Global Standards, speedily and efficiently produced How do we get this? • A single ITU-T Study Group for core NGN studies • A managed release program • A co-ordinated ITU-T approach

17. Conclusions • NGN will only succeed if based on globally standardised components • ITU must work with ETSI, ATIS and other fora to achieve standards for NGN • ITU can provide strategic focus for NGN standards – but must create SG with sufficient critical mass to address NGN issues