Sync'ed Clients and Traffic Trends

1. sync’ed clients and traﬃc trends Matsuzaki ‘maz’ Yoshinobu <maz@iij.ad.jp> 2015/05 maz@iij.ad.jp 1

2. traﬃc and network design •  we plan upgrading based on traﬃc trend – to avoid congesGons 2015/05 maz@iij.ad.jp 2

3. network design #1 •  over-‐subscripGon – only some of users uses the network at once – expecGng staGsGcal mulGplexing eﬀect – need to esGmate uGlizaGon to avoid congesGon User User １００Mbps １００Mbps １００Mbps Internet 2015/05 maz@iij.ad.jp 3

4. network design #2 •  over-‐provisioning – provide more bandwidth than needed User User １００Mbps １００Mbps 1Gbps Internet 2015/05 maz@iij.ad.jp 4

5. backbone network design •  based on over-‐subscripGon – we can expect more staGsGcal mulGplexing effect – cost effecGve •  over-‐provisioning to its uGlizaGon – for redundancy – low latency Backbone staGsGcal mulGplexing effect 2015/05 maz@iij.ad.jp 5

6. typical traﬃc •  enterprises •  consumers •  CDN •  IX •  mobile 2015/05 maz@iij.ad.jp 6

7. enterprise 2015/05 maz@iij.ad.jp 7

8. enterprise weekday 2015/05 maz@iij.ad.jp 8

9. consumer (broadband) 2015/05 maz@iij.ad.jp 9

10. consumer weekday 2015/05 maz@iij.ad.jp 10

11. consumer weekend 2015/05 maz@iij.ad.jp 11

12. CDN (contents distribuGon network) 2015/05 maz@iij.ad.jp 12

13. CDN weekday 2015/05 maz@iij.ad.jp 13

14. CDN weekend 2015/05 maz@iij.ad.jp 14

15. IX (Internet Exchange) 2015/05 maz@iij.ad.jp 15

16. IX weekday 2015/05 maz@iij.ad.jp 16

17. IX weekend 2015/05 maz@iij.ad.jp 17

18. mobile 2015/05 maz@iij.ad.jp 18

19. mobile weekday 2015/05 maz@iij.ad.jp 19

20. mobile weekend 2015/05 maz@iij.ad.jp 20

21. traﬃc trend •  we can upgrade based on that – important! •  know your customer – how they are using network 2015/05 maz@iij.ad.jp 21

22. traﬃc concentraGon •  it someGmes happens •  ‘staGsGcal mulGplexing eﬀect’ is reduced 2015/05 maz@iij.ad.jp 22

23. how to deal with concentraGons •  upgrade – more bandwidth – cost + •  wait and see – congesGon – customer experience -‐ •  something else – ?? 2015/05 maz@iij.ad.jp 23

24. new year greeGngs •  January 1st 00:00-‐02:00 – phone call – SMS – e-‐mail – SNS •  about 7 Gmes more messages than usual •  mobile operators have asked users to avoid such messages during the peak Gme 2015/05 maz@iij.ad.jp 24

25. soware/data distribuGon •  Windows Update •  iOS/MacOS Update •  game update •  karaoke update •  several giga byte data •  at the same Gme •  many clients 2015/05 maz@iij.ad.jp 25

26. iOS8 •  it seems Apple introduced some kinds of queuing mechanism iOS8 started to distribute 2015/05 maz@iij.ad.jp 26

27. mobile device •  people bring it always – they can use it anyGme •  it changed traﬃc pacern – commuGng and lunch Gme •  commuGng is a challenge for mobile in tokyo – about 3000 persons per train – 47 trains per hour – somehow you need to do handover L 2015/05 maz@iij.ad.jp 27

28. mobile devices and alarm clock •  clock on mobile devices is well synced – you can use mobile as a clock •  mobile devices ‘sleep’ to reduce bacery usage – and once wakeup, it starts to communicate •  mobile operators see high traﬃc peek at – 6:30, 7:00, 7:30.... – very short period traﬃc 2015/05 maz@iij.ad.jp 28

29. summary •  ‘StaGsGcal mulGplexing eﬀect’ is a key of backbone network design •  There could be concentraGons because of social and technical reasons •  Network operators should give feedback – to users, CDNs and applicaGon developers – to avoid concentraGons where possible 2015/05 maz@iij.ad.jp 29