| By Bob Hendry | Article Rating: |
|
| April 1, 2004 12:00 AM EST | Reads: |
822 |
One thing we love to do in high tech is invent new terms, especially acronyms, but new terms of any form really appeal to us. I must confess I find the terminology of technology to be one of its paramount appeals. Of course, new terms sometimes fall into pervasive use without adequate definition, leading to confusion, but making the originator or purveyor of such terms feel great nonetheless. Sometimes terms fall into disfavor almost as rapidly as they appear.
Two terms floating around right now are access and distribution. Access is most often used for "Internet access," implying the connection between a user or point of presence and the rest of the Internet, usually represented by and often called a "cloud." Distribution, on the other hand, is the mechanism that provides the connection between a given user and said point of presence. All of this is very interesting in the context of wireless because it defines what is certain to be one of the key battles in the evolution of wireless communications.
To illustrate this, consider two different models for wirelessly connecting to the Internet. The first, based purely on access, is to use a relatively long-range connection between the client and the entry point to the Internet cloud, akin to the way cellular works today. This is how most people envision 3G or WiMAX, for example, being used to access the Internet. The problem with this model is that it uses fairly large cells, and thus doesn't have good frequency-reuse characteristics for a large number of users and/or high bandwidth connections - limiting the number of users and/or the speed of their connections, thus driving up prices. But it does allow a user equipped with a mobile access connection to carry this connection everywhere the appropriate infrastructure exists.
The alternative would be to bring the Internet via a wired or wireless point-to-point connection to a point of presence, and then use a distribution mechanism to provide the final link to the user. An example here might be to use WiMAX or some functionally equivalent terrestrial microwave link to connect to a point of presence, and then use a Wi-Fi access point (again, for example) to provide the infrastructure end of a distribution network. The other end would be, of course, notebooks, PDAs, or handsets equipped with Wi-Fi capability. This allows a fair number of users to share the otherwise expensive wide-area broadband connection, and also largely solves the problem of getting wide-area signals to penetrate a building by avoiding it altogether.
Which model is better? That depends. It would be great to carry only one radio and have it work everywhere. But this is something of a pipe dream, since it's unlikely we'll see a single wide-area technology deployed everywhere. We also have a problem with building radio penetration as noted above, but we might be able to address this issue via repeaters or in-building microcells, as is done with cellular today.
On the other hand, using Wi-Fi as a distribution mechanism also makes a lot of sense, but you might need a lot of access points to make this work. We can also deploy Wi-Fi meshes or lots of access points in a metropolitan area, in effect using Wi-Fi as an access technology. Wi-Fi is certain to be pervasive, and has the potential for very high throughput, so why not just settle on that?
The bottom line is that both models will continue to flourish. Keep in mind that multimode clients (and, eventually, multimode clients implemented with software-defined radio, or SDR) will mitigate this issue to some degree. One of the really exciting possibilities for future wireless communications systems is that we may see wireless services disappear quite literally into the ether, and not have to worry about having the right radio. It could eventually all be quite automatic and transparent. While our primary goal in wireless communications remains to narrow or even eliminate the behavioral and performance differences that exist between it and wire, an equally important goal is to improve ease of use so end users can do more communicating and less network-oriented thinking and planning. Oh, and there's another term - SDR. We'll cover that in a later issue. And maybe a few others as well.
Published April 1, 2004 Reads 822
Copyright © 2004 SYS-CON Media, Inc. — All Rights Reserved.
Syndicated stories and blog feeds, all rights reserved by the author.
More Stories By Bob Hendry
Bob Hendry is a PowerBuilder instructor for Envision Software Systems and a frequent speaker at national and international PowerBuilder conferences. He specializes in PFC development and has written two books on the subject, including Programming with the PFC 6.0.
- Why SOA Needs Cloud Computing - Part 1
- Cloud Expo and The End of Tech Recession
- The Transition to Cloud Computing: What Does It Mean For You?
- A Rules Engine Built in PowerBuilder
- Sybase Named “Silver Sponsor” of iPhone Developer Summit
- How PowerBuilder Got Its Groove Back
- The Cloud Has Cross-Border Ambitions
- Ulitzer Names The World's 30 Most Influential Virtualization Bloggers
- Ulitzer Named "New Media" Partner of Greatly Anticipated iStrategy Event in Berlin
- Risks and Enterprise Mobility?
- Steps for Success in Enterprise Mobility?
- Are Mobile Luddites Resisting Mobility?
- The Difference Between Web Hosting and Cloud Computing
- Sybase CTO to Speak at 4th International Cloud Computing Expo
- Why SOA Needs Cloud Computing - Part 1
- Cloud Expo and The End of Tech Recession
- The Transition to Cloud Computing: What Does It Mean For You?
- Five Reasons to Choose a Private Cloud
- Seeding The Cloud: The Future of Data Management
- The Threat Behind the Firewall
- Economy Drives Adoption of Virtual Lab Technology
- Tips for Efficient PaaS Application Design
- A Rules Engine Built in PowerBuilder
- Sybase Named “Silver Sponsor” of iPhone Developer Summit
- Where Are RIA Technologies Headed in 2008?
- PowerBuilder History - How Did It Evolve?
- The Top 250 Players in the Cloud Computing Ecosystem
- Custom Common Dialogs Using SetWindowsHookEx
- DDDW Tips and Tricks
- OLE - Extending the Capabilities of PowerBuilder
- DataWindow.NET How To: Data Entry Form
- Book Excerpt: Sybase Adaptive Server Anywhere
- Sybase ASE 12.5 Performance and Tuning
- Working with SOA & Web Services in PowerBuilder
- Office 2003 Toolbar: A New Look For Your Old PowerBuilder App
- Dynamically Creating DataWindow Objects
































