Tizen Operating System

Editor's Notes

• #2: Hi, Good morning everyone. I'm Udaykumar Pedduri, and one of Tizen platform architect at Samsung. and actively participating in designing Tizen architecture. Through this talk, I explain what the Tizen project is trying to achieve. and how the Tizen platform is architecturally designed to achieve them. These two things will lay down the basic background why and how one should develop Tizen applications. Finally I explain how we as Tizen platform developers are developing Tizen 3.0 platform. through this last thing, I give some basic information about platform development to those who want to participate in the project
• #3: I speak in this order and I'll talk about Tizen IVI architecture briefly too. IVI stands for In-Vehicle Infotainment.
• #4: Now I introduce Tizen to you.
• #13: Why is the Tizen important to you?
• #14: The most important point is that Tizen is W3C standard-based. as you can see in the graphics, HTML5 is being widely adopted for application development mainly due to its high portability. Recently many platforms like chromium OS and Firefox OS is trying to implement HTML5 standards and Tizen is one of them too. and most of the time, it has the top score in html5test.com. To application developers this means that you can develop your application first on Tizen, and then easily migrate your application to other platforms if they are ready to implement your application. Please, keep on eye on Tizen's html5 score. I’d like to suggest you to find the “10 useful HTML5 infographics”.
• #15: Tizen has an ambitious goal from the start. Tizen is not targetting only mobile devices category but also other device categories like PC, IVI currently and even TV, camera, and printer in future. To application developers, this means that your application can potentially get much wider audiences. We introduced a concept called a profile. We are defining a profile(or profiles) for each device category. Currently mobile profile and IVI profile are under active development.
• #16: Tizen is also getting strong support from industry. If Tizen can't get support from various industry sectors, Tizen could be just a marketing hype. But in reality, it's something important. As you can see, TA is formed by 11 companies. They are major manufacturers, operators and silicon vendors. They guide Tizen project to go in which direction. and TA has adopted ... for that guidance.
• #17: Tizen is one of open source project operated by Linux Foundation. As you can see, tizen is using various open source software. we couldn't have even thought creating Tizen, if open source software didn't exist. I think Tizen owe so much to open source community.
• #18: So,... Tizen is trying to be a good citizen in the open source world. Intel and Samsung maintain or ... Virtually everything newly developed .... To open source developers, this means that Tizen is a great chance to contribute to open source softwares. And to application developers, this mean that Tizen is likely to evolve very fast due to active participation from open source community. Even application developers can contribute to the project as a user, not platform developer, by fileing a bug, requesting a new feature, and something like that.
• #19: If you see the release history of the Tizen Mobile Profile, you can feel how much we are serious about commercialization of Tizen platform. This year, we released Tizen platform 3 times and now I can say it's pretty close to commercial-grade quality. We are continusouly fixing bugs, enhancing performances, resolving security issues to make it more close to commercialization so that other industry leaders and application developers can have confidence in investment onto Tizen.
• #20: Now, let's talk about Tizen architecture.
• #21: First, I'll talk about Tizen Mobile Profile Architecture because upto now, mobile profile is a kinda common profile.
• #22: Tizen is based-on Linux and on top of that, core layer exists. Core layer is composed of various components like app framework, graphics & UI, multimedia, web, messaging, location, security, and etc. There are several components which has adaptation interface for hardware differences. Core application can be written on top of core layer. And web framework and native framework provides dual API stack based on core interface.
• #23: Web framework ... Please, take the Tizen device APIs as extension to support wider range of more feature-rich web application. Native framework... OpenGL ES/EGL graphics driver should be provided at this layer.
• #24: Then why do we provide both web and native framework for application development? In contrast to what one might think,... native and web framework are complementary to each other. Web framework is relatively more portable, easy-to-develop, easy-to-learn. But native framework is relatively better in terms of performance and memory consumption and provides more features. And also, native framework enables reusing the existing engine and libraries written in C & C++ when developing applications.
• #25: You can mix web and native application depending on the characteristics or requirements of your application. If you want to build a highly portable application across various platforms, you may want to use only W3C standard APIs. If you want to build portable yet feature-rich applications, for example, it needs to access content informaton, filesystem, bluetooth, SMS/MMS, or communicate with other applications, then you can develop your application using Tizen web device APIs. What if your application needs to do background monitoring? You can make hybrid application so that most user interaction happen with web UI and back ground monitoring is done by native code because web framework does not support background process. Upto now, on iOS and Android OS, many web application has a form that core logic is implemented in native code and UI logic is implemented using webview . This form of applications can be easily migrated into native application with web control on Tizen. If high performance and feature richness are more important for your applications than portability, you can make it native applications.
• #26: Next, I want to talk about why there are two different native layers. native framework and core. Core focuses on ..... Core is basically not a layer for application development, but for platform implementation. For core, quality attributes like performance, lower power consumption, lower memory footprint, smaller image size, securities are much more important than application binary compatibilities. So it may be dramatically changed from a release to the other release. But for native framework, quality attributes like ABC or application development productivity are much more important. So it is well-documented, and assisted by various productivity tools.
• #27: So, there could be 4 types of application. web application native application hybrid application core application. but... Even though you're a developer working at a mobile device manufacturer, I recommend you to use core APIs at minimum. Core applications can be a maintenance nightmare because it does not guarantee backward compatibility at all.
• #28: web ui framework provides UI elements for consistent look-and-feel according to Tizen UX guideline
• #30: This is about internal architecture of web browser. Tizen web browser is following multiple process model. That means UI, web content, plugin are executed in a seperate process. This is because it is more responsive, more robust, more secure, can use multicore CPUs better. For example, with single process model, if something is wrong with plugin, it affects application's behavior but it does not with multiple process model
• #34: Next let's talk about IVI profile.
• #35: IVI device demands much more than mobile device. Let's think about a car. Rich set of sensors and cameras generating a bunch of real-time data may exist in the car. A couple of high-resolution display throughout the car may exist. A highly complex speaker & microphone system may target different zones individually It is necessary to integrate tightly with a various range of mobile devices Integration with cloud based services
• #36: Tizen IVI profile tried to be as compatible as possible to the compliance GENIVI defined. GENIVI is a large alliance between car manufacturers, chipset vendors, and service companies. GENIVI shapes various IVI requirements Fully-functional Tizen WRT (Web RunTime) Automotive Message Broker: a vehicle network abstraction framework that brokers information from the vehicle (e.g. from the CAN bus) to applications. Ghostcluster: an HTML5-based dashboard application that connects to AMB (Automotive Message Broker) to access vehicle data. Murphy policy manager: Murphy is a resource policy daemon, designed to do cross domain policy decisions in a configurable way. Hands-Free dialer ("lemolo"): a BT HFP (Hands-Free Profile) dialer application that uses oFono and BlueZ to make and receive phone calls through a bluetooth-paired mobile phone. dLeyna: dLeyna is an opensource project that provides high level APIs for creating DLNA enabled applications. Full HD video support: video playback is hardware-accelerated (via the VA-API) allowing you to play full HD videos (1080p). Dual-display support Wi-Fi tethering: allows you to turn your Tizen IVI device into a Wi-Fi hotspot Sample Applications A sane, consistent, optimized boot process Last user mode support Hardware accelerated graphics via Wayland Full access to automotive data Optimized application run-time using HTML technologies Infrastructure for orchestrating user experience based on driving conditions, ensuring driver safety and region specific regulatory requirements and addressed Murphy Policy Manager Enhancements beyond Audio UI Manager for IVI Tizen IVI 3.0
• #43: Next, let's talk about tizen 3.0 development model
• #44: It look like revolving, not evolving and not transparent to external open source community and had little chance for contribution. From 3.0, .... this means that contribution are happening publicly.
• #45: Tizen 3.0 becomes configurable to support multiple profiles with one code base. We divided sharable components and profile-specific components. As you can see. sharable components like sharable apps, shareable platform components, sharable SDK have its own place, and profile-specific components exists on profile directories. And each profile has its own configuration options for each shareable component. In this way, it's possible to build both smartphone ABC on ARM and IVI device XYZ on IA from the same code base.
• #46: To ensure public and transparent development, we implemented some development infrastructures. First, 3.0 feature discussion will happen at "Tizen Features" JIRA which I link here Secondly, 3.0 API discussion will primarily happen at tsg-arch-api mailing list and post-activities for each API such as unit TC development, TC verification, documentation and etc will be tracked on "Tizen APIs" JIRA. Discussion on platform development is already happening at dev mailing list. If you following the link, you can check out discussions. We created git directories according to the git directory hierarchy in the previous slide. There may be two seperate git directories per each component. Keep in mind that In that case, one is for 2.2 maintenance, the other 3.0 development.
• #47: Let's see 3.0 example git. we are developing 3.0 feature on tizen branch. you can see the tizen branch at the first shortlog entry. This module is under active development.
• #48: We are also operating build server. check out the build status of each build project, following the link.