Doc.: IEEE 802.11-08/1248r1 Submission Nov 2008 Adrian Stephens, Intel CorporationSlide 1 802.11 Nov...

IEEE 802.21 MEDIA INDEPENDENT HANDOVER DCN: 21-08-0266-00-0000 Title: 802.21-Enabled Handovers in IMT-AdvancedDate Submitted: September, 2008Presented at IEEE 802.21 session #28 in KonaAuthors or Source(s):Les Eastwood (Motorola)Vivek Gupta (Intel)Abstract: 802.21-enabled Handovers for IMT-Advanced

IEEE 802.21 presentation release statementsThis document has been prepared to assist the IEEE 802.21 Working Group. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein.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 IEEEs name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEEs 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.21.The contributor is familiar with IEEE patent policy, as outlined in Section 6.3 of the IEEE-SA Standards Board Operations Manual and in Understanding Patent Issues During IEEE Standards Development http://standards.ieee.org/board/pat/guide.html>

IEEE 802.21 presentation release statementsThis document has been prepared to assist the IEEE 802.21 Working Group. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein.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 IEEEs name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEEs 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.21.The contributor is familiar with IEEE patent policy, as stated in Section 6 of the IEEE-SA Standards Board bylaws and in Understanding Patent Issues During IEEE Standards Development http://standards.ieee.org/board/pat/faq.pdf>

IMT-A/802.11/802.21 Meeting Goals Sep-08

BackgroundIMT-A 802.11 solution requires use of 802.16Also allows 802.11 to be compliant with 802.16 solution802.16 not sure about close connection with 802.11 in its IMT-A solution802.16 would consider 802.21 as a media independent handover mechanism for non-802.16 technologiesGoalsWhat options should be favored by 802.21?Can 802.21 provide handover features for IMT.TECH?

Bruce Kraemer (Marvell)

Outline

Overview of 802.21

IMT-Advanced Vision/Goals

How 802.21enables 802.11 to meet IMT-Advanced Requirements

And how it will enhance the 802.16 proposal for IMT-Advanced

Summary

IEEE 802.21: Overview

802.21 provides Vertical H/o solution across IEEE Technologies

802.21 History & Timeline

1H 2004

2H 2004

802.21 WG Created

Call For Proposals

1H 2005

14 Initial Proposals

2H 2005

1H 2006

Down selection Initial 802.21 Draft Text

2H 2006

Initiate Amendments to 802.11u, 802.16g. IETF (MIPSHOP) on L3

Year 2007

Sponsor Ballot

Year 2008

802.21 Spec Ratified*

2009-2010

802.21 Deployment*

WG Letter Ballot

*Projected Timelines

Two New Study Groups (July 2007) Security in Handovers Multi-Radio Power Management

ITU-Rs Vision for IMT-Advanced (4G)

For 4G, the International Telecommunications Union-Radio Sector (ITU-R) sees a need for new wireless access technology. The new technology must support data rates much higher than IMT-2000s (or 3Gs) 30Mbps maximum. Motivation: deliver wireless services competitive with broadband wireline.ITU-Rs vision for new IMT-Advanced concept: 100 Mbps for highly mobile access (at speeds of up to 250 km/hr)1 Gbit/s for low mobility (pedestrian speeds or fixed) access.

ITU-Rs IMT-Advanced Vision

IEEE 802s Responses to IMT-A Vision; 802.21s Roles

IEEE 802 extending both IEEE 802.11 and 802.16 for IMT-AdvIEEE 802.16s new 802.16m spec: highly mobile (250km/hr.), high data rate (100Mbps), extension of 802.16 IEEE 802.11 Very High Throughput (VHT) up to 1Gbps, at stationary or pedestrian speedsTogether, 802.16m and 802.11 VHT satisfy the ITU visionIEEE 802.21 adds mobility between 802.11VHT and 802.16m, and creates a single, integrated system for IMT-AdvancedTies the two radio systems together into one Improves 802.16m proposal Enables 802.11 proposal Possible basis of a dual-radio proposal (SRIT)Capable of smooth handovers required in IMT.TECH

