1. Decentralized Clustering Resolution to CID 127
Month Year
doc.: IEEE yy/xxxxr0
March 2014
Decentralized Clustering Resolution to CID 127
Date:
Presenter:
Dejian Li
John Doe, Some Company

2. March 2014
Author List
Dejian Li

3. Fujitsu Research & Development Center /CWPAN
Author List
March 2014
Name
Company
FAN Xiaojing
Fujitsu Research & Development Center /CWPAN
WANG Hao
wangh.cn.fujitsu.com
TIAN Jun
tianjun.cn.fujitsu.com
Dejian Li

4. March 2014
Abstract
This is a submission for comment resolution on D0.01 for comment #127. This submission provides a decentralized CDMG PCP/AP clustering mechanism to improve spatial sharing and interference mitigation for the CDMG PCPs/APs based on the reference [1]. The decentralized CDMG PCP/AP clustering keeps backward compatibility with DMG devices.
Dejian Li

5. Background: Decentralized PCP/AP Clustering
Month Year
doc.: IEEE yy/xxxxr0
March 2014
Background: Decentralized PCP/AP Clustering
In 11ad, PCP/AP clustering is used to improve spatial sharing and interference mitigation with other co-channel DMG BSSs.
S-PCP/S-AP provides synchronization and other services to a PCP/AP cluster.
A member PCP/AP shall transmit its DMG Beacon frame during one of the Beacon SPs.
Clustering: cluster formation, cluster maintenance and cluster report
Dejian Li
John Doe, Some Company

6. Background: DBC Mechanism
Month Year
doc.: IEEE yy/xxxxr0
March 2014
Background: DBC Mechanism
Channelization[2]: 2.16GHz channel and 1.08GHz channel
2.16GHz channel 2 are overlapping with 1.08GHz channel 5 and 6
Dynamic Bandwidth Control (DBC) MAC[2]
Case 1: One PCP/AP starts and operates in a 1.08GHz channel, e.g., Channel 5 or Channel 6.
Case 2: Two 1.08GHz PCPs/APs operate in adjacent 1.08GHz channels: one PCP/AP providing time reference is called synchronizing PCP/AP and the other PCP/AP is called synchronized PCP/AP. 2 3 5 6 7 8
Case 1
Case 2
Dejian Li
John Doe, Some Company

7. Clustering on 1.08 GHz Channel (1/4)
Month Year
doc.: IEEE yy/xxxxr0
March 2014
Clustering on 1.08 GHz Channel (1/4)
If a CDMG PCP/AP 1 is operating on 1.08 GHz channel and supports clustering, it shall perform as an S-PCP/S-AP with transmitting CDMG Beacon frames during both NP and BTI.
To avoid interfering with DMG devices, CDMG PCP/AP 1 (S-PCP/S-AP) must transmit CDMG Beacon frames on the 2.16 GHz Channel 2 during NP.
Besides Beacon SPs, member PCP/AP 3/4 should also reserve an SP for the NP of PCP/AP 1.
If no DMG STAs exists, CDMG PCP/AP 2 can join this cluster in Channel 5 as a member PCP/AP with only transmitting CDMG Beacon frames during its BTI.
Otherwise, if there is at least one DMG STA in PCP/AP 3’s BSS, PCP/AP 3 shall retain its NP after joining the cluster.
CDMG S-PCP/S-AP 1
Member PCP/AP 2
Member PCP/AP 3
Dejian Li
John Doe, Some Company

8. Clustering on 1.08 GHz Channel (2/4)
March 2014
Clustering on 1.08 GHz Channel (2/4)
If a pair of PCP/AP 1 and PCP/AP 2 operate on 1.08GHz Channel 5 and Channel 6, respectively, they may form a cluster on each 1.08 GHz channel .
Note that the maximum number of member PCPs/APs may be different in the two clusters.
S-PCP/S-AP 1 at Channel 5
Member PCPs/APs at Channel 5
S-PCP/S-AP 2 at Channel 6
Member PCPs/APs at Channel 6
Dejian Li

9. Clustering on 1.08 GHz Channel (3/4)
March 2014
Clustering on 1.08 GHz Channel (3/4)
A CDMG PCP/AP operating in 2.16 GHz Channel 2 may join a 1.08 GHz cluster after receiving a CDMG Beacon frame transmitted by the S-PCP/S-AP operating in 1.08 GHz channel during NP.
Assumptions: PCP/AP 1 or 2 or both are clustering enabled and start their own clusters in Channels 5 and 6, respectively. PCP/AP 3 is clustering enabled but did not join any cluster.
Option: Clustering enabled PCP/AP 3 may switch to Channel 5 or 6 to join a cluster.
Cluster formation cases are sorted out and given in the annex of this submission.
Dejian Li

