BS ISO 14827-1-2006 Transport information and control systems - Data interfaces between centres for transport information and control systems - Message definition requirements《运输信息.pdf

《BS ISO 14827-1-2006 Transport information and control systems - Data interfaces between centres for transport information and control systems - Message definition requirements《运输信息.pdf》由会员分享，可在线阅读，更多相关《BS ISO 14827-1-2006 Transport information and control systems - Data interfaces between centres for transport information and control systems - Message definition requirements《运输信息.pdf（20页珍藏版）》请在麦多课文档分享上搜索。

1、BRITISH STANDARDBS ISO 14827-1:2005Transport information and control systems Data interfaces between centres for transport information and control systems Part 1: Message definition requirementsICS 03.220.01; 35.240.60g49g50g3g38g50g51g60g44g49g42g3g58g44g55g43g50g56g55g3g37g54g44g3g51g40g53g48g44g5

2、4g54g44g50g49g3g40g59g38g40g51g55g3g36g54g3g51g40g53g48g44g55g55g40g39g3g37g60g3g38g50g51g60g53g44g42g43g55g3g47g36g58BS ISO 14827-1:2005This British Standard was published under the authority of the Standards Policy and Strategy Committee on 9 January 2006 BSI 9 January 2006ISBN 0 580 47156 XNation

3、al forewordThis British Standard reproduces verbatim ISO 14827-1:2005 and implements it as the UK national standard.The UK participation in its preparation was entrusted to Technical Committee EPL/278, Road transport informatics, which has the responsibility to: A list of organizations represented o

4、n this committee can be obtained on request to its secretary.Cross-referencesThe British Standards which implement international 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 “Sea

5、rch” 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 ob

6、ligations. aid enquirers to understand the text; present to the responsible international/European committee any enquiries on the interpretation, or proposals for change, and keep UK interests informed; monitor related international and European developments and promulgate them in the UK.Summary of

7、pagesThis document comprises a front cover, an inside front cover, the ISO title page, pages ii to v, a blank page, pages 1 to 10, an inside back cover and a back cover.The BSI copyright notice displayed in this document indicates when the document was last issued.Amendments issued since publication

8、Amd. No. Date CommentsReference numberISO 14827-1:2005(E)INTERNATIONAL STANDARD ISO14827-1First edition2005-11-01Transport Information and control systems Data interfaces between centres for transport information and control systems Part 1: Message definition requirements Systmes de commande et dinf

9、ormation des transports Interfaces de donnes entre les centres pour systmes de commande et dinformation des transports Partie 1: Exigences relatives la dfinition du message BS ISO 14827-1:2005ii iiiContents Page Foreword iv Introduction v 1 Scope . 1 2 Normative references . 2 3 Terms and definition

10、s. 2 4 Symbols and abbreviated terms . 3 5 Requirements 4 5.1 Two-way data exchange. 4 5.2 High-level definition 4 5.3 Definitions define expected functionality. 4 5.4 Timing and other issues 5 5.5 Additional attributes. 5 6 Message definition requirements 5 6.1 Name 5 6.2 Definition . 5 6.3 Remarks

11、. 5 6.4 Message body . 5 6.5 Message type 5 6.6 Subscription type 6 6.7 Initial publication 6 6.8 Subsequent publications . 6 6.9 Id. 6 Annex A (normative) Information object specification 7 Annex B (informative) Examples 8 Annex C (informative) Concept of operations. 10 BS ISO 14827-1:2005iv Forewo

12、rd 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 technic

13、al 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 el

14、ectrotechnical 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 t

15、he member bodies for voting. Publication as an International Standard requires approval by at least 75 % of the member bodies casting a vote. 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 id

16、entifying any or all such patent rights. ISO 14827-1 was prepared by Technical Committee ISO/TC 204, Intelligent transport systems, Working group 9, with the collaboration of: European Road Transport Telematics Implementation Co-ordination Organisation (ERTICO); Comite Europeen de Normalisation (CEN

17、); American Association of State Highway and Transportation Officials (AASHTO); Institute of Transportation Engineers (ITE); and National Electrical Manufacturers Association (NEMA). ISO 14827 consists of the following parts, under the general title Transport information and control systems Data int

