synced clients and traffic trends

29
sync’ed clients and traffic trends Matsuzaki ‘maz’ Yoshinobu <[email protected]> 2015/05 [email protected] 1

Upload: bangladesh-network-operators-group

Post on 22-Jan-2018

180 views

Category:

Internet


0 download

TRANSCRIPT

sync’ed  clients  and  traffic  trends

Matsuzaki  ‘maz’  Yoshinobu  <[email protected]>

2015/05 [email protected] 1

traffic  and  network  design

•  we  plan  upgrading  based  on  traffic  trend  –  to  avoid  congesGons  

2015/05 [email protected] 2

network  design  #1

•  over-­‐subscripGon  – only  some  of  users  uses  the  network  at  once  – expecGng  staGsGcal  mulGplexing  effect  – need  to  esGmate  uGlizaGon  to  avoid  congesGon

User

User 100Mbps

100Mbps

100Mbps

Internet

2015/05 [email protected] 3

network  design  #2

•  over-­‐provisioning  – provide  more  bandwidth  than  needed  

User

User 100Mbps

100Mbps

1Gbps

Internet

2015/05 [email protected] 4

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 [email protected] 5

typical  traffic

•  enterprises  •  consumers  •  CDN  •  IX  •  mobile  

2015/05 [email protected] 6

enterprise

2015/05 [email protected] 7

enterprise  weekday

2015/05 [email protected] 8

consumer  (broadband)

2015/05 [email protected] 9

consumer  weekday

2015/05 [email protected] 10

consumer  weekend

2015/05 [email protected] 11

CDN  (contents  distribuGon  network)

2015/05 [email protected] 12

CDN  weekday

2015/05 [email protected] 13

CDN  weekend

2015/05 [email protected] 14

IX  (Internet  Exchange)

2015/05 [email protected] 15

IX  weekday

2015/05 [email protected] 16

IX  weekend

2015/05 [email protected] 17

mobile

2015/05 [email protected] 18

mobile  weekday

2015/05 [email protected] 19

mobile  weekend

2015/05 [email protected] 20

traffic  trend

•  we  can  upgrade  based  on  that  –  important!  

•  know  your  customer  – how  they  are  using  network  

2015/05 [email protected] 21

traffic  concentraGon

•  it  someGmes  happens  •  ‘staGsGcal  mulGplexing  effect’  is  reduced  

2015/05 [email protected] 22

how  to  deal  with  concentraGons  

•  upgrade  – more  bandwidth  – cost  +  

•  wait  and  see  – congesGon  – customer  experience  -­‐  

•  something  else  – ??  

2015/05 [email protected] 23

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 [email protected] 24

so\ware/data  distribuGon

•  Windows  Update  •  iOS/MacOS  Update  •  game  update  •  karaoke  update  

•  several  giga  byte  data  •  at  the  same  Gme  •  many  clients  

2015/05 [email protected] 25

iOS8

•  it  seems  Apple  introduced  some  kinds  of  queuing  mechanism  

 iOS8  started  to  distribute

2015/05 [email protected] 26

mobile  device

•  people  bring  it  always  –  they  can  use  it  anyGme  

•  it  changed  traffic  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 [email protected] 27

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  traffic  peek  at  – 6:30,  7:00,  7:30....  – very  short  period  traffic  

2015/05 [email protected] 28

summary

•  ‘StaGsGcal  mulGplexing  effect’  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 [email protected] 29