TELEMATICS SYSTEM WITH 3D INTERTIAL SENSORS

• US 20150246654A1
• Filed: 01/13/2012
• Published: 09/03/2015
• Est. Priority Date: 01/13/2012
• Status: Abandoned Application

• Current Assignee: Pulse Function F6 Limited
• Original Assignee: Pulse Function F6 Limited
• Inventors: Tadic, Srdjan, Dramicanin, Dejan, Karaklajic, Branko
• Application Number:
  US14/371,911
• Publication Number:
  US 20150246654A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: B60R 2021/01325 Vertical acceleration
• CPC Class Codes: B60R 2021/01327 Angular velocity or angular acceleration
• CPC Class Codes: B60R 21/0136 responsive to actual contact with an obstacle , e.g. to vehicle deformation, bumper displacement or bumper velocity relative to the vehicle monitoring crash strength in combination with passenger seat detection B60R21/01558
• CPC Class Codes: B60W 2556/10 Historical data
• CPC Class Codes: B60W 2556/45 External transmission of data to or from the vehicle
• CPC Class Codes: G01P 15/02 by making use of inertia forces using solid seismic massesG01P15/14 takes precedence
• CPC Class Codes: G01P 15/14 by making use of gyroscopes gyroscopes per se G01C19/00
• CPC Class Codes: G07C 5/0808 Diagnosing performance data testing of vehicles G01M17/00; testing of electrical installation on vehicles G01R31/005
• CPC Class Codes: G07C 5/085 using electronic data carriers

Abstract

The present invention considers the telematics systems providing apparatus and operation methods for apparatus, including wireless, accelerometer and gyroscope capabilities offering: trajectory recovery on transportation vehicle in the case of the predefined event, specific driving event detections like drifting, side-slip, roll-over, abrupt turning, as well as driving under influence, inherently enhanced positioning of the vehicle, as well as capability to provide method for behavior analysis of the vehicle. Proposed method of operation being executed in cloud allows fleet management individual and sub-group behavior analysis, combined with ability of emergency related activities, as well as charging, remote system control and maintainance. Proposed solution is addressing apparatus and method of operation allowing “pay HOW your drive” vehicle operation.

Claims

1. A telematics system comprising T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000)

where T-Box (1000) contains

An inertial unit (200), containing MEMS or NEMS based 3D inertial sensors (210) including 3D gyroscope functionality (210)

A long range wireless communication unit (120)

A global navigation satellite (GNSS) system unit (110)

A processing and a control unit (130)

A memory (310)

where Back End (2000) is a virtual processing entity, being realized on remote servers and being connected internally and externally by an IP network and containing:

A virtual processing entity (2500), which itself comprises;

a) A Graphic Machine with Human Machine Interface with Map Content (2400)

b) A Virtual Vehicle Data Base (2200)

c) A Virtual Group of the Vehicle Data Base (2300)

A WEB Interface related to the System Operations (2110)

A WEB Interface related to the Supervision &

Control Unit (2120)

A Gateway to long range wireless network systems, over which the entity (120) of T-Box (1000) may be accessed

where applied Method of operation (10000) comprises activities related to T-Box (11000) and to activities related to Back End (12000), whereby following activities are executed in scope of (11000);

A Calculation of Real Time Position Data (11100), where the inertial unit (200) data is used and processed

A Calculation of Real Time Vector Trajectory of the Vehicle (11200)

A Calculation of Event Detection (11400), where Event is defined as a plurality of specific dynamic sets of parameters achieved by a vehicle during a specified time period of observation, and where dynamic sets of parameters are related to vector values of speed, acceleration, external and internal forces, as well as to their changes, and statistical appearances over specified time

A Calculation of Behavior of the Driver &

Vehicle (11300) by statically processing data related to vehicle dynamics and specified detected Events (11400), or combinations of events

A Calculation of Vector Trajectory of a Vehicle after specific Event has happened (11500), where the vehicle dynamics data, processed by a processor (130) and stored in the memory (310), is used for a reconstruction of the vehicle trajectory before Event occurrence.

whereby the executed activities in the scope of (12000) are

“

Back End Event Actions”

(12200), registering in a date base the event related information;

event art, time stamp, geographical position, vector acceleration information, vector velocity information and system action on registered event art

“

Event Report Preparation and Handling”

(12300), issuing a computer program readable document containing a graphical print out of locations where events happened, combined with event art, time stamp, geographical position, vector acceleration information, vector velocity information and system action on registered event art

“

Location based Visualization System”

(12400) where via WEB server interface a position of a vehicle, its identification, acceleration vector and velocity vector are observed over the geographical map, as well as related icons to permiting an access to associated event reports and statistical behavior information

“

Vehicle Data Base Processing”

(12500), statistically calculating a vehicle behavior, by entering new data and comparing its behavior with a referent vehicle category group behavior based on statistical data of more vehicles

“

Fleet Data Base Processing”

(12600), statistically calculating a vehicle category group behavior by entering data from vehicle being categorized as a member of a group

“

System Control &

System Settings &

T-Box Updates (12900), executed via WEB server interface software which allows for updates of the T-Box (1000) and control orders to T-Box (1000) functional blocks

where proposed apparatus (1000) and back end (2000) are realized by plurality of the technologies

where proposed Method of Operation (100000) is executed by plurality of the execution approaches for each proposed activity within proposed Method of Operation activities (11000) and (12000).

2. Telematics system comprising T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in claim 1 with

an inclusion of a short range wireless connectivity (320) in the T-Box (1000), by the plurality of the short range wireless technologies, and by the plurality of the realization.

3. Telematics system comprising T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in claim 1 with

inclusion of an entity providing connection or provision of additional (non inertial) sensors, (330) in the T-Box (1000), by the plurality of the sensor functions, and by the plurality of its realization.

4. Telematics system comprising:

T-Box (1000) apparatus and Back End Functionality (2000), and Method of Operation (10000) described in claim 1 with