10. Clustering on 1.08 GHz Channel (4/4)
Month Year
doc.: IEEE yy/xxxxr0
March 2014
Clustering on 1.08 GHz Channel (4/4)
Consider the legacy DMG STA existed in the BSS
If there exists at least one DMG STA in the BSS of a 1.08GHz CDMG PCP/AP, NP1 and NP2 should be retained to keep backward compatibility with the DMG STA when joining.
Suppose PCP/AP 1 of the synchronization pair 1.08GHz PCPs/APs intends to join the co-channel cluster, the rules for setting the BI durations in 1.08 GHz channel and 1.08 GHz channel are:
BI 1 of PCP/AP 1 in Channel 5 should be set to BI of the S-PCP/S-AP of the target cluster
BI in Channel 3 should be set to integer times of both BI 1 in Channel 5 and BI 2 in Channel 6
Dejian Li
John Doe, Some Company

11. Joining the 2.16 GHz cluster for a 1.08 GHz PCP/AP
March 2014
Joining the 2.16 GHz cluster for a 1.08 GHz PCP/AP
Except of joining a co-channel 1.08 GHz cluster, a 1.08 GHz CDMG PCP/AP also can join a channel-overlapped 2.16GHz cluster.
Its BSS can still operate on the 1.08GHz or switch to operate on the 2.16GHz.
Dejian Li

12. Problem of joining 2.16GHz cluster for 1.08GHz PCP/AP
March 2014
Problem of joining 2.16GHz cluster for 1.08GHz PCP/AP
Difficulties of joining or merging with a 2.16 GHz cluster for a 1.08 GHz CDMG PCP/AP:
The 1.08 GHz CDMG PCP/AP may not be able to receive 2.16GHz DMG/CDMG Beacon frames during its NP through passively listening.
It is not feasible to monitor the 2.16 GHz channel for a long time (up to aMinChannelTime) consecutively for a 1.08GHz CDMG PCP/AP.
Dejian Li

13. Active cluster probe in cluster formation (1/4)
Month Year
doc.: IEEE yy/xxxxr0
March 2014
Active cluster probe in cluster formation (1/4)
Proposed active cluster probe scheme for efficient cluster discovery:
A 1.08 GHz PCP/AP that is suffering interference can transmit DMG Beacon/Probe Request frame including Cluster Probe IE on the 2.16 GHz channel in NP/DTI.
The Cluster Probe IE comprises timing information for when the feedback is transmitted.
The 1.08GHz PCP/AP can reserve a few randomly time located SPs in DTI to transmit the Cluster Probe IE.
If Probe Request frame is used for cluster probe, the transmit frequency should be limited.
2.16 GHz S-PCP/S-AP responds with a Probe Response frame including Extended Cluster Report element according to the timing requirement in Cluster Probe element.
Dejian Li
John Doe, Some Company

14. Active cluster probe in cluster formation (2/4)
March 2014
Active cluster probe in cluster formation (2/4)
Joining an existed 2.16GHz cluster for both the synchronization pair PCPs/APs
If PCP/AP 1 detects the presence of a 2.16GHz PCP/AP cluster and meet the requirement of joining the cluster, it should transmit a Cluster Switch Announcement IE to its peer PCP/AP 2 during NP1 prior to joining the cluster.
Cluster Switch Announcement IE
Used to motivate and assist the peer 1.08GHz PCP/AP to join the 2.16GHz cluster
Coordinate the joining sequence of the synchronization pair PCPs/APs
After one of the synchronization pair PCPs/APs transmits the Cluster Switch Announcement IE in its NP, it should cease Beacon transmission during NP.
Dejian Li

15. Active cluster probe in cluster formation (3/4)
March 2014
Active cluster probe in cluster formation (3/4)
Request Token: set to a nonzero value chosen by the requester AP
SP Offset, SP Space, SP Duration, Repetition Count: together to define a number of SPs for transmitting and receiving Probe Response frame including the Extended Cluster Report IE.
Request token: copied from request token field in Cluster Probe element
Next BTI Offset: indicate the start time of the next DMG Beacon
Reported Clustering Control: Control information of the 2.16GHz cluster
Element ID
Length
Request Token
SP Offset
SP Space
SP Duration
Repetition Count
Octets 1 2 4
Cluster Probe element format
Element ID
Length
Request Token
Next BTI Offset
Clustering Control Report
Octets 1 2 4 8
Extended Cluster Report element format
Dejian Li

