A1261255504tIbST

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 Voice1 585
727-2014, FAX [phone],
E-Mailsarallo_at_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.
2
802.15.3b Draft F8 Review
1394 Trade Association 1Qtr Meeting Maui, HI
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

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

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

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

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

8
1934 PAL Protocol Architecture

• 802.15.3b reference model matches 1394 PAL
  Architecture nicely
• PAL interfaces to MLME and MAC SAPs

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

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

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

12
Reset MAC/MLME
802.15.3
802.15.3b

• MLME-RESET.request (
• SetDefaultPIB,
• ResetTimeout
• )

MLME-RESET.request ( SetDefaultPIB ) MLME-RESET.c
onfirm ( ResultCode )

• 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

13
Scanning for Piconets (1)
802.15.3
802.15.3b

• MLME-SCAN.request (
• OpenScan,
• BSID,
• PNID,
• ChannelList,
• ChannelScanDuration
• )

MLME-SCAN.request ( ScanForBSID, BSID, ScanForP
NID PNID, ScanForPNCAddress, PNCAddress )

• Scan for any piconet or scan by any combination
  of BSID, PNID, and PNCAddress
• MLME automatically scans all PHY channels

14
Scanning for Piconets (2)
802.15.3
802.15.3b

• MLME-SCAN.confirm (
• NumberOfPiconets,
• PiconetDescriptionSet,
• NumberOfChannels,
• ChannelRatingList,
• ResultCode
• )

MLME-SCAN.confirm ( ResultCode, NumberOfPiconets
, PiconetDescriptionSet, NumberOfChannels, Chan
nelRatingList, ReasonCode )

• 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)

15
Scanning for Piconets (3)
16
Starting a Piconet (1)
802.15.3
802.15.3b

• MLME-START.request (
• PNID,
• BSID,
• ChannelIndex,
• SuperframeDuration,
• CAPEndTime,
• SECID,
• CAPData,
• CAPCommands,
• CAPAssociation,
• SECMode,
• MaxTXPowerLevel,
• MCTAUsed,
• MCTAAllocationRate
• )

MLME-START.request ( BSID, SECMode )

• 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

17
Starting a Piconet (2)
802.15.3
802.15.3b

• MLME-START.confirm (
• ResultCode
• )

MLME-START.confirm ( ResultCode, DEVID, DEVAddr
ess, ReasonCode )

• If start is successful, FCSL is given DEVs
  assigned DEVID for data communications and the
  DEVAddress

18
Starting a Piconet (3)
19
Stopping a Piconet
802.15.3
802.15.3b

• MLME-PNC-HANDOVER.request (
• NewPNCDEVID,
• NumberOfDEVs,
• HndOvrBeaconNumber,
• DEVInfoSet,
• HandoverStatus,
• HandoverTimeout
• )
• MLME-PNC-HANDOVER.response (
• ReasonCode
• )
• MLME-PNC-HANDOVER.confirm (
• ResultCode
• )

MLME-STOP.request ( RequestType, AllowedHandover
Time, HandoverTargetList ) MLME-STOP.confirm
( ResultCode, ReasonCode )

• 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

20
Piconet Handover (1)
802.15.3
802.15.3b

• MLME-PNC-HANDOVER.indication (
• NumberOfDEVs,
• HandoverStatus
• )
• MLME-NEW-PNC.indication (
• NewPNCDEVID,
• NewPNCDEVAddress
• )

MLME-PNC-HANDOVER.indication ( HandoverStatus ) M
LME-NEW-PNC.indication ( NewPNCDEVAddress, SECMo
de )

• 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

21
Piconet Handover (2)
22
Associating with a Piconet (1)
802.15.3
802.15.3b

• MLME-ASSOCIATE.request (
• DEVAddress,
• PSRC,
• SEC,
• PNCDesMode,
• PNCCapable,
• MaxAssociatedDEVs,
• MaxCTRqBs,
• MaxTXPower,
• SupportedDataRates,
• PreferredFragmentSize,
• ATP,
• PiconetServicesInquiry,
• NeighborPNCRequest,
• AlwaysAWAKE,
• ListenToSource,
• ListenToMulticast,
• AssocTimeout
• )

MLME-ASSOCIATE.request ( BSID, PNC, PNCDEVAddre
ss, ChannelIndex, PiconetServicesInquiry )