inclusion of an entity, providing a microphone functionality (340) in the T-Box (1000), by the plurality of the realization.

5. Telematics system comprising T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in claim 1 with

inclusion of an entity, providing speaker functionality (350) in the T-Box (1000), by the plurality of the realization.

6. Telematics system comprising T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in claim 1 with

an inclusion of an entity, providing a wired connection to the vehicle &

the driver, (340) in the T-Box (1000), by the plurality of the physical interfaces, communication protocols, and by the plurality of realizations.

7. Telematics system comprising T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in previous Claims with Method of operation activities (11400) related to Event detection, where also Environment related influences are additionally used for the Event detection, by the plurality of the Environmental influences, where the environmental influences are at least one of the following:

Rain Detection

Rain Intensity

Snow Detection

Snow Intensity

Wind Detection

Wind Intensity

Temperature Level

Humidity Level

Air quality sensor levels (related to CO2)

Air quality sensor levels (related to dust particle density)

Air quality sensor levels (related to gases, without CO2)

8. Telematics system comprising T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in claims 1 to 6 with Method of operation activities (11400) related to Event detection, where also Driver Related influences are used additionally for the Event detection, by the plurality of the Driver influences, where the driver related influences are at least one of the following influences:

Driving in a specific geographical area

Driving in a specific geographical area during specific period of a day

Driver average behavior from the past

Driver age

Driver audio commands placed towards the vehicle

Driver gestures

Driver face

Driver actions related to pressing mechanical buttons

Change of driver positions within the car during driving

9. Telematics system comprising T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in claim 1 with Method of operation activities (11300) related to Behavior of the Driver &

the Vehicle, where Environment related influences during specific time of observation with a specified duration are used additionally for the Behavior of the Driver &

the Vehicle (11300) calculations, by the plurality of the Environmental influences, where the environmental influences are at least one of the following;

Rain Detection

Rain Intensity

Snow Detection

Snow Intensity

Wind Detection

Wind Intensity

Temperature Level

Humidity Level

Air quality sensor levels (related to CO2)

Air quality sensor levels (related to dust particle density)

Air quality sensor levels (related to gases, without CO2)

10. Telematics system comprising T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in claim 1 with Method of operation activities (11300) related to Behavior of the Driver &

Vehicle, where also Environment related influences during specific time of observation with a specified duration are used additionally for the Behavior of the Driver &

Vehicle (11300) calculations, by the plurality of the Environmental influences, where the environmental influences are at least one of the following;

Driving in a specific geographical area

Driving in a specific geographical area during specified period of a day

Driver average behavior from the past

Driver age

Driver audio commands placed towards the vehicle

Driver gestures

Driver face

Driver actions of pressing mechanical buttons

Change of driver positions with the car during driving

11. Telematics system comprising T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in previous claims where Method of operation activities (11400) containing “

stability events”

(11410) detection are further specified as “

Roll-over”

Event detection (11411) being calculated in a way that;

a predefined time window “

Time Window 1”

is set

a predefined time window “

Time Window 2”

is set to be greater than “

Time Window 1”

a predefined time window “

Time Window 3”

is set

a predefined time window “

Time Window 4”

is set to be smaller than “

Time Window 3”

a predefined acceleration threshold “

Acceleration threshold 1”

is set

a predefined acceleration threshold “

Acceleration threshold 2”

is set to be smaller in magnitude than “

Acceleration threshold 1”

a predefined acceleration threshold 3 “

Acceleration threshold 3”

is set to be smaller in magnitude than “

Acceleration threshold 2”

but smaller than 0 m/ŝ

2

an average acceleration at Z-Axis (perpendicular to the driving surface) “

az average 1”

is observed within “

Time Window 1”

an average acceleration at Z-Axis (perpendicular to the driving surface) “

az average 2”

is observed within “

Time Window 2”

A variance of acceleration vector “

acceleration variance”

is observed within “

Time Window 4”

if the “

az average 1”

is larger than “

Acceleration threshold 1”

an event is detected

if the “

az average 1”

is not larger than “

Acceleration threshold 1”

it is checked if the “

az average 2”

is larger than “

Acceleration threshold 2” and

if so an event is detected

if and when an event is detected start a watchdog timer “

time counter”

if an event is detected check if the “

acceleration variance”

is smaller than “

Acceleration threshold 3”

or “

time counter”

exceeds “

Time Window 3”

, and if so, send full roll-over report including estimate of angles in final position by measuring gravity components on all accelerometer axes

12. Telematics system comprising T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in previous claim, where Method of operation activities (11400) containing “

stability events”

(11410) detection is further specified as Roll-over”

Event detection (11411) where

“

Time Window 1”

is larger than 0.2 s

“

Time Window 2”

is larger than 1 s

“

Time Window 3”

is larger than 2 s

“

Time Window 4”

is larger than 0.5 s

“

Acceleration threshold 1”

is larger in magnitude than 0.4 g, where g is 9.81 m/s2

“

Acceleration threshold 2”

is smaller in magnitude than 0.1 g, where g is 9.81 m/s2

“

Acceleration threshold 3”

is smaller in magnitude than 0.08 g, where g is 9.81 m/s2

13. Telematics system comprising T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in claims 1 to 8 where Method of operation activities (11400) containing “

stability events”

(11410) detection is further specified as Pitch”

Event detection (11412)

Being calculated in a way that

A threshold “

threshold pitch”

is set [in degrees]

A value for integration time “

Integration time”

is set

A value of “

angular velocity”

is integrated over the “

integration time”

resulting in a value called “

change of pitch angle”

If the absolute value of “

change of pitch angle”

is larger than “

threshold pitch”

the event is detected.

14. Telematics system comprising T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described with claim 13 where Method of operation activities (11400) containing “

stability events”

(11410) detection is further specified as Pitch”

Event detection (11412)

Where “

threshold pitch”

is larger than 5 degrees

