Sökning - 10 resultat för 'TK 255'

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.

This document is composed of the following data packages: 

— Driver; 

— Driver Schedule; 

— Rostering; 

— Personnel Disposition; 

— Driver Control Action. 

This document itself is composed of the following parts: 

— main document representing the data model for the concepts shared by the different domains 

covered by Transmodel (normative); 

— Annex A containing the data dictionary and attribute tables, i.e., the list of all the concepts presented 

in the main document together with their definitions (normative); 

— Annex B presenting the model evolution (informative). 

— Annex C, providing details of the significant technical changes between this document and EN 12896

7:2019 (informative)

This document incorporates the following main data packages:

— Dated Production Components;

— Call;

— Dated Call;

— Production Plan;

— Detecting & Monitoring;

— Situation;

— Messaging;

— Control Action;

— Operational Event & Incident;

— Facility Monitoring & Availability;

— Occupancy.

It is composed of the following parts:

— main document representing the data model for the concepts shared by the different domains covered by Transmodel (normative);

— Annex A containing the data dictionary and attribute tables, i.e. the list of all the concepts presented in the main document together with their definitions (normative);

— Annex B presenting the model evolution (informative);

— Annex C detailing the mapping to DATEX-II and SIRI (informative).

— Annex D, providing details of the significant technical changes between this document and EN 12896-4:2019 (informative).

This document entitled “Public transport – Reference data model – Part 5: Fare Management” is 

composed of the following data packages: 

— Fare Structure; 

— Access Right Assignment; 

— Fare Pricing; 

— Sales Description; 

— Sales Transaction; 

— Fare Roles; 

— Validation and Control; 

— Explicit Frames for Fares. 

This document itself is composed of the following parts: 

— Main document representing the data model for the concepts shared by the different domains 

covered by Transmodel (normative); 

— Annex A, containing the data dictionary and attribute tables, i.e., the list of all the concepts presented 

in the main document together with the definitions (normative); 

— Annex B, presenting the model evolution (informative). 

— Annex C, providing details of the significant technical changes between this document and EN 12896

5:2019 (informative)

The document incorporates the following main data packages: 

— Trip Description; 

— Passenger Information Queries. 

It is composed of the following parts: 

— main document representing the data model for the concepts shared by the different fare domains 

covered by Transmodel (normative); 

— Annex A, containing the data dictionary and attribute tables, i.e. the list of all the concepts presented 

in the main document together with the definitions (normative); 

— Annex B presenting the model evolution (informative). 

— Annex C, providing details of the significant technical changes between this document and 

EN 12896-6:2019 (informative).

The present document is composed of the following data packages:

— journey and Interchange;

— vehicle Journey Assignment;

— journey Times;

— block and Vehicle Service;

— dated Journey;

— explicit Frame.

This document itself is composed of the following parts:

— main document representing the data model for the concepts shared by the different domains covered by Transmodel (normative);

— Annex A containing the data dictionary and attribute tables, i.e. the list of all the concepts presented in the main document together with their definitions (normative);

— Annex B presenting the model evolution (informative);

— Annex C, providing details of the significant technical changes between this document and EN 12896 1:2015 (informative)

This document incorporates the following main data packages:

— Network Description;

— Fixed Object;

— Tactical Planning Components;

— Explicit Frame.

It is composed of the following parts:

— main document representing the data model for the concepts shared by the different domains covered by Transmodel (normative);

— Annex A containing the data dictionary and attribute tables, i.e. the list of all the concepts presented in the main document together with their definitions (normative);

— Annex B presenting the model evolution (informative).

— Annex C, providing details of the significant technical changes between this document and EN 12896-2:2016 (informative). 

 ISO 14819-1 describes the ALERT-C protocol concept and message structure used to achieve densely coded messages to be carried in the RDS-TMC feature. This document specifies the ‘Events List’ to be used in coding those messages.

This document incorporates data structures used by all other data domains of Transmodel. It is composed of the following data packages:

versions and validity; 

responsibility; 

generic framework; 

reusable components; 

explicit frames referring to generic data. 

The data structures represented in this part are either generic patterns that can be explicitly reused in 

other domains (e.g., a generic model for version frames, a generic grouping mechanism, etc.) or are 

referenced by different other parts (e.g., service calendar model). 

This document itself is composed of the following parts: 

main document representing the data model for the concepts shared by the different domains covered by Transmodel (normative);

Annex A containing the data dictionary and attribute tables, i.e., the list of all the concepts 

present in the main document, together with their definitions (normative);  

Annex B, indicating the data model evolutions (informative), 

Annex C, presenting the Transmodel development history (informative), 

Annex D, describing all conventions, methodology and notations for conceptual modelling (informative), 

Annex E, providing a clear overview to help readers understand the core principles, structure, and purpose of Transmodel (informative), 

Annex F, providing information on the Functional domains and Modes of operation (informative). 

Annex G, providing details of the significant technical changes between this document and EN 12896-1:2015 (informative).