...
Logical Model
...
Following industry’s paradigm, Agnos Framework is made of 3 distinct layers aligned on EMVCo definitions and industry certification processes cycles:
...
Note: Payment applications are not necessarily clearly identified in that 3-tier model. Level3 is not an official term used in the industry. In that document, it is used to discriminate what pertains to the low level layer (i.e. platform services) versus the EMV contact certifiable libraries (i.e. the “kernels”). Level 3 may be hosted on a mobile phone, a secured payment device, a remote host server or split between an acceptance client and a server depending on architecture and security constraints of the payment solution. Agnos supports any type of architecture and has been ported onto different platforms, OS, and device contexts.
As depicted belowabove:
GPI is the sole library depending on the hardware platform (OS & Firmware). It behaves as a HAL. It is linked onto the operating system’s API provided by the device manufacturer. See [3] for more details on integration
Agnos is linked onto the GPI Interface
AgnosMW is linked onto the GPI Interface, and AGNOS Interface
AgnosEP is linked onto the GPI Interface, AGNOS Interface and AGNOSMW Interface
...