Integration time is larger than 0.4 sec

15. Telematics system comprising T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in claims 1 to 8 where Method of operation activities (11400) containing “

stability events”

(11410) detection is further specified as “

Under Steering &

Over Steering”

Event detection (11415)

Being calculated in a way that

a value for observation time window “

observation window 1”

is set

a value for acceleration threshold “

acceleration threshold 1”

is set

a value for threshold “

understeering threshold”

is set

a value for velocity threshold “

velocity threshold”

is set

“

Lateral acceleration”

is defined as an acceleration component perpendicular to the direction of driving during a specified time increment

“

Averaged lateral acceleration”

is calculated as “

lateral acceleration”

averaged over the “

observation window 1”

time

“

Averaged yaw rate”

is calculated as “

angular rate”

measured on axis orthogonal to vehicle plane and averaged over the “

observation window 1”

time

“

directional velocity estimate”

is defined as a velocity component in the direction of the movement

“

lateral acceleration estimate”

is calculated as “

averaged yaw rate”

multiplied with “

directional velocity estimate”

It is checked if the absolute value of “

averaged lateral acceleration”

is larger than “

acceleration threshold 1” and

if so, then “

average lateral acceleration”

component is deducted from “

lateral acceleration estimate”

, then it is checked if this number is larger than “

understeering threshold”

, and if so, it is checked if vehicle velocity at that moment is larger than “

velocity threshold”

, if so an event is detected.

16. Telematics system comprising T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in claim 15 where Method of operation activities (11400) containing “

stability events”

(11410) detection is further specified as “

Under Steering &

Over Steering”

Event detection (11415)

Being calculated in a way that

“

observation window 1”

is smaller than 1 s.

“

acceleration threshold 1”

is larger than 0.4 g, where g=9.81 m/s2

“

understeering threshold”

is larger than 0.4 g, where g=9.81 m/s2

“

velocity threshold”

is larger than 8 m/s

17. Telematics system comprising T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in claims 1 to 8 where Method of operation activities (11400) containing “

road type and vibration monitoring”

events (11420) detection is further specified as “

On Road &

Off Road Usage”

Event detection (11421)

Being calculated in a way that

a value for time window “

observation window1”

is set

a value for time window “

observation window2”

is set

a value for “

slope”

is set according to vehicle speed

a value for “

starting vibrations”

is set

“

Road type threshold”

is calculated by multiplying “

starting vibrations”

with “

slope”

“

Acceleration variance”

is calculated as a variance of acceleration vector over “

observation window1”

the calculated “

Acceleration variance”

is compared to “

Road type threshold” and

if it exceeds the value of a threshold over “

observation window2”

then an event of off-road usage is detected.

18. Telematics system comprising T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in previous claim where Method of operation activities (11400) containing “

road type and vibration monitoring”

events (11420) detection is further specified as “

On Road &

Off Road Usage”

Event detection (11421)

Being calculated in a way that

“

observation window 1”

is greater than 1 s.

“

observation window 2”

is greater than 10 s.

“

Slope”

is below 1 if vehicle speed is below 40 km/h

“

Slope”

is between 1 and 2 if vehicle speed is between 40 km/h and 100 km/h

“

Slope”

is above 2 if vehicle speed is above 100 km/h

“

starting vibrations”

is greater than 0.3 m/s2 and below 3 m/s2.

19. Telematics system comprising:

T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in claims 1 to 8 where Method of operation activities (11400) containing “

road type and vibration monitoring”

events (11420) detection is further specified as “

Moderate risk of back disorders”

Event detection (11422) and “

High risk of back disorders”

Event detection (11423)

Being calculated in a way that

a value of “

Exposure Action Value”

is set

a value of “

Exposure Limit Value”

is set

Peak values of acceleration between two zero crossings are identified for each of the accelerometer axes and are stored as “

acceleration peaks”

Each of the “

acceleration peaks”

is raised by power of six and stored as “

acceleration peaks to the power six”

“

acceleration dose”

is calculated as the sixth root of the sum of all the acceleration peaks being powered to six, from “

acceleration peaks to the power six”

found on interval of interest

a duration of daily exposure to vibrations is monitored and stored as “

duration of daily exposure”

For each day, duration of daily exposure is divided by the time duration over which the “

acceleration dose”

of each of the accelerometer axis is monitored and these daily values are summed up. The sixth root of this sum represents “

average daily dose” and

it is calculated for each axis.

“

Scale factor”

is defined for each of the axis

“

Acceleration dose”

for each axis of accelerometer is multiplied by a corresponding “

scale factor” and

raised to the sixth power and results for all three axis is sumed up and after their addition, the sixth root of the sum is calculated, defining the “

equivalent static compressive stress”

“

Average daily dose”

for each axis of accelerometer is multiplied by a corresponding “

scale factor” and

raised to the sixth and results for all three axis is summed up and after addition the sixth root of the summary defines “

daily equivalent static compressive dose”

If “

daily equivalent static compressive dose”

exceeds “

Exposure Action Value”

an event of “

Moderate risk of back disorders”

(11422) is detected

If “

daily equivalent static compressive dose”

exceeds “

Exposure Limit Value”

an event of “

High risk of back disorders”

(11423) is detected.

20. Telematics system comprising T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in previous claim, where Method of operation activities (11400) containing “

road type and vibration monitoring”

events (11420) detection is further specified as “

Acceleration Dose”

Event detection (11422) where;

The value of “

Exposure Action Value”

is set to 0.5 MPa

The value of “

Exposure Limit Value”

is set to 0.8 MPa

The value of “

scale factor”

is larger than 0.1

21. Telematics system comprising T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in claims 1 to 8 where Method of operation activities (11400) containing “

Crash”

events (11430) detection is further specified as “

Non Severe Crash”

Event detection (11424)

Being calculated in a way that

a value for observation time window “

Observation Window 1”

is set

a value of “

short-term delta velocity”

is calculated by integrating the value of acceleration vector over “

