ToC

1. Services and applications in IPv6 environmentJordi Mongay BatallaNational Institute of TelecommunicationsWork performed by: NIT, PG, PCSS, PWrWarsaw, May 28th, 2013 1

2. ToC New scenarios for services and applications Applications and services in IPv6: Currentsituation IIP project: IMS and IPTV IIP project: IMS and VoIP Conclusions

3. New scenarios Advantages of IPv6 for newapplications and services: Addressspace Number of devices Re-establishment of an end-to-end communicationarchitecture Better network management and routing efficiency (largersubnetspace) as well as hierarchical route aggregation No need for Network address translation -NAT Auto-configuration Multicast Mobility Security

4. Cloud Computing The network goes towards the cloud From the beginning: users and servers Share of server resources  Grid computing Public access to the services  Service Oriented Architecture Source: Forrester Research Inc.

5. Cloud Computing Limits to the cloud Client  server connection Lack of QoS Lack of self-managed SOA Result: Lack of cooperation between elements in cloud computing. Efficiency decreases. We stay in grid! IPv6 may help since: cooperation protocols for distributed cloud computing requires auto-configuration and self-management (self-managed SOA) simple removal of client-server obligation is not possible in environment with NAT

6. Scenario: Distributed management p2p Even when P2P networks are distributed networks, their management is centralized It results in*: Need for registration of users Also small user groups, which want to share files, must be registered in a service provider Lack of integrity in contents Self-managed distributed management of P2P networks will be acquired only with end-to-end communication and self-managed networks * We do not consider legal issues (the most important in p2p networks)

7. Internet of Things In this moment we have „Islands of Things” instead of Internet of Things (e.g. sensor networks) The original business model of IoT included that whatever wherever whenever may have connectivity Hans Vestberg, CEO of Ericsson, predicted the growth in the number of connected devices to rise from 5 billion to 50 billion by 2020. Much of this connectivity is fuelled by innovative new devices in areas such as e-health and logistics • IPv6 providesconnectivity, security, auto-configuration and eliminates NAT barrier • Therearethousands of newscenarios for Internet of Thingsinnextfields: • Home networks • Vehicular networks • E-Health networks • Educational networks • Etc.

8. E-Health Wireless medical sensor technologies + IPv6 (connectivity + security)= delivering healthcare services at a distance Remote monitoring of the patients’ health condition and remote care for the elderly and handicapped (wherever they are, whatever they do) significantly improve standards of living Sensors for real-time physiology(blood sugar, pulse, temperature, galvanic skin response and many others) - systems used to monitor such diseases as cardiac, diabetic, rehabilitation or monitor general health or wellness Ambient monitoring (e.g. air pollution and humidity) - systems designed for monitoringe.g. patients with allergy or asthma The removal of NAT allows for easy access for service or/and devices, to perform remoteconfiguration and maintenance – it is important issue for the elderly and handicapped which are living alone

