NOV 01 doc IEEE 802 15 01517 r

NOV 01 doc. : IEEE 802. 15 -01/517 r 2 Project: IEEE P 802. 15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Application Specific Information Element] Date Submitted: [14 Nov, 2001] Source: [Mark E. Schrader] Company [Eastman Kodak Co. ] Address [4545 East River Rd. , Rochester, NY 14650 -0898, USA] Voice: [+1. 716. 781. 9561], FAX: [+1. 716. 781. 9733], E-Mail: [mark. e. schrader@kodak. com] Re: [802. 15. 3 MAC Standard. ] [If this is a response to a Call for Contributions, cite the name and date of the Call for Contributions to which this document responds, as well as the relevant item number in the Call for Contributions. ] [Note: Contributions that are not responsive to this section of the template, and contributions which do not address the topic under which they are submitted, may be refused or consigned to the “General Contributions” area. ] Abstract: [An information element that the PNC can use to customize the network for devices that support the enhancement indicated by this element. Any change is transparent to devices that do not support the enhancement The enhancement is undefined in this standard] Purpose: [For inclusion in Draft D 09 of 802. 15. 3 Standard] Notice: This document has been prepared to assist the IEEE P 802. 15. 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. Release: The contributor acknowledges and accepts that this contribution becomes the property of IEEE and may be made publicly available by P 802. 15. Submission 1 Mark E. Schrader, Eastman Kodak Co.

NOV 01 doc. : IEEE 802. 15 -01/517 r 2 Purpose of the new information element • Allow application specific networks to use 802. 15. 3 baseline. • Provide custom information elements to utilize application specific protocol enhancements. • Allow mixed networks, with only some members having the application specific enhancements. Submission 2 Mark E. Schrader, Eastman Kodak Co.

NOV 01 doc. : IEEE 802. 15 -01/517 r 2 Text for Draft 0. 9 Submission 3 Mark E. Schrader, Eastman Kodak Co.

NOV 01 doc. : IEEE 802. 15 -01/517 r 2 Octets: 1 1 1 Element ID Element Length AD-AD N Application Specific Data Figure ? ? --Application Specific Information Element (ASIE) Submission 4 Mark E. Schrader, Eastman Kodak Co.

NOV 01 doc. : IEEE 802. 15 -01/517 r 2 The Element ID field shall have the value (the next available reserved ID). The Element Length shall be K+1 where K is the number of octets in the Application Specific Data field. The AD-AD is set by the PNC as the index of the application specific capable device that will make use of this information element. The Application Specific Data is specified by the PNC. Its use by the application specific capable device is beyond the scope of this standard. More than one ASIE may be placed in any beacon by the PNC. All ASIEs shall be the last information elements in the beacon. Submission 5 Mark E. Schrader, Eastman Kodak Co.

NOV 01 doc. : IEEE 802. 15 -01/517 r 2 The ASIE shall be the last information element in the beacon. The ASIE shall only be used by the PNC after negotiating the application specific capability with a DEV using a standard a GTS or CFP message exchange. The negotiation of the application specific capability between the DEV and the PNC is beyond the scope of this specification. The use of the DATA field of the information element is beyond the scope of this specification. Submission 6 Mark E. Schrader, Eastman Kodak Co.