readme

blue tooth protocol stack source code

* sdp_server is used for searching the sdp database stored in the XML file
  sdp.xml.

* How the data is stored in the XML file will be described bellow.

* sdp_server needs the xml parser Expat to parse the XML file.

HOW THE COMMUNICATION WITH THE BLUETOOTH STACK WORKS.
-----------------------------------------------------
The communication with the bluetooth stack is done through read- and write
operations on a proc-file. The format of the data sent and received through
the proc-file is described in the .h-file  sdp_proc_protocol.h in
/include/linux/bluetooth/


HOW THE SDP DATA IS STORED IN THE XML FILE.
-------------------------------------------
The XML-file is divided into three different sections. These sections is
separated with the tags bluetoothSDP, SDPBrowsingRegister,
SDPTranslationRegister.

bluetoothSDP,
is where the parameters for the different profile is stored. The profile data
is then stored in the following way.


<!--First write the profile name followed by its servicerecord handle-->
<PROFILE_NAME ServiceRecordHandle = "0xXXXXXXXX">

<!--Then you can write all of the records for the given profile, don't forget
 to include the records for ServiceRecordHandle and ServiceClassIDList-->
 
   <ServiceRecordHandle Parameter0 = "0x0aXXXXXXXX">
   </ServiceRecordHandle>  <!--The parameter is written with the prefix 0a-->
   
   <ServiceClassIDList NbrOfEntities = "1">
      <PROFILE_NAME_1>    <!--The PROFILE_NAME will appear as a data element-->
      </PROFILE_NAME_1>   <!--sequence, PROFILE_NAME must be defined in the-->
                          <!-- SDPTranslationRegister-->
			  
      <PROFILE_NAME_2>    <!--If more the one profile are specified in the-->
      </PROFILE_NAME_2>   <!--serviceClassIDList, write them all here--> 
   </ServiceClassIDList>

   <!--If you want a character string write it as text between two tags-->  
   <ServiceName>LAN Access using PPP</ServiceName>

</PROFILE_NAME>

SDPBrowsingRegister,
is where the names for the incoming hex-values can be found. It consists of
three sub classes, Protocols, ServiceClasses, AttributeIdentifierCodes. All values is written as 16 bits UUIDs.
      
SDPTranslationRegister,
is where the hex-values for some of the parameters is found. All values are
written with its proper data element header.