DESC:FIELD OF THE INVENTION
The present invention relates to usage-based billing for telematics services The Telematics-as-a-Service (TaaS) is provided by a telematics service provider [TSP] who raises a bill for each period based on a plan which consists of group of features subscribed by the users or fleet owners who operate and desire to monitor one or more vehicles for efficiencies and safety. Advantageously, the present invention allows fleet owners to control the billing at a granular level instead of being based on a fixed plan with a group of features. This granular and dynamic control offers flexibility and transparency leading to cost and resource efficiencies for both fleet owners and telematics service providers.

BACKGROUND OF THE INVENTION
Telematics is an interdisciplinary term that refers to integrated use of telecommunication and information systems, information storage, usage, transmitting, receiving and processing. Telematics devices and system along with the global positioning system are integrated with computers and mobile communication technologies in automotive information and navigation systems. An onboard telematics device in a vehicle collects information about the engine and driver behavior including but not limited to its location, state, fuel level, speed and ignition. This collected data is sent as data feeds to the telematics server which in turn processes it for reports and alerts. The telematics devices are normally configured to send data every 60 seconds to the telematics server which should have the capacity to process thousands of feeds every second and store historical data for a period of 6 to 12 months. The data exchange interval can be configured and not every category of vehicle requires a 60 second interval.

The subscribers of the telematics services operated by a telematics service provider (TSP) usually pay as per the chosen subscription plan per vehicle in the fleet for a period of time. The period could be monthly, quarterly, yearly or even few years. With each subscription plan, the user is entitled to a list of features with the ability to customize a plan with specific add-on’s such as additional storage space etc.

A fleet may comprise of different kinds of vehicles such as light and heavy trucks or passenger buses, passenger cars or taxis, school buses, earth movers, concrete mixers, armored cash transit vehicles or even two wheelers used for food or courier delivery. Hence, a fleet owner’s requirement from a telematics service varies significantly based on the category of vehicles they own and customer segments they serve. For example, ambulance vehicles or armored cash transit vehicles require near real-time monitoring when compared to passenger vehicles or trucks. The trucking industry requires monitoring of engine parameters and driver behavior which affect fuel consumption given the longer distance in road trips undertaken in this segment. These vehicles also have requirements to store data for longer periods for analysis towards operational efficiency improvements. In the case of school and public transport buses, the users will want to receive alerts on their mobile phones based on the location of the vehicle. Also, in some cases, a particular fleet owner may have different types of vehicles within the fleet serving different customer segments with some vehicles fitted with onboard cameras to continuously capture images or videos of the driver cabin and transmit the same to the telematics server. The problem with subscription-based billing plan is that the pricing is based on features grouped typically as basic, premium and advanced for a given period. The period maybe monthly, quarterly, yearly or even few years. It does not address the varying needs of fleet owners who have different types of vehicles catering to different industries, customer segments and fleet sizes. Even with multiple subscription plan choices with different combination of feature groups, it still does not provide granular control to fleet owners to pay for what they use at an individual feature level. This results in cost inefficiencies for both the fleet owner and the telematics service provider (TSP’s) because in some situations the fleet owners pay for a feature they will never use or leverage well. Also, in some situations the TSP’s will incur higher costs when certain vehicle maximizes use of a feature within the plan. For example, a fleet owner of school buses may require real-time tracking of vehicles only during the school working days particularly for few hours in the morning and in the afternoon and not during weekends and school holidays. Hence, most school buses will find it optimal to subscribe for the telematics service say only for 200 days in a year with real-time tracking for 3 hours in the morning and in the afternoon. In the subscription plan-based approach, the fleet owner is forced to pick a plan that includes real-time tracking feature for 365 days in a year for the entire day. This results in unnecessary costs and inefficiencies for both the fleet owner and TSP’s. As another example, consider a fleet owner with hundreds of geo-fences setup for thousands of vehicles within the fleet resulting in high complexity of data processing on the telematics server leading to higher cost of processing for the TSP’s. It is such variation at feature level is not possible when grouping features in tier-based subscription plans.

The fleet owners and TSP’s alike need a usage-based billing approach which charges them based on actual processing and use of telematics services across their fleet instead of a fixed fee approach based on number of vehicles for a set of features. The case for a billing system which provides granular control is further strengthened by the fact that vehicles used in different sectors and applications are inherently different and so are their requirements from telematics services.

