Presentation is loading. Please wait.

Presentation is loading. Please wait.

September 2002 Ophir, Texas InstrumentsSlide 1 doc.: IEEE 802.11-02/623r0a Submission Forward Compatibility Hooks for 802.11h Part Two Lior Ophir Texas.

Similar presentations


Presentation on theme: "September 2002 Ophir, Texas InstrumentsSlide 1 doc.: IEEE 802.11-02/623r0a Submission Forward Compatibility Hooks for 802.11h Part Two Lior Ophir Texas."— Presentation transcript:

1 September 2002 Ophir, Texas InstrumentsSlide 1 doc.: IEEE 802.11-02/623r0a Submission Forward Compatibility Hooks for 802.11h Part Two Lior Ophir Texas Instruments Incorporated 8 Hasadnaot St. Herzlia, Israel +972-9-970-6444 lior.ophir@ti.com

2 September 2002 Ophir, Texas InstrumentsSlide 2 doc.: IEEE 802.11-02/623r0a Submission Purpose of 802.11h Section 1.2: “Defines mechanisms for dynamic frequency selection (DFS) and transmit power control (TPC) that may be used to satisfy regulatory requirements for operation in the 5GHz band in Europe” But… –Section 11.5 for TPC: “The procedures may also satisfy comparable needs in other regulatory domains and other frequency bands and may be useful for other purposes, such as interference reduction, range control and power consumption reduction” –Section 11.6 for DFS: “The procedures may also satisfy comparable needs in other regulatory domains and frequency bands and may be useful for other purposes” But (2)… –Some definitions are currently very specific to the 5GHz band in Europe and will be difficult to extend

3 September 2002 Ophir, Texas InstrumentsSlide 3 doc.: IEEE 802.11-02/623r0a Submission Motivation 1.Provide forward compatibility hooks within 802.11h so that the same mechanisms can be used (with minor changes/additions) for other regulatory domains, other bands, other purposes. 2. Do not define how these hooks are to be used This is out of the TGh PAR If/When - this will be defined in a future TG

4 September 2002 Ophir, Texas InstrumentsSlide 4 doc.: IEEE 802.11-02/623r0a Submission What was done? 1.Went over the latest 802.11h draft 2.Identified issues/formats that might need to be used/extended in the future for other domains/bands/purposes 3.Came up with proposed hooks that would allow forward compatibility 4.Did not include proposals of how these hooks are to be used

5 September 2002 Ophir, Texas InstrumentsSlide 5 doc.: IEEE 802.11-02/623r0a Submission Identified issues/formats 1.Channel numbers Currently only channel numbers in 5GHz band Might want to change format to allow other bands Refers to: Supported channels element, Channel switch announcement element, Basic/CCA/RPI Histogram request/report 2.Basic report (Map subfield) Only 3 reserved bits left in Map subfield Might want to reserve more bits for future indications 3.Others?

6 September 2002 Ophir, Texas InstrumentsSlide 6 doc.: IEEE 802.11-02/623r0a Submission Channel Numbers Supported channels element Currently 26 bytes used to map 200 channels in 5GHz band

7 September 2002 Ophir, Texas InstrumentsSlide 7 doc.: IEEE 802.11-02/623r0a Submission Channel Numbers Supported channels element Add “Band Field” (1 octet) indicating the band which the supported channels field refers to Only the value “5” is allowed for this field (indicating the 5GHz band) All other values are reserved

8 September 2002 Ophir, Texas InstrumentsSlide 8 doc.: IEEE 802.11-02/623r0a Submission Channel Numbers Channel switch announcement element Currently 1 octet used for New channel number field Theoretically may indicate only 256 channels (used for 200 channels in the 5GHz band)

9 September 2002 Ophir, Texas InstrumentsSlide 9 doc.: IEEE 802.11-02/623r0a Submission Channel Numbers Channel switch announcement element Add “New Band” Field (1 octet) indicating the band which the New channel number field refers to Only the value “5” is allowed for this field (indicating the 5GHz band) All other values are reserved

10 September 2002 Ophir, Texas InstrumentsSlide 10 doc.: IEEE 802.11-02/623r0a Submission Channel Numbers Basic request Currently 1 octet used for Channel number field Theoretically may indicate only 256 channels (used for 200 channels in the 5GHz band)

11 September 2002 Ophir, Texas InstrumentsSlide 11 doc.: IEEE 802.11-02/623r0a Submission Channel Numbers Basic request Add “Band” Field (1 octet) indicating the band which the Channel number field refers to Only the value “5” is allowed for this field (indicating the 5GHz band) All other values are reserved

