Doc.: IEEE 802.15-99/042r4 Submission July 1999 Tom Siep, Texas InstrumentsSlide 1 Description of Proposed Structure for Draft MAC and PHY Standards IEEE.

Slides:



Advertisements
Similar presentations
1 Introducing the Specifications of the Metro Ethernet Forum.
Advertisements

Internetwork An internetwork is a collection of individual networks, connected by intermediate networking devices, that functions as a single large network.
Doc.: IEEE r July 2014 May 2012 Ben Rolfe (BCA) Project: IEEE Working Group for Wireless Personal Area Networks (WPANs) Submission.
Chapter 17 Networking Patricia Roy Manatee Community College, Venice, FL ©2008, Prentice Hall Operating Systems: Internals and Design Principles, 6/E William.
OSI Model OSI MODEL.
OSI Model OSI LAYER / MODEL.
© N. Ganesan, Ph.D., All rights reserved. Chapter ISO-OSI Reference Model and IEEE Standards.
LAN Protocol Architecture
CompTIA Network+ Chapter 2
International Standards Organization Open Systems Interconnect (OSI) Reference Model Advanced Computer Networks.
PROTOCOLS AND ARCHITECTURE Lesson 2 NETS2150/2850.
Jacob Boston Josh Pfeifer. Definition of HyperText Transfer Protocol How HTTP works How Websites work GoDaddy.com OSI Model Networking.
Protocols and the TCP/IP Suite
Chapter 1 Read (again) chapter 1.
Data Communications Architecture Models. What is a Protocol? For two entities to communicate successfully, they must “speak the same language”. What is.
William Stallings Data and Computer Communications 7 th Edition Chapter 2 Protocols and Architecture.
COE 342: Data & Computer Communications (T042) Dr. Marwan Abu-Amara Chapter 2: Protocols and Architecture.
Computer Networks with Internet Technology William Stallings
 The Open Systems Interconnection model (OSI model) is a product of the Open Systems Interconnection effort at the International Organization for Standardization.
