IEEE P Wireless Personal Area Networks. MSCs Incorporating New FCSL/DME/MLME Functional Division and Imm-ACK Removal

Transcription

1 IEEE P Wireless Personal Area Networks Project Title Date Submitted IEEE P Working Group for Wireless Personal Area Networks (WPANs) MSCs Incorporating New FCSL//MLME Functional Division and Removal [15 July, 2004] Source [John Sarallo] [Appairent Technologies] [150 Lucius Gordon Drive, West Henrietta, NY 14586] Voice: [ ] Fax: [ ] Re: [] Abstract Purpose Notice Release [This document contains a list or proposed changes to IEEE Std ] [The purpose of this document is to propose changes to IEEE Std to improve compatibility, performance and clarity in the standard.] This document has been prepared to assist the IEEE P It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. The contributor acknowledges and accepts that this contribution becomes the property of IEEE and may be made publicly available by P Submission Page 1 John C. Sarallo - Appairent Technologies

2 1. Introduction This document presents new clause 8 MSCs resulting from s no longer being used as confirmation commands as presented in 04/202r0 and with the following functional division as defined in the May b meeting. Note: The italicized items have been moved or renamed since the May 2004 meeting. FCSL/PAL Map Upper layer identifier (e.g., MAC address) to ID for data frames Maintain List of available s Map upper layer stream IDs to 15.3 indices Pass data to MAC Fragmentation Maintain list of IDs Convert Async Data to MAC SAP Async Data Requests Rate adjustment decisions Master MAC Address - ID table Stream index only Start/Stop scan Associate/disassociate Track Security Problems Determine PM Mode Convert stream requirements to CT requests Determine when to scan and process results KOME ( originator management entity) Change Data keys (PME) Select Piconet channel Associate/disassociate s Handover Scan for interference Start/stop network (including child/neighbor) Change PNID/BSID Maintain list of associate s Allocate channel time Track PM s Change Superframe Duration Change Superframe Location ID and Stream Index only Data queues 15.3 Fragmentation/Reassembly ACKs On-air timing data, command, beacon Keep data and management keys (because this is where encryption happens) Secure frame processing Channel quality (e.g. FER and retry), TX power adaptation Perform scan and report capacity (status, scan) Rate adaptation implementations (affects CTAs) Identify current Piconet (BSID, PNID and MAC address) Prepare Async CTRq s and tracks async. time requirements. Manage ATP to stay associated () Track ATPs for s () Submission Page 2 John C. Sarallo - Appairent Technologies

3 2. Clause 8 MSC changes 2.1 Section purpose If a request results in a change to the overall piconet state, the other s in the piconet are notified of the piconet state change via information broadcast in a beacon. This section shows through comparison how the MSCs in Clause 8 of IEEE would need to be modified in order to support the changes suggested by this document. The Figure numbers in this section represent Figure numbers from IEEE On each of the following pages in this section a version of an MSC as currently defined in IEEE is shown of the left side of the page. The right side of each page shows the new suggested MSC, along with a list of the changes made to the original MSC to support the changes suggested by this document. 2.2 Strategies/Guidelines used The following are the strategies and guidelines that were followed in the creation of the new MSCs presented in this section. This was done in an effort to have consistencies between all the frame exchanges sequences represented by the MSCs. frames (part of the over-the-air retry mechanism) should not be used as managment level confirmations because they are meaningless if security is used or if the standard is extended to support mesh networks. Although it is possible in some instances for a requesting to confirm that a command was received via information transmitted in a beacon, a beacon can not be used as a confirmation when the request is denied. Furthermore, a response command typically contains more information than is put into a beacon. Therefore, Request commands are always acknowledged with response commands when a confirmation that the command was received and processed is necessary. The start timer symbol (shown below) indicates that starting of the continuously running timer at a rate equal to the current superframe duration. The timer timout symbol (shown below) indicates that the time to transmit a beacon has arrived. This timer is considered to be running continously once a piconet is started. This timeout should be considered to occur sometime in the future with respect to previous information shown on the MSC. Scenarios identified as fire and forget can not be confirmed, so no timeout timer should be started and no MLME confirm primitive should be generated as part of the message exchange sequence. Specific information associated with an over-the-air command frame is only shown once on an MSC with the over-the-air command itself. It can be assumed that the information is also contained in the MLME request/response that caused the over-the-air command to be generated, and also in the MLME indication/confirm generated by the reception of the command. The first MSC in clause 8 (Figure 91) shows that the result code associated with an MLME confirm is always COMPLETED if the timeout timer associated with the original request does not timeout. Therefore, this information is not repeated in the MSCs. 2.3 The MSCs Submission Page 3 John C. Sarallo - Appairent Technologies

4 No Change XXX.request with (timeout) ALT Action completed RequestTimer (timeout) XXX.confirm with ResultCode = COMPLETED RequestTimer (timeout) XXX.confirm with ResultCode = TIMEOUT Figure 91 - MSC showing examples of primitive timers Submission Page 4 John C. Sarallo - Appairent Technologies

5 SCAN.req SCAN.req SCAN.cfm with ResultCode = SUCCESS Perform scan procedure SCAN.cfm Perform scan procedure Figure 92 -MSC for scan operation Figure 92 -MSC for scan operation Submission Page 5 John C. Sarallo - Appairent Technologies

6 START.req START.cfm with ResultCode = SUCCESS Piconet initialization procedure Piconet initialization procedure Now Now beacon Figure 93 - MSC for starting a piconet Figure 93 - MSC for starting a piconet The PME ( ) maintains the information that is contained in a beacon so a START primitive is no longer needed because the PME can simply make a request to send a beacon when it is ready to start a piconet. BEACON is a new primitive with a request component to request the transmission of a beacon frame and a indication component to indicate the arrival of a beacon frame. When a piconet is started, a timer is required for transmitting beacons at the superframe interval. Submission Page 6 John C. Sarallo - Appairent Technologies

