How RTA can fit to Date: September 2016

Slides:



Advertisements
Similar presentations
Suggestions for GRIDMAN PAR Proposal IEEE Presentation Submission Template (Rev. 9) Document Number: IEEE C802.16gman-10/0005 Date Submitted:
Advertisements

Response to Official Comments
P802.11aq Waiver request regarding IEEE RAC comments
MMWave Distribution Network Discovery
MMWave Distribution Network Discovery
Discussion on the Multi-band Discovery Assistance Proposal
doc.: IEEE <doc#>
Discussion on the Multi-band Discovery Assistance Proposal
Discussion on the Multi-band Discovery Assistance Proposal
MMWave Distribution Network Discovery
Discovery Assistance for ay
Extremely High Throughput (EHT) – Way forward
Multi-band Discovery Assistance
Multi-band Discovery Assistance
Discovery Assistance for ay
Extremely High Throughput (EHT) – Way forward
Multi-band Discovery Assistance for ay (CR on CID 1771)
EHT SG formation Motion
Thoughts on RTA Development
Discussion on EHT PAR Construction
View on EHT Candidate Features
Old and new latency requirements
Discussion on Target Use Cases of RTA
Thoughts on RTA Development
Thoughts on RTA Development
Raising the PAR Date: Authors: January 2014 January 2014
Thoughts on RTA Development
Old and new latency requirements
Thoughts on RTA Development
Old and new latency requirements
Thoughts on RTA Development
Thoughts on RTA Development
Extremely High Throughput (EHT) – Way forward
Thoughts on RTA development
doc.: IEEE <doc#>
Additional game use case over WLAN
Proposed resolution of CID 3518
Proposed resolution of CID 3518
Proposed resolution of CID 3518
Functional Requirements for EHT Specification Framework
Multi-band Discovery Assistance for ay (CR on CID 1771)
Discovery Assistance for ay
RTA TIG Closing Report Date: Authors: November 2018
Enhancing BSS Transition Management
FD TIG Summary for EHT Date: Authors: November 2018 Name
Proposed text for HTSG draft PAR and 5 Criteria
TDD-SP Coexistence Date: September 2016
RTA report summary Date: Authors: Jan 2019
Old and new latency requirements
Discussion on Target Use Cases of RTA
IEEE MEDIA INDEPENDENT SERVICES DCN:
Enabling STA to STA communication
Low latency streaming capability for game applications
IEEE MEDIA INDEPENDENT SERVICES DCN:
P802.11aq Waiver request regarding IEEE RAC comments
P802.11aq Waiver request regarding IEEE RAC comments
FD TIG Summary for EHT Date: Authors: November 2018 Name
Proposed resolution of CID 3518
RTA Sep 26, 2018, Teleconference Call
FD TIG Summary for EHT Date: Authors: November 2018 Name
EHT SG formation Motion
Multi-band comments resolution
Multi-link Operation Framework
Functional Requirements for EHT Specification Framework
EHT SG formation Motion
Response to Official Comments
RTA report summary Date: Authors: Jan 2019
Multi-link Operation Framework
Multi-Link Architecture and Requirement Discussion
Multi-link Operation Framework
Presentation transcript:

How RTA can fit to 802.11 Date: 2019-01-14 September 2016 doc.: IEEE 802.11-16/XXXXr0 How RTA can fit to 802.11 Date: 2019-01-14 Name Affiliation Address Phone Email Kazuyuki Sakoda Sony 1730 N. First Street, San Jose CA 95112 kazuyuki.sakoda(at)sony.com William Carney William.Carney(at)sony.com

Introduction RTA TIG studied applications requiring low latency capability As presented in [1], it is desirable that this 802.11 amendment should define a technology that is aligned with 802.1 TSN Some additional APIs might be useful, particularly for 802.11 networks as discussed in [2] In parallel, we see that EHT TIG/SG is also trying to embrace low latency capability as a part of the project scope [3] It would be useful to have some discussion regarding the possible approaches for 802.11 to define real time technology as a part of the 802.11 standard

Recap : TSN compatibility What is suggested by [1]: 802.11 should define compatible features with 802.1 TSN, such as Time-Aware Traffic Shaping This type of technology should be PHY/Lower MAC independent RTA technology coverage: Higher Layer SME 802.1 Network Higher MAC MLME RTA 802.11 MAC Lower MAC PHY PLME 802.11 PHY

Recap : Additional API? If we add additional API similar to TSPEC [4], RTA technology coverage: Higher Layer SME 802.1 Network Higher MAC MLME RTA 802.11 MAC Lower MAC PHY PLME 802.11 PHY

Recap: EHT discussion EHT might be developing real-time technology [3] However, draft PAR proposal [5] does not include real time capability in its scope… RTA technology coverage: Higher Layer SME 802.1 Network Higher MAC MLME RTA?? 802.11 MAC Lower MAC PHY PLME 802.11 PHY

Different approaches potentially exist to achieve similar outcomes regarding RTA Review and discuss the alternatives

Define real-time technology solely If RTA becomes solo project: Pros: We can secure real-time capability in the specification The solution could/should be band agnostic Cons: The coverage of the technology might be limited in some way, i.e., try to reuse existing components; not requiring hardware changes… May not deliver best possible latency improvements if not tightly coupled to specific MAC/PHY SME 802.1 Network Higher MAC MLME RTA Lower MAC PHY PLME

Let EHT work on everything If it is decided to have EHT work on real time technology Pros: We can modify Lower MAC and PHY as needed Cons: Not clear if EHT will put emphasis on real time capability The solution will be operating band specific Higher Layer SME 802.1 Network Higher MAC MLME EHT Real-time feature?? 802.11 MAC Lower MAC PHY PLME 802.11 PHY

A more advanced option We should be able to leverage both RTA focused project deliverable and EHT deliverable Pros: Real time technology could be defined as band agnostic framework We can leverage advanced lower MAC and PHY features if EHT defines such capability Cons: Careful RTA/EHT project coordination will be necessary SME 802.1 Network Higher MAC MLME RTA Lower MAC EHT Real-time Feature ?? PHY PLME

Or more challenging goal might help grow the community If we truly believe that there is a strong need to satisfy challenging low-latency and robustness requirements, it might be better to forget everything about 802.11 backward compatibility… Pros: Maybe possible to design truly optimized specification Cons: Could be hard to obtain support on this direction from 802.11 community SME 802.1 Network Higher MAC MLME RTA: Brand new 802.11 Lower MAC PHY PLME

Summary Walked through some options for 802.11 to develop real-time technology RTA TIG may want to discuss as a group which option would be beneficial to the community while maintaining reasonable/viable project scope

Straw poll (1) Which option do you think that 802.11 should take? RTA defines whole real time functionality (forget about EHT) Let EHT work on the real time capability and do nothing else RTA defines higher MAC/MLME/SME functionality, whereas soliciting EHT to work on real time lower MAC/PHY technology Define a whole new MAC/PHY spec from scratch Need more discussion:

References [1] IEEE 802.11-18/1542r2, “Time-Aware Traffic Shaping over 802.11,” Dave Cavalcanti, et.al. [2] IEEE 802.11-18/1972r7, “Thoughts on RTA development,” Kazuyuki Sakoda, et.al. [3] IEEE 802.11-18/1263r3, “EHT SG formation Motion,” Ron Porat, et.al. [4] Draft P802.11REVmd D2.0 [5] IEEE 802.11-18/1231r1, “EHT draft proposed PAR,” Laurent Cariou