symbian 2.9. Device Management Application lifecycle management Symbia O the set of currently ir plications.The management object uses the Symbian OS sofware install component to carry out the requests and therefore supports the application types software installer supports currently including SIS files,JAR files and JAD files Installation of applications includes the ability to upgrade to a newer version. OMA DM Client Alert Mechanism The Symbian OS DM framework API has been extended to allow device software to alert the DM l emnommche ver e e 8eeatament generic client alert mechanism correlator using HTTP only over a secured transport,i.e.TLS updating the DM Account Object to the 1.2 version ded API will require the same platform security capabilities as existing ework. de OM clier base recare become more complicated,network operators and IT departments are finding more and more alue in providing esate where the DM session has ended before the DM activity ended cn as M session has ended Upgrado OMA DataSync suppor toversion 1.2 A A)L been updated to be support for the suspend and resume features of OMA Data Sync 1.2 new APls to support filtering of synchronisations The new APIs allow a filter to be applied to the data to be synchronised.The filters will be passed to the DataSync server as part of the session,in compliance with the OMA DS 1.2 protocol.The ehei怡eoArwareeaenaedbatbevReuRormieratnIeise8geeeamaseoi the filters to be used. of r to restrict the data t ample of this would be to filter out attachments in email 6 www.symbian.com2.9. Device Management Application lifecycle management Symbian OS v9.2 includes an OMA DM-compliant management object, which is a plug-in to the Symbian OS OMA DM framework. This connects to an OMA DM server to allow the server to manage the applications on a Symbian OS device. The remote server, using the management object, is able to list the set of currently installed applications, request installation of new applications and request removal currently installed applications. The management object uses the Symbian OS software install component to carry out the requests and therefore supports the application types software installer supports currently including SIS files, JAR files and JAD files. Installation of applications includes the ability to upgrade to a newer version. OMA DM Client Alert Mechanism The Symbian OS DM framework API has been extended to allow device software to alert the DM server that a condition has occurred, which requires intervention from the network operator or IT department. The implementation communicates with the server using the OMA DM 1.2 Generic Client Alert mechanism. The DM framework conforms to the mandatory requirements of the OMA DM 1.2 specifications. In particular: • generic client alert mechanism • correlator • using HTTP only over a secured transport, i.e. TLS • updating the DM Account Object to the 1.2 version. Processes calling the extended API will require the same platform security capabilities as existing clients of the DM framework. This makes available a basis on which to provide OMA compliant remote diagnostic client software. The ability to provide customer care solutions and diagnostics solutions which are cost effective across a very large user base requires a solution which is standards based. As devices become more complicated, network operators and IT departments are finding more and more value in providing these solutions. This will also be used by asynchronous device management activity such as firmware update where the DM session has ended before the DM activity ended and there is need to report status back to the server. Upgrade OMA DataSync support to version 1.2 The Open Mobile Alliance (OMA) DataSync protocol in Symbian OS v9.2 has been updated to be version 1.2 compliant. In particular, it includes: • support for the suspend and resume features of OMA Data Sync 1.2 • new APIs to support filtering of synchronisations The new APIs allow a filter to be applied to the data to be synchronised. The filters will be passed to the DataSync server as part of the session, in compliance with the OMA DS 1.2 protocol. The actual filters supported are determined by the data provider plug-in for each application service. The user interface API will be extended to allow the UI to interact with the user to select and modify the filters to be used. Filtering of synchronisations allows a user to restrict the data that is available on small footprint devices compared to that which is held on the server. A prime example of this would be to filter out attachments in email. 6