7 UnSynched SYNCH.req Sync SYNCH.cfm with ResultCode = SUCCESS Synched PNID = Piconet ID beacon with PNID of target piconet UnSynched Synched Sync beacon with PNID of target piconet PNID = Piconet ID Figure MSC of a synchronizing with a Figure MSC of a synchronizing with a can sync itself because it receives beacon indications. Therefore, SYNCH primitives are no longer needed. Submission Page 7 John C. Sarallo - Appairent Technologies

8 Unassociated ASSOCIATE.req Assoc ASSOCIATE.cfm w/ ID=0xzz Associated Association Request command with ID = UnassocID, addr = addr with DestID = UnassocID Association Response command with DestID= UnassocID, ID= 0xzz, addr = addr Association Request command with SrcID = 0xzz Imm ACK with DestID=0xzz beacon ASSOCIATE.ind Addr= Addr ID=UnassocID ASSOCIATE.rsp ID = 0xzz ATP beacon ASSOCIATE.ind Addr= Addr ID=0xzz beacon with Association IE, ID=0xzz, Addr= Addr, Status=Assoc Figure MSC of associating Associated addr=address - ASSOCIATE- INFO.ind with ID=0xzz Addr = Addr, Status=Assoc Unassociated Associated is Associated ASSOCIATE.req Assoc ASSOCIATE.cfm - INFO.cfm Association Request command with ID = UnassocID, addr = addr Association Response command with DestID= UnassocID, ID= 0xzz, addr = addr Association Request command with SrcID = 0xzz, addr = addr Association Response command with DestID= 0xzz, ID= 0xzz, addr = addr ASSOCIATE.ind ASSOCIATE.rsp ATP ASSOCIATE.ind is Associated ASSOCIATE.rsp beacon with Association IE, ID=0xzz, Addr= Addr, Status=Assoc - INFO.rsp Information command is Unassociated addr=address - INFO.cfm is Unassociated is Associated Figure MSC of associating Requesting knows it is associated when it receives the second Association. Other s in the piconet know when they receive a beacon with a Association IE. The associating learns of other s via the Information command. Submission Page 8 John C. Sarallo - Appairent Technologies

9 association process, Piconet Services Inquiry field set to one in the Association with the SrcId set to the newly assigned ID. Association is successful, assigned ID = 0xzz association process, Piconet Services Inquiry field set to one in the Association with the SrcId set to the newly assigned ID. Association is successful, assigned ID = 0xzz PICONET- SERVICES.cfm Piconet Services command with DestID = 0xzz PICONET- SERVICES.ind TrgtID=0xzz PICONET- SERVICES.rsp TrgtID=0xzz PICONET- SERVICES.cfm Piconet Services command PICONET- SERVICES.rsp Figure sending the Piconet Services command to a newly associated in response to a request in the association process Figure sending the Piconet Services command to a newly associated in response to a request in the association process PME is aware when a associates with the Piconet Services Inquiry field set therefore the does not need to send an indication to the PME. Submission Page 9 John C. Sarallo - Appairent Technologies

10 Associated Associated DISASSOCIATE.req Disassoc DISASSOCIATE.cfm with ResultCode = SUCCESS UnAssociated Disassociation with OrigID = beacon DISASSOCIATE.ind with OrigID = beacon with Association IE, ID=, status=disassociated - ASSOCIATION- INFO.ind with ID = Status = Disassoc Associated Unassociated DISASSOCIATE.req Disassociation Reason Code = Leaving Piconet DISASSOCIATE.ind is Unassociated is Associated beacon with Association IE, ID=, status=disassociated is Associated is Unassociated Figure initiated disassociation MSC Figure initiated disassociation MSC initiated disassociation is a fire and forget scenario. Disassociating can immediately mark itself as disassociated. Other s know when they receive a beacon with a Association IE. Submission Page 10 John C. Sarallo - Appairent Technologies

11 Disassociation Associated Associated DISASSOCIATE.ind UnAssociated Disassoc beacon DISASSOCIATE.req with TrgtID = DISASSOCIATE.cfm with ResultCode = SUCCESS beacon with Association IE, ID=, status=disassociated - ASSOCIATION- INFO.ind with ID = Status = Disassoc Associated Unassociated DISASSOCIATE.ind Disassociation with ReasonCode = ATP Expired ATP ATP-EXPIRED.ind DISASSOCIATE.req is Unassociated beacon with Association IE, ID=, status=disassociated is Associated is Unassociated Figure initiated disassociation MSC Figure initiated disassociation MSC initiated disassociation is a fire and forget scenario. is disassociated when it receives a DISASSOCI- ATE.ind. Other s know about the disassociation when they receive a beacon with a Association IE. If a receives a beacon with a Association IE indicating it is disassociated, it should consider itself disassociated. Took opportunity to add ATP-EXPIRED.ind to at least one MSC (Note: must maintain ATP timers because the does not see data frames.) Submission Page 11 John C. Sarallo - Appairent Technologies