LECTURE 2 CT1303 LAN. STANDARD MODELS: OSI Model : Open system Interconnection. is a conceptual model that characterizes and standardizes the internal.
OIS Model TCP/IP Model.
IP Network Basics. For Internal Use Only ▲ Internal Use Only ▲ Course Objectives Grasp the basic knowledge of network Understand network evolution history.
Protocols and the TCP/IP Suite Chapter 4. Multilayer communication. A series of layers, each built upon the one below it. The purpose of each layer is.
Doc.: IEEE /0xxr0 Submission September 1999 Tom Siep, Texas InstrumentsSlide 1 Mapping the Bluetooth Specification to IEEE Tom Siep Texas.
Chapter 1 Overview Review Overview of demonstration network
Introducing Network Standards
Protocols and the TCP/IP Suite
Doc.: IEEE /0981r1 TGs Reference Architecture Considerations September 6, 2004 Tricci So & W. Steven Conner.Slide 1 TGs ESS Mesh System Reference.
Course ILT The OSI model Unit objectives Explain the significance of the OSI model, label the seven layers of the OSI model, and describe services provided.
Fundamentals of Network Management by Behzad Akbari Fall 2008 In the Name of the Most High.
Layer Architecture Layer architecture simplifies the network design. It is easy to debug network applications in a layered architecture network. The network.
Abstract Syntax Notation ASN.1 Week-5 Ref: “SNMP…” by Stallings (Appendix B)
Network Protocol Hierarchies
Computer Networks. Introduction Computer Network2 A History Lesson of Networking 1969 – ARPANET, first packet switched network consist of UCLA, Stanford,
3rd NYMAN Javier, Sai and Sunghyun Sept Philips Research USA Slide 1 Multimedia Clock Synchronization over WLAN Javier del Prado and Sai Shankar.
Doc.: IEEE /042r1 Submission July 1999 Tom Siep, Texas InstrumentsSlide 1 Description of Proposed Structure for Draft MAC and PHY Standards IEEE.
OSI Reference Model. Open Systems Interconnection (OSI) Model International standard organization (ISO) established a committee in 1977 to develop an.
Network Protocols and Standards (Part 2). The OSI Model In 1984, the International Organization for Standardization (ISO) defined a standard, or set of.
CHAPTER 4 PROTOCOLS AND THE TCP/IP SUITE Acknowledgement: The Slides Were Provided By Cory Beard, William Stallings For Their Textbook “Wireless Communication.
Open System Interconnection Describe how information from a software application in one computer moves through a network medium to a software application.
Chapter 2 Network Models
Doc.: IEEE /0981r0 TGs Reference Architecture Considerations August 30, 2004 Tricci So.Slide 1 TGs ESS Mesh System Reference Architecture Considerations.
Doc.: IEEE /1109r0 Submission Month Year Tom Siep, CSRSlide 1 Amendment Creation Process Date: YYYY-MM-DD Authors:
1 Chapter 4. Protocols and the TCP/IP Suite Wen-Shyang Hwang KUAS EE.
1 Protocol Layering Myungchul Kim Tel:
Chapter 7 OSI Data Link Layer.
1 DQDB -  All rights reserved. No part of this publication and file may be reproduced, stored in a retrieval system, or transmitted in any form or by.
September 2002 doc.: IEEE /568r0 David Skellern, Cisco SystemsSlide 1Submission RRM Architectural Framework David Skellern Wireless Networking.
Doc.: IEEE Submission March 2005 Tom Siep, Cambridge Silicon RadioSlide 1 Project: IEEE P Working Group for Wireless Personal.
IEEE 1394b Real-Time Systems Lab. 박 준 호. Real Time Systems Lab. Contents IEEE 1394 Overview IEEE 1394 Specifications P1394a, P1394b, P1394.1, OHCI IEEE.
Doc.: IEEE /368r0 Submission July 2001May 2001 John Barr, MotorolaSlide 1 Project: IEEE Working Group for Wireless Personal Area Networks.
TUNALIData Communications1 Chapter 2 Protocols and Architecture.
Doc.: IEEE /xxxxr0 Submission May 2006 Darwin Engwer, NortelSlide 1 Services and SAPs Notice: This document has been prepared to assist IEEE
Doc.: IEEE /065r1 Submission February 2000 Tom Siep, Texas InstrumentsSlide 1 Project: IEEE P Working Group for Wireless Personal Area Networks.
Computer Networks.
Chap. 2 Network Models.
July, 2003 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Proposed Changes to ] Date Submitted:
ISO-OSI Reference Model and IEEE Standards
NET301 Lecture 2 10/9/2015 NET 301.
IEEE Working Group for Wireless Personal Area Networks (WPANs)
Protocols and the TCP/IP Suite
Chapter 3: Open Systems Interconnection (OSI) Model
Submission Title: [Draft Standard Overview]
Mapping the Bluetooth Specification to IEEE
Chapter 2. Protocols and Architecture
Protocols and the TCP/IP Suite
Overview of Improvements to Key Holder Protocols
IEEE Working Group for Wireless Personal Area Networks (WPANs)
Services and SAPs Date: Authors: May 2006 May2006
Presentation transcript:

doc.: IEEE /042r4 Submission July 1999 Tom Siep, Texas InstrumentsSlide 1 Description of Proposed Structure for Draft MAC and PHY Standards IEEE P Wireless Personal Area Network

doc.: IEEE /042r4 Submission July 1999 Tom Siep, Texas InstrumentsSlide 2 IEEE 802 Structure

doc.: IEEE /042r4 Submission July 1999 Tom Siep, Texas InstrumentsSlide 3 The Project 802 Domain

doc.: IEEE /042r4 Submission July 1999 Tom Siep, Texas InstrumentsSlide 4 Original Bluetooth to IEEE

doc.: IEEE /042r4 Submission July 1999 Tom Siep, Texas InstrumentsSlide 5 New Understanding of Bluetooth/IEEE Correspondence

doc.: IEEE /042r4 Submission July 1999 Tom Siep, Texas InstrumentsSlide 6 Taxonomy of an 802 Standard