The billing system allows fleet owners to dynamically configure preferences at feature level and computes billing based on resultant workload on the telematics server to receive and process data or to generate reports and send alerts based on thresholds for the selected features.
The historical data will be retained based on storage space available and the data exchange interval can be adjusted to maximize storage space for an increased the range. The TSP’s allow fleet owners to grouping vehicles into sub-groups that can subscribe to different plan offerings with varied set of features. While this allows switching between plans within a fleet , it is still within the scope of of features within a plan and does not allow granular and dynamic control at feature level. For example, if the vehicles run less in a given month with reduced number of alerts processed thus resulting in reduced server processing and storage then there is opportunity for the TSP’s to pass on the savings to the subscriber for best transparency and flexibility. The ability for subscribers to dial-up or dial-down usage based on transient needs and budgetary changes provides the flexibility.

US7406321 disclosed a method for providing user-selected telematics services in a mobile vehicle. The method includes accessing a menu of available telematics services and selecting a desired telematics service. The method also includes determining a telematics service fee based on the user selected service and paying the user selected telematics service fee via remote resource. The method further includes receiving the selected telematics service. It discloses method for providing user-selected telematics services in a mobile vehicle, wherein the service request is initiated by an onboard call center request, or by speaking the request through an onboard VRU or voice response unit, this initiates the service, preprogrammed audible script of the list of telematics services is provided, the user is allowed to select the desired service to retrieve, from the onboard control gate, vehicle-specific information and a fixed amount for the selected telematics service; fee is one time and based on the user selected service. It is not usage based billing.

US20050177478 disclosed a method for managing promotional telematics services within a telematics equipped mobile vehicle. The method includes receiving a request to initiate at least one telematics service. The telematics service is associated with a special billing plan with a predetermined time value. The invention doesn't provide user usage based billing, but billing based on a special predetermined time.

Aforesaid background art has a disadvantage. Users have varying needs but existing plans try to templatize their needs and don’t offer the flexibility. In usage based billing, users are charged only for what they use..

It is the purpose of the present invention to aid the users or fleet owners who subscribe to telematics services to control the cost at a granular level based on usage and thus leading to cost and resource efficiencies resulting in growth of telematics adoption by overcoming the inadequacies of the background art. A wider telematics adoption enhances safety and efficiencies of vehicle and passengers.
Accordingly, there exists a need for usage-based billing of telematics services. Further, there exists a need for a billing system to capture user preferences and translate them to data parameters or settings on the telematics device and telematics server which in turn determines the workload of the system; so that telematics service subscribers are charged based on usage.

SUMMARY OF THE INVENTION
It is a primary object of the present invention to provide a usage based billing system for telematics services (100) which comprises of a telematics device (101) mounted on a vehicle and a telematics server (110) integrated with a billing system (130), and a user interface (170) enabling access to the billing system (130) through the telematics server (110), wherein the telematics device (101) collects a vehicle’s engine from vehicle’s controller area network (CAN) bus and location data (300) received from a GPS satellite (206),wherein a communication means (120) is used to transmit the collected vehicle data(300) based on user preference at the user interface (170) from the telematics device (101) to the telematics server (110) through a network or internet (160),
wherein the telematics device (110) be configured to send user preferences for vehicle data (300) through the communication means (120) at pre-determined time intervals, wherein the billing system (130) is configured to calculate billing based on data usage, wherein the user (170) selects required features of telematics services at granular level which in turn determines data parameters such as the data exchange interval (97) and payload of data (99) between the telematics device (101) and the telematics server (110).

The billing depends on data exchange interval (97), report (80) types and duration, alert types (90) and thresholds which in determine the workload (50) of the telematics server (110).
These in turn determines the payload of data being exchanged (99), volume of data stored (98), and processing done to generate reports & alerts and use of vehicle positional data generated by GPS for playback and address look-up features. The billing information (112) comprises of number of transactions based on payload, number and type of reports, number and type of alerts and number of vehicle location displayed and addresses look-up.

It is another aspect of the present invention, wherein the data exchange interval (97) comprises of time interval for sending of data from the telematics device (101) to the telematics server (110).