16. Active cluster probe in cluster formation(4/4)
Month Year
doc.: IEEE yy/xxxxr0
March 2014
Active cluster probe in cluster formation(4/4)
Compatibility problem in active cluster probe
11ad devices can not identify the new Cluster Probe element, thus compatibility needs to be considered during cluster formation or cluster merge.
Resolution for compatibility problem:
If the number of transmitted Cluster Probe IE reaches the upper limitation but the 1.08GHz PCP/AP did not receive any response, then the PCP/AP may request an STA in its BSS to monitor the 2.16GHz channel, similar to DFS of
The STA monitoring the 2.16GHz channel can use cluster report mechanism to report the received cluster information.
The 1.08GHz PCP/AP can reserve SPs to monitor the 2.16GHz channel during each Beacon SP in using the cluster information in the cluster report.
Dejian Li
John Doe, Some Company

17. Cluster Merging in Cluster Maintenance
March 2014
Cluster Merging in Cluster Maintenance
Cluster merging occurs when an S-PCP/S-AP detects the presence of another S-PCP/S-AP through receiving a CDMG Beacon.
To make a decision of whether to join the neighboring cluster, S-PCP/S-AP 1 should compare the value of each subfield in Dynamic Bandwidth Control field included in CDMG Beacon with that of S-PCP/S-AP 2.
The priority is given by the following order: 1) Channel Splitting; 2) Adjacent Chanel Occupancy; 3) Clustering Enabled; 4) Synchronizing PCP/AP MAC Address.
Dynamic Bandwidth Control field format
Dejian Li

18. CDMG Cluster Merging Method
March 2014
Is the DBC Present field set to 0 at S-PCPs/S-APs 1 or 2? Y
CDMG Cluster Merging Method
If the S-PCP/S-AP is a legacy device, e.g., DMG device, or a CDMG device working at the legacy mode, the DBC Present field shall be set to 0. Otherwise, this field is set to 1.
If either of two S-PCPs/S-APs is a legacy device, cluster merging occurs only in a 2.16GHz channel and the cluster merging is the same with the method in IEEE ad [1].
If both S-PCPs/APs are CDMG devices, one S-PCP/S-AP should become a member PCP/AP of the other S-PCP/S-AP’s cluster by comparing the value of each subfield in Dynamic Bandwidth Control field with the fact that the value of the other S-PCP/S-AP is lower than that of this S-PCP/S-AP. N
Compare the Channel Splitting field of S-PCP/S-AP 1 with that of S-PCP/S-AP 2
Lower
Larger
Equal
Compare the Adjacent Channel Occupancy field of S-PCP/S-AP 1 with that of S-PCP/S-AP 2
Lower
Larger
Is the MAC address of S-PCP/S-AP 1 lower than that of S-PCP/S-AP 2? N
Equal
Compare the Clustering Enabled field of S-PCP/S-AP 1 with that of S-PCP/S-AP 2
Lower
Larger Y
Equal
Compare the Synchronizing PCP/AP MAC Address of S-PCP/S-AP 1 with that of S-PCP/S-AP 2?
Lower
Larger
S-PCP/S-AP 1 become a member PCP/AP of S-PCP/S-AP 2’s cluster
End
Dejian Li

19. A Case of Cluster Merging
March 2014
Scenario: PCP/AP 1 starts a cluster in Channel 2, while a pair of PCPs/APs 2 and 3 start their own cluster in Channel 5 and Channel 6, respectively.
Note that the Channel Splitting subfield in Dynamic Bandwidth Control field is set to 0 at S-PCP/S-AP 1 and 1 at S-PCPs/S-APs 2 and 3.
Cluster Merging: By comparing with the Channel Splitting subfield through transmitting Cluster Probe IE and receiving the Extended Cluster Report IE from S-PCP/S-AP 1 [2], S-PCP/S-AP 2 or 3 or both should become a member PCP/AP of S-PCP/S-AP 1.
Channel 5
S-PCP/S-AP 2
Channel 2
S-PCP/S-AP 1
Channel 6
S-PCP/S-AP 3
Channel 2
Member PCP/AP 3
Member PCP/AP 2
S-PCP/S-AP 1
More cluster merging cases are given in the annex of this submission.
Dejian Li

