Briarcliff Manor, New York Month 1998 doc.: IEEE 802.11-98/xxx July 2001 1394 Requirements for 802.11e Takashi Sato Philips Research USA Briarcliff Manor, New York t.sato@philips.com John Doe, His Company

Outline Our view of Wireless 1394 Wireless 1394 architecture Month 1998 doc.: IEEE 802.11-98/xxx July 2001 Outline Our view of Wireless 1394 Wireless 1394 architecture Supported net topology General requirements Hooks needed in 802.11e Summary & Conclusion John Doe, His Company

Wireless 1394 Connect 1394 clusters wirelessly July 2001 Connect 1394 clusters wirelessly Connect wireless 1394 devices to the network Enable mobile1394 applications and ease of installation DTV DVCR Living Room Remote D-VHS CD Changer CD-R MD MIDI Keyboard Notebook PC Amp DV Camcorder NIM HDD Home Office Printer Bed Room DVD TV STB Scanner Security Camera Navi. System Cable Phone Line Wireless 1394 Bridge PDA SP 1394 node

1394 Node/Bridge Architecture July 2001 1394 Node/Bridge Architecture 1394 Phy 1394 Link 1394 App. 1394 Tr. Isoch. asynch. 1394 Node Bridge Phy Bridge Link Bridge Management & Internal Fabric Bridge Tr. Isoch. asynch. 1394 Bridge

Wireless1394 Architecture July 2001 Wireless1394 Architecture Wireless1394 Node Wireless 1394 Bridge 1394 App. Bridge Management & Internal Fabric 1394 Tr. Bridge Tr. Bridge Tr. asynch. Isoch. asynch. Isoch. Isoch. asynch. 1394 PAL 1394 PAL Bridge Link 802.11e 802.11e Bridge Phy 802.11a 802.11a

Net Topology 1394 Bus 1394 node 1394 node 1394 node 1394 Bus 1394 node July 2001 1394 Bus 1394 node 1394 node 1394 node 1394 Bus 1394 node Wireless 1394 bridge Wireless 1394 bridge 802.11 WLAN (virtual 1394 bus) Wireless 1394 bridge Wireless 1394 node Wireless 1394 node 802.11 WLAN (virtual 1394 bus) Wireless 1394 node Wireless 1394 bridge 1394 node 1394 Bus 1394 Bus Wireless 1394 node Wireless 1394 node 1394 bridge 1394 bridge 1394 Bus 1394 node 1394 node 1394 node 1394 node

Wireless 1394 Architecture July 2001 Wireless 1394 Architecture Adopted by ETSI/BRAN for Wireless 1394 over Hiperlan/2 in Europe Adopted by MMAC for Wireless 1394 in Japan Adopted by 1394 TA/WWG for Wireless 1394 in US, including Wireless 1394 over 802.11 There have been efforts for harmonization

General Requirements Support for multiple priority traffic July 2001 General Requirements Support for multiple priority traffic Clock synchronization Isochronous traffic Asynchronous traffic Support for (virtual) bus management Topology change management Bandwidth management Distributed control

July 2001 Hooks Needed in 802.11e Frequent and stable clock/frame synchronization capability enables 1394 clock synchronization in 1394 PAL (1394 clock: 24.576 MHz ± 100 ppm) e.g., HL2 uses 2ms frame synch and frame number 802.11 beacon might be used for this purpose Isochronous capability provides guaranteed bandwidth and bounded latency Multicast capability enables multiple listeners for an isoch/asynch stream join/leave capability without disturbing ongoing streams

Hooks Needed in 802.11e Broadcast capability Retry limit capability July 2001 Hooks Needed in 802.11e Broadcast capability enables asynchronous packet broadcast Retry limit capability number of retries (or lifetime) can be set by higher layer (at least isoch and asynch packets need separate parameters) retry failure (timeout) to be reported to higher layer (Virtual) bus management support notification of (virtual) bus topology change Isochronous resource management support notification of available bandwidth provision for bandwidth degradation after stream setup

Summary & Conclusion We are coming from CE camp July 2001 Summary & Conclusion We are coming from CE camp We cannot adopt IP-centric solutions just yet There is very few IP-enabled CE devices IP is immature for AV applications 1394 (directly) over 802.11 makes more sense than 1394 over IP over 802.11 AV applications care about overhead more than IP applications do IP can coexist over 802.11 or be carried over 1394 over 802.11 if needed

July 2001 Summary & Conclusion We need hooks in 802.11e to support our Wireless 1394 over 802.11 solution Things that can be dealt with in 1394 CL will be dealt in 1394 CL But, some other things (i.e., hooks) have to be in 802.11e More interaction is encouraged between 802.11 TGe and 1394 TA/WWG Please give 1394 TA/WWG a chance to review the 802.11e draft thoroughly, identify required hooks, and make proposals