May 2000 doc IEEE 802 11 00070 Multimedia

  • Slides: 8
Download presentation
May 2000 doc. : IEEE 802. 11 -00/070 Multimedia Synchronization and 802. 11 MAC

May 2000 doc. : IEEE 802. 11 -00/070 Multimedia Synchronization and 802. 11 MAC Enhancements Submission 1 John Kowalski, Sharp Laboratories

May 2000 doc. : IEEE 802. 11 -00/070 Multimedia Synchronization and 802. 11 MAC

May 2000 doc. : IEEE 802. 11 -00/070 Multimedia Synchronization and 802. 11 MAC Enhancements • Considerations for delay synchronization in SOHO networks • Suggested functional requirements • Remarks on submitted proposals. Submission 2 John Kowalski, Sharp Laboratories

May 2000 doc. : IEEE 802. 11 -00/070 Considerations for delay (1 of 2)

May 2000 doc. : IEEE 802. 11 -00/070 Considerations for delay (1 of 2) If significant to user/content: 1. Physical layer FEC coding delay. 2. Any FEC added on at higher layers if significant. 3. Retransmit delays through the network(s). 4. Delays to account for STA’s joining the network. Submission 3 John Kowalski, Sharp Laboratories

May 2000 doc. : IEEE 802. 11 -00/070 Considerations for delay (2 of 2)

May 2000 doc. : IEEE 802. 11 -00/070 Considerations for delay (2 of 2) 6. Synchronization schemes, if possible, should enable new devices to join a network in mid-transmission and during handoff. 7. Control applications that exist concurrently and interact with AV streaming should have low delay perceptible to the user. (SOHO video remote? ) Submission 4 John Kowalski, Sharp Laboratories

May 2000 doc. : IEEE 802. 11 -00/070 Functional Requirements 1. Delay buffers can

May 2000 doc. : IEEE 802. 11 -00/070 Functional Requirements 1. Delay buffers can be assumed to exist at terminal devices in the network, and are adjustable based on communication from the network. For some kinds of traffic packets are timestamped. Data need not be timestamped if synchronization is maintained. Submission 5 John Kowalski, Sharp Laboratories

May 2000 doc. : IEEE 802. 11 -00/070 Functional Requirements 2. The communication of

May 2000 doc. : IEEE 802. 11 -00/070 Functional Requirements 2. The communication of delays should be sent to a central point – for 802. 11 applications we can assume this would be the Point Coordinator- to determine the delay required for synchronizing all devices. Submission 6 John Kowalski, Sharp Laboratories

May 2000 doc. : IEEE 802. 11 -00/070 Remarks on submitted proposals. • Intel

May 2000 doc. : IEEE 802. 11 -00/070 Remarks on submitted proposals. • Intel – Statistical prioritization based on 802. 1 q tags. – So WLAN related delays need to be communicated at higher layers. • Sharewave, AT&T – Appears to support requiremnents – Handoff? Submission 7 John Kowalski, Sharp Laboratories

May 2000 doc. : IEEE 802. 11 -00/070 Remarks on submitted proposals • Lucent

May 2000 doc. : IEEE 802. 11 -00/070 Remarks on submitted proposals • Lucent – Not clear how streaming synch can be supported. • IAPP proposal doesn’t explicitly support communication of delay parameters. (Consider source handing off). Submission 8 John Kowalski, Sharp Laboratories