Industry perspectives: What they need, research-wise and code-wise - - PowerPoint PPT Presentation

industry perspectives what they need research wise and
SMART_READER_LITE
LIVE PREVIEW

Industry perspectives: What they need, research-wise and code-wise - - PowerPoint PPT Presentation

Industry perspectives: What they need, research-wise and code-wise November 13 , 2013 4th NDN Project Retreat Eiichi Muramoto/ Panasonic muramoto.eiichi@jp.panasonic.com Content Who we are (Panasonic) What we did (L4) What we need


slide-1
SLIDE 1

Industry perspectives: What they need, research-wise and code-wise

November 13 , 2013 4th NDN Project Retreat Eiichi Muramoto/ Panasonic muramoto.eiichi@jp.panasonic.com

slide-2
SLIDE 2

Content

 Who we are (Panasonic)  What we did (L4)  What we need

– research-wise and code-wise – Crowed sensing

slide-3
SLIDE 3

Panasonic is

 Panasonic (Maker with 300,000 employee)

– Home appliance maker

  • TV, Camera, Smartphone, Refrigerator, Microwave,

Air-con, Home bakery, Hair drier, Shaver, Car navigation, Laptop, home power-plugs

– System solutions

  • AV system, Security Camera
  • Fax, Copy, white board

ProAV PA Security Camera Appliances (under HEMS) Copy Fax/iFax White Board TV conferencing

slide-4
SLIDE 4

Network Engineer of Panasonic R&D

 We are L4 engineers for conferencing (real-time, low

delay) of Panasonic R&D

TV conferencing 秒 Mb ps Bandwidth Estimation

slide-5
SLIDE 5

5

Brand A Brand B Panasonic(V3.0)

TX Bandwidth Packet Loss* Comparison Video

Bandwidth Control: Low

Available Bandwidth Actual Data Amount

Check the actual video!

Packet Loss : Continues Packet Loss : Continues Packet Loss : Zero Bandwidth Estimation Accuracy : Low

Far Strong against Bandwidth Fluctuation

Bandwidth Estimation Accuracy : High

※ ※Packet Loss Rate (Exclude Error Correction Recovery) Packet Loss Rate (Exclude Error Correction Recovery) Actual Data Amount Available Bandwidth

Hi-Accuracy bandwidth tracing

Check the actual video! Check the actual video!

slide-6
SLIDE 6

Brand A

Comparison video between product of company A and Panasonic

Panasonic

 Accurate the available bandwidth estimation

and high frequency rate control of encoder using TFRC + RTT variation.

slide-7
SLIDE 7

What we need, research-wise and code-wise

slide-8
SLIDE 8

Sensor networking as expected driving application

 Crowd sensing

– Example

  • Waze

– car traffic congestion

  • Nike fuelband

– activity monitoring sportsware

  • CCNx Web-app ‘SHOUT’ @ ccnxcon2013

– Share comments between neighbors

slide-9
SLIDE 9

Features of Crowd sensing

 Collect data and make valuable “Information”  Computing and Communication

– of the people (crowd), by the people for the people

 by the people

– New application is being made – Evolving continuously naturally if platform exist

slide-10
SLIDE 10

Proposal: change the value chain

 Name will be used in terminal (application)  To realize this, stable open source is necessary

Current Status Proposed Everything on Cloud Google is the value collector Make the new loop of value chain Carriers or ISP should be the value collector SNS collect Google Information

API Application

data cloud Internet Carrier, ISP pipe commodity Name assignment and delegation rule CCN/NDN Carrier, ISP

sensor

New Name CCN/NDN Carrier, ISP

Tool kit (SDK)

collect

Application Collect + Search

Power of Crowd

slide-11
SLIDE 11

Deployment milestones

L1 L2 L3 L4 L5 L6 L7 2019 2018 2017 2016 2015 2014 2013

Filed test (Fixed) Filed test (mobile) Wire packet format (CISCO, PARC, etc) Mobility management (carries) Standardize (IETF) 標準化準備(PARC->IRTF、他) Router proto(R&D)(CISCO, ,Alcatel, etc) ルータ試作(製品)(同) ルータ製品開発 Stable software stack (NDN project?-> Linux, *BSD) Public TestBED (government) Facility investment (carrier, ISPs) Mobile/ adhoc Terminal product (Maker) fixed Terminal product (Maker) Virtualization technology Standardize naming (IETF->IANA) Factory proto (vendor) Prepare standardize(PARC->IRTF) Standardize (IETF) Service platform (data collection + search) (Carriers + Maker)

Service evolve (crowd sensing) Service evolve (BtoB)

SDK Issue name, location, time.. (Carriers + Maker) Product develop Global routing method (university) Discuss naming scheme (ENC)) Congestion control/ flow control (maker + carries ) Prepare standardize(NDN project>IRTF)

Ex. 4K Olympic Ex: Security camera

Service evolve (BtoC)

slide-12
SLIDE 12

Conclusion & Discussion

 Crowd sensing is the expected driving application  Currently google (or SNS provider) suck the value of

“Information”

– As the result

  • carriers becomes “pipe” provider, maker becomes looser

 Change the value chain focusing on power of crowd.

Because essentially data is generated at the edge

  • terminals. Carriers or ISPs can collect it directly

 To realize this stable open source is necessary.