- Shopping Bag ( 0 items )
Ships from: Houston, TX
Usually ships in 1-2 business days
Ships from: Austin, TX
Usually ships in 1-2 business days
The up-to-the-minute Wireless Web briefing for every technical professional.
Wireless PC-Based Services is a complete briefing on Wireless Web technologies for every entrepreneur, decision-maker, and technical professional. IBM architect and leading wireless developer R. Scott Lewis covers every aspect of deploying wireless Internet services, from business plans through application design, standards through development tools.
Lewis presents in-depth coverage of state-of-the-art applications such as unified wireless inboxes, S.100-based wireless call processing, wireless message storage, wireless metering services, and wireless network management. The book also includes state-of-the-art coverage of wireless media conversion applications: language translation, text-to-audio, OCR, and handwriting-to-text. Coverage includes:
If you're responsible for next-generation wireless Internet services, this book will increase your effectiveness — and reduce your risks — at every stage of the project lifecycle.
"Mr. Lewis' book is always the first wireless book that I pick up when I need a thorough treatment of all phases of wireless systems."
—Rajnish Prasad, Senior IT Architect, IBM
"With these brilliant descriptions of possible service available to the wireless industry, Scott clearly takes his place as a leading developer in the wireless space."
Nathalie Plaziac, Ph.D. Electrical Engineering, Motorola
|2||Wireless Services Overview||5|
|4||Legal Strategies for Software Companies||101|
|5||Developing Wireless Services||105|
|6||Vendor-Neutral Framework for Wireless Services||125|
|7||Vendor-Neutral Framework for Wireless Security||145|
|8||Wireless Fault Tolerant System Example||157|
|9||Computer Language Performance for Wireless Services||163|
|10||The Unified Wireless Inbox||193|
|11||Wireless Call Processing (S.100) Service||199|
|12||Wireless Directory Services||207|
|13||Wireless Message Storage Service Based on E-Mail||231|
|14||Wireless Network Management Service||259|
|15||Wireless Metering Service with MQI||293|
|16||Media Conversion - An Exemplary Wireless Service||301|
|17||Distributed Batch Processing for Wireless Communications||391|
|18||Queuing Theory for Fixed and Wireless Communications||411|
|19||The Future of Wireless Services||427|
NOTE: There is some overlap with the fixed network standards (i.e., SS7), but an effort was made to concentrate on the wireless networks.
For example, a service under Windows NT is explained that performs text-to-speech conversion for the purpose of retrieving a voice, fax, or e-mail message from your mobile terminal.
Last, the Internet Protocol suite was used to interconnect the various components and services, since it provides a vendor-neutral architectural framework, among other things.
Hence, it should be possible to use these same services on other platforms (e.g., LINUX) besides Windows NT.
A distinction between VAR and OEM is needed in order to clarify what is meant by integration as opposed to development.
Typically, the OEM is a specialist that is responsible for developing a product, whereas the VAR is a manager responsible for integrating the product into the cus-tomers' facilities.
The operative word is "integration"—where does the integration by the OEM stop and where does it begin for a VAR?
For argument's sake, let's take the example of a unified messaging system. Here are the basic off-the-shelf components for unified messaging:
Now, however, the assembly is easier since the software is intelligent and user-friendly and getting easier by the day. No longer is a computer scientist needed to build a state machine for handling the incoming calls. Today, ordinary users with little to no expertise can create a new service just by reading the online help within a CT (computer telephony) application generator and, before long, they have a service.
Therefore, having made this distinction, successful VARs must be quick at identifying applications to turn up in their system, whereas successful OEMs must focus on creating a specific component while not losing sight of the bigger picture the VAR contends with. The forte of the OEM will determine the components they build. What this means is that the OEM will have specialized talents in one field or another.
What distinguishes one OEM from other OEMs are state-of-the-art advances, for example, being the first company to fax at 56Kbps or implementing some new standard of compression.
An OEM requires talented employees who really understand the technology. As soon as a company loses its talent, it is in jeopardy of becoming a VAR.
However, don't be so quick to think you'll be able to find a replacement. According to Grady Booch, "Hyperproductive developers constitute less than about 1 or 2% of the entire development population." Furthermore, "hyperproductive developers are, on the average, 4 to 10 times more productive than the average developer."
If the company wishes to remain an OEM, it had better focus on keeping its talent. OEMs have the potential to sell products directly to the consumer, the government, or to VARs or operators. They are not precluded from selling services pertain-ing to their component.
VARS only have the potential to sell product to the consumer or the govern-ment. They typically don't have the talent to sell to OEMs.
This was done intentionally so the author could focus on the business of wireless PC-based services.
PRINCIPLE: Many organizations lack a documented process for devel-opment. The UML language and Rational Unified Process provide that in-frastructure. Using them raises the quality, capability, and maturity of any development team. Use them today in place of making your own.
The necessary documentation is available free on the Internet at www.rational.com.
1 Newton, pg 695.
2 Newton, pg 1052.