TISA building standards in Automotive Traffic Information ... · TISA Service Providers Road Operators Device Makers ... ( “Conflation” link to map segments) ... Fragmented rollout

TISA –building standards in Automotive Traffic Information Services

Taiwan Telematics 2012 - Taipei- 8th November 2012

TISA – Traveller Information Services Association - Nov2012 /2/

Dave Francis Technical Director-Broadcast Technologies

BEng (Hons) Electrical & Electronic Engineering

–Leeds University UK

10 years DENSO, Coventry UK

Snr Systems Engineer / Engineering Manager

Navigation Systems and Vehicle Infotainment / HMI Integration

-Jaguar Landover, Ford, Volvo infotainment systems

INRIX/ITIS since Nov 2007 Technical Director Broadcast Technologies

UK Premium RDS-TMC service

First Commercial DAB TPEG service

INRIX acquired ITIS in Aug 2011

Active TISA Member

Co-Chair of TISA Technical & Standards Committee

Treasurer


Traveller Information Services Association

RDS-TMC TPEG

Collaboration Standards Development


Formation of TISA

TISA

RDS-TMC forum

RTIG

TPEG forum

Mobile.Info

TISA

Service

Providers

Road

Operators

Device

Makers

Vehicle

Manufacturers

Broadcasters

Liaison

Organisations

Dec 2007

Non Profit

Run by Membership

Hosted by Ertico

Brussels

100+ members

EBU


What is TISA

Traveller Information Services Association

TISA is a market-driven membership association with

worldwide scope, established as a not for-profit

company focussed on proactive implementation of

traffic and travel information services and products

based on existing standards, including primarily

RDS-TMC and TPEG technologies.

http://www.tisa.org


RDS-TMC Specifications

RDS-TMC specifications Development

RDS-TMC first Proposed 1986 (Bosch /Philips)

Early field trials 1992-94

First operational services 1997 in some EU member states

ISO Specifications - ISO14819

• First released in 2000

• Updated 2003/2004

• New update currently in process within ISO (release 2013)

some additional features added , some deprecated features, few new event codes

+ Precise TMC Location Referencing

+ link to IVR telephone service

- spinning wheel mode

MAINTENANCE Phase – not much changing !!


RDS-TMC?

(Radio Data System-Traffic Message Channel)

Coded traffic messages through FM Broadcast using RDS

Uses selected data groups within the RDS system (8A and 3A RDS groups)

Provides language independent display to drivers

Coded Event codes – 1500+ coded events from Tables

Location from predefined Location Code table; integrated into Navigation system

Mapping.( “Conflation” link to map segments)

Originally defined for voice output -> Navigation system focus

Coding of data : Alert-C

Location code + direction + event codes (+ quantifiers) (+ labels)

300 message limit per transmitter

1message per second

Often regionally broadcast

Typ 3-5 min cycle


Worldwide Status of RDS-TMC

RDS-TMC success -> Worldwide adoption

Standardisation

Easy to deploy –

existing FM

infrastructure


Combination of free Public and Private services

Most EU countries have a “public free to air” service.

Combination of Free and Private services.

Private only services

Business model:

Private Services generally have a lifetime Fee paid for by vehicle OEM

Services are still being set up in new countries

TMC Services exist in USA, Canada, Australia, South Africa, New Zealand.

Expanding in Russia and China


UK INRIX RDS-TMC Service

UK RDS-TMC service (ITIS INRIX)

UK DoT and HA “TMC Demonstration” in 1997.

Funding: European Union, AA and RAC motoring clubs and

Communications & Measurement Technologies Ltd (C&MT) a private data

communications company.

C&MT developed a business plan following a very successful trial and in

2000 sold the RDS-TMC infrastructure and business to ITIS, now INRIX.

Commercial Service started in the UK in 2001

First customer :Toyota

Now over 20 vehicle makers, aftermarket providers plus PND devices

The INRIX service now supports 3 Million RDS-TMC devices in the UK

Service free to end users, paid for by OEM per unit. Lifetime access.


Germany RDS-TMC

German RDS-TMC services started in 1997

9 Federal regional services transmitted on Public radio (ARD)

Estimated 25 Million Receivers

Also Private service started in 2004 by T-Mobile

(Now operated by Nokia) • Public location Table