It is another aspect of the present invention, wherein the factors for billing information (112) variants are a) data exchange interval (97) b) payload (99) of data exchanged between telematics device (101) and telematics server (110) c) storage (98) and d) data processing for reports and alerts and e) display of vehicle position with location data generated by GPS satellite (206).

It is another aspect of the present invention, wherein the billing system (130) automatically configures the system for data parameters (300) as per user preferences at feature level captured via the user interface (170).

It is another aspect of the present invention, wherein the system (100) is configured to change the default send interval (97) and payload parameter of the device based on user preference of parameters (300) for alerts (90) and reports (80).

It is another aspect of the present invention, wherein the communication means (120) comprises of wireless or cellular communication.

It is another aspect of the present invention, wherein the telematics server (110) comprises a processor, a memory unit operatively connected to the processor and includes a computer program product/ computer implementable instructions for determining the usage of the telematics server (110) by the user.

It is another aspect of the present invention, wherein the billing information (112) is generated from the user preference of data parameters (300) encompassing feed transactions (60), reports (80), alerts (90) and Maps (95), which determine the of work load (50) on the telematics server (110), volume of data stored (98) and use of GPS data (95) generated by the GPS satellite (206), and
wherein the workload (50) comprises of feeds processed (60), storage space consumed on the telematics server (110), number of reports (80) generated by the telematics platform (110), number of alerts (90) generated and usage type, number of Maps (95), data utilized on the server, server processing (98), two way data transfer between the server and the platform (99), and the like.
It is another aspect of the present invention, wherein the workload (50) due to feeds (60) comprises of:
number of transactions;
payload of transactions, and
wherein the transactions are determined by send interval (97) between the telematics device (101) and the telematics server (110), and
wherein the payload of transaction is based on user (180) configuration of parameters (300).

It is yet another aspect of the present invention, wherein feeds (60) comprises of one or more of location data, alerts, health and engine data of the vehicle.

It is another aspect of the present invention, wherein the reports (80) comprises of parameters selected from one or more of vehicle movement status data comprising speed, overspeed, idle or geofence data, mileage, trip summary, stoppage reports and the like.

It is another aspect of the present invention, wherein the server workload (50) for alert is based on the type of alert and alert threshold.

It is another aspect of the present invention, wherein the alerts (90) of parameters selected from one or more of overspeed alert, ignition alert, or vehicle stoppage alert, route deviation alert, and the like.

It is another aspect of the present invention, wherein maps (95) comprises of one or more such as Google maps, Open Street maps, HERE maps and any data retrievable from the global position of the vehicle.

It is another aspect of the present invention, to provide a method (200) for usage based billing for a telematics platform (110), comprising of steps:
collecting (210) of vehicle engine and location data by the telematics device (101);
Transmission (240) of the data to the telematics server (110) based on user configuration for features; which in turn determines the data exchange interval (97) by communication means (120)
receiving (241) of the data on the telematic server (110) towards support for reports, alerts and location data features;
processing (245) of the data by the server for feed (60), reports (80), alerts (90) and vehicle location data (95);
storage (246) of the processed data on the telematic server (110);
evaluation (250) of the stored data by enablement of the billing system (130) for and computation of the billing information (112);
generation (260) of billing information by the billing system (130) to the user based on the usage, and
wherein the evaluation (250) of vehicle data (300) by the billing system (130) of the telematics server (110) comprises of processing (245) and generation (260) of usage based billing information by computing the usage of the data by the user (180),
wherein usage is determined as variables of feeds received (60), alerts (90) and notifications generated, reports (80) generated, storage (98) used in the telematics server (110), processing in the remote server, two-way data transfer between the server and device (99),
wherein the billing system (130) is configured to receive vehicle data (300), store the data in a memory, and evaluate the data for bill generation based on usage, and
wherein the data exchange interval (97) is determined based on user preferences.