20. Announcing the Cluster Merging State
Month Year
doc.: IEEE yy/xxxxr0
March 2014
Announcing the Cluster Merging State
Problem in cluster merging
It is hard to implement cluster merging for the 1.08 GHz member PCPs/APs, since the 1.08 GHz member PCPs/APs might not find the 2.16 GHz cluster yet.
Resolution
If a PCP/AP discovers a cluster in another channel and intends to join it, it should transmit Cluster Switch Announcement IE to its original cluster prior to switching cluster.
The cluster members should attempt to receive the CDMG Beacon of the target S-PCP/S- AP using the cluster information contained in the Cluster Switch Announcement IE.
If a cluster member receives the CDMG Beacon of S-PCP/S-AP of the new cluster, it should start to perform the cluster formation steps to join it; otherwise, it should complete the cluster maintenance steps according to ad.
Element ID
Length
New Channel Number
Reference Timestamp
Reported Clustering Control
Octets 1 4 8
Cluster Switch Announcement IE format
Dejian Li
John Doe, Some Company

21. Cluster Merging for 1.08 and 2.16 GHz Cluster
March 2014
Cluster Merging for 1.08 and 2.16 GHz Cluster
In some cases, clusters on 2.16 GHz and 1.08 GHz channels need to be coexistent
If a 1.08GHz cluster should be merged into a 2.16GHz cluster, some 1.08 GHz PCPs/APs (e.g. PCP/AP 5~7) may not be able to receive the S-PCP/S-AP’s CDMG Beacon on 2.16 GHz channel because they are too far away from the 2.16 GHz S-PCP/S-AP.
Problem of cluster merging
The 1.08GHz member PCPs/APs which fail to join the 2.16GHz cluster might interfere with the 2.16GHz cluster.
Dejian Li

22. Cluster Coordination after Cluster Merging
Month Year
doc.: IEEE yy/xxxxr0
March 2014
Cluster Coordination after Cluster Merging
If some member PCPs/APs can not join the 2.16 GHz cluster, coordination should be performed between the coexistent 1.08 GHz & 2.16 GHz clusters.
The function of a 1.08 GHz S-PCP/S-AP that performs as a coordinator
Join the 2.16 GHz cluster as member PCP/AP, and transmit CDMG Beacon during one Beacon SP
Remain in 1.08 GHz channel as S-PCP/S-AP at time other than 2.16 GHz Beacon SPs
Broadcast non-idle 2.16 GHz Beacon SP information (as data SP allocation) on 1.08 GHz channel
Broadcast1.08GHz synchronization Beacon SP information (as data SP ) on 2.16 GHz channel
Member PCP/AP and STA in a 1.08 GHz cluster switch to 2.16 GHz channel before non-idle 2.16 GHz Beacon SPs and receive Beacon frames
Collect information about data SP/CBAP schedules
PCP/AP1 is S-PCP/S-AP of
PCP/AP2 is S-PCP/S-AP of
PCP/AP3 is member of
S-PCP/S-AP play as Coordinator
Member
Dejian Li
John Doe, Some Company

23. Avoid interference between coexistent 1.08GHz & 2.16GHz clusters
March 2014
Avoid interference between coexistent 1.08GHz & 2.16GHz clusters
Benefiting from information exchanged by the coordinator, interference between 2.16 GHz & 1.08 GHz clusters could be avoided.
PCPs/APs and STAs of 1.08 GHz cluster get information about 2.16 GHz Beacon SP and SP/CBAP information
Actively avoid interfering with beacon transmission on 2.16 GHz channel
Actively avoid interfering with scheduled data transmission
Support cluster report and re-schedule on 1.08 GHz channel
PCPs/APs of 2.16 GHz cluster get information about 1.08 GHz Beacon SP information
Actively avoid interfering with synchronization Beacon transmission on 1.08 GHz channel
Dejian Li

24. Month Year
doc.: IEEE yy/xxxxr0
March 2014
Cluster Report
Show the cluster channel number by using the 2 reserved bits in cluster report element
If a 1.08GHz non-PCP/non-AP STA receives a DMG beacon of a 2.16GHz cluster, it shall transmit a Cluster Report IE including a Cluster Channel Number field to its PCP/AP to report the interference information.
Cluster Channel Number:
set to 01 if the reported cluster is in the low frequency 1.08GHz channel.
set to 10 if the reported cluster is in the high frequency 1.08GHz channel.
set to 11 if the reported cluster is in the 2.16GHz channel.
Cluster Request
Cluster Report
Schedule Present
TSCONST
Present
ECPAC Policy Enforced
ECPAC Policy Present
Cluster Channel
Number
Bits 1 2
Cluster Report Control field
Dejian Li
John Doe, Some Company