doc.: IEEE /042r4 Submission July 1999 Tom Siep, Texas InstrumentsSlide 7 Outline of Standard Main Text 1)Overview 2)Normative References 3)Definitions 4)Abbreviations and Acronyms 5)General Description 6)Medium Access Control (MAC) 7)Physical Layer (PHY) 8)Layer Management

doc.: IEEE /042r4 Submission July 1999 Tom Siep, Texas InstrumentsSlide 8 Outline of Standard Appendix A.Protocol Implementation Conformance Statement (PICS) proforma B.Formal Description of MAC operation C.Formal Description of PHY operation D.MAC Management Information Base E.PHY Management Information Base F.Bibliography

doc.: IEEE /042r4 Submission July 1999 Tom Siep, Texas InstrumentsSlide 9 Clause 1 Overview –Scope –Purpose

doc.: IEEE /042r4 Submission July 1999 Tom Siep, Texas InstrumentsSlide 10 Clause 2 Normative References –Other documents (IEEE, ISO, ITU…)

doc.: IEEE /042r4 Submission July 1999 Tom Siep, Texas InstrumentsSlide 11 Clause 3 Definitions –Terms specific to this Standard

doc.: IEEE /042r4 Submission July 1999 Tom Siep, Texas InstrumentsSlide 12 Clause 4 Abbreviations and Acronyms

doc.: IEEE /042r4 Submission July 1999 Tom Siep, Texas InstrumentsSlide 13 Clause 5 General Description –Architecture –Components –Services

doc.: IEEE /042r4 Submission July 1999 Tom Siep, Texas InstrumentsSlide 14 Clause 6 Medium Access Control The part of the data link layer that supports topology-dependent functions and uses the services of the physical layer to provide service to the logical link control (LLC) sublayer. In ISO/IEC 8802, the combined set of functions in the DQDB Layer that support the MAC Sublayer service to the logical link control (LLC) sublayer. DQDB

doc.: IEEE /042r4 Submission July 1999 Tom Siep, Texas InstrumentsSlide 15 Clause 6.1 MAC Service Definition (MAC_SAP)MAC_SAP –Overview –Service Specification The unconfirmed connectionless-mode MAC service defined in ISO/IEC 10039, as an abstraction of the features common to a number of specific MAC services for Local Area Networks.

doc.: IEEE /042r4 Submission July 1999 Tom Siep, Texas InstrumentsSlide 16 Clause 6.2 MAC Frame Formats –Conventions –General Frame Formats –Format of Individual Frame Types

doc.: IEEE /042r4 Submission July 1999 Tom Siep, Texas InstrumentsSlide 17 MAC Frame Format Conventions The sequence of octets in the fields of the MAC frame forms an octet stream at the MAC/PLCP sublayer boundary. The leftmost octet in each field of the MAC frame is passed across the MAC/PLCP boundary first. Fields that are longer than a single octet are depicted with the least significant octet on the left. The least significant bit of each octet is defined as bit 0 for that octet and is the leftmost bit of the octet. Fields that are less than one octet in length are ordered with the least significant bit to the left. MAC addresses are assigned as ordered sequences of bits. The Individual/Group bit is always transferred first and is the least significant bit of the first octet. Values specified in decimal are coded in natural binary unless otherwise stated. Reserved fields and subfields are set to 0 upon transmission and are ignored on reception Example

doc.: IEEE /042r4 Submission July 1999 Tom Siep, Texas InstrumentsSlide 18 MAC General Frame Formats Fields common to all frames declared first All possible optional fields follow When present, they occur in specified order Example

doc.: IEEE /042r4 Submission July 1999 Tom Siep, Texas InstrumentsSlide 19 Format of Individual MAC Frame Types Specify purpose of frame and fields Define fields used Specify default values (if any) Reserved fields

doc.: IEEE /042r4 Submission July 1999 Tom Siep, Texas InstrumentsSlide 20 Clause 6.3 MAC Layer Functional Description –Authentication and PrivacyPrivacy –Fragmentation/Defragmentation –Frame Exchange Sequences –Audio

