1.4.1. System Requirements

Derived from the user actions, different requirements on the LBS system architecture emerge. Further different types of services are offered by companies to satisfy the needs. Whereas types of services will be described later we will start with the requirements on LBS. In opposite to Geographic Information Systems which are usually desktop or client server applications with a limited number of users, do LBS provide access and information to a large number of users. (2004) lists the following capabilities of LB-Services that usually exceed the general requirements on static GIS use:

• High Performance: Delivering answers in sub-second if querying information from internet and databases.
• Scalable Architecture: Support thousands of concurrent users and terabytes of data.
• Reliable: Capable of delivering up to 99.999 percent up-time.
• Current: Support the delivery of real-time, dynamic information.
• Mobile: Availability from any device and from any location.
• Open: Support common standards and protocols (HTTP, Wireless Application Protocol - WAP, Wireless Markup Language - WML, Extensible Markup Language – XML, Multimedia Markup Language – MML).
• Secure: Manage the underlying database locking and security services.
• Interoperable: Integrated with e-Business applications such as Customer Relationship Management, Billing, Personalization, and wireless positioning gateways.

These requirements lead to a complex LBS architecture involving a number of players. These Players include hardware and software vendors, content and online service providers, wireless network and infrastructure providers, wireless handset vendors and branded portal sites. Only common specifications and agreements among these players do ensure a user satisfying offering and deployment of services.