Observation Window 1”

a value of “

crash end threshold”

is set

Simultaneously the “

Principal Direction of the Force;

PDOF”

is calculated, being defined as an angle of force in horizontal and vertical plane, relative to the vehicle frame, by the calculation of the argument of “

Short-term delta velocity”

“

Normalization factor”

is set of pre-defined scalar values determined depending on PDOF (in both horizontal and vertical planes) for each of accelerometer components

“

Normalized short-term delta velocity”

is calculated by multiplying “

Short-term delta velocity”

by a pre defined “

Normalization factor”

matched to calculated PDOF at a moment

If the absolute value of “

Normalized short-term delta velocity”

is larger than 1, the an event of “

generalized crash”

is detected, and PDOF calculated at that very moment is “

Crash PDOF”

, while “

Normalization factor”

valid at that moment is “

Crash normalization factor”

The timer started to measure the duration of the “

Generalized crash”

event

“

Normalized accelerometer vector”

is calculated by multiplying acceleration vector components by “

Crash normalization factor”

values, related to specific vector component

Value of “

normalized short-term delta velocity”

is further calculated by integrating the value of “

normalized acceleration vector”

over “

Observation Window 1” and

if the absolute value becomes smaller than “

Crash end threshold”

, the end of “

generalized crash event”

is detected

“

Crash delta velocity”

vector is calculated by integrating “

Normalized accelerometer vector”

over duration of crash event

“

Severe threshold”

value is set, which is required not be surpassed to declare the crash as non-severe

“

Crash delta velocity”

is compared to “

Severe threshold” and

if it is not surpassed “

Non-severe crash”

is detected.

22. Telematics system comprising T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in claims 1 to 8 Method of operation activities (11400) containing “

Crash”

events (11430) detection is further specified as

“

Severe Crash”

Event detection (11431)

Being calculated in a way that

a value for observation time window “

Observation Window 1”

is set

a value of “

short-term delta velocity”

is calculated by integrating value of acceleration vector over “

Observation Window 1”

a value of “

Crash end threshold”

is set

“

Severe threshold”

value is set, which is required to be surpassed to declare the crash as severe

Simultaneously, the “

Principal Direction of the Force;

PDOF”

is calculated, being defined as an angle of force in horizontal and vertical planes, relative to the vehicle frame, by the calculation of the argument of “

short-term delta velocity”

“

Normalization factor”

is set of pre-defined scalar values determined depending on PDOF (in both horizontal and vertical plane) for each of the accelerometer components

“

Normalized short-term delta velocity”

is calculated by multiplying “

Short-term delta velocity”

by pre defined “

Normalization factor”

matched to the calculated PDOF at a moment

If the absolute value of “

Normalized short-term delta velocity”

is larger than 1, the event of “

generalized crash”

is detected and PDOF calculated in that very moment is “

crash PDOF”

, while “

Normalization factor”

valid at that moment is “

Crash Normalization factor”

The timer is started to measure the duration of the “

Generalized crash”

event

“

Normalized accelerometer vector”

is calculated by multiplying the acceleration vector components by “

Crash Normalization factor”

components

Value of “

normalized short-term delta velocity”

is further calculated by integrating the value of “

Normalized acceleration vector”

over “

Observation Window 1” and

the if the absolute value becomes smaller than “

Crash end threshold”

, the end of generalized crash event is detected

“

Crash delta velocity”

vector is calculated by integrating “

Normalized accelerometer vector”

over duration of a crash event

“

Crash delta velocity”

is compared to “

Severe threshold” and

if it is surpassed a “

severe crash”

is detected.

23. Telematics system comprising T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in claims 21 and 22 where Method of operation activities (11400) containing “

Crash”

events (11430) detection is further specified as “

Severe Crash”

Event detection (11431) where

“

Severe threshold”

is measured by abbreviated injury Scale (MAIS), having grades from 0 to 7, where the threshold of determining severe and non severe crashes is set to the value of 3, where all crashes in the scale with mark 3 and larger are claimed as severe crashes, and all crashed below mark 3 as non-severe crashes.

A value for the threshold “

Severe crash probability 75+”

is set

If “

Crash delta velocity”

surpasses the “

Severe crash probability 75+”

then the probability that a severe crash is more severe than MATS 3 crash grade is higher than 75%

If “

Crash delta velocity”

does not achieve “

Severe crash probability 75+”

then the probability that a severe crash is more severe than MAIS 3 crash grade is linearly in between 25% and 75%, whereas 25% is a lowest detectable “

Severe crash”

event (“

Crash delta velocity”

=“

Crash threshold”

)

24. Telematics system comprising T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in claims 21 to 23 where Method of operation activities (11400) containing “

Crash”

events (11400) detection is further specified in a way that

In a case of a detection of multiple crash events during short time period or a detection of roll-over event, a final “

Crash delta velocity”

as calculated in claims 21-23 should be scaled with “

statistic factor”

that not lower than 1.2

25. Telematics system comprising T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in claims 1 to 8 where Method of operation activities (11400) containing “

Driver related events”

(11440) detection is further specified as “

Driving under influence”

Event detection (11441)

Being calculated in a way that;

a profile of a vehicle &

a driver typical behavior is available (11300), and has been calculated statistically in the past, including events profile relevant to driver behavior during specific hours, which is reflected in number Ro (behavior risk), where Ro can take values greater than and equal to zero, where zero means no specific risks

a specific age risk factor is set and numerically expressed as R1, where R1 can take values greater than and equal to zero, where zero means no specific risks

a specific past related risk factor, relevant to driving under the influence in the past is set and numerically expressed as R2, where R2 can take values greater than or equal to zero, where zero means no specific risks

a specific past related risk factor relevant to the public fee register is set and numerically expressed as R3, where R3 make take values greater than or equal to zero, where zero means no specific risks

