OpenLegislation

Commission Delegated Regulation (EU) 2017/79 of 12 September 2016 establishing detailed technical requirements and test procedures for the GB type-approval of motor vehicles with respect to their 112-based eCall in-vehicles systems, of 112-based eCall in-vehicle separate technical units and components and supplementing and amending Regulation (EU) 2015/758 of the European Parliament and of the Council with regard to the exemptions and applicable standards (Text with EEA relevance)

EU Regulation 2017/79 · Adopted 12 September 2016 · Extends to United Kingdom

Original text. legislation.gov.uk does not revise this item, so later amendments are not shown here. Changes made to it are listed under each provision when known.

Commission Delegated Regulation (EU) 2017/79

of 12 September 2016

establishing detailed technical requirements and test procedures for the F1GB type-approval of motor vehicles with respect to their 112-based eCall in-vehicles systems, of 112-based eCall in-vehicle separate technical units and components and supplementing and amending Regulation (EU) 2015/758 of the European Parliament and of the Council with regard to the exemptions and applicable standards

(Text with EEA relevance)

THE EUROPEAN COMMISSION,

Having regard to the Treaty on the Functioning of the European Union,

Having regard to Regulation (EU) 2015/758 of the European Parliament and of the Council of 29 April 2015 concerning type-approval requirements for the deployment of the eCall in-vehicle system based on the 112 service and amending Directive 2007/46/ECf1, and in particular Article 2(2), Article 5(8) and (9) and Article 6(12) thereof,

Whereas:

(1)

Regulation (EU) 2015/758 lays down a general obligation for new types of vehicles of categories M1 and N1 to be equipped with 112-based eCall in-vehicle systems as of 31 March 2018.

(2)

It is necessary to set out the detailed technical requirements and test procedures for the approval of motor vehicles with respect to their 112-based eCall in-vehicle systems. The test procedures also allow for testing and approval of 112-based eCall in-vehicle separate technical units (‘STUs’) and components intended for fitment in motor vehicles or for integration in 112-based eCall in-vehicle systems.

(3)

Tests should be carried out by technical services in their capacity as foreseen in Directive 2007/46/EC of the European Parliament and of the Councilf2 that establishes the general framework for the EC type-approval of motor vehicles and defines the roles and responsibilities of all the actors involved at different stages of the approval process.

(4)

Tests and requirements should be designed in such a way that duplicated testing is avoided. In addition, some flexibility is required regarding special purpose vehicles that are built in multiple stages in accordance with Directive 2007/46/EC as they are exempted from the frontal and lateral collision requirements under UNECE Regulations 94 and 95. For that reason, the approval granted at a previous stage of the process to the base vehicle with respect to the 112-based eCall in-vehicle system should remain valid, unless the system or its sensors were modified after the approval.

(5)

There are cases where certain classes of vehicles cannot for technical reasons be fitted with an appropriate eCall triggering mechanism and should be exempted from the requirements of Regulation (EU) 2015/758. Following an assessment of the costs and benefits carried out by the Commission and taking into account the relevant safety and technical aspects, those classes of vehicles are identified and included in a list established in Annex IX.

(6)

The 112-based eCall in-vehicle system needs to remain functional after a severe accident. An automatic eCall is most beneficial in a high-severity collision where the risk of occupants of the vehicle being incapacitated and not able to call for assistance without an eCall system is highest. The 112-based eCall in-vehicle systems, components and STUs should therefore be tested to verify their sustained functionality after being subjected to inertial loads similar to those that may occur during a severe vehicle crash.

(7)

The post-crash functioning and automatic triggering of the 112-based eCall in-vehicle system should also be ensured at vehicle level. A full-scale impact test procedure should therefore be set out to verify that the vehicle is constructed in such a way that its 112-based eCall in-vehicle system survives a frontal and side collision in its original mounting situation and configuration.

(8)

The core functionality of a 112-based eCall in-vehicle system is not only to notify the Public Safety Answering Point (‘PSAP’) of an accident, but also to establish a voice connection between occupants of the vehicle and a PSAP operator. The audio equipment of the 112-based eCall in-vehicle system should therefore be tested after the full-scale crash tests to guarantee that it does not suffer loudness reduction or distortions that make voice communication impossible.

