malarky16093_4items-JTMppt空話16093_4項(xiàng)目jtmppt.ppt

1、1609.3/4 Items,Malarky/Moring for 1609 WG Meeting Feb 2 2010,Issues Rx handled by 802.11 Must address throughout 1609.3 where request processing,2. 1609.4 Scope etc,Dick: “The scope of this standard is to define services and functionality in the data link layer, and more specifically in the MAC subl

2、ayer, to support multi-channel wireless connectivity among devices using the 5.9 GHz MAC Rx handled by 802.11,7. Availability of Vendor Specific Info,Add ability of external management entities to append Vendor Specific data (VSIE) to general 802.11 management frames Supported by solution described

3、under #1,8. Comment 1609.4/Malarky-29,Comment: the requirement A WAVE device that is not synchronized to UTC shall not transmit Timing Advertisement frames is overly restrictive and in-appropriate Solution: A WAVE device that is not synchronized to UTC shall not transmit Timing Advertisement frames

4、to the broadcast MAC address. The achieves the objective of protecting from flooding while allowing query-response timing for, e.g., security synchronization,Original Presentation Follows,Access to 802.11 Frames,To date it has been assumed that higher layers and extensions to 1609 (.3 or .4) can inv

5、oke other 802.11 frames to provide additional functions beyond those specified in 1609.3 or add in functionality that the application can define to the WME what channels it is eligible to transmit on.,Management ID vs Organization Identity in MLMEX-VSA,The reason we need to create a set of MLMEX pri

6、mitives for VSAs is because we need to pass additional information beyond that used by the 802.11 primitive for VSAs: Repeat Rate Channel Identifier Channel Interval Note Repeat Rate and Channel Interval are really for convenience in creating repeats. The only real driving reason is because we have

7、to define the channel. The VSA frame contains the Organization Identifier (defined by 802.11p) In the MLMEX-VSA.request and Vendor Specific Content The 1609.4 implementation is required to create the 1609.x Organization Identifier in the subsequent frame(s).,Management ID vs Organization Identity in

8、 MLMEX-VSA,Because of this definition we appear to limit the use of the MLMEX-VSA primitives to only 1609 entities. However this also means that any higher level management entities operating with 1609 must define their own MAC extension because they too will need to add Channel Identifier and trans

9、mit power I recommend that the MLMEX-VSA primitives be modified to pass Organization Identifier instead of Management ID.,Availability of Vendor Specific Info,For WME-RCPIRequest and WME-RCPIReport, we provide no means to pass a VSIE in the frame, despite this being supported by 802.11 in MLME-MREQUEST. Whether or not we have defined functi