1. Joint Proposal R1 update
5/18/2019
doc.: IEEE /xxx
September 2000
Joint Proposal R1 update
AT&T, Lucent, Sharewave
BreezeCOM, NWN/Intersil
Presented BY
Wim Diepatraten - Lucent
Vladimir Yanover - BreezeCOM
Menzo Wentink - Intersil
Joint Proposal group
Sunghyun Choi, Philips Research

2. Joint Proposal activities
September 2000
Joint Proposal activities
The Joint Proposal group has been active to further refine the proposal, and generate the associated standard text.
Have worked with other parties to incorporate their ideas into the proposal.
BreezeCOM
Intersil
Joint Proposal group

3. September 2000
Joint Proposal R1
Joint proposal document 120R1 is issued containing the following changes.
Consistency and editorial changes to original document.
Modifications to incorporate the essential elements of the BreezeCOM proposal
Modifications to incorporate a number of elements of the NWN/doc 204 proposal.
Joint Proposal group

4. September 2000
Changes Overview
Added notification mechanism and notification threshold parameters for feedback to higher layers about state of provided QoS service.
Allow 802.1D user priority and/or IETF traffic class values to be used in lieu of VSIDs in cases where connectionless, prioritized differentiation of up to 7 priorities is sufficient and QoS contracts or other connection mechanism are not needed at the MAC sublayer.
Improve effectiveness of power save at stations with active virtual streams through control of receiver on-time by listen epoch rather than the senders' TXOPs.
Intention to add an aggregation mechanism that permits multiple MPDUs to be sent with a single instance of PHY overhead, with details to be presented at the November meeting.
Clarify the reference model and remove the SBM-specific provisions.
Joint Proposal group

5. September 2000
Next steps
The expanded Joint Proposal group is willing to incorporate DCF mechanisms and connectionless PCF mechanisms into their proposal to come to a baseline proposal.
Like to get this started this week to come to a consensus document by the November meeting.
In addition we want to work together with other parties to incorporate their idea’s when it makes sense.
Joint Proposal group

6. Followup presentations
September 2000
Followup presentations
Document 307b from BreezeCOM
Document 307c from Intersil
Integrated document will be 307r1 put on the server later today.
Joint Proposal group

7. New Features in Joint Proposal 00/120r1
September 2000
New Features in Joint Proposal 00/120r1
Naftali Chayat Breezecom
Vladimir Yanover
Joint Proposal group

8. Paradigm of Communication between Upper Layers and MAC
September 2000
Paradigm of Communication between Upper Layers and MAC
Joint Proposal group

9. September 2000
QoS Parameters Set
The QoS Parameter Set element contains the set of parameters necessary to describe the demanded transport characteristics for MSDUs belonging to the specified virtual stream
It is addressed to the TAME at the EPC and the transmission control entities at the ESTA
Joint Proposal group

10. QoS Parameters Set– Cont.
September 2000
QoS Parameters Set– Cont.
Parameters to Identify the Element and the VS
Element ID
Length
VS ID
VS Source
VS Destination
VS Info
Type
Ack Policy = {Normal | Delayed | No Ack}
Joint Proposal group

11. QoS Parameter Set– Cont.
September 2000
QoS Parameter Set– Cont.
General Info Parameters
VS Info
Type = {1 if periodic traffic pattern | 0 }
Ack Policy = {Normal | Delayed | No Ack}
FEC Info – Header FEC & Payload FEC details
Privacy Info placeholder to identify e.g. sec. algorithm applicability to the VS
Joint Proposal group

12. QoS Parameter Set– Cont.
September 2000
QoS Parameter Set– Cont.
Traffic Control Parameters
Parameter Bit Map { 1s for applicable parameters }
Parameter records follow:
Value
Priority = relative priority for handling this parameter within the set of the parameters assigned to the VS
Direction of a change triggering notification = {lower value | higher value | both}
Notification Threshold for a change that triggers the notification
Joint Proposal group

13. QoS Parameter Set– Cont.
September 2000
QoS Parameter Set– Cont.
Traffic Control Parameters
Tx Interval [specific Periodic demand only] / Committed Time [for others]
MSDU Size [Periodic demand only]
Retry Delay Bound
Poll Delay Bound
Latency & Jitter bounds
Minimum Data Rate
Joint Proposal group

14. QoS Parameter Set– Cont.
September 2000
QoS Parameter Set– Cont.
Mean Data Rate
Max Burst Size
Loss Rate Bound
Joint Proposal group

15. Aggregation of the MPDUs into a Single PSDU
September 2000
Aggregation of the MPDUs into a Single PSDU
Motivation: to decrease PHY / PLCP overhead = IFS + Preamble + PLCP Header
The MPDUs are inserted as MAC Header + Body(if present) + FCS
Joint Proposal group

16. Bilthoven, The Netherlands
September 2000
Traffic Classes
Menzo Wentink
Intersil
Bilthoven, The Netherlands
Joint Proposal group

17. The Traffic Class (TC) Mode
September 2000
The Traffic Class (TC) Mode
Besides internal VSID’s, the Joint proposal now also supports Traffic Classes (TC’s).
Traffic Classes (TC’s) are 3 bit numeric traffic labels, as defined in 802.1q.
8 classes are available for upstream traffic, per station
TC labels are passed down by higher layers or by 802.1D tags
TC’s can be used for a priorities or a flow based scheme, where flow based has maximum of 7 QOS flows per station,
Support for more than 7 QoS flows per station requires flow aggregation or VSID’s. This is a policy decision.
Joint Proposal group

18. September 2000
The TC Mode (2)
Classification and TC labeling are performed at higher layers
No Frame Classification Entity (FCE) required inside station
No management messages needed to convey filter specs to the station
Several TC mappings currently exist
Default 802.1D/Intserv mapping (BE=0, CL=3, GS=5, NC=7)
Explicit flow mapping through SBM and RSVP
Diffserv DSCP mapping
More information in document 00/204
Joint Proposal group

19. September 2000
The TC Mode (3)
TC’s are the preferred interface for a DCF based channel access mechanism
DCF based QoS enhanced channel access mechanisms are priorities based by nature
The QoS capabilities (TC or VSID) are station based
Indicated in the capability information field
Potentially more capabilities when other modes (DCF) are added
Joint Proposal group

20. Tying TC’s into the VSID scheme
September 2000
Tying TC’s into the VSID scheme
TC’s are local to a station, but concatenating with the AID gives a unique traffic ID within the BSS
TC.AID is similar to the VSID
TC.AID is in fact a station specific VSID
The uniqueness is required for signalling messages used in the proposal (i.e. CC, RR)
The VSID range now splits into four sub-ranges
Traffic Class range
VSID upstream range
VSID downstream range
VSID sidestream range
Joint Proposal group

21. New VSID Numbering Scheme
September 2000
New VSID Numbering Scheme 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
AID
Traffic Class
VSID for upstream (VS from ESTA to EAP)
VSID for downstream(VS from EAP to ESTA)
VSID for sidestream (VS from ESTA to ESTA in same QBSS)
Joint Proposal group

22. September 2000
Joint Proposal group