Project: IEEE 802.15 Working Group for Wireless Personal Area Networks (WPANs) - PowerPoint PPT Presentation

slide1 n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
Project: IEEE 802.15 Working Group for Wireless Personal Area Networks (WPANs) PowerPoint Presentation
Download Presentation
Project: IEEE 802.15 Working Group for Wireless Personal Area Networks (WPANs)

play fullscreen
1 / 76
Download Presentation
Project: IEEE 802.15 Working Group for Wireless Personal Area Networks (WPANs)
85 Views
bono
Download Presentation

Project: IEEE 802.15 Working Group for Wireless Personal Area Networks (WPANs)

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Project: IEEE 802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Draft F8 Overview] Date Submitted: [January 18, 2004] Source: [John Sarallo] Company [Appairent] Address [150 Lucius Gordon Drive, West Henrietta, NY 14586] Voice:[+1 585 727-2014], FAX: [+1 585 214-2461], E-Mail:[sarallo@appairent.com] Re: [15-05-0074-00-003b] Abstract: [An overview presentation of 802.15.3b Amendment Draft F8] Purpose: [This presentation was made to the 1394 Trade Association by the author at the Q1 2005 meeting. The purpose was to summarize the material in the F8 draft.] Notice: This document has been prepared to assist the IEEE 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 802.15. John Sarallo - Appairent

  2. 802.15.3b Draft F8 Review 1394 Trade Association – 1Qtr Meeting Maui, HI John Sarallo - Appairent

  3. 802.15.3b Status • Draft F8 released for review to IEEE 802.15 members • A rough draft (in my opinion) • Released mainly for feedback on proposed MLME/MAC SAP (which we will review today) • Comments on draft due this Friday, Jan. 14 • Comments will be worked on next week at IEEE meeting in Monterey, CA John Sarallo - Appairent

  4. Goals for this Working Group • Review the MLME/MAC SAP as defined in draft F8 with 1394 PAL needs in mind • Identify the issues for the 1394 3b PAL • Determine which issues require comments against the draft (John Sarallo will submit comments before the deadline) • Identify/work issues that can not be resolved with 802.15.3b comments John Sarallo - Appairent

  5. MLME/MAC SAP Review • The 802.15.3b Reference Model • Reference Model impact on MLME SAP and MAC SAP • Overview of 802.15.3b MLME SAP • Overview of 802.15.3b MAC SAP • Focused look at Stream Management John Sarallo - Appairent

  6. Current 802.15.3 Reference Model • A DME exists between the FCSL and MLME SAP • 1394 PAL assumed DME in the PAL • DME needs to be in MAC to support multiple PALs simultaneously John Sarallo - Appairent

  7. Modified Reference Model for 802.15.3b • The DME concept removed • What was DME functionality is now in MLME functionality • This automatically raises the abstraction level of the MLME SAP • MLME SAP changes required some changes to MAC SAP as well John Sarallo - Appairent

  8. 1934 PAL Protocol Architecture • 802.15.3b reference model matches 1394 PAL Architecture nicely • PAL interfaces to MLME and MAC SAPs John Sarallo - Appairent

  9. Changes to MLME SAP (1) • MAC/PHY details hidden from FCSL • PHY Channel scheme • Superframe size and structure • Operations combined for simplicity • Auto synch to piconet before association • Enhanced application support • Means for any device to announce/receive application specific information • Means for any device to announce/receive piconet services information • Means for any device to send/receive vendor specific commands and information John Sarallo - Appairent

  10. Changes to MLME SAP (2) • Enhanced multicast support • Multiple multicast groups based on 802 Multicast Address • Device Synchronization support • Enable/Disable notification of beacon reception • Enhanced Stream Management • FCSL provides throughput and latency requirements, MLME translates this to time-based requests for PNC • PNC guarantees required latency • Prioritized first come/first served allocation policy John Sarallo - Appairent

  11. Change to All MLME.requests • Requests no longer have timeout values • FCSL may timeout a request that requires a confirm if it chooses • MLME manages the timeout of over-air requests/responses • A MLME timeout results in a confirm indicating Failure John Sarallo - Appairent

  12. Reset MAC/MLME 802.15.3 802.15.3b MLME-RESET.request ( SetDefaultPIB ) MLME-RESET.confirm ( ResultCode ) MLME-RESET.request ( SetDefaultPIB, ResetTimeout ) • MLME-RESET.confirm indicates when the reset is complete • If MLME/MAC is ready to accept requests then ResultCode is READY • If MLME/MAC is not operational then ResultCode is ERROR John Sarallo - Appairent

  13. Scanning for Piconets (1) 802.15.3 802.15.3b MLME-SCAN.request ( ScanForBSID, BSID, ScanForPNID PNID, ScanForPNCAddress, PNCAddress ) MLME-SCAN.request ( OpenScan, BSID, PNID, ChannelList, ChannelScanDuration ) • Scan for any piconet or scan by any combination of BSID, PNID, and PNCAddress • MLME automatically scans all PHY channels John Sarallo - Appairent

  14. Scanning for Piconets (2) 802.15.3 802.15.3b MLME-SCAN.confirm ( ResultCode, NumberOfPiconets, PiconetDescriptionSet, NumberOfChannels, ChannelRatingList, ReasonCode ) MLME-SCAN.confirm ( NumberOfPiconets, PiconetDescriptionSet, NumberOfChannels, ChannelRatingList, ResultCode ) • PiconetDescription includes BSID, PNID, PNCAddress, Channel, and any Application Specific information available in a Beacon • ChannelRatingList allows FCSL to pick between multiple suitable piconets (i.e. the closest one) John Sarallo - Appairent

  15. Scanning for Piconets (3) John Sarallo - Appairent

  16. Starting a Piconet (1) 802.15.3 802.15.3b MLME-START.request ( BSID, SECMode ) MLME-START.request ( PNID, BSID, ChannelIndex, SuperframeDuration, CAPEndTime, SECID, CAPData, CAPCommands, CAPAssociation, SECMode, MaxTXPowerLevel, MCTAUsed, MCTAAllocationRate ) • MLME determines everything except Beacon Source Identifier (BSID) and whether or not security should be used • A MLME-START.request while already associated is considered a request to start a child piconet John Sarallo - Appairent

  17. Starting a Piconet (2) 802.15.3 802.15.3b MLME-START.confirm ( ResultCode, DEVID, DEVAddress, ReasonCode ) MLME-START.confirm ( ResultCode ) • If start is successful, FCSL is given DEV’s assigned DEVID for data communications and the DEVAddress John Sarallo - Appairent

  18. Starting a Piconet (3) John Sarallo - Appairent

  19. Stopping a Piconet 802.15.3 802.15.3b MLME-STOP.request ( RequestType, AllowedHandoverTime, HandoverTargetList ) MLME-STOP.confirm ( ResultCode, ReasonCode ) MLME-PNC-HANDOVER.request ( NewPNCDEVID, NumberOfDEVs, HndOvrBeaconNumber, DEVInfoSet, HandoverStatus, HandoverTimeout ) MLME-PNC-HANDOVER.response ( ReasonCode ) MLME-PNC-HANDOVER.confirm ( ResultCode ) • RequestType of MLME-STOP.request indicates if a handover is allowed before stopping operations • AllowedHandoverTime allows FCSL to indicate how much time is available to complete a handover John Sarallo - Appairent

  20. Piconet Handover (1) 802.15.3 802.15.3b MLME-PNC-HANDOVER.indication ( HandoverStatus ) MLME-NEW-PNC.indication ( NewPNCDEVAddress, SECMode ) MLME-PNC-HANDOVER.indication ( NumberOfDEVs, HandoverStatus ) MLME-NEW-PNC.indication ( NewPNCDEVID, NewPNCDEVAddress ) • MLME-PNC-HANDOVER.indication informs an FCSL it is the target of a handover • HandoverStatus is Started or Cancelled • MLME-NEW-PNC.indication informs all FCSLs of new PNC running piconet John Sarallo - Appairent

  21. Piconet Handover (2) John Sarallo - Appairent

  22. Associating with a Piconet (1) 802.15.3 802.15.3b MLME-ASSOCIATE.request ( BSID, PNC, PNCDEVAddress, ChannelIndex, PiconetServicesInquiry ) MLME-ASSOCIATE.request ( DEVAddress, PSRC, SEC, PNCDesMode, PNCCapable, MaxAssociatedDEVs, MaxCTRqBs, MaxTXPower, SupportedDataRates, PreferredFragmentSize, ATP, PiconetServicesInquiry, NeighborPNCRequest, AlwaysAWAKE, ListenToSource, ListenToMulticast, AssocTimeout ) • MLME always synchs to target PNC before associating • Parameters remove any ambiguity as to which piconet to join • Device capabilities determined by MLME John Sarallo - Appairent

  23. Associating with a Piconet (2) 802.15.3 802.15.3b MLME-ASSOCIATE.confirm ( ResultCode, DEVID, DEVAddress, VendorSpecificIE, ReasonCode ) MLME-ASSOCIATE.indication ( DEVID, DEVAddress ) MLME-ASSOCIATE.confirm ( DEVID, ATP, ReasonCode, VendorSpecificIE, ResultCode ) MLME-DEV-ASSOCIATION-INFO.indication ( DEVAddress, DEVID, SupportedDataRates, AssociationStatus ) • There is no MLME-ASSOCIATE.indication/response to PNC FCSL for association approval • MLME-ASSOCIATE.indication is now used to inform FCSL of DEVs that associate with the piconet (replaces MLME-DEV-ASSOCIATION-INFO.indication) John Sarallo - Appairent

  24. Associating with a Piconet (3) John Sarallo - Appairent

  25. Disassociating from a Piconet (1) 802.15.3 802.15.3b MLME-DISASSOCIATE.request () MLME-DISASSOCIATE.indication ( DEVID, DEVAddress, ReasonCode ) MLME-DISASSOCIATE.request ( TrgtID, ReasonCode, DisassocTimeout ) MLME-DISASSOCIATE.confirm ( TrgtID, ResultCode ) MLME-DISASSOCIATE.indication ( OrigID, ReasonCode ) • An FCSL request to disassociate is always successful (no confirm required) • Only FCSL of an associated non-PNC device can make this request. • PNC FCSL does not control who is associated and can not disassociate DEVs from the piconet John Sarallo - Appairent

  26. Disassociating from a Piconet (2) John Sarallo - Appairent

  27. Disassociating from a Piconet (3) John Sarallo - Appairent

  28. Security Management (1) 802.15.3 802.15.3b MLME-MEMBERSHIP-UPDATE.request( TrgtID, MembershipStatus, SECID, KeyType, KeyOriginator, KeyInfoLength KeyInfo ) MLME-SECURITY-ERROR.indication ( SrcID ReasonCode ) MLME-MEMBERSHIP-UPDATE.request( TrgtID, MembershipStatus, SECID, KeyType, KeyOriginator, KeyInfoLength KeyInfo ) MLME-SECURITY-ERROR.indication ( ReceivedMACHeader, ReceivedFramePayload ReasonCode ) • MAC Header and Payload not passed to FCSL on security error John Sarallo - Appairent

  29. Security Management (2) 802.15.3 802.15.3b MLME-SECURITY-MESSAGE.request( TrgtID, VendorOUI, SecurityInformationLength, SecurityInformation ) MLME-SECURITY-MESSAGE.indication ( OrigID, VendorOUI, SecurityInformationLength, SecurityInformation ) MLME-SECURITY-MESSAGE.request( TrgtID, VendorOUI, SecurityInformation, SecMsgTimeout ) MLME-SECURITY-MESSAGE.indication ( TrgtID, OrigID, VendorOUI, SecurityInformation ) MLME-SECURITY-MESSAGE.confirm ( ResultCode ) • Security messages can be passed from FCSL to FCSL • There is no over-air response command, so no confirm can be generated John Sarallo - Appairent

  30. Security Management (3) John Sarallo - Appairent

  31. Requesting DEV info from the PNC (1) 802.15.3 802.15.3b MLME-DEV-INFO.request ( RequestType, QueriedDEVID ) MLME-DEV-INFO.confirm ( ResultCode, NumDEVInfoSet, DEVInfoSet, ReasonCode ) MLME-DEV-INFO.indication ( NumDEVInfoSet, DEVInfoSet ) MLME-PNC-INFO.request ( QueriedDEVID, PNCInfoTimeout ) MLME-PNC-INFO.confirm ( NumDEVInfoSet, DEVInfoSet, ResultCode ) • Name changed to better match purpose (retrieving DEV info) • RequestType indicates if this is a request for all DEV information or the information for a single DEV • QueiredDEVID only used in request is for a single DEVs info • PNC FCSL is not involved with DEV Info retrieval • MLME-DEV-INFO.indication used to provide FCSL with unsolicited DEV Info broadcast by PNC John Sarallo - Appairent

  32. Requesting DEV info from the PNC (2) John Sarallo - Appairent

  33. Security Information Retrieval (1) 802.15.3 802.15.3b MLME-SECURITY-INFO.request ( TrgtID, RequestType QueriedDEVID ) MLME-SECURITY-INFO.indication ( OrigID. RequestType, QueriedDEVID ) MLME-SECURITY-INFO.response ( OrigID, NumSecurityRecordSet, SecurityRecordSet ) MLME-SECURITY-INFO.confirm ( ResultCode, TrgtID, NumSecurityRecordSet, SecurityRecordSet, ReasonCode ) MLME-SECURITY-INFO.request ( TrgtID, QueriedDEVID, SecurityInfoTimeout ) MLME-SECURITY-INFO.indication ( QueriedDEVID, OrigID ) MLME-SECURITY-INFO.response ( OrigID, NumSecurityRecordSet, SecurityRecordSet ) MLME-SECURITY-INFO.confirm ( TrgtID, NumSecurityRecordSet, SecurityRecordSet, ResultCode ) • FCSL to FCSL security information retrieval as before • QueiredDEVID only used if request is for a single DEV’s info John Sarallo - Appairent

  34. Security Information Retrieval (2) John Sarallo - Appairent

  35. Application Specific Information (1) 802.15.3 802.15.3b MLME-APPLICATION-SPECIFIC.request( RequestType, ApplicationDataID, VendorOUI, ApplicationDataLength, ApplicationData ) MLME-CREATE-ASIE.request ( Cmd, NumBeacons, VendorOUI, TrgtID, ASIEIndex, MessageLength, ASIEMessage, CreateASIETimeout ) • Name changed to hide Information Element (IE) concept from FCSL • New over-air command defined to allow any DEV to request the addition/removal of Application Specific Info to/from PNC Beacon • RequestType allows information to be Added or Removed from PNC • ApplicationDataID only used when previously Added information is Removed • Other parameters only used when new information is Added John Sarallo - Appairent

  36. Application Specific Information (2) 802.15.3 802.15.3b MLME-APPLICATION-SPECIFIC.confirm( ResultCode, ApplicationDataID, ReasonCode ) MLME-APPLICATION-SPECIFIC.indication( NumApplicationSpecificData, ApplicationSpecificDataSet ) MLME-CREATE-ASIE.confirm ( VendorOUI, ASIEIndex, ResultCode ) MLME-RECEIVE-ASIE.indication ( VendorOUI, MessageLength, ASIEMessage ) • Confirm includes ApplicationDataID of information Added or Removed • MLME-APPLICATION-SPECIFIC.indication informs FCSL of a change to the Application Specific Data broadcast by the PNC John Sarallo - Appairent

  37. Application Specific Information (3) John Sarallo - Appairent

  38. Piconet Services (1) 802.15.3 802.15.3b MLME-ANNOUNCE-SERVICE.request( VendorOUI, ServiceDataLength, ServiceData ) MLME-ANNOUNCE-SERVICE.confirm( ResultCode, ReasonCode ) No requests associated with piconet services • MLME-ANNOUNCE-SERVICE.request allows FCSL of an associated DEV to announce the availability of a service to the PNC (PNC optionally stores this information) • PNC removes any stored information when DEV disassociates John Sarallo - Appairent

  39. Piconet Services (2) 802.15.3 802.15.3b MLME-PICONET-SERVICES.request ( TrgtD ) MLME-PICONET-SERVICES.confirm ( ResultCode, NumberOfServices, PiconetServicesSet, ReasonCode ) MLME-PICONET-SERVICES.indication( NumberOfServices, PiconetServicesSet ) MLME-PICONET-SERVICES.indication( TrgtD ) MLME-PICONET-SERVICES.response( TrgtID, NumPiconetServicesIEs, PiconetServicesIESet ) MLME-PICONET-SERVICES.confirm ( NumPiconetServicesIEs, PiconetServicesIESet ) • MLME-PICONET-SERVICES.request allows FCSL of an associated DEV to request service information from the PNC (all information stored by PNC) or request service information from a specific DEV • MLME-PICONET-SERVICES.indication informs FCSL of the reception of unsolicited services information broadcast by the PNC • FCSL should determine a service is no longer available when the DEV offering service disassociates from piconet John Sarallo - Appairent

  40. Piconet Services (3) John Sarallo - Appairent

  41. Piconet Services (4) John Sarallo - Appairent

  42. Piconet Parameter Management (1) 802.15.3 802.15.3b MLME-PICONET-PARM-CHANGE.request ( RequestChangeType, BSID, MaxTXPowerLevel ) MLME-PICONET-PARM-CHANGE.confirm ( ResultCode, ReasonCode ) MLME-PICONET-PARM-CHANGE.request ( ChangeType, ChangeBeaconNumber, NewChannelIndex, SuperframeTiming, PNID, BSID, MaxTXPowerLevel ) MLME-PICONET-PARM-CHANGE.confirm ( ResultCode ) • MLME now manages Channel, Superframe Duration, PNID, and MaxTXPowerLevel • FCSL can only change Beacon Source Identifier (BSID) • I believe MaxTXPowerLevel in draft version is a mistake? John Sarallo - Appairent

  43. Piconet Parameter Management (2) 802.15.3 802.15.3b MLME-PICONET-PARM-CHANGE.indication ( IndicationChangeType, BSID, MaxTXPowerLevel, PNID, ChannelIndex ) No parameter change indication • MLME-PICONET-PARM-CHANGE.indication informs FCSL of a change to a piconet parameter • IndicationChangeType indicates the parameter that has changed • Only the field indicated by IndicationChangeType is used John Sarallo - Appairent

  44. Piconet Parameter Management (3) John Sarallo - Appairent

  45. Power Management (1) 802.15.3 802.15.3b MLME-PS-SET-INFORMATION.request () MLME-PS-SET-INFORMATION.confirm ( ResultCode, MaxSupportedPSSets, NumCurrentPSSets, PSSetStructureSet, ReasonCode ) MLME-PS-SET-INFORMATION.request ( PSRequestTimeout ) MLME-PS-SET-INFORMATION.confirm ( MaxSupportedPSSets, NumCurrentPSSets, PSSetStructureSet, ResultCode ) • MLME-PS-SET-INFORMATION.request allows FCSL to retrieve the current power save sets defined by the PNC John Sarallo - Appairent

  46. Power Management (2) John Sarallo - Appairent

  47. Power Management (3) 802.15.3 802.15.3b MLME-SPS-CONFIGURE.request ( SetOperationType, SPSSetIndex, DesiredWakeInterval ) MLME-SPS-CONFIGURE.confirm ( ResultCode, SetOperationType, SPSSetIndex, WakeInterval, NextWakeTime ) MLME-SPS-CONFIGURE.request ( OperationType, SPSSetIndex, WakeBeaconInterval, PSRequestTimeout ) MLME-SPS-CONFIGURE.confirm ( OperationType, ReasonCode, SPSSetIndex, NextWakeBeacon, ResultCode ) • MLME-SPS-CONFIGURE.request allows FCSL to Join, Leave, or Create a power save set. • The DesiredWakeInterval is only used if the SetOperationType is Join • The DesiredWakeInterval is define in microseconds and not as an integral number of Superframe Durations • The WakeInterval provided by the power save set Joined or Created is defined in microseconds John Sarallo - Appairent

  48. Power Management (4) John Sarallo - Appairent

  49. Power Management (5) 802.15.3 802.15.3b MLME-PM-MODE-CHANGE.request ( PMMode ) MLME-PM-MODE-CHANGE.confirm ( ResultCode, PMMode, ReasconCode ) MLME-PM-MODE-CHANGE.indication ( PMMode, PMActiveEvent ) MLME-PM-MODE-CHANGE.request ( PMMode, PSRequestTimeout ) MLME-PM-MODE-CHANGE.confirm ( ResultCode ) MLME-PM-MODE-ACTIVE.indication ( PMActiveEvent ) • MLME-PM-MODE-CHANGE.request allows FCSL to change the current power save mode of the DEV • MLME-PM-MODE-CHANGE.indication informs FCSL of PMMode change initiated by the MLME John Sarallo - Appairent

  50. Power Management (6) 802.15.3 802.15.3b MLME-MONITOR-PM-MODE.request ( MonitorOperationType, TrgtID ) MLME-MONITOR-PM-MODE.confirm( ResultCode MonitorOperationType, TrgtID, PMMode, ReasonCode ) MLME-MONITOR-PM-MODE.indication( TrgtID, PMMode ) No request for monitoring PM Mode of other DEVs • MLME-MONITOR-PM-MODE.request allows FCSL to Start/Stop the monitoring of PM Mode changes of another DEV in the piconet • MLME-MONITOR-PM-MODE.indication informs FCSL of PM Mode changes of monitored DEVs in the piconet John Sarallo - Appairent