Handovers in a Dual-Radio (e.g. 802.16m/802.11VHT) IMT-Advanced System

HO Challenges; 802.21 Solutions

IEEE 802.11 and 802.16 Drafts Already Incorporate 802.21

IEEE 802.16802.16g amendment incorporates 802.21 enhancements802.21 participants contributing into 802.16m requirementsIEEE 802.11802.11u amendment incorporates 802.21 enhancements

Summary (1)

IMT-Advanced (or 4G) apps require both mobility and 1 Gb/s peak data rateAt least two radio technologies neededProposals for IMT-Advanced are likely to come from both IEEE 802.11 and 802.16IEEE 802.16m for 100 Mb/s high mobility higher data rate fixed adjunct can enhance802.11 VHT for 1 Gb/s at lower mobility needs a mobile adjunct to meet IMT-Adv requirements Implies an added need for technology to integrate dual radios into one system, enabling handoversparticularly for real-time and streaming applications, these handovers should be imperceptible to the user (or seamless).

Summary (2)

IEEE802.21 can provide the glue to enhance 802.16ms proposal and to enable 802.11VHTsby enabling seamless handovers between these two radio systems and for other cellular or IEEE 802 radios

IEEE 802.21 adds unique value by supporting the challenging decision and pre-execution phases of intertechnology handovers, key determinants of latency. 802.21 provides mechanisms to prepare the target network before handover execution occurs, reducing latency

Backupson Handover Options 1 thru 5(Chart #10)

Five Handover Options

Example802.21 Messagingfor Option 2Handover

15) Handover completed and mobile gains full connectivity at the target 802.11VHT network

Candidate Network 1 (802.11VHT)

13) Perform 802.11VHT network entrance procedure with target

14) Restore IP level connectivity (via, for example Mobile IP, etc.)

10) MIH_MN_HO_Commit Response

9) MIH_MN_HO_Commit Request

8) Selected a target

12) Start handover execution - use local MIH commands to activate 802.11VHT and de-activate 802.16m interface

11) Mobile may optionally perform a pre-registration with the target network

7) MIH_MN_HO_Candidate_Query Responses

6) MIH_MN_HO_Candidate_Query Requests

5) Evaluate the suitability of the candidate networks and check resource status

2) Mobile velocity is decreasing; Try to do a handover for higher data throughput.

3) MIH_Get_Information Request

4) MIH_Get_Information Response

1) Mobile in high mobility is connected

to 802.16m

Mobile Node w/ 802.21

802.21 HO Information Database

Candidate Network 2 (802.11VHT)

Serving Network (802.16m)

802.16m

802.11VHT

September 200821-08-0278-00-0000_IMT-Advanced_Discussion-Minutes

IEEE P802Media Independent Handover Services

Tentative Meeting Minutes of the IEEE P802.21 Working Group

Chair: Vivek Gupta

Vice Chair: Subir Das

Secretary: Anthony Chan

(Minute Taker: Y. Cheng in absence of the secretary)

Kings 1, Hilton Waikaloa Villiage, Big Island, Hawaii September 9, 2008

1. IMT-Advanced Discussion (Tuesday PM2 4:00 PM)

1.1. Meeting call to order by Vivek Gupta, Chair of IEEE 802.21 WG at 4:05 PM HST on September 9th, 2008

1.2. IMT-Advanced status from 802.11WG (Bruce Kraemer)

Document: https://mentor.ieee.org/802.11/file/08/11-08-0940-01-0imt-imt-advanced-opening-report-sep-08.ppt

Brief description of IMT-Advanced schedule and its meeting report. Initial meeting was in March 2008 at Dubai. The coming meeting will be in Oct 2008 at Korea.

A workshop is scheduled on Oct 7 prior to the official meeting for positioning the circular letter and presenting some candidate technologies. Based on information from Roger Marks, 802.16 will be presenting in the workshop as one of the candidate technologies.