• Encrypted Location Codes


Location Table Certification

TISA provides the industry-standard certification of TMC location tables.

The certification is carried out by the members of the TISA Location Table

Release Team (LTRT). The team awards a "quality seal" to location

tables that have passed a set of tests.

A small but dedicated (very busy) team of volunteers.

Expansion of tables in Eastern Europe China and Russia.

TMCStudio – TISA Location Table

Certification test tool


Moving forward to TPEG

Proprietary systems exist in market today

-> Vehicle OEMs requesting Standardised solutions

-> Providers: collaborate on Standards ; Compete on Quality and Content

Proprietary Solutions

Standardised delivery

Traffic

+ Driver Services


Why TPEG?

Standardised in ISO – wide adoption and long-term use • ISO21219 series

Binary (for compact transmission) and XML forms

Standard message structure and management

new Applications can be added

extendibility within Apps

Older receiver can skip over (new) unknown features.

Language independent

Multiple location reference methods:

• TMC Tables

• DLR: Agora-C, OpenLR, ULR (new)


TPEG Technology – Application Support

Traffic Flow

•TPE-TFP (TrafficFlow & Prediction) describes traffic flow for real time as well as predictive speeds for time periods of minutes or hours into the future

Traffic Incidents

•TPEG-TEC (Traffic Event Compact) Incidents, road works and safety related items /info

Parking Information

•TPEG-PKI Parking information, price , static and dynamic availability

Fuel Pricing

•TPEG -FPI provides fuel type availability and pricing information.

Weather

• Currently being drafted (expected Q4 2012)

Dynamic Speed Limit Information

• TPEG-SPI (Speed Information) currently in draft form.

“Safety” camera data +

traffic camera (images) (INRIX)

Flight Arrival Departure times

(Proposed -BMT)

Road and Multimodal Routing (BMW)


TAWG Specification Process U

se C

ase

TISA member raises Use case

Modell

ing

UML Model Created

TAW

G 2

week R

evie

w

Review within TAWG

TIS

A M

em

ber

4 w

eek

revie

w

Review by TISA members

Rele

ase

d

Approval by TISA Steering Board

Released as TISA

Publish

Submission to ISO TC

Released as ISO Spec

• Specifications are defined by volunteers

• Anyone can raise a use case

• If there is business case it gets priority

• Aim is for all specifications to become open Standards

ISO


TPEG Specification development

UML Model

UML Export XMI

output

Auto generation Binary and

XML definition

TPEG Spec

Editorial text

Manual addition

Draft Spec for

review

Release to TISA

Members

Modelling Tool – Enterprise Architect TISA UML Converter TISA Spec


Two forms of TPEG

Binary(digital bearer)

XML


TPEG Philosophy

Extendable

Components

Unknown components

are Skipped over

Updatable devices to

allow new features

to be enabled in

market.


TPEG Transport Frames

TPEG Binary is a data stream

transferred in “TRANSPORT FRAMES.”

2 types :

Service Directory (type 0) used for Stream services (DAB)

Normal Data (type 1) used for data transfer

Frames start with

Sync Word “FF0F”


TPEG Message

TPEG Messages have same overall structure

MMC - Message management Container (when)

APP - Application Container (what)

LRC – Location Reference Container (where)


TFP (Traffic Flow & Prediction)

TFP gives a real boost to

user perception of traffic

service over TMC

Allows delivery of high

quality traffic to end user.

Precise positioning of end

of queue.

Improved user experience

• Accurate ETA

• Better route planning.

Examples of 2 INRIX Connect TFP

implementations LIVE in EU and NA

BMW

Audi


Application TFP

TFP provides FLOW data

Current status and Prediction

Different reports over Long road section split into small “sections”

Traffic colour , LOS = “Level Of Service”

• LOS 1 -Free Flow

• (LOS2-Heavy)

• LOS3- Slow

• LOS 4-Queuing

• LOS5 -Stationary

• LOS6- Blocked /No flow

Average Speed (kph)

Generally uses TMC location referencing (compact data size)


Application TFP

Road defined by LRC (typ max 30)

TFP Vector- represents status at specific time (

start + offset)

Vector split into Vector Sections

Each section positioned either with TMC Offset

from ref point or using metric offset

