1111045201000sstatemachinereorder.docx

1、1111045201000sstatemachinereorderIEEE P802.11Wireless LANsA Re-Ordering of the (Authenticated) Peer Link Management ProtocolDate: 2011-03-17Author(s):NameAffiliationAddressPhoneemailDan HarkinsAruba Networks1322 Crossman ave, Sunnyvale, CA+1 408 227 4500dharkins at arubanetworks dot comGuenael Strut

2、tPowerwave Technologies1801 E St Andrew placeSanta Ana, CA 92705+1 714 466 1792gstrutt at pwav dot comAbstractThis submission substantially re-orders the state machine text for MPM and AMPE.Modify section 11C.4.4 and sub-clauses as indicated:11C.4.4 Mesh Peering Management finite state machine (MPM

3、FSM)11C.4.4.1 GeneralEach mesh peering instance, including its states and resource, are managed by a Mesh Peering Management finite state machine (MPM FSM). The MPM FSM uses MLME primitives to control the mesh STA to send and receive Mesh Peering Management frames.11C.4.4.2 StatesThe Mesh Peering Ma

4、nagement finite state machine uses the following six states: IDLEIDLE state is a terminal state. In the IDLE state, the MPM FSM is ready to start a new mesh peering instance by either passively listening for an incoming Mesh Peering Open frame or actively initiating a mesh peering instance. OPN_SNTI

5、n the OPN_SNT state, the finite state machine has sent a Mesh Peering Open frame and is waiting for aMesh Peering Open frame and Mesh Peering Confirm frame from the candidate peer mesh STA. CNF_RCVDIn the CNF_RCVD state, the finite state machine has received a Mesh Peering Confirm frame, but has not

6、 received a Mesh Peering Open frame. The mesh STA has not sent the corresponding Mesh Peering Confirm frame yet. OPN_RCVDIn the OPN_RCVD state, the finite state machine has received only the Mesh Peering Open frame but not the Mesh Peering Confirm. The mesh STA has also sent a Mesh Peering Confirm f

7、rame upon receiving a Mesh Peering Open frame. ESTABIn the ESTAB state, the finite state machine has received both the Mesh Peering Open and Mesh Peering Confirm frames. The mesh STA has also sent both the Mesh Peering Open frame and Mesh Peering Confirm frame. The mesh peering is established and co

8、nfigured for exchanging frames with the peer mesh STA in the ESTAB state. HOLDINGIn the HOLDING state, the finite state machine is closing the mesh peering instance with the peer mesh STA or the candidate peer mesh STA. 11C.4.4.3 Events and actionsThe finite state machine uses three types of events:

9、 1) events for state machine transitions; 2) external events generated by frame processing; and 3) events associated with internal timers.The events for state machine transitions are: CNCL(localLinkID, peerMAC, ReasonCode)Used to instruct the mesh peering instance to cancel the mesh peering with the

10、 peer mesh STA. localLinkID identifies the MPM FSM for the corresponding mesh peering instance. peerMAC is the MAC address of the peer mesh entity. ReasonCode is used to inform the reason to cancel the mesh peering instance. See 11C.3.6.1 (Mesh Peering Close processing). ACTOPN(peerMAC, localLinkID)

11、The SME uses this event to create a new mesh peering instance to actively initiate the mesh peering establishment with the candidate peer mesh STA whose MAC address is peerMAC. localLinkID identifies the MPM FSM.The events generated by frame processing are: OPN_ACPTPeeringOpen_Accept(peerMAC, peerLi

12、nkID) event indicates that a Mesh Peering Open frame meeting the correctness criteria of 11C.4.3.2 (Mesh Peering Open frames) has been received from peerMAC for the mesh peering instance identified by peerLinkID. OPN_RJCTPeeringOpen_Reject(peerMAC, peerLinkID, Configuration, reasonCode) event indica

13、tes that a Mesh Peering Open frame from peerMAC for the mesh peering instance identified by peerLinkID is rejected due to incomplete or erroneous configuration, as indicated by the Confiuration, with reasonCode being the specific reason for rejection of the Mesh Peering Open frame. See 11C.3.4.2 (Me

14、sh Peering Open processing). CNF_ACPTPeeringConfirm_Accept(peerMAC, localLinkID, peerLinkID) event indicates that a Mesh Peering Confirm frame meeting the correctness criteria of 11C.4.3.3 (Mesh Peering Confirm frames) has been received from peerMAC for the mesh peering instance identified by localL

15、inkID and peerLinkID. CNF_RJCTPeeringConfirm_Reject(peerMAC, localLinkID, peerLinkID, reasonCode) event indicates that a Mesh Peering Confirm frame from peerMAC for the mesh peering instance identified by localLinkID, peerLinkID is rejected due to incomplete or erroneous configuration, and reasonCod

