BS EN 16454:2015 – TC:2020 Edition
$280.87
Tracked Changes. Intelligent transport systems. ESafety. ECall end to end conformance testing
Published By | Publication Date | Number of Pages |
BSI | 2020 | 597 |
This European Standard defines the key actors in the eCall chain of service provision as: 1) In-Vehicle System (IVS)/vehicle, 2) Mobile network Operator (MNO), 3) Public safety assistance point [provider](PSAP), in some circumstances may also involve: 4) Third Party Service Provider (TPSP), and to provide conformance tests for actor groups 1) – 4). NOTE Conformance tests are not appropriate nor required for vehicle occupants, although they are the recipient of the service. The Scope covers conformance testing (and approval) of new engineering developments, products and systems, and does not imply testing associated with individual installations in vehicles or locations.
PDF Catalog
PDF Pages | PDF Title |
---|---|
329 | Contents Page |
336 | European foreword |
337 | Introduction |
338 | 1 Scope 2 Normative references |
339 | 3 Terms and definitions |
344 | 4 Symbols and abbreviations |
346 | 5 Conformance 5.1 General 5.2 General conditions |
347 | 6 General overview of the eCall transaction for pan-European eCall |
351 | 7 How to use this Standard 7.1 Layout and procedures |
352 | 7.2 System under test |
353 | 7.3 Accelerated test procedures 7.4 Accelerated test procedures for IVSs 7.4.1 Accelerated test procedures for all types of PE eCall IVS |
355 | 7.4.2 Additional accelerated test procedures for PE eCall only IVS 7.5 Accelerated test procedures for MNOs |
356 | 7.6 Accelerated test procedures for PSAPs – PE eCall |
357 | 7.7 Accelerated test procedures for PSAPs – TPS-eCall 7.8 Accelerated test procedures for TPSPs |
358 | 8 Requirements 8.1 Requirements – General objectives 8.1.1 State transitions |
368 | 8.1.2 Classification of testing |
370 | 8.1.3 CTP naming conventions |
371 | 8.1.4 CTP naming convention for IVS conformance tests 8.2 CTP structure |
373 | 9 Conformance test requirements for in-vehicle user equipment and systems (IVS) 9.1 Conformance test requirements for in-vehicle user equipment and systems for Pan European eCall 9.2 Test objectives and purposes 9.3 Classification of testing and referenced tests for in-vehicle user equipment for Pan European eCall IVS 9.3.1 Taxonomy of testing 9.3.2 Referenced tests 9.3.2.1 Pre eCall including conformance to ETSI In-vehicle network access device tests |
374 | 9.3.2.2 In-vehicle eCall system conformance tests 9.4 State transition conformance tests for in-vehicle equipment and system to comply to Standards for pan European eCall 9.4.1 Conformance requirement 9.4.2 Use case test objectives by stage 9.4.2.1 NAD Conformance tests in accordance with ETSI TS 102 936-1 ETSI TS 102 936-2 (NAD) 9.4.2.2 Ignition OFF I-OFF 9.4.2.3 Ignition ON (no eCall) including power-up I-ON 9.4.2.4 Trigger TRG |
375 | 9.4.2.5 eCall initiation ECI 9.4.2.6 eCall in progress ECP 9.4.2.7 eCall Cleardown CLR 9.4.2.8 Post eCall and Call-back CLB |
377 | 9.4.3 CTP 1.1.0.1 Conformance to ETSI TS 102 936-1 and ETSI TS 102 936-2 – PE eCall IVS |
378 | 9.4.4 CTP 1.1.0.2 Test for conformance to valid SIM/USIM – PE eCall |
379 | 9.4.5 CTP 1.1.0.3 Automatic eCall triggering does not occur when ignition OFF – PE eCall IVS |
380 | 9.4.6 CTP 1.1.1.1 Power on and self test – PE eCall IVS |
381 | 9.4.7 CTP 1.1.2.1 eCall automatically activated – PE eCall IVS |
382 | 9.4.8 CTP 1.1.2.2 Automatically triggered eCall in progress was not disconnected upon a new eCall trigger – PE eCall IVS |
383 | 9.4.9 CTP 1.1.2.3 Post-side-crash performance of automatic trigger – IVS |
384 | 9.4.10 CTP 1.1.2.4 Post-frontal-crash performance of automatic trigger – IVS |
385 | 9.4.11 CTP 1.1.2.5 Performance of automatic trigger – different crash types – IVS |
386 | 9.4.12 CTP 1.1.3.1 eCall manually activated – PE eCall IVS |
387 | 9.4.13 CTP 1.1.3.2 Manually triggered eCall in progress was not disconnected upon a new eCall trigger – PE eCall IVS |
388 | 9.4.14 CTP 1.1.4.1 Test eCall activated – PE eCall IVS |
389 | 9.4.15 CTP 1.1.5.1 Network registration – PE eCall IVS |
390 | 9.4.16 CTP 1.1.5.2 Manual termination of eCall by vehicle occupants not allowed (automatically triggered eCall) – PE eCall IVS |
391 | 9.4.17 CTP 1.1.5.3 Manual termination of eCall by vehicle occupants not allowed (manually triggered eCall) – PE eCall IVS |
392 | 9.4.18 CTP 1.1.5.4 Automatically triggered eCall in progress was not disconnected when ignition is switched to OFF – PE eCall IVS |
393 | 9.4.19 CTP 1.1.5.5 Manually triggered eCall in progress was not disconnected when ignition is switched to OFF – PE eCall IVS |
394 | 9.4.20 CTP 1.1.5.6 Priority over conflicting communication – PE eCall IVS |
395 | 9.4.21 CTP 1.1.5.7 Network registration is re-tried when network registration attempt was not successful – PE eCall IVS 9.4.22 CTP 1.1.6.1 Mute IVS and vehicle audio – PE eCall IVS |
396 | 9.4.23 CTP 1.1.7.1 Set-up TS12 call with eCall identifier (flag) set to ‘automatic’ – PE eCall IVS |
397 | 9.4.24 CTP 1.1.8.1 Set-up TS12 call with eCall identifier (flag) set to ‘manual’ – PE eCall IVS |
398 | 9.4.25 CTP 1.1.9.1 Set-up TS11 call to test number – PE eCall IVS |
399 | 9.4.26 CTP 1.1.10.1 eCall is attempted when no networks are available (limited service condition) – PE eCall IVS |
400 | 9.4.27 CTP 1.1.10.2 Re-dial attempt completed within 2 minutes after eCall is dropped – PE eCall IVS |
401 | 9.4.28 CTP 1.1.10.3 Duration of eCall Initiation signal – PE eCall IVS |
402 | 9.4.29 CTP 1.1.11.1 Send MSD with indicator set to ‘Automatically Initiated eCall’ (AleC) – PE eCall IVS |
403 | 9.4.30 CTP 1.1.12.1 Send MSD with indicator set to ‘Manually Initiated eCall’ (MleC) – PE eCall IVS |
404 | 9.4.31 CTP 1.1.13.1 Send MSD with indicator set to ‘Test Call’ – PE eCall IVS |
405 | 9.4.32 CTP 1.1.14.1 Verify MSD transfer – PE eCall IVS |
406 | 9.4.33 CTP 1.1.14.2 Un-mute IVS audio when AL-ACK received – PE eCall IVS |
407 | 9.4.34 CTP 1.1.15.1 Establish voice link to PSAP – PE eCall IVS |
408 | 9.4.35 CTP 1.1.15.2 MSD transfer request while eCall conversation in progress – PE eCall IVS |
410 | 9.4.36 CTP 1.1.15.3 eCall continuation when SEND MSD request not received (T5 expired) – PE eCall IVS |
411 | 9.4.37 CTP 1.1.15.4 Call continuation when AL-ACK not received (T6 expired) – PE eCall IVS |
412 | 9.4.38 CTP 1.1.15.5 MSD is transferred continuously until T7 expires and IVS reconnects loudspeaker and microphone on its expiry – PE eCall IVS |
413 | 9.4.39 CTP 1.1.16.1 Clear down call automatically – PE eCall IVS |
415 | 9.4.40 CTP 1.1.16.2 IVS clears down the eCall upon T2 expiry – PE eCall IVS |
416 | 9.4.41 CTP 1.1.16.3 IVS registers recent eCalls – PE eCall IVS |
417 | 9.4.42 CTP 1.1.17.1 Call-back allowed and able to be answered by IVS – PE eCall IVS |
418 | 9.4.43 CTP 1.1.17.2 Call-back answered by IVS in the event of abnormal termination – PE eCall IVS |
419 | 9.4.44 CTP 1.1.17.3 MSD transfer occurs upon PSAP request during call-back – PE eCall IVS |
420 | 9.4.45 CTP 1.1.17.4 Remain registered for ≥1 hr – PE eCall IVS |
421 | 9.5 State transition test scripts for in-vehicle equipment and system to comply to Standards for pan European eCall – additional tests for eCall only systems 9.5.1 General |
422 | 9.5.2 CTP 1.1.1.2 IVS does not perform registration after power-up – PE eCall only IVS 9.5.3 CTP 1.1.1.3 IVS periodically scans and maintains a list of available PLMNs – PE eCall only |
423 | 9.5.4 CTP1.1.10.4 Verify that PLMN registration procedure is executed upon initiating an eCall – PE eCall only IVS |
424 | 9.5.5 CTP 1.1.17.5 Remain registered for ≥1 hr ≤12 hr – PE eCall only IVS |
425 | 9.6 State transition conformance test requirements for in-vehicle user equipment for eCall TPS-IVS via a third party service provider 9.6.1 General 9.6.2 Test objectives and purposes 9.6.3 Taxonomy of testing and referenced tests 9.6.4 Taxonomy of testing 9.7 Use case conformance tests for in-vehicle equipment and system to comply to Standards for third party service provider eCall 9.7.1 Conformance requirement |
426 | 9.7.2 Use case test objectives by stage 9.7.2.1 Pre eCall PRE 9.7.2.2 Ignition OFF I-OFF 9.7.2.3 Ignition ON (no eCall) including power-up I-ON 9.7.2.4 Trigger TRG 9.7.2.5 eCall initiation ECI 9.7.2.6 eCall in progress ECP |
427 | 9.7.2.7 eCall Cleardown CLR 9.7.2.8 Post eCall and Call-back CLB |
428 | 9.8 State transition test scripts for TPS in-vehicle equipment and system to comply to Standards for third party services supported eCall 9.8.1 General |
429 | 9.8.2 CTP 1.2.0 Pre operation – TPS-IVS 9.8.2.1 CTP 1.2.0.1 TPS-IVS includes necessary hardware – TPS-IVS |
430 | 9.8.2.2 CTP 1.2.0.2 Protection of privacy – TPS-IVS |
431 | 9.8.3 CTP 1.2.1 Power on self test – TPS-IVS 9.8.3.1 CTP 1.2.1.1 Test conformance for indication that TPS-IVS was not functioning properly – TPS-IVS |
432 | 9.8.3.2 CTP 1.2.1.2 Test conformance for TPS-IVS is functioning properly – TPS-IVS 9.8.4 CTP 1.2.2 Automatically activate eCall – TPS-IVS 9.8.4.1 CTP 1.2.2.1 Test conformance for automatically triggered TPS-eCall sequence – TPS-IVS |
434 | 9.8.4.2 CTP 1.2.2.2 Post-side-crash performance of automatic trigger – TPS-IVS |
436 | 9.8.4.3 CTP 1.2.2.3 Post-frontal-crash performance of automatic trigger – TPS-IVS |
438 | 9.8.4.4 CTP 1.2.2.4 Performance of automatic trigger – different crash types – TPS-IVS |
439 | 9.8.4.5 CTP 1.2.2.5 Disarmed automatic TPS-eCall – TPS-IVS |
440 | 9.8.5 CTP 1.2.3 Manually activate eCall – TPS-IVS 9.8.5.1 CTP 1.2.3.1 Manually triggered TPS-eCall sequence – TPS-IVS |
442 | 9.8.5.2 CTP 1.2.3.2 Manual trigger marking and performance – TPS-IVS |
444 | 9.8.6 CTP 1.2.4 Stop conflicting communication – TPS-IVS 9.8.6.1 CTP 1.2.4.1 Priority over conflicting communication – TPS-IVS |
445 | 9.8.7 CTP 1.2.5 Establish voice link to TPSP – TPS-IVS 9.8.7.1 General 9.8.7.2 CTP 1.2.5.1 Voice call reliability – TPS-IVS |
446 | 9.8.7.3 CTP 1.2.5.2 Test conformance that a TS12 voice connection is made in the event of a failure – TPS-IVS |
447 | 9.8.7.4 CTP 1.2.5.3 Test conformance that a TS12 PE eCall is made in the event of a failure – TPS-IVS |
448 | 9.8.7.5 CTP 1.2.5.4 Running eCall sequence cannot be interrupted or terminated by – TPS-IVS |
449 | 9.8.7.6 CTP 1.2.5.5 Test conformance for limited redial attempts – TPS-IVS |
450 | 9.8.8 CTP 1.2.6 Send IVS dataset to TPSP – TPS-IVS 9.8.8.1 General 9.8.8.2 CTP 1.2.6.1 Dataset content – TPS-IVS |
452 | 9.8.8.3 CTP 1.2.6.2 Data re-transmission – TPS-IVS |
454 | 9.8.8.4 CTP 1.2.6.3 Data transmission reliability – TPS-IVS |
456 | 9.8.9 CTP 1.2.7 Establish voice link between PSAP and occupants – TPS-IVS 9.8.9.1 CTP 1.2.7.1 Establish direct bidirectional audio link between occupants and PSAP – TPS-IVS |
457 | 9.8.10 CTP 1.2.8 Cleardown call – TPS-IVS 9.8.10.1 CTP 1.2.8.1 No reconnect after termination – TPS-IVS |
458 | 9.8.11 CTP 1.2.9 Allow call-cack into vehicle – TPS-IVS 9.8.11.1 CTP 1.2.9.1 Call-back in case of disconnection – TPS-IVS |
460 | 9.8.11.2 CTP 1.2.9.2 Call-back after termination – TPS-IVS |
461 | 9.8.11.3 CTP 1.2.9.3 Automatic call-back acceptance – TPS-IVS |
463 | 10 Conformance tests for mobile network operators 10.1 Test objectives and purposes 10.1.1 General 10.1.2 Default assumptions 10.2 Taxonomy of testing and referenced tests 10.3 Use case conformance tests for mobile network operator systems to comply to Standards for pan European eCall 10.3.1 Conformance requirement 10.3.2 Use case test objectives by stage 10.3.2.1 Pre eCall including conformance to ETSI Standards deliverables |
464 | 10.3.2.2 Ignition OFF I-OFF 10.3.2.3 Ignition ON (no eCall) including power-up I-ON 10.3.2.4 Trigger TRG 10.3.2.5 eCall initiation ECI 10.3.2.6 eCall in progress ECP 10.3.2.7 eCall Cleardown CLR 10.3.2.8 Post eCall and Call-back CLB |
465 | 10.4 State transition test scripts for mobile network operators to demonstrate compliance with Pan European eCall Standards 10.4.1 General |
466 | 10.4.2 CTP 2.0.1 Keep SIMs/USIMs alive even though not in regular operation – MNO |
467 | 10.4.3 CTP 2.0.2 MNO supports general eCall relevant requirements |
468 | 10.4.4 CTP 2.0.3 Decommission SIM/USIM – MNO |
469 | 10.4.5 CTP 2.0.4 Support eCall Flag – MNO 10.4.6 CTP 2.1.1 Accept registration – Home network – MNO |
470 | 10.4.7 CTP 2.1.2 Accept registration – Roaming –MNO |
471 | 10.4.8 CTP 2.2.1.1 Receive TS12 voice call (automatically initiated) – MNO |
472 | 10.4.9 CTP 2.2.1.2 Route call to ‘most appropriate’ PSAP – MNO |
473 | 10.4.10 CTP 2.2.1.3 Provide TS12 data/caller ID – MNO |
474 | 10.4.11 CTP 2.2.2.1 Receive TS12 voice call (manual initiated) – MNO 10.4.12 CTP 2.2.3.1 Test for receiving test eCall (TS11) 10.4.13 CTP 2.2.3.2 Route call to non-emergency number – MNO |
475 | 10.4.14 CTP 2.2.3.3 Provide TS11 data – MNO 10.4.15 CTP 2.3.1 Call in progress–MNO |
476 | 10.4.16 CTP 2.4.1 Call cleardown – MNO |
477 | 10.4.17 CTP 2.5.1 Support call-back – MNO 10.4.18 CTP 2.6.1 Maintain registration for 1-12 hours – MNO 10.4.19 CTP 2.7.1 Maintain call records – MNO |
478 | 10.5 Use case conformance tests for mobile network operator systems to comply to Standards for TPS-eCall 10.5.1 Conformance requirement 10.5.2 Use case test objectives by stage 10.6 State transition test scripts for mobile network operators to demonstrate compliance with TPS-eCall Standards 10.6.1 CTP 2.11.1 MNO supports general TPS-eCall relevant requirements 10.6.2 CTP 2.11.2 Support call-back – MNO |
479 | 11 Conformance tests for PSAP systems 11.1 Test objectives and purposes 11.2 Taxonomy of testing and referenced tests 11.2.1 Taxonomy of testing 11.2.2 Referenced tests 11.3 Use case conformance tests for PSAP systems to comply to Standards for pan European eCall 11.3.1 Conformance requirement 11.3.2 Use case test objectives by stage 11.3.2.1 Pre eCall including conformance to ETSI Standards deliverables 11.3.2.2 Ignition OFF (I-OFF) 11.3.2.3 Ignition ON (no eCall) including power-up (I-ON) 11.3.2.4 Trigger (TRG) |
480 | 11.3.2.5 eCall initiation (ECI) 11.3.2.6 eCall in progress (ECP) 11.3.2.7 eCall Cleardown (CLR) 11.3.2.8 Post eCall and Call-back (CLB) 11.4 State transition conformance tests for PSAPs – PE eCall 11.4.1 General |
482 | 11.4.2 CTP 3.1.0.1 Provide MNOs with appropriate routing data – Member State/ PSAP PE eCall |
483 | 11.4.3 CTP 3.1.0.2 Maintain map geo-information – PSAP PE eCall |
484 | 11.4.4 CTP 3.1.1.1 Receive automatically initiated eCall – PSAP PE eCall |
485 | 11.4.5 CTP 3.1.1.2 Receive manually initiated eCall – PSAP PE eCall |
486 | 11.4.6 CTP 3.1.2 Receive TS12 data- Caller ID & location – PSAP PE eCall |
487 | 11.4.7 CTP 3.1.3.1 Recognise eCall and route to in-band modem – PSAP PE eCall |
488 | 11.4.8 CTP 3.1.3.2 PSAP equipment failure – PSAP PE eCall |
489 | 11.4.9 CTP 3.1.3.3 PSAP modem failure before link layer ACK is sent – PSAP PE eCall |
490 | 11.4.10 CTP 3.1.4 eCall received at in-band modem – PSAP PE eCall |
491 | 11.4.11 CTP 3.1.5.1 Validate initiation signal – PSAP PE eCall |
492 | 11.4.12 CTP 3.1.5.2 Route to operator after T4 expiration – PSAP PE eCall |
493 | 11.4.13 CTP 3.1.6 Request MSD – PSAP PE eCall |
494 | 11.4.14 CTP 3.1.7.1 Receive MSD – PSAP PE eCall |
495 | 11.4.15 CTP 3.1.7.2 Verify status bit in AL-ACK upon positive ACK– PSAP PE eCall |
496 | 11.4.16 CTP 3.1.7.3 Verify MSD transfer upon T8 expiration – PSAP PE eCall |
497 | 11.4.17 CTP 3.1.7.4 Verify transfer of corrupted MSD – PSAP PE eCall |
498 | 11.4.18 CTP 3.1.7.5 Verify PSAP behaviour when MSD format check fails– PSAP PE eCall 11.4.19 CTP 3.1.8 ACK – PSAP PE eCall |
499 | 11.4.20 CTP 3.1.9 Route voice and MSD to operator – PSAP PE eCall |
500 | 11.4.21 CTP 3.1.10 Display TS12 data and MSD to operator – PSAP PE eCall |
501 | 11.4.22 CTP 3.1.11 Decode VIN – PSAP PE eCall |
502 | 11.4.23 CTP 3.1.12 Talk to vehicle occupants – PSAP PE eCall |
503 | 11.4.24 CTP 3.1.13 Request new MSD before call cleardown – PSAP PE eCall |
504 | 11.4.25 CTP 3.1.14.1 Call cleardown – PSAP PE eCall |
505 | 11.4.26 CTP 3.1.14.2 Verify status bit in AL-ACK upon cleardown – PSAP –PE eCall |
506 | 11.4.27 CTP 3.1.15 Call-back to vehicle – PSAP PE eCall |
507 | 11.4.28 CTP 3.1.16 Request new MSD after call cleardown – PSAP PE eCall |
508 | 11.5 State transition conformance tests for PSAPs – TPS-eCall 11.5.1 General |
509 | 11.5.2 CTP 3.2.0.1 TPSP – PSAP agreement – PSAP TPS eCall |
510 | 11.5.3 CTP 3.2.0.2 Provide areas of responsibility and contact numbers to approved TPSPs –PSAP TPS-eCall 11.5.3.1 CTP 3.2.0.2.1 Provide PSAP areas of responsibility to approved TPSPs |
511 | 11.5.3.2 CTP 3.2.0.2.2 Provide PSAP contact numbers to approved TPSPs –PSAP TPS-eCall |
512 | 11.5.4 CTP 3.2.0.3 Agreement on necessary language support – PSAP TPS eCall |
513 | 11.5.5 CTP 3.2.0.4 Agree electronic data connection and provide details to approved TPSPs – PSAP TPS eCall 11.5.5.1 CTP 3.2.0.4.1 Agree method to pass emergency details to the relevant PSAP – PSAP TPS eCall |
514 | 11.5.5.2 CTP 3.2.0.4.2 PSAP provides an indicator whether they accept or not electronic data – PSAP TPS eCall |
515 | 11.5.6 CTP 3.2.0.5 Provide PSAP data addresses and security access to approved TPSPs – PSAP TPS eCall |
516 | 11.5.7 CTP 3.2.1 Receive eCall notification from TPSP (not TS12) –PSAP TPS eCall |
517 | 11.5.8 CTP 3.2.2 Route call to operator – PSAP TPS eCall |
518 | 11.5.9 CTP 3.2.3 Connection, TSD transmission, display relevant information to PSAP operator –PSAP TPS-eCall |
520 | 11.5.10 CTP 3.2.4 PSAP Operator: Talk with TPSP operator and receive relevant information – PSAP TPS eCall |
521 | 11.5.11 CTP 3.2.5 Talk to vehicle occupants – PSAP TPS-eCall |
522 | 11.5.12 CTP 3.2.6 Request new TSD before call cleardown –PSAP TPS-eCall |
523 | 11.5.13 CTP 3.2.7 Inform TPSP that call can be ended – PSAP TPS eCall |
524 | 11.5.14 CTP 3.2.8 Call cleardown with TPSP –PSAP TPS-eCall |
525 | 11.5.15 CTP 3.2.9 Call-back to TPSP – PSAP TPS-eCall |
526 | 11.5.16 CTP 3.2.10 Call-back to vehicle – PSAP TPS eCall |
527 | 11.5.17 CTP 3.2.11 Call cleardown with vehicle – PSAP TPS eCall |
528 | 12 State transition conformance tests for TPS-eCall 12.1 Related specifications and conformance requirements 12.2 TPSP general tests (applicable to both TPS-eCall responder and TPS-eCall notifier) 12.2.1 General |
530 | 12.2.2 CTP 4.0.1 Agree service level agreement and/or Standard ways of working with PSAPs – TPSP |
531 | 12.2.3 CTP 4.0.2 Receive PSAP areas of responsibility and contact numbers – TPSP |
532 | 12.2.4 CTP 4.0.3 Agree necessary language support – TPSP 12.2.4.1 CTP 4.0.3.1 Agree necessary language support for PSAP – TPSP |
533 | 12.2.4.2 CTP 4.0.3.2 Communicate language support to customers – TPSP |
534 | 12.2.5 CTP 4.0.4 Agree electronic data connection details with PSAPs – TPSP |
535 | 12.2.6 CTP 4.0.5 Evidence quality procedures – TPSP 12.2.6.1 CTP 4.0.5.1 Quality policy – TPSP |
536 | 12.2.6.2 CTP 4.0.5.2 Infrastructure availability – TPSP |
537 | 12.2.6.3 CTP 4.0.5.3 Verify appropriate training – TPSP 12.2.7 CTP 4.0.6 Verify automatic call distribution (ACD) system – TPSP |
538 | 12.2.8 CTP 4.0.7 Check link from MNO – TPSP 12.2.9 CTP 4.0.8 Deal with transmission failures – TPSP |
539 | 12.2.10 CTP 4.0.9 Update GIS – TPSP |
540 | 12.2.11 CTP 4.0.10 Protection of privacy – TPSP |
541 | 12.3 TPS-eCall responder tests – TPS-R 12.3.1 General |
542 | 12.3.2 CTP 4.1.1 Receive TPS-eCall from vehicle – TPS-R 12.3.2.1 CTP 4.1.1.1 Respond to a TPS-eCall transaction – TPS-R |
544 | 12.3.2.2 CTP 4.1.1.2 Answer call in a timely manner – TPS-R |
545 | 12.3.3 CTP 4.1.2 Process incoming call – TPS-R 12.3.3.1 CTP 4.1.2.1 Receive and route call – TPS-R |
546 | 12.3.3.2 CTP 4.1.2.2 Receive and check IVS dataset from vehicle – TPS-R |
547 | 12.3.4 CTP 4.1.3 Talk with vehicle occupants and receive relevant information – TPS-R 12.3.4.1 CTP 4.1.3.1 Determine emergency – TPS-R |
548 | 12.3.4.2 CTP 4.1.3.2 Call to vehicle if receiving data-only – TPS-R |
549 | 12.3.4.3 CTP 4.1.3.3 Call-back to vehicle if call drops – TPS-R |
550 | 12.3.5 CTP 4.1.4 Trigger PSAP notification – TPS-R 12.3.6 CTP 4.1.5 Make voice connection between vehicle and PSAP if required – TPS-R |
551 | 12.3.7 CTP 4.1.6 Confirmation received from PSAP that call with vehicle can be ended – TPS-R |
552 | 12.3.8 CTP 4.1.7 Call cleardown with vehicle – TPS-R |
553 | 12.3.9 CTP 4.1.8 Call-back to vehicle – TPS-R |
554 | 12.4 TPS-eCall notifier tests – TPS-N 12.4.1 General |
555 | 12.4.2 CTP 4.2.1 Emergency situation likely to require assistance – TPS-N 12.4.3 CTP 4.2.2 Establish contact with PSAP – TPS-N 12.4.3.1 CTP 4.2.2.1 Establish voice call to most relevant PSAP – TPS-N |
556 | 12.4.3.2 CTP 4.2.2.2 Send data electronically to PSAP – TPS-N 12.4.3.2.1 CTP 4.2.2.2.1 Send data electronically (includes MSD) to PSAP – TPS-N |
558 | 12.4.3.2.2 CTP 4.2.2.2.2 Support Standardized PSAP data interface – TPS-N |
560 | 12.4.4 CTP 4.2.3 Talk with PSAP operator and notify relevant information – TPS-N |
562 | 12.4.5 CTP 4.2.4 Establish voice link between PSAP and vehicle occupants if required by PSAP – TPS-N 12.4.5.1 CTP 4.2.4.1 Make conference call voice connection between TPSP, vehicle and PSAP if required – TPS-N |
563 | 12.4.5.2 CTP 4.2.4.2 Make voice connection between vehicle and PSAP if required – TPS-N |
564 | 12.4.6 CTP 4.2.5 Respond to electronic data update request – TPS-N 12.4.7 CTP 4.2.6 PSAP informs that call can be ended – TPS-N 12.4.8 CTP 4.2.7 Call cleardown to PSAP – TPS-N |
565 | 12.4.9 CTP 4.2.9 Call-back from PSAP – TPS-N 13 Marking, labelling and packaging 14 Declaration of patents and intellectual property |
566 | Annex A (normative) Proforma conformance test report for Pan European eCall in-vehicle system (IVS) A.1 Conformance test report A.1.1 System under test: …………………………. A.1.2 System under test identification |
567 | A.1.3 Testing environment A.1.4 Limits and reservation A.1.5 Comments |
568 | A.2 SUT conformance status A.3 Static conformance summary A.4 Dynamic conformance summary |
569 | A.5 Static conformance review report |
570 | A.6 Test campaign report |
571 | A.7 Observations |
572 | Annex B (normative) ProForma conformance test report for Third Party Service Provider In-Vehicle System (TPS-IVS) B.1 Conformance test report B.1.1 System under test: …………………………. B.1.2 System under test identification |
573 | B.1.3 Testing environment B.1.4 Limits and reservation B.1.5 Comments |
574 | B.2 SUT conformance status B.3 Static conformance summary B.4 Dynamic conformance summary |
575 | B.5 Static conformance review report |
576 | B.6 Test campaign report B.7 Observations |
577 | Annex C (normative) ProForma conformance test report for mobile network operator (MNO) C.1 Conformance test report C.1.1 System under test: …………………………. C.1.2 System under test identification |
578 | C.1.3 Testing environment C.1.4 Limits and reservation C.1.5 Comments |
579 | C.2 SUT conformance status C.3 Static conformance summary C.4 Dynamic conformance summary |
580 | C.5 Static conformance review report |
581 | C.6 Test campaign report C.7 Observations |
582 | Annex D (normative) ProForma conformance test report for public service answering point (PSAP) D.1 Conformance test report D.1.1 System under test: …………………………. D.1.2 System under test identification |
583 | D.1.3 Testing environment D.1.4 Limits and reservation D.1.5 Comments |
584 | D.2 SUT conformance status D.3 Static conformance summary D.4 Dynamic conformance summary |
585 | D.5 Static conformance review report |
586 | D.6 Test campaign report |
587 | D.7 Observations |
588 | Annex E (normative) ProForma conformance test report for third party service provider (TPS-eCall) E.1 Conformance test report E.1.1 System under test: …………………………. E.1.2 System under test identification |
589 | E.1.3 Testing environment E.1.4 Limits and reservation E.1.5 Comments |
590 | E.2 SUT conformance status E.3 Static conformance summary E.4 Dynamic conformance summary |
591 | E.5 Static conformance review report |
592 | E.6 Test campaign report E.7 Observations |
594 | Bibliography |