doc.: IEEE /042r4 Submission July 1999 Tom Siep, Texas InstrumentsSlide 21 Clause 7 Physical Layer

doc.: IEEE /042r4 Submission July 1999 Tom Siep, Texas InstrumentsSlide 22 Clause 7.1 PHY Layer Functional Description

doc.: IEEE /042r4 Submission July 1999 Tom Siep, Texas InstrumentsSlide 23 Clause 7.1 (continued) The Physical Layer is the first layer of the seven- layer OSI model; responsible for transporting bits between adjacent systems. Note: This layer accepts a bit stream, called a frame, from the data link layer and places it on the media. It also performs the inverse operation of extracting a bit stream from the physical media and passes it to the data link layer. This layer describes mechanical and electrical characteristics of the connection, as well as the required interchange circuits.

doc.: IEEE /042r4 Submission July 1999 Tom Siep, Texas InstrumentsSlide 24 Clause 7.2 PHY Service Specification –Overview –Service Specification

doc.: IEEE /042r4 Submission July 1999 Tom Siep, Texas InstrumentsSlide 25 Clause 7.2 (Service Specification) The subdivision that provides the protocol to allow transfer of slot octets, management information octets, and DQDB Layer timing information over the transmission link between DQDB Layer subsystems at adjacent nodes. The Physical Layer provides the service to the DQDB Layer.

doc.: IEEE /042r4 Submission July 1999 Tom Siep, Texas InstrumentsSlide 26 Clause 7.3 PHY Frame Formats –Conventions –General Frame Formats –Format of Individual Frame Types

doc.: IEEE /042r4 Submission July 1999 Tom Siep, Texas InstrumentsSlide 27 Clause 8 Layer Management –Overview –MAC Layer Management Entity –Physical Layer Management Entity –Station Management Entity

doc.: IEEE /042r4 Submission July 1999 Tom Siep, Texas InstrumentsSlide 28 Management Primitives The GET and SET primitives in fact are represented as REQUESTs with associated CONFIRM primitives. These primitives are prefixed by MLME or PLME XXGET.request (MIBattribute) XXGET.confirm (status, MIBattribute, MIBattributevalue) XXSET.request (MIBattribute, MIBattributevalue) XXSET.confirm (status, MIBattribute)

doc.: IEEE /042r4 Submission July 1999 Tom Siep, Texas InstrumentsSlide 29 Clause 8.1 Overview Both MAC and PHY layers conceptually include management entities, called MAC subLayer Management and PHY Layer Management Entities (MLME and PLME). These entities provide the layer management service interfaces through which layer management functions may be invoked.

doc.: IEEE /042r4 Submission July 1999 Tom Siep, Texas InstrumentsSlide 30 Clause 8.2 MAC Layer Management Entity

doc.: IEEE /042r4 Submission July 1999 Tom Siep, Texas InstrumentsSlide 31 Clause 8.3 Physical Layer Management Entity

doc.: IEEE /042r4 Submission July 1999 Tom Siep, Texas InstrumentsSlide 32 Clause 8.4 Station Management Entity The SME is a layer-independent entity which may be viewed as residing in a separate management plane or as residing "off to the side". The exact functions of the SME are not specified in this standard, but in general this entity may be viewed as responsible for such functions as the gathering of layer- dependent status from the various layer management entities, and similarly setting the value of layer-specific parameters. SME would typically perform such functions on behalf of general system management entities and would implement standard management protocols Example

doc.: IEEE /042r4 Submission July 1999 Tom Siep, Texas InstrumentsSlide 33 Appendices A.Protocol Implementation Conformance Statement (PICS) proforma B.Formal Description of MAC operation C.Formal Description of PHY operation D.MAC Management Information Base E.PHY Management Information Base F.Bibliography

doc.: IEEE /042r4 Submission July 1999 Tom Siep, Texas InstrumentsSlide 34 Protocol Implementation Conformace Statement proforma The PICS is a description of an implementation claim. It specifies: –Who implemented –What was implemented –Mandatory capabilities were satisfied –Which options were chosen

