×
Namespaces

Variants
Actions

S60 3rd Edition applications download OTA

From Nokia Developer Wiki
Jump to: navigation, search
Article Metadata
Compatibility
Platform(s):
Symbian
Article
Created: robebran (26 Jun 2007)
Last edited: hamishwillee (31 Jul 2012)

S60 3rd Edition applications download Over-The-Air using OMA Download and OMA DRM


S60 3rd Edition platform offers a simple solution for downloading Over-The-Air Symbian applications. The solution is based on OMA Download and OMA DRM specifications. The solution is easy to be implemented and in the same time it offers the most reliable and trusted user experience.


S60 applications download OTA using OMA Download and OMA DRM - General Use Case

1. Browse - The user, with the help of a terminal resident browser, connects to the operator’s Web page to select the desired S60 application to be downloaded. The Web page should present the user some application-related information, like its price for instance.

2. Download - The user initiates the download. In accordance with OMA Download specifications the Download Descriptor will be first downloaded to the phone followed by the content. The content complies with OMA DRM specification. The delivery method is either OMA DRM Combined Delivery or OMA DRM Separate Delivery. After successful completion of the download, or in case of failure of the download, the server can receive adequate response through the specified OMA Download ‘Install Notification’ message.

3. Install - The user initiates the installation of the successfully downloaded application. The installation can be initiated immediately after the download or at some later point in time.

4. Preview - The user runs the successfully installed application. The downloaded OMA DRM object will allow the user to run the application based on given delivered constraints. Time-based or count-based OMA DRM constraints can be used, and they will be enforced by DRM License Manager. The successful execution of the downloaded application is the ultimate guarantee that the application is compatible with the user's device. It also allows the user to make a buy-decision after seeing the content.

5. Get Rights/Charge - The DRM License Manager will notify the user about the expiration of the rights for the downloaded application. It will instruct the user to make the final step: pay and get the associated Full Rights. If the user accepts to pay and to buy the Full Rights then she/he will be directed, through the device’s browser, to the appropriate Web page. The user will download the corresponding new OMA DRM object. The successful download will be notified to the server by the specified OMA Download ‘Install Notification’ message. This will also trigger the charging. The bill can be added to the user’s phone bill.


Fig. 1 shows a general view of how OTA Download of S60 applications is working in practice using OMA Download combined with OMA DRM.


Fig1.jpg

Fig. 1 S60 applications OTA Download using OMA Download with OMA DRM specifications – General View


As an example, Fig. 2 describes the OMA Download with OMA DRM Combined Delivery method.

Fig2.jpg

Fig. 2 S60 applications OTA Download using OMA Download and OMA DRM Combined Delivery method


Note: 1. In case of OMA DRM Separate Delivery method, the PIP file and the associated DRM object are handled in the following way:

  • For OMA DRM 1.0: while the user downloads the PIP file, the server pushes the Preview Rights via WAP Push to the device.
  • For OMA DRM 2.0: as part of the download process (e.g. as a second OMA Download Descriptor), the device downloads the Preview Rights.

    2. OMA DRM Combined Delivery with Preview Rights is supported only starting with S60 SDK Release 3. For devices based on S60 Release 2, Preview Rights can be used with OMA DRM Separate Delivery. OMA Download The effort to implement OMA Download is minimal. It is needed to create a so-called Download Descriptor file (DD file) for each piece of content and make simple changes in the HTTP server to enable the OMA Download protocol. All these are explained in the OMA Download specification available at http://www.openmobilealliance.org/ OMA DRM OMA DRM provides an established framework for content packaging, content distribution and rights management. The Operator or ISV should add a DRM server in order to support the OMA DRM specification. More information about OMA DRM and these three types of deliveries can be found at http://www.openmobilealliance.org/ . Nokia smartphones based on S60 3rd Edition are using OMA DRM 1.0 and 2.0. S60’s DRM License Manager solution, using the Protected Installation Package (PIP) and the constraints of OMA DRM 2.0 Rights Expression Language offer a very robust model for enforcing the OMA DRM constraints. DRM License Manager DRM License Manager is a component that can be used to protect native applications on S60 devices. It enables application developers to specify usage conditions for applications, as defined in OMA DRM specification. A protected application is packaged in a so-called Protected Installation Package (PIP) file. A PIP is a regular ZIP archive, which contains a set of Control and Data files alongside a SIS installation file. It is encrypted and stored in a DCF (DRM Content Format). Fig3.jpg Fig.3 PIP file format. During the installation of the SIS file, the files comprising the application are copied to their specified locations. Using the downloaded OMA DRM Rights object the DRM License Manager will encrypt the Data file extracted from the PIP file. The encrypted Data file will then be copied to its specified location (location is specified by a dummy placeholder within the SIS file). According to the DRM License Manager Guidelines the developer has to write the application so that during run-time it will check the existence of valid data within the Data file. Every run-time check needs on-the-fly decryption of the encrypted Data file. This is done by DRM License Manager and gives also the possibility to check for the validity of OMA DRM Rights object. More information regarding S60’s DRM License Manager can be found in the S60 SDK.
  • This page was last modified on 31 July 2012, at 10:42.
    118 page views in the last 30 days.
    ×