12 CREATE- STREAM.req Request CREATE- STREAM.cfm Resources available with Reason Code = success Build beacon beacon with requested stream CTA Stream to CREATE- STREAM.req Request CREATE- STREAM.cfm with Reason Code = Success CREATE- STREAM.ind Resources available CREATE- STREAM.rsp beacon with requested stream CTA or CTA Status IE for stream Stream from Figure MSC for creating a to stream Figure MSC for creating a to stream PME is responsible for channel time allocation so CREATE- STREAM indication and response primitives are required. Requesting knows stream is created when it receives the Channel Time. Target knows about the stream when it receives a beacon with a CTA or CTA Status IE indicating it is the target of a stream. Submission Page 12 John C. Sarallo - Appairent Technologies

13 CREATE- STREAM.req Request Resources available with Reason Code not equal to success CREATE- STREAM.req Request with Reason Code = Unavailable CREATE- STREAM.ind Resources unavailable CREATE- STREAM.rsp CREATE- STREAM.cfm CREATE- STREAM.cfm Figure MSC for a denied to stream Figure MSC for a denied to stream Submission Page 13 John C. Sarallo - Appairent Technologies

14 -1/ -1/ CREATE- STREAM.req Resources available Suggest removing this MSC and add text to standard that describes that the component of the does not send commands over the air when it wishes to communicate with the PME. CREATE- STREAM.cfm beacon with requested stream CTA Figure MSC for creating a -1/ to stream Submission Page 14 John C. Sarallo - Appairent Technologies

15 MODIFY- STREAM.req Request MODIFY- STREAM.cfm beacon with requested change in CTA Resources available with Reason Code = success Build beacon Figure MSC for modifying a stream Stream to Modified Stream to MODIFY- STREAM.req Request MODIFY- STREAM.cfm with Reason Code = Success CREATE- STREAM.ind Resources available CREATE- STREAM.rsp beacon with requested change in CTA or CTA Status IE for stream Stream from Modified Stream from Figure MSC for modifying a stream Requesting knows stream is modified when it receives the. Target knows about the stream modification when it receives a beacon with a modified CTA or a CTA Status IE. Submission Page 15 John C. Sarallo - Appairent Technologies

16 MODIFY- STREAM.req Request MODIFY- STREAM.cfm Response Command indicating no change beacon with no change in CTA Resources available Stream to MODIFY- STREAM.req Request MODIFY- STREAM.cfm with Reason Code = Unavailable CREATE- STREAM.ind Resources unavailable CREATE- STREAM.rsp Figure MSC for a denied stream modification Stream from Figure MSC for a denied stream modification Submission Page 16 John C. Sarallo - Appairent Technologies

17 CTA with Stream Index = SI, CTA Type = psuedo-static SrcID = DestID = ID, Request with Target ID List = ID, Stream Index = SI is member of parent piconet or is an associated neighbor Response command with Reason Code = Success Build beacon beacon, CTA block with Stream Index = SI, SrcID = DestID = ID Pseudo-Static CTA with Stream Index = SI, SrcID = DestID = MODIFY- STREAM.req Request MODIFY- STREAM.cfm Request command with Target ID List = Stream Index = SI with Reason Code = Success MODIFY- STREAM.ind beacon, CTA block with Stream Index = SI, SrcID = DestID = is member of parent piconet or is an associated neighbor MODIFY- STREAM.rsp Pseudo-Static CTA with Stream Index = SI, SrcID = DestID = Figure MSC for the handing over control of a private, pseudo-static CTA Figure MSC for the handing over control of a private, pseudo-static CTA Submission Page 17 John C. Sarallo - Appairent Technologies

18 TERMINATE- STREAM.req Request TERMINATE- STREAM.cfm with ResultCode = COMPLETED MLME with TU fields = 0, Stream Index = x Deallocate Stream Index = x Build beacon beacon with null-cta, Stream Index = x TERMINATE- STREAM.ind Figure MSC of source requesting termination of its stream MLME Stream x to TERMINATE- STREAM.req Request Stream x Terminated TERMINATE- STREAM.cfm with TU fields = 0, Stream Index = x with TU fields = 0, Stream Index = x, Reason Code = Success MLME TERMINATE- STREAM.ind TERMINATE- STREAM.rsp beacon with null-cta, Stream Index = x Deallocate Stream Index x MLME Stream x from Stream x Terminated Figure MSC of source requesting termination of its stream If the we desire the target to know why a stream was terminated, then the target must receive a. Otherwise, it will know the stream is terminated when it receives the Null CTA but it will not know why the stream was terminated. Submission Page 18 John C. Sarallo - Appairent Technologies

19 If the we desire the strean source to know why the stream was terminated, then the source must receive a Response command. Otherwise, it will know the stream is terminated when it receives the Null CTA but it will not know why the stream was terminated. TERMINATE- STREAM.ind with Reason Code = stream terminated by target with TU fields =0, Stream Index = x Deallocate Stream Index = x Build beacon TERMINATE- STREAM.req Request TERMINATE- STREAM.cfm with ResultCode = COMPLETED Stream x to TERMINATE- STREAM.ind Deallocate Stream Index x TERMINATE- STREAM.rsp with TU fields =0, Stream Index = x with TU fields =0, Stream Index = x, Reason Code = Success TERMINATE- STREAM.req Request TERMINATE- STREAM.cfm Stream x from Stream x Terminated Figure MSC of target requesting termination of source s stream Stream x Terminated beacon with null-cta, Stream Index = x Figure MSC of target requesting termination of source s stream Submission Page 19 John C. Sarallo - Appairent Technologies

20 TERMINATE- STREAM.ind TERMINATE- STREAM.req Deallocate Stream Index = x Build beacon TERMINATE- STREAM.cfm beacon with null-cta, Stream Index = x with Reason Code = Stream terminated by TERMINATE- STREAM.ind Stream x to Deallocate Stream Index x beacon with null-cta, Stream Index = x Stream x from Figure MSC of terminating a stream Stream x Terminated Stream x Terminated Figure MSC of terminating a stream If the we desire the stream source and target to know why a stream was terminated, then both s must receive a. Otherwise, both s will know the stream is terminated when they receives the Null CTA but they will not know why the stream was terminated. Submission Page 20 John C. Sarallo - Appairent Technologies