(9)

Where a 112-based eCall in-vehicle system is approved for use in conjunction with a system providing third party services (‘TPS system’), it should be ensured that only one of those systems is active at a time and that the 112-based eCall in-vehicle system is triggered automatically when the TPS system does not function. The manufacturer of vehicles fitted with 112-based eCall in-vehicle system and TPS system should explain the fall-back procedure built-in the TPS system and describe the principles of the changeover mechanism between the TPS system and the 112-based eCall in-vehicle system.

(10)

To ensure the provision of accurate and reliable position information, the 112-based eCall in-vehicle system should be able to use the positioning services provided by the Galileo and the EGNOS systems.

(11)

The 112-based eCall in-vehicle system should warn the occupants of a vehicle in the event the system is unable to execute an emergency call. A procedure should therefore be set out for the verification of the self-testing of the system and of its compliance with the malfunction indication requirements.

(12)

Manufacturers should ensure that the 112-based eCall in-vehicle systems are not traceable and not subject to any constant tracking. For that purpose, a test procedure should be set out to verify that the 112-based eCall in-vehicle system is not available for communication with the PSAP before the eCall is triggered.

(13)

Any data processed through the 112-based eCall in-vehicle system must be adequate, relevant and proportionate to the purposes for which those data are collected and processed. To that end, appropriate procedures should be laid down to verify that the data in the internal memory of the system are automatically and continuously removed and are not retained longer than necessary for the purpose of handling the emergency call.

(14)

The versions of the applicable standards on which the requirements for eCall are based should be updated.

(15)

Vehicle manufacturers should be given sufficient time to adapt to the technical requirements for the approval of 112-based eCall in-vehicle systems. The Member States should also be given sufficient time to deploy on their territory the PSAP infrastructure required for the proper receipt and handling of emergency calls. For that reason, the date of application of this Regulation should be the same as the date of compulsory application of the 112-based eCall in-vehicle systems in accordance with Regulation (EU) 2015/758,

HAS ADOPTED THIS REGULATION:

Annotations to the whole text

Textual amendments

F1

Words in Regulation title substituted (31.12.2022 at 11.00 p.m.) by The Road Vehicles and Non-Road Mobile Machinery (Type-Approval) (Amendment and Transitional Provisions) (EU Exit) Regulations 2022 (S.I. 2022/1273), regs. 1(2), 79(2)

Footnotes

f1

OJ L 123, 19.5.2015, p. 77.

f2

Directive 2007/46/EC of the European Parliament and of the Council of 5 September 2007 establishing a framework for the approval of motor vehicles and their trailers, and of systems, components and separate technical units intended for such vehicles (Framework Directive) (OJ L 263, 9.10.2007, p. 1).