There will be a slide for WG16 to include WG21 as handover for WG11. The activity is to provide an enhanced feature for WG16 when presenting as a candidate for RIT.

The scoring of the candidate radio is based on the ITU standards.

The WG11 will bring the discussion result to November 2008 meeting and provide a decision on a go-or no go in pursuing work in IMT-Advance.

Discussion:

In WG11, there are 240 voters and about 15 voters showed up for IMT-Advanced related topics. The amount of participation in IMT-Advance from WG11 is not determined yet. This question will be asked in the November meeting.

What are the specific requirements from circular letter?

Slide 27 includes the requirements that are related to WG21. More details can be found in the circular letter. WG21 does not have a response to how the numbers can be satisfied.

Slide 23 has the requirements for bandwidth. An RIT candidate needs to meet at least one test environment. For the official RIT, it requires at least 3 test environments. The opinion of Bruce is that IEEE 802.16m can satisfy the requirements in slide 23.

1.3. 802.21 enabling IMT-Advanced (Les Eastwood)

Document: https://mentor.ieee.org/802.21/file/08/21-08-0266-00-0000-802-21-in-imt-advanced.ppt

802.21 provide services to reduce false handovers due to roaming/capability/requirements.

The Layer 2 trigger and measurements are for facilitating/initiating a handover. The triggers allow the network selection entity to react on network changes. For example, The MAC/PHY can send specific event such as signal low locally or to the network in order to initiate network handovers. The L2 trigger has corresponding liaisons to other media.

The Commands are for initiating the network information.

IEEE 802.21 does not concern IP connectivity, it is for the IETF.

FMCA has a work item to use 802.21 for session continuity and 802.1 for AAA.

Details of the options defined in slide 10 are provided in the backup slides. As 802.21 concerns, it supports all of the options.

The actual measurements results depend on the scenario.

Comments:

.21 doesnt have ability to detect the PHY. How the information is maintain and collected is not in the specification, but provided to the specific technology for determine the result. There is common format for sorting the information and retrieving it in the same matter.

Security support:

IETF MIPSHOP group is working on layer 3 transport with security mechanisms. The ANDSF is comparing to the MIH+MIPSHOP.

ANDSF is an information repository to push information of the operator policy and network information to the user terminal for both 3GPP and non-3GPP network.

There is a corresponding paper published in the IEEE Communications magazine.

1.4. IMT-Advanced status from 802.18 WG (Mike Lynch)

IEEE 802.18 looked into what needs to be prepared for submission. The WG will provide answers to the template from IMT-Advanced.

The first week of October 2009 is the due date for submission. The submission includes additional 3rd party evaluation. IEEE approves at plenary is July 2009. IMT-Advanced schedule does not line up with IEEE 802 meetings. The EC needs to be convinced and the final approval date will be in September 2009 unless there is a special ad hoc meeting. Delegate the process to 802.18.

The document will be in the 802.18 website tomorrow morning. John is the author. Thursday PM1 will approve the document.

Discussion:

Each WG will fill in the results in the template; 802.18 will manage the workflow and not judging the results.

1.5. Response to questions from 802.11 WG

Document: https://mentor.ieee.org/802.11/file/08/11-08-0940-01-0imt-imt-advanced-opening-report-sep-08.ppt

Question #1 (slide 9)

802.21 supports media independent handover, the internal behavior between the different terminals types are defined by the specific media. 802.21 is able to handle all terminal types.

The mesh network has not been looked into details though conceptually it should be applicable. Since mesh network communication is hop-by-hop, handover concept may not be applicable. Handover uses an access point. IMT-Advanced specification describes only base station and client relationship.

The nomadic portion is 11WG focused. 802.11 can service only the in-door test environment. The next use case is in a micro-urban area; the amount of coverage is currently under debate. However, there are other challenges are more daunting. 11WG is not using the ITU spectrum identified for RIT. The VOIP requirement in ITU is way beyond what .11WG can do.

