Presentation is loading. Please wait.

Presentation is loading. Please wait.

Project Planning Committee Closing Report IEEE 802.16 Presentation Submission Template (Rev. 9) Document Number: IEEE C802.16ppc-10/0082 Date Submitted:

Similar presentations


Presentation on theme: "Project Planning Committee Closing Report IEEE 802.16 Presentation Submission Template (Rev. 9) Document Number: IEEE C802.16ppc-10/0082 Date Submitted:"— Presentation transcript:

1 Project Planning Committee Closing Report IEEE 802.16 Presentation Submission Template (Rev. 9) Document Number: IEEE C802.16ppc-10/0082 Date Submitted: 2011-01-10 Source: Rakesh Taori E-mail: Rakesh.Taori@samsung.com Samsung Electronics Venue: The Grand Hotel, Taipei, Taiwan Base Contribution: None Purpose: Project Planning WG Closing Plenary: Output of the week Notice: This document does not represent the agreed views of the IEEE 802.16 Working Group or any of its subgroups. It represents only the views of the participants listed in the “Source(s)” field above. It is offered as a basis for discussion. It is not binding on the contributor(s), who reserve(s) the right to add, amend or withdraw material contained herein. Release: The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE 802.16. Patent Policy: The contributor is familiar with the IEEE-SA Patent Policy and Procedures: and.http://standards.ieee.org/guides/bylaws/sect6-7.html#6http://standards.ieee.org/guides/opman/sect6.html#6.3 Further information is located at and.http://standards.ieee.org/board/pat/pat-material.htmlhttp://standards.ieee.org/board/pat

2 212/22/2015 Project Planning Session this week Timeslots this week: –1 st Session: Wednesday, 1pm – 5:30pm (V109) –2 nd session: Thursday, 3:30 pm – 5:30 pm (V107) Objectives for the week 1.Revision Project Discuss the submitted contributions Discuss a possible proposal for the WG 2.Enhancements to 16e Discuss the submitted contributions (2 contributions) 3.Hierarchical Network Study Report : Discuss the submitted contributions (9 contributions) Take a stab at relevant PAR Sections (Scope and Purpose)

3 312/22/2015 1. Revision related discussion Option 1: Regular approach –Based on Contribution #39 –Consolidation of 16j, 16h and 16m. –Can be done. Procedurally clear. Option 2: A 2-book approach –What 2-book approach essentially means is: Needs 2 PARs. (Possible in parallel) A PAR to create a standard specifying only the Advanced Air interface Another PAR to create a standard consisting everything else (of 16-2009, 16j and 16h amendments (including the amendments to these resulting from the16m amendment)) The Ongoing TGs (16p, 16n) need to submit PAR changes (if they amend the two standards mentioned above, they will need to submit two PARs.) –There is no standard template to split a standard. Not trivial to craft it as a revision PAR. –Need a sub-identifier for each standard (e.g. 802.16.1,.2, …) –Neither of those is a revision PAR. Option 3: Common MAC in a single section –Followed by a split into 16e, 16m and so on… –Some misunderstandings related to “Common MAC” were clarified and this proposal was dropped. Consensus: Option 2

