ISO TS 29284-2012 Intelligent transport systems - Event-based probe vehicle data《智能交通系统 基于事件的探测车辆数据》.pdf

《ISO TS 29284-2012 Intelligent transport systems - Event-based probe vehicle data《智能交通系统 基于事件的探测车辆数据》.pdf》由会员分享，可在线阅读，更多相关《ISO TS 29284-2012 Intelligent transport systems - Event-based probe vehicle data《智能交通系统 基于事件的探测车辆数据》.pdf（18页珍藏版）》请在麦多课文档分享上搜索。

1、 ISO 2012 Intelligent transport systems Event- based probe vehicle data Systmes intelligents de transport Donnes de sonde du vhicule bases sur les vnements TECHNICAL SPECIFICATION ISO/TS 29284 First edition 2012-12-15 Reference number ISO/TS 29284:2012(E) ISO/TS 29284:2012(E)ii ISO 2012 All rights r

2、eserved COPYRIGHT PROTECTED DOCUMENT ISO 2012 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the a

3、ddress below or ISOs member body in the country of the requester. ISO copyright office Case postale 56 CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 E-mail copyrightiso.org Web www.iso.org Published in Switzerland ISO/TS 29284:2012(E) ISO 2012 All rights reserved iii Contents Page F

4、oreword iv Introduction v 1 Scope . 1 2 Normative references 1 3 T erms and definitions . 1 4 Reference architecture . 2 4.1 Reference architecture for probe vehicle systems . 2 4.2 Extended information package for event-based probe data . 4 5 Event-based probe data message 7 5.1 Concept of core dat

5、a elements (from ISO 22837:2009) 7 5.2 Structure of event-based probe data message 7 5.3 Timestamp 8 5.4 Latitude . 8 5.5 Longitude . 8 5.6 Altitude 8 5.7 Event type object . 8 5.8 Confidence 8 5.9 System identification (optional) 8 5.10 Trust value (optional) . 9 6 Event type object 9 7 Reference e

6、vent-based probe data message 10 ISO/TS 29284:2012(E) Foreword ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies (ISO member bodies). The work of preparing International Standards is normally carried out through ISO technical committees.

7、Each member body interested in a subject for which a technical committee has been established has the right to be represented on that committee. International organizations, governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the Internat

8、ional Electrotechnical Commission (IEC) on all matters of electrotechnical standardization. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of technical committees is to prepare International Standards. Draft International Stand

9、ards adopted by the technical committees are circulated to the member bodies for voting. Publication as an International Standard requires approval by at least 75 % of the member bodies casting a vote. In other circumstances, particularly when there is an urgent market requirement for such documents

10、, a technical committee may decide to publish other types of document: an ISO Publicly Available Specification (ISO/PAS) represents an agreement between technical experts in an ISO working group and is accepted for publication if it is approved by more than 50 % of the members of the parent committe

11、e casting a vote; an ISO Technical Specification (ISO/TS) represents an agreement between the members of a technical committee and is accepted for publication if it is approved by 2/3 of the members of the committee casting a vote. An ISO/PAS or ISO/TS is reviewed after three years in order to decid

12、e whether it will be confirmed for a further three years, revised to become an International Standard, or withdrawn. If the ISO/PAS or ISO/TS is confirmed, it is reviewed again after a further three years, at which time it must either be transformed into an International Standard or be withdrawn. At

13、tention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO shall not be held responsible for identifying any or all such patent rights. ISO/TS 29284 was prepared by Technical Committee ISO/TC 204, Intelligent transport systems.iv ISO 2012

14、All rights reserved ISO/TS 29284:2012(E) Introduction Probe vehicle systems are being investigated and deployed throughout the world. It is expected that the number of practical systems will grow steadily over the next few years. In TC 204/SWG 16.3, probe vehicle systems and probe data have been exa

15、mined, and it is concluded that in many cases communications airtime will be a scarce and expensive commodity, and therefore efficient probe data reporting systems which rely on techniques to use airtime efficiently and economically are essential. One way to accomplish this is to shift data aggregat