BRIEF DESCRIPTION OF DRAWINGS
Embodiments of the invention are illustrated in the figures of the accompanying drawings which are meant to be exemplary and not limiting, in which like references are intended to refer to like or corresponding parts, and in which:
FIG. 1 illustrates a block diagram of a usage based billing system for telematics services.
FIG. 2 illustrates a flow chart of the method for processing of the telematics data by the usage based billing system.
FIG. 3 illustrates the block diagram representing the billing system, the data parameters and the billing information.
DESCRIPTION FOR DRAWINGS WITH REFERENCE NUMERALS:
(100) Usage based billing system
(101) Telematics device
(97) user configured data exchange interval
(98) Server processing or payload on server
(99) Two way data transfer between the server and platform
(120) Communication means
(110) Telematics server
(130) Billing system
(112) Billing information
(60) Feeds
(80) No of reports
(90) No of alerts
(95) No of Maps
(170) user interface
(180) user
(200) Method for usage based billing for a telematics platform
(210) Collecting of vehicle data by the telematics device
(240) Transmission of the data to the telematics platform at user-configured time interval
(241) receiving of data on the telematic server
(245) Processing of data on the server
(246) Storage of the processed data on telematic server
(250) Evaluation of vehicle data and computation the billing information from the usage retrieved, by the billing system
(260) Generation of the billing information to the user based on data usage

DETAILED DESCRIPTION
The present invention as discussed in the various embodiments disclosed herein relates to a usage based billing system for telematics services.

A preferred embodiment of the present invention relates a usage-based billing system for telematics services (100). As illustrated in Figure 1, the usage based billing system (100) as disclosed in a preferred embodiment comprises of a telematic device (101) mounted on a vehicle, a telematics server (110) integrated with a billing system (130), and a user interface (170) enabling access to the billing system (130) through the telematics server (110). The telematics system according to the present invention provides an in-vehicle or vehicle onboard telematics device (101) comprising of: a controller, a diagnostics system configured to receive diagnostic information from the vehicle, a position-locating system configured to determine the vehicle's location information in communication with a GPS satellite (206), a communication means (120) which is either a cellular network or wireless communication configured to transmit information through a wireless network to an Internet-accessible telematics server (110). The position-locating system may be a conventional GPS (that interprets satellite signals to determine location) or a network-assisted GPS (that interprets both satellite and terrestrial wireless signals to determine location). The telematics server (110) comprises of a processor, a memory operatively connected to the processor and includes a computer program product or computer implementable instructions for providing telematics services to the user (180). The controller runs machine-readable computer instructions configured to receive diagnostic information from a host vehicle and location information from a position-locating system.

The data collected by the telematics device (101) is vehicle engine data i.e. diagnostic information, operational data and the location data based on user preferences (300) for transmission to the telematics server (110) via the wireless communication (120). The wireless communication means (120) is used to transmit the collected vehicle data (300) from the telematics device (101) to the telematics server (110) through a network or internet (160). The telematics device (101) is configured to send vehicle data (300) based on feature preferences at user configured time intervals (97) to the telematics server (110).
A preferred embodiment of the present invention provides a graphical user interface (170) to capture user preferences, wherein the user (180) selects required features of telematics services at granular level which in turn determines data parameters such as the data exchange interval (97) and payload of data (99) between the telematics device (101) and the telematics server (110).

The telematics server (110) is configured to receive the data (300) based on user preferences captured via the user interface (170) for further processing and storage on the server (110). The user preference of data parameters (300) such as data exchange interval, report types and duration, alert types and thresholds determines the workload (50) of the telematics server (110) comprising of data exchange interval (97), the payload of data being exchanged (99), volume of data stored (98), and processing done to generate reports & alerts and use of vehicle positional data generated by GPS, playback and address look-up for given latitude and longitude co-ordinates.

The telematics server (110) is integrated with a billing system (130), configured to generate a bill for the usage based on workload on the telematics server due to data exchange interval (97), payload of data (99) i.e two way data transfer between server and device, and data storage (98) on the telematics server, all of which are determined by the user preferences (300) captured via user interface (170). The billing system is configured to change the default send interval or data exchange interval (97) and payload parameters of the device based on user preference of parameters (300) for alerts (90), reports (80), maps (95) and the like.

The telematics server (110) is accessible by the user (180) at any user implementable devices or user interface (170). The user interface is accessible on user implementable devices according to embodiments of the present invention and is selected from one or more of handheld device, i.e. any personal computer, smart phone, laptops, desktops or tablets.