18、erfaces between centres for transport information and control systems: Part 1: Message definition requirements Part 2: DATEX-ASN BS ISO 14827-1:2005vIntroduction In the 1980s and 1990s, transport networks became increasingly congested and computer technologies were deployed to more efficiently manag

19、e the limited transport network. As these systems were deployed, it became increasingly important to integrate nearby systems to properly provide the required services. One of the first efforts to standardize the interface between transport control centres was a European Union effort led by the DATE

20、X Task Force. In May 1993, this group was established as a horizontal activity to coordinate the diverging developments which were ongoing within the framework of the Advanced Transport Telematics (ATT) Programme. Within the ATT Programme, three different data exchange systems were developed, namely

21、 INTERCHANGE, EURO-TRIANGLE and STRADA. The group produced a set of basic tools to meet existing needs, including a common Data Dictionary, a common set of EDIFACT messages and a common Geographical Location Referencing system. The initial solution provided a common interface which satisfied the bas

22、ic requirements of existing systems and was named the Data Exchange Network (DATEX-Net) Specifications for Interoperability. During the initial efforts to deploy this standard, there was a growing sense that the message structure should be better organized and should be defined using Abstract Syntax

23、 Notation One (ASN.1) rather than EDIFACT. ASN.1 presents a standard notation for the definition of data types and values. A data type is a class of information (for example, numeric, textual, still image or video information). A data value is an instance of such a class. ASN.1 defines several basic

24、 types and their corresponding values, and rules for combining them into more complex types and values. These types and values can then be encoded into a byte stream according to any of several standardized encoding rules. Efforts to standardize communications between transport control centres were

25、also underway in other parts of the world. In 1997, all of these efforts began to merge, with the United States developing the initial draft of the ASN.1 structures for the Data Exchange in Abstract Syntax Notation (DATEX-ASN). These structures, called data packets, were then placed within a procedu

26、ral context and submitted to the ISO standardization process. A portion of the submittal dealt with the specification of messages. As this portion of the document could apply to various protocols, it was placed in ISO 14827-1. The remainder of the original submittal formed the basis of the Applicati

27、on Layer protocol and was placed in ISO 14827-2. Thus, Part 2 defines only one way to implement the messages that are specified in the format defined by Part 1. Due to the flexibility required by the rapidly developing Transport Information and Control Systems environment, the resulting Internationa

28、l Standard uses a very generic structure. Thus, although initially intended to be an International Standard for TICS, it is flexible enough to be used for virtually any data exchange. BS ISO 14827-1:2005blank1Transport Information and control systems Data interfaces between centres for transport inf

29、ormation and control systems Part 1: Message definition requirements 1 Scope This part of ISO 14827 defines the format that should be used to document those end-application messages that are to be exchanged between and among central systems. The format is protocol-independent to the extent practical

30、. For example, this one format can be used to define data exchanges that may apply to DATEX-ASN, CORBA, or other application protocols. In general, each system can be viewed as consisting of the interfaces as shown in Figure 1: Key 1 application interface 2 operator interface 3 communication interfa

31、ce 4 database interface 5 communications cloud 6 client system 7 server system NOTE The communications cloud between the systems may be complex or simple. Figure 1 System interface This part of ISO 14827 deals only with the communication interface and is at a very high level. Other parts define how

32、end-application messages can be exchanged using various application layer protocols. While this part of ISO 14827 has been designed to meet the unique requirements of a TICS environment, it has been designed in a generic fashion and thus could be used for other data exchanges as well. BS ISO 14827-1

33、:20052 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. ISO/IEC 7498-4, Inf