Average Speed (kph)

TMC location referencing (compact data size)

LOS is best defined by Service provider

Speed , nominal speed , road type


TEC (Traffic Event Compact

TEC data provides the incident

Effect and Cause

Effect Code:

• Traffic Flow Unknown,

• Heavy, slow, queuing, Stationary

• No Flow / Blocked

Multiple causes can be combined

Causes selected from tables

Diversions /Vehicle restrictions

Toyota


Location Referencing

Multiple Methods available

Currently most services use TMC as base method

Compact and easily integrated with existing mapping

Desire to

improve service

better content

More diverse content ( additional driver services)

Increasingly we are seeing the use of Dynamic Location Referencing

DLR solutions provide on the fly referencing , but can increase message size dramatically.

TPEG Location

Referencing

TMC

DLR1

(Agora-C)

OpenLR

ULR*

Pre-coded*

GLR


Broadcast vs Connected TPEG

TPEG was originally developed with Broadcast delivery in mind

• DAB and HD adaption layer specifications

UK has a fully commercial TPEG-DAB service.

• 16kb/s on NationaD1 Multiplex

• Customers TOYOTA and GARMIN

• UK was early adopter of DAB and has growing coverage.

Germany will launch public free services next year.

• 90% coverage expected mid 2013

Fragmented rollout of DAB across EU with some countries still

not embracing DAB (eg France, Austria)

Several OEMs have decided to launch with TPEG as connected

services

• to ensure full Market coverage was possible.

• Take advantage of 2 way channel to allow delivery of additional driver

services.


Distribution – Broadcast vs Connected

Bro

adcast

• + Fast update

• + only 1 system to operate , fixed cost for service provider.

• + Allows cost free data transfer Lifetime license model. No data carrier fees to pay for.

• - Not flexible for different customers

• - Large dataset for receivers –memory /message handling

• Slow roll out in EU

• Needs Links to regional services Connecte

d

• + Large coverage possible

• + IP connection shared to other vehicle functions; can be used with users tethered phone.

• + Allows other customer specific Location based services to be delivered.

• + Map, location table and vehicle and OEM specific differences can be supported

• - Bandwidth concerns


Connected TPEG development

Connected TPEG uses “backchannel” to request data specific for each car.

2 different Methods are defined in TISA Specifications

Annex A

• BMW implementation

• All communication through OEM Backend

• Simple interfacing

• All sessions use same parameters (all cars the same)

Transfer to car compressed at backend

Annex B

• Audi Implementation (preferred INRIX- due to flexibility)

• Authentication Initialise Session through Backend

• Data payload Request/response through internet

• Data payload compressed and encrypted


Connected TPEG interaction - Annex A

Annex A is simple , but less flexible.

Authentication to the service is done through the OEM “Backend”

Initialise Session /Authentication creates the DriveID which is used

for following Message Requests

Request : basic parameters

passed in URL

Response:

Base64 encoded

TPEG Binary transport Frame(s)

Compressed by Backend before sent to Car.


Connected TPEG interaction -

Annex B

Connected TPEG uses “backchannel” to request data specific for each car.

Authentication to the service is done through the OEM “Backend”

Initialise Session sets up parameters for following Requests and provides

encryption Key.

Request : HTTP Post current Location, (destination)

as XML

compressed and encrypted

Response:

TPEG Binary transport Frame(s)

(compressed and encrypted)


Response Payload

Data transferred to Car is based on Current Vehicle Location

Radius of interest

Requested Applications, TFP, TEC,PKI,FPI …

Class of roads

Route defined

Message density

Request frequency

Vehicle Speed

Incremental Updates

• First Request - ALL Messages

• Next Request - New /Updated messages

• Unimportant messages Cancelled


Summary

RDS-TMC has been standard for traffic Services

continues to grow

Hugely successful- low cost, simple.

Next Generation services are using TPEG

Connected or Broadcast

Standardized - ISO 21219 series

Flexibility : multiple Applications, Dynamic Loc referencing

TPEG already well established in REAL implementations

in EU and NA

Thank You

[email protected]

[email protected]

Documents

TISA building standards in Automotive Traffic Information ... · TISA Service Providers Road Operators Device Makers ... ( “Conflation” link to map segments) ... Fragmented rollout