Channel time allocation period Channel time allocation period 802.15.5 MAC enhancement approaches Lets clarify this structure – is this more accurate? Non-BP approach BP approach IEEE 802.15.3 IEEE 802.15.3 B CAP Channel time allocation period B CAP Channel time allocation period … … PCTA 1 PCTA 2 CTA n-1 CTA n PCTA 1 PCTA 2 CTA n-1 CTA n B CAP CFP B CAP CFP B CAP CFP B CAP CFP Dev 1 Dev 2 Mesh 1 Mesh 2 Mesh 3 Superframe view Superframe view Compatible with 15.3 devices Incompatible with 15.3 devices * Quoted from Michael Sim, "IEEE 802.15 TG5 Teleconference #2"

Define some more terms MESH Superframe Size Superframe SAP offset Shared access period ( SAP ) The SAP can be a CTA assigned to all mesh devices Mesh devices may access channel during their own CAPs / CTAs, as well as the common SAP The SAP may be further divided into a CAP and multiple CTAs Mesh devices may negotiate the usage of the SAP by using their beacons Mesh devices may record the differences (SAP offsets) between their own beacon staring times and the SAP starting time, in order to locate the SAP

Comment/Question Routing (source, destination, etc.) is best handled in the Data and not the beacon since there may be multiple data streams per mesh device.

General comments What was decided about the ability to use 15.3 MCTAs to simulate a BP? What were the issues?