21 FCSL MAC-ASYNC- DATA.req Transmission Resources available FCSL FCSL MAC-ASYNC- DATA.req Transmission CREATE- STREAM.ind Resources available FCSL Build beacon with requested asynchronous CTA beacon with requested asynchronous CTA MAC-ASYNC- DATA.cfm with ResultCode = SUCCESS asynchronous data frame MAC-ASYNC- DATA.ind MAC-ASYNC- DATA.cfm asynchronous data frame MAC-ASYNC- DATA.ind Figure MSC for reserving asynchronous data channel time Figure MSC for reserving asynchronous data channel time Submission Page 21 John C. Sarallo - Appairent Technologies

22 -INFO.req -INFO.req Info Info Request command -INFO.ind Info Info Request command -INFO.ind -INFO.cfm with ResultCode = SUCCESS Information command -INFO.rsp -INFO.cfm Information command -INFO.rsp Figure MSC for acquiring information regarding a specific or all of the s from the using the Information Request and Information commands Figure MSC for acquiring information regarding a specific or all of the s from the using the Information Request and Information commands Only change is s removed. Submission Page 22 John C. Sarallo - Appairent Technologies

23 PROBE.req PROBE.req Probe PROBE.cfm with ResultCode = SUCCESS Probe Request command with IR field = yy Probe Response command with IEs Provided = requested IEs PROBE.ind PROBE.rsp IR = information requested IE = information element Probe PROBE.cfm Probe Request command with IR field = yy Probe Response command with IEs Provided = requested IEs PROBE.ind PROBE.rsp IR = information requested IE = information element Figure MSC for acquiring IEs using the Probe Request and Probe s Figure MSC for acquiring IEs using the Probe Request and Probe s Only change is s removed. Submission Page 23 John C. Sarallo - Appairent Technologies

24 ANNOUNCE.req Announce ANNOUNCE.cfm with ResultCode = SUCCESS Announce command with IEs Provided ANNOUNCE.ind Figure MSC showing sending of information using the Announce command IE = information element ANNOUNCE.req Announce IE = information element ANNOUNCE.cfm Announce command with IEs Provided Announce Response command ANNOUNCE.ind ANNOUNCE.rsp Figure MSC showing sending of information using the Announce command MLME Announce Response and Announce added. Submission Page 24 John C. Sarallo - Appairent Technologies

25 CHANNEL- STATUS.req CHANNEL- STATUS.req ChannelStatus Channel Status CHANNEL- STATUS.ind ChannelStatus Channel Status CHANNEL- STATUS.ind CHANNEL- STATUS.cfm with ResultCode = SUCCESS Channel Status CHANNEL- STATUS.rsp CHANNEL- STATUS.cfm Channel Status CHANNEL- STATUS.rsp Channel status determined Channel status determined Figure MSC for determining the channel status between two s using the Channel Status Request and Channel Status s Figure MSC for determining the channel status between two s using the Channel Status Request and Channel Status s Only change is s removed. Submission Page 25 John C. Sarallo - Appairent Technologies

26 REMOTE- SCAN.req RemoteScan REMOTE- SCAN.cfm with ResultCode = SUCCESS Remote Scan beacon (optionally with quiet channel time for scan) Remote Scan Figure Remote scan MSC REMOTE- SCAN.ind SCAN.req SCAN.cfm REMOTE- SCAN.rsp beacon transmission (optionally with quiet channel time for scan) REMOTE- SCAN.req RemoteScan REMOTE- SCAN.cfm Remote Scan Remote Scan with Reason Code = Success Perform scan procedure REMOTE- SCAN.ind SCAN.req SCAN.cfm REMOTE- SCAN.rsp Figure Remote scan MSC Only real change is s removed. Submission Page 26 John C. Sarallo - Appairent Technologies

27 PICONET- PARM-CHANGE.req with new BSID or PNID PICONET- PARM-CHANGE.cfm with ResultCode = SUCCESS beacon with Piconet Parameter Change IE with new BSID or PNID x # of beacons before switching to new BSID beacon with Piconet Parameter Change IE with new BSID or PNID New PNID or BSID for piconet -1-1 Figure MSC for changing either the PNID or BSID for a piconet beacon with Piconet Parameter Change IE indicating new BSID or PNID x # of beacons before switching to new PNID or BSID beacon with Piconet Parameter Change IE indicating new BSID or PNID beacon with new BSID or PNID -1-1 Figure MSC for changing either the PNID or BSID for a piconet PME is responsible for information in the beacon so the PICONET-PARM-CHANGE primitives are no longer needed. Submission Page 27 John C. Sarallo - Appairent Technologies

28 Channel status determined to be unsatisfactory Channel status determined to be unsatisfactory PICONET- PARM-CHANGE.req moves to new channel PICONET- PARM-CHANGE.cnf with ResultCode = SUCCESS beacon with Piconet Parameter Change IE x # of beacons before switching to new channel beacon with Piconet Parameter Change IE beacon (on new channel) moves to new channel Figure MSC for changing piconet parameters beacon with Piconet Parameter Change IE indicating new Channel x # of beacons before switching to new Channel beacon with Piconet Parameter Change IE indicating new Channel and all s move to new channel beacon on new channel Figure MSC for changing piconet parameters Submission Page 28 John C. Sarallo - Appairent Technologies

