industry perspectives what they need research wise and
play

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


  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

  2. Content  Who we are (Panasonic)  What we did (L4)  What we need – research-wise and code-wise – Crowed sensing

  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 Appliances (under HEMS) PA ProAV Security Camera Copy Fax/iFax White Board TV conferencing

  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

  5. Hi-Accuracy bandwidth tracing Available Bandwidth Actual Data Amount Panasonic(V3.0 ) Brand A Brand B Available Bandwidth TX Bandwidth Actual Data Amount Bandwidth Estimation Bandwidth Estimation Bandwidth Control: Low Accuracy : High Accuracy : Low Packet Loss : Continues Packet Loss : Zero Packet Loss : Continues Packet Loss* Far Strong against Bandwidth Fluctuation Comparison Video Check the Check the Check the actual video! actual video! actual video! ※ Packet Loss Rate (Exclude Error Correction Recovery) Packet Loss Rate (Exclude Error Correction Recovery) ※ 5

  6. Comparison video between product of company A and Panasonic Brand A Panasonic  Accurate the available bandwidth estimation and high frequency rate control of encoder using TFRC + RTT variation.

  7. What we need, research-wise and code-wise

  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

  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

  10. Proposal: change the value chain  Name will be used in terminal (application)  To realize this, stable open source is necessary Proposed Current Status Everything on Cloud Make the new loop of value chain Google is the value collector Carriers or ISP should be the value collector Name assignment and delegation rule cloud Information New Name CCN/NDN CCN/NDN Internet Tool kit (SDK) Carrier, ISP Carrier, ISP collect Carrier, ISP Collect + Search Google pipe Application collect SNS commodity data API Application Power of Crowd sensor

  11. Deployment milestones 2013 2014 2015 2016 2017 2018 2019 L7 Mobile/ adhoc fixed Service Terminal product Terminal product L6 evolve (Maker) (Maker ) (crowd sensing) L5 Standardize naming ( IETF->IANA ) Discuss naming scheme (ENC)) SDK Service platform Service Issue name, location, time.. (data collection + search) L4 (Carriers + Maker) (Carriers + Maker) evolve Filed Filed test (BtoC) test Congestion control/ flow control (maker + carries ) (Fixed ) ( mobile ) Ex. Prepare standardize ( NDN project>IRTF) Standardize ( IETF ) 4K Olympic L3 Global routing method (university) Mobility management (carries) Public TestBED Facility investment (government) (carrier, ISPs) Stable software stack ( NDN project?-> Linux, *BSD ) Service Factory proto (vendor) ルータ試作(製品 ) (同) Product develop Virtualization technology evolve Router proto ( R&D) ( CISCO, ,Alcatel, etc ) ルータ製品開発 (BtoB) Prepare standardize ( PARC->IRTF) 標準化準備( PARC->IRTF 、他 ) Standardize ( IETF ) Wire packet format ( CISCO, PARC, etc ) L2 Ex : L1 Security camera

  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.

Recommend


More recommend