Searching SDP Attributes Using COM Interfaces (Windows CE 5.0)

Send Feedback

Microsoft® Windows® CE provides COM interfaces that you can use to parse SDP records as streams. The application can check the validity of the response and convert the raw binary SDP data to a record stream by using ISdpStream methods. The record is returned as an ISdpRecord array. The array contains attribute identifiers and NodeData structures that contain meta data associated with the attributes. To retrieve attribute information about a service use the ISdpNodeContainer:IUnknown methods.

The Bthnscreate sample that ships with Windows CE, contains source code for creating and searching SDP records. For more information about this sample, see SDP Search and Record Generator Sample.

The following procedure converts binary service data into ISdpRecords and retrieves the RFCOMM channel identifier. For the complete code, see Retrieving the RFCOMM Channel Identifier.

To search SDP attributes by using COM interfaces

  1. Retrieve raw SDP binary data in a BLOB structure that you want to parse. For more information about discovering services of a Bluetooth device, see Querying Service Capability on Remote Bluetooth Devices.

  2. To initialize the Component Object Model (COM) for use by the current thread, call CoInitializeEx, as the following example code shows.

  3. To parse the buffer that contains the SDP data and return the service data in an ISdpRecord array, use ISdpStream methods. Retrieve the SDP records in a pointer of type ISdpRecord, as the following example code shows.

    ISdpRecord **pRecordArg;
    ISdpRecord *pRecord = NULL;
    if (ERROR_SUCCESS != ServiceAndAttributeSearchParse(szBuf,sizeof(szBuf),&pRecordArg,
      ...//Error handling code goes here.

    For information about SDP record parsing, and the implementation of the ServiceAndAttributeSearchParse function, see Parsing an SDP Record Using COM Interfaces.

  4. To store information about a specific attribute, define a class that inherits the NodeData class.

    class CNodeDataFreeString : public NodeData {
      CNodeDataFreeString() {
        type = SDP_TYPE_NIL;
      ~CNodeDataFreeString() {
      if (type == SDP_TYPE_STRING)
      else if (type == SDP_TYPE_URL)

    NodeData, is defined in the Bthapi.idl file, and stores information about Bluetooth service attributes.

  5. To retrieve the information about the attribute of the service record, iterate through the SDP record array and call the ISdpRecord::GetAttribute method. Pass the attribute identifier and receive the NodeData structure in the pNode parameter. The following code example shows how to call the ISdpRecord::GetAttribute function to retrieve a NodeData structure that is associated with the attribute identifier SDP_ATTRIB_PROTOCOL_DESCRIPTOR_LIST (4). The NodeData structure that is received contains information about the Bluetooth protocols settings for the service.

    ULONG ulRecords = 0;
    for (ULONG i = 0; i < ulRecords; i++) 
      pRecord = pRecordArg[i]; // Record to be examined.
      CNodeDataFreeString protocolList;
      // Contains SDP_ATTRIB_PROTOCOL_DESCRIPTOR_LIST data, if available.
      if (ERROR_SUCCESS != pRecord->GetAttribute(
                 SDP_ATTRIB_PROTOCOL_DESCRIPTOR_LIST, &protocolList) ||
                 (protocolList.type != SDP_TYPE_CONTAINER))
       ...  //If GetAttribute is sucessful process attribute.

    Note   When the application calls ISdpRecord::GetAttribute, the result set is returned as a URL or a string that is allocated by the caller. To ensure that the string is automatically released, use the class created in step 4. This class can also be used with ISdpNodeContainer::GetNodeStringData.

    In the preceding example, the returned NodeData structure, received in protocolList, may contain Bluetooth protocol information in multiple NodeData child elements. Each one of these elements represents a particular Bluetooth protocol, such as RFCOMM or L2CAP. These protocol elements are composed of NodeData child elements that contain information about the protocol such as the UUID and the channel identifier.

  6. To retrieve information such as the channel for a protocol, from the NodeData structure retrieved in step 5, iterate through the NodeData structure by using ISdpNodeContainer methods such as:

    The following code example determines the channel identifier for the RFCOMM protocol. To do this, the application iterates through the child elements of each protocol NodeData structure to find the RFCOMM UUID. As per the Bluetooth specification, the next item in this NodeData structure is an integer that contains the channel identifier. Once this integer value is found, searching is terminated and the channel identifier is returned to the caller.

    ISdpNodeContainer *pRecordContainer = protocolList.u.container;
    DWORD cProtocols = 0;
    NodeData protocolDescriptor; // Information about a specific protocol (for example, L2CAP, RFCOMM).
    for (j = 0; j < cProtocols; j++) 
      if (protocolDescriptor.type != SDP_TYPE_CONTAINER)
      ISdpNodeContainer *pProtocolContainer = protocolDescriptor.u.container;
      DWORD cProtocolAtoms;
      for (k = 0; k < cProtocolAtoms; k++) 
        NodeData nodeAtom;  // Individual data element, such as what protocol this is or RFCOMM channel ID.
        if (IsRfcommUuid(&nodeAtom))
          if (k+1 == cProtocolAtoms) 
            break;// Misformatted response.
          NodeData channelID;
    //Call the helper function that returns the channel ID based on specificType.
          if (GetChannel(&channelID,&ulChannelId)) 
            fSuccess = TRUE;
            goto done;
          break; // Formatting error.
  7. Perform memory cleanup operations by releasing the ISdpRecord record.

    The following code example shows how to release the SDP record by using standard COM methods.

    for (i = 0; i < ulRecords; i++) 
      return 0;

See Also

Bluetooth Application Development

Send Feedback on this topic to the authors

Feedback FAQs

© 2006 Microsoft Corporation. All rights reserved.