IEEE P802.15 Wireless Personal Area Networks · MLME SAP defined in IEEE Std 802.15.3-2003 should...

16 September, 2004 IEEE - 04/401r2

John C. Sarallo - Appairent Technologies

g ect

ein.

y

Submission

IEEE P802.15Wireless Personal Area Networks

Project IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs)

Title FCSL/PAL - MAC/MLME SAP Proposal

Date Submitted

[16, September 2004]

Source [John Sarallo][Appairent Technologies][150 Lucius Gordon Drive, West Henrietta, NY 14586]

Voice: [585-727-2014]Fax: [585-214-2461]E-mail: [[email protected]]

Re: []

Abstract [This document contains a list or proposed changes to IEEE Std 802.15.3.]

Purpose [The purpose of this document is to propose changes to IEEE Std 802.15.3 to improve compatibility, performance and clarity in the standard.]

Notice This document has been prepared to assist the IEEE P802.15. It is offered as a basis for discussion and is not binding on the contributinindividual(s) or organization(s). The material in this document is subjto change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained her

Release The contributor acknowledges and accepts that this contribution becomes the property of IEEE and may be made publicly available bP802.15.



/neighbor)

ble

T requestsss results

ent entity)

eaconbecause this is where encryption

y), TX power adaptationstatus, scan)affects CTAs)ID and PNC MAC address)

async. time requirements.EV)

Submission

1. Introduction

At the July 2004 802.15.3b meeting in Portland it was determined that MLME SAP defined in IEEE Std 802.15.3-2003 should be modified in consideration to the DME functionality defined in the standard be part of the MLME entity. This allows the MLME SAP to be a defined exposed interface for a FCSL. This document proposes this new MLME SAP. Because the MLME SAP is to be an exposed interface, the MAC SAP would be assumed to be exposed as well. Therefore, a new more imple-mentable MAC SAP interface is also presented in this document.

2. FCSL - MAC/MLME Functional Division

Document 297/r2 presented a division of functionality between the FCSL, DME, PME (Piconet Management Entity), and MAC/MLME. This same functional division is shown below with the DME and PME functionality of 297/r2 moved under MAC/MLME functionality. The functional division shown below was used as a guide when development the MLME SAP and MAC SAP primitives in this document.

FCSL/PAL

• Map Upper layer identifier (e.g., MAC address) to DEVID for data frames

• Maintain List of available DEVs• Map upper layer stream IDs to 15.3 indices• Pass data to MAC• Fragmentation• Maintain list of DEVIDs • Convert Async Data to MAC SAP Async Data Requests• Rate adjustment decisions

PNC MAC/MLME

• Select Piconet channel• Associate/disassociate DEVs• Handover • Scan for interference

• Start/stop network (including child• Change PNID/BSID• Maintain list of associate DEVs• Allocate channel time• Track PM DEVs• Change Superframe Duration• Change Superframe Location

DEV MAC/MLME

• Master MAC Address - DEVID ta• Stream index only • Start/Stop scan• Associate/disassociate • Track Security Problems• Determine PM Mode• Convert stream requirements to C• Determine when to scan and proce• KOME (Key originator managem• Change Data keys• DEVID and Stream Index only• Data queues• 15.3 Fragmentation/Reassembly• ACKs • On-air timing – data, command, b• Keep data and management keys (

happens)• Secure frame processing• Channel quality (e.g. FER and retr• Perform scan and report capacity (• Rate adaptation implementations (• Identify current Piconet (BSID, PN• Prepare Async CTRq’s and tracks• Manage ATP to stay associated (D• Track ATPs for DEVs (PNC)



ing layer of some sort will be ME SAP to support multiple

uld be identified in the standard as ort higher layers.

Submission

3. Standard Reference Model

Because it is being proposed that the DME functionality define in IEEE Std 802.15.3-2003 be considered part of the MLME functionality, the ref-erence model shown in Figure 3 of the standard would no longer be valid. The figure below shows a proposal for a new reference model to be included in Clause 6 (and in Appendix A).

Proposed Reference Model (Figure 3)

4. Proposed MLME SAP Primitives

The table in this section proposes MLME primitives, their purpose, and their parameters based on a MLME entity that contains the DME func-tionality currently define in IEEE Std 802.15.3-2003. This interface would be the SAP for a FCSL using the 802.15.3 MLME.

Note that the MLME SAP as specified does not inherently support multi-ple FCSLs at one time (for example, two separate FCSLs requiring pico-nets with very different superframe durations). It is assumed that an

additional coordination and multiplexrequired above the MAC SAP and MLFCSLs at one time.

The MLME/SAP presented below wothe minimal required interface to supp

MAC SAP

PHY SAP

PHY layer

802.15.3Media access control

sublayer (MAC)

MAC

PHY

MLME

FCSL

Frame convergencesublayer

FCSL SAP

PLME

PLME SAP

MLME SAP



arameters (Values)

ERROR)

, FALSE)

, FALSE)

(TRUE, FALSE)

S, FAILURE)

t

cDataSet

icData

Submission

MLME Primitive Purpose New P

MLME-RESET.request A request to reset the MAC/MLME. SetDefaultPIB

MLME-RESET.confirm After any reset (self initiated or MLME-RESET.request) the MAC/MLME will send a MLME-RESET.confirm to the FCSL to indicate that it is ready to accept requests.

ResultCode (READY,ReasonCode

MLME-SCAN.request A request to scan all channels for piconets. The FCSL can optionally supply a BSID, PNID, or PNCAddress to scan for.

ScanForBSID (TRUEBSIDScanForPNID (TRUEPNIDScanForPNCAddress PNCAddress

MLME-SCAN.confirm Report the piconets found as a result of a MLME-SCAN.request. Basic information about each piconet found is returned including any Application Specifc Data broadcast by a PNC in the Beacon.

Note that Piconet Services are not broadcast in the Beacon and can therefore not be supplied as part of a scan result.

ResultCode (SUCCESReasonCodeNumberOfPiconetsPiconetDescriptionSe - BSID - PNID - PNCAddress - ChannelIndex - SECMode - ApplicationSpecifi - VendorOUI - Length - ApplicationSpecifChannelRatingSet - ChannelIndex - ChannelRating



LSE)

S, FAILURE)

ntity) identiy)

OWN, HANDOVER)estType = HANDOVER)

S, FAILURE)

y (TRUE, FALSE)

S, FAILURE)

ation

arameters (Values)

Submission

MLME-START.request A request to start operation as a PNC. The FCSL specifies the BSID, SuperframeDuration, SECMode, and MaxTXPowerLevel for the piconet.

Note: A start request while associated will result in the start of a dependent piconet.

BSIDSuperframeDurationSECMode (TRUE, FAMaxTXPowerLevel

MLME-START.confirm Report result of the start request. A ResultCode of FAILURE is returned if the MLME can not support the parameters supplied in the MLME-START.request

ResultCode (SUCCESReasonCodeDEVID (for DEV ideDEVAddress (for DEV

MLME-STOP.request A request to stop operation as a PNC. The FCSL/MAC can specify if the shutdown of the piconet should be immediate or if there is time for an attempt to handover control of PNC operations to another DEV.

RequestType (SHUTDAllowedTime (if RequHandoverTrgtSet - DEVID

MLME-STOP.confirm Report result of the stop request ResultCode (SUCCESReasonCode

MLME-ASSOCIATE.request A request to associate with a specifc piconet.The MLME will automatically synch with the target piconet before attempting to send an Association Request command. The capabilities of the DEV are implementation specific or are obtained from the PIB. The FCSL may request the PNC return the available Piconet Services after successful associa-tion.

BSIDPNIDPNCAddressChannelIndexPiconetServicesInquir

MLME-ASSOCIATE.confirm Report the result of associate request.

Note, the Association Response command as cur-rently defined may return a single Vendor IE.

ResultCode (SUCCESReasonCodeDEVIDDEVAddressVendorOUILengthVendorSpecificInform




ANCELLED)

E, ALL)

S, FAILURE)

arameters (Values)

Submission

MLME-ASSOCIATE.indication Report the association of a new DEV in the piconet. DEVIDDEVAddress

MLME-DISASSOCIATE.request

A request to disassociate from the current piconet.

Note: An FCSL acting as PNC should not send thisrequest.

ReasonCode

MLME-DISASSOCIATE.indication

Report the disassociation of a DEV from the pico-net. It may be this DEV that is now disassociated.

DEVIDDEVAddressReasonCode

MLME-HANDOVER.indication

Report that this DEV is the target, or is no longer the target of a PNC handover

Status (STARTED, C

MLME-NEW-PNC.indication Report a change in PNC due to handover event.

Note: If this DEV is the new PNC the MLME will send this indication to the FCSL upon receipt of the first Handover IE in the Beacon. The FCSL shall recognize that it will be the new PNC FCSL and shall request the necessary security information from the previous PNC.

BSIDPNIDPNCAddressSuperframeSizeChannelIndexSECMode

MLME-DEV-INFO.request A request for the membership status of one or more DEVs associated with the piconet.

RequestType (SINGLQueriedDEVID

MLME-DEV-INFO.confirm Result of the request for membership status of one or more DEVs associated with the piconet.

ResultCode (SUCCESReasonCodeNumberOfDevsDevInfoSet - DEVID - DEVAddress - MembershipStatus




(ASSOCIATED, MEMBER)

EMOVE, MODIFY, COUNT) (if RequestType = REMOVE)

estType = COUNT)

ata

S, FAILURE)

(assigned by PNC)

ataSeticIDEMOVED)

cData

EMOVE, MODIFY)Type /= ADD)

S, FAILURE)

y PNC)

arameters (Values)

Submission

MLME-DEV-INFO.indication Report a change in the mebership status of one or more DEVs associated with the piconet

NumberOfDevsDevInfoSet - DEVID - DEVAddress - MembershipStatus

MLME-APPLICATION-SPECIFIC-DATA.request

A request to announce, remove, or modify applica-tion specific information.

NOTE: A new request command is required to sup-port this primitive