Maybe 21WG can propose an SRIT that includes the 11WG and 16WG. The ITU identifies the unlicensed spectrum but not allocate the license. The ITU manages no spectrum, but provides an administration to minimize the overlapping of the usage of spectrums.

Can .11 handover within .11 satisfy the handover requirements specified by ITU? The specification is written as MUST meet the requirement. However, if the terminal is in the sleep mode, probably not. The ITU requirement is for average delay time rather than never to exceed the specified time.

When there is a make before break or turning on/off the radio for measuring the handover time. The specification does not specify the precondition way for handover.

Session continuity is the theme, so mainly is to determine if the session continuity is provided.

Question #2 (slide 10)

Time will tell if 802.21 specification is mature enough to be used. The Mipshop addresses security concerns for MIH in L3. The 802.11 also have security access. For 3GPP there is also specification addresses.

(Stephen McCann) TGu havent look into ANDSF however it is possible to look into that in the future. TGu does not specify handover mechanisms; it provides the interface for the handover from 802.21 to 802.11. TGu provides a transport for 802.21. TGu contains additional interworking within certain aspect with 3GPP. However, it is not as comprehensive as the 802.21 information server. There is a lot missing to use TGu directly for handover to 802.16. That is, TGu relies on the 802.21 specification for providing the proper handover.

This discussion started with only .16m and .11, but if there are additional mechanisms to handover to other RIT, it will be great.

The combination of 802.16m, 802.11 and 802.21 is not literally an SRIT since no ITU spectrum is used.

There is nothing tie the VHT timeline with the IMT-advance. There are mechanisms added for the use case, but not directly addressed in the VHT PAR.

Vivek: The minutes will be posted in the entire corresponding working group; if there is any other additional works required we will continue discussion in November meeting.

Bruce: We may want to continue a joint .16 and .11 meeting in the November meeting.

1.6. Recess at 6PM.

2. Attendance

2.1. 802.21 WG

Last Name

First Name

Affiliation

Canchi

Radhakrishna

Kyocera

Chaplin

Clint

Imagicon

Cheng

Yuu

Telcordia Technologies

Cho

Il

National Information Society Agency (NIA)

Das

Subir

Telcordia Technologies Inc.

Eastwood

Lester

Motorola, Inc.

Gloger

Reinhard

Nokia Siemens Networks

Henderson

Gregory

Research In Motion Limited

Khatibi

Farrokh

Qualcomm Incorporated

Mccann

Stephen

Siemens AG Global

Ohba

Yoshihiro

Toshiba America Research, Inc.

Salminen

Reijo

seesta ltd

Sarikaya

Behcet

Huawei Technologies Co., Ltd.

Singh

Shubhranshu

Samsung Electronics

Song

Myung

National Information Society Agency

Taff

Louis

Ericsson

Williams

Michael

Nokia Corporation

Zuniga

Juan Carlos

InterDigital Communications, LLC

PAGE

4

IEEE 802.21 WG Meeting Minutes

doc.: IEEE 802.11-08/1248r1Submission

WG18 Exchangesfrom slide 5 of IEEE 802.11-08/1429r0 by Bruce Kraemer (Marvell); Darwin Engwer (Nortel)

Adrian Stephens, Intel Corporation

IEEE 802.18-08-0056-02-0000

Submission

Slide *

ITU-R Regulatory Background

Date: 2008-09-11

Authors:

Michael Lynch, Nortel Networks

Name

Company

Address

Phone

email

Mike Lynch

Nortel Networks

Richardson, TX

972.684.7518

[email protected]

doc.: IEEE 802.18-08-0056-00-0000

Submission

ITU-R Regulatory Background


doc.: IEEE 802.18-08-0056-00-0000

Submission

The ITU-R Overview

The ITU is a special agency of the United Nations which deals with international telecommunications matters.The ITU-R is the sector of the ITU responsible for addressing radiocommunications matters, issuing recommendations, and making regulations.All decisions made in the ITU-R are made by agreement of Member States (MS), which acting together hold the final authority.


