Slide 1

D u k e S y s t e m s Android (Simplified) Jeff Chase Duke University Slide 2 Part 1: Background Slide 3 Slide 4 From Bloomberg Krall and General Counsel Bruce Sewell have amassed a team of lawyers from inside Apple and some of the top U.S. law firms to fight Samsung, HTC, and Googles Motorola Mobility unit over Googles Android mobile operating system and the smartphones and tablets that run on it. The fight is central to Apples identityit got 46.4 percent of its sales from the iPhone last quarter and 26 percent from the iPad. The iPhone generated $47 billion in sales last fiscal year. Apple and Samsung together make more than half of the smartphones sold in the world. Samsung is the biggest player in the global market and Apple is dominant in the U.S. The companies are vying for a market that grew 62 percent to $219 B Slide 5 Slide 6 Conspiracy theory? Slide 7 Leading tech companies are filled with good system builders with vision, strong principles, and a commitment to technological purity. Others in the company focus on market strategy and tactics. By US law their commitment to profits for the companys owners dominates other values. Good system builders learn to understand the social, legal, and market context for their work. Technology choices are always intertwined with market structure and strategic concerns. Slide 8 Unix, looking backward: UI+IPC Conceived around keystrokes and byte streams User-visible environment is centered on a text-based command shell. Limited view of how programs interact files: byte streams in a shared name space pipes: byte streams between pairs of sibling processes Slide 9 Unix, looking backward: upcalls Limited view of how programs interact with the OS. The kernel directs control flow into user process at a fixed entry point: e.g., entry for exec() is _crt0 or main. Process may also register a signal handlers for events relating to the process, (generally) signalled by the kernel. Process lives until it exits voluntarily or fails receives an unhandled signal that is fatal by default. data Protected system calls...and upcalls (e.g., signals ) Slide 10 X Windows (1985) Big change: GUI. 1.Windows 2.Window server 3.App events 4.Widget toolkit Slide 11 Unix, looking backward: security Presumes multiple users sharing a machine. Each user has a userID. UserID owns all files created by all programs user runs. Any program can access any file owned by userID. Each user trusts all programs it chooses to run. We deputize every program. Some deputies get confused. Result: decades of confused deputy security problems. Contrary view: give programs the privileges they need, and nothing more. Principle of Least Privilege Slide 12 Confused deputy http://finntrack.co.uk/http://finntrack.co.uk/, erights.org http://www.cap-lore.com/CapTheory/ConfusedDeputyM.html Bob has the Power. Bob wishes to hold the power and use it properly. Alice considers Bob her deputy in the use of this Power. Alice trusts Bob to deny the power to Mal. Mal wants the power. Can Mal trick Bob to get it? Slide 13 Android protection Each application (app) runs with its own identity. Each app has a private space of files, processes, etc. that defines a sandbox. It does not matter that they run on behalf of the same user: the code matters more than the user. No deputies! The system mediates access to the sensors and UI by applications. GPS, camera, microphone, touchpad, etc. Each app declares the named permissions it needs. subject to user approval Each app declares the permissions another app needs to interact with it. Slide 14 Slide 15 Part 2, Android technology The goal here is to present an overview of the Android structure, and rationale for that structure. We wont learn how to program Android apps. Detailed docs are available. developer.android.com What we offer is the conceptual underpinnings and connections to other OS concepts. We choose Android for its instructive value: open source. Some images are borrowed from material on the web. E.g., Google material: Anatomy and Physiology of Android Slide 16 [http://www.android.com] Virtual Machine (JVM) C/C++ Slide 17 Dalvik JVM (Interpreter) Bytecode is an abstract machine instruction set. Java source compiles to bytecode. Android apps compile to bytecode. Dalvik has various optimizations for the Android platform. Dalvik interprets Java bytecode. Slide 18 Android: components Apps declare typed components. metadata list of components (manifest) Components have upcall interfaces visible to system. System instantiates and destroys components driven by events in the system and UI. System upcalls components to notify them of lifecycle events. Apps may interact by typed messages among components. events (intents) object invocation (binder RPC) Component intents, RPC System App upcalls Slide 19 Components run in contexts Components are Java code. A component is a class in an app. Its name is (appname, classname). Apps are named as packages. Components run in JVM contexts. Each component runs at most one instance in exactly one context. Context is a process with a JVM and a trusted system library. Android library defines context object with system API. app context (app process) JVM+lib instances component launch (activate) Slide 20 Apps are isolated Components in the same app generally share a context. Components in different apps are always in different contexts. Apps cannot reference each others memory contexts: soft JVM protection hard process boundaries Apps interact only via IPC. intents, events service RPC and content put/get Apps run with distinct user IDs. Principle of Least Privilege app app sandbox context app files JVM+lib Slide 21 Component launch To launch a component: Select a JVM context to run it. Tell JVM to instantiate the class. System communicates with the context via its system library. System obtains info about the component from app manifest. Class component type: the component class descends from a system base class. List of event profiles (intent filters) that trigger component launch. System JVM+lib launch manifest read manifest load class app context app If there is no JVM context active for the components app, then the system must start one. Slide 22 App launch JVM+lib Linux kernel Activity Manager Service etc. JVM+lib Zygote start fork JVM+lib children setuid to app uid How do we launch the applications code? Exec? Zygote is a preinitialized warm JVM image for unborn children. Slide 23 App launch JVM+lib Linux kernel Activity Manager Service etc. JVM+lib Zygote No exec needed: all Android contexts run the same Linux program: the JVM. Fork is just right! launch open read App files forked child context Slide 24 Slide 25 Binder: object RPC channels JVM+lib Linux kernel Activity Manager Service etc. Android services and libraries communicate by sending messages through shared-memory channels set up by binder. JVM+lib Android binder A client binds to a service. Bindings are reference-counted. Services register to advertise for clients. an add-on kernel driver for binder RPC Slide 26 Android environment server JVM+lib Activity Manager Service etc. The Activity Manager maintains a binding to every app context. Apps call system APIs and receive events via binder RPC calls to/from Android Activity Manager etc. JVM+lib Slide 27 Post-note Zygote also forks a system service manager on system startup. SM is a process that forks a lot of the basic Java android services. SM looks for installed apps with binder services in the manifest, and starts those components. - They include daemons that listen to usb, audio etc. and send events Slide 28 Deactivating components and apps JVM+lib Activity Manager Service etc. The Activity Manager decides when to deactivate components and tear down app contexts. JVM+lib If a service has no bound clients, the system may deactivate it. X Slide 29 Deactivating components and apps JVM+lib Activity Manager Service etc. The Activity Manager decides when to deactivate components and tear down app contexts. JVM+lib If an app has no active components, the system may deactivate it. X Slide 30 Deactivating components and apps JVM+lib Activity Manager Service etc. The Activity Manager decides when to deactivate components and tear down app contexts. JVM+lib If an app has no active components, the system may deactivate it. X Slide 31 Deactivating components and apps Activity Manager Service etc. JVM+lib The user navigates with the screen and buttons, activating components and moving on. The components set up interactions among themselves as needed to serve the user. The system monitors activity and memory pressure and cleans up behind components as needed. Slide 32 The four component types 1.Activity. Display a screen. Push on a back stack. May be launched by other apps. 2.Service. Serve an API. Establish an external binder interface. Public methods are externally visible. 3.Provider. Get/put content objects. Serve a URI space with MIME types. Backed by SQLite database tables. 4.Receiver. Respond to events. E.g., low battery. Slide 33 Intents for activities and receivers Intents are named events. Components signal intents with various attributes and data. They declare filters to specify which intents they may receive. Filter specifies named permissions the sender must have. A component may invoke an activity with an explicit intent, which invokes a named target component. A component may broadcast an implicit intent for delivery to any interested receiver component. Sender names permissions that each receiver must have. The event may be sent to its receivers in order or in parallel. See also: implicit vs. explicit invocation in Garlan/Shaw. Explicit intents and ordered broadcasts may receive a result. Slide 34 Post-note We did not discuss the state diagrams on the following slides in any detail. But understand that each executing component is a finite state machine. States are defined by the component type. Transitions are driven by UI events and/or other system or app events. These events generate system upcalls or intents to the component, which change its state. Components in certain states are eligible to be reclaimed by the system. Slide 35 Activity System upcalls component as its state changes due to user actions. If another activity is started, the activity is paused. If a paused activity is not visible to the user, it is stopped. A stopped activity may be destroyed. And its app process may be killed. Slide 36 Saving/restoring activity state Slide 37 Service Services advertise one or more binder endpoints. Clients choose to bind/unbind (or unbind when stopped). A service with no bound clients may be shut down. Slide 38 Service Slide 39 For later Threading models and concurrency Each app has a main thread (activity thread) that controls its UI and invokes the upcalls of its components as they are needed. Apps must never block the activity thread. Components can create other threads in various ways. Binder/RPC structure Service threading/queue models and request handling RPC data translation Permission structure An extensible namespace of permissions whose meaning is defined by system or by apps. For any interaction, both components define the permissions needed by the other. Slide 40 A note on subsystems A subsystem is a server that provides system functions to untrusting contexts, but runs with only partial system privilege. E.g., this code cannot manipulate the hardware state except by invoking the kernel. Android AMS subsystem JVM+lib Android AMS manipulates contexts. With no special kernel support! It uses same syscalls as anyone else. Unix provides no syscalls for managing another context (just kill). AMS controls user contexts by forking them with a trusted lib, and issuing RPC commands to that lib. Linux kernel binder