《DD-CEN-TS-13149-3-2007.pdf》由会员分享,可在线阅读,更多相关《DD-CEN-TS-13149-3-2007.pdf(86页珍藏版)》请在三一文库上搜索。
1、DRAFT FOR DEVELOPMENT DD CEN/TS 13149-3:2007 Public transport Road vehicle scheduling and control systems Part 3: WorldFIP message content ICS 43.020; 35.240.60; 43.080.20; 45.060.01 ? Licensed Copy: London South Bank University, London South Bank University, Sat Sep 01 03:05:42 GMT+00:00 2007, Unco
2、ntrolled Copy, (c) BSI DD CEN/TS 13149-3:2007 This Draft for Development was published under the authority of the Standards Policy and Strategy Committee on 31 August 2007 BSI 2007 ISBN 978 0 580 54465 1 National foreword This Draft for Development is the UK implementation of CEN/TS 13149-3:2007. Th
3、is 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 its practical application can be obtained. Comments
4、 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 years after its publication by the European orga
5、nization 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 responsible BSI Committee will decide whether to
6、 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 Road, London W4 4AL. The UK participation in its pr
7、eparation 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 provisions of a contract. Users are responsible for it
8、s correct application. Amendments issued since publication Amd. No. DateComments Licensed Copy: London South Bank University, London South Bank University, Sat Sep 01 03:05:42 GMT+00:00 2007, Uncontrolled Copy, (c) BSI TECHNICAL SPECIFICATION SPCIFICATION TECHNIQUE TECHNISCHE SPEZIFIKATION CEN/TS 13
9、149-3 July 2007 ICS 35.240.60; 43.080.20; 45.060.01 English Version Public transport - Road vehicle scheduling and control systems - Part 3: WorldFIP message content Transports publics - Systmes dordonnancement et de contrle des vhicules routiers - Partie 3 : Contenu de messages WorldFIP ffentlicher
10、 Verkehr - Straenfahrzeuge Planungs- und Steuerungssysteme - Teil 3: WORLDFIP Nachrichteninhalt This 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 me
11、mbers of CEN will be requested to submit their comments, particularly on the question 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 available promptly at national lev
12、el in an appropriate form. It is permissible to keep conflicting national standards 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, Cz
13、ech Republic, Denmark, 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. EUROPEAN COMMITTEE FOR STANDARDIZATION COMIT EU
14、ROPEN DE NORMALISATION EUROPISCHES KOMITEE FR NORMUNG Management Centre: rue de Stassart, 36 B-1050 Brussels 2007 CENAll rights of exploitation in any form and by any means reserved worldwide for CEN national Members. Ref. No. CEN/TS 13149-3:2007: E Licensed Copy: London South Bank University, Londo
15、n South Bank University, Sat Sep 01 03:05:42 GMT+00:00 2007, Uncontrolled Copy, (c) BSI 2 Contents Page Foreword4 Introduction.4 1 Scope 4 2 Normative references5 3 Terms and definitions .5 4 Vehicle related identifiers and numbers .5 4.1 Vehicle operation identifiers and numbers.6 4.2 Fare terms an
16、d related identifiers and numbers10 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 cable13 5.6 Data modelling.13 5.6.1 General13 5.6.2 Text stru
17、cture.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 Profile Model47 A.2.1 Device General Structure47
18、 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.66 A.3.3 Profiles Characteristics.67 Annex B (i
19、nformative) Example of Simple Network Application68 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.4 Macro Cycle71 B.3 Virtual Device Profiles.71 CEN/
20、TS 13149-3:2007 Licensed Copy: London South Bank University, London South Bank University, Sat Sep 01 03:05:42 GMT+00:00 2007, Uncontrolled Copy, (c) BSI 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 (informativ
21、e) Examples of Device Descriptions.78 C.1 Device Description Example 1 .78 C.2 Device Description Example 2 .80 Bibliography81 CEN/TS 13149-3:2007 Licensed Copy: London South Bank University, London South Bank University, Sat Sep 01 03:05:42 GMT+00:00 2007, Uncontrolled Copy, (c) BSI 4 Foreword This
22、 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 national standards organizations of the following countries are bound to announce
23、 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, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerlan
24、d 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 13149 describes a complete solution independent from part 4, part 5 and pa
25、rt 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 specifies the choice and the general applications rules of an onboard data tra
26、nsmission 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 tramways when they are operated as part of a train, subway or metro opera
27、tion. 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, brake systems, door opening systems, etc.) are excluded from the scope o
28、f 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 describe the CANopen bus system. There is no ranking between the two bus syste
29、ms. 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 13149 specifies the WorldFIP-based network. This specification describes the
30、 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 pin assignment and the cabling. Part 3 (this Technical Specification) speci
31、fies in detail the application profiles for a simple network. CEN/TS 13149-3:2007 Licensed Copy: London South Bank University, London South Bank University, Sat Sep 01 03:05:42 GMT+00:00 2007, Uncontrolled Copy, (c) BSI 5 2 Normative references The following referenced documents are indispensable fo
32、r the application of this document. For dated references, only the 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-
33、1; Public transport - Road vehicle scheduling and control systems - 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 pur
34、poses of this document, the terms and definitions given in EN 12896: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
35、 or the number is coded by a fixed connector at the main computer (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 b
36、y the system designer refers to the radio ID containing the textual 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:2007 Licensed Copy: London South Bank University, London South Ba
37、nk University, Sat Sep 01 03:05:42 GMT+00:00 2007, Uncontrolled Copy, (c) BSI 6 4.2 Vehicle operation identifiers 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
38、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 park at a parking point. Any subsequent departure from a parking point after parking marks the
39、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 system designer refers to the Line ID object containing the textual or numerical name of the li
40、ne, 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 of points defining one single path through the road (or rail) network. Stop points, timing poin
41、ts 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 object representing uniquely a stop point within a transportation network (see Figure 3). The
42、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 a route (see Figure 3). CEN/TS 13149-3:2007 Licensed Copy: London South Bank University, London
43、 South Bank University, Sat Sep 01 03:05:42 GMT+00:00 2007, Uncontrolled Copy, (c) BSI 7 Key Li Line i Dn Destination number n Rx Route 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 journe
44、y (between one terminus to another terminus) related to a given time or time table (see Figure 4). CEN/TS 13149-3:2007 Licensed Copy: London South Bank University, London South Bank University, Sat Sep 01 03:05:42 GMT+00:00 2007, Uncontrolled Copy, (c) BSI 8 Key Ri = route number Ji = journey number
45、 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 line/route is defined for a vehicle. For example, this is used for the controlling of rail switches in the track (
46、see Figure 5). CEN/TS 13149-3:2007 Licensed Copy: London South Bank University, London South Bank University, Sat Sep 01 03:05:42 GMT+00:00 2007, Uncontrolled Copy, (c) BSI 9 Key Lx = Line ID x Ri = Route number I Dj = Destination number RDn = Route destination ID Figure 5 - Description of the use o
47、f Route Destination ID CEN/TS 13149-3:2007 Licensed Copy: London South Bank University, London South Bank University, Sat Sep 01 03:05:42 GMT+00:00 2007, Uncontrolled Copy, (c) BSI 10 4.3 Fare terms and related identifiers and numbers The Route Segment Number indicates a set of consecutive links on
48、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 the number of the last/previous crossed fare zone (see Table 1). The Previous Route Segment Number is the number of the last/previo
49、us 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 identifiers and numbers Table 1 - Contents of the objects at the different vehicle positions Positions P1 P2 P3 P4 Fare zone Z1 Z1 Z2 Z2 Route segment RS1 RS2 RS1 RS2 Previous fare zone - - Z1 Z1 Previous route segment - RS1 RS2 RS1 NOTE In this document, a Fare Stage Number is a stop point on a route beyond which an increment in the far
链接地址:https://www.31doc.com/p-3760741.html