4 412/22/2015 2. 16e Enhancement proposals 2 contributions (#79 and 80) addressed this topic. Only one was presented (#79). –Contribution #80 was more-or-less identical to #79. So it was skipped. The proponent wanted a straw poll. Straw Poll –Are you interested in addressing improvements to WirelessMAN OFDMA? Interested: 7 Not interested: 9

5 512/22/2015 3. Contributions on Hierarchical Network Study Report Discussed all the contributions. An ad-hoc was created to harmonize the inputs. Adopted 008r3 as the “updated” hierarchical network study report (by consensus). The study report contains: –Single RAT Interference mitigation (no text), Client cooperation, Effective Spectrum Utilization –Multi-RAT Enhanced Interworking, Multi-RAT Client Cooperation, Unlicensed Spectrum Usage, Security (almost unexplored) Plan going forward –Created an ad-hoc group (Lead: Inuk Jung). –The goal of the ad-hoc is to Discuss the issues that could not be agreed upon in Session #71 (MIH, C-AP, O-RAT). Bring a harmonized proposal back to the PPC Discuss the scope (as shown in previous slide) and consider/sub-select what is worth following-up. Bring a proposal to the PPC. –Conf Calls 17th Feb, 6 pm PST, 90 minutes 24th Feb, 6 pm PST, 90 minutes (if needed. TBD at the end of the first call) 3rd Mar, 6 pm PST, 90 minutes

6 612/22/2015 Real-Time Minutes (non-binding)

7 712/22/2015 Agenda Contributions related to Revision –37 Contributions related to 16e enhancements –#79, 80 Contributions related to Hierarchical Networks –#70 through #78 AoB

8 812/22/2015 Comments on Contribution #39 As many amendments in 3 years after 2009. Not forced to do a revision earlier than that. Consolidation may take some time/effort –Analysis of Figures/Tables/Clauses (possible overlap identification etc.) ongoing –IEEE editors to provide a base document (consolidated). That could be a starting point. –WG chair asks the IEEE to trigger the consolidation work. 30-day deadline does not apply to Maint projects. –48-hour notices suffice for Main PARs. The group decided to look at the alternatives

9 912/22/2015 Alternatives (How to approach the Revision) Regular approach as suggested in Contribution #39 –Consolidation of 16j, 16h and 16m. –Can be done. Procedurally clear. If we go this way, we need to but perhaps now may be a good time to see if better alternatives are possible. 2 book approach –Needs 2 PARs. (Possible in parallel) –There is no standard template to split a standard. Not trivial to craft it as a revision PAR. –Need a sub-identifier for each standard (e.g. 802.16.1,.2, …) –Neither of those is a revision PAR What 2-book approach essentially means is that we need to submit two PARs: –A PAR to create a standard specifying only the Advanced Air interface –Another PAR to create a standard consisting everything else (of 16-2009, 16j and 16h amendments (including the amendments to these resulting from the16m amendment)) –Both the PARs can be submitted in parallel. –The Ongoing TGs (16p, 16n) need to submit PAR changes (if they amend the two standards metioned above, they will need to submit two PARs.) 3 rd Approach: Common MAC in a single section –Followed by a split into 16e, 16m and so on… –Some misunderstandings related to “Common MAC” were clarified and this proposal was dropped.

10 1012/22/2015 Other Comments related to Revision/Maintanance Possibility to update annually –Can be clothed as Amendment or Revision –Annual update as a maint issue (would be trivial) –Putting major amendments would be more complex –Annually or Bi-annually? –The discussion was aborted. Weneed to have more concrete thoughts.

11 1112/22/2015 Conclusion There was a consensus on following the “two book” approach. Further action: –PAR discussion proposals are invited for realizing the two-book approach.

12 1212/22/2015 16e Enhancement proposals 2 contributions (#79 and 80) addressed this topic. Only one was presented (#79). –Contribution #80 was more-or-less identical to #79. So it was skipped. The proponent wanted a straw poll. Straw Poll –Are you interested in addressing improvements to WirelessMAN OFDMA? Interested: 7 Not interested: 9

13 1312/22/2015 Discussion on HN-related contributions Contribution #70 –Discussion Is MIH an example of GLL? Or do you wish to replace GLL with MIH –Replace GLL by MIH. –Use MIH as an example. We can use MIH, ORAT, C-AP, … –Tightly coupled architecture would not need MIH per se If we use tightly coupled approach, do we still need the new layer (GLL)? Contribution #71 Discussion Replace GLL with MIH What would be the focus of this group then? Improve MIH? –802.1 considers multi-RAT functionality (including multi-radio cooperation) Interworking WiMAX-Wi-Fi alsodefined in WMF. What is the relation with MIH? –MIH is included in the spec. The general concept of inter-MAC communication is defined in 802.1

14 1412/22/2015 Discussion on HN-related contributions Contribution #72 –Addition of ND&S to the requirements –Clean up –MIH for interworking Contribution #73 –Adding ND&S to standards implication –Making aware of the MIH option.

15 1512/22/2015 Discussion on HN-related contributions Contribution #74 –Summary Enhanced spectrum utilization across multiple -tiers Enhanced interference management techniques enabling maximal spectral reuse across tiers (e.g. Femto/Macro-tiers) or Multi-RATs Seamless mobility of connection flows among Multi-RATs (e.g. data offloading, handover) Enhanced interworking with other RAT (e.g. IEEE802.11). Simultaneous use of spectrum across multiple RATs. Multi-RAT device collaboration Contribution #75 –Summary –Editorial clean up and grammar fixing (some additional fixes for clarification?)

16 1612/22/2015 Discussion on Options for Way forward with HN Update the Study report –Ad-hoc to harmonize which ones to adopt in the updated report. Discuss how to eventually develop the PAR –Scope and Purpose –Recommendation #1 Prepare the topics of your interest and share. Discuss the topics (create an ad-hoc which can work in the morning) Consensus: The group wanted to do some work in this meeting to update the study report

17 1712/22/2015 Ad-hoc for harmonizing the Inputs All the authors + interested people get together, harmonize and come back by Thursday afternoon with a proposal what should get in to the HN study report (008r2) as an update (Based on the 9 contributions that we have). –Ad-hoc lead: Inuk Jung In the scheduled PPC session on Thu afternoon, propose to adopt the harmonized changes (adoption pending consent of the PPC) and update the study report Later (not a part of the ad-hoc): Consider assigning a group to work on narrowing the scope by the next meeting.

18 1812/22/2015 Adoption of the ad-hoc output –Adopt 008r3 as the hierarchical network study report Editorial instructions: –Remove the items highlighted in yellow from the ad-hoc output report. –Replace “GLL” in Figures 7 and 8 with “?” Plan for the coming weeks (before the March meeting)

19 1912/22/2015 Issues Currently in the Report Single RAT –Interference mitigation (no text) –Client cooperation –Effective Spectrum Utilization Multi-RAT –Enhanced Interworking Unresolved issue: Coordinated CA-P GLL vs. MIH –Multi-RAT Client Cooperation –Unlicensed Spectrum Usage –Security (almost unexplored)

20 2012/22/2015 Ad-hoc to discuss –Issues that could not be agreed upon in Session #71 (MIH, C-AP, O- RAT) –Discuss the scope (as shown in previous slide) and consider/sub-select what is worth following-up. –Ad-hoc lead: Inuk Jung Conf Calls –17 th Feb, 6 pm PST, 90 minutes –24 th Feb, 6 pm PST, 90 minutes (if needed. TBD at the end of the first call) –3 rd Mar, 6 pm PST, 90 minutes


Download ppt "Project Planning Committee Closing Report IEEE 802.16 Presentation Submission Template (Rev. 9) Document Number: IEEE C802.16ppc-10/0082 Date Submitted:"

Similar presentations


Ads by Google