a specific insurance related risk factor relavant to the insurance company internal rules is set and numerically expressed as R4, where R4 can take values greater than or equal to zero, where zero means no specific risks

a specific observation time “

time window 1”

is set

a specific acceleration threshold for detection of sub-event “

harsh braking”

is set

a specific acceleration threshold for detection of sub-event “

fast acceleration”

is set

a specific “

fast cornering”

threshold for detection of sub-event “

abrupt changing of the driving direction”

is set

a specific number “

importance factor fatigue”

is set, to be multiplied with an occurrence of the detected event “

fatigue”

during specifically defined observation time “

time window 1”

, to express the importance of the specific sub-event, where numbers greater than zero are used and where number zero means no importance

a specific number “

importance factor slide slip”

is set, to be multiplied with an occurrence of the detected event “

slide slip”

during specifically defined observation time “

time window 1”

, to express the importance of the specific sub-event, where numbers greater than zero are used, and where number zero means no importance

a specific number “

importance factor spinning”

is set, to be multiplied with an occurrence of the detected event “

spinning”

during specifically defined observation time “

time window 1”

, to express the importance of the specific sub-event, where numbers greater than zero are used, and where number zero means no importance

a specific number “

importance harsh braking”

is set, to be multiplied with an occurrence of the detected event “

harsh braking”

during specifically defined observation time “

time window 1”

, to express the importance of the specific sub-event, where numbers greater than zero are used, and where number zero means no importance

a specific number “

importance fast acceleration”

is set, to be multiplied with an occurrence of the detected event “

fast acceleration”

during specifically defined observation time “

time window 1”

, to express the importance of the specific sub-event, where numbers greater than zero are used, and where number zero means no importance

a specific number “

importance fast turning”

is set, to be multiplied with an occurrence of the detected event “

fast turning”

during specifically defined observation time “

time window 1”

, to express the importance of the specific sub-event, where numbers greater than zero are used, and where number zero means no importance

a specific number “

importance of geographical area”

is set, to be used for scoring of “

being in the specific geographical area”

during specifically defined observation time “

time window 1”

, where numbers greater than zero are used, and where number zero means no importance of the geographical area

a specific number “

importance of environment”

is set, to be used for scoring of “

being under the influence of specific weather conditions”

during specifically defined observation time “

time window 1”

, where numbers greater than zero are used, and where number zero means no importance of the specific weather conditions

a specific number “

importance of traffic”

is set, to be used for scoring of “

being under the influence of specific traffic conditions”

during specifically defined observation time “

time window 1”

, where numbers greater than zero are used, and where number zero means no importance of the specific traffic conditions

“

driving under the influence score threshold”

is set, which is a positive number, and when the number is smaller the detection probability of an event is greater, or the score required to detect the event driving under influence is smaller

In the predefined “

time window 1”

, a number of the occurrence of events;

driving under fatigue, slide slip, spinning, harsh braking, fast acceleration, fast turning is calculated by detection of these events using T-Box (1000)

“

Driving score”

is calculated as a sum of;

Ro+R1+R2+R3+R4+

30 “

importance factor fatigue”

* number of occurrences of event “

fatigue”

during “

time window 1”

,+

+ “

importance factor slide slip”

* number of occurrences of event “

side slip”

during “

time window 1”

,+

+ “

importance factor spinning”

* number of occurrences of event “

spinning”

during “

time window 1”

,+

+ “

importance factor fast braking”

* number of occurrences of event “

fast braking”

during “

time window 1”

,+

+ “

importance factor fast acceleration”

* number of occurrences of event “

fast acceleration”

during “

time window 1”

,+

+ “

importance factor fast turning”

* number of occurrences of event “

fast turning”

during “

time window 1”

,+

+ “

importance of geographical area”

+

+ “

importance of environment”

+

+ “

importance of traffic”

If “

Driving score”

is equal or greater than “

driving under influence score threshold”

the event “

driving under influence”

is detected.

26. Telematics system comprising T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in claims 1 to 8 where Method of operation activities (11400) containing “

Driver related events”

(11440) detection is further specified as “

Driving fatigue”

Event detection (11441)

Being calculated in a way that;

“

moving average window”

is set

“

observation window 1”

is set

“

observation window 2”

is set

“

observation window 3”

is set

“

observation window 4”

is set

“

absolute value of acceleration threshold”

is set

“

vehicle speed threshold”

is set

“

angle threshold fatigue”

is set

“

angle threshold correction”

is set

a moving average of acceleration on X-axis (longitudinal to vehicle) “

ax average”

is observed within the “

moving average window”

if the absolute value of “

ax average”

is not greater than the “

absolute value of acceleration threshold” and

if the velocity of the vehicle is greaten than “

vehicle speed threshold” and

if the change of vehicle heading angle as calculated by T-Box (1000) within “

observation window 2”

is less than “

angle threshold”

than the new “

observation window 3”

is started where a sudden and opposite (during the observation window 4) change of vehicle heading is observed, with angle change greater than “

angle threshold correction”

, and if the sudden and opposite change of vehicle heading happens, the event fatigue is detected.

if the vehicle heading angle change as calculated by T-Box (1000) within “

observation window 2”

is less than “

angle threshold”

than the new “

observation window 3”

is started where the sudden and opposite change (within the duration of the observation window 3) of vehicle heading is observed, with an angle change greater than “

angle threshold correction”

, and if the sudden and opposite change of vehicle heading happens, the event fatigue is detected.

During the “

observation window 1”

, the constant acceleration of the vehicle is observed under “

Absolute value of acceleration threshold” and

if the velocity of the vehicle is greater than “

vehicle speed threshold” and

if the vehicle heading angle change as calculated by T-Box (1000) during “

observation window 2”

is less than “

angle threshold”

than the new “

observation window 3”

is started where the sudden and opposite change (within the duration of the observation window 3) of vehicle heading is observed, with angle change greater than “

angle threshold correction”

, and if the sudden and opposite change of vehicle heading happens, the event fatigue is detected.