RequestType (ADD, RApplicationSpecificIDCountValue (if RequVendorOUILengthApplicationSpecificD

MLME-APPLICATION-SPECIFIC-DATA.confirm

Result of the request to announce, remove, or modify application specific information.

NOTE: A new response command is required to sup-port this primitive

ResultCode (SUCCESReasonCodeApplicationSpecificID

MLME-APPLICATION-SPECIFIC-DATA.indication

Report a change in application specific information.

NOTE: In order for this primitive to only report changes to application specific data, the Applica-tionSpecificID would need to be added to the ASIE.

NumberOfDataApplicationSpecificD - ApplicationSpecif - Status (ADDED, R - VendorOUI - Length - ApplicationSpecifi

MLME-ANNOUNCE-SERVICE.request

A request to announce or remove the availability of a piconet service provided by this DEV.

NOTE: If we need the ability to remove a service previously announced to the PNC then a new request command is required to support this primitive

RequestType (ADD, RServiceID (if RequestVendorOUILengthPiconetServicesData

MLME-ANNOUNCE-SERVICE.confirm

The result of the request to announce or remove the availability of a piconet service provided by this DEV.

ResultCode (SUCCESReasonCodeServiceID (assigned b




SS, FAILURE)

ta

ta

MATION, COMMAND)pe = INFORMATION)estType = COMMAND)

S, FAILURE)

arameters (Values)

Submission

MLME-PICONET-SERVICES.request

Request information about the piconet services offered by the piconet or by a specific DEV.

TrgtID

MLME-PICONET-SERVICES.confirm

Report result of the request for piconet services information.

ResultCode (SUCCEReasonCodeNumberOfServicesPiconetServicesSet - DEVID - VendorOUI - Length - PiconetServicesDa

MLME-PICONET-SERVICES.indication

Report the piconet services offered by the piconet.

Note: This primitive will be generated any time piconet services information is received.

NumberOfServicesPiconetServicesSet - DEVID - VendorOUI - Length - PiconetServicesDa

MLME-VENDOR-SPECIFIC.request

Request to send vendor specific information to another device in the piconet as either an Informa-tion Element or as a Command.

RequestType (INFORElementId (RequestTyCommandType (RequTrgtIdVendorOUILengthVendorSpecificData

MLME-VENDOR-SPECIFIC.confirm

The result of the request to send vendor specific information to another device in the piconet.

Note: If an Vendor Specific command is generated from the MLME-VENDOR-SPECIFIC.request, then this confirm can only indicate that the command was transmitted and not that a cooresponding Response command was received.

ResultCode (SUCCESReasonCode




RMATION, COMMAND)Type = INFORMATION)ationType = COMMAND)

U payload in Kbytes per second)mum MSDU payload in bytes)

% if ACKPolicy = Imm-ACK)

S, FAILURE)

U payload in Kbytes per second)

arameters (Values)

Submission

MLME-VENDOR-SPECIFIC.indication

Report the reception of vendor specific information.

Note: This indication would be generated any time a VendorSpecifc IE or VendorSpecific command was received.

IndicationType (INFOElementId (IndicationCommandType (IndicOrigIDVendorOUILengthVendorSpecificData

MLME-CREATE-STREAM.request

A request to create an an isochronous stream from the requesting DEV to another DEV in the piconet.

Note: There is a question about whether the FCSL should supply the default number of retries per frame (NumRetries), or if the MLME should deter-mine the proper number of retries depending on the value of MaxDroppedFrames. Note also that it is being proposed that the NumRetries value can be modified with each MAC-xxx-DATA.request.

StreamRequestIDTrgtIDDSPSSetIndexACKPolicyNumRetriesUserPriorityPMCTRqTypeMaxThroughput (MSDMaxFrameSize (MaxiMaxLatency (msec)MaxJitter (msec)MaxDroppedFrames (

MLME-CREATE-STREAM.confirm

The result of the request to create an an isochronous stream from the requesting DEV to another DEV in the piconet.

ResultCode (SUCCESReasonCodeStreamRequestIDStreamIndexMaxThroughput (MSDMaxLatency (msec)MaxJitter (msec)

MLME-CREATE-STREAM.indication

An indication to a DEV that it is the destination of an isochronous stream.

StreamIndex,OrigID





% if ACKPolicy = Imm-ACK)

S, FAILURE)

U payload in Kbytes per second)


SS, FAILURE)

arameters (Values)

Submission

MLME-MODIFY-STREAM.request

A request to modify an an isochronous stream from the requesting DEV to another DEV in the piconet

StreamIndexUserPriorityPMCTRqTypeDSPSSetIndexACKPolicyNumRetriesMaxThroughput (MSDMaxFrameSize (MaxiMaxLatency (msec)MaxJitter (msec)MaxDroppedFrames (

MLME-MODIFY-STREAM.confirm

The result of the request to modify an an isochronous stream from the requesting DEV to another DEV in the piconet

ResultCode (SUCCESReasonCodeStreamIndexMaxThroughput (MSDMaxLatency (msec)MaxJitter (msec)

MLME-MODIFY-STREAM.indication

An indication to the originator of an isochronous stream of a change in the quality parameters for the stream

StreamIndexMaxThroughput (MSDMaxFrameSize (MaxiMaxLatency (msec)MaxJitter (msec)

MLME-TERMINATE-STREAM.request

A request by either the originator or the target of an isochronous stream to terminate the stream

StreamIndex

MLME-TERMINATE-STREAM.confirm

The result of the request by either the originator or the target of an isochronous stream to terminate the stream

ResultCode (SUCCEReasonCodeStreamIndex




S, FAILURE)

Size (Bps)ec)

mes (if ACKPolicy = Imm-ACK)

IZE, POWER)

S, FAILURE)

arameters (Values)

Submission

MLME-TERMINATE-STREAM.indication

An indication that an isochronous stream has been terminated. If received by the originator it is an indi-cation that the stream was terminated by the target DEV for the stream or the PNC. If received by the target it is an indication that the stream was termi-nated by the source DEVID for the stream or termi-nated by the PNC.

Note: In order to provide a reason code with this primitive, the definition of a Null CTA must be modi-fied to pass a reason code.

StreamIndexReasonCode

MLME-STREAM-STATUS.request

A request by the originator of an isochrohous stream for a measurment of the quality parameters for the stream.

StreamIndex

MLME-STREAM-STATUS.confirm

The result of a request by the originator of an isoch-rohous stream for a measurment of the quality parameters for the stream.

ResultCode (SUCCESReasonCodeStreamIndexMeasurementWindowMeasuredThroughputMeasuredLatency (msMeasuredJitter (msec)MeasuredDroppedFra

MLME-PICONET-PARM-CHANGE.request

A request by a DEV currently acting as PNC to change the BSID, Superframe Size, or Max TX Power Level for the picoinet.

ChangeType (BSID, SBSIDSuperframeDurationMaxTXPowerLevel

MLME-PICONET-PARM-CHANGE.confirm

The result of the request by a DEV currently acting as PNC to change the BSID, Superframe Size, or Max TX Power Level for the picoinet.





SID, SIZE, POWER,

PNID) BSID)ChangeType = SIZE)hangeType = POWER)

eType = CHANNEL)

, STOP)

S, FAILURE)

t

arameters (Values)

Submission

MLME-PICONET-PARM-CHANGE.indication

An indication to a DEV not acting as a PNC that the BSID, Superframe Size, or Max TX Power Level of the piconet has changed.

ChangeType (PNID, BCHANNEL)PNID (ChangeType =BSID (ChangeType =SuperframeDuration (MaxTXPowerLevel (CChannelIndex (Chang

MLME-BEACON-EVENT.request

Request activation of the MAC synchronization sup-port facility

RequestType (START

MLME-BEACON-EVENT.confirm

Report result of request to activate the MAC syn-chronization support facility


MLME-BEACON-EVENT.indication

Report beginning of Beacon PHY preamble TimeSinceBeaconStarBeaconNumber

MLME-MEMBERSHIP-UPDATE.request

A request that the membership status, SECID and keying information associated with a securityrelationship be included or updated.

TrgtIDMembershipStatusSECIDKeyTypeKeyOriginatorKeyInfoLengthKeyInfo

MLME-SECURITY-MESSAGE.request

A request to send security related information to another DEV in the piconet.

TrgtIDVendorOUILengthSecurityMessage

MLME-SECURITY-MESSAGE.indication

Report security related information received from another DEV in the piconet.

OrigIDVendorOUILengthSecurityMessage




thd

ILABLE-KEY, FAILED-, BAD-TIME-TOKEN)

et

gth

S, FAILURE)

et

gth

arameters (Values)

Submission

MLME-SECURITY-ERROR.indication

Report failed security operation ReceivedMACHeaderReceivedPayloadLengReceivedFramePayloaSrcIDReasonCode (UNAVASECURITYCHECK

MLME-SECURITY-INFO.request

A request for security information regarding either a single DEV or all of the DEVs in the piconet.

TrgtIDQueriedDEVID

MLME-SECURITY-INFO.indication

Indicates the reception of a request by a DEV for security information it manages regardingeither a specific DEV or all of the DEVs in the pico-net.

OrigIDQueriedDEVID

MLME-SECURITY-INFO.response

A response to the reception of a request by a DEV for security information it manages regardingeither a specific DEV or all of the DEVs in the pico-net.

OrigIDNumSecurityRecordSSecurityRecordSet - DEVAddress - DEVID - VerificationInfoLen - VerificationInfo

MLME-SECURITY-INFO.confirm

An indication of the receipt of sercurity information. ResultCode (SUCCESReasonCodeTrgtIDNumSecurityRecordSSecurityRecordSet - DEVAddress - DEVID - VerificationInfoLen - VerificationInfo

MLME-MULTICAST-INFORMATION.request

Request information about existing Multicast groups.

<none>




S, FAILURE)

stGroupsGroups

VE)

S, FAILURE)

by PNC)

S, FAILURE)

al

ATE, JOIN, LEAVE)ionType /= CREATE)

arameters (Values)

Submission

MLME-MULTICAST-INFORMATION.confirm

Result of request for information about existing Mul-ticast groups.

ResultCode (SUCCESReasonCodeMaxSupportedMulticaNumCurrentMulticastMulticastGroupSet - MulticastGroupID - MembersSet - DEVID

MLME-MULTICAST-CONFIGURATION.request

Request to join or leave a Multicast group. Operation (JOIN, LEAMulticastAddress

MLME-MULTICAST-CONFIGURATION.confirm

Result of request to join or leave a Multicast group. ResultCode (SUCCESReasonCodeMulticastAddressMcstGrpID (assigned

MLME-PS-SET-INFORMATION.request

A request for the power save set information from the PNC.

<none>

MLME-PS-SET-INFORMATION.confirm

Result of the request for the power save set informa-tion from the PNC.

ResultCode (SUCCESReasonCodeMaxSupportedPSSetsNumCurrentPSSetsPSSetStructureSet - PSSetIndex - BeaconWakeInterv - MembersSet - DEVID

MLME-SPS-CONFIGURE.request

Request to create, join, or leave a power save group. OperationType (CRESPSSetIndex (OperatBeaconWakeInterval




S, FAILURE)

ATE, JOIN, LEAVE)

S, FAILURE)

Mode = ACTIVE)

BLE, DISABLE)

S, FAILURE)

BLE, DISABLE)

arameters (Values)

Submission

MLME-SPS-CONFIGURE.confirm

Result of the request to create, join, or leave a power save group.

ResultCode (SUCCESReasonCodeOperationType (CRESPSSetIndex BeaconWakeInterval

MLME-PM-MODE-CHANGE.request

A request to change the current power save mode. PMMode

MLME-PM-MODE-CHANGE.confirm

Result of the request to change the current power save mode.

ResultCode (SUCCESReasonCodePMMode

MLME-PM-MODE-CHANGE.indication

Report an unrequest change to the current power save mode.

PMModePMActiveEvent (if PM

MLME-MONITOR-PM-MODE.request

Request to enable or disable the monitoring of the power save mode of another DEV in the piconet.

OperationType (ENATrgtID

MLME-MONITOR-PM-MODE.confirm

The result of the request to enable or disable the monitoring of the power save mode of another DEV in the piconet.

ResultCode (SUCCESReasonCodeOperationType (ENATrgtIDPMMode (of TrgtID)

MLME-MONITOR-PM-MODE.indication

Report a change in the power save mode of a DEV in the piconet that is currently being monitored.

TrgtIDPMMode (of TrgtID)




LME.

nitiated by the MLME itself.

primitive is now used to request the piconet.

ME as needed.

e MLME as needed.

AST-INFORMATION and ION are now used to inquiry

respectively.

uality of a stream due to many fac-he channel. The new primitive laces this primitive. The MLME nds.

Submission

5. MLMEs Removed or Renamed

This section lists the MLME primitives that are no longer required due to the fact that DME functionality is contained in the MLME entity.

5.1 MLME-START-DEPENDENT

If the MLME receives a request to start a piconet an attempt to start a dependent piconet will automatically be started if there are no open chan-nels for a new piconet.

5.2 MLME-SYNCH

If the MLME receives a request to associate with a piconet, the MLME will automatically synch with the target piconet before attempting an association.

5.3 MLME-ATP-EXPIRED

The MLME will maintain an ATP timer required by the standard. If the ATP timer expires, the MLME will notify the FCSL with a MLME-DIS-ASSOCIATE.indication. The ReasonCode will indicate that the reason for the disassociation was that the ATP timer expired.

5.4 MLME-DEV-ASSOCIATION-INFO (replaced with MLME-DEV-INFO)

The new MLME-DEV-INFO.confirm primitive will be used to report info requested by the FCSL about one or all DEVs in the piconet. The new MLME-DEV-INFO.indication primitive will report unsolicited information about one or all DEVs in the piconet to the FCSL.

5.5 MLME-REQUEST-KEY

Key origination is done in the MAC/MLME.

5.6 MLME-DISTRIBUTE-KEY

Key origination is done in the MAC/M

5.7 MLME-PNC-HANDOVER

Handover of PNC operations will be i

5.8 MLME-PNC-INFO

The new MLME-DEV-INFO.request information about one or all DEVs in

5.9 MLME-PROBE

Probe commands are issued by the ML

5.10 MLME-ANNOUNCE

Announce commands are issued by th

5.11 MLME-MULTICAST-RX-SETUP

The new primitives MLME-MULTICMLME-MULTICAST-CONFIGURATabout and configure multicast groups

5.12 MLME-CHANNEL-STATUS

The FCSL needs to know the overall qtors and not just the current status of tMLME-STREAM-QOS-STATUS repmay still issue Channel Status comma


Submission
5.13 MLME-REMOTE-SCAN

The MAC/ MLME independently issues a Remote Scan Request com-mand to other devices in the piconet as needed for interference mitiga-tion.

5.14 MLME-TX-POWER-CHANGE

The MLME independently issues a TX Power Change Request command to other devices it is communicating with to increase QOS.

5.15 MLME-PM-MODE-ACTIVE

Replaced be MLME-PM-MODE-CHANGE.indication.

6. Proposed MAC SAP Primitives

The table in this section proposes MAC primitives, their purpose. This interface would be the SAP for a FCSL using the 802.15.3 MAC.

Note that the MAC SAP as specified does not inherently support multiple FCSLs at one time. It is assumed that an additional coordination and mul-tiplexing layer of some sort will be required above the MAC SAP (and MLME SAP) to support multiple FCSLs at one time.

The MAC SAP presented below would be identified in the standard as the minimal required interface to support higher layers.



rameters (Values)

concurrent requests)

r frame control)LSE)UE, FALSE)

S, FAILURE)

LSE)

concurrent requests)

r frame control)LSE)UE, FALSE)

