fleet management systems for professionals: some specific ...€¦ · fleet management systems for...

unrestricted

Fleet management systems for professionals: some specific requirements

Orange Labs

Pascal Bodin, Research & Development 2010-10-19, ETSI M2M Workshop

Orange Labs - Research & Development – Fleet management systems – 2010-10-19 - 2 unrestricted

Contents

definitions

let's take an example: a taxi system

– functions

– requirements on the communication network(s)

system integrator's view

conclusion


Fleet management systems for professionals

Central system (taxi central dispatch office, bus operation and management

center...)

Vehicle (taxi, waste collection truck, bus...)

Communication network(s)

Human being (taxi driver, truck driver,

bus driver...)


Taxi system – main functions

taxi request dispatch

– customer request allocated to the best taxi

taxi request follow-up

– to anticipate request dispatch, when heavy traffic

credit card payments

general messages (e.g. « speed camera at... »)

personal messages (e.g. « call your wife back »)

security alarm, with audio monitoring

taxi locating

information about distribution of taxis over the city

information about distribution of customer requests

etc.


Taxi system – Request dispatch - 1/3

Taxis waiting at taxi stand

Cruising taxi

Central dispatch office

Taxi 1

Taxi 2

Taxi 3

Simplified dispatch algorithm

· city is divided in sectors

· one taxi stand at most per sector

· taxis can be waiting at a stand, or cruising

· taxi request dispatch:• sector is selected (depending on customer address)• if taxis waiting at stand, first taxi complying with

services requirements is selected• if stand is empty, a cruising taxi is selected (usually

the nearest one)• if no cruising taxi in sector, search is broadened to

neighbouring sectors• etc.

· the selected taxi driver must acknowledge the request

Sector 1

Sector 2



To taxi: are you really here? If yes, here is a request for your driver

From taxi to dispatch office: yes, I'm here

Displayed to driver:Services

requirements displayed.Do you accept them?

From driver to dispatch office: yes, I accept them

Displayed to driver:Address.

Do you accept the request?From driver to dispatch office: yes, I accept the request

Request allocated to taxi 1

Taxi 1

To other taxis at same stand: request allocated to taxi 1



Requirement:

– transmit messages to a group of addressees

– groups are defined dynamically by the system

technical architecture 1: PMR analog network

– all taxis at the same stand « hear » data exchanges (provided that they are on same radio channel)

– => displaying allocated request does not require additional data exchanges

technical architecture 2: GPRS

– one additional data exchange per taxi to inform


Taxi system – Security alarm - 1/2

From driver to dispatch office: help!

Tracking mode activated:- start location tracking- start audio monitoring

To dispatch office: locations + audio

Taxi 1

To driver: help request received

To nearby taxis: security alarm information + taxi 1 location

Taxi driver at risk



Requirement:

– high priority acknowledged message

– remote activation of audio

– audio and data transmitted at the same time

– group fonction, as seen in previous slides




– one channel for voice, one channel for data

– voice channel allocated to taxi 1

– every 20 s, voice transmission stopped – current location transmitted

– base station broadcasts alarm status and current location on data channel. Nearby taxis display this information.


– open a voice communication for audio transmission

– every 20 s, stop voice communication, activate GPRS socket and send current location

– or: continuous voice communication + SMS for location

– => low quality of service


Taxi system – Operating zone

Requirement:

– ensure coverage all over taxi operating zone

with PMR: not so easy, but a level of adjustement is possible

with GPRS: well, you can try to ask your favorite operator


Taxi system – System integrator's view

technical blocks that must be assembled by the system integrator:

installation in vehicles is an important step

Central sideEmbedded side

embedded OS

embedded equipment

telematics services embedded

application software embedded

OS

PC / serverperipheral devices

telematics services central

fleet management components central

com

pone

nt

com

pone

nt

com

pone

nt

fleet management components embedded

com

pone

nt

com

pone

nt

com

pone

nt

application software central

OS API

telematics services APItelematics services API

OS API

components APIscomponents APIs

telematics protocol

components protocols

application protocols

Customer-dedicated integration

Technical components

Communication

Execution platforms



so, where to look when there is a problem???

is it a hardware problem, an embedded software problem, a radiocommunication terminal problem, a bad protocol design, an application software problem, a bad installation or ... a network operator originated problem?

for test / debug: the integrator has visibility into almost all those components... excepted the mobile network.

=> how to provide such visibility (type of information, how to make it available...)?


Conclusion

fleet management systems: niche markets (for 20 years now...)

but they place quite demanding requirements on mobile networks

looking at those requirements in a detailed way:

– ideas for new functionalities?

– supporting standards but: business opportunities?

– consider ITS?

unrestricted

thank you

Orange, the Orange mark and any other Orange product or service names referred to in this material are trade marks of Orange Personal Communications Services Limited. © Orange Personal Communications Services Limited.

1

unrestricted

Fleet management systems for professionals: some specific requirements

Orange Labs

Pascal Bodin, Research & Development 2010-10-19, ETSI M2M Workshop

2


Contents

definitions

let's take an example: a taxi system

– functions

– requirements on the communication network(s)

system integrator's view

conclusion

3


Fleet management systems for professionals

Central system (taxi central dispatch office, bus operation and management

center...)

Vehicle (taxi, waste collection truck, bus...)

Communication network(s)

Human being (taxi driver, truck driver,

bus driver...)

In the context of this presentation, « fleet management system » means « system used by an association of professionals who use vehicles to perform their tasks ».

