ISO TR 24098-2007 Intelligent transport systems - System architecture taxonomy and terminology - Procedures for developing ITS deployment plans utilizing ITS sy.pdf

《ISO TR 24098-2007 Intelligent transport systems - System architecture taxonomy and terminology - Procedures for developing ITS deployment plans utilizing ITS sy.pdf》由会员分享，可在线阅读，更多相关《ISO TR 24098-2007 Intelligent transport systems - System architecture taxonomy and terminology - Procedures for developing ITS deployment plans utilizing ITS sy.pdf（20页珍藏版）》请在麦多课文档分享上搜索。

1、 Reference number ISO/TR 24098:2007(E) ISO 2007TECHNICAL REPORT ISO/TR 24098 First edition 2007-03-15 Intelligent transport systems System architecture, taxonomy and terminology Procedures for developing ITS deployment plans utilizing ITS system architecture Systmes intelligents de transport Archite

2、cture, taxinomie et terminologie des systmes Procdures pour dvelopper des plans de dploiement ITS en utilisant une architecture ITS ISO/TR 24098:2007(E) PDF disclaimer This PDF file may contain embedded typefaces. In accordance with Adobes licensing policy, this file may be printed or viewed but sha

3、ll not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In downloading this file, parties accept therein the responsibility of not infringing Adobes licensing policy. The ISO Central Secretariat accepts no liability in this area.

4、 Adobe is a trademark of Adobe Systems Incorporated. Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by

5、ISO member bodies. In the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below. ISO 2007 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electron

6、ic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address 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

7、Web www.iso.org Published in Switzerland ii ISO 2007 All rights reservedISO/TR 24098:2007(E) ISO 2007 All rights reserved iii Contents Page Foreword iv Introduction v 1 Scope . 1 2 Normative references . 1 3 Terms and definitions. 1 4 Abbreviation 2 5 Basic policy of ITS deployment. 2 5.1 Realizatio

8、n of regional ITS. 2 5.2 National ITS architecture . 3 6 The procedure for developing ITS deployment plans. 4 6.1 Framework. 4 6.2 Procedure 4 6.3 Requirements 6 Annex A (informative) Examples of ITS deployment guidelines . 7 Bibliography . 12 ISO/TR 24098:2007(E) iv ISO 2007 All rights reservedFore

9、word 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. Each member body interested in a subject for which a techn

10、ical 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 International Electrotechnical Commission (IEC) on all matters of

11、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 Standards adopted by the technical committees are circulated to

12、 the member bodies for voting. Publication as an International Standard requires approval by at least 75 % of the member bodies casting a vote. In exceptional circumstances, when a technical committee has collected data of a different kind from that which is normally published as an International St

13、andard (“state of the art”, for example), it may decide by a simple majority vote of its participating members to publish a Technical Report. A Technical Report is entirely informative in nature and does not have to be reviewed until the data it provides are considered to be no longer valid or usefu

14、l. Attention 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/TR 24098 was prepared by Technical Committee ISO/TC 204, Intelligent transport systems. ISO/TR

15、 24098:2007(E) ISO 2007 All rights reserved v Introduction This Technical Report was developed by ISO/TC 204, WG 1, Architecture, in order to provide a procedure for developing Intelligent Transport System (ITS) deployment plans utilizing ITS system architectures. It is well perceived in the ITS com

16、munity that understanding the system architecture is significant for the realization of ITS, which extends over wide areas on service domains, system sizes, and relating stakeholders and users. Those who deploy ITS systems within a specific region need to consider the coverage area, as well as exist

17、ing inventories. This Technical Report facilitates the introduction of ITS at regional levels through the development of the ITS deployment plans by utilizing regional ITS architectures. Examples of ITS deployment guidelines are given in Annex A. TECHNICAL REPORT ISO/TR 24098:2007(E) ISO 2007 All ri

18、ghts reserved 1 Intelligent transport systems System architecture, taxonomy and terminology Procedures for developing ITS deployment plans utilizing ITS system architecture 1 Scope This Technical Report describes the procedure for developing Intelligent Transport System (ITS) deployment plans utiliz

19、ing ITS system architectures. The document consists of the basic policy of ITS deployment and the procedure for developing ITS deployment plans. Framework, procedures and requirements for developing regional ITS deployment plans utilizing regional ITS architecture are reported. 2 Normative reference

20、s 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. ISO 14813-1:2007, Intelligent transport systems

21、 Reference model architecture(s) for the ITS sector Part 1: ITS service domains, service groups and services ISO/TR 14813-5:1999, Transport information and control systems Reference model architecture(s) for the TICS sector Part 5: Requirements for architecture description in TICS standards 3 Terms

22、and definitions For the purposes of this document, the following terms and definitions apply. 3.1 institutional architecture architecture based on political or administrational infrastructure partitioning and its division of responsibilities (rather than functions) ISO 14813-5:1999 3.2 ITS service c

23、onsists of a product or activity targeted to a specific type of ITS user NOTE 1 Adapted from ISO 14813-1:2007. NOTE 2 An ITS service group consists of one or more similar or complementary services provided to ITS users. An “ITS service domain” refers to a specific application area which comprises on

24、e or more service groups. 3.3 ITS stakeholders people or organizations that are involved in some way in the deployment of ITS NOTE Their involvement can be through use, manufacture of products, provision of services, or regulations. ISO/TR 24098:2007(E) 2 ISO 2007 All rights reserved3.4 ITS user one

25、 who directly receives and can act on ITS data, information or outputs that implement a measure of control NOTE 1 Adapted from ISO 14813-1:2007. NOTE 2 An ITS user is one who receives, directly or indirectly, or provides, the transaction of an ITS service. These users of ITS services may be human, s

