unication Figure 11.8 Possible m-government JAVA mobile WS application community. 11.4.1 GUI Object The GUI object of the proposed JAVA mobile Web Service application is respon- sible to show user interface that enable calling of authentication function for authentication of the end user and presenting the core functionalities to the end user. According to this, the GUI object communicates with the following modules: User Authentication module for JAVA application of the Security object. User PKI Registration module (XKMS module) of the Security object. User Authentication and Authorization module for the m-government plat- form (SAML module) of the Security object. m-residence module of the Business object. User Authentication module will be described in Section 11.4.3 (Security object) and other modules will be described in the next section. 11.4.2 Business Functionalities Object This object of the SWEB JAVA mobile application is responsible for realization of the core SWEB client-based functionalities: Secure requesting and receiving the m-residence certificate from the corre- sponding municipality SOA-based platform, receiving a notification and delivering the obtained certificate to some interested party. Secure sending of other kind of predefined message (e.g., m-invoice) to the corresponding municipality platform and receiving the notification from the platform. Both business functionalities have links to Security and Communication objects. Service Delivery Platforms 11.4.3 Security Object The Security object of the considered JAVA mobile application is responsible for over- application-level security functionalities. It consists of the following modules: Authentication module to the JAVA application XKMS module STS module XML-security module WS-security module Time-stamping module The above-mentioned modules will be briefly described in the following text. 11.4.3.1 User Authentication Module to the JAVA Mobile Application An end user could have the proposed JAVA application installed on his mobile phone/t