BS EN ISO 17575-2:2016定义了如何传达其他文件中定义的所有或部分数据元素结构 适用于此应用的任何通信堆栈和介质上的ISO 17575部分。这是适用的 只有移动通信链路（尽管有线链路，即后台连接，可以使用相同的 方法论）。建立到服务调用序列的链接，初始化通信通道，寻址 需要接收消息并转发有效负载。本部分提供的定义 ISO 17575标准包括所需的通信介质独立服务，由 抽象应用程序编程接口（API）。通信接口作为API在所选的编程环境中实现 前端（FE）系统。后端（BE）API的规范不在本部分的范围内 符合ISO 17575标准。本API的具体定义不在ISO 17575本部分的范围内。这部分 ISO 17575的定义了一个抽象API，定义了具体API的语义，如中所示 图3及其协议实施一致性声明（PICS）形式表（见附录B）。一 附录C中给出了具体API的示例。 没有区分摘要 以及具体的通信API，可以使用术语“通信API”或只是“API”。ISO 17575的这一部分还提供了相关API结构的详细规范 语句，一个关于如何实现它以及它在复杂的收费集群（如EETS）中的作用的示例 （见附件A至附件E）。交叉引用:ISO/IEC 9646-7ISO/IEC 8824-1ISO 14906:2011/Amd1:2015ISO 17573:2010ISO 17575-1:2016ISO 17575-3:20162004/52/EC2009/750/E购买本文件时提供的所有现行修订版均包含在购买本文件中。

BS EN ISO 17575-2:2016 defines how to convey all or parts of the data element structure defined in other parts of ISO 17575 over any communication stack and media suitable for this application. It is applicable only to mobile communication links (although wired links, i.e. back office connections, can use the same methodology).To establish a link to a sequence of service calls initializing the communication channel, addressing the reception of the message and forwarding the payload are required. The definition provided in this part of ISO 17575 includes the required communication medium independent services, represented by an abstract application programming interface (API).The communication interface is implemented as an API in the programming environment of choice for the Front End (FE) system. The specification of the Back End (BE) API is outside the scope of this part of ISO 17575.The definition of this API in concrete terms is outside of the scope of this part of ISO 17575. This part of ISO 17575 specifies an abstract API that defines the semantics of the concrete API as illustrated in Figure 3 and its protocol implementation conformance statement (PICS) proforma (see Annex B). An example of a concrete API is presented in Annex C. Where no distinction is made between the abstract and concrete communications APIs, the term "communications API" or just "API" can be used.This part of ISO 17575 also provides a detailed specification for the structure of associated API statements, an example on how to implement it and its role in a complex toll cluster such as the EETS (see Annex A to Annex E).Cross References:ISO/IEC 9646-7ISO/IEC 8824-1ISO 14906:2011/Amd1:2015ISO 17573:2010ISO 17575-1:2016ISO 17575-3:20162004/52/EC2009/750/ECAll current amendments available at time of purchase are included with the purchase of this document.