VIVID Runtime and Secured Content Delivery System on Tizen

Transcription

1 VIVID Runtime and Secured Content Delivery System on Tizen Ariro Nagayama Acrodea Inc. TDC2013 Confiden'al 1

2 Company Profile Corporate Name: Acrodea Inc. (acro+idea=acrodea) Established: July 2004 Consolidated Sales: 2,961 M Yen ($30M) FY2012 Employees: 167 Group Companies: AMS,Inc. Main business: Ø Smartphone Solutions Ø Contents Services Ø Middleware Solutions Acrodea Korea Inc. Device DRM Social game development VIVID Runtime/VIVID UI Confiden'al 2

3 Presentation summary ü Native application executables can be treated as data by utilizing VIVID Runtime. ü By encrypting data with our ARG, even if the data is extracted, it will not execute on an unauthorized terminal. ü For this reason, native applications can be distributed in an encrypted format with our DRM processing. ü Acrodea intends to monetize this business at the electronic delivery platform for DRM-protected native applications. Confiden'al 3

4 1. VIVID Runtime Confiden'al 4

5 What is VIVID Runtime? To enable the same application binary to be executed on any mobile terminal. VIVID Runtime = Program Execution Environment The same binary program operates without any underlying OS dependence. Offers full C++ functionality across multiple environments. No Game Engine Dependence Dynamically linked shared libraries are also supported. Confiden'al 5

6 Features Improves software portability, lowers cost and fosters consistency on multiple platforms Brings application development advantages Provides an attractive platform to both mobile operators and handset makers Development process non-reliant upon handset environment Confiden'al 6

7 VIVID Runtime Architecture on Tizen Apps Application (portable binary) (*.rpk) Library (portable binary) (*.so) Runtime Launcher Low API Object loader Object parser OpenKODE Object relocator Dynamic extension resolver Extension High API EGL 2D & 3D lib Network lib OpenGLES OpenAL lib More.. OpenSLES Core Base System Graphics & UI Multimedia Tizen Kernel Linux Kernel Confiden'al 7

8 Tizen APIs Cover VIVID Runtime Requirement The following native APIs are used to link functions when porting with VIVID Runtime. - OpenKODE => Base-Libc & POSIX API - OpenKODE Extension => System Sensor Accelerometer - OpenSLES => Multimedia Audio IO Audio Output - Launcher /Loader => UI-OpenGL Confiden'al 8

9 VIVID Runtime Application on Tizen Touchscreen and sensor events generated from Tizen are transferred to Runtime apps via Runtime s OpenKODE interface. Expressions related to visual graphics and audio are sent to UI and multimedia APIs, respectively. VIVID Runtime thread API OpenKODE OpenGLES Window rendering (UI APIs) Touch / Sensor events (System APIs) More.. OpenSLES Audio output (Multimedia APIs) Launcher VIVID Runtime application Executable File + Resources Confiden'al 9

10 Architecture: Additional Native Bindings Application Loader Module Providing a plug-in system for defining additional native functions that should be available for the portable application. Enables additional hardware capabilities To be efficiently exposed to the ported side, e.g, GPS and accelerometer Dynamic linking Function discovery at runtime using dlopen() / dlsym() style calls Direct.so linking (optional) Confiden'al 10

11 Selection of Development Environment Any dev platform may be used, if the compiler (gcc) supports elf objects. Developers can work in their accustomed environment. ü Dev environment with debugger can be built without IP fees. ü Open platform provides public releases of all notices. ü No charges are assessed for information. Dev Environment with Ready Access Confiden'al 11

12 Dev Environment s 4 Main Features Desktop ARM Simulator Software Development Kit Easy Porting Integration Kit *For Device Manufacturers. Objective C/C++, ECMAScript are supported. Built-in support for shared libraries (SysVr4-style shared objects) Confiden'al 12

13 Porting: Typical Application Development Process Application development Develop using Eclipse IDE Test and debug using ARM Simulator environment Packaging Create application package Executable External dependencies Data files Privileges Signing and certification Testing Install and test on a developer provisioning profile installed on the handset Use the stress-testing tools in the ARM simulator Provisioning Submit to the provisioning authority for approval process Approval Confiden'al 13

14 Typical Integration Process Overview OpenKODE Implement OpenKODE, EGL and other media abstraction APIs on the target handset Use the provided conformance tests to verify API functionality Application loader module porting Integration test with provided test suite of binary portable applications Additional native function bindings Expose any non-standard functionality via custom native binding plug-ins Final testing Confiden'al 14

15 2. Secured Content Delivery System Confiden'al 15

16 Acrodea Content Delivery System Overview Content distribution server features content management and content encryption facilities. Distribution server encrypts automatically. Content data generates rights object with encryption key generated on basis of User ID. App authenticates at content usage, based on User ID. User with Unauthorized ID cannot use downloaded content. ID is unique to user. User ID unique to service or unique to terminal (IMSI, IMEI, etc) is used. Device Content Content Unusable, even if copied to another device. App Content (e.g. Vivid Runtime RPK) ID Encryption module (DRM feature) Send encryption key Admin/Developer Site Provisioning For example: IMSI / IMEI Selectable by service Download Encryption module Content Content encryption based on Key Distribution Server Confiden'al 16 User Mgmt Register Env Mgmt CP Content Management

17 Acrodea DRM for Game Apps ü Protection from illicit copying of video/audio ü Designed to protect downloaded content ü Data and apps are all subject to encryption as data ü Device ID detected to confirm device Game Content Register CP.exe.so Resources App (.rpk) Executables Encryption (CP) Device ID Encryption Module Send device ID for DL request Download Send device ID for billing Billing Key Content Distribution Server Encryption module Game Content Billing Server Encryption module Billing Key generated on device ID basis Confiden'al 17

18 DRM Feature Comparison w/acrodea DRM w/o Acrodea DRM Scope of DRM Premium (pay) and free apps, content files Premium (pay) apps only Encryption Apps and content encrypted App data is not encrypted DRM settings per handset DRM keys are uniquely identified by IMSI (or IMEI, MAC address, etc.) Google ID used; not handset discrete Network connection at app launch Not required Required Copy protection Encryption prevents copying Root permission access enables copying Confiden'al 18

19 Features Comparison Table Dalvik Dalvik/NDK iphone C/C++ development Objective-C development DRM (Encryption) 3rd party SDK support IDE environment Eclipse Visual Studio Eclipse Eclipse X-Code OS abstraction VM/Native Native VM VM/Native Native Performance High Mid/Low High/Mid High Confiden'al 19

20 Tizen game demo Confiden'al 20

21 Thank you! Contact to: Confiden'al 21