1 / 6

Preliminary Evaluation of Japan Band Issues

Preliminary Evaluation of Japan Band Issues. Peter Ecclesine, Cisco Systems. Top Level Issues. How to learn AP/Base Station’s capabilities? Multi-band with rules per band, multi-mode Base Stations licensed, other stations not licensed in some bands IBSS prohibited in some bands

reed
Download Presentation

Preliminary Evaluation of Japan Band Issues

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Preliminary Evaluation of Japan Band Issues Peter Ecclesine, Cisco Systems Peter Ecclesine, Cisco Systems

  2. Top Level Issues • How to learn AP/Base Station’s capabilities? • Multi-band with rules per band, multi-mode • Base Stations licensed, other stations not licensed in some bands • IBSS prohibited in some bands • 2.5MHz channelization in 4.9 and 5.0 GHz • How to signify Channel Ids • Carrier sense rules satisfied • PCF maximum duration; fragmentation • Already required for .11, .11b lower rates • Spectral efficiency requirements • met by mandatory 16QAM modes Peter Ecclesine, Cisco Systems

  3. AP/Base Station’s capabilities? • .11 7.2.3.1 Beacon frame format – set dot11MultiDomainCapabilityEnabled • Extend multi-domain definition to multi-band • .11d 7.3.2.15 Probe Request/Probe Response Information Elements 13- • ID, Length, Channel Properties Zero, Channel Properties 1, … • Channel Bandwidth, Licensed BSS, IBSS allowed, Licensed STAs, Alternate Band, First Channel Offset (0.5 MHz) Peter Ecclesine, Cisco Systems

  4. Channel ID techniques • .11a 17.3.8.3.2 Channel center = 5000 + 5 x n [n=0-199] • Could designate [n=239-255] negative to signify 4915-4995 [negative first channel signifies below 5000] • Together with ‘First Channel Offset’ signifies center frequency on 0.5 MHz accuracy (examples on slide5) • .11g 18.4.6.2 Table 105, enumerated by country Peter Ecclesine, Cisco Systems

  5. 4.9 and 5 GHz Channel ID examples • Carrier freq ‘First channel’ ‘Number of chls’ ‘First chl offset’ • 5032.5 6 6 5 • 5035 7 5 0 • 5040 8 3 0 • 5055 11 1 0 • 4997.5 -1 = 255 1 5 • 4995 -1 = 255 1 0 • 4980 -4 = 252 4 0 • 4947.5 -11 = 245 8 5 • 4945 -11 = 245 3 0 • 4925 -15 = 241 3 0 Peter Ecclesine, Cisco Systems

  6. .11a 17.2.2 TXVECTOR parameters 17.2.2.2 DATARATE 17.2.2.4 TXPWR 17.2.3 RXVECTOR parameters 17.2.3.2 RSSI 17.2.3.3 DATARATE 17.3.2.2    RATE-dependent parameters 17.3.2.3    17.3.2.3 Timing-related parameters 17.3.4.1 and Table 80 Data Rate Table 86 Major parameters of the OFDM PHY 17.3.8.2 and Table 87 Regulatory requirements 17.3.8.3.2 Channel numbering 17.3.8.3.3 and Table 88 Channelization 17.3.8.4 Transmit and receive in-band and out-of-band spurious emissions 17.3.9.1.x Transmit power 17.3.9.2 and Figure 120 Transmit spectrum mask 17.3.9.6.3 and Table 90 Transmitter constellation error 17.3.10.1 and Table 91 Receiver performance requirements 17.3.10.5 CCA sensitivity Table 92 MIB attribute default values/ranges Tx Power, Domains supported, Supported data rates Table 96 List of parameters for the PMD primitive Tx Power 17.5.5.5 PMD_TXPWR .11d 7.2.3.1 Beacon frame format dot11MultiDomainCapabilityEnabled Table 20 Element Ids Element 11 7.3.2.12 Country information Element First channel number, Number of channels 9.9 Operation across regulatory domains .11h 3.53 transmit power 5.7.2 Association, 5.7.3 Reassociation Power Capability, Supported Channels 7.2.3.4 Association Request frame format dot11MultiDomainCapabilityEnabled 7.2.3.6 Reassociation Request frame format dot11MultiDomainCapabilityEnabled 7.3.1.7 and Table 18 Reason codes 10, 11 7.3.1.9 and Table 19 Status codes 23 and dot11MultiDomainCapabilityEnabled 10.3.6.1.2 MLME-ASSOCIATE.request Supported channels 10.3.7.1.2 MLME-REASSOCIATE.request Supported channels 10.3.10.1.2 MLME-START.request Country dot11MultiDomainCapabilityEnabled May Be Affected paragraphs and tables Peter Ecclesine, Cisco Systems

More Related