doc.: IEEE 802.18-08-0056-00-0000

Submission

The ITU-R mission

The ITU Radiocommunication Sector (ITU-R) plays a vital role in the global management of the radio-frequency spectrum and satellite orbits - limited natural resources which are increasingly in demand from a large and growing number of services such as fixed, mobile, broadcasting, amateur, space research, emergency telecommunications, meteorology, global positioning systems, environmental monitoring and communication services - that ensure safety of life on land, at sea and in the skies.Our primary objective is to ensure interference free operations of radiocommunication systems. This is ensured through implementation of the Radio Regulations and Regional Agreements, and the efficient and timely update of these instruments through the processes of the World and Regional Radiocommununication Conferences. Furthermore, radio standardization establishes Recommendations intended to assure the necessary performance and quality in operating radiocommunication systems. It also seeks ways and means to conserve spectrum and ensure flexibility for future expansion and new technological developments.


doc.: IEEE 802.18-08-0056-00-0000

Submission

The ITU-R Regulatory Process

The intent of this presentation is to explain the ITU-R regulatory processSpectrum identified for IMT has been selected as an example but this applies to other applications that have specific spectrum identified in the Radio Regulations (RR)


doc.: IEEE 802.18-08-0056-00-0000

Submission

In the beginning

At WARC-92, WRC-00 and WRC-07 Member States (MS) identified spectrum for a new concept in mobile technologyFPLMTS, now called IMT-2000, has progressed to IMT-Advanced.Some MS wanted an allocation others identificationBoth relate to regulating spectrumThe identification had support from Sector Members (SM) and the private sector but was a MS decisionIEEE SA is a Sector Member


doc.: IEEE 802.18-08-0056-00-0000

Submission

Then

Concurrent with having identified spectrum for what is now IMT, the MS began a process to identify radio air interface requirements for systems that would use the spectrum for IMT applicationsThe system requirements have been developed over a 20+ year period in the ITU-R IMT groupMS approve Recommendations and reportsWork, technical or regulatory, is done by experts from MS, SM and the private sector their end documents are studied and agreed by MS


doc.: IEEE 802.18-08-0056-00-0000

Submission

The next step

Having developed the requirements the MS set about the technology selection processRadio air interfaces were required to meet the system requirementsThe judgment that they met the requirements, and inclusion in an ITU-R Recommendation, was an action of the MSSM and private sector experts participated in the work the final approval decisions were made by the MS


doc.: IEEE 802.18-08-0056-00-0000

Submission

MS expectations

The end goal of the MS in identifying and regulating spectrum and radio air interface technologies for IMT is to improve their economies and the well being of their citizensThat goal is a MS sovereign right and obligationSM and the private sector also benefited


doc.: IEEE 802.18-08-0056-00-0000

Submission

So today..

The current process is focused on identifying new technologies for IMTIt is simply a continuation of the process the MS sanctioned and approved when work on FPLMTS beganThe inclusion of any technology into M.1457 carries with it the acceptance of the MS that the technology meets the goals for which the spectrum was identified


doc.: IEEE 802.18-08-0056-00-0000

Submission

The result is

This is all regulatory in nature since the goal of the MS is that the identified spectrum, a resource of each sovereign MS, is used to the best advantage of that State.It started with FPLMTS, we are now at IMT-Advanced nothing has changed in the ITU-R processAnything that impacts the access to spectrum identified for IMT includes a regulatory aspectThe MS are the ones that regulate the use of that spectrum


doc.: IEEE 802.18-08-0056-00-0000

Submission

For more on the ITU-R

http://www.itu.int/ITU-R/index.asp?category=information&rlink=rhome&lang=en

http://www.itu.int/ITU-R/index.asp?category=information&rlink=itur-welcome&lang=en


doc.: IEEE 802.11-yy/xxxxr0

Month Year

John Doe, Some Company

Page *

IEEE 802.18-08-0058/r6

Submission

