Differences

This shows you the differences between two versions of the page.

--- wiki:introduction_to_bluetooth_profiles [2017/10/22 15:50]
1.241.172.144
+++ wiki:introduction_to_bluetooth_profiles [2017/10/22 15:54] (current)
1.241.172.144
@@ Line 38: / Line 38: @@
 \\
 The Generic Access profile, as the basic piconet enabler, uses features of the RFCOMM, L2CAP, Link Manager and Link Controller layers of the Bluetooth stack. As an application developer you do not need to concern yourself with the details of the protocols as this is handled internally. The APIs will handle all of the connection, linking and role negotiation for you. Note however that there are no explicit GAP APIs.
-\\
 **SPP**
-\\
 The Serial Port Profile gives Bluetooth devices RS-232 emulation capabilities, allowing applications that were written with cable connection in mind to make the transition to Bluetooth. The application establishes a link over the Bluetooth connection without being aware of Bluetooth. The SPP simply emulates a typical RS-232 serial cable communications session. The SPP enables multiplexing and provides support for two device types: communication endpoint devices and intermediate devices. SPP operates on the RFCOMM and L2CAP layers of the Bluetooth stack.
 \\
@@ Line 56: / Line 56: @@
 \\
 Links to examples, guides, and tutorials that use the SPP will be provided here as they become available.
-\\
 **GOEP**
-\\
 The Generic Object Exchange Profile provides the functionality needed to use the Object Exchange (OBEX) Protocol over Bluetooth. GOEP is used by the following profiles:
 \\
@@ Line 67: / Line 67: @@
 \\
 GOEP makes a significant contribution to the overall offering by providing client and server roles to the devices of the Bluetooth Piconet. Applications using GOEP can push and pull objects from other devices in the piconet.
-\\
-**[[wiki:pan|PAN Profile]]**
+**[[wiki:pan|PAN]]**
-\\
 The Personal Area Networking profile provides a simplification to the LAN Access and Dial-up Networking profiles (both now deprecated), by reducing the number of layers in a network connection. PAN enhances networking over Bluetooth by providing new functionality such as the Group Ad-hoc Networking role, discussed below.
 \\
@@ Line 78: / Line 77: @@
 \\
 PAN is integrated into the networking framework as a plugin. See the Networking documentation for more information about networking with the Bluetooth PAN profile plugin. Therefore applications can treat a Bluetooth PAN as any other networking technology.
-\\
 **AVRCP**
-\\
 The Audio video remote control profile implements certain aspects of the AV/C Digital Interface Command Set (IEEE 1394) for use over a Bluetooth connection. This profile defines two possible roles: controller (CT) and target (TG). The controller device sends commands to the target who acts on those commands.
 \\
@@ Line 88: / Line 86: @@
 Features of the profile implemented in the Symbian OS Bluetooth subsystem are presented in the following table according to defined role.
 \\
-CT	TG
+|CT|TG|
-All Mandatory features.
+|All Mandatory features.|All Mandatory features.|
+|Sending UNIT info command.|Initiating connection for control.|
-All Mandatory features.
+|Sending subunit info command.|Receiving pass through commands.|
+|Sending pass through commands.|Sending all operation_ids.|
-Sending UNIT info command.
+|Sending all operation_ids.|Receiving all operation_ids.|
+|Receiving all operation_ids.||
-Initiating connection for control.
+\\
-Sending subunit info command.
-Receiving pass through commands.
-Sending pass through commands.
-Sending all operation_ids.
-Sending all operation_ids.
-Receiving all operation_ids.
-Receiving all operation_ids.
 AVRCP operates over a GAP connection, communicating via the Audio Video Control Transport Protocol (AVCTP) on a channel in the L2CAP layer. Application developers will use the Remote Control Framework for creating apps that use the AVRCP.
-GAVDP
+**GAVDP**
 The Generic audio video distribution profile provides the mechanism for distributing audio and video content over a Bluetooth connection. There are two roles defined for GAVDP, they are: Initiator (INT) and Acceptor (ACP). INT begins a signalling procedure and ACP responds. The roles are not linked to the master / slave relationship between devices and can switch when a new procedure is initiated.
+\\
 GAVDP has been implemented in the Symbian OS Bluetooth subsystem specifically to support the Bluetooth stereo headset usecase. The Audio Video Distribution Transport Protocol (AVDTP) manages the transmission of audio packets over an L2CAP channel. The GAVDP component of the Bluetooth subsystem provides an API to configure, send and receive data over the AVDTP within an ESock plugin.
+\\
-[Top]
-Supported Bluetooth Profiles
+===Supported Bluetooth Profiles===
 The following list indicates profiles for which the Symbian OS subsystem has provided the necessary framework should a licensee have a need to implement them. Application developers should refer to the documentation for the platform(s) they are targeting to determine which additional profiles (if any) are available for a particular device.
+\\
 The Bluetooth profile implementers guide, available soon, describes how licensees can enable profiles on their devices.
+\\
+*Advanced Audio Distribution Profile
+ Linked to MMF.
+*Video Distribution Profile
+ Linked to MMF.
+*Object Push Profile
+ Linked to Messaging APIs.
+*File Transfer Profile
+*Synchronization Profile
+*Fax Profile
+*Dial Up Networking (DUN) Profile
+*Headset Profile
+*Hands Free Profile
+ Use the Remote Control Framework.
+*HID Profile
+*Device ID Profile
+*Basic Printing Profile
+*Basic Imaging Profile
+*Service Discovery Application Profile
+*Unrestricted Digital Information Profile
-Advanced Audio Distribution Profile
-Linked to MMF.
+===Omitted Bluetooth profiles===
-Video Distribution Profile
-Linked to MMF.
-Object Push Profile
-Linked to Messaging APIs.
-File Transfer Profile
-Synchronization Profile
-Fax Profile
-Dial Up Networking (DUN) Profile
-Headset Profile
-Hands Free Profile
-Use the Remote Control Framework.
-HID Profile
-Device ID Profile
-Basic Printing Profile
-Basic Imaging Profile
-Service Discovery Application Profile
-Unrestricted Digital Information Profile
-[Top]
-Omitted Bluetooth profiles
 The following profiles are explicitly omitted from the Current Symbian OS Bluetooth subsystem:
+\\
-Cordless Telephony Profile
+*Cordless Telephony Profile
+*Intercom Profile
-Intercom Profile
+*SIM Access Profile
-SIM Access Profile

DokuWiki

Site Tools

Differences

Page Tools