diff options
authorBruna Moreira <>2012-02-28 08:56:04 -0400
committerClaudio Takahasi <>2012-02-28 13:38:19 -0300
commit71756741fe8ee346e9dc1b3e560d2da62cc9ef65 (patch)
parent136cfc7bee1f4b9c53466e2dd6636f5ba2caa30a (diff)
bluez: Add Proximity profile description
1 files changed, 42 insertions, 0 deletions
diff --git a/bluez.tex b/bluez.tex
index 0776122..d116ada 100644
--- a/bluez.tex
+++ b/bluez.tex
@@ -2,6 +2,7 @@
@@ -133,9 +134,50 @@ using this API should register a watcher to control connections, and to receive
+The Proximity profile specification defines the behavior related to the spatial
+relationship between devices (how the device will act when the connection is
+lost or the path loss increases, etc.).
+It includes two roles: the Proximity Reporter (GATT server) and the Proximity
+Monitor (GATT client).
+A device that supports the Proximity Reporter role shall implement the Link
+Loss service \cite{lls}, and optionally the Immediate Alert \cite{ias} and TX
+Power \cite{txp} services.
+A device that supports the Proximity Monitor role should contain an application
+that interacts with the Link Loss service and optionally the Immediate Alert
+and TX Power services. This application should allow the user to set the alert
+This profile is implemented in BlueZ and has a specific D-Bus API (described in
+{\em doc/proximity-api.txt} located on BlueZ source code) for both roles.
+For Monitor role we have:
+\item Methods: GetProperties(), SetProperty()
+\item Signals: PropertyChanged()
+\item Properties: SignalLevel, LinkLossAlertLevel, ImmediateAlertLevel
+For Reporter role:
+\item Methods: GetProperties()
+\item Signals: PropertyChanged()
+\item Properties: ImmediateAlertLevel, LinkLossAlertLevel
\section{Contact channels}
+\bibitem{lls}Link Loss service. \url{}
+\bibitem{ias}Immediate Alert service. \url{}
+\bibitem{txp}TX Power service. \url{}