doc.: IEEE /042r4 Submission July 1999 Tom Siep, Texas InstrumentsSlide 35 Formal Definitions Formal definitions are represented in Specification and Description Language (SDL) ITU-T Recommendation Z.100 REF: Ellsberger, J., SDL Formal Object-Oriented Language for Communicating Systems, Hertfordshire, Prentice Hall Europe, 1997 (ISBN )

doc.: IEEE /042r4 Submission July 1999 Tom Siep, Texas InstrumentsSlide 36 Management Information Base MIBs are abstract representation of data They are represented in ASN.1 –Abstract Syntax Notation One –ITU-T Recommendations X.280 X Z.105 REF: SDL Formal Object-Oriented Language for Communicating Systems

doc.: IEEE /042r4 Submission July 1999 Tom Siep, Texas InstrumentsSlide 37 LLC Discussion Research needed

doc.: IEEE /042r4 Submission July 1999 Tom Siep, Texas InstrumentsSlide 38 MAC Bridging Not applicable (?)

doc.: IEEE /042r4 Submission July 1999 Tom Siep, Texas InstrumentsSlide 39 Proposed Work Areas

doc.: IEEE /042r4 Submission July 1999 Tom Siep, Texas InstrumentsSlide 40 END OF PRESENTATION (backup slides follow)

doc.: IEEE /042r4 Submission July 1999 Tom Siep, Texas InstrumentsSlide 41 Bluetooth and IEEE Structure

doc.: IEEE /042r4 Submission July 1999 Tom Siep, Texas InstrumentsSlide 42 Distributed Queue Dual Bus (1 of 2) IEEE Std Information Technology Telecommunications And Information Exchange Between Systems Local And Metropolitan Area Networks Specific Requirements—Part 6: Distributed Queue Dual Bus (DQDB) Access Method And Physical Layer Specifications. This standard is part of a family of standards for local area networks (LANs) and metropolitan area networks (MANs) that deals with the Physical and Data Link Layers as defined by the ISO Open Systems Interconnection Reference Model. It defines a high-speed shared medium access protocol for use over a dual, counterflowing, unidirectional bus subnetwork. The Physical Layer and Distributed Queue Dual Bus (DQDB) Layer are required to support a Logical Link Control (LLC) Sublayer by means of a connectionless Medium Access Control (MAC) Sublayer service in a manner consistent with other IEEE 802 networks. Additional DQDB Layer functions are specified as a framework for other services. These additional functions will support Isochronous Service Users and Connection-Oriented Data Service Users, but their implementation is not required for conformance.

doc.: IEEE /042r4 Submission July 1999 Tom Siep, Texas InstrumentsSlide 43 Distributed Queue Dual Bus (2 of 2) IEEE Std 802.6j Local and Metropolitan Area Networks: Supplement to 802.6: Connection-Oriented Service on a Distributed Queue Dual Bus (DQDB) Subnetwork of a Metropolitan Area Network (MAN). Enhanced Queued Arbitrated (QA) Functions, which can support applications requiring bandwidth guarantees and delay limits on a DQDB subnetwork, are specified. Connection-Oriented Convergence Functions (COCFs) using the enhanced QA Functions, which are necessary to support connection-oriented service, are also specified return

doc.: IEEE /042r4 Submission July 1999 Tom Siep, Texas InstrumentsSlide 44 Service Access Point service access point (SAP) (1) The point at which services are provided by one layer (or sublayer) to the layer (or sublayer) immediately above it (ISO 7498), ISO (2) An address that identifies a user of the services of a protocol entity individual address (1) An address that identifies a single source or destination service access point. ISO return

doc.: IEEE /042r4 Submission July 1999 Tom Siep, Texas InstrumentsSlide 45 Encryption Question How does the 128 bit encryption requirement impact USA export restrictions? return

doc.: IEEE /042r4 Submission July 1999 Tom Siep, Texas InstrumentsSlide 46 Bluetooth Classes of Services AudioSynchBridgingNetworkHID Still Image Comm Port App. WAP RF AUDIOAUDIO BB LM L 2 CAP Audio Ctrl TS0710TCP/IPHID IrOBEXPPP WAP Still Images vCardvCalUDP