ces, however, is flexible access to them. As long as a user can get online, he can access his services. So, whether using that DSL line, or dialing-up remotely, he should be able to access the same set of services, limited only by his available bandwidth. Simple service examples include Web-based e-mail, voice mail, Internet fax and scheduling tools. We can expand this example to include things like ASP services, perhaps providing access to ERP applications. In a VoIP/VoDSL environment, the user might have access to find-me/follow-me services, which might allow him to log-in to any IP-based phone and direct all of his normal voice services to it. What we find here is a major difference between the nature of infrastructure services and virtual services. An infrastructure service, such as a T-1 circuit, generally serves a location and a group of users. It is not a personalized service, it is just an access pipe. Virtual services, however, are based more on the individual. Individuals need access to certain sets of services and often want some ability to personalize their user interfaces. The key is not to tie the user to a location. If he cannot be in the office to access the T-1 line, he should still be able to access his services remotely. In many cases, this is done on another network or by dial-up modem. Mobile networks, as they converge on the Internet, are becoming the culmination of both service and access ubiquity. THE MOBILE WORLD The ways in which the mobile world is evolving and growing are making it a more and more suitable environment for eBusiness. Mobile services, Chapter 3 - Automating the Internet Infrastructure Supply Chain networks, and devices are increasingly important parts of the IIC supply chain. eBusiness applications are already being ported to mobile devices, and that trend is likely to continue with improved device flexibility and increased network bandwidth. Simply stated, one can access the Internet with mobile devices and can use most of what the Internet offers this way. Furthermore,