Group Ad-hoc Network (GN) (Windows Embedded CE 6.0)
1/6/2010
The Group Ad-hoc Network (GN) role enables two or more PAN User (PANU) to interact with each other through a wireless network without using additional networking hardware. The devices are connected in a piconet where the GN acts as a master and communicates either point-to-point or a point-to-multipoint with a maximum of seven PANU subordinate devices, by using the Bluetooth Network Encapsulation Protocol (BNEP).
A GN can only connect with a PANU that publishes a PANU SDP record. To connect to a PANU, the GN must perform the following tasks:
Discover the PANU by sending a baseband inquiry and conducting a Service Discovery Protocol (SDP) search.
Request a connection from the PANU if a connection does not already exist.
Note
No master/slave switch is required when a GN establishes a connection with a PANU. You can toggle the master/slave switch by configuring the registry. For more information, see Personal Area Network (PAN) Profile Registry Settings.
Create an L2CAP channel for Bluetooth Network Encapsulation Protocol (BNEP) to transmit network packets by using the BNEP control commands to initialize the BNEP connection. The commands are defined in the BNEP specification.
Transfer Ethernet packets across the link.
You can configure the PAN profile to be a GN by setting the PRJ_BTH_PAN_GN environment variable.
Alternatively, you can configure the PAN profile through registry settings. For more information, see Personal Area Network (PAN) Profile Registry Settings.
For more information about the procedures related to the GN service, see the Personal Area Networking Profile Specification at this Official Bluetooth Wireless Info Web site.
See Also
Concepts
Personal Area Networking (PAN) Profile