29 TX-POWER -CHANGE.ind Transmit Power Change command with TX Power Change = yy TX-POWER- CHANGE.req with TrgtID =, TXPowerChange = yy TXPowerChange TX-POWER- CHANGE.cfm with ResultCode = SUCCESS Transmit Power Change with TX Power Change = yy Transmit Power Change with Reason Code = Success Determines that a TX Power Change at is needed TXPowerChange Figure Transmit power change MSC Figure Transmit power change MSC responsible for TX power adaptation, therefore TX-POWER-CHANGE primitives are no longer needed. Submission Page 29 John C. Sarallo - Appairent Technologies

30 PS-SET- INFORMATION.req PSRequest PS-SET- INFORMATION.cfm with PSSetStructureSet, ResultCode = SUCCESS PS Set Information PS Set Information Response command with PS Set Structures Figure MSC for PS set information exchange PS-SET- INFORMATION.req PSRequest PS-SET- INFORMATION.cfm PS Set Information PS Set Information with PS Set Structures PS-SET- INFORMATION.ind PS-SET- INFORMATION.rsp Figure MSC for PS set information exchange PME is responsible for maintaing power set information, therefore, PS-SET-INFORMATION indication and response primitives are needed. Submission Page 30 John C. Sarallo - Appairent Technologies

31 SPS-CONFIGURE.req with SPSSetIndex = Unallocated DSPS Set, SPSSetOperation = join, WakeInterval = N SPS-CONFIGURE.cfm with SPSSetIndex = new PS Set, SPSSetOperation = join, NextWake = N ResultCode = SUCCESS New SPS set created PSRequest SPS Configuration Request command with SPS Set Index = Unallocated DSPS set, Operation Type = join, Wake Interval = N SPS Configuration Response command with SPS Set Index = new DSPS set index, Next Wake = X SPS-CONFIGURE.req PSRequest SPS-CONFIGURE.cfm SPS Configuration Request command with SPS Set Index = Unallocated DSPS set, Operation Type = join, Wake Interval = N SPS Configuration Response command with SPS Set Index = new DSPS set index, Next Wake = X SPS-CONFIGURE.ind SPS-CONFIGURE.rsp New DSPS set created Figure MSC for DSPS set creation Figure MSC for DSPS set creation PME is responsible for maintaing power set information, therefore, SPS-CONFIGURE indication and response primitives are needed. Submission Page 31 John C. Sarallo - Appairent Technologies

32 SPS-CONFIGURE.req with SPSSetIndex = zz, OperationType = join, WakeInterval = N zz = valid SPS set index PSRequest SPS-CONFIGURE.cfm with SPSSetIndex = zz, OperationType = join, NextWake = X ResultCode = SUCCESS Joined PSPS or SPS set SPS Configuration Request command with SPS Set Index = zz, Operation Type = join, Wake Interval = N SPS Configuration Response command with SPS Set Index = zz, Next Wake = X Non-member of Set zz SPS-CONFIGURE.req Member of Set zz PSRequest SPS-CONFIGURE.cfm SPS Configuration Request command with SPS Set Index = zz, Operation Type = join, Wake Interval = N SPS Configuration Response command with SPS Set Index = zz, Next Wake = X SPS-CONFIGURE.ind SPS-CONFIGURE.rsp zz = valid SPS set index Added to Set zz Figure MSC showing a joining an existing SPS set Figure MSC showing a joining an existing SPS set PME is responsible for maintaing power set information, therefore, SPS-CONFIGURE indication and response primitives are needed. Submission Page 32 John C. Sarallo - Appairent Technologies

33 SPS-CONFIGURE.req with SPSsetIndex = zz, OperationType = leave zz = valid PS set index SPS-CONFIGURE.cfm with SPSsetIndex = zz, OperationType = leave, ResultCode = SUCCESS Left SPS set = zz PSRequest SPS Configuration Request command with SPS Set = zz, Operation Type = leave Figure MSC showing a leaving an SPS set Member of Set zz Non-member of Set zz SPS-CONFIGURE.req PSRequest SPS-CONFIGURE.cfm SPS Configuration Request command with SPS Set = zz, Operation Type = leave SPS Configuration Response command with SPS Set Index = zz SPS-CONFIGURE.ind SPS-CONFIGURE.rsp zz = valid SPS set index Romved from Set zz Figure MSC showing a leaving an SPS set PME is responsible for maintaing power set information, therefore, SPS-CONFIGURE indication and response primitives are needed. Submission Page 33 John C. Sarallo - Appairent Technologies

34 PM Mode = ACTIVE PM-MODE-CHANGE.req with PMMode = SPS PM-MODE-CHANGE.cfm with ResultCode = SUCCESS PM Mode = SPS PSRequest PM Mode Change command with PM Mode = PS beacon with PS Status IE(s) with bit for set in ID Bitmap Figure MSC showing initiated PM mode change from ACTIVE to an SPS mode PM Mode is ACTIVE PM Mode is SPS PM-MODE -CHANGE.req PSRequest PM-MODE -CHANGE.cfm PM Mode Change with PM Mode = SPS PM Mode Change Response Command with Reason Code = Success PM Mode is ACTIVE PM- MODE- CHANGE.req PM Mode is SPS PM- MODE -CHANGE.cfm beacon with PS Status IE(s) with bit for set in ID Bitmap PM Mode is ACTIVE PM Mode is SPS Figure MSC showing initiated PM mode change from ACTIVE to an SPS mode PME is responsible for maintaing power save state information, therefore, PM-MODE-CHANGE indication and response primitives are needed. Other s aware of mode change when they receive beacon. Submission Page 34 John C. Sarallo - Appairent Technologies