16、ion tasks in to the probe vehicle itself. Vehicles that feature this advanced form of on board probe data processing will report information based on the occurrence of actual events as opposed to delivering a constant stream of raw vehicle probe data. Event- based probe data reporting will allow eco

17、nomic use of communication capacity. As probe vehicle systems have to collect and manage probe data from a variety of vehicles from different vehicle manufacturers, the standardization of these event-based messages is essential. To do this, a common framework for event-based probe vehicle message re

18、porting is also required. The purpose of this project is to develop (1) a reference architecture for event-based probe data reporting within an architecture which encompasses both this function and standard probe data reporting defined in ISO 22837; (2) the basic data framework for defining event-ba

19、sed probe data messages; and (3) the concrete definition of these messages. The benefits of this standardization include: It helps system developers and operators to specify efficient probe data collection and processing systems. It also promotes communication and mutual understanding among the deve

20、lopers and the operators of probe systems. It helps system developers who are developing probe vehicle systems to define a key tool for communications-efficient probe data systems, i.e. event-based probe data reporting. Probe data may be collected from various vehicles of different vehicle manufactu

21、rers. It provides a common framework for handling event-based probe data. ISO 2012 All rights reserved v Intelligent transport systems Event-based probe vehicle data 1 Scope This Technical Specification specifies: reference architecture for event-based probe vehicles which encompasses event-based pr

22、obe data and standard probe data elements (ISO 22837:2009); basic data framework of event-based probe data reporting, based on ISO 22837:2009; the definition of an initial set of event-based probe data elements. These elements will be commonly used in typical event-based probe data enabled applicati

23、on domains, such as traffic, weather, and safety. Standardizing these event-based probe data elements facilitates the development of probe vehicle systems and the distribution of probe data. This is not intended to be an exhaustive listing of event-based probe data probe data elements. This Technica

24、l Report provides a common framework for defining event-based probe data messages to facilitate the specification and design of probe vehicle systems. It provides concrete definitions of event-based probe data elements. It serves as a supplement to ISO 22837:2009, and specifies additional normative

25、data (probe data elements) that are delivered by an event-based probe data system. 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

26、 referenced document (including any amendments) applies. ISO 22837:2009, Vehicle probe data for wide area communications 3 T erms an d definiti ons For the purposes of this document, the following terms and definitions apply. 3.1 probe vehicle system system consisting of vehicles which collect and t

27、ransmit probe data and land-based centres which collate and process data from many vehicles to build an accurate understanding of the overall roadway and driving environment ISO 22837:2009, 4.1 3.2 vehicle sensor device within a vehicle that senses conditions inside and/or outside the vehicle or tha

28、t detects actions that the driver takes ISO 22837:2009, 4.2 TECHNICAL SPECIFICATION ISO/TS 29284:2012(E) ISO 2012 All rights reserved 1 ISO/TS 29284:2012(E) 3.3 probe data vehicle sensor information formatted as probe data elements and/or probe messages that is processed, formatted, and transmitted

29、to a land-based centre for processing to create a good understanding of the driving environment ISO 22837:2009, 4.3 3.4 event-based probe message stuctured collation of probe data elements that represents occurrence of a defined event for transmission to a land-based centre Note 1 to entry: An event

30、-based probe data message is sent only when a specific incident or event occurs. It is not transmitted in a periodic manner. The transmission of an event-based probe message itself indicates that an event has occurred. An event-based probe message is defined as a probe message that is not triggered

31、by a periodically occurring condition (i.e. time or distance). A typical trigger is the detection of a different situation by the vehicle on board system (i.e. low visibility or traffic jam entry). An event may be defined as a simple incident, such as a change in status of a standard probe data elem

32、ent (i.e. fog light switching state), or can refer to a complex incident detected by a detection algorithm (i.e. traffic jam entry). 3.5 probe data element data item included in a probe message ISO 22837:2009, 4.4 3.6 event-based probe data element item of data included in an event-based probe messa

