Presentation is loading. Please wait.

Presentation is loading. Please wait.

Doc.: IEEE 802.11-04/604r0 Submission May 2004 Darwin Engwer, Nortel Networks; Lily Yang, Intel Corp.Slide 1 AP Functional Descriptions Update Darwin Engwer,

Similar presentations


Presentation on theme: "Doc.: IEEE 802.11-04/604r0 Submission May 2004 Darwin Engwer, Nortel Networks; Lily Yang, Intel Corp.Slide 1 AP Functional Descriptions Update Darwin Engwer,"— Presentation transcript:

1 doc.: IEEE /604r0 Submission May 2004 Darwin Engwer, Nortel Networks; Lily Yang, Intel Corp.Slide 1 AP Functional Descriptions Update Darwin Engwer, Nortel Networks Lily Yang, Intel Corp.

2 doc.: IEEE /604r0 Submission May 2004 Darwin Engwer, Nortel Networks; Lily Yang, Intel Corp.Slide 2 What To describe the AP architecture and functionality standardized by the current standard and its amendments, or implied by them. The purpose is to provide a better informative description of an AP, to provide: –the basis for interoperability by design (rather than by test), –technical innovation, and –alignment with the work of other groups.

3 doc.: IEEE /604r0 Submission May 2004 Darwin Engwer, Nortel Networks; Lily Yang, Intel Corp.Slide 3 Trends A trend in WG: –from “link view” to “wireless network view” –i.e. from 11e, 11n ==> 11r, 11s, WNM, WIEN Natural evolution for WLAN architectures –From one-box AP with BSS-centric view (“Autonomous Architecture”) –To better coordinated inter-BSS services: “Distributed Architecture”: distributed coordination by peer nodes (example: mesh) “Centralized Architecture”: centralized controller for the network Original AP definitions: interaction with the DS is vague –No interoperability within ESS Need to provide better descriptions of ESS and interoperability within the ESS

4 doc.: IEEE /604r0 Submission May 2004 Darwin Engwer, Nortel Networks; Lily Yang, Intel Corp.Slide 4 Why To provide a formal description of the AP for use by other groups. –802.1X also needed and needs a clean description of the functions and behaviors of an AP. –CAPWAP: The AP functional descriptions can be used by the IETF CAPWAP group. – TGs (ESS Mesh) will extend the functions of an AP to provide for operation in a mesh of APs. This again requires a clear description of the baseline functions of an AP as a starting point. – will be specifying inter-802 mobility (e.g to , and to 802.3), and also 802 to cellular mobility. These efforts also require a core functional description of an AP.

5 doc.: IEEE /604r0 Submission May 2004 Darwin Engwer, Nortel Networks; Lily Yang, Intel Corp.Slide 5 What’s in-scope? –Clear logical decomposition of the AP functionality into some logical units (modules, services, functions, or whatever makes sense) –Clear description of the interaction, relationship or interfaces between these logical units (SAP) What’s out-of-scope? –Physical mapping of these logical units onto physical entities (this implies a specific architecture: belongs to other groups) e.g. Split architectures will not be described or standardized. Scoping for “AP Functional Descriptions”

6 doc.: IEEE /604r0 Submission May 2004 Darwin Engwer, Nortel Networks; Lily Yang, Intel Corp.Slide 6 Example Functional Descriptions Needed Distribution System Services are not described anywhere: –Integration is not described anywhere –Portal function is not described anywhere –The association mechanics are described in the standard, possible error codes are identified, but use of those error codes under particular circumstances is not described. –Yet, every AP on the market includes all those functions. QED.

7 doc.: IEEE /604r0 Submission May 2004 Darwin Engwer, Nortel Networks; Lily Yang, Intel Corp.Slide 7 Need to form a new SG To work on better “AP Functional Descriptions” Some open questions for the SG to investigate: –What do we have today in the Standards (as starting points)? –What is missing, lacking, or confusing? –How to approach the functional decomposition (methodology)? –What is the right granularity for decomposition? –How to describe the interface or interaction? –How to better separate data plane and control plane? –What kind of documents will be produced in the end? –What impact does it have on other groups?

8 doc.: IEEE /604r0 Submission May 2004 Darwin Engwer, Nortel Networks; Lily Yang, Intel Corp.Slide 8 References: For additional information, please refer to these more detailed submissions: – wng-ap-functional-needs-capwap.ppt – wng-wlan-mesh-in-capwap-architecture.ppt – wng-thoughts-on-ap-functional-descriptions.ppt – wng-need-ap-functional-descriptions.ppt

9 doc.: IEEE /604r0 Submission May 2004 Darwin Engwer, Nortel Networks; Lily Yang, Intel Corp.Slide 9 The End


Download ppt "Doc.: IEEE 802.11-04/604r0 Submission May 2004 Darwin Engwer, Nortel Networks; Lily Yang, Intel Corp.Slide 1 AP Functional Descriptions Update Darwin Engwer,"

Similar presentations


Ads by Google