DATA PARAMETERS:
The billing is executed by the system to generate the billing information (112) to the user from the data parameters (300) that determine the workload (50) on the telematics server (110).The workload (50) according to an embodiment of the present invention comprises of number of feed data (60) transactions and volume of data exchanged between the telematics device and telematics server (99) or payload of data exchanged, number of reports (80) generated, both manual and automated based on type and duration of reports (80), number and type of Alerts (90) processed based on threshold settings and mode of notifications and use of maps for display and look-up of vehicle location data (95).

The billing information (112) is the information generated by the billing system (130) and comprises of a) number of feed transactions in each category [Table 1], b) number and type of reports [Table 4], c) number and type of alerts [Table 7] and d) number of vehicle locations displayed and address look-up transactions [Table 10]

It is pertinent to discuss that the feed data maybe of different categories as illustrated in Table 2 with varying payloads as discussed in Table 3. The feed transactions capture the number of such occurrences in each category for a given billing period as shown in Table 1.

Example 1: The billing information for feeds is computed based on total transactions during a given time period. An occurrence of feed of a particular type and category will be considered as a feed transaction. Each of such feed transaction will have its unique price per transaction to determine the bill amount. For example, if Alerts of Category 1 is 10 per transaction and Alerts of Category 2 is 20 per transaction due to higher payload then in a monthly billing for 100 alerts in Category 1 and 50 alerts in Category 2, the total bill amount will be 2000/- ( Two thousand only).

Example 2: The billing information for Reports (80) is based on the type of report [Table 5] such as over-speed, geo-fences, idling, mileage, trip summary and stoppage reports, to name a few. The type of report and the duration have impact on the billing. For example, to generate the geo-fences report for 1 week or 1 month will be significantly higher when compared to generating an overspeed report for the same period.
Example 3:
The workload (50) due to alerts (90) generated is based on the type of alert such as overspeed alert, route deviation alert, stoppage to name a few. While the payload across different alerts does not vary much, some type of alerts will have higher processing costs due to inspection of one or multiple feeds from the telematics device (101). The billing information for Alerts [Table 7] depends on type of alerts [Table 8] and notification categories [Table 9] such as email, SMS, or push notifications due to impact on the cost to the telematics service providers (TSP’s). For example, for push notifications to be supported, the users need to subscribe to the mobile application and cost of SMS’s are significantly higher when compared to Emails.

For processing geo-fence alerts where the telematics server (110) will need to inspect multiple feed data (60) with one more relevant geo-fences when compared to checking for a threshold value in the case of over speed alert. Also, certain alerts like idling alert will need correlation of vehicle movement data across multiple feeds based on threshold for processing.

Telematic server workload (50) is also based on alert thresholds and hence the processing costs reflects the same as alert transactions. For example, the workload on the telematics server to generate over-speed alerts with threshold of 80 km/hour will be significantly lower for 50 km/hour.
Example 4:
The type of maps [Table 11] to display vehicle location data can use either Google or Open Street maps which has impact on costs incurred by the telematics service provider and hence billing [Table 10]. Each of these types used either separately or in combination to support the features required as established by the user preferences [300]; for example, Google maps can be used for displaying addresses [Table 2] for Alerts of higher significance such as Overspeed Alert [Table 8] and a cost efficient maps choice such as Open Street [Table 11] can be used to display the addresses for Idle Report category. Hence, each is a separate transaction and priced accordingly for granular control.

An embodiment of the present invention, as shown in Figure 2, discloses a Billing system (130) which uses a method of billing based on usage of the telematics services as per user preferences (300).

The method comprises of determining the billing for the telematic services based on a) workload (50) on telematics server based on transactions [Table 1, 4, 7, 10] b) volume of data stored [Table 13] in the telematics server (98).

METHOD:
The method of processing of the usage-based billing system for telematics services (100), as illustrated in Figure 2, comprises of collecting (210) vehicle data (300) from the telematics device (101) mounted in the vehicle. The vehicle data comprises of both vehicle diagnostic data collected by the sensors on the vehicle and communicated to the telematics device and the vehicle location data (95) as captured by the GPS satellite (206).

