scope:

This part of ISO 17575 defines how to convey all or parts of thedata element structure defined in other parts of ISO 17575 over anycommunication stack and media suitable for this application. It isapplicable only to mobile communication links (although wiredlinks, i.e. back office connections, can use the same methodology).To establish a link to a sequence of service calls initializing thecommunication channel, addressing the reception of the message andforwarding the payload are required. The definition provided inthis part of ISO 17575 includes the required communication mediumindependent services, represented by an abstract applicationprogramming interface (API). The communication interface isimplemented as an API in the programming environment of choice forthe Front End (FE) system. The specification of the Back End (BE)API is outside the scope of this part of ISO 17575. The definitionof this API in concrete terms is outside of the scope of this partof ISO 17575. This part of ISO 17575 specifies an abstract API thatdefines the semantics of the concrete API as illustrated in Figure3 and its protocol implementation conformance statement (PICS)proforma (see Annex B). An example of a concrete API is presentedin Annex C. Where no distinction is made between the abstract andconcrete communications APIs, the term ?communications API? or just?API? can be used.