Fleet management systems are often seen as being M2M systems. M2M systems are often seen as being systems not requiring any human intervention. So, logically, fleet management systems should not require any human intervention. Our diagram depicts exactly the opposite: human beings are actors of the system, on the mobile side, and at the central office. Not considering them would restrict our view to trivial functions of the systems only.

4


Taxi system – main functions

taxi request dispatch

– customer request allocated to the best taxi

taxi request follow-up

– to anticipate request dispatch, when heavy traffic

credit card payments

general messages (e.g. « speed camera at... »)

personal messages (e.g. « call your wife back »)

security alarm, with audio monitoring

taxi locating

information about distribution of taxis over the city

information about distribution of customer requests

etc.

• best means: taxi that can serve the request (number of persons, luggage, non-smoking...), being the nearest one (in time, not in distance), according to taxi association priority rules

• information about taxi distribution, about distribution of customer requests: to taxi drivers

5



Taxis waiting at taxi stand

Cruising taxi

Central dispatch office

Taxi 1

Taxi 2

Taxi 3

Simplified dispatch algorithm

· city is divided in sectors

· one taxi stand at most per sector

· taxis can be waiting at a stand, or cruising

· taxi request dispatch:• sector is selected (depending on customer address)• if taxis waiting at stand, first taxi complying with

services requirements is selected• if stand is empty, a cruising taxi is selected (usually

the nearest one)• if no cruising taxi in sector, search is broadened to

neighbouring sectors• etc.

· the selected taxi driver must acknowledge the request

Sector 1

Sector 2

• examples of services requirements: smoking or non-smoking car, car for more than 4 persons, animal accepted, etc.

6



To taxi: are you really here? If yes, here is a request for your driver

From taxi to dispatch office: yes, I'm here

Displayed to driver:Services

requirements displayed.Do you accept them?

From driver to dispatch office: yes, I accept them

Displayed to driver:Address.

Do you accept the request?From driver to dispatch office: yes, I accept the request

Request allocated to taxi 1

Taxi 1

To other taxis at same stand: request allocated to taxi 1

7



Requirement:

– transmit messages to a group of addressees

– groups are defined dynamically by the system


– all taxis at the same stand « hear » data exchanges (provided that they are on same radio channel)

– => displaying allocated request does not require additional data exchanges


– one additional data exchange per taxi to inform

PMR: Private Mobile Radio

The group requirement described here applies as well to several other functions:

• general messages

• when a taxi enters a stand queue, other taxis at the stand must be informed

• information about distribution of taxis over the city, to be displayed in taxis

• information about customer requests distribution, to be displayed to taxis

• alarms (see next slide)

• etc.

8



From driver to dispatch office: help!

Tracking mode activated:- start location tracking- start audio monitoring

To dispatch office: locations + audio

Taxi 1

To driver: help request received

To nearby taxis: security alarm information + taxi 1 location

Taxi driver at risk

9



Requirement:

– high priority acknowledged message– remote activation of audio

– audio and data transmitted at the same time

– group fonction, as seen in previous slides

High priority: message to be transmitted and acknowledged in less than a few seconds.

10




– one channel for voice, one channel for data

– voice channel allocated to taxi 1

– every 20 s, voice transmission stopped – current location transmitted

– base station broadcasts alarm status and current location on data channel. Nearby taxis display this information.


– open a voice communication for audio transmission– every 20 s, stop voice communication, activate GPRS

socket and send current location

– or: continuous voice communication + SMS for location

– => low quality of service

PMR: one channel for voice and one channel for data is a common configuration for small taxis associations (less than 100). For larger associations, several data channels are used.

GPRS: do class A GPRS modules exist nowadays?

3G: OK?

11


Taxi system – Operating zone

Requirement:

– ensure coverage all over taxi operating zone

with PMR: not so easy, but a level of adjustement is possible

with GPRS: well, you can try to ask your favorite operator

Another example: road rally. Coverage must be provided along the road, only during a given period.

12



technical blocks that must be assembled by the system integrator:

installation in vehicles is an important step

Central sideEmbedded side

embedded OS

embedded equipment

telematics services embedded

application software embedded

OS

PC / serverperipheral devices

telematics services central

fleet management components central

com

pone

nt

com

pone

nt

com

pone

nt

fleet management components embedded

com

pone

nt

com

pone

nt

com

pone

nt

application software central

OS API

telematics services APItelematics services API

OS API

components APIscomponents APIs

telematics protocol

components protocols

application protocolsCustomer-dedicated integration

Technical components

Communication

Execution platforms

13



so, where to look when there is a problem???

is it a hardware problem, an embedded software problem, a radiocommunication terminal problem, a bad protocol design, an application software problem, a bad installation or ... a network operator originated problem?

for test / debug: the integrator has visibility into almost all those components... excepted the mobile network.

=> how to provide such visibility (type of information, how to make it available...)?

Possible types of information:

• communication logs

• rejected communications

• user subscription status

• network outages (past, planned)

• etc.

Access to this information must be protected, of course.

14


Conclusion

fleet management systems: niche markets (for 20 years now...)

but they place quite demanding requirements on mobile networks

looking at those requirements in a detailed way:

– ideas for new functionalities?

– supporting standards but: business opportunities?

– consider ITS?

15

unrestricted

thank you

Orange, the Orange mark and any other Orange product or service names referred to in this material are trade marks of Orange Personal Communications Services Limited. © Orange Personal Communications Services Limited.

fleet management systems for professionals: some specific ...€¦ · fleet management systems for...

Documents