Community Sites
Create your own community website and start earning today !
It's Free !
 
Communities Members BookmarksPolls Fresher Jobs Strange Photos Academic Projects New Member FAQ  



My Profile
Active Members
TodayLast 7 Days more...



Awards & Gifts
Online Exams

Fresher Jobs


Our fresher job section is exclusively for fresh graduates! Find jobs for freshers in major Indian cities including Bangalore, Chennai, Hyderabad, Pune or Kochi

Resources


Find educational articles, blogs, discussion threads and other resources.

Colleges


Find details about any college in India or search for courses.

website counter



IMPLEMENTATION OF WAP FOR BLUETOOTH


Posted Date: 21 Feb 2008    Resource Type: Articles/Knowledge Sharing    Category: General

Posted By: satish       Member Level: Gold
Rating:     Points: 5



IMPLEMENTATION OF WAP FOR BLUETOOTH
In order to effectively implement support for WAP over Bluetooth, certain capabilities
must be considered.
4.2.1 WDP Management Entity
Associated with an instance of the WDP layer in the WAP Protocol Stack is an
entity that is responsible for managing the services provided by that layer. The
WDP Management Entity (WDP-ME) acts as an out-of-band mechanism for
controlling the protocol stack.
4.2.1.1 Asynchronous Notifications
The WDP-ME will need to be able to generate asynchronous notifications to
the application layer when certain events occur. Example notifications are:
• New Client Node Detected
• New Server Node Detected
• Client Node Signal Lost
• Server Node Signal Lost
• Server Push Detected (detected as unsolicited content)
Platform support for these events is implementation-specific. All of the listed
events may be derived through the Bluetooth Host Controller Interface
(page 535), with the exception of Server Push.
4.2.1.2 Alternate Bearers
An implementation of WAP on a particular device may choose to support multiple
bearers. Methods of performing bearer selection are beyond the scope of
this document. The procedure to be followed is implementation-dependent.
4.2.2 Addressing
Two basic types of addressing are being used in the WAP environment: User
Addressing and Proxy/gateway Addressing. User addressing describes the
location of objects within the network, and is independent of the underlying
bearer. Proxy/Gateway Addressing describes the location of the WAP proxy/
gateway that the device is communicating with. Proxy/Gateway addressing is
dependent on the bearer type.
The end user deals mainly with Uniform Resource Locators (URL). These
addresses are text strings that describe the document that is being accessed.
Typically, the Proxy/gateway in conjunction with Internet Domain Name.
Servers resolve these strings into network addresses.
The address of the WAP Proxy/gateway is usually a static value that is configured
by the user or network operator. When the user enters a URL, the request
is forwarded to the configured WAP proxy/gateway. If the URL is within the
domain of a co-located server, then it indicates that the document is actually
WAP content. If the URL is outside of the WAP proxy/gateway’s domain, then
the WAP Proxy/gateway typically uses DNS name resolution to determine the
IP address of the server on which the document resides.
The client device would first identify a proxy/gateway that is reachable through
Bluetooth, then it would use the service discovery protocol to present the user
with a server name or description. When the user selects a server, then the
WAP client downloads the home page of the server (as determined by the discovery
process; see section 4.1.1.1 on page 523) Once the user has navigated
to the home page of the desired server, then all subsequent URLs are relative
to this home page. This scenario presumes that the WAP Proxy/gateway and
WAP Content server are all co-located in the Bluetooth device, although this
structure is not required for interoperability.
A WAP Proxy/gateway/Server will typically provide a default URL containing
the home page content for the server. A proxy-only device typically provides no
URL or associated content.
4.3 NETWORK SUPPORT FOR WAP
The following specifies a protocol stack, which may be used below the WAP
components. Support for other protocol stack configurations is optional, and
must be indicated through the Bluetooth Service Discovery Protocol.




Responses


No responses found. Be the first to respond and make money from revenue sharing program.

Feedbacks      
Popular Tags   What are tags ?   Search Tags  
(No tags found.)

Post Feedback


This is a strictly moderated forum. Only approved messages will appear in the site. Please use 'Spell Check' in Google toolbar before you submit.
You must Sign In to post a response.
Next Resource: THE USE OF WAP IN THE BLUETOOTH ENVIRONMENT
Previous Resource: IMPLEMENTATION OF WAP FOR BLUETOOTH
Return to Discussion Resource Index
Post New Resource
Category: General


Post resources and earn money!
 
Related Resources

Watch TV Channels



Contact Us    Editors    Privacy Policy    Terms Of Use   

SpiderWorks Technologies Pvt Ltd. 2006 - 2007 All Rights Reserved.