1、raising standards worldwideNO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAWBSI Standards PublicationRailway applications Rolling stock Intercommunication between vehicles and train/waysidePart 2: Technical contents of standardization work in the field of intercommunicationPD CL
2、C/TR 50501-2:2012National forewordThis Published Document is the UK implementation of CLC/TR 50501-2:2012. The UK participation in its preparation was entrusted by Technical CommitteeGEL/9, Railway Electrotechnical Applications, to Subcommittee GEL/9/2, Railway Electrotechnical Applications - Rollin
3、g stock.A list of organizations represented on this committee can be obtained on request to its secretary.This publication does not purport to include all the necessary provisions of a contract. Users are responsible for its correct application. The British Standards Institution 2012Published by BSI
4、 Standards Limited 2012 ISBN 978 0 580 72989 8 ICS 35.240.60; 45.020; 45.060.10Compliance with a British Standard cannot confer immunity from legal obligations.This Published Document was published under the authority of the Standards Policy and Strategy Committee on 30 September 2012.Amendments iss
5、ued since publicationDate Text affectedPUBLISHED DOCUMENTPD CLC/TR 50501-2:2012TECHNICAL REPORT CLC/TR 50501-2 RAPPORT TECHNIQUE TECHNISCHER BERICHT August 2012 CENELEC European Committee for Electrotechnical Standardization Comit Europen de Normalisation Electrotechnique Europisches Komitee fr Elek
6、trotechnische Normung Management Centre: Avenue Marnix 17, B - 1000 Brussels 2012 CENELEC - All rights of exploitation in any form and by any means reserved worldwide for CENELEC members. Ref. No. CLC/TR 50501-2:2012 E ICS 35.240.60; 45.020 English version Railway applications - Rolling stock - Inte
7、rcommunication between vehicles and train/wayside - Part 2: Technical contents of standardization work in the field of intercommunication Applications ferroviaires - Matriel roulant - Communications entre vhicules et communications sol/train - Partie 2: Contenu technique du travail de normalisation
8、dans le domaine de la communication Bahnanwendungen - Interkommunikation zwischen Fahrzeugen und Fahrweg - Teil 2: Technischer Inhalt der Normung auf dem Gebiet der Interkommunikation This Technical Report was approved by CENELEC on 2012-02-13. CENELEC members are the national electrotechnical commi
9、ttees of Austria, Belgium, Bulgaria, Croatia, Cyprus, the Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, the Netherlands, Norway, Poland, Portugal, Romania, Slovakia, S
10、lovenia, Spain, Sweden, Switzerland, Turkey and the United Kingdom. PD CLC/TR 50501-2:2012CLC/TR 50501-2:2012 - 2 Contents Page Foreword 3 1 Scope 4 2 Normative references 4 3 Terms and definitions . 4 4 Summary of results of works carried out by WG14 . 5 4.1 Proposal for a standard “reference archi
11、tecture” for vehicle intercommunication 5 4.2 Methods for functional modelling 5 4.3 Requirements for a “Functional addressing” feature 5 4.4 Requirements for a central data dictionary/repository 6 5 Data from other related activities 7 5.1 From Integrail FP6 research project . 7 5.2 From Modtrain F
12、P6 research project 9 6 Data from the sector organisations . 10 6.1 UIC Leaflet 556 BIB 2.: functional addressing for the UIC train bus . 10 6.2 UIC GSM-R functional addressing 11 6.3 Codification specified in TSI operation 17 6.4 Telematic applications TSIs 17 6.5 Existing “Railway” identifiers and
13、 codes . 20 7 Scope for standardisation topics supporting “Functional addressing” . 26 7.1 Introduction 26 7.2 Scope 26 8 Proposed structure for Functional Addressing standardisation documents . 27 8.1 Introduction 27 8.2 Part 1 Functional addressing: Requirements . 27 8.3 Part 2 Definition of an UR
14、I scheme for identification of vehicle functions 27 8.4 Part 3- URI resolution guidelines 29 8.5 Part 4 - Elementary identifiers . 30 9 Overlaps between IEC/TC9/WG43 Annex A Updates, and corrections following comments of S. Ingenhorst V3 Third draft 2009/11/16 G. Demars All Incorporation of informat
15、ion collected from InteGRail project, and sector organisations V4.1 Fourth draft 2009/12/11 G. Demars 4.4 Update after WG14 meeting #21 V4.2 G. Demars 6.2 Addition functional open coupling V4.3 Working version 2010/01/29 G.Demars various Remarks on remaining actions V4.4 Final V4 draft 2010/05/12 JL
16、 Profizi 6.4 Inserted Mr Demars paragraphs on telematics in 6.4 Submitted to WG14 approval V4.5 Final version 2011/08/18 JL Profizi 10 Re-shaping of the bibliography as Clause 10 and references marked in yellow in the text . PD CLC/TR 50501-2:2012CLC/TR 50501-2:2012 - 4 1 Scope The scope of this Tec
17、hnical Report is to summarize all available data on standardization work in the field of Intercommunication including 1. the results of work of WG B14 carried out so far, 2. data from other related activities such as the research projects MODTRAIN and INTEGRAIL, 3. data from the sector organisation
18、TMP. NOTE “TMP”, Technical Management Platform, is one of the structures created by the rail representatives associations in order to express common views on TSI open issues or standardization work programs (not active anymore). 2 Normative references The following documents, in whole or in part, ar
19、e normatively referenced in this document and are indispensable for its application. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. CLC/TR 50501-1:2007, Railway applications - Rolling sto
20、ck - Intercommunication between vehicles and train/wayside - Part 1: Data dictionary and rules for functional standardisation 3 Terms and definitions For the purposes of this document, the following terms and definitions apply. 3.1 consist train set rake of coaches single vehicle or a group of vehic
21、les which are not separated during normal operation. Note 1 to entry: A consist contains no, one or several consist networks. assembly of vehicles (may be reduced to a single vehicle), which are permanently coupled while in service, and fitted with a “vehicle communication system”, linking the devic
22、es, and providing one interface with the train level (such a communication system may be a vehicle bus, spanning over all the vehicle of the consist). Note 2 to entry: A physical consist which is not capable of data communication with other consist or ground installation is not in the scope of the R
23、eference Architecture. A consist is described by a set of static properties (as in UIC Leaflet 556 BIB 2.) 3.2 entity anything of interest (such as a person, material object, place or process) within a given domain of discourse. Note 1 to entry: An entity class is a stereotyped class used to model l
24、ong-lived information that may be persistent. An entity is said complex when it can be described by at least two other entities. Otherwise, it is called a simple entity or primitive 3.3 functional requirement an action that the target system is able to perform 3.4 functional specification specificat
25、ion of functions performed by the entities in a given application, in a manner that is independent of the technology adopted to implement the specified functions PD CLC/TR 50501-2:2012- 5 - CLC/TR 50501-2:2012 3.5 train assembly of coupled consists (may be reduced to a single consist), configured fo
26、r autonomous operation on the railway system. and in use for an operational mission; the train is a dynamic object, identified with a “train running number”, active only during its operational mission 4 Summary of results of works carried out by WG14 The main results of works carried out by WG14 so
27、far, are documented in CLC/TR 50501-1, and are summarised below: 4.1 Proposal for a standard “reference architecture” for vehicle intercommunication Functions which are in the scope of this series of standards are supported by distributed applications. Functional standardisation activities are suppo
28、rted by production of functional models. The elaboration of a functional model for a specific function of the railway system, belonging to categories STD2 and STD3 defined in the global scope of WG14, shall use a “reference architecture”. The purpose of this Reference Architecture is to support the
29、standardisation of the communication procedures between vehicles and train/wayside. To provide a common understanding among the standardisation working groups, this reference architecture includes a list of the interacting entities which are considered in the reference architecture o rolling stock e
30、ntities: train, vehicles, devices, o external entities interacting with rolling stock entities o interfaces considered in the reference architecture because they are “interoperability relevant” 4.2 Methods for functional modelling The functional modelling framework which is described is derived from
31、 MODTRAIN European project results. This framework is intended to provide a “common language” for the experts involved functional standardisation of “communication” rail vehicle functions with interoperability constraints (i.e in the scope of further standardisation works). 4.3 Requirements for a “F
32、unctional addressing” feature Functional addressing was identified as an important issue in CLC/TR 50501-1:2007, 4.3, 4.5.4, and 5.4.2. Annex B is dedicated to functional addressing in GSM-R and UIC leaflet 556. Is to be noted that GSM-R consider “functional addressing” as one of the main “railway s
33、pecific feature” which has been added to the standard GSM communication system. Requirements relative to functional addressing, already given in CLC/TR 50501-1, are a functional addressing scheme should be provided, which permits entities to be identified by a “name”, used as a “functional address”,
34、 representative of their functional roles rather than by “numbers” tied to the interface equipment they are using; use of functional addressing will include identifying on-train functions and other users performing particular roles such as train driver, passenger, train conductor, etc.; PD CLC/TR 50
35、501-2:2012CLC/TR 50501-2:2012 - 6 NOTE Communications protocols not belonging to the “application levels”, which are using functional addresses, and are necessary for the implementation of communications systems, should be specified (independently of the various functional models) in STD4, as these
36、communication systems are to be shared by several user functions. These protocols should be chosen among existing open industry standards. An important concept within the Reference Functional Architecture (defined in CLC/TR 50501-1) is dealing with how a functional element is accessed in the railway
37、 vehicle dynamic environment. Railway vehicles are mobile, and communicate with ground stations using wireless communication, which implies the existence of a ground based communication infrastructure. Reaching a functional element implies the use of communication path. It is then necessary to assoc
38、iate to each relevant element: its identification, or name; its location, or address; and a route leading to this address. The name shall not be bound to the address until a specific mapping process takes place. This mapping takes all its relevance in the railway transport context, where mobility ma
39、y imply address changes over time. The information exchange infrastructure shall guarantee: geographic independence: an entity and its functions are reachable independently of vehicle location; function binding: an entity and its functions are made available (published) in the communication network
40、as soon as a communication path is available; function discovery: a specific function of a specific entity may be discoverable upon request from a potential user (a client); 4.4 Requirements for a central data dictionary/repository The data dictionary is a central component necessary for development
41、 of consistent families of functional standards such as STD2 and STD3. Its purpose, related to the scope of WG14, is to document elements pertinent to the functional areas and essential for interoperability, to allow the reuse of element among functional areas, and to facilitate data interchange. Ma
42、in elements types are model elements, data elements, messages. Data dictionary handles metadata which provide full definition of data elements, along with their essential attributes at conceptual level. In this context, data are limited to basic information elements, which are necessary to define st
43、andard messages required for interoperability, and handled on the interfaces of the communicating entities. The central “data dictionary/model repository” shall be managed and operated by a single authority. PD CLC/TR 50501-2:2012- 7 - CLC/TR 50501-2:2012 5 Data from other related activities 5.1 Fro
44、m Integrail FP6 research project 5.1.1 Introduction Discussions took place with representatives of InteGRail subproject ICOM. Among the subjects considered by ICOM as “candidates for standardisation”, the one which is in the scope of WG 14 is “functional addressing”, used to provide interoperability
45、 for rail vehicle applications using communications. 5.1.2 Functional addressing relevant documents from INTEGRAIL 5.1.2.1 Introduction In InteGRail project (IGR), the topic is addressed in several documents. Integrail documents provided to WG14 are IGR-I-BTG-112-03 Train Onboard Addressing.doc BIB
46、3., IGR-D-BTG-111-11 Trainwide Communication.doc BIB 4., IGR-I-ALS-292-01 Concept for Symbolic Addressing in ICOM.ppt BIB 5., IGR-I-SIE-259-01 5.3.4 Symbolic Addressing in ICOM BIB 6., IGR-I-INR-033-01 Train to ground addressing scenario.ppt BIB 7., IGR-I-ALS-240-02 ICOM general approach for address
47、ing trains.doc BIB 8. 5.1.2.2 Train on board addressing Document reference: IGR-I-BTG-112-03 BIB 3. Summary provided in the referenced document: This document defines an overall addressing scheme for the on board train devices supporting the integration of TCMSs inside the IGRIS architecture. Target
48、s of the addressing scheme are the definition of the rules, how distributed resources of the TCMS can be identified, and the basis for the communication protocols which shall provide access to these resources. Clause 2 in this IGR document is dedicated to “Addressing” (52 pages): Subclause 2.2 is de
49、dicated to “functional addressing” (22 pages); Subclause 2.3 is dedicated Network addressing; Subclause 2.5 is dedicated to address resolution. Relevant requirements are found in the following paragraphs of this document: Subclause 2.1, Hierarchical addressing scheme; Subclause 2.2, Functional addressing: o Subclause 2.2.1, Basic concept; o Subclause 2.2.2, IPTCS Universal resource identifier; PD CLC/TR 50501-2:2012CLC/TR 50501-2:2012 - 8 o Subclause 2.2.3, IPT-URI Direct Identifier; o