25. March 2014
Conclusion
This submission provides decentralized CDMG PCP/AP clustering solution for comment #127 on the comment resolution for D0.01.
Cluster formation
CDMG PCP/AP cluster can be formed on 1.08GHz channel.
An active probe method to discover the 2.16GHz cluster for 1.08GHz PCP/AP.
Rules of adjusting BI and SBBI for 1.08GHz PCP/AP that is joining a cluster.
Cluster maintenance
The PCP/AP that is switching cluster should announce its cluster switching state to other members.
Cluster merging between two S-PCPs/S-APs should compare the Dynamic Bandwidth Control field
Cluster coordination: Exchange scheduling information between overlapped 2.16GHz and 1.08GHz clusters through the 1.08GHz S-PCP/S-AP that is a coordinator of the two clusters.
Cluster report
The cluster channel number is indicated by modifying Cluster Report IE.
Main modifications to 11ad:
4 new elements/fields are defined: Cluster Probe element, Extended Cluster Report element, Cluster Switch Announcement element, Dynamic Bandwidth Control field
1 element is modified: Cluster Report element
Dejian Li

26. Annex Cluster formation cases Cluster merging cases March 2014
Dejian Li

27. Cluster formation － Case 1
March 2014
Cluster formation － Case 1
Scenario: Both PCPs/APs 1 and 2 establish their own networks in Channel 2, respectively.
Assumptions: PCP/AP 1 is clustering enabled and starts a cluster in Channel 2.
Options: When PCP/AP 2 detects the presence of S-PCP/S-AP 1 and becomes into clustering enabled, it shall become a member PCP/AP of this cluster. This is same to the existing IEEE ad clustering mechanism [1].
Two PCPs/APs operate in the same 2.16GHz channel.
Dejian Li

28. Cluster formation － Case 2
March 2014
Scenario: PCP/AP 1 establishes its network in Channel 2, while PCP/AP 2 establishes its network in channel 5 and the adjacent Channel 6 is unoccupied.
Assumptions: PCP/AP 1 is clustering enabled and starts a cluster in Channel 2.
Options: Clustering enabled PCP/AP 2 may switch to Channel 2 to become a member PCP/AP through transmitting Cluster Probe element (IE) and receiving the Extended Cluster Report IE from S-PCP/S-AP 1.
One PCP/AP operates in a 2.16GHz channel and the other one operates in one of 1.08GHz channels within this large land but its adjacent 1.08GHz is unoccupied.
Dejian Li

29. Cluster formation － Case 3
March 2014
Scenario: PCP/AP 1 establishes its network in Channel 2, while a pair of PCPs/APs 2 and 3 establish their own networks in Channels 5 and 6, respectively.
Assumptions: PCP/AP 1 is clustering enabled and starts a cluster in Channel 2.
Options: Clustering enabled PCP/AP 2 or 3 or both may become a member PCP/AP by Cluster Probe element (IE) and Extended Cluster Report IE [2].
One PCP/AP operates in a 2.16GHz channel and another pair of PCPs/APs operate in two 1.08GHz channels of the same 2.16GHz channel, respectively.
Dejian Li

30. Cluster formation － Case 4
March 2014
Scenario: PCP/AP 1 establishes its network in channel 5 and the adjacent Channel 6 is unoccupied, while PCP/AP 2 establishes its network in Channel 2.
Assumptions: PCP/AP 1 is clustering enabled and starts a cluster in Channel 5.
Options:
Clustering enabled PCP/AP 2 may become a member PCP/AP .
PCP/AP 2 may switch to Channel 6 to continue its BSS/PBSS under DBC MAC protocol.
One PCP/AP operates in one of 1.08GHz channels within a large land but its adjacent 1.08GHz is unoccupied as well as the other one operates in the same 2.16GHz channel.
Dejian Li

31. Cluster formation － Case 5
March 2014
Scenario: PCP/AP 1 establishes a network in Channel 5 and its adjacent Channel 6 is unoccupied. Similarly, another PCP/AP 2 also establishes a network in Channel 5 and its adjacent Channel 6 is unoccupied.
Assumptions: PCP/AP 1 is clustering enabled and starts a cluster in Channel 5.
Options:
Clustering enabled PCP/AP 2 may choose to become a member PCP/AP.
PCP/AP 2 may switch to Channel 6 to continue its BSS/PBSS under DBC MAC protocol.
One PCP/AP operates in a 1.08GHz channel and its adjacent 1.08GHz channel is unoccupied as well as another PCP/AP operates in the same 1.08GHz and its adjacent 1.08GHz is unoccupied.
Dejian Li