35 PM Mode = ACTIVE PM-MODE-CHANGE.req with PMMode = APS PM-MODE-CHANGE.cfm with ResultCode = SUCCESS PM Mode = APS PSRequest PM Mode Change command with PM Mode = APS beacon with PS Status IE for PS Set =0 with bit set for in ID Bitmap Figure MSC showing initiated PM mode change from ACTIVE to APS PM Mode is ACTIVE PM Mode is APS PM-MODE -CHANGE.req PSRequest PM-MODE -CHANGE.cfm PM Mode Change with PM Mode = APS PM Mode Change Response Command with Reason Code = Success beacon with PS Status IE for PS Set =0 with bit set for in ID Bitmap PM Mode is ACTIVE PM- MODE- CHANGE.req PM Mode is APS PM- MODE -CHANGE.cfm PM Mode is ACTIVE PM Mode is APS Figure MSC showing initiated PM mode change from ACTIVE to APS PME is responsible for maintaing power save state information, therefore, PM-MODE-CHANGE indication and response primitives are needed. Other s aware of mode change when they receive beacon. Submission Page 35 John C. Sarallo - Appairent Technologies

36 PM-MODE-CHANGE.req with PMMode = ACTIVE PSRequest PM-MODE-CHANGE.cfm with ResultCode = SUCCESS PM Mode = ACTIVE PM Mode Change command with PM Mode = ACTIVE beacon with status bit for cleared in all PS Status IE(s) Figure MSC showing initiated PM mode change from any PS mode to ACTIVE PM Mode is APS or SPS PM Mode is ACTIVE PM-MODE -CHANGE.req PSRequest PM-MODE -CHANGE.cfm PM Mode Change with PM Mode = ACTIVE PM Mode Change Response Command with Reason Code = Success beacon with status bit for cleared in all PS Status IE(s) PM Mode is APS or SPS PM- MODE- CHANGE.ind PM Mode is ACTIVE PM- MODE -CHANGE.rsp PM Mode is APS or SPS PM Mode is ACTIVE Figure MSC showing initiated PM mode change from any PS mode to ACTIVE PME is responsible for maintaing power save state information, therefore, PM-MODE-CHANGE indication and response primitives are needed. Other s aware of mode change when they receive beacon. Submission Page 36 John C. Sarallo - Appairent Technologies

37 CREATE- STREAM.req with CTARateType = 0 CREATE- STREAM.cfm with ResultCode = SUCCESS Channel time request process with and Build beacon Figure Message sequence showing MLME initiated PM mode change from DSPS to ACTIVE in response to a new chanel time allocation beacon in 's wake superframe, CTA Status IE with DestID = ID, PCTM IE with 's ID bit set, CTA block with SrcID = ID, DestID = ID PM Mode Change command with PM Mode = ACTIVE beacon with requested CTA and without 's ID bit set in either the PS Status IE or in the PCTM IE in DSPS mode changes state to ACTIVE PM- MODE-ACTIVE.ind with PMActiveEvent = DATA_PENDING Stream to CREATE- STREAM.req Request CREATE- STREAM.cfm PM Mode is ACTIVE PM Mode is DSPS with CTARateType = 0 CREATE- STREAM.ind Resources available CREATE- STREAM.rsp with Reason Code = Success, in PS Mode beacon in 's wake superframe, CTA Status IE with DestID = ID, PCTM IE with 's ID bit set, CTA block with SrcID = ID, DestID = ID PM- MODE- CHANGE.ind PM Mode is ACTIVE PM- MODE -CHANGE.rsp PM Mode Change Request command with PM Mode = ACTIVE PM Mode Change Response command with Reason Code = Success beacon with requested CTA and without 's ID bit set in either the PS Status IE or in the PCTM IE PM-MODE -CHANGE.req PSRequest PM Mode is DSPS PM- MODE -CHANGE.rsp with ResultCode = SUCCESS PM Mode is ACTIVE Stream from Figure Message sequence showing MLME initiated PM mode change from DSPS to ACTIVE in response to a new chanel time allocation To be consistent with other scenarios, requesting is aware of stream when it receives a. Submission Page 37 John C. Sarallo - Appairent Technologies

38 -1 SECURITY -INFO.req with queried ID = nn SECURITY -INFO.cfm with Security Record for ID = nn -1 Security Information Security Information command SECURITY -INFO.ind SECURITY -INFO.rsp with Security Record for ID = nn -1-1 SECURITY -INFO.req Request SECURITY -INFO.cfm Security Information with queried ID = nn Security Information command with Security Record for ID = nn SECURITY -INFO.ind SECURITY -INFO.rsp Figure 148 Message sequence chart for - Security information request Figure 148 Message sequence chart for - Security information request Only change is s removed. Submission Page 38 John C. Sarallo - Appairent Technologies

39 New New New New SECURITY -INFO.req with queried ID = BcstID SECURITY -INFO.cfm with Security Records for all s Security Information Security Information command SECURITY -INFO.ind SECURITY -INFO.rsp with Security records for all s SECURITY -INFO.req Request SECURITY -INFO.cfm Security Information with queried ID = BcstID Security Information command with Security records for all s SECURITY -INFO.ind SECURITY -INFO.rsp Figure 149 Message sequence chart for New -Old Security Information transfer Figure 149 Message sequence chart for New -Old Security Information transfer Only change is s removed. Submission Page 39 John C. Sarallo - Appairent Technologies