The accrued data is transmitted (240), to the telematics server (110) at predefined time intervals, which may be periodical or programmed and instantaneous. The predefined time interval is a user configured time interval (97) for data exchange between the telematics device (101) and the telematics server (110) based on features (300) chosen.
The data transmitted by the telematic device by a communication means (120) which is preferably a cellular network (120) or the like, is received (241) at the telematics server (110).
The received data is processed (245) for reports, alerts, and vehicle location by the telematics server.
Processing of the data comprises of generation of reports (80), generation of alerts (90) and determination of vehicle location based on GPS location data (95) for display on maps.
Further the processed data is stored (246) on the telematic server (110).
The billing system (130) generates the bill by evaluating (250) the data stored on the server. The billing information (112) is the information generated by the billing system (130) and comprises of number of transactions based on payload, number and type of reports, number and type of alerts and number of vehicle location displayed and address look-up, and the user is charged for the bill generated (260).

TABLE 1: FEEDS (60)
Feeds
Month Day Feed Type Feed Category Transactions
1 1 F1 C1 1500
1 1 F2 C2 20
1 10 F2 C2 20
1 12 F2 C3 10

TABLE 2: FEED TYPE

CATEGORY
C Name
1 Location data
2 Alert packet
3 Health packet
4 Engine data

TABLE 3: FEED CATEGORIES

Feed category Payload range
1 < 1 MB
2 1 MB to 10 MB
3 > 10 MB

TABLE 4: REPORTS (80)
Reports
Month Day Report
Type Duration
category Transactions
1 1 R1 C1 10
1 1 R2 C2 10
1 10 R2 C3 5

TABLE 5: REPORT TYPE
Report Type Report
R1 Over speed Report
R2 Idle Report
R3 Geo-fences Report

TABLE 6: DURATION CATEGORY

Duration category Days range
C1 <7 days
C2 7 to 30 days
C3 >31 to 59 days

TABLE 7: ALERTS (90)

Alerts
Month Day Alert Type Notification
Category Transactions
1 1 A1 C1 1500
1 1 A2 C2 20
1 10 A2 C1 20

TABLE 8: ALERTS TYPE

Alert Type Alert
1 Overspeed
2 Ignition
3 Stoppage

TABLE 9: NOTIFICATION CATEGORY

Notification Category Notification
1 Email
2 SMS
3 Push notification

TABLE 10: LOCATION DATA (95)

Maps Usage
Month Day Map Type Usage
Category Transactions
1 1 M1 C1 1500
1 1 M2 C2 20
1 10 M2 C3 20

TABLE 11: MAPS DATA

Map Type Map type
1 Open Street Maps
2 Google Maps
3 Here Maps

TABLE 12: MAPS USE CASE

Usage Category Use case
1 Map View
2 Reverse Geocoding
3 Routes

TABLE 13: BILLING INFORMATION

Storage = price/GB * new data
Storage
Month Day New data (GB) Total
storage (GB)
1 1 10 100
1 1 20 130
1 10 5 135 ,CLAIMS:WE CLAIM:
1. A usage based billing system for telematics services (100), comprising of:
a telematics device (101) mounted on a vehicle;
a telematics server (110) integrated with a billing system (130); and
a user interface (170) enabling access to the billing system (130) through the telematics server (110),
wherein the telematics device (101) collects a vehicle’s engine and location data (300) received from a GPS satellite (206);
wherein a communication means (120) is used to transmit the collected vehicle data (300) from the telematics device (101) to the telematics server (110) through a network or internet (160);
wherein the telematics device (110) is configured to send vehicle data (300) through the communication means (120) at pre-determined time intervals,
wherein the billing system (130) is configured to calculate billing based on the workload (50), on the telematics server (110),
wherein user preference for billing is translated to data parameters (300) such as feed data (60), report types and duration, alert types and thresholds, maps, that determines the workload (50) on the telematics server (110) comprising of data exchange interval (97), the payload of data being exchanged (99), volume of data stored (98), and processing done to generate reports (80) & alerts (90) and use of vehicle positional data (95) generated by GPS, playback and address look-up for given latitude and longitude co-ordinates, and
wherein the billing information (112) comprises of number of transactions based on payload, number and type of reports, number and type of alerts and number of vehicle location displayed and address look-up.

2. The usage based billing system for telematics services (100) as claimed in claim 1, wherein the data exchange interval (97) comprises of time interval for sending of data from the telematics device (101) to the telematics server (110).