32. Cluster formation － Case 6
March 2014
Scenario: PCP/AP 1 establishes a network in Channel 5 and its adjacent Channel 6 is unoccupied. At the same time, a pair of PCPs/APs 2 and 3 establish their own networks in Channels 5 and 6, respectively.
Assumptions: PCP/AP 1 is clustering enabled and starts a cluster in Channel 5.
Option: Clustering enabled PCP/AP 2 may choose to become a member PCP/AP.
One PCP/AP operates in a 1.08GHz channel and its adjacent 1.08GHz is unoccupied as well as another pair of PCPs/APs operates in two 1.08GHz channel of the same 2.16GHz channel, respectively.
Dejian Li

33. Cluster formation － Case 7
March 2014
Scenario: A pair of PCPs/APs 1 and 2 establish their own networks in Channels 5 and 6, respectively, while another PCP/AP 3 establishes its networks in Channel 2.
Assumptions: PCP/AP 1 or 2 or both are clustering enabled and start their own clusters in Channels 5 and 6, respectively.
Option: Clustering enabled PCP/AP 3 may switch to Channel 5 or 6 to become a member PCP/AP .
One PCP/AP operates in a 2.16GHz channel and another pair of PCPs/APs operates in two 1.08GHz channels of the same 2.16GHz channel, respectively.
Dejian Li

34. Cluster formation － Case 8
March 2014
Scenario: A pair of PCPs/APs 1 and 2 establish their own networks in Channels 5 and 6, respectively. At the same time, PCP/AP 1 establishes a network in Channel 5 and its adjacent Channel 6 is unoccupied.
Assumptions: PCP/AP 1 is clustering enabled and starts a cluster, regardless of whether PCP/AP 2 is clustering enabled or not.
Option: Clustering enabled PCP/AP 3 may choose to become a member PCP/AP.
A pair of PCPs/APs operates in two 1.08GHz channels of the same 2.16GHz channel, respectively, as well as another PCP/AP operates in one 1.08GHz and its adjacent 1.08GHz is unoccupied.
Dejian Li

35. Cluster formation － Case 9 (1/3)
March 2014
Scenario: A pair of PCPs/APs 1 and 2 establish their own networks in Channels 5 and 6, respectively. At the same time, another pair of PCPs/APs 3 and 4 also establish their own networks in Channels 5 and 6, respectively.
Assumptions: Both PCPs/APs 1 and 2 are clustering enabled and start their own clusters in Channels 5 and 6, respectively.
Option: A pair of clustering enabled PCP/AP 3 and 4 choose to become member PCPs/APs in Channels 5 and 6, respectively.
(a)
A pair of PCPs/APs operates in two 1.08GHz channels of a 2.16GHz channel, respectively, as well as another pair of PCPs/APs also operates in these two 1.08GHz channels, respectively.
Dejian Li

36. Cluster formation － Case 9 (2/3)
March 2014
Cluster formation － Case 9 (2/3)
Assumption 2: PCPs/APs 1 and 4 are clustering enabled and start their own clusters in Channels 5 and 6, respectively.
Option: In each channel, clustering enabled PCP/AP 3 or 2 chooses to become a member PCP/AP.
(b)
A pair of PCPs/APs operates in two 1.08GHz channels of a 2.16GHz channel, respectively, as well as another pair of PCPs/APs also operates in these two 1.08GHz channels, respectively.
Dejian Li

37. Cluster formation － Case 9 (3/3)
March 2014
Assumption 3: PCP/AP 1 is clustering enabled and starts its cluster in Channel 5, while PCP/AP 2 in Channel 6 is clustering disabled.
Option: Only clustering enabled PCP/AP 3 chooses to become a member PCP/AP.
(c)
A pair of PCPs/APs operates in two 1.08GHz channels of a 2.16GHz channel, respectively, as well as another pair of PCPs/APs also operates in these two 1.08GHz channels, respectively.
Dejian Li

