IT- tillämpningar inom transport

In respect of pan European eCall (operating requirements defined in EN 16072), this document defines the high level application protocols, procedures and processes required to provide the eCall service via a packet switched wireless communications network using IMS (IP Multimedia Subsystem) and wireless access (such as LTE, NR and their successors). This document assumes support of eCall using IMS over packet switched networks by an IVS and a PSAP and further assumes that all PLMNs available to an IVS at the time an eCall or test eCall is initiated are packet switched networks. Support of eCall where eCall using IMS over packet switched networks is not supported by an IVS or PSAP is out of scope of this document. At some moment in time packet switched networks will be the only Public Land Mobile Networks (PLMN) available. However as long as GSM/UMTS PLMNs are available (Teleservice 12/TS12) ETSI TS 122 003 will remain operational. Both the use of such PLMNs and the logic behind choosing the appropriate network in a hybrid situation (where both packet-switched and circuit-switched networks are available) are out of scope of this document. NOTE 1 The objective of implementing the pan-European in-vehicle emergency call system (eCall) is to automate the notification of a traffic accident, wherever in Europe, with the same technical standards and the same quality of services objectives by using a PLMN (such as ETSI prime medium) which supports the European harmonized 112/E112 emergency number (TS12 ETSI TS 122 003 or IMS packet switched network) and to provide a means of manually triggering the notification of an emergency incident. NOTE 2 HLAP requirements for third party services supporting eCall can be found in EN 16102. This document makes reference to those provisions but does not duplicate them.

This document defines the key actors in the eCall chain of service provision using IMS over packet switched networks (such as LTE/4G) as: 1) In-vehicle system (3.20) (IVS)/vehicle, 2) Mobile network Operator (MNO), 3) Public safety answering point (3.27) (PSAP), and to provide conformance tests for actor groups 1) - 3). NOTE 1 Conformance tests are not appropriate nor required for vehicle occupants (3.36), although they are the recipient of the service. NOTE 2 Third party eCall systems (TPS eCall) are not within the scope of this deliverable. This is because the core TPS-eCall (3.32) standard (EN 16102) does not specify the communications link between the vehicle and the TPS service provider (3.29). NOTE 3 These conformance tests are based an the appropriate conformance tests from EN 16454 which was published before Internet Protocol multimedia Systems (IMS) packet switched networks were available. This deliverable therefore replicates the appropriate tests from EN 16454 (and acknowledge their source); adapt and revise Conformance Test Protocols (CTP) from EN 16454 to an IMS paradigm; or provide new additional tests that are required for the IMS paradigm. Some 14 112-eCall (Pan European eCall) tests provided in EN 16454 are specific to GSM/UMTS circuit switched communications and not appropriate for the IMS paradigm and are therefore excluded from this deliverable. This document therefore provides a suite of ALL conformance tests for IVS equipment, MNO's, and PSAPS, required to ensure and demonstrate compliance to CEN/TS 17184. NOTE 4 Because in the event of non-viability or non-existence of an IMS supporting network at any particular time/location, IMS-eCall systems revert to CS networked eCall systems eCall via GSM/UMTS, IVS and PSAPs need to support, and prove compliance to both IMS and CS switched networks. 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.

1.1 In Scope The EN 9300-5xx series specifies the methods for long term archiving and retrieval of MBSE data represented as digital models. The characterization of models that are considered in scope of this document and the MBSE process use cases include: - product or system design requirements models; - functional architecture models; - logical architecture models (system structure, arrangement, connectivity, software allocations and controls, and part relationships); - numerically-based system analysis and simulation models, generally regulated 1D control loop models featuring system components and transport elements (tubing, piping, signalling, software); - verification and validation of requirements; - protocol dependent signal or communication networks; - multi-model linking and system parametric models; - system trade study models; - the solution architecture models and data that are needed to implement the system and generate system engineering data for downstream designs. 1.2 Out of Scope The EN 9300-5xx series does not address the original product model design process, or a specific configuration management process for the LOTAR archive. It does not address models depicting part specific technical data (physical materials or detail part standards). It is assumed that these archiving processes are within the scope of other parts of the EN 9300 series such as the 1xx series for CAD, the 2xx series for Product Data Management (PDM) data, or by applying existing alternative industry standards, or existing company business procedures. Typical models and capabilities considered out of scope of this document include: - physical spatial models or composite structures (as described by other LOTAR Parts); - Finite Element and CFD models (as described by other LOTAR Parts); - Product Data Management models (as described by other LOTAR Parts); - electrical circuit boards, or physical wiring parts or systems (described by other LOTAR Parts or standards); - the software development process and software models that are outside of the context of software parts, behaviours, or functions that represent software code within a model; - how to preserve property and access rights, or government acquisition-regulatory controls; - new standards, or major revisions to existing MBSE standards that were not available or applicable prior to the publication of this document.