26、ystems or environment monitoring. 3.5 logical architecture functional architecture functional viewpoint describes how the system behaves, including what it does with the inputs that it receives and how it produces the outputs; it may be described either from an object-oriented, or process-oriented,

27、perspective and describes the system according to its behaviour NOTE 1 Adapted from ISO 14813-1:2007. NOTE 2 In an object-oriented perspective, a logical architecture elaborates the conceptual behaviour and in so doing defines some detail of the objects. In a process-oriented perspective, the logica

28、l (or functional) architecture determines the nature of the system (in terms of functions and data stores), and describes its conceptual behaviour and the detail of what must be done to the inputs to produce the outputs. The logical architecture is independent of any hardware or software approach. 3

29、.6 physical architecture allocation of the logical architecture to physical entities but not including details of the deployment of specific numbers of systems or equipment at particular geographic locations NOTE 1 Adapted from ISO 14813-1:2007. NOTE 2 A physical architecture, whilst describing phys

30、ical configurations in system terms, is not specific to any particular location. 3.7 physical model subset of a physical architecture which mainly considers the realization of providing one or more service(s) 4 Abbreviation For the purposes of this document, the following abbreviation applies. ITS I

31、ntelligent Transport System 5 Basic policy of ITS deployment 5.1 Realization of regional ITS The general framework of ITS deployment within a region (or any other part of a nation, such as a city, state, or county) is described in Figure 1. The target is realization of regional ITS systems and provi

32、sion of ITS services to the users by the collaboration of subsystems that are implemented by relevant ITS stakeholders. An ITS deployment plan for a region will make the efficient implementation through the intelligible accountability and the consensus among the regional stakeholders. The plan is us

33、ed for obtaining a budget for deployment, for designing the regional ITS systems, and for promoting the deployment and operation of the systems within the region. ISO/TR 24098:2007(E) ISO 2007 All rights reserved 3Figure 1 Framework of regional ITS deployment 5.2 National ITS architecture There are

34、several ways in which a national ITS architecture can be used to create ITS deployment plans. These are illustrated in Figure 2. Figure 2 Relationship between regional and national ITS deployments The example in Figure 2 enables interoperability between the ITS systems deployed at nearby regions, as

35、 well as within the target region itself. ISO/TR 24098:2007(E) 4 ISO 2007 All rights reserved6 The procedure for developing ITS deployment plans 6.1 Framework A national architecture covers overall ITS services within a nation and this may be what is needed for some ITS deployments. However, a regio

36、nal architecture may be needed when only some of the ITS services within the national architecture are required. In order to realize sustainable ITS within a region or nation, it is necessary to identify the ITS services that are required, to establish subsystems by dividing roles among ITS-related

37、stakeholders, and to keep a close liaison between those stakeholders. To achieve this, it is necessary to prepare ITS deployment plans based on the regional or national ITS architecture. These plans will illustrate the division of roles and coordination between ITS stakeholders. Based on these plans

38、, it will be possible to negotiate and secure budgets and establish operational systems at the stakeholder level. 6.2 Procedure The procedure for developing an ITS deployment plan for a region or nation should be the following. Identify the appropriate ITS stakeholders and gain their cooperation and

39、 participation. With the stakeholders, define the ITS services that they want to see deployed. Describe the ITS physical system structure that is needed to provide the services. Define and agree upon the stakeholders roles for the ITS deployment. 6.2.1 Identifying the participation of appropriate IT

40、S stakeholders It is essential that the scope of the regional (or national) ITS architecture, and the identification and participation of the ITS stakeholders involved in the development process, are determined and agreed. The mobility of residents in daily activities should be taken into account (e

41、.g. commuting, shopping and business). The geographic coverage of the ITS architecture will depend on the area of jurisdiction belonging to its owners. Thus, regional ITS architecture may cover one or more metropolitan regions and transport infrastructures between them, and a city ITS architecture m

42、ay cover one city. The area where the stakeholders involved in the ITS development operate or administer should also be taken into consideration. However, the need for a regional ITS architecture should also depend on how much of the national ITS architecture it will include. Stakeholders involved i

43、n the development of the ITS architecture should include organizations that fit into one or more of the following types. These types should include those stakeholders that: want ITS: these will be local authorities that manage the highways, and road operators that will want ITS to improve the operat

44、ion of their transport networks; make ITS: these will be organizations that are component and system suppliers and/or infrastructure providers that will see ITS as providing them with extra business opportunities; use ITS: these will be travellers, pedestrians, PT passengers, plus those that move fr

45、eight; all of whom hope that ITS will improve the ways that they can travel; rule ITS: these will be organizations such as national and regional governments and standards bodies that regulate and control the way that ITS is deployed and implemented. ISO/TR 24098:2007(E) ISO 2007 All rights reserved

46、5 A broad range of stakeholders of several of the above types may exist within the area in which ITS is to be deployed. It is also important for any stakeholders whose existence is recognized during the ITS architecture development process be asked to participate, as appropriate. It is important to

47、ensure that outreach to the ITS stakeholders gains commitment to the usefulness and significance of the ITS architecture in the process of establishing the ITS systems that need to be deployed to provide the services. It is useful to nominate a leading stakeholder, sometimes called the “architecture

48、 champion” to urge all the stakeholders to participate positively in the establishment of the ITS systems. The leading stakeholder will normally review the area covered by the ITS architecture to be developed and identify the stakeholders participating in the development process. 6.2.2 Defining ITS

49、services Services to be provided within the area of the ITS deployment should be based on local issues and needs for transportation. The services that are required are normally selected from the list of ITS services described in the national ITS architecture or the framework ITS architectures that are to be adopted. Consideration must be allowed for the services currently existing in the region to be incorporated into the ITS architecture and the resulting ITS deployment. Issues arising in the area of