TML. There are a number of competing formats, such as WAP and xHTML, which also vary from vendor to vendor. Devices are non-standard, and each type generally has its own set of requirements for receiving Internet data. After reading the HTTP header, the server then compares the information against a database that stores rules for content conversion while downloading the requested content from the Internet. The conversion rules provide parameters for reducing color depth and image size, data compression formats, deleting non-critical graphics, reformatting tables to plain text, and in general, for dealing with graphic formats and images the mobile network or device cannot support. Obviously, devices are limited by the capabilities of their user interface. A text-only screen simply cannot display Web graphics, The Ultimate Guide to Building and Delivering OSS/BSS but it can handle menus, links and data. Most transformation vendors build their conversion rules databases to be configurable, SO IICs have some control over the look and feel of the mobile Web content they deliver. Proxy reads HTTP header information; determines Mobile device device type, browser and initiates request for available bearer capacity Internet content Proxy Server Internet 5 Delivers Requests and converted receives Internet content content Conversion Database Refers to Cache conversion database Figure 12. Content Transformation Process OSS FOR 2.5 AND 3G NETWORKS The provisioning processes and content transformation technologies we have just looked at could be replaced entirely as new mobile network technologies are deployed, though it will be a gradual transition. What provisioning and billing requirements these new networks will bring remains Chapter 3 - Automating the Internet Infrastructure Supply Chain to be seen. There are still a number of questions to answer about exactly how services will be controlled and delivered in the next-generation mobile environment, generally referred to as 2.5 and/or 3G - in other words, mobile networks ge