mRCertificate afterwards. See Figure 11.2 for the scenario overview. In a more detailed view, there are three system objects belonging to the munici- pality. It is the platform, the local IT Infrastructure (Legacy system), and the Civil Service Delivery Platforms Citizen Municipality 1 : send request() 2 : create mRCertificate() 3 : send notification() 4 : retrieve mRCertificate() Figure 11.2 Municipality's service overview. servant as the human actor. The citizen sends his request to the platform, which in return first sends a notification back about the incoming request and then forwards the request to the Civil servant for approval. After this, the request is sent to the Legacy system, where the mRCertificate is created. After that, the Civil servant has to approve this mRCertificate. Furthermore, there is a final notification sent to the mobile to inform the citizen that he can pick up his mRCertificate. Finally, the mRCertificate needs to be retrieved by the citizen using the document retrieval service described before (see Figure 11.3). 11.3.1 Secure Service Request Creation and Dispatch This section describes all the steps required from the mobile user who uses the JAVA mobile application in order to securely create a request for m-government online service and dispatch it to the platform. Time-stamping authority is an entity which provides valid and digitally signed time-stamp tokens. In order for a mobile user to request a specific m-government service, following all the steps described in this paragraph, he/she must successfully complete the following: To successfully install the secure stand-alone JAVA application on the mobile device. On Secure JAVA Mobile Application Citizen SWEB platform Legacy system Civil servant 1: send request() 3 ind:request() 2 send notification() 4 : approve request() 5 send request() 6 create mRCertificate() 7 send mRCertificate() 8 approve mRCertificate() 9 : send mRCertificate() 10 send notification() 11 : retrieve mRCertificate() 12 : send mRCertificate() Figure 11.3 Muni