November 2008

John Notor, Cadence Design Systems, Inc.

Slide *

IEEE 802.18 IMT-Advanced Review Process

Date: 2008-11-11

Authors:


Name

Company

Address

Phone

email

John Notor

Cadence Design Systems, Inc.

San Jose, CA

408.473.8373

[email protected]

Frank Whetten

Boeing

Seattle, WA

206.852.8914

[email protected]

IEEE 802.18-08-0058/r6

Submission

November 2008


Slide *

The IMT-Advanced process in ITU-R has advanced to the point where:The technical requirements (IMT.TECH) are completed and approved.The evaluation criteria and methodology document (IMT.EVAL) is completed and approved.The Circular Letter, 5/LCCE/2, has been released, along with one addendum, inviting submission of technology proposals and participation in the evaluation process. Final adoption of IMT-Advanced reports was achieved at the November 2008 ITU-R SG 5 meeting.Interested IEEE 802 WGs now need to consider how to respond to IMT-Advanced.Submit a Radio Interface Technology proposal (RIT) as a single WG.Submit a proposal for a Set of Radio Interface Technologies (SRIT) jointly with one or more other WGs.The EC Chair has tasked 802.18 to review and recommend approval of technology proposals to the EC for submission to the ITU-R IMT-Advanced process.

Background


IEEE 802.18-08-0058/r6

Submission

IMT-Advanced Schedule

November 2008


Rich Kennedy, OakTree Wireless

IEEE 802.18-08-0058/r6

Submission

November 2008


Slide *

A single Working Group (WG), or a joint WG collaboration, creates and approves a draft RIT proposal, or a draft SRIT proposal, conforming to IMT-Advanced submission requirements.The proposal is then sent to 802.18, which reviews the proposal for completeness (see slide 5) per IMT-Advanced submission requirements. After review, 802.18 will determine by vote, requiring 75% approval of the voters present (excluding abstentions), whether the proposal is considered complete per IMT-Advanced submission requirements, and either submit the approved proposal, or return the proposal to the WG for update with incomplete items identified.After approval, the IEEE SA ITU-R liaison will submit the proposal to the ITU-R with appropriate cover letter.Proposals returned to IEEE by the ITU-R as incomplete will be sent back to the WG(s) by the IEEE SA ITU-R liaison for correction, and the corrected proposal will be re-submitted to ITU-R per the process outlined above.

IEEE 802 Approval Process for IMT-Advanced Final Technology Proposals


IEEE 802.18-08-0058/r6

Submission

November 2008


Slide *

A complete proposal, as specified in the current version of IMT.REST, Requirements, evaluation criteria and submission templates for the development of IMT-Advanced, is summarized as follows:Completed templates and other requested information.Either a self-evaluation, or the endorsement of an initial evaluation submitted by another entity, per IMT-Advanced requirements for self-evaluation.Where necessary, a statement of compliance with the ITU policy on intellectual property rights (see Annex 1 of Resolution ITU-R 1-5), as specified in the Common Patent Policy for ITU-T/ITU-R/ISO/IEC available at http://www.itu.int/ITUT/dbase/patent/patent-policy.html.The definition of complete is subject to change by ITU-R.The most current versions of the requirements, evaluation criteria, and submission templates for the development of IMTAdvanced are on the IMT-Advanced web page (http://www.itu.int/ITU-R/go/rsg5-imt-advanced/).

ITU-R Definition of Completeness for IMT-Advanced Technology Proposals


IEEE 802.18-08-0058/r6

Submission

November 2008


Slide *

802.18 does not wish to impair the ability of WGs to submit fully formed and reviewed technical proposals to the ITU-R IMT-Advanced process in a timely fashion. Therefore, 802.18 recommends that the EC delegate the IMT-Advanced approval process to 802.18, making approval by 802.18 sufficient for submission to ITU-R WP 5D. If necessary, the EC could take additional action to approve proposals that could not be completed in the 802.18 process specified here.Last date for WGs to submit technology proposals (WG approved drafts) to 802.18 for review: September 4, 2009.September 21-25: Review proposals during 802.18 session. Proposals could be revised, with the consent of the submitting WG or its delegation.Last date for 802.18 approval of proposals for submission to the ITU-R: September 25, 2009.Last date WP5D will accept technology proposals: October 7, 2009.

