Services – a perspective on building applications Richard Swale ETSI TIPHON Wg1 chair VoIP Technologist BTexaCT ITU Workshop on IP Networking and Mediacom 2004 Joint Session 1 – Multimedia service evolution

Agenda Evolution of IP services beyond voice The heterogeneous network environment Some views on how services are developed Services and Service Capabilities Conclusions

Beyond Voice over IP IP –Emerged as the de facto network convergence layer of choice; its on the desktop. –Can support a wide range of applications including real-time but at present this is largely only “best effort” real-time –Provides an opportunity to look at public network services afresh. Voice over IP –A term which describes a wide range of technical solutions. –Available at varying levels of maturity. –Is not a service! BUT –IP is largely “media neutral” and can support video as well as voice applications. [QoS is an issue though!]

Evolution and Revolution New services are being targeted on IP –3GPP release 5+ –BUT mass market customers buy applications they don’t buy technology Existing services migrating to IP based platforms –IPCableCom Existing platforms are unlikely to be replaced overnight –Performance, reliability, availability, integrity, security, accounting are all issues in the IP space. –A heterogeneous public network infrastructure is likely to exist for some time to come. –Best efforts IP networks may be complemented by QoS capable IP networks which also provide best effort services.

Apps GW The heterogeneous network environment IP Network IP Network 2G 3G Fixed IP NW Possible point of interest for inter- working and inter- connect

Views on current service development The Switched Circuit world –Network features are standardised as “services”. “Service descriptions” are mapped onto a specific network technology (e.g. ISDN, GSM etc.) and specified by standards bodies. This takes a long time and is never complete due needing to address feature interaction, an absence of regression compliance. –OR Edge of network platforms are created to combine network based functions into new customised applications. IN network features are used to create new applications. In both cases the network features constrain what can be achieved.

Views on current service development The IP network world –Network features are enabled though standardised “protocols”. “Services” in IP networks are really network functions. Applications are built using any number of protocols integrated together outside of the specification development process. Process is highly dynamic and specific protocols emerge and fade.

Services and Applications Focus on reusable components and flexible construction to fuel innovation rather than procedural bit-wise definition of services.

Service Abstraction Layer Service Application Layer Service Applications Service Capabilities Registration Capability Application Construction More information: – Routing Capability A design-time view... Connection Control Capability

Conclusions Key issues to consider –Enabling innovation in a controlled manner such that accepted social practises (e.g. privacy etc.) are preserved. Opportunities –Enabling new network technologies to be adopted. –Enabling innovation in network services. Challenges –How to address the key issues such that the opportunities can be realised.