1. doc.: IEEE COEX 02/018r0 Submission May 2002 Jim Lansford, Mobilian CorporationSlide 1 IEEE 802 Wireless Coexistence Study Group Jim Lansford Jim.Lansford@mobilian.com Tim Blaney tim@commcepts.net Sydney Interim Meeting Wednesday Afternoon

2. doc.: IEEE COEX 02/018r0 Submission May 2002 Jim Lansford, Mobilian CorporationSlide 2 Update for Sydney meeting SEC conference calls held between meetings –Refine mission statement –Discussion of goals for anticipated TAG –Definition of Coexistence Goals for Sydney meeting –Broader feedback –Further refinement of mission statement and goals –Finalize mission statement and charter –Proposed definition of coexistence –Start work on organization and voting rules –Prep for Vancouver plenary

3. doc.: IEEE COEX 02/018r0 Submission May 2002 Jim Lansford, Mobilian CorporationSlide 3 Tasks the SG/TAG needs to accomplish  Develop Mission Statement (SG ongoing)  Statement of purpose (Recommend to ExCom how IEEE 802 should address coexistence in existing and future specs) (SG ongoing)  Definition of coexistence (TAG)  Summary of current standards where coexistence is an issue (TAG)  Recommendations to SEC (SG July Plenary)  Summary and report (SG July Plenary)

4. doc.: IEEE COEX 02/018r0 Submission May 2002 Jim Lansford, Mobilian CorporationSlide 4 Mission Statement The IEEE 802 Coexistence Technical Advisory Group (TAG) has the following missions: –The COEX TAG develops and maintains the IEEE 802 policy for establishing coexistence between Standards. – –The COEX TAG evaluates the coexistence issues between IEEE 802 PARs and Draft Standards, and makes recommendations to the IEEE 802 Executive Committee. (Based on feedback from 1 May conference call)

5. doc.: IEEE COEX 02/018r0 Submission May 2002 Jim Lansford, Mobilian CorporationSlide 5 Coexistence Definition Coexistence: The ability of one system to perform a task in a given shared environment where other systems have an ability to perform their tasks and may or may not be using the same set of rules. –Coexistence is quantified by degradation (simulated or measured) under a set of usage model assumptions, which must be defined for coexisting systems

6. doc.: IEEE COEX 02/018r0 Submission May 2002 Jim Lansford, Mobilian CorporationSlide 6 Q&A #1 Will this group try to “quantify” coexistence? –Not likely – coexistence depends on so many variables (geometry, power, etc.) that defining a number that says whether you have achieved it or not isn’t practical. What will this group do then? –We currently don’t have a policy for addressing coexistence; that’s first. This policy will address the ground rules for analyzing the degradation two systems cause to each other (or pairs of systems for multiple standards).

7. doc.: IEEE COEX 02/018r0 Submission May 2002 Jim Lansford, Mobilian CorporationSlide 7 Q&A #2 How would this work? –The TAG first defines policy. For example, the policy might be to say a WG needs to pick five usage models and determine the degradation due to a set of other approved standards, pairwise. We want to examine most likely scenarios, not corner cases, which may give pathological results. So how would you know if two systems “coexist”? –The TAG is an advisory group to SEC; analysis using the usage models would be used by WGs and SEC to make informed decisions. This is a similar concept to the FCC’s OET. So the answer is that the TAG procedures will either convince voters that a Recommended Practice is needed, or that a draft has no coexistence issues and can proceed to further balloting.

8. doc.: IEEE COEX 02/018r0 Submission May 2002 Jim Lansford, Mobilian CorporationSlide 8 Q&A #3 Does the TAG play a role other than formulating policy? –Possibly. The current thinking is that the COEX TAG develops a definition of coexistence and a policy to guide WG’s analysis of coexistence. Beyond that, the TAG may be called upon to help resolve coexistence conflicts by writing an independent report when a draft is submitted to SEC, but this has not been agreed upon. What about participation and voting? –A TAG is governed by the same attendance and voting rules as WG’s, but the specifics are not finalized.

9. doc.: IEEE COEX 02/018r0 Submission May 2002 Jim Lansford, Mobilian CorporationSlide 9 Notes from Monday Minutes: “COEX-02017r0_Coexistence- Meeting-Minutes-Sydney” on Mars Key points: –Desireable to coordinate with ETSI/BRAN –Discussion of “acceptable” degradation –Several ingredients needed in policy: PHY model (first order) MAC model (second order) Upper layers (third order) Usage models are critical, and must be agreed upon between affected WG’s

10. doc.: IEEE COEX 02/018r0 Submission May 2002 Jim Lansford, Mobilian CorporationSlide 10 Proposed Operation (discussion points) The Coexistence TAG is responsible for defining the meaning of coexistence within the IEEE 802 context. The Coexistence TAG will develop the guidelines by which WGs establish whether a given TG coexists. –Uses official definition –Uses usage models –Uses modeling and/or measurements –Recommends creation of a TG to develop a Recommended Practice, if needed (a la 802.15.2) The Coexistence TAG will publish guidelines by which the industry can evaluate coexistence. The Coexistence TAG is responsible for reviewing all proposed wireless PARs –Like FCC/OET, evaluates PARs and highlights those that may require a Recommended Practice –Summary report to be voted on by TAG –Summary report presented to SEC –SEC members take this summary under advisement This TAG is responsible for generating a final review report of the Draft Standard prior to Sponsor Ballot –TAG should begin work when the first WG ballot is published Preliminary report should be issued to SEC within 40 days –Must be voted on by TAG –Must be ratified by SEC –SEC can require creation of a TG to write Recommended Practice