1 September 2016 IEEE P802.15 -16-0661-00-0008
1
2 IEEE P802.15 3 Wireless Personal Area Networks
4
Project IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs)
Title Resolution for service primitive definitions: Synchronization
Date September 14, 2016 Submitted
Source Byung-Jae Kwak (ETRI), Nah-Oak Song (KAIST)
Response
Abstract
Purpose For discussion & Approval
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 contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein.
Release The contributor acknowledges and accepts that this contribution becomes the property of IEEE and may be made publicly available by P802.15. 5
2Submission Page 1 Hernandez, Li, Kojima (NICT) 1 September 2016 IEEE P802.15 -16-0661-00-0008
11. Overview
22. Normative references
33. Definitions
44. General description
55. MAC functional description
66. MAC services
76.1 MLME-SAP primitives
86.1.1 PIB access
96.1.2 Discovery primitives
106.1.3 Peering primitives
116.1.4 De-peering primitives
126.1.5 Frame error notification primitives
136.1.6 Reset MAC sublayer
146.1.7 Receiver enable
156.1.8 Channel scanning
166.1.9 Group configuration
176.1.10 Synchronization
186.1.10.1 MLME-SYNCHRONIZATION.request
19The primitive requests to synchronize with other PDs by acquiring and tracking their synchronization 20signal. The properties of this primitive are:
21MLME-SYNCHRONIZATION.request{
22 ChannelNumber;
23 ChannelPage;
24 TrackMode;
25}
26The primitive parameters are defined in Table 1.
2Submission Page 2 Hernandez, Li, Kojima (NICT) 1 September 2016 IEEE P802.15 -16-0661-00-0008
1 Table 1—MLME-SYNCHRONIZATION.request parameters Property Type Valid range Description
As defined in Error: The channel number ChannelNumber Integer Reference source not on which to attempt found synchronization.
As defined in Error: The channel page on ChannelPage Integer Reference source not which to attempt found synchronization.
TRUE if the PD is to synchronize from the next synchronization TrackMode Boolean TRUE, FALSE period. FALSE if the PD is to synchronize with only the next synchronization period.
2
3When the primitive is received by the MLME, it will set phyCurrentPage and phyCurrentChannel equal 4to the values of the ChannelPage and ChannelNumber, respectively. If the TrackMode parameter is 5equal to TRUE, the MLME will track the synchronization period, i.e., enable its receiver just before the 6expected time of synchronization period. If the TrackMode parameter is equal to FALSE, the MLME 7will locate the synchronization period, but not continue to track it.
8If this primitive is received by the MLME while it is currently tracking the synchronization period, the 9MLME will not discard the primitive but will treat it as a new synchronization request.
106.1.10.1.1 When generated
11This primitive is generated by the next higher layer to request MLME to synchronize with other PDs.
126.1.10.1.2 Effect on receipt
13MLME attempts synchronization with other PDs by acquiring and tracking their synchronization 14signal. The result of synchronization is reported to the next higher layer using MLME- 15SYNCHRONIZATION.confirm described in 6.1.10.2.
166.1.10.2 MLME-SYNCHRONIZATION.confirm
17The primitive reports the results of synchronization request to the higher layer. The properties of this 18primitive are:
19MLME-SYNCHRONIZATION.confirm{
20 Status;
21}
22The primitive parameters are defined in Table 1.
23 Table 2—MLME-SYNCHRONIZATION.confirm parameter Property Type Valid range Description
2Submission Page 3 Hernandez, Li, Kojima (NICT) 1 September 2016 IEEE P802.15 -16-0661-00-0008
SUCCESS, FAILURE, The result of the Status Enumeration CHANNEL_ACCESS_FAILURE synchronization
16.1.10.2.1 When generated
2This primitive is generated by MLME in response to an MLME-SYNCHRONIZATION.request, 3described in 6.1.10.1, received from the next higher layer, to report the result of synchronization.
46.1.10.2.2 Effect on receipt
5The next higher layer receives the result of MLME-SYNCHRONIZATION.request it has requested to 6MLME.
76.1.10.3 MLME-SYNCHRONIZATION-LOSS.indication
8The primitive indicates the loss of synchronization. The properties of this primitive are:
9MLME-SYNCHRONIZATION-LOSS.indication{
10 LossReason;
11 GroupID;
12 PD_ID;
13 ChannelNumber;
14 ChannelPage;
15}
16The primitive parameters are defined in Table 3.
17 Table 3—MLME-SYNCHRONIZATION-LOSS.indication parameters Property Type Valid range Description
The reason LossReason Enumeration SYNC_LOST synchronization was lost.
Group ID of the PD MulticastGroup_ID Integer 0 to 255 that has lost synchronization
The MAC address of PD_ID MAC address PD specific the PD that has lost synchronization
The channel number Any valid channel number as on which the PD that ChannelNumber Integer defined in Error: Reference has lost source not found synchronization operated.
ChannelPage Integer Any valid channel page as The channel page on defined in Error: Reference which the PD that source not found has lost
2Submission Page 4 Hernandez, Li, Kojima (NICT) 1 September 2016 IEEE P802.15 -16-0661-00-0008
synchronization operated.
1
2The primitive is generated by the MLME of a PD and issued to its next higher layer in the event of a 3loss of synchronization. The reason for synchronization loss is expressed by the parameter of 4LossReason:
5SYNC_LOST – The PD has missed synchronization for five superframes.
66.1.10.3.1 When generated
7This primitive is generated by MLME to indicate the loss of synchronization to the next higher layer.
86.1.10.3.2 Effect on receipt
9The next higher layer shall generate MLME-SYNCHRONIZATION.request, described in 6.1.10.1, to 10request MLME to synchronize with other PDs.
116.1.11 Channel sounding
12
2Submission Page 5 Hernandez, Li, Kojima (NICT)