27. Telematics system comprising T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in claims 25 where Method of operation activities (11400) containing “

Driver related events”

(11440) detection is further specified as “

Driving fatigue”

Event detection (11441)

Being calculated in a way that

“

moving average window”

is less than 1 s

“

observation window 1”

is longer than 5 s

“

observation window 2”

is longer than 5 s

“

observation window 3”

is longer than 5 s

“

observation window 4”

is shorter than 0.3 sec

“

Absolute value of acceleration threshold”

is lower than 0.05 g, where “

g”

is 9.81 m/s2

“

vehicle speed threshold”

is greater than 10 m/s

“

angle threshold fatigue”

is smaller than 5 degrees

“

angle threshold correction”

is greater than 10 degrees

28. Telematics system comprising T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in claims 1 to 8 where Method of operation activities (11500) containing “

Post-event calculation of vehicle vector trajectory”

(11500) is comprising “

Estimating sensor error model”

(11510) method

Being calculated in a way that;

“

inertial sensor data set”

is available as data output gathered from accelerometers, gyroscopes, as well as from magnetometers and temperature sensors

“

external sensor data set”

is available as data output gathered from Global navigation satellite system (GNSS) unit (110) (including latitude, longitude, heading, as well as altitude and dilution of precision) and optionally data from vehicle odometer such as speed.

“

sensor data set”

is available as composite information made out of “

inertial sensor data set” and

“

external sensor data set”

where “

Sensor error model”

is being calculated in a way that;

“

Final vehicle state”

is available as a set of data consisting of vehicle position (geographic latitude, longitude and optionally altitude), vehicle attitude (roll, pitch and heading angle) and time.

“

Predicted vehicle state”

is available as a set of data consisting of vehicle position (geographic latitude, longitude and optionally altitude), vehicle attitude (roll, pitch and heading angle), vehicle speed vector and time, whereby the starting values for “

predicted vehicle state”

are available using recent inertial sensor measurements.

“

Inertial sensor data set”

is recorded to a circular buffer

New “

inertial sensor data set”

is calculated by compensating “

inertial sensor data set”

using values set in “

sensor error model”

Current “

predicted vehicle state” and

“

inertial sensor data set”

are used to estimate a new “

predicted vehicle state”

by applying a known strap-down integrated navigation system apparatus and by solving navigation equations and known coordinate frame transformations.

If new measurements from “

external data set”

are available “

innovation”

is calculated as a difference between measurements from “

external data set” and

“

predicted vehicle state”

“

Innovation”

, “

external sensor data set” and

“

predicted vehicle state”

are used to correct the “

sensor error model”

by applying one of the known apparatuses such as linear or non-linear estimators by plurality of the approaches.

“

Predicted vehicle state”

is updated according to “

external sensor data set”

measurements. (step “

correction”

)

29. Telematics system comprising T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in claims 1 to 8 and in claim 27 where Method of operation activities (11500) containing “

Post-event calculation of vehicle vector trajectory”

(11500) is comprising “

Crash trajectory reconstruction”

(11520) method

“

sensor error model T0”

is available as “

sensor error model”

obtained at moment T0.

value of “

Interval 0”

is set as a time duration, value starting with T(minus1) and ending with T0, being “

Pre-Crash Interval”

“

Interval 2”

as a time duration is set, with the starting value T1 and ending value T2, being “

Post-Crash Interval”

“

Interval 1”

as a time duration is set, with the starting value TO and ending value T1, being “

Crash Interval”

“

Interval 3”

as a time duration is set

“

Crash trajectory reconstruction”

is being calculated in a way that;

“

inertial sensor data set”

stored in a circular buffer for the whole duration of a crash is compensated using “

sensor error model T0”

before the crash and after the crash and resulting updated “

inertial sensor data set”

is stored to the memory

“

Averaged global positioning satellite system unit (110) position”

is calculated as an average of GPS positions from “

external sensor data set”

over interval 3.

“

Averaged acceleration vector”

is calculated as an average of accelerometer data from “

inertial sensor data set”

over “

Interval 3”

.

“

Final roll” and

“

Final pitch”

angles (defined according to the navigation frame convention) are calculated using trigonometry and “

averaged acceleration vector”

“

Averaged final heading”

is calculated as an average of magnetometer heading data from “

inertial sensor data set”

over “

Interval 3”

.

“

Final vehicle state”

is calculated from “

Averaged global positioning satellite system unit (110) position”

, “

final pitch”

, “

final roll” and

“

averaged final heading”

Method is further executed by using a “

Final vehicle state”

as initial condition in execution of an inverse kinematics trajectory calculation, wherein following steps are executed;

Stored “

inertial sensor data set”

is integrated in the reverse order over the interval T2==>

T1 (interval 2) using plurality of the methods and the “

Final vehicle state T1”

is obtained.

By using “

Final vehicle state T1”

as starting a state, stored “

inertial sensor data set”

is integrated in the reverse order over interval T1==>

T0 (interval 1) using plurality of the methods and “

Final vehicle state TO”

is obtained.

By using “

Final vehicle state T0”

as starting state, stored “

inertial sensor data set”

is integrated in the reverse order over interval T0==>

Tminus1 (interval 0) using plurality of the methods and “

Final vehicle state Tminus1”

is obtained.

30. Telematics system comprising T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in claim 28 where Method of operation activities (11500) containing “

Post-event calculation of vehicle vector trajectory”

(11500) is comprising “

Crash trajectory reconstruction”

(11520) method where

“

Averaged global positioning satellite system unit (110) position” and

“

averaged final heading”

are improved by a collection of data obtained by an expert witness.

31. Telematics system comprising T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in claim 28 where Method of operation activities (11500) containing “

Post-event calculation of vehicle vector trajectory”

(11500) is comprising “

Crash trajectory reconstruction”

(11520) method where

“

Averaged global positioning satellite system unit (110) position” and

“

averaged final heading”

