Requirements
 
Prerequisite Knowledge
Basic understanding of the Flash authoring environment and prior experience developing mobile applications with Flash Lite for the S60 platform is recommended.
Required Products
User level
Intermediate
 

 
Additional Requirements

 
Nokia S60 Platform SDK for Symbian OS, for C++
 
Nokia SIS packaging tool
 
Nokia Multimedia Internet Toolkit 4.1
 
Web server
  • Hosted web server with privileges to upload files and configure mime types
 
Nokia S60 or Samsung mobile device
  • Flash Lite-enabled handset
 
As a mobile architect, I've spent some time researching the solutions to deliver Flash Lite content protected with digital rights management (DRM). Recently I authored a Developer Center article titled How to protect Flash Lite content with OMA DRM 1.0. To follow up on that research to protect Flash Lite media, I went a step further and found a way to protect Flash Lite content that is packaged using a Symbian installer, which uses the .sis file format.
A Symbian installer for Flash Lite content offers two major functionalities:
  • A launcher (Symbian C++ application) which launches Flash Lite content
  • A menu icon that allows the user to easily launch the Flash Lite content
To learn more about working with OMA DRM 1.0, please refer to the article referenced above.
You can use the method described here to protect Flash Lite content packaged into .sis format (also known as a SIS installer) on the following platforms:
  • Nokia S60
  • Samsung (based on S60 technology)
In this article, I'll provide information on how to package your Flash Lite mobile content into a Symbian installer, which is the first important step. I'll also cover how to create a Protected Installation Package (PIP) and describe the process for applying and testing the PIP package. For the purposes of this article, we'll be using the Nokia Mobile Internet Toolkit.
 

 
Packaging Flash Lite content into a SIS installer file

The first step to protect Flash Lite mobile content is to create a Symbian (also known as SIS) installer file (that uses a .sis file extension). This process allows you to package Flash Lite content into a single file that is ready for installation on a mobile phone.
The following article on the Adobe Developer Connection provides all of the code you need: Making a simple SWF launcher with Nokia Carbide.c++ IDE (for Symbian 3rd Edition).
In addition to the information listed above, you may also find the following online resources helpful:
 

 
Creating a Protected Installation Package (PIP)

A Protected Installation Package (PIP) allows you to protect content packaged in a SIS installer (.sis file) and uses the file extension .pip.
For the purposes of this discussion, let's imagine that you've created a Flash Lite application (test.swf) that contains content you wish to protect, and that you've packaged the SWF file into a Symbian installer named test.sis.
At this point, you'll also need to create a definition file with the .def file extension. The definition file (named datafiles.def) should contain the following text:
 
application test.swf application/x-shockwave-flash c:\DATA\Others\test.swf
The creation of the definition file is necessary because it defines which file will be protected, the protected file's MIME type and the location where the protected file will be stored on the mobile phone after it is installed.
Note: In order to successfully protect your Flash Lite content (test.swf) you must know the location where the SWF file will be installed on the device. The location (the path to a directory) must be defined in the datafiles.def file as shown above.
The next step involves creating a PIP file—which is basically a ZIP file. (It really is as simple as creating an archive (.zip file) that contains the files listed below, and then renaming the file extension from .zip to .pip).
In this theoretical example, the ZIP file you create would contain the following files:
datafiles.def
test.sis
test.swf
For more information and details about creating PIP files format, see the S60 Platform: Implementing OTA Application Delivery and Protection white paper posted on Forum Nokia.
In order to apply OMA DRM 1.0, you'll need to use one of the delivery methods outlined in the OMA DRM specification. The simplest way to do this is to create a mobile web page.
The following MIME types are defined for OMA DRM; you will need to configure them into your web server to ensure that OMA DRM protected files will be recognized by the mobile phone after they are downloaded.
 
application/vnd.oma.drm.rights+xml .dr application/vnd.oma.drm.rights+wbxml .drc application/vnd.oma.drm.content .dcf application/vnd.oma.drm.message .dm application/vnd.oma.drm.dd+xml .dd
Note: The application/vnd.oma.drm.message .dm is the only MIME type specifically required for OMA DRM Forward Lock 1.0.
Additionally, you'll need to set the following MIME types in order to support .pip and .sis file types:
 