9. Vehicular services • Approximately number of vehicles exceeds 800 million in the world today. Those vehicles travel billions km: • Let’s them connect together (Vehicle-to-Vehicle V2V) and with devices installed along the roadside (Vehicle-to-Infrastructure V2I), to improve safety and traffic efficiency • Vehicular networks will provide three types of services: • Road safety (e.g. detection potentially dangerous situations in advance and extending the drivers' awareness of the surrounding environment) • Traffic efficiency (e.g. thanks to V2V communication cars can detect an obstacle or traffic jam and avoid it by rerouting) • Others (infotainment, fleet control etc.) • IPv6: mobility support and large address space

10. Current situation: Network operators becoming Content providers The example of Comcast: Big network operator that tries to integrate users and content servers in seamless end-to-end communication Comcast moved to IPv6 because it was in need of over 100 million addresses (estimations were that within a few years, Comcast would have some 20 million video customers, an average of 2.5 set-top boxes per customer, and 2 IP addresses per box) IPv6 may help the integration of network providers, content providers, service providers (as CDN) thanks to possibility of end-to-end communication More efficiency in content streaming, control of traffic (e.g. load balancing)

11. Current situation • Google: one uniquedomain • Telefonica network • Problems with IPv6 users • Closed environment in applications, in opposite of network services • Commercial applications

12. Current situation: Fitness of legacy IPv4 apps&services to IPv6 Changes in IPv6-running apps: Larger IP headersmust be consideredwhencomputing maximum payloadsize DNS recordsinclude, amongothers: AAAA recordtype Functionalities related to NAT can be ignored New socketoptions: New functions for passingaddresses New functions for returningaddresses New addressstructures for API Changes in „checksum” for TCP and UDP protocols Memory units for storingaddresses (vectors, arrays) New formats for URLs: http://[IPv6_addr]:port/

13. IIP project: Motivation for Multimedia platform • Increasing popularity of multimedia services

14. IIP project: IPTV scenario Real Time Protocol (RTP) was designed for IPTV and VoD communication Why RTP does not run in the Internet? NAT breaks end-to-end connectivity, especially in connectionless protocols as UDP (RTP uses UDP) Many NAT traversal techniques exist, but no single method works in every situation since NAT behavior is not standardized Results: the most of video traffic is sent by http or similar there is no open IPTV platforms correctly working in the Internet IPTV systems are implemented only on the last mile network (ISP) IPv6 allows the use of protocols specialized in IPTV and live transmission

15. IPTV scenario The communication between Service provider and Set-Top-Box is not possible in IPv4 IPv6 offers new business models for IPTV Better QoE, Awareness of User preferences, Optimized advertising Companies interested in the investigation of this issue: youtube, BCS global…

16. IPTV scenario Multicast is mandatory for IPTV in the Internet In IPv4 Multicast requires additional mechanisms, which generally do not collaborate with network level mechanisms mechanisms as network level adaptation cannot be provided in Multicast IPv4 • onlyapplicationlevelmechanisms (Scalable Video Coding - SVC, DynamicAdaptivestreamingover HTTP - DASH) arevalidin IPv4 scenarios • Results: • Applicationlevelmechanismsaretheuniqueusedwithinthenetwork • dynamicadjustment of multicasttreescouldofferbetterQoE

17. IPTV scenario In IPv6 there is dynamic adjustment of multicast trees at the network layer New streaming adaptation may be provided for multicast flows as e.g., network level adaptation The adaptation may be provided in many points of the network and not only in edge points (better adaptation in multi-domain scenario) • Itiseasier to providenetworkawareness for treeadjustment(since multicastisresponsibility of thenetworkprovider) • All theimplementations of the IPv6 protocolcontainnativelyMulticast service, so no more hardware isnecessary

18. IPTV: Integrated services • IPTV: • streaming • VoD • VoIP • conversations • conferencing

19. IMS Platform OpenIMSCore (IPv6) IPTV Application Server (AS) UCT IPTV AS IPTV: Integrated services • Streamming Serwer • Live555. We selectedthis! • Darwin Streaming Server • VLC • QuickTimeStreaming Server

20. IPTV: Integrated services • Open IMS Core • Advance configuration for IPv6 support • UCT IMS Client • Support for IPv6 • Improvement of RTP implementation • Library Live555 • Support for RTSP • Support for IPv6 • Streaming server • Interface y2

21. IPTV: Integrated services

22. IIP project: VoIP scenario Kamailio + Python AS Calls routing with load-balancing. MRF server monitoring. Sessions failover mechanism. Media servers management (gain, mute, volume level). Conference details (user list, session state) FreeSWITCH + Python QoS/QoE evaluation tool Open IMS Core MRF Media manipulation Qos/QoE evaluation 3GPP TS 23.218 V10.0.0 (2011-03)

23. IIP project: VoIP scenario • Local agent • Application log • RTP timeout • ad hoc QoS/QoE(MOS) • Reports sent to AS • Connectivitymonitoring • Heartbeat

24. IIP project: VoIP scenario • QoS/QoE monitoring

25. IIP project: VoIP scenario • Failover scenario Initialization of conference call Conference room restoration Change of RTP user session parameters

26. Conclusions • Thecurrentapplications and services require no limitsin IP layer. IPv6 overcomessome of theselimits • Currentsolutionsarefullyfitted to the IPv4 protocol and, currently, allnewscenariosmust be adapted to thisprotocol • Users will acquiremorecontrol of thecommunications, betterQoE, moresimplifieduse of thenetwork • Network providers will reachmorecontrol of traffic, self-management, possibility of expanding to other business models • Contentproviders will acquireintegritythanks to end-to-endcommunication • IIP project: • Implementation of IPTV and VoIP services on IMS platform • Testbed in IPv6 network • Performedexperiments: IPTV; Reliableconferencing; Ad hoc QoS/QoE monitoring

27. Thankyou!