are improved by a collection of data obtained by external measurements.

32. Telematics system comprising T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in claims 1 to 26 with inclusion of the activities within Method of operation (11000):

“

Event Warning to Vehicle System (Driver) (11600), where the T-Box (1000) is issuing warnings by the plurality of the means (audio, video, belt fasting) to the driver, in the case when

a detected Event has occurred, by plurality of the Event manifestations

a combination of detected Events has occurred, by the plurality of the combinations of at least two Events

a related specific pre-defined statistics of an appearance of a specific Event or of a Group of Events has occurred, by plurality of the detected Events

whereby the driver is addressed by an interface entity (320) or (340).

33. Telematics system comprising T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in claims 1 to 26 with inclusion of the activities within Method of operation (11000):

“

Pre-Event Warning to Vehicle System (Driver)”

(11600), where the T-Box (1000) is issuing warnings by the plurality of the means (audio, video, belt fasting) to the driver, in the case of a detected Event, or a set of Events by plurality of the Events that may happen in the future,

whereby the driver is addressed by an interface entity (320) or (340)

whereby the decision to issue an alert is based on the processing of past information based on;

occurred detected Event, by plurality of the Event manifestations

occurred combination of detected Events, by the plurality of combinations of at least two Events

occurred relevant specific pre-defined statistics of appearance of specific Event or Group of Events, by plurality of the detected Events

inputs from environment sensors

position of the vehicle

34. Telematics system comprising T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in claims 1 to 26 with an inclusion of the activities within Method of operation (11000):

“

Encryption and Multimedia Compressions”

(11700), where the T-Box (1000) is executing data encryption by the plurality of the encryption solutions and deepness of the keying in the processor unit (130).

35. Telematics system comprising T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in claims 1 to 26 with an inclusion of the activities within Method of operation (11000):

“

Encryption and Multimedia Compressions (11700), where the T-Box (1000) is executing multimedia data compression by the plurality of the multimedia data compression in the processor unit (130).

36. Telematics system comprising T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in claims 1 to 26 with an inclusion of the activities within Method of operation (11700) being related to video capture action step activities:

(11710, 11711, 11712, 11713, 11714), where Control System of the T-Box (1000) executed in T-Box processor unit (130), is initiating and enabling activity of the Video capture procedure, depending on at least one of the procedures

a) a regular time frame assigned activity of video capturing

b) a detected pre defined driving related Event

c) a detected pre defined Sensor Input through (330) entity

d) a driver wish, typically initiated by (320) entity

37. Telematics system comprising T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in claims 1 to 26 with an inclusion of the activities within Method of operation (11700) being related to audio capture action step activities:

(11720, 11721, 11722, 11723, 11724), where Control System of the T-Box (1000) executed in T-Box processor unit (130) is initiating and enabling activity of the Audio capture procedure, depending on at least one of the procedures

a) a regular time frame assigned activity of audio capturing

b) a detected pre defined driving related Event

c) a detected pre defined Sensor Input through (330) entity

d) a driver wish, typically initiated by (320) entity

38. Telematics system comprising T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in claims 1 to 26, with an inclusion of the activities within Method of operation (11000):

“

Initialization of Event related Alerts”

(11800), where the T-Box (1000) is initiating alerts to “

out of the vehicle”

world through an entity (120), whereby the alerts are issued upon;

occurring detected Event, by plurality of the Event

occurring combination of detected Events, by the plurality of the combinations of at least two Events

occurring relevant specific pre-defined statistics of an appearance of a specific Event or Group of Events, by plurality of the detected Events

39. Telematics system comprising T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in previous Claims, where the Back End functionality (2000) comprises additionally the Network Interface to external Charging Systems (2140), by the plurality of realization.

40. Telematics system comprising T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in previous Claims where the Back End functionality (2000) comprises additionally the Network Interface to external Charging Systems (2140), is a charging system of the long range wireless network service provider.

41. Telematics system comprising T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in claims 1 to 37, where the Back End functionality (2000) compromises additionally the Network Interface to External Data Base Systems (2130) by the plurality of the realization.

42. Telematics system comprising T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in previous claim 40 where the Back End functionality (2000) compromises additionally the Network Interface to External Data Base Systems (2130), where the external data base system is external data base system of the insurance company being SAP System.

43. Telematics system comprising T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in claim 40 where the Back End functionality (2000) compromises additionally the Network Interface to External Data Base Systems (2130), where the external data base system is external data base system of the insurance company being Oracle System.

44. Telematics system comprising T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in claims 1 to 37, where the Back End functionality (2000) compromises additionally WEB user Interface dedicated to the Users (2100) allowing personalized access to the proposed System, where the access rights are granted through WEB interfaces (2120) dedicated to supervision and Control (2120).

45. Telematics system comprising T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in claims 1 to 37, where the Back End functionality (2000) has in the scope of entity (2500) Charging Calculation functionality (2600), being realized by the plurality of the realizations, using information form entity (2200).

46. Telematics system comprising T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in claims 1 to 37, where the Method of operation activities (12000) are additionally supplemented by Method of operation “

Back End Alert Actions”

(12100), being realized by the plurality of the approaches, using information available from entities (2200) and (2300), being enriched by information coming from T-Box (100) related to pre defined events, whereby security organization networks are addressed (12110).

47. Telematics system comprising T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in claim 45, where the Method of operation activities (12000) are additionally expanded by Method of operation “

Back End Alert Actions”

(12100), being realized by the plurality of the approaches, using information available from entities (2200) and (2300) and being enriched by information coming from T-Box (100) related to pre defined events, whereby health &

emergency organization networks are addressed (12120).

48. Telematics system comprising T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in claims 1 to 37, where the Method of operation activities (12000) are additionally supplemented by Method of operation “

Back End Alert Actions”

(12100), being realized by the plurality of the approaches, using information available from entities (2200) and (2300) and being enriched by information coming from T-Box (100) related to pre defined events, whereby vehicle &