33、ge, typically describing the event that has triggered the transmission of the message 3.7 core data element probe data element which appears in all probe messages ISO 22837:2009, 4.5 3.8 probe message structured collation of data elements suitable to be delivered to the onboard communication device

34、for transmission to a land-based centre Note 1 to entry: It is emphasized that a probe message should not contain any information that identifies the particular vehicle from which it originated or any of the vehicles occupants, directly or indirectly. In delivering a probe message to be transmitted

35、by the onboard communication device, the onboard data collection system will request that the message be packaged and transmitted without any vehicle or occupant identifying information. ISO 22837:2009, 4.6 3.9 processed probe data data from probe data messages which has been collated and analysed i

36、n combination with other data ISO 22837:2009, 4.7 4 Reference architecture 4.1 Reference architecture for probe vehicle systems The reference architecture for probe vehicle systems presents the initial categorization of system components and their relationships from a conceptual point of view. A com

37、ponent is depicted as a 2 ISO 2012 All rights reserved ISO/TS 29284:2012(E) UML class and represents an encapsulation of functions and data that is conceptually considered as an individual entity in the probe vehicle system. A relationship is depicted as a UML association and represents potential co

38、ntrol and/or data flow among components. Figure 1 Overall structure of the reference architecture for probe vehicle systems The followings are the components of this reference architecture. Onboard data source (from ISO 22837:2009). The onboard data source provides original data that will become a p

39、robe data element. Original data may be raw sensor data or data from other onboard applications. Onboard data sources may be (various types of) sensors, onboard systems, etc. Probe data element generation (from ISO 22837:2009). Probe data element generation creates probe data elements from original

40、data. All of the following cases are included: 1) no processing (probe data element is identical to original data), 2) normalize original data (probe data element is the result of performing a calculation or transformation on original data), and 3) process original data to generate new type of data

41、(multiple items of original data are processed, possibly over a time period, to produce the probe data element, e.g.“traffic jam detected”). E v e n t- b a s e d pr ob e d at a elem en t g e ne r at ion . Event-based probe data element generation creates from probe data elements that represents occu

42、rrence of a defined event. Probe message generation (from ISO 22837:2009). Probe message generation creates and formats probe messages from probe data elements and sends them to probe collection. Here, “send” is at the application layer, not the communication layer. Probe message generation manages

43、the timing of sending messages as an application issue. Actual message transmission out the vehicle is left to the communication layer. Probe message generation may refer to stored reference data, to assist with data transformation or to help determine whether a probe message should be sent. E v e n

44、 t- b a s e d pr ob e me s s a g e g e ne r at ion . Event-based probe message generation is a special type of probe message generation that creates and formats event-based probe messages from event-based probe data elements and sends them to probe collection when the event is detected. ISO 2012 All

45、 rights reserved 3 ISO/TS 29284:2012(E) Referenced data repository ( f r o m I S O 22837:2009). Referenced data repository holds data for reference by the probe message generator. Probe collection (from ISO 22837:2009). Probe collection is a land-side activity that receives probe messages sent by ve

46、hicles and extracts probe data from these messages. Probe processing (from ISO 22837:2009). Probe processing receives collected probe data from probe collection and processes it (for example, using analysis and fusion). Probe processing does not receive any information from probe collection that ide

47、ntifies the vehicle or driver. Probe application (from ISO 22837:2009). Application which uses information produced by probe processing. Other data source (from ISO 22837:2009). Other data source provides additional data that is used for probe processing and/or by probe applications. Other data sour

48、ces may be road authorities, police, weather information providers, etc. User (from ISO 22837:2009). Entity that receives services and/or information produced from probe data. Users may be drivers, road authorities, police, weather services, public agencies, individual users (of cell phones, PDAs),

49、etc. Each relationship in this reference architecture is represented as a data and/or control flow. The followings are those data and flow in this reference architecture. Original data (from ISO 22837:2009). Data used for probe data generation. Original data may be raw sensor data or data from other onboard applications. Reference data ( from ISO 22837:2009). Data stored in a repository and referred to for probe data generation. Reference data may be (among other things) historical data and/o