You Are Here:

Community: Blogs

Who am I?

Carbider

Konstantine Voytenko
BluSPAN project coordinator
Fishnest Ltd.
bluspan@gmail.com

 

Calendar

« May 2008 »
Mo Tu We Th Fr Sa Su
      1 2 3 4
5 6 7 8 9 10 11
12 13 14 15 16 17 18
19 20 21 22 23 24 25
26 27 28 29 30 31  
 

Open Source Bluetooth PAN's Forum Nokia Blog

PAN service advertise

Carbider | 28 May, 2008 14:47


It is interesting the PAN (Bluetooth Personal Area Networking) profile is listed at Symbian 9.2 abilities.
The PAN overview is here:
...symbian.com/developer/techlib/v9.2docs/...

And a small API mention is here:
...symbian.com/developer/techlib/v9.2docs/...

Despite the fact that there is no completely ready PAN API in S60 3rd there are some type definitions and constants related to the deal. They are defined at btsdp.h header file here:
...symbian.com/developer/techlib/v9.2docs/...

Here are some constants that seem to be tempting for my Bluetooth inquisitive mind:

Listing - 1
/** PAN Service Class UUID */
static const TInt KPanUUUID = 0x1115;
/** PAN NAP Service Class UUID */
static const TInt KPanNapUUID = 0x1116;
/** PAN GN Service Class UUID */
static const TInt KPanGnUUID = 0x1117;


These values represent identifiers of Bluetooth(c) services that could be advertised by device.

There is a Chat example that advertises the Serial Port service. I decided to try one's luck with PAN.

const TInt KServiceClass = 0x1101;    //  SerialPort

Chat example supplies the service's identifier constant by returning this value from function below:

Listing - 2
TInt CChatServiceAdvertiser::ServiceClass()
{
    return KServiceClass;
}

The KServiceClass constant is assigned to '0x1101' by default. I've changed the function to this manner:

Listing - 3
TInt CChatServiceAdvertiser::ServiceClass(TInt aAttemptNumber)
{
    switch(aAttemptNumber) {
     case 0 :
        return 0x1115; // PAN
        break;
     case 1 :
     return 0x1116; // PAN NAP
     break;
     case 2 :
     return 0x1117; // PAN GN
     break;
    }
}


This gives me a possibility to supply the AttemptNumber parameter to the function - so to test all 3 service classes by turns.

In the similar manner I had rewritten the function that returns the service's symbolic name.

Listing - 4
const TDesC& CChatServiceAdvertiser::ServiceName(TInt aAttemptNumber)
{
 switch(aAttemptNumber) {
 
  case 0 :
     return _L("PAN"    );  //  PAN
     break;
  case 1 :
     return _L("PAN NAP");  //  PAN NAP
     break;
  case 2 :
     return _L("PAN GN" );  //  PAN GN
     break;
 
     
 }
}

Each time I've started the chat server I’ve outputted the qualifying message in this way:

iLog.LogL( _L("Attempt#"), iAttemptNumber );


After building the application under Phone release (GCCE) I had signed it myself and sent to my device.

As a Contributor of the Month I have got one. It's a Nokia N95 8GB.
With that one I can test a lot. It really helps in development. And also that multimedia computer is cool one ;)

Then I started the app on the phone and turned on the PAN search service on the WinXP SP2 machine.
However after all three service classes were advertised one by one, the XP machine did not detect any.

Connectivity, S60, Symbian C++ | Next | Previous | Comments (0) | Trackbacks (0)

RSSComments

You must login to post comments. Login
 

Rate This

 
 
