doc IEEE 802 11 04xxxr 0 5 9

doc. : IEEE 802. 11 -04/xxxr 0 5. 9 GHz WIRELESS ACCESS IN VEHICULAR ENVIRONMENTS / DEDICATED SHORT RANGE COMMUNICATION (5. 9 WAVE / DSRC) CONCEPT UPDATE July 2004 Submission 1 A Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 5. 9 WAVE / DSRC CONCEPT 5. 9 GHz WAVE / DSRC (Dedicated Short Range Communications) is a short to medium range communications service that supports both Public Safety and Private operations in roadside-to-vehicle and vehicle-to-vehicle communication environments. 5. 9 WAVE / DSRC is meant to be a complement to cellular communications by providing very high data transfer rates in circumstances where minimizing latency in the communication link and isolating relatively small communication zones are important. Submission 2 A Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 5. 9 WAVE / DSRC ENVIRONMENT Submission 3 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 5. 9 GHz DSRC BAND PLAN Shared Public Safety/Private Med Rng Service Short Rng Service Control Power Limit Dedicated Public Safety High Avail Intersections 44. 8 d. Bm Power Limit 40 d. Bm 33 d. Bm Power Limit 23 d. Bm Uplink Downlink Submission Frequency (GHz) Canadian Special License Zones* 4 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher 5. 925 5. 920 5. 915 5. 910 Public Safety/ Intersections Private Ch 182 Ch 184 5. 905 5. 900 Public Safety/ Private Ch 180 5. 895 5. 890 Control Channel Ch 178 5. 885 5. 880 Public Safety/ Private Ch 176 5. 875 5. 870 5. 860 5. 855 5. 850 5. 845 5. 840 5. 835 5. 830 5. 825 Ch 172 Public Safety/ Private Ch 174 5. 865 Public Safety

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 5. 9 WAVE / DSRC USAGE REQUIREMENTS • INTEROPERABILITY of UNITS from DIFFERENT MANUFACTURES • PUBLIC SAFETY and PRIVATE APPLICATIONS SHARE UTILIZATION of the 5. 9 GHz BAND • PUBLIC SAFETY MESSAGES HAVE PRIORITY • 100 ms or less ACCESS TIME to Safety Messages • CONTROL CHANNEL MUST NOT FAIL UNDER CONGESTED CONDITIONS • HIGH TRANSFER RATE EFFICIENCY DURING HIGH SPEED MOBILE DATA TRANSACTIONS Submission 5 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 5. 9 WAVE / DSRC USAGE REQUIREMENTS (continued) • WAVE-SPECIFIC APPLICATION SUPPORT • NON-WAVE SPECIFIC APPLICATION SUPPORT • GENERAL PURPOSE INTERNET (GPI) APPLICATION SUPPORT • PRIVATE and SECURE OPERATION • RSUs CONTROL LICENSED CHANNELS IN THE DESIGNATED COMMUNICATIONS ZONE • OBUs TRANSFER SAFETY DATA ON WIDE AREA CHANNELS WITH ONLY THE CSMA MECHANISM RESTRICTION Submission 6 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 5. 9 WAVE / DSRC USAGE REQUIREMENTS (continued) • Receipt of Vehicle Safety Messages must not be interrupted for extended periods of time. Extended periods of time probably means somewhere between 100 and 500 ms or more • Some transactions will take more than 100 ms to complete and we want to maximize the efficiency of channel usage • The Car companies want the ability to implement Vehicle Safety Messages and the Cooperative Collision Avoidance Application with a one channel radio Submission 7 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 PUBLIC SAFETY Messages Have Priority • Management Frames have a higher priority than any priority of data frame. Beacon Frames have the highest priority but only one level. Levels of Priority must be added to Action Frames. • High Priority Public Safety Broadcast Messages are sent in Wave Service Information elements in Beacon Frames from RSUs or Action Management Frames from OBUs. • Quality of Service Data Frames have priority levels that allow further delineation of priority among applications • Private Application Messages are sent in Action Frames on the Control Channel and Quality of Service Data Frames in Service Channels Submission 8 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 Updated WAVE Architecture OBU SNMP agent (RFC 1157) SNMP MIB App 3 App 2 App 1 UDP (RFC 768) UDP Networking Services (IPv 6 – RFC 2460) Networking Services SME (802. 11) Logical Link Control (802. 2) WME (802. 11 p/1609. 3) Channelization (1609. 4) Channelizer (1609. 4) Submission IVN MLME (802. 11 p) MAC (802. 11 p/ ASTM E 2213) PLME (802. 11 p) PHY (802. 11 p/ ASTM E 2213) IVN L 2/L 1 Notes: 1. Each device may have a single SNMP manager servicing multiple applications. 2. Role of 1609. 1 & 1609. 2 needs further discussion. For now, the applications are shown in a general context to focus on the lower layers. 9 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 Possible 5. 9 WAVE Control and Service Channel Implementation Options • Short Public Safety Messages may be included as elements in Beacon and Action Frames to be Broadcast on the Control Channel • High Priority messages may be Broadcast on all the service channels • Extended Public Safety Message exchanges may occur with Unicast data frames on Service channels • Private Application Messages may be Broadcast in Action Frames on the Control Channel with strict interval and size limits (as listed on a following slide) • Private Application Messages may be Broadcast or Unicast on a selected service channel • Private Application Message exchanges occur with unicast data frames on Service channels Submission 10 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 Control Channel Rules Frequency (GHz) Submission 11 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher 5. 925 5. 910 5. 905 5. 900 5. 895 5. 890 5. 885 Unicast (RSU only ) - Action Frame (Safety - NO limits) - Action Frame (Private subject to limits) 5. 880 2. 5. 875 Broadcast - Beacon Frame (RSUs only) - Action Frame (Safety - NO limits) - Action Frame (Private Messages - subject to limits shown on the following slide) 5. 920 Dedicated Public Safety High Avail Intersections 1. 5. 870 5. 865 5. 860 5. 855 5. 850 5. 845 5. 840 5. 835 5. 830 5. 825 Shared Public Safety/Private Med Rng Service Short Rng Service Control

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 Service Channel Rules Frequency (GHz) Submission 12 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher 5. 925 5. 910 5. 905 5. 900 5. 895 5. 890 Unicast - Data Frame - All Other Frames 5. 885 2. 5. 880 Broadcast - Beacon Frame (RSUs only) - Action Frame (Safety NO limits) - Data Frame - All other frames 5. 920 Dedicated Public Safety High Avail Intersections 1. 5. 875 5. 870 5. 865 5. 860 5. 855 5. 850 5. 845 5. 840 5. 835 5. 830 5. 825 Shared Public Safety/Private Med Rng Service Short Rng Service Control

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 ACTION FRAME CONTROL CHANNEL USAGE LIMITS Below is a table that defines the limits of Control Channel usage for private applications using broadcast or unicast action frame transmissions. 1. For Private Applications: RSUs Maximum Data Transmission Duration: 750 usec Minimum Interval between Data Transmissions: 100 msec* OBUs 580 usec 750 msec *20 msec Minimum Transmissions Intervals are allowed in low power (20 d. Bm EIRP) operations. 2. Applications are not allowed to respond on the Control Channel to announcements of RSU or OBU Application Services. Submission 13 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 DEFINITIONS WAVE Beacon: • A WAVE beacon is composed of a WAVE Service Information Element added to the IEEE 802. 11 beacon. • The WAVE Service Information Element is composed of a Provider Service Table (PST), a WAVE Routing Advertisement (optional), a Safety Message (optional), and Authentication elements. Submission 14 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 DEFINITIONS WAVE Action Frame: • A WAVE action frame contains the WAVE Service Information Element • The WAVE Service Information Element is composed of a Provider Service Table (PST), a WAVE Routing Advertisement (optional), a Safety Message (optional), and Authentication elements. Submission 15 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 DEFINITIONS Provider Service Table: • A set of data that identifies applications being offered • Identification of the hosting device • Characteristics of the media to be used (including the Service Channel) Submission 16 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 DEFINITIONS User Service Table: • 1. Dynamically generated in response to a PST • 2. Identifies applications and device parameters for a communications session Submission 17 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 Broadcast Scenarios • Case 1. OBU receives a broadcast message in a management frame on the Control Channel or a Service Channel • a. If a broadcast message is contained in a management frame , the MAC passes it to the MLME. The MLME passes it on to the WME for processing where it is verified as being from a trusted source by the trailing authentication. • b. If authenticated the WME routes the message to the appropriate application as indicated in the message header. Submission 18 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 Broadcast Scenarios OBU receives a broadcast message in a data frame on a service channel • Case 2. • a. If it is verified as being for an application authorized to accept broadcast messages on the service channel it is passed up the stack for processing in the layers above the MAC Submission 19 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 Broadcast Scenarios • Case 1. OBU receives a broadcast message requesting a response in a management frame on the Control Channel or a Service Channel • a. If a broadcast message is contained in a management frame , the MAC passes it to the MLME. The MLME passes it on to the WME for processing where it is verified as being from a trusted source by the trailing authentication. • b. If authenticated and if there is a service or services in the PST that has been registered with the OBU for implementation the OBU will create a UST, create and adopt the appropriate WAVE interface IP address, switch to the service channel and sets up the correct power and priority level and notify or open the appropriate application(s). • c. Once the OBU finishes the above setup procedures it will send the UST to the RSU. Submission 20 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 Unicast Scenarios • Case 1. OBU receives a unicast message in a action frame on the Control Channel • a. The OBU will NOT respond - except with an ack - to a unicast message in a data frame Submission 21 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 Unicast Scenarios • Case 2. OBU receives a unicast message in a data frame on the Service Channel • After it is verified as being for a port (application) authorized to accept messages on the service channel it is passed up the stack for processing in the layers above the MAC Submission 22 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 Management System Overview Submission 23 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 Notification Handler and Traps • Utility on OBU and RSU • Listens for SNMP Traps from SNMP Agent • Alerts appropriate application to be executed • SNMP may send Trap to both Notification handler and SNMP Manager • Enterprise Specific Traps – E. g. STMatch, OBUIn. Range, OBUOut. Of. Range Submission 24 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 Notification Handler and Traps Example E. g. CALM system or Roadside Infrastructure UDP Broadcast gateway (IPv 4 or IPv 6) Mgmt IPv 6 Data IPv 6 Channelizer WME MAC MLME PLME Submission 25 PHY Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 Broadcast UDP Gateway (Scenario 1 a) • UDP interface for broadcasts on the Control Channel – Broadcast Service Information elements in an (Action Frame) – Application ID (AID) registered along with UDP port and IP address used on IVN Submission 26 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 Broadcast UDP Gateway (cont’d) To UDP port 7001 Application Host Ethernet Application Host DIC Prototype To UDP port 7441 AID & BSI element constructed in action frame Submission DIC Prototype 27 To UDP port 7321 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 Wave Link Initialization (Scenario 1 b) • Enterprise specific SNMP traps must be defined for application initialization – E. g. STMatch – Used to indicate application availability to notification handler • Notification handler launches the application • Application looks up the IPv 6 profile in the WME MIB – Stored by the WME for retrieval by the application when a ST match occurs – Destination IPv 6 address and destination port number of the application Submission 28 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 Wave Link Initialization and Exchange Example MAC broadcast beacon frame sent on Control Channel Application Initialization… RSU indicates switch to service channel UDP datagram (MAC unicast) send on Service Channel Source (UDP port selected by OBU): 2001: 400: 420: E 212: 45 FF: FE 04: ABC 0 Destination (UDP port 365): 2001: 420: 400: : 150 Global IPv 6 2001: 400: 420: E 212: 45 FF: FE 04: ABC 0 UDP datagram (MAC unicast) send on Service Channel Source (UPD port 365): RSU switches to service channel RSU routes datagram to Global IPv 6 2001: 420: 400: : 150 Application Response RSU routes datagram from Global IPv 6 2001: 420: 400: : 150 Destination (UDP port of OBU): 2001: 400: 420: E 212: 45 FF: FE 04: ABC 0 Submission 29 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 Wave Link Initialization and Exchange Example Diagram WME Submission 30 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 Channelization Overview • Generalized Approach – One set of prioritized queues for each channel – A simplementation may support only one service channel at a time (single set of prioritized queues) Submission 31 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 Queue Routing Triggers • Channelization function uses IPv 6 destination address – Based on destination MAC if unicast – Based on IPv 6 Prefix (and Subnet ID) if broadcast • May need multicast address trigger • May need multicast group address designation in PST – Second radio required if more than one service channel used per RSU • Unique MAC per radio (can use “virtual radios” – multiple MAC per PHY) • Unique IPv 6 prefix Submission 32 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 Example Channelization Flow RSU OBU 1 Beacon Frame (PST, WRA) WME Optional Application notification 4 3 Optional Action Frame (UST) Configure channel queue based on WRA and source MAC Queue Router Rx Path UDP/IP 5 datagram Channelization & MAC Submission 3 QR SCH Tx Queue Rx Path Application initialization based on PST(app IP, UDP port) Application SCH Tx Queue UDP/IP datagram 2 UDP/IP Application 4 QR WME Channelization & MAC 33 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 Network Infrastructure Overview Submission 34 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 Address Assignment • • • Assign link-local and global addresses – Site local addresses to be obsoleted by next IPv 6 RFC Global addresses used for both WAVE and GPI applications Options for global prefixes: Network Prefix (64 -bit) 2001: 420: 400: : /64 Interface ID (64 -bit) : : 11 : : 12 : : 13 : : 14. : : 15 Submission 35 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 Address Assignment (cont’d) • Option for using Subnets Network Prefix (48 -bit) 2001: 420: 400: : /48 Subnet ID (16 -bit) : : 36 Interface ID (64 -bit) : : 11 : : 12 : : 13 Subnet 1 : : 14 : : 11 : : 37 : : 12 Subnet 2 : : 13 : : 14 Submission 36 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 WAVE Address Discovery • WAVE Router Advertisement (WRA) contains – Prefix, DNS Server, Default Gateway • Global address generated from Prefix in WRA – Need to double check default gateway (may only need MAC address – see standard router advertisement) – Assumes duplicate detection handled by MAC layer (per VSCC random MAC generation) Submission 37 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 Address Assignment (RSUs on same subnet) NOTE: should be single colon after 2001 in IPv 6 addresses Submission 38 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 GPI Application Flow (UDP) UDP data transfer 2001: 420: 400: : XXX UDP data transfer 2001: 420: 400: XXX Submission 39 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 GPI Application Flow (TCP) Submission 40 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 Channel Switching Approach • Leverage 802. 11 h and the TSF – The TSF provides an accurate timing mechanism – Channelization is greatly simplified using this approach • If the current channel matches the queue set for that channel, the queue is served until the channel changes • Timers no longer required by channelization function – Control Channel Interval & Service Channel Interval • Controlled by RSU beacon frames CCH Interval SCH Interval Beacon Frame Data or other management Busy Medium Switch to SCH Submission Switch back to CCH 41 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 Channel Switching Approach (cont’d) • Vehicle to Vehicle sync options – 1. No sync when not in the presence of an RSU – 2. Use distributed beaconing for sync – Channel switching supported by 802. 11 h action frames in this case • E. g. V 2 V communications session can switch to high availability V 2 V channel under special circumstances Submission 42 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 Initial Proposed Inputs to 802. 11 p • Updates to IEEE 802. 11 baseline document • Based on ASTM E 2213 – 03 Submission 43 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 1 doc. : IEEE 802. 11 -04/xxxr 0 RSU Communicating With an OBU Submission 44 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 2 doc. : IEEE 802. 11 -04/xxxr 0 Basic Service Sets With RSUs and OBUs Submission 45 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 Fig 3 Submission doc. : IEEE 802. 11 -04/xxxr 0 Independent Basic Service Sets With OBUs Only 46 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 FIG. 4 Submission doc. : IEEE 802. 11 -04/xxxr 0 Connecting OBUs to Wide. Area Networks 47 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 Fig 5. Submission doc. : IEEE 802. 11 -04/xxxr 0 Connecting an OBU to an In-vehicle Network 48 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 BSS Connects Onboard Computer Through the WAN to the ITS Application Fig 6 Submission 49 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 FIG. 11 OFDM PHY Frequency Channel Plan for North America Submission 50 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 TABLE 6 Submission doc. : IEEE 802. 11 -04/xxxr 0 Major Parameters of the OFDM PHY 51 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 TABLE 7 Submission doc. : IEEE 802. 11 -04/xxxr 0 Regulatory Requirement List 52 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 TABLE 8 Valid Operating Channel numbers by Regulatory Domain and Band Submission 53 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 TABLE 9 doc. : IEEE 802. 11 -04/xxxr 0 5. 9 WAVE/DSRC Device Classes and Transmit Power Levels Submission 54 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 Table 10 doc. : IEEE 802. 11 -04/xxxr 0 WAVE Transmitter Power Limits for Public Safety Submission 55 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 Table 11 Submission doc. : IEEE 802. 11 -04/xxxr 0 WAVE Transmitter Power Limits for Private Usage 56 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 TABLE 12 Submission doc. : IEEE 802. 11 -04/xxxr 0 5. 9 WAVE/DSRC Spectrum Mask 57 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 FIG. 12 Submission doc. : IEEE 802. 11 -04/xxxr 0 Class A Transmit Spectrum Mask 58 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 FIG. 13 Submission doc. : IEEE 802. 11 -04/xxxr 0 Class B Transmit Spectrum Mask 59 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 FIG. 14 Submission doc. : IEEE 802. 11 -04/xxxr 0 Class C Transmit Spectrum Mask 60 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 FIG. 15 Submission doc. : IEEE 802. 11 -04/xxxr 0 Class D Transmit Spectrum Mask 61 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 TABLE 13 Submission doc. : IEEE 802. 11 -04/xxxr 0 Allowed Relative Constellation Error Versus Data Rate 62 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 TABLE 14 Submission doc. : IEEE 802. 11 -04/xxxr 0 Type 1 Receiver Performance Requirements 63 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 TABLE 15 Submission doc. : IEEE 802. 11 -04/xxxr 0 Type 2 Receiver Performance Requirements 64 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 TABLE 17 Submission doc. : IEEE 802. 11 -04/xxxr 0 OFDM PHY Characteristics 65 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 TABLE 18 Submission doc. : IEEE 802. 11 -04/xxxr 0 List of Parameters for the PMD Primitives 66 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 Table 0. 1 Submission doc. : IEEE 802. 11 -04/xxxr 0 User priority to Access Category mappings 67 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 WAVE Service Information Elements (WSIE) Submission 68 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 WAVE Action Frame Formats Cate gory Submission Action n Conten Code t 69 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 Category Value associated with a WAVE Action Frame Format Submission 70 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 WAVE Action Code for WSI Submission 71 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 MLME-START. request( SSID, BSSType, Beacon. Period, DTIMPeriod, CF parameter set, PHY parameter set, IBSS parameter set, Probe. Delay, Capability. Information, BSSBasic. Rate. Set, Operational. Rate. Set, WSI 1, WSI 2, WSE 3, WSE 4, WSEn ) Type Valid Range Description As defined in WAVE Service information elements Reports Wave Service Information Name WSI Submission 72 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 MLME-WAVE. request WSI 1, WSI 2, WSE 3, WSE 4, WSEn, Peer MAC address ) ( Type Valid Range Description WSI As defined in WAVE Service information elements Reports Wave Service Information Peer MAC address Any valid address Name Submission The address of the peer MAC entity to which a WAVE action shall be set. 73 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 MLME-WAVE. confirm Result. Code ) Submission ( Name Type Valid Range Description Result. Code Enumeration SUCCESS, INVALID PARAMETERS Reports the result of the WAVE request. 74 Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher

July 2004 doc. : IEEE 802. 11 -04/xxxr 0 MLME-WAVE. indication ( WSI, RSSI, Peer MAC address ) Type Valid Range Description WSI As defined in WAVE Service information elements Reports Wave Service Information RSSI Integer tbd RSSI value in d. Bm Source MAC address Any valid address Name Submission 75 The address of the MAC entity from which the WSI was received. Broady Cash, Justin Mc. New, Doug Kavner, Wayne Fisher