3. The usage based billing system (100) as claimed in claim 1, wherein the factors for billing information (112) variants are data exchange interval (97), payload (99) of data exchanged between telematics device (101) and telematics server (110), data storage (98), data processing for reports and alerts and display of vehicle position/ location data generated by GPS satellite (206).

4. The usage based billing system (100) as claimed in claim 1, wherein the billing system (130) automatically configures the system for data parameters (300) as per user preference captured via the user interface (170).

5. The usage based billing system (100) as claimed in claim 1, wherein the system (100) is configured to change the default send interval (97) and payload parameter of the device based on user preference of parameters (300) for alerts (90), reports (80) maps (95) and the like.

6. The usage based billing system (100) as claimed in claim 1, wherein the communication means (120) comprises of wireless or cellular communication.

7. The usage based billing system (100) as claimed in claim 1, wherein the telematics server (110) comprises a processor, a memory unit operatively connected to the processor and includes a computer program product/ computer implementable instructions for determining the usage of the telematics server (110) by the user.

8. The usage based billing system (100) as claimed in claim 1, wherein the vehicle operational data/vehicle data is collected by the telematics platform (110) at predetermined time intervals that are user (180) configured.

9. The usage based billing system (100) as claimed in claim 1, wherein the billing information (112) is generated from data parameters (300) comprising of work load (50) on server (110), volume of data stored (98) on telematics server (110) and use of GPS data generated by the GPS satellite (206), and
wherein the workload (50) comprises of feeds (60), number of reports (80) generated by the telematics platform (110), number of alerts (90) generated and usage type, number of map views and address look-up (95), server processing (98), two way data transfer between the server and the device (99), and the like.

10. The usage based billing system (100) as claimed in claim 1, wherein the workload (50) due to feeds (60) comprises of:
number of transactions;
payload of transactions, and
wherein the transactions are determined by send interval (97) between the telematics device (101) and the telematics server (110), and
wherein the payload of transaction is based on user (180) configuration of parameters (300).

11. The usage based billing system (100) as claimed in claim 9, wherein feeds (60) comprises of one or more of location data, alerts, health and engine data of the vehicle.
12. The usage based billing system (100) as claimed in claim 9, wherein the reports (80) comprises of parameters selected from one or more of vehicle movement status data comprising speed, overspeed, idle or geofence data, mileage, trip summary, stoppage reports and the like.

13. The usage based billing system (100) as claimed in claim 9, wherein the server workload (50) for alert (90) is based on the number and type of alert and alert thresholds.

14. The usage based billing system (100) as claimed in claim 9, wherein the alerts (90) of parameters selected are from one or more of overspeed alert, ignition alert, or vehicle stoppage alert, route deviation alert, and the like.

15. The usage based billing system (100) as claimed in claim 9, wherein maps (95) choices comprise of one or more such as Google maps, Open Street maps, HERE maps and any data retrievable from the global position of the vehicle.

16. A method (200) for usage based billing for telematics services (110), comprising of steps:
collecting (210) of vehicle data by the telematics device (101);
transmission (240) of the data to the telematics server (110) based on user configuration of features; which determine the data exchange interval by the communication means;
receiving (241) of the data on the telematic server (110);
processing (245) of the data by the server for feed (60), reports (80), alerts (90) and vehicle location data (95);
storage (246) of the processed data on the telematic server (110;
evaluation (250) of the stored data and
generation (260) of billing information by the billing system (130) to the user based on the data usage, and
wherein the evaluation (250) of vehicle data (300) by the billing system (130) of the telematics server (110) comprises of processing (245) and generation (260) of usage based billing information by computing the usage of the data by the user (180),
wherein evaluation (250) is executed by the billing system (130) to compute the billing information (112),
wherein usage is determined as variables of feeds received (60), alerts (90) and notifications generated, reports (80) generated, storage (98) used in the telematics server (110), processing in the remote server, two-way data transfer between the server and device (99),
wherein the billing system (130) is configured to receive vehicle data (300), store the data in a memory, and evaluate the data for bill generation based on usage, and

wherein the data exchange interval (97) is the user configured time interval for transfer/ transmission of data from the telematics device (101) to the platform (110) is user configured.