Critical Milestones


IEEE 802.18-08-0058/r6

Submission

Critical Milestones

November 2008


Slide *


IEEE 802.18-08-0058/r6

Submission

November 2008


Slide *

In order to prepare for the work load of IMT-Advanced proposal reviews, 802.18 requires advance information regarding the intentions and work plans of participating WGs.

In particular, 802.18 requires that participating WGs provide notification of their intent by January 20, 2009. The notification must include:

Statement of intention to submit IMT-Advanced proposal for 802.18 reviewIntended proposal scope (for example: RIT and/or SRIT; test environments to be supported; standards or draft standards to be used as a foundation)Work plan for completion of required proposal elements

Statement of Intent from Participating WGs


IEEE 802.18-08-0058/r6

Submission

November 2008


Slide *

WGs may want to provide information to WP 5D at its meetings of February and June. 802.18 will support such contributions, provided that they are clearly identified as not complete proposals per Step 3 of the IMT-Advanced process. Timelines for submission of informative contributions:Jan 20: Deadline for WG draft contributions to February WP 5D meetingInformation on intent, background, work plan, etc.Jan 22: 802.18 approval of contributions to February WP 5D meetingFeb 3: ITU-R deadline for contributions to Feb WP 5D meeting

May 12: Deadline for WG draft contributions to June WP 5D meetingWork plan update, additional information on features, etc.May 14: 802.18 approval of contributions to June WP 5D meetingJune 3: ITU-R deadline for contributions to June WP 5D meeting

Contributions to February and June 2009 WP 5D Meetings




Month Year


Page *




Month Year


Page *




Month Year


Page *




Month Year


Page *




Month Year


Page *




Month Year


Page *




Month Year


Page *



Seoul Korea Workshop slide from slide 6 of IEEE 802.11-08/1429r0 by Bruce Kraemer (Marvell); Darwin Engwer (Nortel)



Connection Status.16.11.21CompleteRequires completion of TGufrom slide 7 of IEEE 802.11-08/1429r0 by Bruce Kraemer (Marvell); Darwin Engwer (Nortel)



Ongoing WG11 Obligations for IMTVia 18Create, review, approve WG11 relevant documents to ITU-R WP5DE.g. M.1801 RADIO INTERFACE STANDARDS FOR BROADBAND WIRELESS ACCESS SYSTEMS, INCLUDING MOBILE AND NOMADIC APPLICATIONS, IN THE MOBILE SERVICE OPERATING BELOW 6 GHzM.1450-3 Characteristics of Broadband Local Area Networks

Participate in Circular letter review process (e.g. 18-08-0058 r5)from slide 8 of IEEE 802.11-08/1429r0 by Bruce Kraemer (Marvell); Darwin Engwer (Nortel)



IMT-A Activities ProposalAgree that WG11 will make no IMT-A RIT submission to WP5D. Agree that supporting other IEEE 802 WG IMT-A RIT submissions is beneficialAgree that the MIH approach is the most beneficial activity for WG11 to complete (slide 10).Agree that WG11 Assist WG21 and TGu , as appropriate, to expedite closure of any open items needed for Item #3.Continue to maintain dialog with, and respond to requests from, other WGs

from slide 9 of IEEE 802.11-08/1429r0 by Bruce Kraemer (Marvell); Darwin Engwer (Nortel)



Project ProposalDisband ad hoc Rely WG chair and WG 21 liaison reports for status information

from slide 10 of IEEE 802.11-08/1429r0 by Bruce Kraemer (Marvell); Darwin Engwer (Nortel)



JTC1 Ad Hoc November ClosingDate: 2008-11-13Authors:from slide 1 of IEEE 802.11-08/1427r0 by Jesse Walker, Intel Corporation