Contents

  1. 1Subject matter
  2. 2Classes of vehicles exempted from the requirement to be equipped with a 112-based eCall in-vehicle system
  3. 3Multi-stage approval of special purpose vehicles
  4. 4Definitions
  5. 5Requirements and test procedures for GB type-approval of motor vehicles with regard to the installation of 112-based eCall in-vehicle systems
  6. 6Requirements and test procedures for GB type-approval of 112-based eCall in-vehicle system components
  7. 7Requirements and test procedures for GB type-approval of 112-based eCall in-vehicle STUs
  8. 8Obligations of the approval authority
  9. 9Amendments to Regulation (EU) 2015/758
  10. 10Entry into force and application
  11. Signature
  12. Annex TABLE OF CONTENTS
  13. Annex I: Technical requirements and procedures for testing the resistance of eCall in-vehicle systems to severe crashes (high-severity deceleration test)
  14. Requirements
  15. Performance requirements
  16. 1.1.1Division 1.1.1
  17. 1.1.2Division 1.1.2
  18. 1.1.3Division 1.1.3
  19. 1.1.4Division 1.1.4
  20. 1.1.5Division 1.1.5
  21. Test procedure
  22. 2.1Purpose of the high-severity deceleration test procedure
  23. 2.2Division 2.2
  24. 2.2.1Division 2.2.1
  25. 2.2.2Division 2.2.2
  26. 2.2.3Division 2.2.3
  27. 2.2.4Division 2.2.4
  28. Deceleration/acceleration procedure
  29. 2.3.1Division 2.3.1
  30. 2.3.2Division 2.3.2
  31. 2.3.3Division 2.3.3
  32. 2.3.4Division 2.3.4
  33. 2.3.5Division 2.3.5
  34. 2.3.6Division 2.3.6
  35. Description of the test pulse
  36. FigureMinimum and maximum curve of the test pulse (pulse corridor)
  37. Verification procedure
  38. 2.4.1Division 2.4.1
  39. 2.4.2Division 2.4.2
  40. 2.4.3Division 2.4.3
  41. 2.4.4Division 2.4.4
  42. 2.4.5Division 2.4.5
  43. 2.4.6Division 2.4.6
  44. Positioning test procedure
  45. 2.5.1Division 2.5.1
  46. 2.5.2Division 2.5.2
  47. 2.5.3Division 2.5.3
  48. 2.5.4Division 2.5.4
  49. Division
  50. 2.5.5Division 2.5.5
  51. Antenna test procedure
  52. 2.6.1Division 2.6.1
  53. 2.6.2Division 2.6.2
  54. 2.6.2.1Division 2.6.2.1
  55. 2.6.2.2Division 2.6.2.2
  56. 2.6.3Division 2.6.3
  57. Connection procedures
  58. Simulated Mobile Network Procedure
  59. 2.7.1.1Division 2.7.1.1
  60. 2.7.1.2Division 2.7.1.2
  61. 2.7.1.3Division 2.7.1.3
  62. 2.7.1.4Division 2.7.1.4
  63. 2.7.1.5Division 2.7.1.5
  64. Public Mobile Network Procedure
  65. 2.7.2.1Division 2.7.2.1
  66. 2.7.2.2Division 2.7.2.2
  67. 2.7.2.3Division 2.7.2.3
  68. 2.7.2.4Division 2.7.2.4
  69. 2.7.2.5Division 2.7.2.5
  70. Wired Transmission Procedure
  71. 2.7.3.1Division 2.7.3.1
  72. 2.7.3.2Division 2.7.3.2
  73. 2.7.3.3Division 2.7.3.3
  74. 2.7.3.4Division 2.7.3.4
  75. Verification procedures for components
  76. 2.8.1Division 2.8.1
  77. 2.8.1.1Division 2.8.1.1
  78. Control module including its connectors and wire harness as described in point 2.2.4 of this Annex.
  79. 2.8.2.1Division 2.8.2.1
  80. 2.8.2.2Division 2.8.2.2
  81. 2.8.2.3Division 2.8.2.3
  82. 2.8.2.4Division 2.8.2.4
  83. 2.8.2.5Division 2.8.2.5
  84. 2.8.2.6Division 2.8.2.6
  85. Mobile network antenna including its connectors and wire harness as described in point 2.2.4 of this Annex
  86. 2.8.3.1Division 2.8.3.1
  87. 2.8.3.2Division 2.8.3.2
  88. 2.8.3.3Division 2.8.3.3
  89. 2.8.3.4Division 2.8.3.4
  90. 2.8.3.5Division 2.8.3.5
  91. Power supply (if not part of the control module) including its connectors and wire harness as described in point 2.2.4 of this Annex
  92. 2.8.4.1Division 2.8.4.1
  93. 2.8.4.2Division 2.8.4.2
  94. Annex II: Full-scale impact test assessment
  95. Requirements
  96. Performance requirements
  97. 1.1.1Division 1.1.1
  98. 1.1.2Division 1.1.2
  99. 1.1.3Division 1.1.3
  100. 1.1.4Division 1.1.4
  101. 1.1.5Division 1.1.5
  102. 1.1.6Division 1.1.6
  103. Test procedure
  104. 2.1Purpose of the full-scale impact test procedure
  105. 2.2Division 2.2
  106. Impact test procedure
  107. 2.3.1Division 2.3.1
  108. 2.3.2Division 2.3.2
  109. 2.3.3Division 2.3.3
  110. Verification procedure
  111. 2.4.1Division 2.4.1
  112. 2.4.2Division 2.4.2
  113. 2.4.3Division 2.4.3
  114. 2.4.4Division 2.4.4
  115. 2.4.5Division 2.4.5
  116. 2.4.6Division 2.4.6
  117. 2.5Positioning test procedure
  118. Antenna test procedure
  119. 2.6.1Division 2.6.1
  120. 2.7Connection procedures
  121. Annex III: Crash resistance of audio equipment
  122. Requirements
  123. Performance requirements
  124. 1.1.1Division 1.1.1
  125. 1.1.2Division 1.1.2
  126. 1.1.3Division 1.1.3
  127. Test procedure
  128. 2.1Purpose of the audio equipment crash resistance test procedure
  129. 2.2Division 2.2
  130. Overview of test procedure
  131. 2.3.1Division 2.3.1
  132. 2.3.2Division 2.3.2
  133. 2.3.3Division 2.3.3
  134. Arrangement of testers
  135. 2.4.1Division 2.4.1
  136. 2.4.2Division 2.4.2
  137. 2.4.3Division 2.4.3
  138. Test setup
  139. 2.5.1Division 2.5.1
  140. 2.5.2Division 2.5.2
  141. 2.5.3Division 2.5.3
  142. Test call
  143. 2.6.1Division 2.6.1
  144. Exchange of test messages
  145. Receive direction
  146. 2.6.2.1.1Division 2.6.2.1.1
  147. 2.6.2.1.2Division 2.6.2.1.2
  148. 2.6.2.1.3Division 2.6.2.1.3
  149. Send direction
  150. 2.6.2.2.1Division 2.6.2.2.1
  151. 2.6.2.2.2Division 2.6.2.2.2
  152. 2.6.2.2.3Division 2.6.2.2.3
  153. 2.6.3Division 2.6.3
  154. 2.6.4Division 2.6.4
  155. Connection procedures
  156. 2.7.1Division 2.7.1
  157. Test sentences
  158. Annex IV: Co-existence of third party services (TPS) with the 112-based eCall in-vehicle systems
  159. Requirements
  160. 1.1Division 1.1
  161. Performance requirements
  162. 1.2.1Division 1.2.1
  163. 1.2.2Division 1.2.2
  164. Documentation requirements
  165. 1.3.1Division 1.3.1
  166. 1.3.2Division 1.3.2
  167. Test procedure
  168. 2.1Purpose of the TPS co-existence test procedure
  169. 2.2Division 2.2
  170. 2.3Division 2.3
  171. 2.3.1Division 2.3.1
  172. 2.3.2Division 2.3.2
  173. 2.3.3Division 2.3.3
  174. 2.3.4Division 2.3.4
  175. 2.3.5Division 2.3.5
  176. 2.4Division 2.4
  177. 2.4.1Division 2.4.1
  178. 2.4.2Division 2.4.2
  179. 2.4.3Division 2.4.3
  180. 2.4.4Division 2.4.4
  181. 2.4.5Division 2.4.5
  182. 2.5Connection procedures
  183. Annex V: Automatic triggering mechanism
  184. Requirements
  185. 1.1Division 1.1
  186. Documentation requirements
  187. 1.2.1Division 1.2.1
  188. 1.2.2Division 1.2.2
  189. 1.2.3Division 1.2.3
  190. 1.2.3.1Division 1.2.3.1
  191. 1.2.3.2Division 1.2.3.2
  192. 1.2.3.3Division 1.2.3.3
  193. 1.2.3.4Division 1.2.3.4
  194. Annex VI: Technical requirements for compatibility of eCall in-vehicle systems with the positioning services provided by the Galileo and the EGNOS systems
  195. Requirements
  196. Compatibility requirements
  197. 1.1.1Division 1.1.1
  198. 1.1.2Division 1.1.2
  199. 1.1.3Division 1.1.3
  200. 1.1.4Division 1.1.4
  201. Performance requirements
  202. 1.2.1Division 1.2.1
  203. 1.2.2Division 1.2.2
  204. 1.2.3Division 1.2.3
  205. 1.2.4Division 1.2.4
  206. 1.2.5Division 1.2.5
  207. 1.2.6Division 1.2.6
  208. 1.2.7Division 1.2.7
  209. 1.2.8Division 1.2.8
  210. 1.2.9Division 1.2.9
  211. 1.2.10Division 1.2.10
  212. Test methods
  213. Test conditions
  214. 2.1.1Division 2.1.1
  215. 2.1.2Division 2.1.2
  216. 2.1.3Division 2.1.3
  217. 2.1.4Division 2.1.4
  218. 2.1.5Division 2.1.5
  219. 2.1.6Division 2.1.6
  220. 2.1.7Division 2.1.7
  221. 2.1.8Division 2.1.8
  222. Test procedures
  223. NMEA-0183 messages output test.
  224. 2.2.1.1Division 2.2.1.1
  225. 2.2.1.2Division 2.2.1.2
  226. 2.2.1.3Division 2.2.1.3
  227. 2.2.1.4Division 2.2.1.4
  228. 2.2.1.5Division 2.2.1.5
  229. 2.2.1.6Division 2.2.1.6
  230. Assessment of positioning accuracy in autonomous static mode.
  231. 2.2.2.1Division 2.2.2.1
  232. 2.2.2.2Division 2.2.2.2
  233. 2.2.2.3Division 2.2.2.3
  234. 2.2.2.4Division 2.2.2.4
  235. 2.2.2.5Division 2.2.2.5
  236. 2.2.2.6Division 2.2.2.6
  237. 2.2.2.7Division 2.2.2.7
  238. 2.2.2.8Division 2.2.2.8
  239. 2.2.2.9Division 2.2.2.9
  240. 2.2.2.10Division 2.2.2.10
  241. 2.2.2.11Division 2.2.2.11
  242. 2.2.2.12Division 2.2.2.12
  243. 2.2.2.13Division 2.2.2.13
  244. 2.2.2.14Division 2.2.2.14
  245. 2.2.2.15Division 2.2.2.15
  246. 2.2.2.16Division 2.2.2.16
  247. 2.2.2.17Division 2.2.2.17
  248. 2.2.2.18Division 2.2.2.18
  249. 2.2.2.19Division 2.2.2.19
  250. Assessment of positioning accuracy in autonomous dynamic mode.
  251. 2.2.3.1Division 2.2.3.1
  252. 2.2.3.2Division 2.2.3.2
  253. 2.2.3.3Division 2.2.3.3
  254. Movement in shadow areas, areas of intermittent reception of navigation signals and urban canyons.
  255. 2.2.4.1Division 2.2.4.1
  256. 2.2.4.2Division 2.2.4.2
  257. 2.2.4.3Division 2.2.4.3
  258. Cold start time to first fix test.
  259. 2.2.5.1Division 2.2.5.1
  260. 2.2.5.2Division 2.2.5.2
  261. 2.2.5.3Division 2.2.5.3
  262. 2.2.5.4Division 2.2.5.4
  263. 2.2.5.5Division 2.2.5.5
  264. 2.2.5.6Division 2.2.5.6
  265. 2.2.5.7Division 2.2.5.7
  266. 2.2.5.8Division 2.2.5.8
  267. 2.2.5.9Division 2.2.5.9
  268. Test of re-acquisition time of tracking signals after block out of 60 seconds.
  269. 2.2.6.1Division 2.2.6.1
  270. 2.2.6.2Division 2.2.6.2
  271. 2.2.6.3Division 2.2.6.3
  272. 2.2.6.4Division 2.2.6.4
  273. 2.2.6.5Division 2.2.6.5
  274. 2.2.6.6Division 2.2.6.6
  275. 2.2.6.7Division 2.2.6.7
  276. Test of GNSS receiver sensitivity in cold start mode, tracking mode, and re-acquisition scenario.
  277. 2.2.7.1Division 2.2.7.1
  278. 2.2.7.2Division 2.2.7.2
  279. 2.2.7.3Division 2.2.7.3
  280. 2.2.7.4Division 2.2.7.4
  281. 2.2.7.5Division 2.2.7.5
  282. 2.2.7.6Division 2.2.7.6
  283. 2.2.7.7Division 2.2.7.7
  284. 2.2.7.8Division 2.2.7.8
  285. 2.2.7.9Division 2.2.7.9
  286. 2.2.7.10Division 2.2.7.10
  287. 2.2.7.11Division 2.2.7.11
  288. 2.2.7.12Division 2.2.7.12
  289. 2.2.7.13Division 2.2.7.13
  290. Annex VII: In-vehicle system self-test
  291. Requirements
  292. 1.1Division 1.1
  293. Performance requirements
  294. 1.2.1Division 1.2.1
  295. 1.2.2Division 1.2.2
  296. 1.2.3Division 1.2.3
  297. 1.2.3.1Division 1.2.3.1
  298. 1.2.3.2Division 1.2.3.2
  299. Documentation requirements
  300. 1.3.1Division 1.3.1
  301. Test procedure
  302. Self-test function verification test
  303. 2.1.1Division 2.1.1
  304. 2.1.2Division 2.1.2
  305. 2.1.3Division 2.1.3
  306. 2.1.4Division 2.1.4
  307. 2.1.5Division 2.1.5
  308. Modification of type of 112-based eCall in-vehicle system or STU
  309. 3.1Division 3.1
  310. Annex VIII: Technical requirements and test procedures related to privacy and data protection
  311. Part I: Procedure for verifying the lack of traceability of an eCall in-vehicle system or STU
  312. Purpose
  313. 1.1Division 1.1
  314. Requirements
  315. 2.1Division 2.1
  316. 2.2Division 2.2
  317. Test procedure
  318. 3.1Division 3.1
  319. 3.2Division 3.2
  320. 3.2.1Division 3.2.1
  321. 3.2.2Division 3.2.2
  322. 3.2.3Division 3.2.3
  323. 3.2.4Division 3.2.4
  324. Assessment
  325. 4.1Division 4.1
  326. 4.2Division 4.2
  327. Part II: Procedure for verifying the length of time an eCall log file is stored by the eCall in-vehicle system or STU
  328. Purpose
  329. 1.1Division 1.1
  330. 1.2Division 1.2
  331. Requirements
  332. 2.1Division 2.1
  333. Test conditions
  334. 3.1Division 3.1
  335. 3.2Division 3.2
  336. Test Method
  337. 4.1Division 4.1
  338. 4.2Division 4.2
  339. Assessment
  340. 5.1Division 5.1
  341. 5.2Division 5.2
  342. Part III: Procedure for verifying the automatic and continuous removal of data in the internal memory of an eCall in-vehicle system or STU
  343. Purpose
  344. 1.1Division 1.1
  345. 1.2Division 1.2
  346. Requirements
  347. 2.1Division 2.1
  348. Test conditions
  349. 3.1Division 3.1
  350. 3.2Division 3.2
  351. Test Method
  352. 4.1Division 4.1
  353. Assessment
  354. 5.1Division 5.1
  355. 5.2Division 5.2
  356. Part IV: Procedure for verifying the non- exchange of personal data between an eCall in-vehicle system or STU and third party services systems
  357. Purpose
  358. 1.1Division 1.1
  359. Requirements
  360. 2.1Division 2.1
  361. Performance requirements
  362. 2.2.1Division 2.2.1
  363. 2.2.2Division 2.2.2
  364. Test procedure
  365. 3.1Division 3.1
  366. 3.2Division 3.2
  367. 3.2.1Division 3.2.1
  368. 3.2.2Division 3.2.2
  369. 3.2.3Division 3.2.3
  370. 3.2.4Division 3.2.4
  371. 3.2.5Division 3.2.5
  372. 3.3Division 3.3
  373. 3.3.1Division 3.3.1
  374. 3.3.2Division 3.3.2
  375. 3.3.3Division 3.3.3
  376. 3.4Connection procedures
  377. Annex IXClasses of vehicles referred to in Article 2
  378. Annex XProcedure for the extension of GB type-approvals granted in accordance with this Regulation to 112-based eCall in-vehicle systems operating over circuit-switched mobile networks