38. Cluster Merging－ Case 1 March 2014
Scenario: Both PCPs/APs 1 and 2 start their own clusters by becoming S-PCPs/S-APs 1 and 2 in Channel 2.
Note that the Channel Splitting subfield, the Adjacent Channel Occupancy subfield and the Clustering Enabled subfield are both set to the same value of 1000 at S-PCPs/S-APs 1 and 2.
Assumptions: Suppose that S-PCP/S-AP 2 receives a DMG Beacon frame from S-PCP/S-AP 1 within Channel 2 and its MAC address is higher than that of S-PCP/S-AP 1.
Cluster Merging: By comparing with the Synchronizing PCP/AP MAC Address subfield, S-PCP/S-AP 2 should become a member PCP/AP of S-PCP/S-AP 1.
Channel 2
S-PCP/S-AP 1
S-PCP/S-AP 2
Channel 2
Member PCP/AP 2
S-PCP/S-AP 1
Dejian Li

39. Cluster Merging－ Case 2 March 2014
Scenario: PCP/AP 1 starts a cluster in Channel 2, while PCP/AP 2 starts a cluster in Channel 5 and its adjacent Channel 6 is unoccupied.
Note that the Channel Splitting subfield in Dynamic Bandwidth Control field is set to 0 at S-PCP/S-AP 1 and 1 at S-PCP/S-AP 2.
Cluster Merging: By comparing with the Channel Splitting subfield through transmitting Cluster Probe IE and receiving the Extended Cluster Report IE from S-PCP/S-AP 1 [2], S-PCP/S-AP 2 should become a member PCP/AP of S-PCP/S- AP 1.
Channel 5
S-PCP/S-AP 2
Channel 2
S-PCP/S-AP 1
Channel 2
Member PCP/AP 2
S-PCP/S-AP 1
Dejian Li

40. Cluster Merging － Case 3 March 2014
Scenario: PCP/AP 1 starts a cluster in Channel 2, while a pair of PCPs/APs 2 and 3 start their own cluster in Channel 5 and Channel 6, respectively.
Note that the Channel Splitting subfield in Dynamic Bandwidth Control field is set to 0 at S-PCP/S-AP 1 and 1 at S-PCPs/S-APs 2 and 3.
Cluster Merging: By comparing with the Channel Splitting subfield through transmitting Cluster Probe IE and receiving the Extended Cluster Report IE from S-PCP/S-AP 1 [2], S-PCP/S-AP 2 or 3 or both should become a member PCP/AP of S-PCP/S-AP 1.
Channel 5
S-PCP/S-AP 2
Channel 2
S-PCP/S-AP 1
Channel 6
S-PCP/S-AP 3
Channel 2
Member PCP/AP 3
Member PCP/AP 2
S-PCP/S-AP 1
Dejian Li

41. Cluster Merging － Case 4 March 2014
Scenario: PCP/AP 1 starts a cluster in Channel 5, and its adjacent Channel 6 is unoccupied. At the same time, another PCP/AP 2 also starts a cluster in Channel 5 and its adjacent Channel 6 is unoccupied.
Note that the Channel Splitting subfield, the Adjacent Channel Occupancy subfield and the Clustering Enabled subfield are set to the same value of 0101 at S-PCPs/S-APs 1 and 2 .
Assumptions: Suppose that S-PCP/S-AP 2 receives a DMG Beacon frame from S-PCP/S-AP 1 within Channel 5 and that its MAC address is higher than that of S-PCP/S-AP 1.
Cluster Merging:
By comparing with the Synchronizing PCP/AP MAC Address field, S-PCP/S-AP 2 should become a member PCP/AP of S-PCP/S-AP 1.
S-PCP/S-AP 2 may switch to Channel 6 to start a new cluster .
Channel 5
S-PCP/S-AP 1
S-PCP/S-AP 2
Channel 6
Channel 5
Member PCP/AP 2
S-PCP/S-AP 1
S-PCP/S-AP 1
Channel 6
S-PCP/S-AP 2
(a) Option 1
(b) Option 2
Dejian Li

42. Cluster Merging － Case 5 March 2014
Scenario: PCP/AP 1 starts a cluster in Channel 5, and its adjacent Channel 6 is unoccupied. At the same time, another PCP/AP 2 also starts a cluster in Channel 5 and its adjacent Channel 6 is occupied by a PCP/AP or an S-PCP/S-AP.
The Channel Splitting subfield is set to the same value of 0 at S-PCPs/S-APs 1 and 2 . However, the Adjacent Channel Occupancy subfield is set to 1 at S-PCP/S-AP 1 and 0 at S-PCP/S-AP 2.
Assumption: Suppose that S-PCP/S-AP 1 receives a DMG Beacon frame from S-PCP/S-AP 2.
Cluster Merging: By comparing with the Adjacent Channel Occupancy field, S-PCP/S-AP 1 should become a member PCP/AP of S-PCP/S-AP 1.
S-PCP/S-AP 2
Channel 5
S-PCP/S-AP 1
PCP/AP 3
Channel 6
Channel 5
S-PCP/S-AP 2
Member PCP/AP 1
PCP/AP 3
Channel 6
Dejian Li