S, FAILURE)

Submission

MAC Primitive Purpose New Pa

MAC-ASYNC-DATA.request Request the transfer asynchronous data to another DEV.

RequestID (to supportTrgtIDUserPriorityACKPolicyTransmissionTimeoutNumRetires (allows peSECMode (TRUE, FAConfirmRequested (TRLengthData

MAC-ASYNC-DATA.confirm Result of request to transfer asynchronous data to another DEV (only generated if confirmation was requested).

ResultCode (SUCCESReasonCodeRequestID

MAC-ASYNC-DATA.indication Report the reception of asynchronous data from another DEV.

OrigIDSECMode (TRUE, FALengthData

MAC-ISOCH-DATA.request Request the transfer isochronous data associated with a specific stream to another DEV.

RequestID (to supportStreamIndexTrgtIDACKPolicyTransmissionTimeoutNumRetries (allows peSECMode (TRUE, FAConfirmRequested (TRLengthData

MAC-ISOCH-DATA.confirm Result of request to transfer isochronous data associated with a specific stream to another DEV (only generated if confirmation was requested).

ResultCode (SUCCESReasonCodeRequestIDSteamIndex



LSE)

rameters (Values)

Submission

MAC-ISOCH-DATA.indication Report the reception of isochronous data associ-ated with a specific stream data from another DEV.

StreamIndexOrigIDSECMode (TRUE, FALengthData

MAC Primitive Purpose New Pa


Submission
7. Modified MSCs

This section provides suggested new MSCs for those MSCs that cur-rently exist in the standard. The suggested MSCs assume the MAC/MLME SAPs defined in this document.



sted

ossible results of a primitive est

RequestTimer(timeout)

MAC/MLME

Actioncompleted

successfully



ilure>

Actioncompletedwith error

Submission

Current

Figure 91 - MSC showing examples of primitive timers

Sugge

Figure 91 - MSC showing the prequ

MLME-XXX.request with (timeout)

RequestTimer(timeout)ALT

DME MAC/MLME

MLME-XXX.confirm withResultCode = COMPLETED

Actioncompleted


MLME-XXX.confirm withResultCode = TIMEOUT

MLME-XXX.request

ALT

FCSL

MLME-XXX.confirm withResultCode = SUCCESS

MLME-XXX.confirm withResultCode = FAILURE,

ReasonCode = TIMEOUT

MLME-XXX.confirm withResultCode = FAILURE,

ReasonCode = <reason for fa



sted

r scan operation

DEVMAC/MLME

Keyreq = requestcfm = confirm

=

erform scanprocedure

Submission

Current

Figure 92 -MSC for scan operation

Sugge

Figure 92 -MSC fo

DEVMAC/MLME

DEVDME


MLME-SCAN.req

MLME-SCAN.cfm

with ResultCode =SUCCESS

Perform scanprocedure

DEVFCSL

MLME-SCAN.req

MLME-SCAN.cfmwith ResultCode

SUCCESS

P



sted

starting a piconet

DEVMAC/MLME


=

Piconetinitializationprocedure

Submission

Current

Figure 93 - MSC for starting a piconet

Sugge

Figure 93 - MSC for

DEVMAC/MLME

DEVDME


MLME-START.req

MLME-START.cfm



DEVFCSL

MLME-START.req

MLME-START.cfm

with ResultCodeSUCCESS



sted

synchronizing with a PNC

ion process.

VED

Submission

Current

Figure 125 - MSC of a DEV synchronizing with a PNC

Sugge

Figure 125 - MSC of a DEV

• Synching now part of the associat

DEVMAC/MLME

PNCMAC/MLME

DEVDME

Keyreq = requestcfm = confirmPNID = Piconet ID

beaconwith PNID oftarget piconet

MLME-SYNCH.req

MLME-SYNCH.cfm


UnSynched

Synched

SyncTimeout

REMO



sted

DEV-2 associating

PNCFCSL

DEV-3MAC/MLME

DEV-3FCSL

Keyreq = requestind = indicationcfm = confirmaddr=address

Association IE,Addr=DEV-2 Addr,Assoc

DEV-2 isUnassociated

MLME-ASSOCIATE.ind

MLME-SOCIATE.ind

P

DEV-2 is Associated

-2 is Associated

DEV-2 isnassociated

ormationand

Submission

Current

Figure 102 - MSC of DEV-2 associating

Sugge

Figure 102 - MSC of

DEV-2MAC/MLME

PNCMAC/MLME

DEV-2DME

PNCDME

DEV-3MAC/MLME

DEV-3DME

Association Requestcommand with

DEVID = UnassocID,DEV addr = DEV-2 addr

Association Responsecommand with

DestID= UnassocID,DEVID= 0xzz,

DEV addr = DEV-2 addr

Keyreq = requestind = indicationrsp = responsecfm = confirmaddr=address

MLME-ASSOCIATE.req

MLME-ASSOCIATE.cfmw/ DEVID=0xzz

Association Requestcommand withSrcID = 0xzz

MLME-ASSOCIATE.ind

DEVAddr=DEV-2 Addr

DEVID=UnassocID

MLME-ASSOCIATE.rsp

DEVID = 0xzz

Imm ACK withDestID=0xzz

Associated

Unassociated

beacon with DEV Association IE,DEVID=0xzz, DEVAddr=DEV-2 Addr,

Status=Assoc

Associated

MLME-DEV-ASSOCIATE-

INFO.indwith DEVID=0xzz

DEVAddr =DEV-2 Addr,

Status=Assoc

Imm-ACK withDestID = UnassocID

AssocTimeout

MLME-ASSOCIATE.ind

DEVAddr=DEV-2 AddrDEVID=0xzz

beacon

beacon

ATP

DEV-2MAC/MLME

PNCMAC/MLME

DEV-2FCSL

Association Requestcommand with

DEVID = UnassocID,DEV addr = DEV-2 addr

Association Responsecommand with

DestID= UnassocID,DEVID= 0xzz,


MLME-ASSOCIATE.req

MLME-ASSOCIATE.cfm

Association Requestcommand withSrcID = 0xzz,


Associated

Unassociated andUnsynched

beacon with DEVDEVID=0xzz, DEV

Status=

AssocTimeout

AS

AT

Association Responsecommand withDestID= 0xzz,DEVID= 0xzz,


DEV

U

MLME-DEV-INFO.ind

PNC Infcomm

DEV-3 is Associated

beaconwith PNID, BSID,

and PNCAddress oftarget piconet

SyncTimeout



sted

iconet Services command to esponse to a request in the process

PNCMAC/MLME

PNCFCSL

rvices Inquiry field set to one in thercId set to the newly assigned DEVID.-2 assigned DEVID = 0xzz

ervicesand

Submission

Current

Figure 103 - PNC sending the Piconet Services command to a newly associated DEV in response to a request in the

association process

Sugge

Figure 103 - PNC sending the Pa newly associated DEV in r

association

DEV-2MAC/MLME

PNCMAC/MLME

DEV-2DME

PNCDME

Keyind = indicationrsp = responsecfm = confirm

DEV-2 association process, Piconet Services Inquiry field set to one in theAssociation Request command with the SrcId set to the newly assigned DEVID.

Association is successful, DEV-2 assigned DEVID = 0xzz

MLME-PICONET-

SERVICES.rspTrgtID=0xzz

MLME-PICONET-

SERVICES.cfm

Piconet Servicescommand withDestID = 0xzz

Imm-ACK

MLME-PICONET-

SERVICES.indTrgtID=0xzz

DEV-2MAC/MLME

DEV-2FCSL

Keyind = indication

DEV-2 association process, Piconet SeAssociation Request command with the S

Association is successful, DEV

MLME-PICONET-

SERVICES.ind

Piconet Scomm



sted

ed disassociation MSC

PNCFCSL/]\\

DEV-3MAC/MLME

DEV-3FCSL

Keyreq = requestind = indication

LME-OCIATE.ind

MLME-DISASSOCIATE.ind

ssociation IE,s=disassociated

Associated DEV-2 is Associated

Unassociated

DEV-2 is Unassociated

Submission

Current

Figure 104 - DEV initiated disassociation MSC

Sugge

Figure 104 - DEV initiat

DEV-2MAC/MLME

PNCMAC/MLME

DEV-2DME

PNCDME

DEV-3MAC/MLME

DEV-3DME

DisassociationRequest command

with OrigID = DEV-2

Keyreq = requestind = indicationcfm = confirm

MLME-DISASSOCIATE.req

MLME-DISASSOCIATE.cfm


MLME-DISASSOCIATE.indwith OrigID = DEV-2

UnAssociated

Associated Associated

MLME-DEV-ASSOCIATION-

INFO.ind withDEVID = DEV-2

Status = Disassoc

Imm-ACK

DisassocTimeout

beacon with DEV Association IE,DEVID=DEV-2, status=disassociated

beacon

DEV-2MAC/MLME

PNCMAC/MLME

DEV-2FCSL


Reason Code =DEV Leaving Piconet

MLME-DISASSOCIATE.req

MDISASS

beacon with DEV ADEVID=DEV-2, statu

DEV-2 isAssociated

Unassociated

DEV-2 is



sted

ed disassociation MSC

PNCFCSL

DEV-3MAC/MLME

DEV-3FCSL

Keyind = indication

ssociation IE,s=disassociated


V-2P

MLME-SOCIATE.ind

Unassociated

DEV-2 is Unassociated

DEV-2 is Associatedis Associated

Submission

Current

Figure 105 - PNC initiated disassociation MSC

Sugge

Figure 105 - PNC initiat

DEV-2MAC/MLME

PNCMAC/MLME

DEV-2DME

PNCDME

DEV-3MAC/MLME

DEV-3DME




UnAssociated

Associated Associated

MLME-DEV-ASSOCIATION-

INFO.ind withDEVID = DEV-2

Status = Disassoc

Imm-ACK

DisassocTimeout

beacon with DEV Association IE,DEVID=DEV-2, status=disassociated

beaconMLME-

DISASSOCIATE.reqwith TrgtID = DEV-2

MLME-DISASSOCIATE.cfm


DEV-2MAC/MLME

PNCMAC/MLME

DEV-2FCSL

beacon with DEV ADEVID=DEV-2, statu

DisassociationRequest commandwith ReasonCode =

ATP ExpiredMLME-DISASSOCIATE.ind

DEAT

Associated

Unassociated

DISAS

DEV-2 is

DEV-2



sted

a DEV-2 to DEV-3 stream

PNCFCSL

DEV-3MAC/MLME

DEV-3FCSL


h DEV-2am CTA or for stream

Stream fromDEV-2

MLME-CREATE-STREAM.ind

Submission

Current

Figure 114 - MSC for creating a DEV-2 to DEV-3 stream

Sugge

Figure 114 - MSC for creating

PNCDME

DEV-2DME

DEV-2MAC/MLME

DEV-3MAC/MLME

DEV-3DME

MLME-CREATE-STREAM.req

Channel TimeRequest command

Channel TimeResponse commandwith Reason Code =

success

MLME-CREATE-STREAM.cfm

PNCMAC/MLME


Imm-ACK

Resourcesavailable

Buildbeacon

RequestTimeout

Imm-ACK

beacon with DEV-2requested stream CTA

DEV-2FCSL

DEV-2MAC/MLME




Success


PNCMAC/MLME

Resourcesavailable

RequestTimeout

beacon witrequested streCTA Status IE

Stream toDEV-3



sted

d DEV-2 to DEV-3 stream

PNCFCSL

DEV-3MAC/MLME

DEV-3FCSL


Submission

Current

Figure 115 - MSC for a denied DEV-2 to DEV-3 stream

Sugge

Figure 115 - MSC for a denie

PNCDME

DEV-2DME

DEV-2MAC/MLME

DEV-3MAC/MLME

DEV-3DME



Channel TimeResponse commandwith Reason Code

not equal to success


PNCMAC/MLME


Imm-ACK

Resourcesavailable

RequestTimeout

Imm-ACK

DEV-2FCSL

DEV-2MAC/MLME




Channel TimeUnavailable


PNCMAC/MLME

Resourcesunavailable

RequestTimeout



sted

dd text to standard that describes C does not send commands over

cate with the PME.

VED

Submission

Current

Figure 116 - MSC for creating a DEV-1/PNC to DEV-2 stream

Sugge

• Suggest removing this MSC and athat the DEV component of the PNthe air when it wishes to communi

DEV-1/PNCDME

DEV-1/PNCMAC/MLME

DEV-2MAC/MLME

DEV-2DME


beaconwith requestedstream CTA

Resourcesavailable



REMO



sted

modifying a stream

PNCFCSL

DEV-3MAC/MLME

DEV-3FCSL


onested

CTA or for stream

Stream fromDEV-2

Stream fromDEV-2

Submission

Current

Figure 117 - MSC for modifying a stream

Sugge

Figure 117 - MSC for

DEV-2DME

DEV-2MAC/MLME

MLME-MODIFY-STREAM.req


beaconwith requestedchange in CTA

PNCMAC/MLME

PNCDME

Resourcesavailable

Channel TimeResponse commandwith Reason Code

= success

Imm-ACK

Buildbeacon

RequestTimeout

Imm-ACK


MLME-MODIFY-STREAM.cfm

DEV-2FCSL

DEV-2MAC/MLME




Success


PNCMAC/MLME

Resourcesavailable

RequestTimeout

beacwith requ

change inCTA Status IE

Stream toDEV-3

Modified Stream toDEV-3



sted

ied stream modification

PNCFCSL

DEV-3MAC/MLME

DEV-3FCSL


Stream fromDEV-2

Submission

Current

Figure 118 - MSC for a denied stream modification

Sugge

Figure 118 - MSC for a den

DEV-2DME

DEV-2MAC/MLME



PNCMAC/MLME

PNCDME


beacon with nochange in CTA

Channel TimeResponse Commandindicating no change

Imm-ACK

Imm-ACKResourcesavailable

RequestTimeout


DEV-2FCSL

DEV-2MAC/MLME




Channel TimeUnavailable


PNCMAC/MLME

Resourcesunavailable

RequestTimeout

Stream toDEV-3



sted

ing over control of a private, tic CTA

PNCFCSL

DEV-3MAC/MLME

DEV-3FCSL

block withex = SI,D = DEV-3

Pseudo-Static CTA with Stream Index = SI,SrcID = DestID = DEV-3

Submission

Current

Figure 119 - MSC for the handing over control of a private, pseudo-static CTA

Sugge

Figure 119 - MSC for the handpseudo-sta

DEV-2DME

DEV-2MAC/MLME

Channel Time Request commandwith Target ID List = DEV-3DEVID, Stream Index = SI

beacon, CTA block withStream Index = SI,

SrcID = DestID = DEV-3 DEVID

PNCMAC/MLME

PNCDME

DEV-3 is memberof parent piconet or is

an associatedneighbor PNC

Channel Time Responsecommand with

Reason Code = Success

Imm-ACK

Buildbeacon

RequestTimeout

Imm-ACK


CTA with Stream Index = SI,CTA Type = psuedo-static

SrcID = DestID = DEV-2 DEVID,

DEV-2FCSL

DEV-2MAC/MLME

Channel Time Requestcommand with

Target ID List = DEV-3Stream Index = SI

Channel TimeResponse command

withReason Code =

Success

PNCMAC/MLME

RequestTimeout

beacon, CTAStream Ind

SrcID = DestI

Pseudo-Static CTA with Stream Index = SI,SrcID = DestID = DEV-2

DEV-3 is memberof parent piconet or is

an associatedneighbor PNC



sted

V-2 requesting termination ream

that a reason code for the stream Target DEV for the stream.


PNCFCSL

DEV-3MAC/MLME

DEV-3FCSL

null-CTA,ex = n MLME-

TERMINATE-STREAM.ind

for

Stream n fromDEV-2

Stream n fromDEV-2 Terminated

Submission

Current

Figure 120 - MSC of source DEV-2 requesting termination of its stream

Sugge

Figure 120 - MSC of source DEof its st

• Suggest defining NULL CTA suchtermination can be provided to the

DEV-2DME

DEV-2MAC/MLME

Channel TimeRequest commandwith TU fields = 0,Stream Index = x

MLME-TERMINATE-STREAM.ind


PNCMLME

PNCDME

DEV-3MLME

DEV-3DME

MLME-TERMINATE-STREAM.req

DeallocateStream Index = x

Build beacon

Imm-ACKMLME-

TERMINATE-STREAM.cfm

with ResultCode= COMPLETED

beacon with null-CTA,Stream Index = x

RequestTimeout

DEV-2FCSL

DEV-2MAC/MLME

Channel TimeRequest commandwith TU fields = 0,Stream Index = n

PNCMAC/MLME


MLME-TERMINATE-STREAM.cfm

beacon with Stream Ind

RequestTimeout

Deallocate Resources Stream Index n

Channel TimeResponse commandwith TU fields = 0,Stream Index = n,

Reason Code= Success

Stream n toDEV-3

Stream n toDEV-3 Terminated



sted

V-3 requesting termination -2’s stream

that a reason code for the stream Source DEV for the stream.

Channel TimeRequest commandwith TU fields =0,Stream Index = n

PNCAC/MLME

DEV-3MAC/MLME

DEV-3FCSL



RequestTimeout

Channel TimeResponse command

with TU fields =0,Stream Index = n,

Reason Code= Success

ull-CTA,x = n

Stream n fromDEV-2

ate Resources foream Index n


Submission

Current

Figure 121 - MSC of target DEV-3 requesting termination of source DEV-2’s stream

Sugge

Figure 121 - MSC of target DEof source DEV

• Suggest defining NULL CTA suchtermination can be provided to the

DEV-2DME

DEV-2MAC/MLME

Channel TimeRequest commandwith TU fields =0,Stream Index = x



PNCMAC/MLME

PNCDME

DEV-3MAC/MLME

DEV-3DME



Build beacon

Imm-ACK

Channel Time Response commandwith Reason Code = streamterminated by target DEV


with ResultCode =COMPLETED

Imm-ACK

RequestTimeout

DEV-2FCSL

DEV-2MAC/MLME


MPNCFCSL

beacon with nStream Inde

Stream n toDEV-3

DeallocStr





sted

terminating a stream

that a reason code for the stream th the Source and Target DEVs for

PNCMAC/MLME

DEV-3MAC/MLME

DEV-3FCSL

ull-CTA,ex = n

Stream n fromDEV-2

llocate Resources forStream Index n



Submission

Current

Figure 122 - MSC of PNC terminating a stream

Sugge

Figure 122 - MSC of PNC

• Suggest defining NULL CTA suchtermination can be provided to bothe stream.

DEV-2DME

DEV-2MAC/MLME



PNCMAC/MLME

PNCDME

DEV-3MAC/MLME

DEV-3DME


Build beacon

Channel Time Response commandwith Reason Code

= Stream terminated by PNC

Imm-ACK




beacon with null-CTA,Stream Index = x

DEV-2FCSL

DEV-2MAC/MLME

PNCFCSL

beacon with nStream Ind

Keyind = indication

Stream n toDEV-3

Dea





sted

asynchronous data channel e

PNCFCSL


DEV-3FCSL

DEV-3MAC/MLME

MAC-ASYNC-DATA.ind

data frame

h DEV-2hronous CTA

CK

Submission

Current

Figure 123 - MSC for reserving asynchronous data channel time

Sugge

Figure 123 - MSC for reservingtim

PNCDME

DEV-2MAC/MLME


PNCMAC/MLME

Keyreq = requestind = indicationcfm = confirmImm-ACK

MAC-ASYNC-DATA.req

DEV-2FCSL

DEV-3FCSL

DEV-3MAC/MLME

MAC-ASYNC-DATA.ind

MAC-ASYNC-DATA.cfm with

ResultCode= SUCCESS

Resourcesavailable

BuildBeacon

asynchronous data frame

Imm-ACK

TransmissionTimeout

beacon with DEV-2requested asynchronous CTA

DEV-2MAC/MLME


PNCMAC/MLME

MAC-ASYNC-DATA.req

DEV-2FCSL

MAC-ASYNC-DATA.cfm

Resourcesavailable

asynchronous

TransmissionTimeout

beacon witrequested async

Imm-A



sted

ng information regarding a Vs from the PNC using the t and PNC Information nds

equestnd

mationnd

PNCMAC/MLME

PNCFCSL


Submission

Current

Figure 127 - MSC for acquiring information regarding a specific DEV or all of the DEVs from the PNC using the

PNC Information Request and PNC Information commands

Sugge

Figure 127 - MSC for acquirispecific DEV or all of the DE

PNC Information Requescomma

DEVDME

DEVMAC/MLME

MLME-PNC-INFO.req

PNC Info Requestcommand

MLME-PNC-INFO.ind

MLME-PNC-INFO.rspPNC Informationcommand

MLME-PNC-INFO.cfmwith ResultCode =

SUCCESS

PNCMAC/MLME

PNCDME

Keyreq = requestind = indicationrsp = responsecfm = confirm

Imm-ACK

Imm-ACK

PNCInfoTimeout

DEVFCSL

DEVMAC/MLME

MLME-DEV-INFO.req

PNC Info Rcomma

PNC Inforcomma

MLME-DEV-INFO.cfm

PNCInfoTimeout



sted

g DEV IEs using the Probe esponse commands

VED

Submission

Current

Figure 128 - MSC for acquiring DEV IEs using the Probe Request and Probe Response commands

Sugge

Figure 128 - MSC for acquirinRequest and Probe R

DEV-3DME

DEV-3MAC/MLME

MLME-PROBE.req

Probe Requestcommand with

IR field = yy

Probe Responsecommand with

IEs Provided = requested IEs

MLME-PROBE.cfmwith ResultCode =

SUCCESS

DEV-2MAC/MLME

DEV-2DME

Keyreq = requestind = indicationrsp = responsecfm = confirmIR = information requestedIE = information element

ProbeTimeout

Imm-ACK

Imm-ACK

MLME-PROBE.ind

MLME-PROBE.rsp REMO



sted

unrequested DEV IEs using nounce Response commands

VED

Submission

Current

Figure 129 - MSC showing sending of information using the Announce command

Sugge

Figure 129 - MSC for sending the Announce Request and An

DEV-3DME

DEV-3MAC/MLME

MLME-ANNOUNCE.req

Announcecommand withIEs Provided

MLME-ANNOUNCE.cfmwith ResultCode =

SUCCESS

DEV-2MAC/MLME

DEV-2DME

Keyreq = requestind = indicationcfm = confirmIE = information element

Imm-ACK MLME-ANNOUNCE.ind

AnnounceTimeout

REMO



sted

mining the channel status hannel Status Request and

ponse commands

VED

Submission

Current

Figure 130 - MSC for determining the channel status between two DEVs using the Channel Status Request and

Channel Status Response commands

Sugge

Figure 130 - MSC for deterbetween two DEVs using the C

Channel Status Res

DEV-3DME

DEV-3MAC/MLME

MLME-CHANNEL-STATUS.req

Channel StatusRequest command

MLME-CHANNEL-STATUS.ind

MLME-CHANNEL-STATUS.rspChannel Status

Response command

MLME-CHANNEL-STATUS.cfm


DEV-2MAC/MLME

DEV-2DME


Channel status determined

ChannelStatusTimeout

Imm-ACK

Imm-ACK

REMO



sted

ote scan MSC

VED

Submission

Current

Figure 131 - Remote scan MSC

Sugge

Figure 131 - Rem

PNCDME

PNCMAC/MLME

MLME-REMOTE-SCAN.req

MLME-REMOTE-SCAN.ind

Remote ScanResponse command

MLME-REMOTE-SCAN.cfm


DEV-1MAC/MLME

DEV-1DME


MLME-SCAN.req

MLME-SCAN.cfm

Remote ScanRequest commandRemoteScan

Timeout Imm-ACK

Imm-ACK

beacon (optionallywith quiet channel

time for scan)

MLME-REMOTE-SCAN.rsp

REMO



sted

ing the BSID for a piconet

DEV-1MAC/MLME

DEV-1FCSL

aconsitchingSID

withrameterndicatingSID

withrameterndicatingSID

ith new MLME-PICONET-PARM-CHANGE.ind

with ChangeType = BSID


r Piconet

Submission

Current

Figure 134 - MSC for changing either the PNID or BSID for a piconet

Sugge

Figure 134 - MSC for chang

PNCDME

PNCMAC/MLME

DEV-1MAC/MLME

DEV-1DME


MLME-PICONET-PARM-CHANGE.req

with new BSIDor PNID

x # of beaconsbefore switching

to new BSID

MLME-PICONET-PARM-CHANGE.cfm


beacon withPiconet Parameter

Change IE with newBSID or PNID

New PNID or BSID for piconet


Change IE with newBSID or PNID

PNCFCSL

PNCMAC/MLME

x # of bebefore sw

to new B

beaconPiconet Pa

Change IE inew B

beaconPiconet Pa

Change IE inew B

MLME-PICONET-PARM-CHANGE.cnf


beacon wBSID



New BSID fo



sted

g the channel for a piconet

DEV-1MAC/MLME

DEV-1FCSL

beacons switching Channel

witharameterindicatingannel

witharameterindicatingannel

n onannel

determinedfactory

ll DEVs channel

MLME-PICONET-PARM-CHANGE.indwith ChangeType =

CHANNEL

Keyind = indication

Submission

Current

Figure 135 - MSC for changing piconet parameters

Sugge

Figure 135 - MSC for changin

PNCDME

PNCMAC/MLME

DEV-1MAC/MLME

DEV-1DME



beacon(on newchannel)

Channel status determinedto be unsatisfactory


Change IE

DEV moves tonew channel

x # of beaconsbefore switchingto new channel

MLME-PICONET-PARM-CHANGE.cnf



Change IE

PNC moves tonew channel

PNCFCSL

PNCMAC/MLME

x # of before to new

beaconPiconet P

Change IE new Ch

beaconPiconet P

Change IE new Ch

beaconew ch

Channel status to be unsatis

PNC and amove to new

MLME-PICONET-PARM-CHANGE.indwith ChangeType =

CHANNEL



sted

power change MSC

VED

Submission

Current

Figure 136 - Transmit power change MSC

Sugge

Figure 136 - Transmit

DEV-2MAC/MLME

DEV-3MAC/MLME

DEV-2DME

DEV-3DME

Transmit Power Changecommand with

TX Power Change = yy


MLME-TX-POWER-CHANGE.req

with TrgtID = DEV-2,TXPowerChange = yy

MLME-TX-POWER-CHANGE.cfm


Imm-ACK

MLME-TX-POWER-CHANGE.ind

TXPowerChangeTimeout

REMO



sted

et information exchange

PNCMAC/MLME

PNCFCSL


tionand

tionand

ctures

Submission

Current

Figure 140 - MSC for PS set information exchange

Sugge

Figure 140 - MSC for PS s

DEVMAC/MLME

PNCMAC/MLME

DEVDME


MLME-PS-SET-INFORMATION.req

PS Set InformationRequest command

MLME-PS-SET-INFORMATION.cfm

with PSSetStructureSet,ResultCode = SUCCESS

PSRequestTimeout

PS Set Information Responsecommand with PS Set Structures

Imm-ACK

Imm-ACK

DEVMAC/MLME

DEVFCSL

MLME-PS-SET-INFORMATION.req

PS Set InformaRequest comm

MLME-PS-SET-INFORMATION.cfm

PSRequestTimeout

PS Set InformaResponse comm

with PS Set Stru



sted

DSPS set creation

PNCMAC/MLME

on RequestS Set IndexSPS set,e = join,

nterval = N

n ResponseS Set Indexet index,acon = X

PNCFCSL


New DSPSset created

Submission

Current

Figure 141 - MSC for DSPS set creation

Sugge

Figure 141 - MSC for

DEVMAC/MLME

PNCMAC/MLME

DEVDME


MLME-SPS-CONFIGURE.reqwith SPSSetIndex = Unallocated

DSPS Set, SPSSetOperation = join,WakeBeaconInterval = N SPS Configuration Request

command with SPS Set Index= Unallocated DSPS set,

Operation Type = join,Wake Beacon Interval = N

MLME-SPS-CONFIGURE.cfmwith SPSSetIndex = new PS Set,

SPSSetOperation = join,NextWakeBeacon = N

ResultCode = SUCCESS

PSRequestTimeout

SPS Configuration Responsecommand with SPS Set Index

= new DSPS set index,Next Wake Beacon = X

New SPS set created

Imm-ACK

Imm-ACK

DEVMAC/MLME

DEVFCSL


MLME-SPS-CONFIGURE.req

SPS Configuraticommand with SP

= Unallocated DOperation Typ

Wake Beacon I

MLME-SPS-CONFIGURE.cfm

PSRequestTimeout

SPS Configuratiocommand with SP

= new DSPS sNext Wake Be



sted

EV joining an existing SPS

PNCMAC/MLME

tion RequestS Set Index = zz,ype = join, Interval = N

tion ResponseS Set Index = zz,eacon = X

PNCFCSL

Keyreq = requestcfm = confirmzz = valid SPS set index

DEV Addedto Set zz

Submission

Current

Figure 142 - MSC showing a DEV joining an existing SPS set

Sugge

Figure 142 - MSC showing a Dset

DEVMAC/MLME

PNCMAC/MLME

DEVDME


MLME-SPS-CONFIGURE.reqwith SPSSetIndex = zz,OperationType = join,

WakeBeaconInterval = N SPS Configuration Requestcommand with SPS Set Index = zz,

Operation Type = join,Wake Beacon Interval = N

MLME-SPS-CONFIGURE.cfmwith SPSSetIndex = zz,OperationType = join,NextWakeBeacon = X


PSRequestTimeout

SPS Configuration Responsecommand with SPS Set Index = zz,

Next Wake Beacon = X

Joined PSPS or SPS set

Imm-ACK

Imm-ACK

DEVMAC/MLME

DEVFCSL


SPS Configuracommand with SP

Operation TWake Beacon


PSRequestTimeout

SPS Configuracommand with SP

Next Wake B

Memberof Set zz

Non-memberof Set zz



sted

a DEV leaving an SPS set

PNCMAC/MLME

tion RequestSPS Set = zz,pe = leave

ion ResponseS Set Index = zz

PNCFCSL


DEV Romvedfrom Set zz

Submission

Current

Figure 143 - MSC showing a DEV leaving an SPS set

Sugge

Figure 143 - MSC showing

DEVMAC/MLME

PNCMAC/MLME

DEVDME

Keyreq = requestcfm = confirmzz = valid PS set index

MLME-SPS-CONFIGURE.reqwith SPSsetIndex = zz,OperationType = leave

SPS Configuration Requestcommand with SPS Set = zz,

Operation Type = leave

MLME-SPS-CONFIGURE.cfmwith SPSsetIndex = zz,OperationType = leave,


PSRequestTimeout

Left SPS set = zz

Imm-ACK

DEVMAC/MLME

DEVFCSL


SPS Configuracommand with

Operation Ty


PSRequestTimeout

SPS Configuratcommand with SP

Memberof Set zz

Non-memberof Set zz



sted

DME initiated PM mode E to an SPS mode

PNCFCSL

DEV-3MAC/MLME

DEV-3FCSL


Status IE(s)DEV-2 set Bitmap MLME-

MONITOR-PM-MODE.ind

DEV-2PM Mode is

ACTIVE,DEV-2 PM Mode

is Monitored

DEV-2PM Mode is

SPS

DEV-2PM Mode is

not Monitored

Submission

Current

Figure 144 - MSC showing DME initiated PM mode change from ACTIVE to an SPS mode

Sugge

Figure 144 - MSC showing change from ACTIV

DEVMAC/MLME

PNCMAC/MLME

DEVDME

Keyreq = requestcfm = confirmMLME-PM-MODE-CHANGE.req

with PMMode = SPS

PM Mode Change commandwith PM Mode = PS

MLME-PM-MODE-CHANGE.cfmwith ResultCode = SUCCESS

PM Mode = ACTIVE

PSRequestTimeout

beacon with PS Status IE(s)with bit for DEV setin DEVID Bitmap

PM Mode = SPS

Imm-ACK

DEV-2FCSL

DEV-2MAC/MLME

PNCMAC/MLME

MLME-PM-MODE-CHANGE.req

PSRequestTimeout

PM Mode ChangeRequest command

with PM Mode = SPS

PM Mode ChangeResponse Commandwith Reason Code =

SuccessMLME-PM-MODE

-CHANGE.cfm

beacon with PSwith bit for

in DEVID

PM Mode isACTIVE

PM Mode isSPS

DEV-2PM Mode is

SPS



sted

DME initiated PM mode TIVE to APS

PNCFCSL

DEV-3MAC/MLME

DEV-3FCSL


ith PS PS Set =0or DEV-2 Bitmap

MLME-MONITOR-PM-

MODE.ind

DEV-2PM Mode is

ACTIVE, DEV-2PM Mode isMonitored

DEV-2PM Mode is

APS

DEV-2PM Mode is

not Monitored

Submission

Current

Figure 145 - MSC showing DME initiated PM mode change from ACTIVE to APS

Sugge

Figure 145 - MSC showing change from AC

DEVMAC/MLME

PNCMAC/MLME

DEVDME

Keyreq = requestcfm = confirmMLME-PM-MODE-CHANGE.req

with PMMode = APS

PM Mode Change commandwith PM Mode = APS


PM Mode = ACTIVE

PSRequestTimeout

beacon with PS Status IE for PS Set =0

with bit set for DEVin DEVID Bitmap

PM Mode = APS

Imm-ACK

DEV-2FCSL

DEV-2MAC/MLME

PNCMAC/MLME

PM Mode isACTIVE


PSRequestTimeout


with PM Mode = APS


Success

MLME-PM-MODE-CHANGE.cfm

beacon w Status IE for

with bit set fin DEVID

PM Mode isAPS

DEV-2PM Mode is

APS



sted

DME initiated PM mode mode to ACTIVE

PNCFCSL/PAL

DEV-3MAC/MLME

DEV-3FCSL/PAL


th status cleared intus IE(s)

MLME-MONITOR-PM-

MODE.ind

DEV-2PM Mode isAPS or SPS,

DEV-2 PM Modeis Monitored

DEV-2PM Mode is

ACTIVE

DEV-2PM Mode is

not Monitored

Submission

Current

Figure 146 - MSC showing DME initiated PM mode change from any PS mode to ACTIVE

Sugge

Figure 146 - MSC showing change from any PS

DEVMAC/MLME

PNCMAC/MLME

DEVDME


MLME-PM-MODE-CHANGE.reqwith PMMode = ACTIVE

PM Mode Change commandwith PM Mode = ACTIVE


PSRequestTimeout

beacon with statusbit for DEV cleared in

all PS Status IE(s)

PM Mode = ACTIVE

Imm-ACK

DEV-2FCSL/PAL

DEV-2MAC/MLME

PNCMAC/MLME


PSRequestTimeout


with PM Mode =ACTIVE


SuccessMLME-PM-MODE

-CHANGE.cfm

beacon wibit for DEV-2

all PS Sta

PM Mode isAPS or SPS

PM Mode isACTIVE

DEV-2PM Mode is

ACTIVE



sted

e showing MLME initiated to ACTIVE in response to a e allocation

PS Mode be automatically acti-ceived for a PS DEV.

PNCMAC/MLME

DEV-3MAC/MLME

DEV-3FCSL


CTA and without DEV-3’status IE or in the PCTM IE

rame, CTA Status IE withIE with DEV-3’s DEVID bit-3 DEVID, DestID = PNCID

PM Mode ChangeRequest

command with PMMode = ACTIVE

PM Mode ChangeResponse

command withReason Code =

SuccessMLME-PM-

MODE-CHANGE.rsp


MLME-PM-MODE-CHANGE.ind


PM Mode is ACTIVE

MLME-CREATE-

STREAM.ind

Stream fromDEV-2

PSRequestTimeout

DEV-3PM Mode is

DSPS

DEV-3PM Mode is

ACTIVE

Resourcesavailable

PM Mode is DSPS

Submission

Current

Figure 147 - Message sequence showing MLME initiated PM mode change from DSPS to ACTIVE in response to a

new chanel time allocation

Sugge

Figure 147 - Message sequencPM mode change from DSPS

new chanel tim

• Suggest monitoring of target DEVvated in channel time request is re

PNCDME

DEV-2DME

DEV-2MAC/MLME

DEV-3MAC/MLME

DEV-3DME

MLME-CREATE-STREAM.req withCTARateType = 0



PNCMAC/MLME


Buildbeacon

beacon with DEV-2 requested CTA and without DEV-3'sDEVID bit set in either the PS Status IE or in the PCTM IE

DEV-3 changesstate to ACTIVE

DEV-3 inDSPS mode

Channel time request processwith DEV-2 and PNC

beacon in DEV-3's wake superframe, CTA Status IE withDestID = DEV-3 DEVID, PCTM IE with DEV-3's DEVID bit

set, CTA block with SrcID = DEV-3 DEVID, DestID = PNCID

PM Mode Change commandwith PM Mode = ACTIVE

Imm-ACKMLME-PM-

MODE-ACTIVE.indwith PMActiveEvent= DATA_PENDING

DEV-2FCSL

DEV-2MAC/MLME

PNCFCSL

beacon with DEV-2 requested DEVID bit set in either the PS S

beacon in DEV-3’s wake superfDestID = DEV-3 DEVID, PCTM

set, CTA block with SrcID = DEV

MLME-MONITOR-PM-

MODE.ind

Stream toDEV-3



with CTARateType = 0


Success, DEV in PS Mode


RequestTimeout

DEV-3PM Mode is ACTIVE



sted

e chart for DEV-DEV Secu-ion request

rmationmand withID = nn MLME-SECURITY

-INFO.ind

MLME-SECURITY-INFO.rsp

rmationd withecord

D = nn

DEV-2MAC/MLME

DEV-2FCSL

Submission

urrent

Figure 148—Message sequence chart for DEV-DEV Secu-rity information request

Sugge

Figure 148—Message sequencrity informat

DEV-1DME

DEV-1MAC/MLME

MLME-SECURITY-INFO.req with

queried DEVID = nn Security InformationRequest command

MLME-SECURITY-INFO.ind

MLME-SECURITY-INFO.rsp withSecurity Record for DEVID = nn

Security Informationcommand

DEV-2MAC/MLME

DEV-2DME


Imm-ACK

Imm-ACK

MLME-SECURITY-INFO.cfm withSecurity Recordfor DEVID = nn

DEV-1FCSL

DEV-1MAC/MLME

MLME-SECURITY-INFO.req

Security InfoRequest com

queried DEV

Security Infocomman

Security R for DEVI


MLME-SECURITY-INFO.cfm

RequestTimeout



sted

ce chart for New PNC-Old rmation transfer

rmationmand

riedcstID


MLME-SECURITY-INFO.rsp

rmation withcordsVs

Old PNCMAC/MLME

Old PNCFCSL

overmmand

Submission

Current

Figure 149—Message sequence chart for New PNC-Old PNC Security Information transfer

Sugge

Figure 149—Message sequenPNC Security Info

New PNCDME

New PNCMAC/MLME

MLME-SECURITY-INFO.req with queried

DEVID = BcstID Security InformationRequest command


MLME-SECURITY-INFO.rsp with

Security recordsfor all DEVs

Security Informationcommand

PNCMAC/MLME

PNCDME


Imm-ACK

Imm-ACK

MLME-SECURITY-INFO.cfm with

Security Recordsfor all DEVs

New PNCFCSL

New PNCMAC/MLME

MLME-SECURITY-INFO.req

Security InfoRequest com

with queDEVID = B

Security Infocommand

Security refor all DE


MLME-SECURITY-INFO.cfm

RequestTimeout

MLME-HANDOVER.ind

withStatus =

STARTED

PNC HandRequest co



sted

e chart for sending security rity Message command

essageandhormation

MLME-SECURITY-MESSAGE.ind

DEV-3MAC/MLME

DEV-3FCSL

Submission

Current

Figure 150—Message sequence chart for sending security information with the Security Message command

Sugge

Figure 150—Message sequencinformation with the Secu

DEV-2DME

DEV-2MAC/MLME

MLME-SECURITY-MESSAGE.req withSecurityInformation

Security Messagecommand

MLME-SECURITY-MESSAGE.ind withSecurityInformation

DEV-3MAC/MLME

DEV-3DME


Imm-ACK

MLME-SECURITY-MESSAGE.cfm with

ResultCode =SUCCESS

SecMsgTimeout

DEV-2FCSL

DEV-2MAC/MLME

MLME-SECURITY-MESSAGE.req

Security Mcomm

witSecurityInf




sted

ce chart for PNC-DEV key tion

VED

Submission

Current

Figure 151—Message sequence chart for PNC-DEV key distribution

Sugge

Figure 151—Message sequendistribu

DEV-1DME

DEV-1MAC/MLME

MLME-DISTRIBUTE-

KEY.req

Distribute KeyRequest command

MLME-DISTRIBUTE-

KEY.ind

PNCMAC/MLME

PNCDME

MLME-DISTRIBUTE-KEY.cfm withResultCode

= SUCCESS


Imm-ACK

DistributeKeyTimeout

REMO



sted

e chart for peer-to-peer key tion

VED

Submission

Current

Figure 152—Message sequence chart for peer-to-peer key distribution

Sugge

Figure 152—Message sequencdistribu

DEV-1DME

DEV-1MAC/MLME

MLME-DISTRIBUTE-

KEY.reqDistribute Key

Request command

MLME-DISTRIBUTE-

KEY.ind

DEV-2MAC/MLME

DEV-2DME

MLME-DISTRIBUTE-KEY.cfm withResultCode =

SUCCESS


Distribute KeyResponse command

MLME-DISTRIBUTE-

KEY.rsp

DistributeKeyTimeout

Imm-ACK

Imm-ACK

REMO



sted

e chart for DEV key request

VED

Submission

Current

Figure 153—Message sequence chart for DEV key request

Sugge

Figure 153—Message sequenc

DEV-1DME

DEV-1MAC/MLME

MLME-REQUEST-KEY.req

Request Keycommand

MLME-REQUEST-KEY.ind

Request KeyResponsecommand

MLME-REQUEST-KEY.cfm


Key originatorMAC/MLME

Key orignatorDME


KeyRequestTimeout

Imm-ACK

Imm-ACK

MLME-REQUEST-KEY.rsp

REMO



sted

eating a child piconet

DEVMAC/MLME

sociation process with PNC and if required,es secure membership

nnel time request for atatic CTA with itself as

rcID and DestID


First beaconwith child PNC

parameters

Now PNCMAC/MLME

=

V determines thatption is dependent

piconet

Submission

Current

Figure 99 - MSC for creating a child piconet

Sugge

Figure 99 - MSC for cr

•

MLME-START-DEPENDENT-PNC.req

First beaconwith child PNC parameters

DEVMAC/MLME

DEVDME


MLME-START-DEPENDENT-PNC.cfm


PNCinitializationprocedure

DEV association process withparent PNC and if required,

establishes secure membership

DEV channel time request for apseudo-static CTA with itself as

SrcID and DestID

DEVFCSL

DEV asparent

establish

DEV chapseudo-s

S

Now PNCFCSL

MLME-START.req

MLME-START.cfm

with ResultCode SUCCESS


DEonly o



sted

ating a neighbor piconet

DEVMAC/MLME

First beacon withneighbor PNC

param eters(if 802.15.3 neighbor

piconet)

ciation process with parent requesting neighbor. PNC

gns neighbor DEVID.

hannel tim e request foro-static CTA with itself SrcID and DestID


Now PNCMAC/MLME

=

EV determ ines that option is dependent

piconet

Submission

Current

Figure 101 - MSC for initiating a neighbor piconet

Sugge

Figure 101 - MSC for initi

DEVMAC/MLME

DEVDME


MLME-START-DEPENDENT-

PNC.req

MLME-START-DEPENDENT-PNC.cfm

(w/ ResultCode =SUCCESS)

PNCinitializationprocedure

First beacon withneighbor PNC parameters

(if 802.15.3 neighbor piconet)

DEV association process with parentpiconet and requesting neighbor. PNC

assigns neighbor DEVID.

DEV channel time request forpseudo-static CTA with itself

as SrcID and DestID

DEVFCSL

DEV assopiconet and

assi

DEV cpseud

as

Now PNCFCSL

MLME-START.req

MLME-START.cfm

with ResultCodeSUCCESS


Donly



sted

handover MSC

Keyind = indication

DEV-3MAC/MLME

PNCFCSL

DEV-3FCSL

PNC Handover IE

PNC Handover IE

New PNC beacon

ME-NEW-NC.ind

MLME-NEW-PNC.ind

w DEV-N

Submission

Current

Figure 94 - PNC handover MSC

Sugge

Figure 94 - PNC

MLME-PNC-HANDOVER.ind

(STARTED) Keyreq = requestind = indicationrsp = responsecfm = confirm

MLME-PNC-HANDOVER.req

PNC HandoverRequest command

PNC HandoverInformation command

PNC HandoverResponse command

DEV-3MAC/MLME

DEV-2DME

DEV-2MAC/MLME

PNCMAC/MLME

PNCDME

DEV-3DME

HandoverTimeout

MLME-PNC-HANDOVER.cfm

Imm-ACK

Imm-ACK

PNC InformationcommandImm-ACK

MLME-NEW-PNC.ind

MLME-PNC-HANDOVER.rsp

Imm-ACK

New PNC MLME receivedall PNC related information andMLME-PNC-HANDOVER.rsp

MLME-PNC--INFO.cfm

PS InformationResponse command

Imm-ACK

MLME-PNC-HANDOVER.ind(COMPLETED)

DEV-2 assumescontrol, now is PNC DME

and PNC MLME. Original PNC relinquishescontrol, now is DEV-1 DME

and DEV-1 MLME.

Optional security information handover

Old PNC beacon with PNC Handover IE

Old PNC beacon with PNC Handover IE

New PNC beacon New PNC beacon


PNC HandoverResponse commandwith Reason Code =Success, Ready for

Handover

DEV-2FCSL

DEV-2MAC/MLME

PNCMAC/MLME

HandoverTimeout

Old PNC beacon with

Old PNC beacon with

New PNC beacon

MLP

MLME-NEW-PNC.ind

MLME-HANDOVER.ind

withStatus =

STARTED

NoNow PNC

Mandatory and Optional Handover InformationTransfered from PNC to DEV-2

PNC optionally creates stream to target PNC



sted

handover in a dependent et

Keyind = indication

DEV-3MAC/MLME

PNCFCSL

DEV-3FCS

PNC Handover IE

PNC Handover IE

reamt ID forx

w DEV-N

New PNC beacon

E-NEW-NC.ind

MLME-NEW-PNC.ind

Submission

Current

Figure 95 - Successful PNC handover in a dependent piconet

Sugge

Figure 95 - Successful PNCpicon






PNC HandoverResponse commandwith Reason Code =

DEVID in parent piconet

DEV-3MAC/MLME

DEV-2DME

DEV-2MAC/MLME

PNCMAC/MLME

PNCDME

DEV-3DME

HandoverTimeout

MLME-PNC-HANDOVER.cnf

Imm-ACK

Imm-ACK


MLME-NEW-PNC.ind


Imm-ACK


MLME-PNC--INFO.cfm

PS Set InformationResponse command

Imm-ACK

MLME-PNC-HANDOVER.ind(COMPLETED)

DEV-2 assumescontrol, now is PNC DME

and PNC MLME.

Original PNC relinquishescontrol, now is DEV-1 DME

and DEV-1 MLME.


Old PNC beacon with handover IE

Old PNC beacon with handover IE

New PNC beacon

DEV-2 becomes member of parentpiconet (if not already member)

PNC requests isoch stream modification,new Target ID for existing Stream Index



Handover

DEV-2FCSL

DEV-2MAC/MLME

PNCMAC/MLME

HandoverTimeout

Old PNC beacon with

Old PNC beacon with



PNC requests isoch stmodification, new Targe

existing Stream Inde

No

New PNC beacon

MLMP

MLME-NEW-PNC.ind

Now PNC


MLME-HANDOVER.ind

withStatus =

STARTED



sted

PNC handover when target parent piconet

DEV-3MAC/MLME

PNCFCSL

DEV-3FCSL

ainspiconet

Submission

Current

Figure 96 - Failed dependent PNC handover when target DEV fails to join parent piconet

Sugge

Figure 96 - Failed dependent DEV fails to join





PNC HandoverResponse commandwith Reason Code =

0xFE

DEV-3MAC/MLME

DEV-2DME

DEV-2MAC/MLME

PNCMAC/MLME

PNCDME

DEV-3DME

HandoverTimeout

MLME-PNC-HANDOVER.cfmReasonCode =

FAILED

Imm-ACK

MLME-PNC-HANDOVER.rspReasonCode =

0xFE

DEV-2 fails to become member ofparent piconet

Imm-ACK


PNC HandoverResponse commandwith Reason Code =Unable to Join Parent

DEV-2FCSL

DEV-2MAC/MLME

PNCMAC/MLME

HandoverTimeout

DEV-2 fails to become member ofparent piconet

Original PNC remPNC of dependent



sted

NC handover when control is handed over in the iconet

DEV-3MAC/MLME

PNCFCSL

DEV-3FCSL

ainspiconet

h streamget ID forex fails

Submission

Current

Figure 97 - Failed dependent PNC handover when control for the dependent piconet CTA is handed over in the parent piconet

Sugge

Figure 97 - Failed dependent Pfor the dependent piconet CTA

parent p






PNC HandoverResponse command

Reason Code = DEVIDin parent piconet

DEV-3MLME

DEV-2DME

DEV-2MLME

PNCMLME

PNCDME

DEV-3DME

HandoverTimeout

MLME-PNC-HANDOVER.cnf

ResultCode =FAILED

Imm-ACK

Imm-ACK



Imm-ACK


MLME-PNC--INFO.cfm

PS Set InformationResponse command

Imm-ACK

Original PNC remainsPNC of dependent piconet



PNC request for isoch stream modification,new Target ID for existing Stream Index fails

PNC handoverrequest command,Handover Status =

Cancelled

Imm-ACK

DEV-2FCSL

DEV-2MAC/MLME

PNCMAC/MLME

PNC HandoverRequest commandHandover Status =

Cancelled

HandoverTimeout

PNC HandoverResponse commandwith Reason Code =Success, Handover

Cancelled

Original PNC remPNC of dependent



Handover

HandoverTimeout


PNC request for isocmodification, new Tar

existing Stream Ind



MLME-HANDOVER.ind

withStatus =

STARTED

MLME-HANDOVER.ind

withStatus =

CANCELLED



DEV-3FCSL

questdication

confirm

ME-ATION-IFIC-

A.indtatus =DED

aware ofn specificta

Submission

8. New MSCs

This section provides suggested new MSCs for functionality that was not previously documented with MSCs.

New - DEV adding application specific data to beacon

DEV-2MAC/MLME

PNCMAC/MLME

DEV-2FCSL

PNCFCSL

DEV-3MAC/MLME

ASIE Requestcommand with

RequestType = ADD

ASIE Responsecommand with

RequestType = ADD,ApplicationSpecificID =

0xzz

Keyreq = reind = incfm =

MLME-APPLICATION-

SPECIFIC-DATA.reqwith

RequestType = ADD

MLME-APPILICATION-

SPECIFC-DATA.cnfwith ResultCode =

SUCCESS,ApplicationSpecificID =

0xzz

beacon with ASIE,ApplicationSpecificID=0xzz

MLAPPLIC

SPECDAT

with SAD

RequestTimeout

MLME-APPLICATION-

SPECIFIC-DATA.ind

with Status =ADDED

PNC aware ofapplication specific

data

DEV-3 applicatio

da



er of beacons

DEV-3FCSL

uesticationnfirm

E-TION-

IFIC-.indtus =

ED

are of specifica

E-TION-

IFIC-.indtus =VED

wareval of specifica

Submission

New - DEV adding application specific data to the beacon for a specific numb

DEV-2MAC/MLME

PNCMAC/MLME

DEV-2FCSL

PNCFCSL

DEV-3MAC/MLME

ASIE Requestcom m and with

RequestType = COUNT,CountValue = n

ASIE Responsecom m and with

RequestType = COUNT,ApplicationServicesID =

0xzz

Keyreq = reqind = indcfm = co

MLME-APPLICATION-

SPECIFIC-DATA.indwith S tatus =

COUNT

MLME-APPLICATION-

SPECIFIC-DATA.cnfwith ResultCode =

SUCCESS

beacon with ASIE ,ApplicationServicesID=0xzz

MLMAPPLICA

SPECDATA

with S taADD

RequestT im eout

MLME-APPLICATION-

SPECIFIC-DATA.ind

with S tatus =ADDED

PNC aware ofapplication specific

data

DEV-3 awapplication

dat

n-1 beaconswith ASIE ,

ApplicationServicesID=0xzz

beacon without ASIE ,ApplicationServicesID=0xzz

MLMAPPLICA

SPECDATA

with S taREMO

DEV-3 aof rem o

applicationdat

MLME-APPLICATION-

SPECIFIC-DATA.ind

with S tatus =REMOVED

PNC awareof rem oval of

application specificdata



DEV-3FCSL

questdication

confirm

ME-ATION-IFIC-

A.indtatus =OVED

awareoval ofn specificta

Submission

New - DEV removing application specific data from a beacon

DEV-2MAC/MLME

PNCMAC/MLME

DEV-2FCSL

PNCFCSL

DEV-3MAC/MLME

ASIE Requestcommand withRequestType =

REMOVE,ApplicationSpecificID =

0xzz

ASIE Responsecommand withRequestType =


0xzz

Keyreq = reind = incfm =

MLME-APPLICATION-

SPECIFIC-DATA.req withRequestType =


0xzz

MLME-APPLICATION-

SPECIFIC-DATA.cnf withResultCode =

SUCCESS

beacon without ASIE,ApplicationSpecificID=0xzz

MLAPPLIC

SPECDAT

with SREM

RequestTimeout

MLME-APPLICATION-

SPECIFIC-DATA.ind

with Status =REMOVED

PNC awareof removal of

application specificdata

DEV-3of rem

applicatioda



NC

DEV-3FCSL

equestndication confirm

ME-ONET-ICES.ind

aware of service

Submission

NEW - DEV announcing the availability of a piconet service to the P

DEV-2MAC/MLME

PNCMAC/MLME

DEV-2FCSL

PNCFCSL

Announce Requestcommand with

Piconet Services IE

Announce Responsecommand


MLME-ANNOUNCE-SERVICE.req

MLME-ANNOUNCE-SERVICE.cnf

withResultCode =

SUCCESS

RequestTimeout

PNC optionally saves PiconetServices IE

DEV-3MAC/MLME

Keyreq = rind = icfm =

MLPIC

SERV

DEV-3added

Announce Request command with DestID = BcstIDand with provided Piconet Services IE

MLME-PICONET-

SERVICES.ind

PNC aware ofadded service


Submission
NEW - DEV requesting available piconet services from PNC

DEV-2MAC/MLME

PNCMAC/MLME

DEV-2FCSL

PNCFCSL

Probe Requestcommand requestingPiconet Services IEs

Probe Responsecommand with

Piconet Services IEs


MLME-PICONET-

SERVICES.req

MLME-PICONET-

SERVICES.cnfwith

ResultCode =SUCCESS

RequestTimeout


Submission
NEW - DEV sending vendor specific information to another DEV

DEV-2MAC/MLME

DEV-3MAC/MLME

DEV-2FCSL

DEV-3FCSL

Announce Requestcommand with

VendorSpecificIE

Announce Responsecommand


MLME-VENDOR-SPECIFIC.req with

RequestType =INFORMATION

MLME-VENDOR-SPECIFIC.cnf

RequestTimeout

MLME-VENDOR-SPECIFIC.ind with

RequestType =INFORMATION



PNCFCSL

Submission

NEW - DEV sending a vendor specific command to another DEV

NEW - DEV joining multicast group

DEV-2MAC/MLME

DEV-3MAC/MLME

DEV-2FCSL

DEV-3FCSL

Vendor Specificcommand


MLME-VENDOR-SPECIFIC.req with

RequestType =COMMAND

MLME-VENDOR-SPECIFIC.cnf

MLME-VENDOR-SPECIFIC.ind with

RequestType =COMMAND

DEVMAC/MLME

PNCMAC/MLME

DEVFCSL

MLME-MULTICAST-CONFIGURE.req withOperationType = JOIN,MutlicastAddress = addr

Multicast Configuration Requestcommand with

MutlicastAddress = addr,OperationType = JOIN

MLME-MULTICAST-CONFIGURE.cfm with

ResultCode = SUCCESS,MutlicastAddress = addr,

McstGrpId = 0xzz

RequestTimeout

Multicast Configuration Responsecommand with

MutlicastAddress = addr,McstGrpId = 0xzz

Keyreq = requestcfm = confirmaddr = MAC address

DEV Added toMcstGrpId corresponding to

MulicastAddress



PNCFCSL

Submission

NEW - DEV leaving multicast group

DEVMAC/MLME

PNCMAC/MLME

DEVFCSL

MLME-MULTICAST-CONFIGURE.req with

OperationType = LEAVE,MutlicastAddress = addr

Multicast Configuration Requestcommand with

OperationType = LEAVE,MutlicastAddress = addr

MLME-MULTICAST-CONFIGURE.cfm with

ResultCode = SUCCESS,MutlicastAddress = addr,

McstGrpId = 0xzz

RequestTimeout

Multicast Configuration Responsecommand with

MutlicastAddress = addr,McstGrpId = 0xzz

Keyreq = requestcfm = confirmaddr = MAC address

DEV removed frommulticast group

McstGrpId


Submission

IEEE P802.15 Wireless Personal Area Networks · MLME SAP defined in IEEE Std 802.15.3-2003 should...

Documents

Transcript of IEEE P802.15 Wireless Personal Area Networks · MLME SAP defined in IEEE Std 802.15.3-2003 should...