Enabling carrier evolution for triple play services

Transcription

1 Obr.: d Enabling carrier evolution for triple play services EFFECTS OF TRANSMISSION PERFORMANCE ON MULTIMEDIA QoS June Prague, Czech Republic Roman Osredkar, osredkar@ iskratel.si, Aljaž Tomaž, iskratel.si, Iskratel Ltd.

2 Overview Telecommunication Services in Slovenia QoS in access and core networks Discovered triple play issues and solutions Conclusion 1

3 Telecommunication Services in Slovenia Number of operators Main operators: Telekom Slovenije, T-2, Tuš Telekom, Amis... Services offered Service Penetration of broadband access 17,3% ( ) Number of double play users Number of triple play users IPTV : Cable TV: Terrestrial TV ~ 10% : 40% : 50% Sources: number of operators offering the service Broadband 64 internet access xdsl access 14 Cable internet access 37 FTTH 8 Wireless radio access

4 Slovenian broadband access pie 3

5 Telekom Slovenia and transition to IP 1996 IP network operational 2001: ADSL lanuched 2003: IP TV introduced (as one of first IPTV) 2004: National WiFi network 2004: ADSL users 2005: Triple Play launched 2005: ADSL users, 2006: ADSL users, 2008: WiMax access (1 Mbit/s)

6 T : Established 2005: Offering triple play based on VDSL 2006: FTTH

7 QoS In beginning VoIP ATM DSLAM Then transition to IP-DSLAMs because of multicast supported IPTV QoS in access (PVC ADSL..), bandwidth over-provisioning Video services (IPTV, VoD...) QoS, higher bandwidth requirements, MPLS in core 6

8 It works without DiffServ in aggregation Access uses ADSL CBR for voice and video and PVC mapped to ethernet COS Bandwidth is known after user s modem is synchronized for the first time The IPTV is available if users have enough bandwidth. ADSL2+ is used to reach users which would otherwise be unreachable The voice bandwidth is guaranteed as overall bandwidth is always over-provisioned in aggregation The Core is dimensioned to support all the required bandwidth The BRAS is limiting the BW according the up/down BW that is defined by the packet user is paying for Core uses MPLS 7

9 QoS requirements Voice, Video, Data Quality of experience Same user experience as for broadcast TV Maximum one error in TV picture each half of the hour Couch surfing / channel zapping Channels for IPTV do not change immediatelly (< 150ms) If there is not enough bandwidth users are not satisfied with bad picture, also coding and bitrate matters Especially if there is a second or more delay in case of football goal, Users of old style TV already saw it and jump with joy while IPTV is still waiting to see it. 8

10 Discovered triple play issues Delays Buffers in equipment Packet loss in bursty traffic video imperfections IGMP delays must not be too big! Bandwidth for video ADSL CPE/STB Need for transition from MPEG2 to MPEG4 decoding DHCP broadcasts are seen by all STB in same VLAN After shutdown of STB the VoD stream continues = flood New services Unlimited DL internet access if user connects to VLAN port for video 9

11 Solutions Delays Adjust right size for buffers (for ftp use TCP window scaling) Shaping of video traffic to avoid packet loss in bursty traffic. We developed addition to Wireshark (menu Statistics/Multicast_streams) Shorter time when switching channels with faster IGMP switching Bandwidth for video From ADSL to ADSL2+ for long copper lines Even better is optical access (Active optical network, FTTH) CPE/STB Limit size of VLAN to limit broadcasts Health messages to VoD streamer to stop the stream in case of STB fault New services Walled garden internet HDTV (MPEG4 decoding) 10

12 Conclusion Implementation of triple play solutions starts with correct network design The triple play network must be dimensioned and planned to support the VoIP, IPTV and VoD Integration of equipment from chosen equipment providers is next step to the working solution The triple play issues can be solved only with cooperation of equipment vendor and service provider 11

13 Thank you for your attention 12