This document discusses plans for unifying in-vehicle systems (IVS) in Russia, including the ERA-GLONASS emergency response system, fleet management systems, road tolling systems, and digital tachographs. The goals are to reduce costs by eliminating redundant hardware and functions across different IVS, standardize interfaces and communication protocols, and develop a single "connected IVS" approach. Key steps include developing standards for IVS/backend communication, regulations around unified use of GNSS data, and software/test tools to validate a reference implementation of unified protocols. Unifying these systems could lower total IVS costs per vehicle by at least 40% according to estimates.

1. ERA-GLONASS system architecture
IVS unification
End-user advantages
Yaroslav Domaratsky, PhD
Project office director
27 Nov 2012

2. GLONASS Union information
Founding members
JSC “MTS”, JSC “Vimpelcom”, JSC “Megafon”, JSC “RTComm.ru” (Rostelecom), LLC
Yandex, JSC “Navigation-Information Systems”, “GLONASS/GNSS-Forum” Association,
LLC “Summa-Telecom”
Major dates:
May, 18th 2012 – foundation of Partnership for Development and Use of Satellite
Navigation Technologies (GLONASS Partnership);
May 25th 2012 – GLONASS Partnership is appointed to be National Navigation Services
Provider (Government regulation #522);
May 18th 2012 – GLONASS Partnership is dedicated to be sole contractor for ERA
GLONASS infrastructure deployment (Government regulation #1732-p)
Oct 8th 2012 - the Ministry of Transportation of Russian Federation signed a Contract
with GLONASS Partnership for deployment and operations of ERA GLONASS Emergency
Response System.
The capabilities of ERA GLONASS infrastructure can be used to facilitate the development of
interoperable telematics systems, like fleet management systems for transportation transit
corridors, passenger transportation, heavy, hazardous cargo forward and deliveries, tolling
systems, stolen vehicle recovery service, digital tachographs
The capabilities of ERA GLONASS infrastructure make it possible to introduce innovative
products based on Insurance Telematics Services. Those are road traffic accident
reconstruction Service for Compulsory Insurance and Pay-as-You-Drive/Pay-as-You-Use
Insurance Programs for Voluntary Insurance.

3. GLONASS/GPS Systems
ERA-GLONASS
Vehicle Terminal
Mobile
communication
networks
ERA-GLONASS
operator
Regional
EMERCOM
center (1-1-2
service)
Emergency
Response
Services
Project started in May 2010
Shall be ready for full scale
operation in December 2013
Response to a road traffic accident
ERA-GLONASS System:
National Initiative to Increase Safety on Russian Roads
Fully deployed ERA GLONASS system could save up to 4,000 lives every year. In Russia annual economic effect
could be up to 8 billion rubles from the reduction in number of fatalities, not including savings due to reduction
in number of heavy injuries.

4. 2010
Design Planning
2011
Project Development
2012
Pilot Projects
2013
System Deployment
ERA-GLONASS System:
System Design Milestones and Activities
May2010
StartofERA-GLONASSproject
(GovernmentContractsigned)
ERA-GLONASSfull-scale
operationstartsin2014
Design and deployment of ERA-GLONASS
infrastructure
Legislation enabling the creation and operation
of ERA-GLONASS System
Development of ERA-GLONASS in-vehicle system
prototypes
Ensuring interaction with emergency response
services

5. ERA-GLONASS Federal Infrastructure
2011
2012
2013
Will be deployed:
• 8 navigation-information centers
• 72 regional communication centers
Main roads coverage*:
•МТС 82%
•Megafon 75%
•Beeline 73%
ERA-GLONASS
90%
* Official data, March 2012
Technical solution will provide best possible
coverage
GLONASS Union assigned to build and to operate ERA-GLONASS system in Russia

6. ERA-GLONASS System Architecture

7. Innovation cycle targets

8. Main differences between ERA-GLONASS and eCall
GLONASS GNSS support is the must
– Combined GNSS receivers (e.g. GLONASS/GPS/Galileo) are OK
MSD transmission
– In-band (primary method – standardized by 3GPP)
– SMS (back-up mechanism)
Echo cancellation and noise reduction requirements defined
Test requirements defined:
– Test session can be initiated from vehicle, test results can be transmitted to
back-end
Remote IVS configuration
Remote IVS software upgrade
Crash acceleration profile record and transmission
IVS installation in OEM pre-installed and aftermarket / retrofit configurations
“Black box” function
Standardized I/O port and standardized communication
protocol to connect additional sensors.

9. ERA-GLONASS IVS requirements development and approval
IVS requirements review data
Requirements review started July 2010
Requirements review duration 13 months
Number of companies received
requirements
370
Number of companies submitted
comments
33
Total number of comments received 1081
Confirmed IVS requirements review was organized
effectively
- OEM associations – 22 members in total
- more than 5 Tier 1 suppliers
35 OEM’s confirmed they do understand IVS requirements
More than 5 Tier 1 suppliers and more than 5 Russian
companies confirmed aftermarket / retrofit IVS mass
production can start in Q1 2013
IVS national standards review data
Standards drafts review started Aug 2011
Standards drafts review duration 3 months
Number of companies notified about
standards drafts review
345
Number of companies submitted comments 12
Total number of comments received 285
Defined IVS introduction year is 2014
IVS suppliers ready for mass production starting in Q1 2013
Some OEM companies ready for factory IVS installation in 2013

10. IVS national standards development and approval status
National standards approved in Dec 2011
GOST R 54620—2011 Global navigation satellite system. Road accident emergency
response system. In-vehicle emergency call system. General technical requirements
GOST R 54618–2011 Compliance test methods for electromagnetic compatibility,
environmental and mechanical resistance requirements of In-Vehicle Emergency Call
System
GOST R 54619—2011 Protocol of Data Transmission from In-Vehicle Emergency Call
System to Emergency Response System Infrastructure
National standards passed public review in 2012
Functional test methods of In-Vehicle Emergency Call System and data transfer protocols
Compliance testing for the requirements for quality speakerphone in a vehicle
Test methods for navigation module of In-Vehicle Emergency Call System
Requirements to determine the mechanism of the road accident, the algorithm
determining the events and methods of testing in-vehicle system in the definition of the
road accident (aftermarket / retrofit IVS only)
Test methods for wireless communication module of In-Vehicle Emergency Call System.

11. Defined IVS introduction schedule
01 Oct 2014 – new vehicles of categories М2, М3 intended for passenger
transportation and new vehicle of category N1 (weight > 2.5 tons), new vehicle
of categories N2 and N3 intended for dangerous cargo transportation
(assessment of compliance in the form of vehicle type approval at first time)
01 Jan 2015 – new vehicles of categories М1, N1 (assessment of compliance in
the form of vehicle type approval at first time); new vehicles of categories N2,
N3 not intended for dangerous cargo transportation; new vehicles of categories
М2, М3 not intended for passenger transportation (assessment of compliance
in the form of vehicle type approval at first time)
01 Jan 2016 – vehicles of categories M2, M3 intended for passenger
transportation and vehicles of category N1 (weight > 2.5 tons), vehicles of
categories N2 and N3 intended for dangerous cargo transportation that will put
in circulation at first time (as new vehicles as well as all vehicles not previously
in use in the territory of the Russian Federation which will be imported to
Russia)
01 Jan 2017 – all categories of vehicles that will put in circulation at first time
(as new vehicles as well as all vehicles not previously in use in the territory of
the Russian Federation which will be imported to Russia).

12. Value added services support - priorities
* - the feature can be implemented on board or off board ** - optional feature

13. What next - proposals to extend ERA-GLONASS features
Crash reconstruction
Vehicle track and acceleration information recording before, during and after the crash,
trustable vehicle track and acceleration information transmission per request;
Vehicle state information recording before, during and after the crash, trustable vehicle
state information transmission per request;
Automated real time crash information analysis at back end.
Crash prevention
Road and environmental information collection from drivers and other information
sources;
Automated road state information collection from vehicles, automated information
aggregation and filtering, processed information transmission to Police and other
consumers;
Road state and other related information transmission to drivers along the road;
Active crash prevention using V2V communication technologies;
Active crash prevention using V2I communication technologies.
IVS unification
ERA-GLONASS IVS unification with below systems:
fleet management;
road tolling;
digital tachographs;
passenger transportation ticketing systems;
other connected IVS .

14. IVS unification – problems today
Need to install a number of IVS with duplicated functions
Different IVS using different internal and external GNSS and GSM/UMTS
antennas (not optimal antenna performance)
Different IVS implement different UI (buttons, voice, display) – driver
distraction
Interfaces between IVS components not standardized – need to install new IVS
to implement additional functions or need to use proprietary interfaces
between IVS components (higher system cost)
Cost estimation today assuming big volume:
Fleet management – 6 000 RUB
ERA-GLONASS – 4 000 RUB
Digital tachograph – 22 000 RUB
Road tolling – 9 000 RUB
Passenger transportation ticketing > 20 000 RUB
Total cost: > 61 000 RUB
Target: decrease system cost by at least 40% (24 400 RUB) with the unified IVS.

15. IVS unification – main principles
Unification based on government regulation (emergency call, fleet
management, road tolling, digital tachographs)
Standardize interfaces between IVS components
Develop IVS installation requirements and procedures
Standardize interfaces with OEM pre-installed systems
Develop true connected GNSS digital tachograph
Standardize vehicle “black box” features (aka. EDR) including data
upload path
Unify user interface
Standardize IVS / back ends communication protocols
Promote “connected IVS” approach.

16. IVS unification – development plan
Standards development
Fleet management IVS / back-end communication protocol
Connected digital tachograph IVS / back-end communication
protocol
Road tolling IVS / back-end communication protocol
Black box IVS / back-end communication protocol
Regulation development
GNSS information use to calculate vehicle move / speed and driver
work hours
Handle GNSS signal loss events at back end
Define the way to do enforcement
Road tolling and digital tachograph requirements shall not block IVS
unification
Software and test tools development
Develop reference implementation for fleet management and
connected digital tachographs IVS / back end communication
protocols
Develop validation tools for fleet management and connected digital
tachographs IVS / back end communication protocols.

17. Thank you
yaroslav@glonassunion.ru