• MLME always synchs to target PNC before
  associating
• Parameters remove any ambiguity as to which
  piconet to join
• Device capabilities determined by MLME

23
Associating with a Piconet (2)
802.15.3
802.15.3b

• MLME-ASSOCIATE.confirm (
• DEVID,
• ATP,
• ReasonCode,
• VendorSpecificIE,
• ResultCode
• )
• MLME-DEV-ASSOCIATION-INFO.indication
• (
• DEVAddress,
• DEVID,
• SupportedDataRates,
• AssociationStatus
• )

MLME-ASSOCIATE.confirm ( ResultCode, DEVID, DEV
Address, VendorSpecificIE, ReasonCode ) MLME-ASS
OCIATE.indication ( DEVID, DEVAddress )

• 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)

24
Associating with a Piconet (3)
25
Disassociating from a Piconet (1)
802.15.3
802.15.3b

• MLME-DISASSOCIATE.request (
• TrgtID,
• ReasonCode,
• DisassocTimeout
• )
• MLME-DISASSOCIATE.confirm (
• TrgtID,
• ResultCode
• )
• MLME-DISASSOCIATE.indication (
• OrigID,
• ReasonCode
• )

MLME-DISASSOCIATE.request () MLME-DISASSOCIATE.in
dication ( DEVID, DEVAddress, 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

26
Disassociating from a Piconet (2)
27
Disassociating from a Piconet (3)
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 (
• ReceivedMACHeader,
• ReceivedFramePayload
• ReasonCode
• )

MLME-MEMBERSHIP-UPDATE.request( TrgtID, Membersh
ipStatus, SECID, KeyType, KeyOriginator, KeyIn
foLength KeyInfo ) MLME-SECURITY-ERROR.indication
( SrcID ReasonCode )

• MAC Header and Payload not passed to FCSL on
  security error

29
Security Management (2)
802.15.3
802.15.3b

• MLME-SECURITY-MESSAGE.request(
• TrgtID,
• VendorOUI,
• SecurityInformation,
• SecMsgTimeout
• )
• MLME-SECURITY-MESSAGE.indication (
• TrgtID,
• OrigID,
• VendorOUI,
• SecurityInformation
• )
• MLME-SECURITY-MESSAGE.confirm (
• ResultCode
• )

MLME-SECURITY-MESSAGE.request( TrgtID, VendorOUI
, SecurityInformationLength, SecurityInformation
) MLME-SECURITY-MESSAGE.indication
( OrigID, VendorOUI, SecurityInformationLength,
SecurityInformation )

• Security messages can be passed from FCSL to FCSL
• There is no over-air response command, so no
  confirm can be generated

30
Security Management (3)
31
Requesting DEV info from the PNC (1)
802.15.3
802.15.3b

• MLME-PNC-INFO.request (
• QueriedDEVID,
• PNCInfoTimeout
• )
• MLME-PNC-INFO.confirm (
• NumDEVInfoSet,
• DEVInfoSet,
• ResultCode
• )

MLME-DEV-INFO.request ( RequestType, QueriedDEVI
D ) MLME-DEV-INFO.confirm ( ResultCode, NumDEVIn
foSet, DEVInfoSet, ReasonCode )
MLME-DEV-INFO.indication ( NumDEVInfoSet, DEVInf
oSet )

• 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

32
Requesting DEV info from the PNC (2)
33
Security Information Retrieval (1)
802.15.3
802.15.3b

• 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

MLME-SECURITY-INFO.request ( TrgtID, RequestType
QueriedDEVID ) MLME-SECURITY-INFO.indication
( OrigID. RequestType, QueriedDEVID ) MLME-SECU
RITY-INFO.response ( OrigID, NumSecurityRecordSe
t, SecurityRecordSet ) MLME-SECURITY-INFO.confirm
( ResultCode, TrgtID, NumSecurityRecordSet, S
ecurityRecordSet, ReasonCode )

• FCSL to FCSL security information retrieval as
  before
• QueiredDEVID only used if request is for a single
  DEVs info

34
Security Information Retrieval (2)
35
Application Specific Information (1)
802.15.3
802.15.3b

• MLME-CREATE-ASIE.request (
• Cmd,
• NumBeacons,
• VendorOUI,
• TrgtID,
• ASIEIndex,
• MessageLength,
• ASIEMessage,
• CreateASIETimeout
• )

MLME-APPLICATION-SPECIFIC.request( RequestType,
ApplicationDataID, VendorOUI, ApplicationDataLen
gth, ApplicationData )

• 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

36
Application Specific Information (2)
802.15.3
802.15.3b

• MLME-CREATE-ASIE.confirm (
• VendorOUI,
• ASIEIndex,
• ResultCode
• )
• MLME-RECEIVE-ASIE.indication (
• VendorOUI,
• MessageLength,
• ASIEMessage
• )

MLME-APPLICATION-SPECIFIC.confirm( ResultCode, A
pplicationDataID, ReasonCode ) MLME-APPLICATION-S
PECIFIC.indication( NumApplicationSpecificData,
ApplicationSpecificDataSet )

• 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

37
Application Specific Information (3)
38
Piconet Services (1)
802.15.3
802.15.3b

• No requests associated with piconet
• services

MLME-ANNOUNCE-SERVICE.request( VendorOUI, Servic
eDataLength, ServiceData ) MLME-ANNOUNCE-SERVICE.
confirm( ResultCode, ReasonCode )

• 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

39
Piconet Services (2)
802.15.3
802.15.3b

• MLME-PICONET-SERVICES.indication(
• TrgtD
• )
• MLME-PICONET-SERVICES.response(
• TrgtID,
• NumPiconetServicesIEs,
• PiconetServicesIESet
• )
• MLME-PICONET-SERVICES.confirm (
• NumPiconetServicesIEs,
• PiconetServicesIESet
• )

MLME-PICONET-SERVICES.request ( TrgtD ) MLME-PICO
NET-SERVICES.confirm ( ResultCode, NumberOfServi
ces, PiconetServicesSet, ReasonCode ) MLME-PICON
ET-SERVICES.indication( NumberOfServices, Picone
tServicesSet )

• 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

40
Piconet Services (3)
41
Piconet Services (4)
42
Piconet Parameter Management (1)
802.15.3
802.15.3b

• MLME-PICONET-PARM-CHANGE.request
• (
• ChangeType,
• ChangeBeaconNumber,
• NewChannelIndex,
• SuperframeTiming,
• PNID,
• BSID,
• MaxTXPowerLevel
• )
• MLME-PICONET-PARM-CHANGE.confirm
• (
• ResultCode
• )

MLME-PICONET-PARM-CHANGE.request ( RequestChangeT
ype, BSID, MaxTXPowerLevel ) MLME-PICONET-PARM-C
HANGE.confirm ( ResultCode, ReasonCode )

• 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?

43
Piconet Parameter Management (2)
802.15.3
802.15.3b

• No parameter change indication

MLME-PICONET-PARM-CHANGE.indication ( IndicationC
hangeType, BSID, MaxTXPowerLevel, PNID, Channe
lIndex )

• 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

44
Piconet Parameter Management (3)
45
Power Management (1)
802.15.3
802.15.3b

• MLME-PS-SET-INFORMATION.request (
• PSRequestTimeout
• )
• MLME-PS-SET-INFORMATION.confirm (
• MaxSupportedPSSets,
• NumCurrentPSSets,
• PSSetStructureSet,
• ResultCode
• )

MLME-PS-SET-INFORMATION.request
() MLME-PS-SET-INFORMATION.confirm
( ResultCode, MaxSupportedPSSets, NumCurrentPSSets
, PSSetStructureSet, ReasonCode )

• MLME-PS-SET-INFORMATION.request allows FCSL to
  retrieve the current power save sets defined by
  the PNC

46
Power Management (2)
47
Power Management (3)
802.15.3
802.15.3b

• MLME-SPS-CONFIGURE.request
• (
• OperationType,
• SPSSetIndex,
• WakeBeaconInterval,
• PSRequestTimeout
• )
• MLME-SPS-CONFIGURE.confirm
• (
• OperationType,
• ReasonCode,
• SPSSetIndex,
• NextWakeBeacon,
• ResultCode
• )

MLME-SPS-CONFIGURE.request ( SetOperationType, S
PSSetIndex, DesiredWakeInterval ) MLME-SPS-CONFIG
URE.confirm ( ResultCode, SetOperationType, SPS
SetIndex, WakeInterval, NextWakeTime )

• 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

48
Power Management (4)
49
Power Management (5)
802.15.3
802.15.3b

• MLME-PM-MODE-CHANGE.request (
• PMMode,
• PSRequestTimeout
• )
• MLME-PM-MODE-CHANGE.confirm (
• ResultCode
• )
• MLME-PM-MODE-ACTIVE.indication
• (
• PMActiveEvent
• )

MLME-PM-MODE-CHANGE.request ( PMMode ) MLME-PM-MO
DE-CHANGE.confirm ( ResultCode, PMMode, Reascon
Code ) MLME-PM-MODE-CHANGE.indication ( PMMode,
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

50
Power Management (6)
802.15.3
802.15.3b

• No request for monitoring PM Mode of
• other DEVs

MLME-MONITOR-PM-MODE.request ( MonitorOperationTy
pe, TrgtID ) MLME-MONITOR-PM-MODE.confirm( Resul
tCode MonitorOperationType, TrgtID, PMMode, Re
asonCode ) MLME-MONITOR-PM-MODE.indication( TrgtI
D, PMMode )

• 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

51
Power Management (7)
52
Vendor Specific Operations (1)
802.15.3
802.15.3b

• No request for sending Vendor Specific
• Commands or Information Elements

MLME-VENDOR-SPECIFIC.request ( RequestType, Info
rmationElementID, CommandID, TrgtID, VendorOUI,
VendorDataLength, VendorData ) MLME-VENDOR-SPEC
IFIC.confirm ( ResultCode, ReasonCode ) MLME-VEN
DOR-SPECIFIC.indication( IndicationType, Informa
tionElementID, CommandID, OrigID, VendorOUI, V
endorDataLength, VendorData )

• MLME-VENDOR-SPECIFIC.request allows FCSL to send
  vendor specific over-air Commands and Information
  Elements to other FCSLs in the piconet (values
  for each are reserved in the standard for vendor
  specific use)
• RequestType is Command or Information
• CommandID is only used if the RequestType is
  Command
• InformationElementID is only used in the
  RequestType is Information
• MLME-VENDOR-SPECIFIC.indication informs FCSL of
  the reception of a vendor specific Command or
  Information Element

53
Vendor Specific Operations (2)
54
Multicast Operations (1)
802.15.3
802.15.3b

• MLME-MULTICAST-RX-SETUP.request(
• MulticastStatus,
• SrcID,
• StreamIndex
• )

MLME-MULTICAST-CONFIGURATION.request( RequestType
, MulticastAddress ) MLME-MULTICAST-CONFIGURATION
.confirm( ResultCode, MulticastAddress Multicas
tGroupID, ReasonCode )

• Allows FCSL to Join/Leave a multicast group
  associated with a IEEE 802 Multicast Address
• PNC manages unique DEVIDs for each unique
  MulticastAddress
• DEVID is allocated when first DEV joins group
• DEVID is de-allocated when last DEV leaves group
• A disassociated DEV is removed from all multicast
  groups
• The target DEVID of a stream may be the DEVID
  associated with a multicast group

55
Multicast Operations (2)
56
Timing Synchronization
802.15.3
802.15.3b

• No request for timing synchronization

MLME-BEACON-EVENT.request () MLME-BEACON-EVENT.co
nfirm ( ResultCode, ReasonCode ) MLME-BEACON-EVE
NT.indication ( BeaconNumber )

• MLME-BEACON-EVENT.request allows FCSL to activate
  MAC synchronization support
• MLME-BEACON-EVENT.indication informs FCSL of the
  start of the Beacon preamble when synchronization
  support activated
• Allows synchronization at a rate equal to the
  current Superframe Duration (65535 ms max)

57
Stream Management (1)
802.15.3

• MLME-CREATE-STREAM.request (
• TrgtID,
• DSPSSetIndex,
• StreamRequestID,
• StreamIndex,
• ACKPolicy,
• Priority,
• PMCTRqType,
• CTAType,
• CTARateType,
• CTARateFactor,
• CTRqTU,
• MinNumTUs,
• DesiredNumTUs,
• RequestTimeout
• )

• The parameters of old request were mainly the
  fields in the over-air Channel Time Request
  command (no abstraction)

58
Stream Management (2)
802.15.3b

• New request is based on stream requirements
• SourceDataRate Data rate of stream (bits per
  second)
• MaxRetries Number of transmit attempts per
  frame (reliability)
• MaxTransmitDelay Maximum amount of time a
  frame can be delayed before transmit (latency)
• MaxDataFrameSize Maximum frame size used with
  this stream
• Priority Relative value for FCSL to use to
  prioritize streams (0 7) Not 802 Priorities
• StreamGroupId Tells MLME/MAC which streams can
  be multiplexed (channel time shared among all
  streams in a group)

MLME-CREATE-STREAM.request ( RequestID, TrgtID,
SourceDataRate MaxRetries, MaxTransmitDelay, P
riority, MaxDataFrameSize, SECMode, StreamGroup
ID )

• MLME translates stream requirements into channel
  time requests
• PNC only grants a channel time request if all
  stream requirements can be satisfied including a
  max transmit delay value calculated from the
  channel time request ( lt MaxTransmitDelay)
• MLME attempts to maintain stream requirements as
  channel conditions change

59
Stream Management (3)
802.15.3
802.15.3b

• MLME-CREATE-STREAM.confirm (
• StreamRequestID,
• StreamIndex,
• AvailableNumTUs,
• ReasonCode,
• ResultCode
• )

MLME-CREATE-STREAM.confirm ( ResultCode, Request
ID, StreamIndex, ReasonCode ) MLME-CREATE-STREAM
.indication ( StreamIndex, OrigID )

• No AvailableNumTUs in confirm
• If PNC can not provide what is required, the
  stream is not created
• MLME-CREATE-STREAM.indication informs target FCSL
  of the creation of a stream

60
Stream Management (4)
61
Stream Management (5)
802.15.3
802.15.3b

• MLME-MODIFY-STREAM.request (
• StreamIndex,
• Priority,
• PMCTRqType,
• CTAType,
• CTARateType,
• CTARateFactor,
• CTRqTU,
• MinNumTUs,
• DesiredNumTUs,
• RequestTimeout
• )
• MLME-MODIFY-STREAM.confirm (
• StreamIndex,
• AvailableNumTUs,
• ReasonCode,
• ResultCode
• )

MLME-MODIFY-STREAM.request ( StreamIndex, Source
DataRate MaxRetries, MaxTransmitDelay, Priority
, MaxDataFrameSize, SECMode, StreamGroupID ) ML
ME-MODIFY-STREAM.confirm ( ResultCode, StreamInd
ex, ReasonCode )

• Same stream-based approach used to modify
  streams

62
Stream Management (6)
63
Stream Management (7)
802.15.3
802.15.3b

• MLME-TERMINATE-STREAM.request(
• StreamIndex,
• RequestTimeout
• )
• MLME-TERMINATE-STREAM.confirm(
• StreamIndex,
• ResultCode
• )
• MLME-TERMINATE-STREAM.indication(
• StreamIndex
• )

MLME-TERMINATE-STREAM.request( StreamIndex ) MLME
-TERMINATE-STREAM.confirm( ResultCode, StreamInd
ex, ReasonCode ) MLME-TERMINATE-STREAM.indication
( StreamIndex )

• The source or the target my terminate a stream
• The PNC may also terminate a stream if a higher
  priority stream requires channel time
• MLME-TERMINATE-STREAM.indication informs FCSL
  when a stream is terminated by the other DEV
  involved or the PNC

64
Stream Management (8)
65
Stream Management (9)
66
Stream Management (10)
67
MLME Primitives Removed
Deleted Primitive Reason
MLME-START-DEPENDENT An MLME-START.request from the FCLS while a DEV is associated is treated as a request to start a child piconet
MLME-SYNCH The MLME automatically synchs with a piconet as part of a MLME-ASSOCIATE.request from the FCSL
MLME-ATP-EXPIRED If the ATP (Association Timeout Period) expires at the DEV or the PNC, the DEV is disassociated and each FCSL receives an MLME-DISASSOCIATE.indication
MLME-REQUEST-KEY Request Key is an over-air command that the MLME uses to request key information from another MLME
MLME-DISTRIBUTE-KEY Distribute Key is an over-air command that the MLME uses to distribute key information to another MLME
MLME-PROBE Probe is an over-air command that the MLME uses to request information from another MLME
MLME-ANNOUNCE Announce is an over-air command that the MLME uses to announce information to another MLME
MLME-CHANNEL-STATUS Channel Status is an over-air command that the MLME uses to obtain information on channel conditions from another DEV
MLME-REMOTE-SCAN Remote Scan is an over-air command that the PNC uses to request other DEVs to perform a scan
MLME-TX-POWER-CHANGE TX Power Change is an over-air command that the MLME uses to change the transmit power of another DEV
68
MAC SAP Isoch Data (1)
802.15.3
802.15.3b

• MAC-ISOCH-DATA.request (
• StreamIndex,
• ACKPolicy
• TransmissionTimeout,
• Length,
• Data
• )

MAC-ISOCH-DATA.request ( RequestID, StreamIndex,
TransmitTimeout, MaxRetries, SECMode, Confirm
Requested, Length, Data )

• MaxRetries allows FCSL to over-ride stream
  setting for MaxRetries on a frame per frame basis
• ConfirmRequested allows FCSL to determine if a
  MAC-ISOCH-DATA.confirm is desired for this
  request
• RequestID allows FCSL to match requests to
  confirms

69
MAC SAP Isoch Data (2)
802.15.3
802.15.3b

• MAC-ISOCH-DATA.confirm (
• StreamIndex,
• ResultCode
• )
• MAC-ISOCH-DATA.indication (
• TrgtID,
• OrigID,
• StreamIndex,
• Length,
• Data
• )

MAC-ISOCH-DATA.confirm ( ResultCode, RequestID,
StreamIndex, TransmitDelay, ReasonCode ) MAC-IS
OCH-DATA.indication ( TrgtID, OrigID, StreamInd
ex, SECMode, Length, Data )

• Confirm only generated if requested
• TransmitDelay indicates how long frame took to
  transmit

70
MAC SAP Async Data (1)
802.15.3
802.15.3b

• MAC-ASYNC-DATA.request (
• TrgtID,
• OrigID,
• Priority,
• ACKPolicy,
• TransmissionTimeout,
• Length,
• Data
• )

MAC-ASYNC-DATA.request ( RequestID, TrgtID, Tra
nsmitTimeout, MaxRetries, SECMode, ConfirmReque
sted, Length, Data )

• MaxRetries allows FCSL to indicate the maximum
  number of transmit attempts
• ConfirmRequested allows FCSL to determine if a
  MAC-ASYNC-DATA.confirm is desired for this
  request
• RequestID allows FCSL to match requests to
  confirms

71
MAC SAP Async Data (2)
802.15.3
802.15.3b

• MAC-ASYNC-DATA.confirm (
• TrgtID,
• OrigID,
• Priority,
• ResultCode
• )
• MAC-ASYNC-DATA.indication (
• TrgtID,
• OrigID,
• Length,
• Data
• )

MAC-ASYNC-DATA.confirm ( ResultCode, RequestID,
TransmitDelay, ReasonCode ) MAC-ASYNC-DATA.indic
ation ( TrgtID, OrigID, SECMode, Length, Data
)

• Confirm only generated if requested
• TransmitDelay indicates how long frame took to
  transmit

72
Focus on Stream Management

• How does a DEV convey the maximum transmit delay
  requirements to the PNC with the existing Channel
  Time Request command?
• (We will look at IEEE 803.15 document
• 15-04-0610-01-003b-argument-for-pnc-controlled-la
  tency.ppt at this point if there is an interest
  in the answer to this question)

73
Issues for 1394 PAL

• Synchonization
• Variable Bit-Rate Streams?
• ? (If uncovered during review)
• ?
• ?
• ?
• ?

74
Synchronization Issue

• The MAC/MLME controls the Superframe Duration
• Current 1394 PAL relies on a maximum Superframe
  Duration of 10ms for synchronization purposes
• 3b does provide a means to synchronize all DEVs
  to the transmission of a beacon
• 3b allows any DEV to put Application Specific
  information in a beacon

75
Synchronization Discussion Points

• What is the source of the 10ms Superframe
  requirement?
• What if 802.15.3 specified a more accurate
  crystal?
• Are there other ways to do synchronization?
• Do wireless 1394 devices really need to maintain
  sync over the air?
• Do we want a closed wireless community in which
  only 1394 devices can communicate?

76
Variable Bit-Rate Issue

• The current MLME interface does not appear to
  support variable bit-rate streams.
• Is this a comment we want to submit?