43. Cluster Merging － Case 6 March 2014
Scenario: PCP/AP 1 starts a cluster in Channel 5, and its adjacent Channel 6 is occupied by a clustering disabled PCP/AP 2. At the same time, another PCP/AP 3 also starts a cluster in Channel 5 and its adjacent Channel 6 is also occupied by a clustering disabled PCP/AP 4.
Note that the Channel Splitting subfield, the Adjacent Channel Occupancy subfield and the Clustering Enabled subfield are set to the same value of 0001 at S-PCPs/APs 1 and 3.
Assumptions: Suppose that S-PCP/S-AP 3 receives a DMG Beacon frame from S-PCP/S-AP 1and that its Synchronizing PCP/AP MAC address is higher than that of S-PCP/S-AP 1.
Cluster Merging: By comparing with the Synchronizing PCP/AP MAC address field, S- PCP/S-AP 3 should become a member PCP/AP of S-PCP/S-AP 1.
S-PCP/S-AP 1
S-PCP/S-AP 3
Channel 5
PCP/AP 2
PCP/AP 4
Channel 6
Member PCP/AP 3
S-PCP/S-AP 1
Channel 5
PCP/AP 4
PCP/AP 2
Channel 6
Dejian Li

44. Cluster Merging － Case 7 March 2014
Scenario: A pair of PCPs/APs 1 and 2 starts their own clusters in Channels 5 and 6, respectively. At the same time, another PCP/AP 3 starts a cluster in Channel 5 and its adjacent Channel 6 is occupied by a clustering disabled PCP/AP 4.
The Channel Splitting subfield, the Adjacent Channel Occupancy subfield are set to the same value of 00. However, the Clustering Enabled subfield is set to 00 at S-PCP/AP 1 and 01 at S-PCP/AP 3.
Assumption: Suppose that S-PCP/S-AP 3 receives a DMG Beacon frame from S-PCP/S-AP 1.
Cluster Merging: Comparing with the Synchronizing PCP/AP MAC address field, S-PCP/S- AP 3 should become a member PCP/AP of S-PCP/S-AP 1.
S-PCP/S-AP 1
S-PCP/S-AP 3
Channel 5
S-PCP/S-AP 2
PCP/AP 4
Channel 6
Member PCP/AP 3
S-PCP/S-AP 1
Channel 5
PCP/AP 4
S-PCP/S-AP 2
Channel 6
Dejian Li

45. Cluster Merging － Case 8 March 2014
Scenario: A pair of PCPs/APs 1 and 2 starts their own clusters in Channels 5 and 6, respectively. At the same time, another pair of PCPs/APs 3 and 4 also starts their own clusters in Channels 5 and 6, respectively.
Note that the Channel Splitting subfield, the Adjacent Channel Occupancy subfield and the Clustering Enabled subfield are set to the same value of 0000 at S-PCPs/APs 1, 2, 3 and 4.
Assumption: Suppose that S-PCP/S-AP 3 and 4 receive a DMG Beacon frame from S-PCP/S-AP 1 and 2, respectively, and that their Synchronizing PCP/AP MAC address is higher than that of the other pair.
Cluster Merging: Comparing with the Synchronizing PCP/AP MAC address field, S- PCPs/S-APs 3 and 4 should become a member PCP/AP of S-PCPs/S-APs 1 and 2, respectively.
S-PCP/S-AP 1
S-PCP/S-AP 3
Channel 5
S-PCP/S-AP 2
S-PCP/S-AP 4
Channel 6
Member PCP/AP 3
S-PCP/S-AP 1
Channel 5
Member PCP/AP 4
S-PCP/S-AP 2
Channel 6
Dejian Li

46. March 2014
Reference
[1] Decentralized Clustering Mechanism for aj (60GHz NT)
[2] Dynamic Bandwidth Control for aj (60GHz NT)
[3] In the IEEE P802.11ad TM Standard “Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications – Amendment 3: Enhancements for Very High Throughput in the 60 GHz band,” December 2012.
Dejian Li