1、DRAFT FOR DEVELOPMENTDD CEN/TS 13149-3:2007Public transport Road vehicle scheduling and control systems Part 3: WorldFIP message contentICS 43.020; 35.240.60; 43.080.20; 45.060.01g49g50g3g38g50g51g60g44g49g42g3g58g44g55g43g50g56g55g3g37g54g44g3g51g40g53g48g44g54g54g44g50g49g3g40g59g38g40g51g55g3g36g
2、54g3g51g40g53g48g44g55g55g40g39g3g37g60g3g38g50g51g60g53g44g42g43g55g3g47g36g58DD CEN/TS 13149-3:2007This Draft for Development was published under the authority of the Standards Policy and Strategy Committee on 31 August 2007 BSI 2007ISBN 978 0 580 54465 1National forewordThis Draft for Development
3、 is the UK implementation of CEN/TS 13149-3:2007.This publication is not to be regarded as a British Standard.It is being issued in the Draft for Development series of publications and is of a provisional nature. It should be applied on this provisional basis, so that information and experience of i
4、ts practical application can be obtained.Comments arising from the use of this Draft for Development are requested so that UK experience can be reported to the European organization responsible for its conversion to a European standard. A review of this publication will be initiated not later than 3
5、 years after its publication by the European organization so that a decision can be taken on its status. Notification of the start of the review period will be made in an announcement in the appropriate issue of Update Standards.According to the replies received by the end of the review period, the
6、responsible BSI Committee will decide whether to support the conversion into a European Standard, to extend the life of the Technical Specification or to withdraw it. Comments should be sent to the Secretary of the responsible BSI Technical Committee at British Standards House, 389 Chiswick High Roa
7、d, London W4 4AL.The UK participation in its preparation was entrusted to Technical Committee EPL/278, Road transport informatics.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 provision
8、s of a contract. Users are responsible for its correct application.Amendments issued since publicationAmd. No. Date CommentsTECHNICAL SPECIFICATIONSPCIFICATION TECHNIQUETECHNISCHE SPEZIFIKATIONCEN/TS 13149-3July 2007ICS 35.240.60; 43.080.20; 45.060.01English VersionPublic transport - Road vehicle sc
9、heduling and control systems -Part 3: WorldFIP message contentTransports publics - Systmes dordonnancement et decontrle des vhicules routiers - Partie 3 : Contenu demessages WorldFIPffentlicher Verkehr - Straenfahrzeuge Planungs- undSteuerungssysteme - Teil 3: WORLDFIP NachrichteninhaltThis Technica
10、l Specification (CEN/TS) was approved by CEN on 5 September 2006 for provisional application.The period of validity of this CEN/TS is limited initially to three years. After two years the members of CEN will be requested to submit theircomments, particularly on the question whether the CEN/TS can be
11、 converted into a European Standard.CEN members are required to announce the existence of this CEN/TS in the same way as for an EN and to make the CEN/TS availablepromptly at national level in an appropriate form. It is permissible to keep conflicting national standards in force (in parallel to the
12、CEN/TS)until the final decision about the possible conversion of the CEN/TS into an EN is reached.CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Cyprus, Czech Republic, Denmark, Estonia, Finland,France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuani
13、a, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal,Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and United Kingdom.EUROPEAN COMMITTEE FOR STANDARDIZATIONCOMIT EUROPEN DE NORMALISATIONEUROPISCHES KOMITEE FR NORMUNGManagement Centre: rue de Stassart, 36 B-1050 Brussels 2007 CEN All
14、 rights of exploitation in any form and by any means reservedworldwide for CEN national Members.Ref. No. CEN/TS 13149-3:2007: E2 Contents Page Foreword4 Introduction .4 1 Scope 4 2 Normative references 5 3 Terms and definitions .5 4 Vehicle related identifiers and numbers .5 4.1 Vehicle operation id
15、entifiers and numbers.6 4.2 Fare terms and related identifiers and numbers 10 5 Requirements.11 5.1 Hardware preferences .11 5.2 Devices in a complex network11 5.3 Station numbers.12 5.4 Bus arbiter modes .13 5.5 Physical layer.13 5.5.1 Bit rates.13 5.5.2 Bus connector13 5.5.3 Bus cable 13 5.6 Data
16、modelling .13 5.6.1 General13 5.6.2 Text structure.14 5.6.3 Plain text .14 5.6.4 XML formatted text 14 5.7 Object dictionary15 5.7.1 Overview of object dictionary entries15 5.7.2 Detailed Specification of Process Data Units .15 Annex A (informative) Device profiles.44 A.1 Definitions 44 A.2 Device P
17、rofile Model47 A.2.1 Device General Structure47 A.2.2 Physical Node Interface 50 A.2.3 Logical Node Interface 51 A.2.4 Function Block Interface.53 A.2.5 Exchange Block Interface .57 A.2.6 General Function Block Type.62 A.3 Overview of Device Profiles64 A.3.1 Definitions 64 A.3.2 Profiles Positioning
18、 .66 A.3.3 Profiles Characteristics.67 Annex B (informative) Example of Simple Network Application 68 B.1 Simple Network Application .68 B.1.1 Introduction68 B.1.2 List of Stations.68 B.2 Bus Arbitration.68 B.2.1 Start-up and Election Timeouts68 B.2.2 Bus Arbiter Priority69 B.2.3 Micro Cycle.70 B.2.
19、4 Macro Cycle71 B.3 Virtual Device Profiles.71 CEN/TS 13149-3:20073 B.3.1 Mapping of Virtual Device, Physical Device and Process Data Units71 B.3.2 Process Data Unit Producers and Consumers.75 Annex C (informative) Examples of Device Descriptions .78 C.1 Device Description Example 1 .78 C.2 Device D
20、escription Example 2 .80 Bibliography81 CEN/TS 13149-3:20074 Foreword This document CEN/TS 13149-3:2007 has been prepared by Technical Committee CEN/TC 278 “Road transport and traffic telematics”, the secretariat of which is held by NEN. According to the CEN/CENELEC Internal Regulations, the nationa
21、l standards organizations of the following countries are bound to announce this Technical Specification: Austria, Belgium, Bulgaria, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway
22、, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and United Kingdom. Introduction This Technical Specification is intended to be developed into part 3 of EN 13149, which gives rules for on-board data transmission systems. This part 3 together with part 1 and part 2 of EN 1
23、3149 describes a complete solution independent from part 4, part 5 and part 6. This document uses terms which are already used in other standards e.g. EN 12896 Road transport and traffic telematics - Public transport - Reference data model, when applicable. 1 Scope This Technical Specification speci
24、fies the choice and the general applications rules of an onboard data transmission bus between the different equipment for service operations and monitoring of the fleet. This applies to equipment installed onboard buses, trolley-buses and tramways only as part of a bus fleet operation. It excludes
25、tramways when they are operated as part of a train, subway or metro operation. This equipment includes operation aid systems, automatic passenger information systems, fare collection systems, etc. The equipment directly related to the safety-related functioning of the vehicle (propulsion management,
26、 brake systems, door opening systems, etc.) are excluded from the scope of the present standard and are dealt with in other standardisation bodies. For the described application two bus systems are standardised. Part 1 to part 3 of EN 13149 describe the WorldFIP bus system and part 4 to part 6 descr
27、ibe the CANopen bus system. There is no ranking between the two bus systems. The present Technical Specification covers the link between equipment inside a single vehicle. Although it could be applied to multiple vehicles, this application is not explicitly covered by this standard. Part 1 of EN 131
28、49 specifies the WorldFIP-based network. This specification describes the general architecture in terms of hierarchical layers according to the ISO reference model for Open Systems Interconnection (OSI) specified in ISO 7498. Part 2 of EN 13149 specifies in detail the connectors and the connector pi
29、n assignment and the cabling. Part 3 (this Technical Specification) specifies in detail the application profiles for a simple network. CEN/TS 13149-3:20075 2 Normative references The following referenced documents are indispensable for the application of this document. For dated references, only the
30、 edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. EN 12896:2006, Road transport and traffic telematics - Public transport - Reference data model EN 13149-1; Public transport - Road vehicle scheduling and control systems
31、- Part 1: WORLDFIP definition and application rules for onboard data transmission EN 13149-2; Public transport - Road vehicle scheduling and control systems - Part 2: WORLDFIP cabling specifications 3 Terms and definitions For the purposes of this document, the terms and definitions given in EN 1289
32、6:2006 apply. 4 Vehicle related identifiers and numbers 4.1 General The Vehicle ID is assigned uniquely by the system designer to the vehicle. Usually it refers to the vehicle ID containing the number given inside of the main computer or the number is coded by a fixed connector at the main computer
33、(see Figure 1: x). The Body ID assigned by the system designer refers to the body ID containing the readable identification on the vehicle body. Usual this text is printed on the vehicle body (see Figure 1: y). The Radio ID assigned by the system designer refers to the radio ID containing the textua
34、l radio address of the bus. This address is necessary for selective calls to this bus (see Figure 1: z). Figure 1 Vehicle related identifiers and numbers CEN/TS 13149-3:20076 4.2 Vehicle operation identifiers and numbers The Garage ID assigned by the system designer refers to the garage ID object co
35、ntaining the textual description of the depot or garage, where a vehicle is going to be parked during the night (see Figure 2). The Block ID assigned by the system designer indicates the work of a vehicle from the time it leaves a parking point (depot, garage) after parking until its next return to
36、park at a parking point. Any subsequent departure from a parking point after parking marks the start of a new block. A block should consist of one or several lines (see Figure 2). The Block ID refers to the Block ID object containing the textual description of the block. The Line ID assigned by the
37、system designer refers to the Line ID object containing the textual or numerical name of the line, which the public knows it by. A line should consist of a single route or a group of routes. Key Bz = Block z Lx = Line x Gi = Garage i Figure 2 - Non-closed and closed block A route is an ordered list
38、of points defining one single path through the road (or rail) network. Stop points, timing points and points of other types should be used to define this path uniquely. The route number is related to a line (see Figure 3). The Stop Point ID assigned by the system designer refers to the Stop Point ID
39、 object representing uniquely a stop point within a transportation network (see Figure 3). The Destination Number is the reference to the route destination. The number can differ from Stop Point ID (see Figure 3). The number of running in route representation is the Running Stop Point Number within
40、a route (see Figure 3). CEN/TS 13149-3:20077 Key LiLine i DnDestination number n RxRoute number x in Line i SPy= Stop Point Identifier y Nz= running Stop Point Number z in the route Figure 3 - Definition of a line The Journey Number refers to a journey (between one terminus to another terminus) rela
41、ted to a given time or time table (see Figure 4). CEN/TS 13149-3:20078 Key Ri = route number Ji= journey number t = time 1 Departure 2 Terminus Figure 4 - Definition of a journey The Route Destination ID identifies a unique route and line. With this identifier the path and the rail track of this lin
42、e/route is defined for a vehicle. For example, this is used for the controlling of rail switches in the track (see Figure 5). CEN/TS 13149-3:20079 Key Lx= Line ID x Ri= Route number I Dj = Destination number RDn= Route destination ID Figure 5 - Description of the use of Route Destination ID CEN/TS 1
43、3149-3:200710 4.3 Fare terms and related identifiers and numbers The Route Segment Number indicates a set of consecutive links on a given route and is unique for a fare zone (see Figure 6). The fare zone indicates the current Fare Zone Number (see Figure 6). The Previous Fare Zone Number indicates t
44、he number of the last/previous crossed fare zone (see Table 1). The Previous Route Segment Number is the number of the last/previous crossed route segment (see Table 1). Key Gi = Garage i Lj= Line j Zn= Fare zone n RSx= Route segment x Pz= Vehicle position z Figure 6 - Fare terms and related identif
45、iers and numbers Table 1 - Contents of the objects at the different vehicle positions Positions P1P2P3P4Fare zone Z1Z1Z2Z2Route segment RS1RS2RS1RS2Previous fare zone - - Z1Z1Previous route segment - RS1RS2RS1NOTE In this document, a Fare Stage Number is a stop point on a route beyond which an incre
46、ment in the fare value occurs. CEN/TS 13149-3:200711 5 Requirements 5.1 Hardware preferences There is a WorldFip convention to characterise standard physical device profiles that contain specific applications and virtual devices, but this is beyond the present scope of this part of the standard. The
47、 aim here is to define the physical layer and data object dictionary to enable the interoperability of physical devices (Stations) on a vehicle WorldFip LAN. This specification deals essentially with the Transport Process Data Units (TPDU) which is elsewhere referred to as Exchange Blocks (Annex A).
48、 The Applications Process Data Units (APDU) also referred to in Annex A as Function Blocks, are not hereafter defined even though they contribute to the Transport Process Data Units. 5.2 Devices in a complex network The following illustrates the possible devices in a complex network. Figure 7 - Devi
49、ces in a complex network CEN/TS 13149-3:200712 5.3 Station numbers Station numbers are given in Table 2. Table 2 Station numbers Number Station00H Test and Maintenance Device 01H Master On-Board Processor 02H Spare 03H04H Electronic Ticket Machine 05H Drivers Consol06H Badge Reader 07H Tag/Beacon Reader 08H Short Range Communications 09H Radio Control Unit 0AH Data Modem 0BH On-Board Display 1 OCH On-Board Display 2 ODH On-Board Display 3 0EH On-Board Display 4 0FH External Sign (Front) 10H External Sign (Rear) 11H External Sign (Side/Kerb) 12H GPS 13H Ticket Canceller 14