34、ormation processing systems Open Systems Interconnection Basic Reference Model Part 4: Management framework ISO/IEC 8824-1, Information technology Abstract Syntax Notation One (ASN.1) Specification of basic notation ISO/IEC 8824-2, Information technology Abstract Syntax Notation One (ASN.1) Informat

35、ion object specification ISO/IEC 8825-1, Information technology ASN.1 encoding rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER) ISO/IEC 8825-2, Information Technology ASN.1 encoding rules: Specification of Packed Encoding Rules

36、 (PER) ISO 9735, Electronic data interchange for administration, commerce and transport (EDIFACT) Application level syntax rules 3 Terms and definitions For the purposes of this document, the following terms and definitions apply. 3.1 application layer top layer of the OSI seven-layer model as defin

37、ed in ISO/IEC 7498-4 NOTE This layer defines the structure and format of the data packet content along with the rules and procedures for exchanging data packets. 3.2 center any computer or network that is required to meet a standardized communications interface over a fixed-point communications netw

38、ork, regardless of whether the “center” is the only system within the building or just one of many, or even if the “center” is located in the field NOTE This part of ISO 14827 only deals with communications that are between “centers”. 3.3 client computer or application which requests and accepts dat

39、a from a server computer or application using some kind of protocol 3.4 command data packet which is prepared by one system in order to control some function(s) of another system NOTE Commands may be conveyed as a subscription (request) or publication (reply) depending on the design of the specific

40、data exchange. 3.5 data packet entity of data that can be sent between end-application systems in order to exchange information NOTE A data packet relates to the Application Layer of the OSI stack and may be broken into several pieces by lower layer protocols. BS ISO 14827-1:200533.6 end application

41、 message message data structure that has been associated with a specific meaning and which, when properly sent in a data packet, an instance of the structure can convey information between systems NOTE A data structure might, for example, be specified to include a list of speeds from detector statio

42、ns. This one data structure could be used to specify the content of several messages (e.g. the list of current speeds being detected, the list of stored speeds that will trigger a congestion warning if current values fall below the indicated level, or a request for a list of locations where the curr

43、ent speed is less than the indicated speed). An instance of the message would then contain actual values. 3.7 message instance specific instance of an end application message 3.8 message specification documentation defining the meaning of a message, the result of applying this part of ISO 14827 to a

44、 specific message 3.9 profile International Standard that defines rules by only combining requirements of other International Standard EXAMPLE An application profile is a profile that specifies the application, presentation, and session layers by referencing a group of other International Standards.

45、 3.10 protocol set of formal rules describing how to transmit data, especially across a network 3.11 publication reply data which have been prepared by a server, usually in response to a subscription NOTE In some cases, a publication may be termed a “reply” or a “response”. 3.12 server computer or a

46、pplication which receives and responds to requests for data from client computers or applications using some kind of protocol 3.13 subscription request data packet which is prepared by a client in order to request current or future publication(s) NOTE In some cases, a subscription may be termed a “r

47、equest”. 4 Symbols and abbreviated terms ASN.1 Abstract Syntax Notation 1 (ISO/IEC 8824-1 and ISO/IEC 8824-2) BER Basic Encoding Rules (ISO/IEC 8825-1) CORBA Common Object Request Broker Architecture BS ISO 14827-1:20054 DATEX-ASN Data Exchange in Abstract Syntax Notation EDIFACT Electronic Data Int

48、erchange for Administration, Commerce and Transport (ISO 9735) OID Object Identifier OSI Open Systems Interconnect PER Packed Encoding Rules (ISO/IEC 8825-2) TICS Transport Information and Control Systems 5 Requirements This part of ISO 14827 provides a standardized format that can be used to define

49、 end application messages for multiple application protocols; each application protocol has its own unique set of services. In order to provide a practical definition of messages, a number of assumptions were made about the services provided by the lower layers of the protocol stack and overall design concepts. These assumptions are documented in this clause. NOTE Nothing in this part of ISO 14827 removes the agency responsibility to ensure that the message does not contravene any legal obligation placed upon them by the laws of