Transport information and control systems - Data interfaces between centres for transport information and control systems - Part 3: Data interfaces between centres for intelligent transport sytems (ITS) using XML (Profile A)
|Publication Date:||1 January 2019|
|ICS Code (Transport in general):||03.220.01|
|ICS Code (IT applications in transport):||35.240.60|
This document is applicable to data exchange between different systems. This document defines the message rules and procedures for communication between transport information and control systems using XML. This document clarifies how to package end-application messages and relevant data. This document defines the mechanism to request end-application data from the client and to deliver the requested data from the supplier. Several profiles are defined, however only Profile A is defined in this document. Other profiles will be defined in future parts of the ISO 14827 series of standards. A system can be both a client and a supplier of another system simultaneously, using multiple sessions.
Rules and procedures for exchanging data-packets in lower layers are out of scope of this document. These functionalities can be implemented using generic protocols defined in the industrial standards. However this document defines how to use these protocols.
Data definition used in specific end-applications is out of scope in this document.
A network following this document comprises multiple kinds of systems. Each system can be viewed as an element including databases and interfaces, as shown in Figure 2:
This document is applicable to "communication interface" only. It is specified to meet the requirements of communication between ITS centres. However, it is designed in a generic fashion and thus can be used for data exchanges in other parts of the ITS field as well.
The framework for communication between centres using XML and the area that is prescribed by this document is shown in Figure 3. This document defines message rules and procedures for communication utilizing XML. In addition, this document explains how to use these protocols.
This document defines a Platform Specific Model (PSM) for exchange, which specifically uses XML. A PSM is an actual implementation of a Platform Independent Model (PIM) for exchange. A PIM is defined in another standard. When implementing a specific PSM, a Functional Exchange Profile (FEP), which is a selection of data exchange features, is identified. This document provides a FEP in Annex A.