40 SECURITY- MESSAGE.req with SecurityInformation SecMsg SECURITY -MESSAGE.cfm with ResultCode = SUCCESS Security Message command SECURITY- MESSAGE.ind with SecurityInformation SECURITY- MESSAGE.req Security Message command with SecurityInformation SECURITY- MESSAGE.ind Figure 150 Message sequence chart for sending security information with the Security Message command Figure 150 Message sequence chart for sending security information with the Security Message command Fire and forget so no confirm is needed. Submission Page 40 John C. Sarallo - Appairent Technologies

41 -1 DISTRIBUTE- KEY.ind -1 Distribute DISTRIBUTE- KEY.req Distribute DISTRIBUTE- KEY.cfm with ResultCode = SUCCESS -1 DISTRIBUTE- KEY.ind -1 Distribute DISTRIBUTE- KEY.req Figure 151 Message sequence chart for - key distribution Figure 151 Message sequence chart for - key distribution Fire and forget scenario Submission Page 41 John C. Sarallo - Appairent Technologies

42 -1 DISTRIBUTE- KEY.ind DISTRIBUTE- KEY.rsp -1 Distribute Distribute DISTRIBUTE- KEY.req Distribute DISTRIBUTE- KEY.cfm with ResultCode = SUCCESS -1 DISTRIBUTE- KEY.ind DISTRIBUTE- KEY.rsp -1 Distribute Distribute DISTRIBUTE- KEY.req Distribute DISTRIBUTE- KEY.cfm Figure 152 Message sequence chart for peer-to-peer key distribution Figure 152 Message sequence chart for peer-to-peer key distribution Only change is s removed. Submission Page 42 John C. Sarallo - Appairent Technologies

43 -1 REQUEST- KEY.req Request REQUEST- KEY.cfm with ResultCode = SUCCESS -1 Request command Request Response command originator REQUEST- KEY.ind REQUEST- KEY.rsp orignator Figure 153 Message sequence chart for key request -1 REQUEST- KEY.req Request REQUEST- KEY.cfm -1 Request command Request Response command Figure 153 Message sequence chart for key request Only change is s removed. originator REQUEST- KEY.ind REQUEST- KEY.rsp orignator Submission Page 43 John C. Sarallo - Appairent Technologies

44 association process with parent and if required, establishes secure membership channel time request for a pseudo-static CTA with itself as SrcID and DestID START- DEPENDENT-.req START- DEPENDENT-.cfm with ResultCode = SUCCESS initialization procedure First beacon with child parameters Figure 99 - MSC for creating a child piconet association process with parent and if required, establishes secure membership channel time request for a pseudo-static CTA with itself as SrcID and DestID Piconet initialization procedure Now Now First beacon with child parameters Figure 99 - MSC for creating a child piconet The PME ( ) maintains the information that is contained in a beacon so a START primitive is no longer needed because the PME can simply make a request to send a beacon when it is ready to start a piconet. When a piconet is started, a timer is required for transmitting beacons at the superframe interval. Submission Page 44 John C. Sarallo - Appairent Technologies

45 association process with parent piconet and requesting neighbor. assigns neighbor ID. channel time request for pseudo-static CTA with itself as SrcID and DestID START- DEPENDENT-.req START- DEPENDENT-.cfm (w/ ResultCode = SUCCESS) initialization procedure First beacon with neighbor parameters (if neighbor piconet) Figure MSC for initiating a neighbor piconet association process with parent piconet and requesting neighbor. assigns neighbor ID. Piconet initialization procedure Now channel time request for pseudo-static CTA with itself as SrcID and DestID Now First beacon with neighbor parameters (if neighbor piconet) Figure MSC for initiating a neighbor piconet The PME ( ) maintains the information that is contained in a beacon so a START primitive is no longer needed because the PME can simply make a request to send a beacon when it is ready to start a piconet. When a piconet is started, a timer is required for transmitting beacons at the superframe interval. Submission Page 45 John C. Sarallo - Appairent Technologies

46 Handover - HANDOVER.req - HANDOVER.ind (STARTED) Information - -INFO.cfm - HANDOVER.rsp New MLME received all related information and -HANDOVER.rsp assumes control, now is and MLME. - HANDOVER.ind (COMPLETED) Handover command Handover Information command PS Information Handover Optional security information handover - HANDOVER.cfm Old beacon with Handover IE Old beacon with Handover IE Original relinquishes control, now is -1 and -1 MLME. New beacon New beacon NEW -.ind OPT - HANDOVER.ind Stream from - HANDOVER.rsp assumes control, now is and MLME. Handover Handover Handover with Reason Code = Success, Ready for Handover - HANDOVER.req beacon with allocated stream CTA Mandatory and Optional Handover Information Transfered from to Old beacon with Handover IE - HANDOVER.cfm Old beacon with Handover IE Original relinquishes control, now is -1 and -1 MLME. New beacon New beacon Stream to Figure 94 - handover MSC Figure 94 - handover MSC Shows handover data is optionally transfered in a stream. Submission Page 46 John C. Sarallo - Appairent Technologies

47 - Handover HANDOVER.req Handover - HANDOVER.ind (STARTED) becomes member of parent piconet (if not already member) - -INFO.cfm - HANDOVER.rsp Information command Handover Information command PS Set Information New MLME received all related information and -HANDOVER.rsp Handover with Reason Code = ID in parent piconet assumes control, now is and MLME. - HANDOVER.ind (COMPLETED) Optional security information handover - HANDOVER.cnf requests isoch stream modification, new Target ID for existing Stream Index Old beacon with handover IE Old beacon with handover IE Original relinquishes control, now is -1 and -1 MLME. New beacon NEW -.ind OPT - HANDOVER.ind becomes member of parent piconet (if not already member) Stream from - HANDOVER.rsp Old beacon with Handover IE assumes control, now is and MLME. Handover Handover Handover with Reason Code = Success, Ready for Handover - HANDOVER.req beacon with allocated stream CTA Mandatory and Optional Handover Information Transfered from to - HANDOVER.cfm Old beacon with Handover IE Original relinquishes control, now is -1 and -1 MLME. New beacon New beacon Stream to requests isoch stream modification, new Target ID for existing Stream Index Figure 95 - Successful handover in a dependent piconet Figure 95 - Successful handover in a dependent piconet Submission Page 47 John C. Sarallo - Appairent Technologies