driver is addressed, (12130) and (12140).

49. Telematics system comprising T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in claims 1 to 37 and in claim 44, where the Method of operation activities (12000) are additionally supplemented by Method of operation “

Charging functionality”

(12700), being realized by the plurality of the approaches, using information available from entity (2600), whereby the calculated information from (2600) is prepared for charging users of the proposed system directly, by plurality means including explicitly credit card charging, debit card charging, billing through IP network, or dispatching of post printed paper bills.

50. Telematics system comprising T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in claims 1 to 37 and in claim 44, where the Method of operation activities (12000) are additionally supplemented by Method of operation “

Interface to the External Data Base Systems &

Charging Systems”

(12800), being realized by the plurality of the approaches and realizations, using information available from entity (2600), and preparing the data to be provided to Entity (2140) and (2130).

51. Method of Operation related to Service Company Business Model (20100), which is utilizing T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in claims 1 to 42,

where in addition to Tracking information of the vehicle, being accessible from WEB service at least one of innovative additional services are being provided to the system user:

SERVICE ITEM (20110) Vehicle Trajectory Report in case of pre defined event reports from (12200)

SERVICE ITEM (20120) Vehicle driving profiles based on statistics related to specific pre-defined events, being conceptually defined and calculated by the (11400), and processed by (11200), (12300), (12500) and (12600)

SERVICE ITEM (20130) Vehicle warning in case of pre defined events, being calculated by (11300)

SERVICE ITEM (20140) Commitment of automatically placing alerts to the vehicle according to (11600)

SERVICE ITEM (20150) Commitment of automatically placing alerts to the security and safety organizations according to (12100)

Where at least one of the following customers is addressed;

transportation fleets like;

vehicle leasing companies,

public fleets like school busses,

Taxi organizations,

logistics companies, like post delivery companies

organizations like chemistry-, oil-, steel-, mining-industry (with more than 100 vehicles in fleet)

organizations having own fleets, like emergency organization (fire protection, health), defense organizations, security organizations (police)

smaller enterprises (with smaller fleets under 100 vehicles)

private organizations, like “

worried parents organization” and

“

community kids tracking”

, being interested in tracking the cars of their kids to assess the specific pre-defined events by specific group of vehicles

private persons, with a need to have service for one or more vehicle

automotive national Clubs, for extending their services to drivers, by typically reselling the services from a Service company

Certification, Vehicle control as well as Automotive repair chain organizations, for extending their services to drivers by typically reselling the services from a Service Company

where charging is executed like;

upfront per vehicle payment (partially covering cost 1 for installation of the (1000) in the vehicle and partially covering cost 2 for T-Box (1000), where the partial coverage 1 and partial coverage 2 may vary from 0% to 100%)

payment for the services in more than one installment

52. Method of Operation related to Service provisions to Insurance Companies (20200), which is utilizing T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in claims 1 to 44,

where at least one of innovative additional services is offered:

SERVICE ITEM 1 (20210) Vehicle driving profiles based on statistics related to specific pre-defined events, being conceptually defined and calculated by the (11400), and processed by (11200), (12300), (12500) and (12600).

SERVICE ITEM 2 (20220) Vehicle Trajectory Report in case of the pre defined event reports, from (12200), where trajectory recovery and crash report in the case of the incident / crash is an essential and very valuable service provision.

SERVICE ITEM 3 (20230) Tracking information of the vehicle, being accessible from WEB service (state of the art), but due to newly proposed system (apparatus+method of operations) customer is obtaining AT LEAST one additional service like;

Commitment to automatically supply alerts to a vehicle according to (11600)

Commitment to automatically supply alerts to security and safety organizations according to (12100)

where charging to Insurance companies is executed like;

upfront payment partially covering cost 1 for installation of the (1000) in the vehicle and partially covering cost 2 for T-Box (1000), where the partial coverage 1 and partial coverage 2 may vary from 0% to 100%)

payment for the services in more than one installment

53. Method of Operation related to Service provisions for “

Traffic Organizations”

(20300), which is utilizing T-Box (1000) apparatus and Back End Functionality (2000) and Method of Operation (10000) described in claims 1 to 44,

where traffic organizations are one of the listed organisations;

Traffic organizations providing traffic regulation services

Traffic organizations providing traffic optimization services

Traffic organizations providing charging for used infrastructure in a specific geographical areas

where at least one of innovative additional services is offered;

SERVICE ITEM (20310) Cluster (more than one vehicles in the monitoring system) driving profiles based on statistics related to specific pre-defined events, being conceptually defined and calculated by the (11400) and processed by (11200), (12300), (12500) and (12600).

SERVICE ITEM (20320) Vehicle (individual) driving profiles based on statistics related to specific pre-defined events, being conceptually defined and calculated by the (11400) and processed by (11200), (12300), (12500) and (12600).

SERVICE ITEM (20330) Pre defined event reports, from (12200), where pre-defined events reports are used for “

Pay HOW you drive”

(related to payment per pre defined Event) business model, imposing that the service provider being in charge (a traffic regulatory company) is issuing the charges related to specific events.

SERVICE ITEM (20340) Tracking information of the vehicle, being accessible via WEB service (state of the art), but due to newly proposed system (apparatus+method of operations) traffic participants are advantageously obtaining additional features like;

automatically raising alerts to the vehicle according to (11600) if the traffic participants are violating the pre-defined rules in areas and/or if the specific events are important for participant security;

Automatically raising alerts to the security and safety organizations according to (12100) in a specific geographical area

where;

Traffic participant pays to “

Traffic Organization”

according the following options;

Specific regular (time) fees depending on the customer profile

Specific payments (fees and punishment fees) for the appearance of the pre-defined events on “

pay how you drive”

basis

where the “

Traffic Organization”

is paying typically fees in regular data intervals for using technology, services from general service providers, or paying in a manner of one time payment and providing services of the systems and its operation by its own stuff.