Hi Sascha,

Thank you for clarifying this.   I take it this is when an active scan 
is performed? so a device will use the MLME-SCAN.request primitive with 
scan type set to ACTIVE with a list of channels to scan.  This will send 
a BEACON request frame out on each channel with the destination PAN Id 
containing the broadcast short address. Coordinators that receive the 
request will send back a single beacon frame to which the receiver will 
extract the Source PAN Id from the addressing part of the MAC header 
(MHR).  The beacon MAC payload will be set to indicate a "beaconless" 
network.   From the spec - "PANs that do not wish to use the superframe 
structure (referred to as nonbeacon-enabled PANs) shall set both 
macBeaconOrder and macSuperframeOrder to 15".  Beacon Order and 
Superframe Order are both in the Superframe Specification field.

Best Regards,
Martin.




On 15/01/14 17:36, Sascha Herrmann wrote:
> Hi Martin,
>
>> After reading the 802.1.5.4 spec I was wondering if anyone knew how a
>> device discovery works in a beaconless  PAN.  The section on Device
>> Discovery in the spec states that "The PAN coordinator or a coordinator
>> indicates its presence on a PAN to other devices by transmitting beacon
>> frames.  This allows the other devices to perform device discovery".
>>   From this I'm assuming that for beaconless PAN there is no device
>> discovery and that it is achieved by statically configuring all devices
>> to use the same channels and PAN Id?  Can anyone confirm this?
> No, the term "beaconless" in this context means, that the coordinator
> isn't sending its beacons periodically but only on request. If a device
> needs to detect an active PAN, its send one or more beacon request
> frames to the channels of interest. With this configuration the
> Coordinator(s) need to listen on the channel for such an request and
> replies with a single beacon. Because of this, the coordinator can't go
> to sleep mode in this configuration.
>
> Real Device Discovery is handled by higher protocol layers, the beacon
> just tells your device, that there is an active 15.4 network. ZigBee for
> examples defines an own ZDO-Object for device discovery, which works
> with network broadcasts and should return a list of all active (and
> sleeping) network devices.
>
> Sascha.
>
>> Cheers,
>> Martin.
>>
>>
>> ------------------------------------------------------------------------------
>> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
>> Learn Why More Businesses Are Choosing CenturyLink Cloud For
>> Critical Workloads, Development Environments & Everything In Between.
>> Get a Quote or Start a Free Trial Today.
>> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Linux-zigbee-devel mailing list
>> Linux-zigbee-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/linux-zigbee-devel
>>


------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
Linux-zigbee-devel mailing list
Linux-zigbee-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-zigbee-devel

Reply via email to