16、e is the specific reason for rejection of the Confirm frame. See 11C.3.5.2 (Mesh Peering Confirm processing). CLS_ACPTPeeringClose_Accept(peerMAC, localLinkID, peerLinkID, reasonCode) event indicates that a Mesh Peering Close frame meeting the correctness criteria of 11C.4.3.4 (Mesh Peering Close fr

17、ames) has been received from peerMAC for the mesh peering instance identified by localLinkID and peerLinkID. The reasonCode specifies the reason that caused the generation of the Mesh Peering Close frame. See 11C.3.6.1 (Mesh Peering Close processing). REQ_RJCTPeeringRequest_Reject(peerMAC, peerLinkI

18、D, reasonCode) event indicates a special incidence that the mesh STA rejects the incoming Mesh Peering Open frame requesting to set up a new mesh peering for some specified reason. The incoming request is identified by the peerMAC, peerLinkID is the peerLinkID received from the Mesh Peering Open fra

19、me, and reasonCode is the specific reason for rejection of the Mesh Peering Open frame. See 11C.3.4.2 (Mesh Peering Open processing).1. The finite state machine may take an action triggered by an event. It uses two types of actions: sending a Mesh Peering Management frame and handling a timer. Actio

20、ns related to sending a Mesh Peering Management frame are as follows: sndOPN sendOpen(peerMAC, localLinkID, Configuration) is the action that the mesh STA takes to send a Mesh Peering Open frame to the candidate peer mesh STA, whose MAC address is peerMAC. The MLME-MeshPeeringManagement.request prim

21、itive shall be invoked to send the frame to the peer mesh entity. sndCNF sendConfirm(peerMAC, localLinkID, peerLinkID, Configuration) is the action that the mesh STA takes to send a Mesh Peering Confirm frame to the candidate peer mesh STA, whose MAC address is peerMAC. The MLME-MeshPeeringManagemen

22、t.request primitive shall be invoked to send the frame to the peer mesh entity. sndCLS sendClose(peerMAC, localLinkID, peerLinkID, reasonCode) is the action that the mesh STA takes to send a Mesh Peering Close frame to the peer mesh STA or candidate peer mesh STA, whose MAC address is peerMAC. The M

23、LME-MeshPeeringManagement.request primitive shall be invoked to send the frame to the peer mesh entity. 11C.4.4.4 TimersThree timers are used by the finite state machine:2. The retryTimer triggers a resend of the Mesh Peering Open frame when a Mesh Peering Confirm frame was not received as a respons

24、e. The retryTimer is set to the dot11MeshRetryTimeout. 3. The confirmTimer signals that a link establishment attempt should be aborted because a Mesh Peering Confirm frame responding to a Mesh Peering Open frame was never received. The confirmTimer is set to the value of dot11MeshConfirmTimeout.4. T

25、he holdingTimer signals that its mesh peering instance may be completely closed and facilitates graceful shutdown. The holdingTimer is set to the value of dot11MeshHoldingTimeout.The events associated with internal timers are indicated in the state machine as acronyms that indicate timer expiry . Wi

26、th each timer event there is an associated action. TOR1 This event indicates that the retryTimer has expired and dot11MeshMaxRetries has not been reached. The Mesh Peering Open frame shall be resent, an action indicated in the state machine by setR. TOR2This event indicates that the retryTimer has e

27、xpired and dot11MeshMaxRetries has been reached. The mesh peering instance shall be closed when TOR2 occurs. TOCThis event indicates that the confirmTimer has expired. When TOC event occurs, the mesh peering instance shall be closed, an action indicated in the state machine as setC. TOHThis event in

28、dicates that the holdingTimer has expired. When TOH occurs, the mesh peering instance shall be closed and the finite state machine shall transition to IDLE state, an action indicated in the state machine as setH. 11C.4.4.5 State transitionsTable11C-1 (Mesh Peering Management finite state machine) an

29、d Figure11C-2 (Finite state machine of Mesh Peering Management protocol) summarize the state transitions for the Mesh Peering Management protocol.In Table11C-1 (Mesh Peering Management finite state machine), each row represents state transitions from the state to all other states. A blank entry indi

30、cates animpossible transition.Table 11C-1 Mesh Peering Management finite state machineTo StateIDLEOPN_SNTCNF_RCVDOPN_RCVDESTABHOLDINGFrom StateIDLEREQ_RJCT / sndCLSACTOPN/ (sndOPN, setR)OPN_ACPT/ (sndOPN, sndCNF, setR)OPN_SNTTOR1/ (sndOPN, setR)CNF_ACPT/ (clR, setC)OPN_ACPT/ (sndCNF)CLS_ACPT, OPN_RJ

31、CT, CNF_RJCT, TOR2, CNCL/ (sndCLS, clR, setH)CNF_RCVDOPN_ACPT / (clC, sndCNF)CLS_ACPT, OPN_RJCT, CNF_RJCT, CNCL/ (sndCLS, clC, setH)TOC / (sndCLS, setH)OPN_RCVDOPN_ACPT/ sndCNF TOR1 / (sndOPN, setR)CNF_ACPT / clRCLS_ACPT, OPN_RJCT, CNF_RJCT,TOR2, CNCL/ (sndCLS, clR, setH)ESTABOPN_ACPT / sndCNFCLS_ACPT, OPN_RJCT, CNF_RJCT, CNCL/ (sndCLS, setH)HOLDINGTOH/, CLS_ACPT /clHOPN_ACPT, CNF_ACPT, OPN_RJCT, CNF_RJCT/ sndCLSIn Figure11C-2 (Finite state machine of Mesh Peering Management protocol), each arrow represents a state transition. Figure 11C-2 Finite state machine of Mesh Peering Management proto