48 - HANDOVER.ind (STARTED) fails to become member of parent piconet - HANDOVER.rsp ReasonCode = 0xFE Handover Handover Handover with Reason Code = 0xFE - HANDOVER.req - HANDOVER.cfm ReasonCode = FAILED - HANDOVER.ind fails to become member of parent piconet - HANDOVER.rsp Handover Handover Handover with Reason Code = Unable to Join Parent - HANDOVER.req begins handover data transfer process - HANDOVER.cfm Original remains of dependent piconet Figure 96 - Failed dependent handover when target fails to join parent piconet Figure 96 - Failed dependent handover when target fails to join parent piconet Submission Page 48 John C. Sarallo - Appairent Technologies

49 MLME - Handover HANDOVER.req Handover - HANDOVER.ind (STARTED) becomes member of parent piconet (if not already member) - -INFO.cfm - HANDOVER.rsp New MLME received all related information and -HANDOVER.rsp Information command Handover Information command PS Set Information MLME Optional security information handover Handover Reason Code = ID in parent piconet request for isoch stream modification, new Target ID for existing Stream Index fails handover request command, Handover Status = Cancelled - HANDOVER.cnf ResultCode = FAILED Original remains of dependent piconet MLME - HANDOVER.ind becomes member of parent piconet (if not already member) OPT Stream from - HANDOVER.rsp - HANDOVER.ind - HANDOVER.rsp Handover Handover Handover with Reason Code = Success, Ready for Handover Handover Handover Handover Status = Cancelled Handover with Reason Code = Success, Handover Cancelled - HANDOVER.req beacon with allocated stream CTA Mandatory and Optional Handover Information Transfered from to - HANDOVER.cfm - HANDOVER.req - HANDOVER.cfm Stream to request for isoch stream modification, new Target ID for existing Stream Index fails Original remains of dependent piconet Figure 97 - Failed dependent handover when control for the dependent piconet CTA is handed over in the parent piconet Figure 97 - Failed dependent handover when control for the dependent piconet CTA is handed over in the parent piconet Submission Page 49 John C. Sarallo - Appairent Technologies

50 3. MLME Impact Summary Table 1: Summary of MLME primitives (Continued) The following identifies the neccessary changes to the existence of MLME primitives based on the suggested MSCs in the previous section. RESET Table 1: Summary of MLME primitives Name Request Indication Response Confirm X SCAN X X START X X START-DEPENDENT X X SYNCH X X ATP-EXPIRED ASSOCIATE X X X X -ASSOCIATION- INFO DISASSOCIATE X X X REQUEST-KEY X X X X DISTRIBUTE-KEY X X X X X X PICONET-SERVICES X X X CREATE-STREAM X X X X MODIFY-STREAM X X X X TERMINATE-STREAM X X X X MULTICAST-RX-SETUP X CHANNEL-STATUS X X X X REMOTE-SCAN X X X X PICONET-PARM- CHANGE Name Request Indication Response Confirm X TX-POWER-CHANGE X X X PS-SET-INFORMATION X X X X SPS-CONFIGURE X X X X PM-MODE-CHANGE X X X X PM-MODE-ACTIVE BEACON X X X X MEMBERSHIP-UPDATE X SECURITY-ERROR X SECURITY-MESSAGE X X X -HANDOVER X X X X NEW- X -INFO X X X X SECURITY-INFO X X X X CREATE-ASIE X X RECEIVE-ASIE X PROBE X X X X ANNOUNCE X X X X Submission Page 50 John C. Sarallo - Appairent Technologies

51 The following table shows the fully editing MLME table after all deletions and additions. Table 2: Summary of MLME primitives Table 2: Summary of MLME primitives (Continued) Name Request Indication Response Confirm PM-MODE-CHANGE X X X X Name Request Indication Response Confirm BEACON X X RESET X SCAN X X ATP-EXPIRED X ASSOCIATE X X X X DISASSOCIATE X X REQUEST-KEY X X X X DISTRIBUTE-KEY X X X X MEMBERSHIP-UPDATE X SECURITY-ERROR X SECURITY-MESSAGE X X -HANDOVER X X X X -INFO X X X X SECURITY-INFO X X X X PROBE X X X X ANNOUNCE X X X X PICONET-SERVICES X X CREATE-STREAM X X X X MODIFY-STREAM X X X X TERMINATE-STREAM X X X X MULTICAST-RX-SETUP X CHANNEL-STATUS X X X X REMOTE-SCAN X X X X PS-SET-INFORMATION X X X X SPS-CONFIGURE X X X X Submission Page 51 John C. Sarallo - Appairent Technologies

52 4. Command Impact Summary The following commands would need to be renamed if the suggested MSCs of section 2 were adopted. Transmit Power Change becomes Transmit Power Change Request PM Mode Change becomes PM Mode Change Request The following commands would need to be created if the suggested MSCs of section 2 were adopted. Note that these commands will likely have zero length payloads or only a reason code. Announce Response Transmit Power Change Response PM Mode Change Response Submission Page 52 John C. Sarallo - Appairent Technologies