Name

Company

Address

Phone

email

Jesse Walker

Intel Corporation

2111 N.E. 25th Ave, Hillsboro, OR USA

+1-503-712-1849

[email protected]


AbstractThis presentation contains the IEEE 802.11 JTC1 Ad Hoc closing report for November 2008.from slide 2 of IEEE 802.11-08/1427r0 by Jesse Walker, Intel Corporation



AccomplishmentsReviewed outcome of Montreux JTC1/SC6 meetingDiscussed options and next stepsDecision: Respond to Liaison letter from SC6 in January meeting, and consider other actions as appropriatefrom slide 3 of IEEE 802.11-08/1427r0 by Jesse Walker, Intel Corporation



January Meeting PlanningObjectivesPrepare response to SC6 Liaison letterSchedule other actions which would support the needs of WLAN customers and users in the WAPI debatefrom slide 4 of IEEE 802.11-08/1427r0 by Jesse Walker, Intel Corporation


doc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0July 2007Terry Cole (AMD)Page *Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0July 2007Terry Cole (AMD)Page *Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0July 2007Terry Cole (AMD)Page *Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0July 2007Terry Cole (AMD)Page *Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0July 2007Terry Cole (AMD)Page *Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0July 2007Terry Cole (AMD)Page *Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0July 2007Terry Cole (AMD)Page *Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0July 2007Terry Cole (AMD)Page *Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0July 2007Terry Cole (AMD)Page *Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0July 2007Terry Cole (AMD)Page *Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0September 2007Terry Cole (AMD)Page *Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0July 2007Terry Cole (AMD)Page *Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0July 2007Terry Cole (AMD)Page *Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0doc.: IEEE 802.11-yy/xxxxr0Month YearJohn Doe, Some CompanyPage *Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0doc.: IEEE 802.11-yy/xxxxr0Month YearJohn Doe, Some CompanyPage *Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0doc.: IEEE P802.11-08/1369r2November 2008Donald Eastlake 3rd, MotorolaPage *Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0doc.: IEEE P802.11-08/1369r2November 2008Donald Eastlake 3rd, MotorolaPage *Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0doc.: IEEE P802.11-08/1369r2November 2008Donald Eastlake 3rd, MotorolaPage *Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0doc.: IEEE P802.11-08/1369r2November 2008Donald Eastlake 3rd, MotorolaPage *Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0doc.: IEEE P802.11-08/1369r2November 2008Donald Eastlake 3rd, MotorolaPage *Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0doc.: IEEE P802.11-08/1369r2November 2008Donald Eastlake 3rd, MotorolaPage *Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0doc.: IEEE 802.11-yy/xxxxr0Month YearJohn Doe, Some CompanyPage *Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0doc.: IEEE 802.11-yy/xxxxr0Month YearJohn Doe, Some CompanyPage *Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0doc.: IEEE 802.11-08/1123r0September 2008Alex Ashley, NDS LtdPage *Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0doc.: IEEE 802.11-08/1123r0September 2008Alex Ashley, NDS LtdPage *Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0doc.: IEEE 802.11-08/1123r0September 2008Alex Ashley, NDS LtdPage *doc.: IEEE 802.11-08/918r0July 2008Ganesh Venkatesan, Intel CorporationPage *Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0doc.: IEEE 802.11-08/1123r0September 2008Alex Ashley, NDS LtdPage *doc.: IEEE 802.11-07/2752r1November 2007Peter Ecclesine, Cisco SystemsPage *Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0doc.: IEEE 802.11-08/1123r0September 2008Alex Ashley, NDS LtdPage *Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvelldoc.: IEEE 802.11-06/0528r0Bruce Kraemer, Marvell

Date post:	21-Jan-2016
Category:	Documents
Upload:	laurence-lyons
View:	214 times
Download:	0 times

Doc.: IEEE 802.11-08/1248r1 Submission Nov 2008 Adrian Stephens, Intel CorporationSlide 1 802.11 Nov...

Documents