12 September 2002 Ophir, Texas InstrumentsSlide 12 doc.: IEEE 802.11-02/623r0a Submission Channel Numbers CCA request Currently 1 octet used for Channel number field Theoretically may indicate only 256 channels (used for 200 channels in the 5GHz band)

13 September 2002 Ophir, Texas InstrumentsSlide 13 doc.: IEEE 802.11-02/623r0a Submission Channel Numbers CCA request Add “Band” Field (1 octet) indicating the band which the Channel number field refers to Only the value “5” is allowed for this field (indicating the 5GHz band) All other values are reserved

14 September 2002 Ophir, Texas InstrumentsSlide 14 doc.: IEEE 802.11-02/623r0a Submission Channel Numbers RPI Histogram request Currently 1 octet used for Channel number field Theoretically may indicate only 256 channels (used for 200 channels in the 5GHz band)

15 September 2002 Ophir, Texas InstrumentsSlide 15 doc.: IEEE 802.11-02/623r0a Submission Channel Numbers RPI Histogram request Add “Band” Field (1 octet) indicating the band which the Channel number field refers to Only the value “5” is allowed for this field (indicating the 5GHz band) All other values are reserved

16 September 2002 Ophir, Texas InstrumentsSlide 16 doc.: IEEE 802.11-02/623r0a Submission Channel Numbers Basic response Currently 1 octet used for Channel number field Theoretically may indicate only 256 channels (used for 200 channels in the 5GHz band)

17 September 2002 Ophir, Texas InstrumentsSlide 17 doc.: IEEE 802.11-02/623r0a Submission Channel Numbers Basic response Add “Band” Field (1 octet) indicating the band which the Channel number field refers to Only the value “5” is allowed for this field (indicating the 5GHz band) All other values are reserved

18 September 2002 Ophir, Texas InstrumentsSlide 18 doc.: IEEE 802.11-02/623r0a Submission Channel Numbers CCA response Currently 1 octet used for Channel number field Theoretically may indicate only 256 channels (used for 200 channels in the 5GHz band)

19 September 2002 Ophir, Texas InstrumentsSlide 19 doc.: IEEE 802.11-02/623r0a Submission Channel Numbers CCA response Add “Band” Field (1 octet) indicating the band which the Channel number field refers to Only the value “5” is allowed for this field (indicating the 5GHz band) All other values are reserved

20 September 2002 Ophir, Texas InstrumentsSlide 20 doc.: IEEE 802.11-02/623r0a Submission Channel Numbers RPI Histogram response Currently 1 octet used for Channel number field Theoretically may indicate only 256 channels (used for 200 channels in the 5GHz band)

21 September 2002 Ophir, Texas InstrumentsSlide 21 doc.: IEEE 802.11-02/623r0a Submission Channel Numbers RPI Histogram response Add “Band” Field (1 octet) indicating the band which the Channel number field refers to Only the value “5” is allowed for this field (indicating the 5GHz band) All other values are reserved

22 September 2002 Ophir, Texas InstrumentsSlide 22 doc.: IEEE 802.11-02/623r0a Submission Basic report (Map field) Current definition 5 bits used for indications (BSS, OFDM preamble, Unidentified, Radar, Unmeasured) Only 3 bits left for future indications

23 September 2002 Ophir, Texas InstrumentsSlide 23 doc.: IEEE 802.11-02/623r0a Submission Basic report (Map field) Forward compatible proposal Add one more byte in map field All bits in the new byte are reserved

24 September 2002 Ophir, Texas InstrumentsSlide 24 doc.: IEEE 802.11-02/623r0a Submission Summary TGh is defining new powerful mechanisms Some mechanisms are currently defined in a specific format for the 5GHz band in Europe In order to allow these mechanisms to be extended to other regulatory domains, other frequency bands, other purposes… Insert today forward compatibility hooks that will be used tomorrow instead of redefining these mechanisms tomorrow …So on to the Motion…

25 September 2002 Ophir, Texas InstrumentsSlide 25 doc.: IEEE 802.11-02/623r0a Submission Motion Move to incorporate the forward compatibility hooks per slides 6-23 in the 802.11h draft to support future extensions for other regulatory domains, other frequency bands and other purposes


Download ppt "September 2002 Ophir, Texas InstrumentsSlide 1 doc.: IEEE 802.11-02/623r0a Submission Forward Compatibility Hooks for 802.11h Part Two Lior Ophir Texas."

Similar presentations


Ads by Google