Bookmark this page: DeliciousDiggFacebookGoogleYahooStumbleUponRedditFurlTechnocratiMagnoliaTwitter  Share this page Share this page Print this Page Print this page Invite a friend Invite a friend
Email Newsletters Press Terms & Conditions Privacy Policy Sitemap Contact Us © 2009 Nokia 
RDF Facets: qdcZdescriptionQSxCarbiderE20E7cE2028E20MayE2cE202008E2014E3a47E20ItE20isE20interestingE20theE20PANE20E28BluetoothE20PersonalE20AreaE20NetworkingE29E20profileE20isE20listedE20atE20SymbianE209E2e2E20abilitiesE2eE20TheE20PANE20overviewE20isE20hereE3aE20E2eE2eE2esymbianE2ecomE2fdeveloperE2ftechlibE2fv9E2e2docsE2fE2eE2eE2eE20AndE20aE20smallE20APIE20mentionE20isE20hereE3aE20E2eE2eE2esymbianE2ecomE2fdeveloperE2ftechlibE2fv9E2e2docsE2fE2eE2eE2eE20E44espiteE20theE20factE20thatE20thereE20isE20noE20completelyE20readyE20PANE20APIE20inE20S60E203rdE20thereE20areE20someE20typeE20definitionsE20andE20constantsE20relatedE20toE20theE20dealE2eE20TheyE20areE20definedE20atE20btsdpE2ehE20headerE20fileE20hereE3aE20E2eE2eE2esymbianE2ecomE2fdeveloperE2ftechE2eE2eE2eX qdcZidentifierQSxhttpE3aE2fE2fblogsE2eforumE2enokiaE2ecomE2fblogE2fopenE2dsourceE2dbluetoothE2dpansE2dforumE2dnokiaE2dblogE2f2008E2f05E2f28E2fpanE2dserviceE2dadvertiseX qdcZpublisherQUxhttpE3aE2fE2fswE2enokiaE2ecomE2fidE2fc764fd1cE2d8b06E2d499aE2d9a6aE2d17c3903d5a65E2fforumE5fnokiaE5fcrawlerE5fagentX qdcZtitleQSxOpenE20SourceE20BluetoothE20PANE27sE20ForumE20NokiaE20BlogE20E7cE20PANE20serviceE20advertiseX qdcZtypeQUqfnZE45E78cludedFromGeneralE4cistingsQ qdcZtypeQUqfnTypeZBlogContentQ qdcZtypeQUqfnTypeZBlogE45ntryQ qdcZtypeQUqfnTypeZCommunityContentQ qdcZtypeQUqfnTypeZE52esourceQ qdcZtypeQUqfnTypeZWebpageQ qdcZtypeQUqmarsZManagedE52esourceQ qdcZtypeQUqwebZInformationE52esourceQ qdcZtypeQUqwebZPageQ qdcZtypeQUqwebZE52esourceQ qdcZtypeQUqrdfsZE52esourceQ qrssZdescriptionQSxCarbiderE20E7cE2028E20MayE2cE202008E2014E3a47E20ItE20isE20interestingE20theE20PANE20E28BluetoothE20PersonalE20AreaE20NetworkingE29E20profileE20isE20listedE20atE20SymbianE209E2e2E20abilitiesE2eE20TheE20PANE20overviewE20isE20hereE3aE20E2eE2eE2esymbianE2ecomE2fdeveloperE2ftechlibE2fv9E2e2docsE2fE2eE2eE2eE20AndE20aE20smallE20APIE20mentionE20isE20hereE3aE20E2eE2eE2esymbianE2ecomE2fdeveloperE2ftechlibE2fv9E2e2docsE2fE2eE2eE2eE20E44espiteE20theE20factE20thatE20thereE20isE20noE20completelyE20readyE20PANE20APIE20inE20S60E203rdE20thereE20areE20someE20typeE20definitionsE20andE20constantsE20relatedE20toE20theE20dealE2eE20TheyE20areE20definedE20atE20btsdpE2ehE20headerE20fileE20hereE3aE20E2eE2eE2esymbianE2ecomE2fdeveloperE2ftechE2eE2eE2eX qfnZdistributionQUxhttpE3aE2fE2fblogsE2eforumE2enokiaE2ecomE2fX qfnZtopicQUqfnTopicZconnectivityQRqdcZtypeQUqrdfsZE52esourceQRqmarsZrelevanceQNx100X qfnZtopicQUqfnTopicZcppQRqdcZtypeQUqrdfsZE52esourceQRqmarsZrelevanceQNx100X qfnZtopicQUqfnTopicZseriesE5f60QRqdcZtypeQUqrdfsZE52esourceQRqmarsZrelevanceQNx100X qfnZtypeQUqfnTypeZBlogContentQ qfnZtypeQUqfnTypeZBlogE45ntryQ qfnZtypeQUqfnTypeZCommunityContentQ qfnZtypeQUqfnTypeZE52esourceQ qfnZtypeQUqfnTypeZWebpageQ qfnZupdatedQDx2008E2d05E2d28X qfnZuserE5ftagQSxconnectivityX qfnZuserE5ftagQSxs60X qfnZuserE5ftagQSxsymbianE2dcE2bE2bX qmarsZdescriptionQSxCarbiderE20E7cE2028E20MayE2cE202008E2014E3a47E20ItE20isE20interestingE20theE20PANE20E28BluetoothE20PersonalE20AreaE20NetworkingE29E20profileE20isE20listedE20atE20SymbianE209E2e2E20abilitiesE2eE20TheE20PANE20overviewE20isE20hereE3aE20E2eE2eE2esymbianE2ecomE2fdeveloperE2ftechlibE2fv9E2e2docsE2fE2eE2eE2eE20AndE20aE20smallE20APIE20mentionE20isE20hereE3aE20E2eE2eE2esymbianE2ecomE2fdeveloperE2ftechlibE2fv9E2e2docsE2fE2eE2eE2eE20E44espiteE20theE20factE20thatE20thereE20isE20noE20completelyE20readyE20PANE20APIE20inE20S60E203rdE20thereE20areE20someE20typeE20definitionsE20andE20constantsE20relatedE20toE20theE20dealE2eE20TheyE20areE20definedE20atE20btsdpE2ehE20headerE20fileE20hereE3aE20E2eE2eE2esymbianE2ecomE2fdeveloperE2ftechE2eE2eE2eX qmarsZlanguageQUxhttpE3aE2fE2fswE2enokiaE2ecomE2flanguageE2d1E2fenX qrdfZtypeQUqfnZE45E78cludedFromGeneralE4cistingsQ qrdfZtypeQUqfnTypeZBlogContentQ qrdfZtypeQUqfnTypeZBlogE45ntryQ qrdfZtypeQUqfnTypeZCommunityContentQ qrdfZtypeQUqfnTypeZE52esourceQ qrdfZtypeQUqfnTypeZWebpageQ qrdfZtypeQUqmarsZManagedE52esourceQ qrdfZtypeQUqwebZInformationE52esourceQ qrdfZtypeQUqwebZPageQ qrdfZtypeQUqwebZE52esourceQ qrdfZtypeQUqrdfsZE52esourceQ