本文件定义并规定了支持交通和旅行领域数据和信息交换和共享使用的组件方面。 组件方面包括交换的框架和上下文、必要的数据内容、结构和关系以及通信规范，以使其独立于任何定义的技术平台。 本文件为以下参与者的任意两个实例之间的数据交换制定了规范: -？交通信息中心（TICs）； -？交通控制中心/交通管理中心（TCC/TMC）； -？服务提供商（SP）。 本文件也可供其他参与者使用，例如:。 g、 停车场经营者。 本文件包括以下类型的信息: -？用例和相关需求，以及与不同交换情况相关的特性； -？不同的功能交换配置文件； -？协议的抽象元素； -？交换的数据模型（所需的信息结构、关系、角色、属性和相关数据类型）。 为了建立一个新的技术交换框架，有必要将一个功能交换概要文件与一个提供互操作性领域的技术平台相关联，在这个领域中，可以预期技术级别的即插即用互操作性。此类互操作性域的定义不在本文件的范围内，但可在其他国际标准或技术规范（如。 g、 ISO？14827系列）。 本文件仅限于数据交换。有效负载内容模型的定义不在本文档的范围内。

This document defines and specifies component facets supporting the exchange and shared usage of data and information in the field of traffic and travel. The component facets include the framework and context for exchanges, the data content, structure and relationships necessary and the communications specifications, in such a way that they are independent from any defined technical platform. This document establishes specifications for data exchange between any two instances of the following actors: —？Traffic information centres (TICs); —？Traffic control centres/Traffic management centres (TCCs/TMCs); —？Service providers (SPs). This document can also be applied for use by other actors, e.g. car park operators. This document includes the following types of information: —？use cases and associated requirements, and features relative to different exchange situations; —？different functional exchange profiles; —？abstract elements for protocols; —？data model for exchange (informational structures, relationships, roles, attributes and associated data types required). In order to set up a new technical exchange framework, it is necessary to associate one functional exchange profile with a technical platform providing an interoperability domain where plug-and-play interoperability at a technical level can be expected. The definition of such interoperability domains is out of scope of this document but can be found in other International Standards or Technical Specifications (e.g. the ISO？14827 series). This document is restricted to data exchange. Definition of payload content models is out of the scope of this document.