BS en 13149-1-2004
BS en 13149-1-2004
BS en 13149-1-2004
13149-1:2004
Public transport —
Road vehicle
scheduling and control
systems —
Part 1: WORLDFIP definition and
application rules for onboard data
transmission
National foreword
This British Standard is the official English language version of
EN 13149-1:2004. It supersedes DD ENV 13149-1:2000, which is withdrawn.
The UK participation in its preparation was entrusted to Technical Committee
EPL/278, Road transport informatics, which has the responsibility to:
— aid enquirers to understand the text;
— present to the responsible international/European committee any
enquiries on the interpretation, or proposals for change, and keep the
UK interests informed;
— monitor related international and European developments and
promulgate them in the UK.
A list of organizations represented on this committee can be obtained on
request to its secretary.
Cross-references
The British Standards which implement international or European
publications referred to in this document may be found in the BSI Catalogue
under the section entitled “International Standards Correspondence Index”, or
by using the “Search” facility of the BSI Electronic Catalogue or of British
Standards Online.
This publication does not purport to include all the necessary provisions of a
contract. Users are responsible for its correct application.
Compliance with a British Standard does not of itself confer immunity
from legal obligations.
ICS 35.1 00.05; 35.240.60; 43.080.20; 45.060.01 Supersedes ENV 1 31 49-1 :1 999
English version
© 2004 CEN All rights of exploitation in any form and by any means reserved Ref. No. EN 1 31 49-1 :2004: E
worldwide for CEN national Members.
EN 1 31 49-1 :2004 (E)
Contents
page
Introduction.......................................................................................................................................... 4
1 Scope.............................................................................................................................................. 5
2 Normative references ................................................................................................................... 5
3 Terms and definitions ................................................................................................................... 6
4 Typical structure of the network ................................................................................................. 6
4.1 Outline functions of the network................................................................................................... 6
4.2 Diagram of preferred implementation .......................................................................................... 7
5 Specifications for the on-board data transmission system ..................................................... 7
5.1 Data transmission bus.................................................................................................................. 7
5.2 General rules................................................................................................................................ 7
5.2.1 Introduction................................................................................................................................ 7
5.2.2 Network medium ....................................................................................................................... 7
5.2.3 Transmission speed .................................................................................................................. 7
5.2.4 Coupling mode .......................................................................................................................... 7
5.2.5 Redundant media ...................................................................................................................... 7
5.2.6 Network configuration rules....................................................................................................... 7
5.2.7 Encoding ................................................................................................................................... 8
5.2.8 Turnaround time ........................................................................................................................ 8
5.2.9 Waiting time at the bus arbiter level for an answer................................................................... 8
5.2.1 0 Jabber inhibit........................................................................................................................... 8
5.2.1 1 Connectors .............................................................................................................................. 8
5.2.1 2 Cables ..................................................................................................................................... 8
5.3 Conformance Class...................................................................................................................... 8
5.4 Bus Arbiter.................................................................................................................................... 8
5.5 Presence Variable ........................................................................................................................ 8
Annex A (informative) CEN/TC 278 Internal report on requirements for on board
transmission between equipment ..................................................................................................... 9
Bibliography....................................................................................................................................... 76
2
EN 1 31 49-1 :2004 (E)
Foreword
This document (EN 1 31 49-1 :2004) has been prepared by Technical Committee CEN/TC 278
"Road Transport and Traffic Telematics", the secretariat of which is held by NEN.
This European Standard shall be given the status of a national standard, either by publication of an
identical text or by endorsement, at the latest by February 2005, and conflicting national standards
shall be withdrawn at the latest by February 2005.
According to the CEN/CENELEC Internal Regulations, the national standards organizations of the
following countries are bound to implement this European Standard: Austria, Belgium, Cyprus,
Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland,
Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Slovakia,
Slovenia, Spain, Sweden, Switzerland and United Kingdom.
3
EN 1 31 49-1 :2004 (E)
Introduction
The present situation is the following:
— A large number of Vehicle Scheduling and Control Systems (VSCS) do not use a data bus,
resulting in
— point to point data links with expensive cabling which cannot be preinstalled during the
manufacturing of the vehicle, increasing the cost of the system
— IBIS bus is not an open system and does not cover some of the necessary messages
— practically every VSCS manufacturer has been obliged to implement a second high speed
data bus which is proprietary, resulting in no possibility of interchanging equipment with other
manufacturers
The buses, which are proposed by CEN/TC278, aim at avoiding the preceding difficulties with the
following characteristics:
— existing chips and basic software up to and including the layer 7 of the ISO 7 layer
communication model and existing developments tools, minimising the development costs
The buses proposed by CEN/TC 278 have been chosen among others through a progressive
selection process. This work took into account a flexible approach to the range of applications, the
potential traffic loading under different operating circumstances and the definition of objective
criteria for a transmission bus. The candidate buses were evaluated against the criteria in terms of
performance, cost, industrial support and the existence of maintained documents.
4
EN 1 31 49-1 :2004 (E)
1 Scope
The present document specifies the choice and the general application’s 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, trolleybuses 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. The equipment includes operations aid systems, automatic passenger information
systems, fare collection systems, etc....
The equipment directly related to the functioning of the vehicle (driver dashboard, engine
management, brake systems, door opening systems, etc...) are excluded from the scope of the
present document and are dealt with in other standardisation bodies.
Two alternative transmission buses will be accepted. This document refers to the so called
WORLDFIP bus. A second set of documents will be published for the second solution (so called
CAN). There is no ranking between the two solutions and the selected bus system, between the
two standardised alternatives, shall be subject to an agreement between each transport operating
organisation and its equipment providers.
The present document refers to the so-called OSI transmission model and covers OSI layers 1 ,2,7,
the other layers are not used in our applications.
The present document 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 document.
The present document is the first part of a set of standards, related to the onboard transmission
bus, which will comprise, for each allowed transmission bus, the following set of documents:
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 references, the latest edition of the
referenced document (including any amendments) applies.
5
EN 1 31 49-1 :2004 (E)
3.1
network
s ys te m form e d b y a pa rti cu l a r i m p l e m e n ta ti on of th e d a ta tra n s m i s s i on b u s
3.2
presence variable
vari a b l e tra n s m i tte d b y a d e vi ce to i n d i ca te th a t i t i s p re s e n t o n th e b u s
th e m a i n fe a tu re s of th e n e twork:
— E s s en ti a l l y fi e l d b u s l i n ea r top o l og y
— A p e ri od i c (E ve n ts ) d a ta
— M es s a g e an d fi l e tra n s fe r
— O p en n e twork
— S el f cl ocki n g
— H a l f d u p l ex
— M ed i u m red u n d a n cy p os s i b i l i ty
— I n te l l i g e n t a n d n on -i n te l l i g e n t d e vi ce s
— D i s tri b u te d d ata b a s e
— E rror d e te cti o n
6
EN 1 31 49-1 :2004 (E)
5.2.1 Introduction
These general rules are derived from EN 61 1 58-2, and particularly those referring to the Medium
Attachment Unit (MAU): 1 Mbits/s, voltage mode, wire medium. The following are particularly
relevant and shall apply.
7
EN 1 31 49-1 :2004 (E)
5.2.7 Encoding
The Preamble and Delimiters coding shall be as defined by EN 61 1 58-2:1 994 section 9. CRC
coding shall be as defined by EN 501 70.
5.2.1 1 Connectors
The connectors referred to in EN 61 1 58-2:1 994 section 1 2 are not mandatory. They are defined in
EN 1 31 49-2.
5.2.1 2 Cables
Cables are referred to in EN 61 1 58-2:1 994 section 1 2 and the corresponding specifications are laid
down in EN 1 31 49-2.
a) There shall be at least one bus arbiter but any device can be nominated as the main bus
arbiter.
c) It shall be possible to modify the arbitration table easily by updating the memory.
d) It shall be possible for the arbiter to store and manage at least four arbitration tables, which
can be received and switched via the bus
e) The arbiter shall provide for a minimum of 64 Kbytes of dedicated memory for the
arbitration function.
8
EN 1 31 49-1 :2004 (E)
Annex A
(i n form ati ve)
9
EN 1 31 49-1 :2004 (E)
TABLE OF CONTENTS
1 -Introduction:
10
EN 1 31 49-1 :2004 (E)
1 -Introduction:
1 -1 -Scope:
This informative annex is aimed at explaining the path followed to choose the transmission buses.
The purpose of this document is to specify the main requirements of a transmission bus to be used
between the on board equipment of a Vehicle Scheduling and Control System for road public
transport vehicles. It corresponds to the Work Item 3.1 .1 of the program of work of the CEN
TC278/WG3 "Public Transport". It applies to equipment installed onboard buses, trolleybuses 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 document has been the basis for the rest of the
standardisation work on the on board data transmission bus, it has first been published as part of
an Internal Technical report.
The use of this transmission bus is limited to the systems and equipment on board the vehicles of
urban and interurban public transportation (buses and tramways when they are operated as buses,
excluding transportation in complete individual sites such as trains or tramways operated as trains)
that are designed for the operation of public transportation (operation aid systems, automatic
passenger information systems, fare collection systems, maintenance aid systems).
The functions corresponding to the management of the vehicle itself (such as for example engine
control, brake control, etc.) are totally excluded from the scope of work of the present document.
Normally the scope of the document is limited to the transmissions taking place onboard a single
vehicle, the transmission between more than one vehicle may require a separate intervehicle bus.
However, it would be preferred (but it is not taken as mandatory for the definition of the required
bus), to be able to extend the bus through multiple vehicles (3 at the maximum) to avoid the
complication of an intervehicle bus. To evaluate this possibility, the additional transmission load
corresponding to the addition of a supplementary vehicle will be defined.
The Tables given in chapter 4 to evaluate the transmission busload are only rough estimates and
shall not been taken as mandatory.
11
EN 1 31 49-1 :2004 (E)
12
EN 1 31 49-1 :2004 (E)
1 -3 -D e fi n i ti o n s :
S ys te m eq u i pm e n t on b oa rd th e ve h i cl e of u rb a n a n d i n te ru rb a n p u b l i c tra n s p ortati on ( b u s e s an d
s ys te m s)
-Tra n s m i s s i on bu s :
-E tc.
N ot a l l of th e s ys te m s a re com p reh e n s i ve a n d th e re e xi s t s ys te m s th a t h a ve on l y a ve ry l i m i te d
l oca l i s a ti on s ys tem a n d wh i ch h a ve n o d a ta com m u n i cati o n wi th a cen tra l con trol room e xce p t
b oa rd eq u i pm e n t th e y wi l l m ake u s e of th e tra n s m i s s i on b u s .
2 -1 -F u n cti on s of th e s ys te m :
Th e VS C S m a y i m p l e m e n t a s u b s e t or al l of th e m ai n fol l o wi n g fu n cti on s :
13
EN 1 31 49-1 :2004 (E)
Depending on the subset of functions being performed, the architecture of the system may vary.
The most general architecture is represented on the Figure 1 (coming from the DRIVE project
BARTOC) taking into account the different possibilities to implement the system.
Figure 1 represents the main elements of the system and their links. The most comprehensive
systems are composed of:
-a Control Centre with a VSCS computer and the attached regulator or operator
workstations. The VSCS computer normally manages the whole system and
communicates in real time with the vehicles and other peripherals. There exist also
completely decentralised systems in which the central computer is reduced and does not
communicate in real time with the vehicles.
-links to other control and information centres to exchange information for example with an
external transport user information server.
-a specific link to the traffic control centre in order to implement a centralised priority at
traffic lights (this priority may also be implemented without any link to the traffic control
centre in a decentralised concept) and to exchange information on congestion and travel
times.
-a link to the company database in order to automatically receive the theoretical
parameters of the system (schedules, driver duties, vehicle duties, etc...) and to download
the statistics produced by the system.
-a link to the fuel distribution subsystem
-a link to the driver sign on subsystem
-a link to the garage management subsystem
-voice links to the network agents.
14
EN 1 31 49-1 :2004 (E)
b e of d i ffere n t n a tu re :
. a s h ort-ran g e l i n k, to b e u s e d at th e g a ra g e , to d o wn l o ad s ta ti s ti cs i n to th e VS C S com p u te r an d to
ve h i cl e , to th e d ri ve r, to th e p a s s en g e rs a n d to s p e ci fi c l oca l i s a ti on d e vi ce s .
corre s p on d i n g ro a d s i d e e q u i p m e n t
-user information devices at home (data terminals such as minitel or voice communication),
which are linked to the control centre through public, switched telephone network.
3 - TH E O N B O ARD S U B S YS TE M
3 -1 -G e n e ra l p res e n ta ti o n of th e s u b s ys te m :
Th e on bo a rd e q u i pm e n t i s a rra n g e d a ro u n d a n i n te rn a l tran s m i s s i on bu s wh i ch ru n s a l l a ro u n d th e
s om e d a ta .
m a y be fou n d i n th e ve h i cl e .
ve h i cl e b u s , or b y a s e pa ra te tra n s m i s s i on m e d i u m .
3 -2 -Th e on b oa rd e q u i p m en t:
Th e tra n s m i s s i on b u s ca b l e wi l l b e d e fi n ed i n 2 cl a s s e s :
15
EN 1 31 49-1 :2004 (E)
• Cl ass 1 :
* th e tra n s m i s s i on b u s wi re s .
* th e p o wer wi re s :
. 1 for g rou n d .
-s wi tch e d on b y m ai n s wi tch of ve h i cl e .
• Cl ass 2:
* th e tra n s m i s s i on b u s wi re s .
* th e p o wer wi re s :
. 1 for g rou n d .
-s wi tch e d on b y m ai n s wi tch of ve h i cl e .
* th e l o u d s p ea ke rs an d m i crop h o n e .
Wh a te ve r th e cl as s of th e b u s ca b l e , s om e p a rt of th e s ys te m m a y b e p erm a n e n tl y s wi tch e d on to
th e veh i cl e p o we r s u pp l y.
3-3 -D e fi n i ti o n of d e vi ce s :
- Ti cke t C a n ce l l or or Va l i d a tor :
- Ti cke t p ri n ter, or Ve n d i n g M a ch i n e :
D e vi ce d e d i ca ted to fa re m an a g e m en t a n d ti cke t p ri n ti n g .
-P as s en g er co u n ti n g d e vi ce :
D e vi ce d e d i ca te d to p a s s e n g e r cou n ti n g m an a g e m en t.
- Loa d M e a s u re m e n t D e vi ce :
D e vi ce d e d i ca te d to p a s s e n g e r l oa d m e a s u rem e n t.
- Ve h i cl e I d e n ti ty C od e :
D e vi ce d ed i ca te d to ve h i cl e i d e n ti ty a s s i g n m e n t.
1 6
EN 1 31 49-1 :2004 (E)
D e vi ce d e d u ce d to D /A I n p u ts /O u tp u ts i n te rfa ce m a n a g e m e n t, s u ch as te ch n i ca l a l a rm s ,
veh i cl e s ta tu s , . . .
-Vari a bl e E xte rn al s i g n :
s u ch a s l i n e i d e n ti fi ca ti o n , d e s ti n a ti o n , ro u te ta ke n , . . .
-I n te rn a l P a s s e n g e r I n form a ti o n D i s p l a y:
veh i cl e s u ch as l i n e i d e n ti fi cati on , d e s ti n a ti o n , n e xt s to p, . . .
-Voi ce An n ou n ce m en t S ys tem a n d Pu b l i c Ad d re s s :
-D ri ve r C on s o l e :
eve n ts of ve h i cl e o pe rati on .
- S h ort ra n g e C om m u n i ca ti on S ys te m :
i n to th e g a ra g e e n vi ro n m e n t.
- Ta g Re a d e r:
- 2 D i m e n s i on s L ocati on D e vi s s e :
D e vi ce d ed i ca te d to ve h i cl e l oca ti on , wh i ch i s ca pa b l e of fe ed i n g ou t two d i m e n s i o n a l
- M a i n O n b oa rd C om p u ter:
M a i n d e vi ce d e d i ca te d to d a ta tra n s m i s s i on m a n a g e m e n t a n d g e n e ral on b oa rd d e vi ce s
m an a g e m en t.
- Te s t an d m a i n ten a n ce D e vi ce :
al arm s m e ss a g es for th e ve h i cl e .
- G a te wa y d e vi ce to a n ci e n t b u s :
D e vi ce d ed i ca te d to th e l i n k wi th a n exi s ti n g AVM S b u s , i n s i d e th e ve h i cl e.
-Ra d i o C om m u n i cati o n D e vi s s e :
th e C e n tra l C o n trol Ro om .
- Ve h i cl e E q u i p m e n t B ri d g e or I n te rface :
17
EN 1 31 49-1 :2004 (E)
18
EN 1 31 49-1 :2004 (E)
19
EN 1 31 49-1 :2004 (E)
Figure A.2 - REFERENCE BLOC DIAGRAM OF ON BOARD SUBSYSTEM, USED FOR THE ANALYSIS
20
EN 1 31 49-1 :2004 (E)
• The terminology conforms to document No. 21 - Glossary of terms reference EuroBus Project
V2025 where possible.
• Data may be transmitted to different devices. For example a tag (beacon) identity may be
required by the destination sign, or the main on board computer unit, or the ticket machine. To
consider the worst-case situation for the transmission system, the destination of the data is
therefore given as the main on board computer, which then relays the data and obtains
acknowledgements to ensure the integrity of the Serial Data-Bus Bar.
• It is envisaged that any device containing a microprocessor, could be programmed with its
individual application code via the data-bus. Since this would not occur whilst the vehicle is in
service such traffic is not included in the inventory.
4.2 Assumptions
The following assumptions are made to avoid duplication of exchanges for the following tables:
Table B1 ):
Ticket cancellors or validators have sufficient processing power and intelligence to accept, deduct
and cancel pre-paid tickets or smart cards. They will require configuration data for a trip, a black
list, exchange data for the man/machine interface, and produce statistics via the Main Onboard
Computer.
Table B2):
The Ticket issuing Machine or Vending machine will accept printing and formatting instructions
from the console via the Main Onboard Computer.
Table B3):
The Passenger Counter communicates with the Main Onboard computer only.
Table B4):
The Load Measurement Device communicates with the Main Onboard Computer only.
Table B5):
The Vehicle I/D Code Device provides a fixed identity for external communications, and for fleet
management in the VSCS system.
Table B6):
Digital Inputs
21
EN 1 31 49-1 :2004 (E)
4. Alarm on maximum folding (limit of the authorised angle of the articulation of an articulated
vehicle)
1 5. Fuel consumption
1 7. Voltage alarm
Digital Outputs
Vehicle Monitoring Error Login is assumed to be stored in the Main On Board Computer, where it is
later accessed via the Short range Communication System.
Table B7):
22
EN 1 31 49-1 :2004 (E)
The External Destination Sign are assumed to be configured from the Drivers Console using menu
selection, or automatically from the Main Onboard Computer at the start of the trip. The data
containing the home garage, route, and destination for all possible routes for the vehicle are
assumed to be updated by the Short range Communications System in the garage.
Table B8):
The Internal Passenger Information signals are considered to be configured by the Short range
Communications System, triggered by Location Device, and manually controlled from the Console
via the Main Onboard Computer.
Table B9):
Table B1 0):
The drivers Console is considered as the primary man/machine interface giving audio
(tones/speech) and visual information to the driver. It will be user friendly to minimise training and
operation, and be somewhat dependant upon other input devices to minimise initialisation of the
vehicle. Functions could be key or menu driven. It will enable/disable the vehicle equipment and
support fare collection and tele-diagnosis.
Table B1 1 ):
The Short Range Data Transmission Transceiver (Short Range Communication System in short) is
considered essentially as an extension of the VSCS Serial Data Bus Bar into the garage data
environment. It could also be a local link to traffic management systems such as traffic light priority.
Table B1 2):
The Tag reader is considered as a beacon reader as illustrated in Fig. 2, rather than as a vehicle
identification device.
Table B1 3):
The Badge Reader is considered as a security device and source of information for the VSCS
management system.
Table B1 4):
The Two Dimension Location Device is considered to be capable of feeding out two dimensional
information and data as waypoints.
Table B1 5):
The Main Onboard Computer will store and buffer data, and manage control, status and confidence
messages on the data bus.
Table B1 6):
The Test Maintenance Device is considered as a first in/first out data logger of status and alarm
messages for the vehicle and an access port for external test equipment.
Table B1 7):
The Gateway to Ancient Bus is a link to an existing vehicle control bus, i.e. IBI S or VDV. The data
traffic is not considered as significant in this analysis as it is already included in the other items.
23
EN 1 31 49-1 :2004 (E)
Table B1 8):
The Radio Communications Device is considered capable of receiving and transmitting speech and
data via duplex or semi duplex radio frequency channels. These may be configured in a trunked or
non-a trunked system and use either control or traffic channels. It is assumed that digital inputs
from the drivers console may be used to configure channels, status messages or operational data.
It is also assumed that vehicle's location or other two way data exchanges can be made to the
VSCS Central Computer.
Table B19):
The Vehicle Equipment Bridge is capable of communicating with the vehicle manufacturer’s bus.
2. Data: It is the data contained in the transmission exchange considered (ex: next stop identification).
6. Size: Estimation of the number of useful (not taking into account the protocol encapsulation) bytes of the
transmission
7. Recurrence: Number of occurrences/hour based on the assumption that there are 1 run per hour and 30
stops per run.
8. Ack: Maximum time allowed for an acknowledgement by the receiver. If there is no answer after this time,
a new transmission will be initiated.
9. Access time: Maximum acceptable delay between the decision to transmit by a sender and the effective
transmission on the bus.
1 0. Moment or location when the transmission takes place: Self explaining (for example at stops).
To provide a realistic estimate of the data-bus traffic, the following series of tables (C1 to C5)
analyse the functions from the Inventory of Data-Exchanges for a defined event in the operating
day cycle of a vehicle. These tables consider possible events and permissible overall time
durations for data-bus traffic, and the combined tables attempt to cover all events.
No allowance is made at this point for addressing, prioritisation, parity and error checking.
24
EN 1 31 49-1 :2004 (E)
The events here are minimised to ensure speedy entry of a vehicle into operational use. The
equipment needs to be fully powered up in a controlled sequence, which minimises the effects from
large fluctuations in the battery voltage which may occur during engine start up, and large current
surges caused by many items of equipment being activated simultaneously.
The activity on the data-bus will mostly be concerned with the final configuration of the vehicle for
the day's service, and its registration onto the VSCS network, up to the point of arrival at the start
terminus.
The events in this Table are concerned with normal activities in service, except for the Random,
Cyclic, and Failure events. The number of passengers boarding at each stop is effectively 1 5
between all Ticket Cancellors and Validators and 5 for all Ticket printer or Vending Machines.
Since the traffic load on the data-bus is not great, no further attempt has been made to re-estimate
for a full transmission busload, as the time duration would increase proportionately.
The events in this Table may not be fully comprehensive, but the maximum time limit is generally
not critical for maintenance events.
These are concerned with the downloading of the day's service records, equipment status, and the
upgrade of the vehicle data-base for significant changes, i.e. a new route data-base; advertising;
fare collection and statistics.
These events are considered to occur within a very short time period to provide the worst-case
estimate of data-traffic. The average load would be significantly less if taken over a period of, say,
1 0 seconds. The traffic for other situations such as In Service Events should be added to the
contents of Table 5 to allow for simultaneous activity. A suitable protocol with prioritisation will
enable the data-bus speed to be set to realistic level.
25
EN 1 31 49-1 :2004 (E)
The Garage Run out Events show that event C1 .7 "Run to Outlet Gate" carries high data traffic due
to final bus operating system configuration. This may occur as a result of vehicle substitution when
it will be necessary to prepare the vehicle at the latest possible time for service.
"In Service Events" in Table C2 do not impose a significant load on the data bus.
Fault and maintenance Events in Table C3 can have some large data traffic, but the time
constraints are much less onerous as this occurs infrequently.
Garage Run In Events in Table C4 imposes the most severe conditions on the data bus. At this
stage we do not make any assumptions about the protocol to be used. The net data transmission
speed assuming 8 bits/byte is:
1 5 . 83 3 . 3 3 + 4 . 000
x8 =1 58, 67 kbits/sec .
1 000
Random and Cyclic Events in Table C5 comprise many short messages. It may be conjectured that
all random and cyclic events occur simultaneously for the purpose of estimating the peak traffic and
this yields:
This is greater than the probable traffic but there may be a lower efficiency in the network for short
data messages.
Combination of Random and Cyclic Events with Other Events. The addition of event C2.1 5 and
Table C5 yields the peak condition for normal traffic giving:
526 x8
+88 . 96 =93 ,1 68kbits/sec.
1 000
26
EN 1 31 49-1 :2004 (E)
Item Device Function Data Content Type Input/ Destination/ Size Recurrenc Acknowl Access Moment or Alt.
Output Source e edge Time location Source/Dest.
when
transmissio
n takes
place
B1 .1 Ticket Cancellor or Ticket Signal to Msg Output Main 1 0b 360 0,5 sec 0,1 sec At Stops/ Console
Validator Acceptanc Console Onboard Passenger
e Computer
B1 .2 Ticket Cancellor or Ticket Ticket Type. File Output Main 240kb 0,05 5 sec 1 sec At garages. Short Range
Validator Records Fare Data Onboard Comms.
Computer
B1 .3 Ticket Cancellor or Fare stage Route & Fare Msg Input Main 1 0b 60 2 sec 5 sec At Stops
Validator Stage Data Onboard
(1 ) Computer
B1 .4 Ticket Cancellor or Validator Machine Msg Output Main 20b 0,1 5 sec 1 sec At Garage
Validator Managem Serial No. Onboard
ent Computer
B1 .5 Ticket Cancellor or Fraud Det. Black List (2) File Input Main 20kb 1 1 0 sec 20 sec Start of Run
Validator Onboard
Computer
B1 .6 Ticket Cancellor or Fare Route Stages File Input Main 1 00kb 0,05 1 0 sec 20 sec At Garage
Validator Structure Fares. Dest. Onboard
Computer
B1 .7 Ticket Cancellor or Run Data Route Fare Msg Input Main 20b 2 2 sec 5 sec Start of Run
Validator (3) Stages Onboard
Computer
B1 .8 Ticket Chancellor or Clock Data Date, Day, Msg Input Main 20b 60 1 sec 0,1 sec Cyclic
Validator Day Types, Onboard
Time Computer
1 Route.zone or farestage. Ticket Cancellor or Validator Table: B1
2 Blocked fare cards.
3 Run or journey between two termini
B2.1 Ticket Printer or Vending Ticket Ticket Type, Msg Input Main 1 00b 360 0,5 sec 0,1 sec At Stops
Machine Issuing Route/Zone, Onboard
Fare Stage, Computer
Date, Number
27
EN 1 31 49-1 :2004 (E)
Item Device Function Data Content Type Input/ Destination/ Size Recurrenc Acknowl Access Moment or Alt.
Output Source e edge Time location Source/Dest.
when
transmissio
n takes
place
B2.2 Ticket Printer or Vending Alarms Paper Roll Msg Output Main 2b 0,1 5 sec 1 sec Random
Expired/Jam Onboard
med Computer
B2.3 Ticket Printer or Vending Machine Machine Msg Output Main 20b 0,1 5 sec 1 sec At Garage
Managem Serial No. Onboard
ent Computer
Ticket Machine or Vending Machine Table : B2
B3.1 Passenger Passenger Count Data Msg Output Main 1 0b 60 1 0 sec 20 sec At Stops
Counter Counting Onboard
Computer
B3.2 Passenger Passenger Control Data Msg Input Main 1 0b 60 1 0 sec 20 sec At Stops
Counter Counting Onboard
Computer
Passenger Counter Table: B3
B4.1 Load Measure Load Load Data Msg Output Main Onboard 1 0b 60 1 0 sec 20 sec Al Stops
Estimation Computer
B4.2 Load Measure Load Control Data Msg Input Main Onboard 1 0b 60 1 0 sec 20 sec At Stops
Estimation Computer
Load Measuring Table: B4
B5.1 Vehicle ID Code Vehicle ID Number of Msg Output Main Onboard 1 0b 0, 01 5 sec 5 sec Garage
Management vehicle Computer
B5.2 Vehicle ID Code Radio ID Number of Msg Output Radio 1 0b 0, 01 1 sec 1 sec Garage
Technical vehicle
Address
B5.3 Vehicle ID Code Short Range ID Number of Msg Output Short range 1 0b 0, 01 1 sec 1 sec Garage
Comms. vehicle Communicatio
Technical ns
Address
Vehicle ID Code Table : B5
B6.1 Digital Inputs Vehicle See Section 4.1 Msg Input Main Onboard 1 0b 1 000 0, 02 sec 0, 05 sec Random Event
Monitoring Notes Computer & Testing
B6.2 Digital Outputs Vehicle See Section 4.1 Msg Output Main Onboard 1 0b 60 1 sec 1 sec Random
Control Notes Computer
28
EN 1 31 49-1 :2004 (E)
Item Device Function Data Content Type Input/ Destination/ Size Recurrenc Acknowl Access Moment or Alt.
Output Source e edge Time location Source/Dest.
when
transmissio
n takes
place
1 The Odometer is direct liked to the Main Onboard Computer or Location Device Digital inputs/outputs Table : B6
2 Only the changes to the Digital Inputs and Outputs are sent after initialisation
when they are all sent
B7.1 Variable External Signs Route and Route Msg Input Main 1 00b 2 3 sec 1 0 sec Start and From
Destinatio number, Onboard End of Run Short/Long
n Display Destination Computer range
ID, Via... Comms
B7.2 Variable External Signs Test or Bit Map File Input Short range 1 0kb 2 3 sec 1 0 sec Garage Main
Config Communica Onboard
Display tions Computer
B7.3 Variable External Signs Display Format, Dest. File Input Short range 1 0kb 0,01 3 sec 1 0 sec Garage at Card Reader
database Text, Route Communica End of Day Module/Cass
No tions ette reader
External Variable Signs Table: B7
B8.1 Internal Passenger Info.Signs Store/Displ Bit maps, File Input Short range 32kb 0,01 5 sec 5 sec Garage
ay Text, Link Communica
Messages Data tions
B8.2 Internal Passenger Info.Signs Advertising Bit Maps File Input Short range 1 00kb 0,01 5 sec 1 0 sec Garage
Communica
tions
B8.3 Internal Passenger Info.Signs Next Stop, Positional Msg Input Location 64b 30 3 sec 1 0 sec Stops Odometer/Do
Route and Data Device or Closure
Destinatio via Main
n Display Onboard
Computer
B8.4 Internal Passenger Info.Signs Interchang Positional File Input Location 64b 10 3 sec 1 0 sec Random Odometer/Do
e Display Data Device or Closure
via Main
Onboard
Computer
29
EN 1 31 49-1 :2004 (E)
Item Device Function Data Content Type Input/ Destination/ Size Recurrenc Acknowl Access Moment or Alt.
Output Source e edge Time location Source/Dest.
when
transmissio
n takes
place
B8.5 Internal Passenger Info Time Data/Time Msg Input Main 1 2b 0,05 0,1 sec 1 sec Garage Short range
Display Synchronisati Onboard Comms
on Computer
B8.6 Internal Passenger Info Real Time Menu Msg Input Main 64b 0,5 5 sec 5 sec Random
Messages Selection Onboard
Computer
B8.7 Internal Passenger Info Advertising Menu Msg Input Main 64b 0,5 5 sec 5 sec Random
Messages Function Onboard
Computer
Internal Passenger Information Table: B8
Signs
B9.1 Voice Announcer and PA Record Coded File Input Short range 0,01 5 sec 5 sec Garage Radio via
Speech Speech and Communica main
Messages Control tions Onboard
Computer
B9.2 Voice Announcer and PA Store Route Link Data File Input Short range 1 0kb 0,01 5 sec 5 sec Garage Radio via
data Communica main onboard
tions computer
B9.3 Voice Announcer and PA Next Bus Positional Msg Input Location 64b 30 3 sec 1 0 sec Bus Stops Odomeler/Do
Stop, Route Data Device or Closure
and via Main
Destination Onboard
Computer
B9.4 Voice Announcer and PA Interchange Positional Msg Input Location 64b 15 3 sec 1 0 sec Random Odomeler/Do
information data Device or Closure
via Main
Onboard
Computer
30
EN 1 31 49-1 :2004 (E)
Item Device Function Data Content Type Input/ Destination/ Size Recurrenc Acknowl Access Moment or Alt.
Output Source e edge Time location Source/Dest.
when
transmissio
n takes
place
Voice Announcement and Public Table : B9
Address
B1 0.1 Driver Console Vehicle Driver ID Msg Output Main 20b 0,5 1 sec 1 sec At Garage Badge
Security Confirmation Onboard or relief Reader
Computer points
B1 0.2 Driver Console Service Info. Route/Runnin Msg Output Main 20b 0,5 1 sec 1 sec At Garage Badge /
Entry g N°.s Onboard or relief Cartridge
Computer points Rader
B1 0.3 Driver Console Run Info. Run Msg Output Main 20b 2 1 sec 1 sec Start of
Entry N°./Destinatio Onboard Run or
n Computer Garage
B1 0.4 Driver Console Time Card/ Schedule Msg Input Main 50b 60 1 sec 1 sec Cyclic
Deviation data and Onboard
from Clock Computer
schedule
Display
B1 0.5 Driver Console Departure Departure Msg Input Main 20b 2 1 sec 1 sec At
Order Sequence of Onboard terminals,
Orders Computer interchange
s or bus
stops
B1 0.6 Driver Console Fare Fare Msg Output Main 20b 30 1 sec 1 sec At Bus Location
Collection Stage/Zone Onboard Stops Device
Computer
B1 0.7 Driver Console Fare Type of Msg Output Main 50b 360 0,5 sec 0.1 sec At Bus
Collection Ticket, Value Onboard Stops
or Destination Computer
B1 0.8 Driver Console Validator Type of Msg Input Main 50b 360 0,5 sec 0.1 sec At Bus
Display/Alarm permit / Onboard Stops
validity Computer
31
EN 1 31 49-1 :2004 (E)
Item Device Function Data Content Type Input/ Destination/ Size Recurrenc Acknowl Access Moment or Alt.
Output Source e edge Time location Source/Dest.
when
transmissio
n takes
place
B1 0.9 Driver Console Sign Selection / Msg Output Main 20b 2 3 sec 1 0 sec Start and AVL/Location
Management Functions Onboard End of Run
(External) Computer
B1 0.1 0 Driver Console Sign Display Msg Input Main 64b 2 1 sec 1 sec Start and at
Monitoring Content Onboard stops
(External) Computer
B1 0.1 1 Driver Console Sign Selection / Msg Output Main 20b 30 3 sec 1 0 sec Start and at AVL/Location
Management Functions Onboard stops
(I nternal) Computer
B1 0.1 2 Driver Console Sign Display Msg Input Main 64b 30 1 sec 1 sec Start of run
Monitoring Content Onboard and at
(I nternal) Computer stops
B1 0.1 3 Driver Console Sign Blocking Control Msg Input Main 4 0,1 1 sec 1 sec Random
(I nternal) Onboard
Computer
B1 0.1 4 Driver Console Voice Selection Msg Output Main 20b 0,5 1 sec 1 sec Random
Announcer Onboard
Management Computer
B1 0.1 5 Driver Console Voice Blocking Msg Output Main 20b 0,5 1 sec 1 sec Random
Announcer Onboard
Management Computer
B1 0.1 6 Driver Console Voice Correction Msg Output Main 20b 0,5 1 sec 1 sec Random
Announcer Onboard
Management Computer
B1 0.1 7 Driver Console Public Control Msg Output Main 4b 30 1 sec 1 sec Random
Address Functions Onboard
Computer
B1 0.1 8 Driver Console Passenger Counter/Weig Msg Input Main 1b 30 5 sec 1 0 sec At Stops
Load ht Onboard
Display/Alarm Computer
32
EN 1 31 49-1 :2004 (E)
Item Device Function Data Content Type Input/ Destination/ Size Recurrenc Acknowl Access Moment or Alt.
Output Source e edge Time location Source/Dest.
when
transmissio
n takes
place
B1 0.1 9 Driver Console Vehicle Vehicle Msg Input Main 1 0b 1 1 sec 1 sec Random
Monitoring Monitoring Onboard
Alarms Computer
B1 0.20 Driver Console Engineerin Misc.Function Msg Input Main 20b 0,01 5 sec 1 0 sec Random
g s Onboard
Test/TeleD Computer
iagnosis
Entry/Displ
ay
B1 0.21 Driver Console Engineerin Misc.Function Msg Output Main 50b 0,01 5 sec 1 0 sec Random
g s Onboard
Test/TeleD Computer
iagnosis
Entry/Displ
ay
B1 0.22 Driver Console Vehicle Height/Width/ Msg Input Main 1 0b 0,1 0,1 sec 0,1 sec Random Tag Reader
Restriction Weight Limits Onboard or Short
Warning Computer Range
Comms
B1 0.23 Driver Console Validator Start / Stop Msg Output Main 4b 0,1 1 sec 1 sec Inspector
Blockage Machine Onboard on the bus
Computer
B1 0.24 Driver Console Radio Request Msg Output Main 4b 1 1 sec 1 sec Random Long Range
Control Speech / Onboard Comms
functions Select. Computer
B1 0.25 Driver Console Radio Monitoring Msg Input Main 4b 1 1 sec 1 sec Random
Control Functions Onboard
functions Computer
B1 0.26 Driver Console Driver Sign Off Msg Output Main 20b 0,2 1 sec 1 sec At Garage
Inputs Procedure Onboard or terminus
Computer etc.
33
EN 1 31 49-1 :2004 (E)
Item Device Function Data Content Type Input/ Destination/ Size Recurrenc Acknowl Access Moment or Alt.
Output Source e edge Time location Source/Dest.
when
transmissio
n takes
place
B1 0.27 Driver Console Driver Inputs Sign Off Msg Input Main 1 0b 0,2 1 sec 1 sec At Garage Short Range
Procedure Onboard or terminus Communicati
Computer etc. ons System
B1 0.28 Driver Console Special Key Traffic Light Msg Input Main 1b 1 1 sec 1 sec Random Short Range
Functions Pre-Emption Onboard Communicati
Computer ons System
B1 0.29 Driver Console Special Key Point Control Msg Output Main 1b 1 1 sec 1 sec Random Short Range
Functions Onboard Communicati
Computer ons System
Driver Console Table: B1 0
B1 1 .1 Short range Communications Line (Route) Schedules of File Output Dest: Main 48kb 0,04 At 1 sec 1 sec Garage Ticket
System Schedule 1 line for the Onboard most once machine
Update next day Computer per day, at module/card,
(20b/run,20 least once Radio Device
runs/serv, 40 per three
serv/line 3 days
days)
B1 1 .2 (1 ) Short range Communications Garage Line Itineraries of File Output Dest: Main 32kb 0,0001 1 sec 1 sec Garage Ticket
System (Route) all lines of Onboard (Occasional machine
Table) garage, 1 Ist Computer ) module/card,
hypothesis : Radio Device
one dim locn.
(1 kb/ln.32lns)
B1 1 .3 (1 ) Short range Communications Link data Itineraries of File Output Dest: Main 1 92kb 0,0001 1 sec 1 sec Garage Ticket
System all lines of Onboard (Occasional machine
garage, 2 nd Computer ) module/card,
hypothesis: Radio Device
two dim locn.
(6b/vector,
1 000
vectors/ln, 32
lns)
34
EN 1 31 49-1 :2004 (E)
Item Device Function Data Content Type Input/ Destination/ Size Recurrenc Acknowl Access Moment or Alt.
Output Source e edge Time location Source/Dest.
when
transmissio
n takes
place
B1 1 .4 Short range Communications VSCS Stats Passenger File Input Source: 96kb 0,04 (at 1 sec 1 sec Garage Ticket
System counts, arrival Main most machine
lime, stop Onboard once/day module/card,
time per stop Computer al least Radio Device
(20b/stop 40 once/3
stops/run, 40 days)
runs/day, 3
days)
B1 1 .5 Short range Communications Fare Location, File Input Source: 240kb 0,04 1 sec 1 sec Garage Ticket
System Collection Time, Validators machine
Stats Quantity, module/card,
Value Radio Device
B1 1 .6 (1 ) Short range Communications Fare Times, Fare File Output Destination 1 00kb 0,04 1 sec 1 sec Only twice Ticket
System Structure Stages, Fares : Validators per year at machine
garage module/card,
Radio Device
(1 ) Infrequent events not considered in analysis
B1 1 .7 Short range Communications Fraud Fares File Output Destination 30kb 0,04 1 sec 1 sec Garage Ticket
System Detection Collection : Validators machine
black list, module/card,
invalid tickets Radio Device
Identities
B1 1 .8 Short range Communications Traffic Lights Identity and Msg Input Source: 20kb 30 1 sec 1 sec Before Radio Device
System Priority line (route) Main Traffic
Onboard Lights
Computer (random)
B1 1 .9 Short range Communications Vehicle Sign Msg Input Source: 2kb 0,04 1 sec 1 sec Garage Vehicle
System Monitoring off/Vehicle Main Bridge or
Status Onboard Interface,
Computer Radio Device
At the garage (duration of all the exchanges at the garage limited to 30 sec) Short Range Communications Table: B1 1
System
35
EN 1 31 49-1 :2004 (E)
Item Device Function Data Content Type Input/ Destination/ Size Recurrenc Acknowl Access Moment or Alt.
Output Source e edge Time location Source/Dest.
when
transmissio
n takes
place
B1 2.1 Tag Reader (1 ) Tag ID Beacon Msg Output Destination: 1 0b 30 No 0,02 Random Validators,
Identity and Main Ticket M/c
Battery Status Onboard Int. Signs
Computer
B1 2.2 Tag Reader (1 ) Vehicle Height/ Width/ Msg Output Destination 1 0b 0,1 No 0,01 Random
Restriction Weight Limits Main
Warning / Light on / Onboard
Platform Computer
Level
(1 ) : Tag = Beacon Tag Reader Table: B1 2
B1 3.1 Badge Reader Driver ID Driver Name Msg Output Destination: 20b 5 3 sec 1 0 sec At the Console
and Number Main garage or
Onboard at relief
Computer points
Badge Reader Table: B1 3
B1 4.1 Location Device Vehicle Differential Msg Input Source: 260b 360 1 sec 1 sec Cyclic
Locn GPS Radio Data
Correction transmissio
n
B1 4.2 Location Device Vehicle X-Y Coords. Msg Output Source: 1 1 0b 3600 0,1 sec 0,1 sec Cyclic
Locn Main
Onboard
Computer
Location Device Table: B1 4
B1 5.1 Main Onboard Computer Start-up Data Bus Msg Output All Other 1 00b 0,1 No 1 sec Bus
Cycle Silence / Devices Powers Up
Initialise
delay, Multi
vehicle
Initialisation
B1 5.2 Main Onboard Computer Reset/Can Control and Msg Output Any Other 1 0b 0,1 1 sec 1 sec Random
cel status data devices
36
EN 1 31 49-1 :2004 (E)
Item Device Function Data Content Type Input/ Destination/ Size Recurrenc Acknowl Access Moment or Alt.
Output Source e edge Time location Source/Dest.
when
transmissio
n takes
place
B1 5.3 Main Onboard Computer Switch Control and Msg Output Any Other 1 0b 0,1 1 sec 1 sec Random
off/on Status Data device
equipment
B1 5.4 Main Onboard Computer Confidenc Control Data Msg Output Any Other 1 0b 10 1 0 sec 1 0 sec Cyclic
e (1 ) device
Messages
B1 5.5 Main Onboard Computer Confidenc Status Data Msg Input Any Other 1 0b 10 1 0 sec 1 0 sec Cyclic
e (2) device
Messages
B1 5.6 Main Onboard Computer Test Device Msg Output Any Other 1 0b 0,01 5 sec 1 0 sec Garage Test and
Selection and device maintenance
Test device
commands
B1 5.7 Main Onboard Computer Revenue Ticket Msg Output Ticket 1 00b 0,1 1 sec 1 sec Garage or
Collection Records and Printer Relief
Cash Balance points
B1 5.8 Main Onboard Computer Shutdown Interrupt and Msg Output All Devices 32b 0,1 No 0,1 sec Random
switch off all
equipment
and main
supply
(1 ) eg: Switch on/off "Bus will Stop" sign Main Onboard Computer Table: B1 5
(2) eg: From sign
B1 6.1 Test and Maintenance Diagnostic Status / Msg Input Main 1 0b 1 0,1 sec 1 sec Random Any Other
device s Alarms / Time Onboard Device
Computer
B1 6.2 Test and Maintenance Diagnostic Status / File Output Main 1 000b 0,05 0,1 sec 1 sec Garage Any Other
device s Alarms / Time Onboard Device
Computer
B1 6.3 Test and Maintenance Diagnostic Status / Msg Input Main 1 0b 0,05 0,1 sec 1 sec Garage Any Other
device s Alarms / Time Onboard Device
clear Computer
37
EN 1 31 49-1 :2004 (E)
Item Device Function Data Content Type Input/ Destination/ Size Recurrenc Acknowl Access Moment or Alt.
Output Source e edge Time location Source/Dest.
when
transmissio
n takes
place
Test and Maintenance Device Table: B1 6
B1 7.1 Gateway to ancient Bus (1 ) Main
Onboard
Computer
(1 ) Allowed for in other devices Gateway to Ancient Device Table Table: B1 7
B1 8.1 Radio Communication Radio In Service / Msg Output Main 2b 30 0,1 sec 1 sec Random
Device Status Out of Service Onboard
Computer
B1 8.2 Radio Communication Radio Special key Msg Input Main 2b 30 0,1 sec 1 sec Random
Device Control Functions Onboard
Computer
B1 8.3 Radio Communication Data Early / Late Msg Output Main 1 00b 30 0,1 sec 0,1 sec Cyclic
Device reception Instructions Onboard
Computer
B1 8.4 Radio Communication Data Early / Late Msg Input Main 1 00b 30 0,1 sec 0,1 sec Cyclic
Device Transmissi Instructions Onboard
on Computer
Radio Communication Device Table: B1 8
B1 9.1 Vehicle Equipment Bridge Vehicle Error Data File Input Main 2kb 0.04 1 0 sec 20 sec At Garage Short Range
Monitoring Onboard Comms.
Data Log Computer
Vehicle Equipment Bridge or Table: B1 9
Interface
38
EN 1 31 49-1 :2004 (E)
Event Nº Event Max Time Inventory Function Data Content Nº Devices Data Size per Data Data
Limit (Sec.) Table (B) / device (bytes) Throughput Throughput
Item Ref Nº (bytes per per additional
Second) vehicle
C1 .2 Vehicle 1 80
Inspection
39
EN 1 31 49-1 :2004 (E)
Event Nº Event Max Time Inventory Function Data Content Nº Devices Data Size per Data Data
Limit (Sec.) Table (B) / device (bytes) Throughput Throughput
Item Ref Nº (bytes per per additional
Second) vehicle
Totals: 40 20,00 0,00
C1 .5 Start Vehicle 10 6,1 Vehicle See Section 1 10 1 ,00
Monitoring 4.1 Notes
40
EN 1 31 49-1 :2004 (E)
Event Nº Event Max Time Inventory Function Data Content Nº Devices Data Size per Data Data
Limit (Sec.) Table (B) / device (bytes) Throughput Throughput
Item Ref Nº (bytes per per additional
Second) vehicle
60 1 ,8 Clock Data Date, Day, Day 1 20 0,33
Type, Time
41
EN 1 31 49-1 :2004 (E)
Event Nº Event Max Time Inventory Function Data Content Nº Devices Data Size per Data Data
Limit (Sec.) Table (B) / device (bytes) Throughput Throughput
Item Ref Nº (bytes per per additional
Second) vehicle
3 1 2,2 Vehicle Height/Width/ 1 10 3,33
Restriction Weight
Warning Limits/Light
On/Platform
Level
42
EN 1 31 49-1 :2004 (E)
Event Nº Event Max Time Inventory Function Data Content Nº Devices Data Size per Data Data
Limit (Sec.) Table (B) / device (bytes) Throughput Throughput
Item Ref Nº (bytes per per additional
Second) vehicle
In Service Events
C2.1 Arrive at first 1 7,1 Route and Route Nº, Dest 1 1 00 1 00,00
departure Destination ID, Via's &c
terminus to Display
commence
service
43
EN 1 31 49-1 :2004 (E)
Event Nº Event Max Time Inventory Function Data Content Nº Devices Data Size per Data Data
Limit (Sec.) Table (B) / device (bytes) Throughput Throughput
Item Ref Nº (bytes per per additional
Second) vehicle
30 1 0,1 1 Sign Selection/Funct 1 20 0,67
Management ions
(Int)
44
EN 1 31 49-1 :2004 (E)
Event Nº Event Max Time Inventory Function Data Content Nº Devices Data Size per Data Data
Limit (Sec.) Table (B) / device (bytes) Throughput Throughput
Item Ref Nº (bytes per per additional
Second) vehicle
Note #2: 30 4,2 Load Control Data 1 10 0,33 0,33
Estimation
45
EN 1 31 49-1 :2004 (E)
Event Nº Event Max Time Inventory Function Data Content Nº Devices Data Size per Data Data
Limit (Sec.) Table (B) / device (bytes) Throughput Throughput
Item Ref Nº (bytes per per additional
Second) vehicle
boarding / fare 30 1 ,3 Fare Stage Route & Fare 1 10 0, 33
collection Stage Data
46
EN 1 31 49-1 :2004 (E)
Event Nº Event Max Time Inventory Function Data Content Nº Devices Data Size per Data Data
Limit (Sec.) Table (B) / device (bytes) Throughput Throughput
Item Ref Nº (bytes per per additional
Second) vehicle
30 4,1 Load Load Data 1 10 0,33 0,33
Estimation
47
EN 1 31 49-1 :2004 (E)
Event Nº Event Max Time Inventory Function Data Content Nº Devices Data Size per Data Data
Limit (Sec.) Table (B) / device (bytes) Throughput Throughput
Item Ref Nº (bytes per per additional
Second) vehicle
C2.7 Random and 0 0,00
Cyclic Events
(see section 5)
C2.9 Arrive at 5 7,1 Route & Dest. Route Nº, Dest 1 1 00 20,00
terminus Display ID, Via...
48
EN 1 31 49-1 :2004 (E)
Event Nº Event Max Time Inventory Function Data Content Nº Devices Data Size per Data Data
Limit (Sec.) Table (B) / device (bytes) Throughput Throughput
Item Ref Nº (bytes per per additional
Second) vehicle
10 1 ,4 Validator Machine Serial 8 20 1 6,00 1 6,00
Management Nº
Totals: 1 70 33 30
C2.1 1 Stop Engine, 0 1 0,00
Dwell
49
EN 1 31 49-1 :2004 (E)
Event Nº Event Max Time Inventory Function Data Content Nº Devices Data Size per Data Data
Limit (Sec.) Table (B) / device (bytes) Throughput Throughput
Item Ref Nº (bytes per per additional
Second) vehicle
Totals: 40 20,00 0,00
C2.1 4 Finish Service 0 1 0,00
(see section 4)
50
EN 1 31 49-1 :2004 (E)
Event Nº Event Max Time Inventory Function Data Content Nº Devices Data Size per Data Data
Limit (Sec.) Table (B) / device (bytes) Throughput Throughput
Item Ref Nº (bytes per per additional
Second) vehicle
1 1 0,6 Fare Collection Fare Stage, 1 20 20,00
Zone
51
EN 1 31 49-1 :2004 (E)
Event Nº Event Max Time Inventory Function Data Content Nº Devices Data Size per Data Data
Limit (Sec.) Table (B) / Item device (bytes) Throughput Throughput
Ref Nº (bytes per per additional
Second) vehicle
Failure / Maintenance Events
C3.1 Bus Failure / 1 1 0,20 Engineering Misc. 1 20 20,00
Diagnose Tests
52
EN 1 31 49-1 :2004 (E)
Event Nº Event Max Time Inventory Function Data Content Nº Devices Data Size per Data Data
Limit (Sec.) Table (B) / Item device (bytes) Throughput Throughput
Ref Nº (bytes per per additional
Second) vehicle
C3. 8 C ou p l e to 5 1 5, 6 Te s t D e vi ce 1 1 0 2, 00 2, 00
d i a g n os ti cs S el e cti o n a n d
Te s t
C om m a n d s
5 1 6, 1 D i ag n os ti cs S tatu s / Al a rm s 1 1 0 2, 00
/ Ti m e
Te s t
C om m a n d s
h a rd wa re / D i s pl a y
s oftwa re
1 00 9, 1 Re cord S pe e ch C od e d S p e e ch 1 0, 00
M essages a n d C on tro l
1 00 1 1 ,2 G ara g e L i n e / I ti n e ra ri e s of a l l 1 32 0, 32
Rou te Ta bl e l i n e s of g ara g e
( 1 kb/l n , 3 2 l n s )
1 00 1 1 ,3 G ara g e L i n e / I ti n e ra ri e s of a l l 1 1 92 1 , 92
Rou te Ta bl e l i n e s of g ara g e
( 6 b/ve ct,
1 0 0 0 v/l n ,
32l n s)
53
EN 1 31 49-1 :2004 (E)
Event Nº Event Max Time Inventory Function Data Content Nº Devices Data Size per Data Data
Limit (Sec.) Table (B) / Item device (bytes) Throughput Throughput
Ref Nº (bytes per per additional
Second) vehicle
1 00 1 1 ,6 Fare Structure Tim es, Fare 1 1 00 000 1 000, 00
Stages, Fares
1 00 1 5, 6 Test Device 1 10 1 0, 00 1 0, 00
Selection and
Test
Comm ands
54
EN 1 31 49-1 :2004 (E)
Event Nº Event Max Time Inventory Function Data Content Nº Devices Data Size per Data Data
Limit (Sec.) Table (B) / Item device (bytes) Throughput Throughput
Ref Nº (bytes per per additional
Second) vehicle
C3.1 1 Update 0 1 0,00
database
55
EN 1 31 49-1 :2004 (E)
Event Nº Event Max Time Inventory Table Function Data Content Nº Devices Data Size per Data Data
Limit (Sec.) (B) / Item Ref Nº device (bytes) Throughput Throughput
(bytes per per additional
Second) vehicle
Garage Run In Events
C4.1 Dead run to 30 3,1 Passenger Count Data 1 10 0,33 0,33
garage Counting
56
EN 1 31 49-1 :2004 (E)
Event Nº Event Max Time Inventory Table Function Data Content Nº Devices Data Size per Data Data
Limit (Sec.) (B) / Item Ref Nº device (bytes) Throughput Throughput
(bytes per per additional
Second) vehicle
30 1 0,1 1 Sign Selection / 1 20 0,67
Management Functions
(Int)
57
EN 1 31 49-1 :2004 (E)
Event Nº Event Max Time Inventory Table Function Data Content Nº Devices Data Size per Data Data
Limit (Sec.) (B) / Item Ref Nº device (bytes) Throughput Throughput
(bytes per per additional
Second) vehicle
10 1 0,1 Vehicle Driver ID 1 20 2,00
Security Confirmation
58
EN 1 31 49-1 :2004 (E)
Event Nº Event Max Time Inventory Table Function Data Content Nº Devices Data Size per Data Data
Limit (Sec.) (B) / Item Ref Nº device (bytes) Throughput Throughput
(bytes per per additional
Second) vehicle
60 7,3 Display Format, Dest. 1 1 0 000 1 66,67
Database Text, Route
Number
59
EN 1 31 49-1 :2004 (E)
Event Nº Event Max Time Inventory Table Function Data Content Nº Devices Data Size per Data Data
Limit (Sec.) (B) / Item Ref Nº device (bytes) Throughput Throughput
(bytes per per additional
Second) vehicle
60 1 1 ,4 VSCS Stats Passenger 1 96 000 1 600,00
Counts, arrival
time, stop time
per stop
(20b/stop, 40
stop/run, 40
run/day, 3
days)
60
EN 1 31 49-1 :2004 (E)
Event Nº Event Max Time Inventory Table Function Data Content Nº Devices Data Size per Data Data
Limit (Sec.) (B) / Item Ref Nº device (bytes) Throughput Throughput
(bytes per per additional
Second) vehicle
C4.5 Bus wash 30 1 0,00
C4.6 Park 10 1 5,7 Shut Down Switch off Eqpt 1 1 000 1 00,00
Cycle / Supply
61
EN 1 31 49-1 :2004 (E)
Event Nº Event Max Time Inventory Function Data Content N Devices Data Size per Data Data
Limit (Sec.) Table (B) / device (bytes) Throughput Throughput
Item Ref Nº (bytes per per additional
Second) vehicle
Random / Cyclic Events
C5. 1 Random Events 0,1 2,2 Alarms Paper Roll 2 2 40,00 40,00
Expired/Jamm
ed
62
EN 1 31 49-1 :2004 (E)
Event Nº Event Max Time Inventory Function Data Content N Devices Data Size per Data Data
Limit (Sec.) Table (B) / device (bytes) Throughput Throughput
Item Ref Nº (bytes per per additional
Second) vehicle
0,1 1 0,1 5 Voice Blocking 1 20 200,00
Announcer
Mgmt
63
EN 1 31 49-1 :2004 (E)
Event Nº Event Max Time Inventory Function Data Content N Devices Data Size per Data Data
Limit (Sec.) Table (B) / device (bytes) Throughput Throughput
Item Ref Nº (bytes per per additional
Second) vehicle
0,1 1 0,24 Radio Control Request 1 4 40,00
Functions Speech/ Select
Channel
64
EN 1 31 49-1 :2004 (E)
Event Nº Event Max Time Inventory Function Data Content N Devices Data Size per Data Data
Limit (Sec.) Table (B) / device (bytes) Throughput Throughput
Item Ref Nº (bytes per per additional
Second) vehicle
0,1 1 5,8 Emergency Interrupt/ 1 32 320,00
Shut Down Switch off all
eqpt and main
supply
65
EN 1 31 49-1 :2004 (E)
Event Nº Event Max Time Inventory Function Data Content N Devices Data Size per Data Data
Limit (Sec.) Table (B) / device (bytes) Throughput Throughput
Item Ref Nº (bytes per per additional
Second) vehicle
0, 1 1 5, 5 Confidence Status Data 1 10 1 00, 00
Messages
66
EN 1 31 49-1 :2004 (E)
1 .1 a Bus topology: Way in which the bus members are interconnected, e.g. star,
bus, etc.
1 .1 b Node: Access point on the bus for a set of data or a device on the
bus. A node without an address may receive broadcasted
messages only. Each node has a unique address (logical
node).
1 .1 c Bus segment: Part of bus without repeaters.
1 .1 d Device: Equipment (physical node) connected to the bus, which
presents a load to the bus.
1 .2 Min. no. of nodes: Minimum number of addressable nodes in a bus segment.
1 .3 Max. no. of nodes: Maximum number of addressable nodes in a bus segment.
1 .4 Max. no. of devices: Maximum number of devices connectable to a bus segment.
1 .5 Max. no. of segments: Maximum number of segments the bus can consist of.
1 .6 Min. Bus segment length: Minimum length of a bus segment without a repeater.
1 .7 Max. BUS segment length: Maximum length of a bus segment without a repeater.
1 .9 Expandability: What effort (configuration) is necessary in order for example,
to accept an extra member into the network:
· Auto configuration if the no. of devices or nodes is
changed.
· No hardware tuning is required if the no. of devices or
nodes is changed.
· The framing must allow for future expansion at the
application level.
2.1 - Intelligent device: Bus member with its own microprocessor. Data is prepared
before being transmitted.
- Non-intelligent device: E.g. sensors, digital inputs/outputs. No data processing in the
device.
2.2 Bus node structure Short description of the hardware / software architecture of an
access point to the bus. Example: "The buyable hardware
consists of a medium access unit (MAU), a protocol
ASIC/Chip and software which can be loaded into the
application processor", description of buffering, node
throughput, layers covered by node HW/SW, etc.
2.3 Availability of bus access List of existing firms which manufacture chip set and
hardware and software: possibly software for the bus system?
2.4 + Price of bus access Cost of chip set including software for the network
2.5 software and hardware: connection, for a) intelligent, b) non-intelligent devices.
Software is only necessary for intelligent devices.
2.6 Gateway: Special node as a connection between two or more different
bus systems (e.g. vehicle bus and train bus)
67
EN 1 31 49-1 :2004 (E)
68
EN 1 31 49-1 :2004 (E)
4.9 Frame length: The max. length of a data telegram transmitted without
segmentation from the sender to one or more receivers,
without protocol overhead.
4.1 0 File transfer: Ability to transfer files from application to application.
4.1 1 Software licence for Cost and structure of licences which manufacturers of
manufacturer: the bus members have to pay. (e.g. once only, for each
installed system, etc.)
4.1 2 Software licence for Cost and structure of licences, which end users have to
end user: pay. (e.g. once only, for each installed system, etc.)
4.1 3 Tools: List of tools for configuration, maintenance, error search, etc.
which are readily available.
5.1 Noise immunity: Minimum ratio of clean to noisy signals, which still guarantees
data transmission with an acceptable error rate.
5.2 Galvanic separation: Galvanic separation of the bus members, avoids disturbances
e.g. due to earth loops.
5.3 Realization of the
galvanic separation: Description of how the galvanic separation is realized.
5.4 Hamming distance: n data bits complemented by k check bits. The Hamming
distance defines how many bit errors in a data word of n+k
bits can be detected.
5.5 Error detection method: Description of methods of transmission error detection
(hardware and/or software), which are integrated.
5.6 Safe behaviour and Measures taken to ensure that a faulty bus member
Self-recovery: does not cause the complete network to crash. Independent
and automatic means of re-creating disrupted communication
from a defective device.
5.7 Network net Number of transmitted net data bits per second (net data
transmission speed: rate, bits of useful data without any protocol overhead). 8 bits /
byte, synchronous bus assumed.
5.8 Network data rate: Number of transmitted data bits per second (including protocol
overhead, framing, bit stuffing, etc.).
5.9 Minimum polling rate: minimum time interval with which a particular bus member is
prompted for its status (if there is any polling). This value
depends upon, among other things, how many bus members
must be polled.
5.1 0 Access latency: Maximum time for a bus member to access the bus when it
has data to transmit.
5.1 1 Bit coding: Method with which the bits are electrically represented to be
transmitted over the bus (Manchester, FFSK, etc.).
6.1 OSI-Layers covered by product (7 Layers):
Layers of the OSI-model, which are fully covered by the available product-
hardware/software, assuming that the missing layers have to be dealt with by the application
process.
1 : Physical (electrical signals)
69
EN 1 31 49-1 :2004 (E)
4: Transport (segmentation/repetitions)
7: Application (API)
6.2 Level of Standardization: List of all components, layers or functionalities of the bus,
which are already standardized. Level of standardization, e.g.
national, european or international.
70
EN 1 31 49-1 :2004 (E)
64 with/without repeater m
1 .3 Max. no. of nodes ---
1 .4 Max. no. of devices ---
1 .5 Max. no. of segments ---
1 .6 Max. bus segment length ---
1 .7 Min. bus segment length 40m m
1 .8 Max. bus length with repeaters 1 20m m
1 .9 Future expandability of installed bus Required m
2.1 Intelligent or non-intelligent devices connectable Both d
2.2 Bus node structure ---
2.3 Availability of bus access hardware / software on the market Guaranteed m
2.4 Price of non-intelligent bus access hardware / software Max.ECUs 30.-- d
2.5 Price of intelligent bus access hardware / software on the market Max.ECUs 1 20.-- d
2.6 Availability of gateways to other buses or train bus Yes d
71
EN 1 31 49-1 :2004 (E)
- Active: bridge d
- Fibre optic d
3.2 Bus cable structure ---
3.3 Cost of cabling / connectors Cheap (shielded cable, SUB-D connectors)
3.4 Power supply in bus cable Yes m
3.5 Transmission of audio data Not requested
3.6 Transmission of video data Not requested
4.1 Type of bus control Multimaster (> 1 master possible) d
4.2 Bus management method Must exist m
4.3 Interrupt / priority polling 1 0ms m
4.4 Priority scheme Yes m
4.5 Priority levels Min. 2 d
4.6 Broadcast feature Yes m
72
EN 1 31 49-1 :2004 (E)
73
EN 1 31 49-1 :2004 (E)
P os i ti on C ri te ri on Req u i re m e n t M a n d atory/d e s i ra b l e
m / d
- Pol l i n g of b u s s ta tu s , wi th re cog n i ti o n a n d d
i s ol a ti on of d e fe ct b u s m em b e rs .
- D e fe cti ve d e vi ce s s h ou l d i n d ep e n d e n tl y re - d
5. 9 M i n i m u m p ol l i n g ra te 1 0m s m
5. 1 0 Acces s l a te n cy ( g u a ran te e d m a xi m u m ) 1 0m s m
5. 1 1 B i t co d i n g --- m
6. 1 N u m b e r of O S I l e ve l s wh i ch s h ou l d b e co vere d b y th e 1 , 2 m
m a rketa bl e h a rd wa re a n d s oftwa re
6. 2 Le ve l of s ta n d a rd i zati on --- m
74
EN 1 31 49-1 :2004 (E)
5-3-Typical configuration for a bus or a tram with trailer
- Interchange display
centre
Short range communication - Local data transfer device, 1 2
system
to/from the vehicle
management
Train bus interface unit - 1
Load measurement device - Passenger load 1 2
measurement
Passenger counting device - Passenger counting 4* 8*
75
EN 1 31 49-1 :2004 (E)
Bibliography
76
blank
BS EN
13149-1:2004
BSI — British Standards Institution
BSI is the independent national body responsible for preparing
British Standards. It presents the UK view on standards in Europe and at the
international level. It is incorporated by Royal Charter.
Revisions
British Standards are updated by amendment or revision. Users of
British Standards should make sure that they possess the latest amendments or
editions.
It is the constant aim of BSI to improve the quality of our products and services.
We would be grateful if anyone finding an inaccuracy or ambiguity while using
this British Standard would inform the Secretary of the technical committee
responsible, the identity of which can be found on the inside front cover.
Tel: +44 (0)20 8996 9000. Fax: +44 (0)20 8996 7400.
BSI offers members an individual updating service called PLUS which ensures
that subscribers automatically receive the latest editions of standards.
Buying standards
Orders for all BSI, international and foreign standards publications should be
addressed to Customer Services. Tel: +44 (0)20 8996 9001.
Fax: +44 (0)20 8996 7001. Email: [email protected]. Standards are also
available from the BSI website at http://www.bsi-global.com.
In response to orders for international standards, it is BSI policy to supply the
BSI implementation of those that have been published as British Standards,
unless otherwise requested.
Information on standards
BSI provides a wide range of information on national, European and
international standards through its Library and its Technical Help to Exporters
Service. Various BSI electronic information services are also available which give
details on all its products and services. Contact the Information Centre.
Tel: +44 (0)20 8996 7111. Fax: +44 (0)20 8996 7048. Email: [email protected].
Subscribing members of BSI are kept up to date with standards developments
and receive substantial discounts on the purchase price of standards. For details
of these and other benefits contact Membership Administration.
Tel: +44 (0)20 8996 7002. Fax: +44 (0)20 8996 7001.
Email: [email protected].
Information regarding online access to British Standards via British Standards
Online can be found at http://www.bsi-global.com/bsonline.
Further information about BSI is available on the BSI website at
http://www.bsi-global.com.
Copyright
Copyright subsists in all BSI publications. BSI also holds the copyright, in the
UK, of the publications of the international standardization bodies. Except as
permitted under the Copyright, Designs and Patents Act 1988 no extract may be
reproduced, stored in a retrieval system or transmitted in any form or by any
means – electronic, photocopying, recording or otherwise – without prior written
permission from BSI.
This does not preclude the free use, in the course of implementing the standard,
of necessary details such as symbols, and size, type or grade designations. If these
details are to be used for any other purpose than implementation then the prior
BSI written permission of BSI must be obtained.
389 Chiswick High Road Details and advice can be obtained from the Copyright & Licensing Manager.
London Tel: +44 (0)20 8996 7070. Fax: +44 (0)20 8996 7553.
Email: [email protected].
W4 4AL