1、 Collection of SANS standards in electronic format (PDF) 1. Copyright This standard is available to staff members of companies that have subscribed to the complete collection of SANS standards in accordance with a formal copyright agreement. This document may reside on a CENTRAL FILE SERVER or INTRA
2、NET SYSTEM only. Unless specific permission has been granted, this document MAY NOT be sent or given to staff members from other companies or organizations. Doing so would constitute a VIOLATION of SABS copyright rules. 2. Indemnity The South African Bureau of Standards accepts no liability for any
3、damage whatsoever than may result from the use of this material or the information contain therein, irrespective of the cause and quantum thereof. ISBN 978-0-626-22967-2 SANS 53149-3:2009Edition 1CEN/TS 13149-3:2007Edition 1SOUTH AFRICAN NATIONAL STANDARD Public transport Road vehicle scheduling and
4、 control systems Part 3: WorldFIP message content This national standard is the identical implementation of CEN/TS 13149-3:2007 and is adopted with the permission of CEN, rue de Stassart 36, B-1050 Brussels. Published by SABS Standards Division 1 Dr Lategan Road Groenkloof Private Bag X191 Pretoria
5、0001Tel: +27 12 428 7911 Fax: +27 12 344 1568 www.sabs.co.za SABS SANS 53149-3:2009 Edition 1 CEN/TS 13149-3:2007 Edition 1 Table of changes Change No. Date Scope National foreword This South African standard was approved by National Committee SABS SC 71H, Information technology Intelligent transpor
6、t systems, in accordance with procedures of the SABS Standards Division, in compliance with annex 3 of the WTO/TBT agreement. This SANS document was published in July 2009. TECHNICAL SPECIFICATIONSPCIFICATION TECHNIQUETECHNISCHE SPEZIFIKATIONCEN/TS 13149-3July 2007ICS 35.240.60; 43.080.20; 45.060.01
7、English VersionPublic transport - Road vehicle scheduling and control systems -Part 3: WorldFIP message contentTransports publics - Systmes dordonnancement et decontrle des vhicules routiers - Partie 3 : Contenu demessages WorldFIPffentlicher Verkehr - Straenfahrzeuge - Planungs- undSteuerungssystem
8、e - Teil 3: WORLDFIPThis Technical 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 q
9、uestion whether the CEN/TS can be 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 standa
10、rds in force (in parallel to the 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,
11、 Ireland, Italy, Latvia, Lithuania, 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
12、, 36 B-1050 Brussels 2007 CEN All rights of exploitation in any form and by any means reservedworldwide for CEN national Members.Ref. No. CEN/TS 13149-3:2007: ESANS 53149-3:2009This s tandard may only be used and printed by approved subscription and freemailing clients of the SABS .CEN/TS 13149-3:20
13、07 (E) 2 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 identifiers and numbers.6 4.2 Fare terms and related identifiers and numbers 10 5 Requirements.11 5.1 Hardware preferences
14、 .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 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 dictio
15、nary15 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 Profile Model47 A.2.1 Device General Structure47 A.2.2 Physical Node Interface 50 A.2.3 Logical Node Interface 51 A.2.4 F
16、unction 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 .66 A.3.3 Profiles Characteristics.67 Annex B (informative) Example of Simple Network Application 68 B.1 Simple Network
17、 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.4 Macro Cycle71 B.3 Virtual Device Profiles.71 SANS 53149-3:2009This s tandard may only be used and printed by approved
18、subscription and freemailing clients of the SABS .CEN/TS 13149-3:2007 (E) 3 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
19、Device Description Example 2 .80 Bibliography81 SANS 53149-3:2009This s tandard may only be used and printed by approved subscription and freemailing clients of the SABS .CEN/TS 13149-3:2007 (E) 4 Foreword This document CEN/TS 13149-3:2007 has been prepared by Technical Committee CEN/TC 278 “Road tr
20、ansport and traffic telematics”, the secretariat of which is held by NEN. According to the CEN/CENELEC Internal Regulations, the national standards organizations of the following countries are bound to announce this Technical Specification: Austria, Belgium, Bulgaria, Cyprus, Czech Republic, Denmark
21、, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and United Kingdom. Introduction This Technical Specification is intended to be develope
22、d 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 13149 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
23、 transport and traffic telematics - Public transport - Reference data model, when applicable. 1 Scope This Technical Specification specifies the choice and the general applications rules of an onboard data transmission bus between the different equipment for service operations and monitoring of the
24、fleet. This applies to equipment installed onboard buses, trolley-buses and tramways only as part of a bus fleet operation. It excludes tramways when they are operated as part of a train, subway or metro operation. This equipment includes operation aid systems, automatic passenger information system
25、s, fare collection systems, etc. The equipment directly related to the safety-related functioning of the vehicle (propulsion management, 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 describe
26、d 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 describe 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 v
27、ehicle. Although it could be applied to multiple vehicles, this application is not explicitly covered by this standard. Part 1 of EN 13149 specifies the WorldFIP-based network. This specification describes the general architecture in terms of hierarchical layers according to the ISO reference model
28、for Open Systems Interconnection (OSI) specified in ISO 7498. Part 2 of EN 13149 specifies in detail the connectors and the connector pin assignment and the cabling. Part 3 (this Technical Specification) specifies in detail the application profiles for a simple network. SANS 53149-3:2009This s tanda
29、rd may only be used and printed by approved subscription and freemailing clients of the SABS .CEN/TS 13149-3:2007 (E) 5 2 Normative references The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated
30、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 - Part 1: WORLDFIP definition and ap
31、plication 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 12896:2006 apply. 4 Vehicle related iden
32、tifiers 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 (see Figure 1: x). The Body ID assig
33、ned 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 textual radio address of the bus. This add
34、ress is necessary for selective calls to this bus (see Figure 1: z). Figure 1 Vehicle related identifiers and numbers SANS 53149-3:2009This s tandard may only be used and printed by approved subscription and freemailing clients of the SABS .CEN/TS 13149-3:2007 (E) 6 4.2 Vehicle operation identifiers
35、 and numbers The Garage ID assigned by the system designer refers to the garage ID object containing 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 fro
36、m the time it leaves a parking point (depot, garage) after parking until its next return to 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 B
37、lock ID object containing the textual description of the block. The Line ID assigned by the 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
38、Lx = Line x Gi = Garage i Figure 2 - Non-closed and closed block A route is an ordered list 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 (
39、see Figure 3). The Stop Point ID assigned by the system designer refers to the Stop Point ID 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 Figur
40、e 3). The number of running in route representation is the Running Stop Point Number within a route (see Figure 3). SANS 53149-3:2009This s tandard may only be used and printed by approved subscription and freemailing clients of the SABS .CEN/TS 13149-3:2007 (E) 7 Key LiLine i DnDestination number n
41、 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) related to a given time or time table (see Figure 4). SANS 53149-3:2009This s tandar
42、d may only be used and printed by approved subscription and freemailing clients of the SABS .CEN/TS 13149-3:2007 (E) 8 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 id
43、entifier the path and the rail track of this line/route is defined for a vehicle. For example, this is used for the controlling of rail switches in the track (see Figure 5). SANS 53149-3:2009This s tandard may only be used and printed by approved subscription and freemailing clients of the SABS .CEN
44、/TS 13149-3:2007 (E) 9 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 SANS 53149-3:2009This s tandard may only be used and printed by approved subscription and freemailing clients of the SABS .CEN/TS 13
45、149-3:2007 (E) 10 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 indicat
46、es the 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 ide
47、ntifiers 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 i
48、ncrement in the fare value occurs. SANS 53149-3:2009This s tandard may only be used and printed by approved subscription and freemailing clients of the SABS .CEN/TS 13149-3:2007 (E) 11 5 Requirements 5.1 Hardware preferences There is a WorldFip convention to characterise standard physical device pro
49、files that contain specific applications and virtual devices, but this is beyond the present scope of this part of the standard. The 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). The Applications Process Data Units (APDU) also referred to in Annex A as Function Blocks, are not hereafter defined even though they contribute
