doc.: IEEE /044r0 Submission March, 2000 Cypher/NISTSlide 1 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Overview of SDLs (BB, LMP, and L2CAP)] Date Submitted: [6 March, 2000] Source: [David Cypher] Company [NIST] Address [100 Bureau Drive, STOP 8920, Gaithersburg, MD ] Voice:[+1 (301) ], FAX: [ ], Re: [] Abstract:[This contribution provides the overview and introduction to the SDLs for the MAC sublayer that are contained in three separate contributions:] Purpose:[To inform the March, 2000 participants of the current status of the SDLs for the MAC sublayer. Also to inform the group of what the SDL are and what they are not in order to reach agreement on how to proceed with the SDL development for the IEEE TG1 Draft Standard (IEEE DX/X (Annex B)] Notice:This document has been prepared to assist the IEEE P 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 Contribution of the NIST, not subject to copyright in the United States of America.

doc.: IEEE /044r0 Submission March, 2000 Cypher/NISTSlide 2 Overview and Introduction to the SDLs for the MAC Sublayer References: IEEE P /045r0 - Baseband IEEE P /046r0 - Link Manager Protocol IEEE P /001r2 - Logical Link Control Adaptation Protocol

doc.: IEEE /044r0 Submission March, 2000 Cypher/NISTSlide 3 What is SDL Specification and Description Language Standardized by ITU-T in the Z-series Mainly ITU-T Recommendation Z.100

doc.: IEEE /044r0 Submission March, 2000 Cypher/NISTSlide 4 Why use SDL Provides Clear and Unambiguous Description of … (e.g. Protocols, or Systems) Simulation, Validation, and Verification tools available for SDLs Conversion tools available to take SDL in and generate “useable code” or “TTCN tests”

doc.: IEEE /044r0 Submission March, 2000 Cypher/NISTSlide 5 When to create SDLs In the beginning Not after the protocol is described by other means (e.g. English text) After English text to aid in protocol review, validation, and testing.

doc.: IEEE /044r0 Submission March, 2000 Cypher/NISTSlide 6 SDLs consist of System block One or more Blocks Process (at least one) (Flow chart) Processes can be dynamically allocated, blocks can not

doc.: IEEE /044r0 Submission March, 2000 Cypher/NISTSlide 7 Details of SDL Describes System Behavior in abstract terms Describes Coding in abstract terms May Describe Coding in ASN.1 format

doc.: IEEE /044r0 Submission March, 2000 Cypher/NISTSlide 8 Sample System Block Block A Block B

doc.: IEEE /044r0 Submission March, 2000 Cypher/NISTSlide 9 Testing SDLs Single System/Block/ProcessPeer System/Block/Process_type “Like Conformance Testing” “Like Interoperability Testing”

doc.: IEEE /044r0 Submission March, 2000 Cypher/NISTSlide 10 Where are SDLs L2CAP LMP BB

doc.: IEEE /044r0 Submission March, 2000 Cypher/NISTSlide 11 SDL Development L2CAP is defined as a “Process type”, so it can be used in various scenarios. LMP is defined as a “Process type”, so it can be used in various scenarios. BB is only a process. It has not been converted into a “process type”

doc.: IEEE /044r0 Submission March, 2000 Cypher/NISTSlide 12 Simulating, Validating, and Verifying the SDLs L2CAP and LMP has been validated in a peer to peer environment. Only begun validating in a single environment. BB has been validated in a single environment. Errors are present. Need to decide how to correct/proceed.

doc.: IEEE /044r0 Submission March, 2000 Cypher/NISTSlide 13 Current Status and Plans Attempting to integrate three SDLs into one SDL, but ambiguity exists in the Bluetooth Specification, which hampers development Implementation decisions (TX/RX) also hampering integration Continue to do behavior and SDL data structure in the abstract, not actual coding