application/x-pip pip x-epoc/x-sisx-app sis x-epoc/x-sisx-app sisx
To learn more about setting MIME types on your web server, see the following online documentation:
 

 
Applying OMA DRM 1.0 Forward Lock to a PIP file

In this section, I'll describe the process of using the Nokia Mobile Internet Toolkit (version 4.1) to apply OMA DRM Forward Lock 1.0 to a .pip file.
Describing the details for every option is outside the scope of this article, but if you have questions, you can refer to the Nokia Mobile Internet Toolkit 4.1 User Guide. The user guide contains a great deal of information to help you learn more about all the capabilities and features of the toolkit.
Follow the steps below to apply the OMA DRM 1.0 Forward Lock:
  1. Launch the Nokia Mobile Internet Toolkit 4.1 tool. If you have the Nokia S60 Platform SDK installed, you will see the following screen (see Figure 1).
 
The Nokia Multimedia Internet Toolkit 4.1 start-up screen
Figure 1. The Nokia Multimedia Internet Toolkit 4.1 start-up screen
 
  1. Select File > New. The Available Content Types screen appears. Select the Deployment tab in the interface and then select the DRM Message icon. Click OK (see Figure 2).
 
The Nokia Mobile Internet Toolkit 4.1 Deployment screen
Figure 2. The Nokia Mobile Internet Toolkit 4.1 Deployment screen
 
  1. This next part describes how to specify the type of DRM (digital rights management) that will be applied to the .pip file. There are four sections on this screen:
    • The first section, titled Select Message Type, allows you to select which type of OMA DRM 1.0 to apply to the content. Since we're using Forward Lock (which is the default setting), no changes are needed.
    • The second section, titled Load Media Content, allows you to load the file that you want to protect. In this case, we'll be uploading a PIP file (.pip). Be sure to leave the Content-Transfer-Encoding setting to binary.
    • The third section, titled Edit Headers, allows you to define the header information. In the Content-Type line, enter the following text into the Header Value field: application/x-pip
    • The fourth section, titled Specify Rights, is not used when applying the Forward Lock DRM. In future projects, if you choose to use another DRM protection method, there are several options available. Refer to the Nokia Mobile Internet Toolkit 4.1 User Guide for more information.
    After making these changes, the DRM definition window should look similar to the screenshot shown below (see Figure 3).
 
The DRM definition window
Figure 3. The DRM definition window
 
  1. Now we're ready to load the PIP file. In the second section, titled Load Media Content, click the Load Content… button. Browse your hard drive to select the file named test.pip.
  2. If you haven't already done so, be sure to type in the following text in the Header Value field of the Content-Type line: application/x-pip. This step is necessary because the toolkit doesn't natively recognize the Flash file format.
  3. Save the file. Enter the file name: test.dm (see Figure 4).
 
Apply OMA DRM 1.0 Forward Lock to the file named test.pip
Figure 4. Apply OMA DRM 1.0 Forward Lock to the file named test.pip
 
At this point, you've created a DRM message file that is ready for deployment. The next step involves uploading it to your web server so that it is available to be downloaded and installed on your mobile device.
Note: The digital rights protection will only be applied once a user downloads the test.dm file from the mobile website and installs it on the device.
 

 
Testing OMA DRM 1.0 Forward Lock on a protected PIP package

To test the protected PIP package (the content contained in the .pip file) you can follow the step-by-step instructions outlined in a previous article Developer Center article I authored, titled: How to protect Flash Lite content with OMA DRM 1.0. Use the steps provided and adapt them to test your mobile content.
In order to test the protection, you must first upload your test.pip file and generate the test.dm file using the Nokia Mobile Internet Toolkit as described in the previous section.

 
Where to go from here

Search for specific topics in the Forum Nokia Library to get more details about specific tasks and help with troubleshooting issues. The Forum Nokia Documentation page also contains a wealth of information to help you get started and answer any questions you may encounter.
Check out the Mobile and Devices Developer Center, where you'll find helpful articles and sample files to learn more about developing mobile applications. And be sure to visit the Flash Lite section of the Mobile and Devices Developer Center to learn more about programming strategies and techniques for delivering mobile content.
And if you haven't already, be sure to read the following related articles: