EarthLink SPARK Development Kit

Available Information:

• Introduction
• Potential Applications
• Developer Kit Information
• Early Access Availability and Pricing
• Hardware Specifications
• AVL In-vehicle Protocol (API)
• Application Server API
• Order Now

AVL Telematic Application Server API

The Telematic Application Server component is the middleware AVL layer providing services to back-end server applications, such as web-server applications, WAP/WML applications, Palm Web Clipping applications, or Enterprise applications.

The Telematic Application Server interconnects to the mobile AVL network to retrieve the AVL unit's location data and provides this data to authorized applications via an easy-to-use HTTP interface.

Features

• HTTP/XML interface: to support location requests from Internet applications
  
• Location database: stores accurate information for all mobile units: time-stamp, latitude, longitude, speed, direction of travel, telemetry, and source
  
• Access controls: Ensure user privacy
  
• Separation of applications and mobile network: New network technologies can be deployed without requiring changes to already installed applications
  

The Telematic Application Server API functions are:

• Current Data. Request the current position information for a specified AVL unit, including time of report, latitude, longitude, geocoded location (street, city, state, zip), speed, course, and telemetry data including state of alarms and sensors, and the system temperature.
• Historical Data. Position data may be requested by specific date range, or the last n most recent positions.
• Diagnostic Data. Statistical and remote diagnostic data.
• Preferences and Settings. Retrieving and setting various user parameters, such as identity information, notification preferences, and other features.
• Remote AVL Control. Set tracking interval, request AVL statistics report, request position report (poll), reset statistics, turn off outputs, trigger alarm, unlock doors, and perform other AVL functions remotely.
• Events. Configure the Telematic Application Server to post events to your applications via HTTP.
• Messaging. Exchange messages with AVL in-vehicle applications. Such messages are passed transparently through the system and could contain application-specific protocol/control data to be processed by the in-vehicle application.