Tuesday, January 29, 2013

BLUETOOH 4




http://msdn.microsoft.com/en-us/library/ms883411.aspx


Personal Area Network (PAN) Profile Registry Settings (Windows CE 5.0)

Windows CE 5.0This topic has not yet been rated - Rate this topicSend FeedbackYou can configure the PAN profile through the registry.Note   The default registry values vary depending on which Catalog items are included in your OS design. For more information, see Default Registry Settings.Global registry settings for the PAN profile are located under the HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\pan key.The following table shows the named values for the pan registry key:Value : typeDescriptionAuthenticate :REG_DWORDDetermines whether the connection is authenticated.0 - Disables authentication.1 - Enables authentication. Default.This setting is optional.Security Note   Setting this value to 0 disables authentication. This may result in potential security risks.Encrypt :REG_DWORDDetermines whether the connection is encrypted.0 - Disables encryption.1 - Enables encryption. Default.This setting is optional.Security Note   Setting this value to 0 disables encryption. This may result in potential security risks.InquiryLength : REG_DWORDSpecifies the length of the Bluetooth inquiry within the range of 1 to 255. Default value is 8.MediaDelay :REG_DWORDSpecifies the total length of time, in milliseconds, between two Bluetooth inquiries. Default value is 300000 milliseconds (5 minutes). Minimum value is 30000 milliseconds (30 seconds).Additional registry settings for configuring the PAN parameters are located under the HKEY_LOCAL_MACHINE\Comm\BTPAN1\Parms.The following table shows the named values for the Parms registry key:Value : typeDescriptionAccept Connections : REG_DWORDDetermines whether new connections are allowed for PANU and Group Ad-hoc Network (GN) roles.0 - Disables new connections. Default.1 - Enables new connections.AdapterType :REG_SZSpecifies the type of adapters. Possible string values are:PANUNAPGNConnectionTimeout : REG_DWORDSpecifies the total length of time, in milliseconds, that the device waits for a connection to complete. If the specified time elapses before connection completes, the connection is closed. The value can be set in the range of 1000 to 30000 milliseconds.Description :REG_SZSpecifies the service description to use in SDP records.FriendlyName : REG_SZSpecifies the friendly name of the service to use in Service Discovery Protocol (SDP) records.MaxConnections : REG_DWORDSpecifies the maximum number of simultaneous connections for GN and Network Access Point (NAP) roles.SDP : REG_BINARYSpecifies a BLOB that contains the SDP record for the service. If this is not provided, then the record is implicitly built.ServiceId : REG_SZSpecifies the global service identifier as a standard GUID string.You can also add the network associations for the PAN profile. The following code shows the registry values that are created for every network.[HKEY_LOCAL_MACHINE\Comm\BTPAN1\Associations\device1] "Address"=hex:00,00,00,00,00,00 "ServiceId"="{00001115-0000-1000-8000-00805f9b34fb}" "SSID"="FriendlyDevice" "Priority"=dword:1 You can configure the HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\l2cap registry key. For the Network Access Point role, configure this key to enable the Bluetooth stack to request a role-switch with the peer device.The following table shows the named values to set for the l2cap registry key.Value : typeDescriptionNoRoleSwitch: REG_DWORD0 - Enables the stack to request a role-switch with the peer device for an incoming connection.1 - Disables role switching. Default.

See Also

Bluetooth Registry Settings | Personal Area Network (PAN) | Bluetooth ProfilesSend Feedback on this topic to the authorsFeedback FAQs© 2006 Microsoft Corporation. All rights reserved.Did you find this helpful? Yes No

Bluetooth Profiles (Windows CE 5.0)

Windows CE 5.02 out of 6 rated this helpful - Rate this topicSend FeedbackA Bluetooth profile is a specification that defines the minimum requirements that the Bluetooth device must support in a specific usage scenario. These requirements define the end-user services and the features and procedures that the Bluetooth device must support to enable interoperability with peer devices.There are two types of profiles: conforming and interoperability. Conforming profiles define the core requirements for Bluetooth devices and are available by default. Interoperability profiles, which are based on the conforming profiles, define the minimum requirements for Bluetooth devices to support specific applications. Bluetooth profiles have implicit and explicit dependencies on each other.The following table shows the profiles supported by Microsoft® Windows® CE.Conforming ProfilesProfileDescriptionGeneric Access Profile (GAP)Defines the generic requirements for detecting and establishing a connection to a Bluetooth device.All other profiles are based on GAP.Generic Object Exchange Profile (GEOP)Defines procedures for the support of the Object Exchange Protocol (OBEX) usage models.Serial Port Profile (SPP)Defines procedures required for configuring serial cable connections between peer Bluetooth devices using RFCOMM.Interoperability ProfilesProfileDescriptionDial-up Networking (DUN) ProfileDepends on SPP. Defines procedures to support the use of a wireless modem by a computer for connecting to a dial-up service such as a dial-up Internet service.File Transfer Profile (FTP)Depends on GEOP. Defines procedures to support transferring data and manipulating objects on or with a peer Bluetooth device.Hands-Free Profile (HFP)Depends on SPP. Defines procedures for using a mobile device, such as a cellular phone, in conjunction with a hands-free device over a Bluetooth link, to allow the hands-free device to act as an audio input or output device for the mobile device.Headset Profile (HSP)Depends on SPP. Defines procedures to support interoperability between a headset and a mobile device, such as a cellular phone, that the headset controls through AT commands.Human Interface Device (HID) ProfileDefines procedures to support human interface devices such as keyboard and mouse.LAN Access Profile (LAP)Depends on SPP. Defines procedures to support LAN Access using Point-to-Point Protocol (PPP). PPP over RFCOMM.Object Push Profile (OPP)Depends on GEOP. Defines procedures to support the pushing or pulling of small data objects, for example calling card exchange, between Bluetooth devices.Personal Area Networking (PAN) ProfileDefines procedures to support standard IP based network services deployed over the Bluetooth transport layer. Typical usage scenarios include:Transferring data between two Bluetooth devices using a point-to-point link.Volatile membership in a group, for data sharing or gaming purposes, where users can add and remove their membership.One of the members of a piconet that provides a mobile gateway that enables other members to access the Internet or intranet.For more information about Bluetooth profiles, see this Official Bluetooth Wireless Info Web site.

See Also

Bluetooth OS Design Development | Bluetooth Protocol ArchitectureSend Feedback on this topic to the authorsFeedback FAQs




No comments:

Post a Comment