How unit 5 is examined
This unit covers the constraints on mobile OS design, iOS and Android, and M-commerce with payments and security; the Commercial Mobile Operating Systems short note carries the most marks, then the 7-mark M-commerce questions.
Special Constraints & Requirements
<span style="display:inline-block;padding:.16em .6em;border:1.5px solid currentColor;border-radius:999px;font-size:.68em;font-weight:700;letter-spacing:.06em;text-transform:uppercase;opacity:.75">Low weight</span>
Definition. <mark>A mobile OS must run on small, battery-powered, always-connected devices, so it is designed around scarce power, memory, processing and display rather than raw performance.</mark>
Key points.
- Power is limited by the battery, so the OS must switch off idle radios, screen and CPU cores and schedule background work sparingly.
- Memory and storage are small and there is no swap disk, so the OS kills background apps instead of paging them out.
- Processors are slower than desktop ones, so the OS and its apps must be light and efficient.
- The screen is small and touch-driven, so the user interface needs gestures, an on-screen keyboard and adaptive layouts.
- Requirements are portability, real-time response for calls, constant connectivity (cellular, Wi-Fi, Bluetooth), security of personal data, and support for many hardware makers (heterogeneity).
Asked: [7 marks] (Dec 2024) What are the special constraints and requirements of operating systems of mobile devices?
Commercial Mobile Operating Systems
<span style="display:inline-block;padding:.16em .6em;border:1.5px solid currentColor;border-radius:999px;font-size:.68em;font-weight:700;letter-spacing:.06em;text-transform:uppercase;opacity:.75">High weight</span>
Definition. <mark>A mobile operating system is system software that manages the hardware, memory, power, networking and applications of a smartphone or tablet and provides the touch interface and services on which apps run.</mark>
Key points.
- Commercial mobile OSs are Android (Google, open source, Linux based), iOS (Apple, closed, Unix based), and the older Windows Phone, BlackBerry OS and Symbian.
- A mobile OS is layered: kernel and drivers at the bottom, then libraries and runtime, an application framework, and apps on top.
- It gives power management, touch and sensor handling, radio and connectivity management, and app sandboxing.
- It offers an app store and an update mechanism through which software is distributed.
- A Software Development Kit (SDK) is the bundle of compiler, libraries, APIs, emulator, debugger and documentation used to build apps for one OS (Xcode for iOS, Android SDK for Android).
- Examples of use are calls, messaging, navigation, banking and mobile commerce apps.
Short notes (any three).
i) Mobile OS. Points 1-4 above; conclude with apps such as calls and payments.
ii) SDK. Point 5 above; it contains APIs, tools, emulator and sample code, and cuts development time.
iii) DSR (Dynamic Source Routing). DSR is an on-demand ad hoc routing protocol in which the source puts the whole route in each packet header. Route discovery floods a Route Request (RREQ) that collects the node addresses it passes; the destination returns a Route Reply (RREP) along the reversed route, and the source caches it. Route maintenance uses Route Error (RERR) when a link breaks. It needs no periodic updates, but headers grow with route length.
iv) TCP and UDP.
| Point | TCP | UDP |
|---|---|---|
| Connection | Connection-oriented (three-way handshake) | Connectionless |
| Reliability | Acknowledgements and retransmission | No guarantee |
| Ordering | Ordered delivery | No ordering |
| Flow and congestion control | Yes | No |
| Speed and header | Slower, 20-byte header | Faster, 8-byte header |
| Use | Web, email, file transfer | Voice, video, DNS |
Pitfall: Writing only definitions for the short note loses marks; give one working or difference for each topic chosen.
Answer frame. Open with the definition of each of your three chosen topics; draw the RREQ/RREP route for DSR if you choose it, or the comparison table for TCP and UDP; develop each in 3-4 sentences; close with applications.
Asked: [14 marks] (Dec 2020) Write short notes (any three): i) Mobile Operating System ii) Software Development Kit iii) DSR iv) UDP and TCP
Software Development Kit: iOS
<span style="display:inline-block;padding:.16em .6em;border:1.5px solid currentColor;border-radius:999px;font-size:.68em;font-weight:700;letter-spacing:.06em;text-transform:uppercase;opacity:.75">Low weight</span>
Definition. <mark>iPhone OS (iOS) is Apple's closed mobile OS, developed with the iOS SDK (Xcode, Swift or Objective-C, simulator) and built as four layers.</mark>
Key points.
- Cocoa Touch is the top layer and gives the UI framework (UIKit), multitasking, touch and gesture handling, and push notifications.
- The Media layer provides graphics, audio and video services such as Core Graphics, Core Animation, OpenGL ES and AV Foundation.
- The Core Services layer provides fundamental services such as iCloud, networking, SQLite database, location and contacts.
- The Core OS layer is the base: kernel, drivers, security, Bluetooth, sockets and power management.
- Special mobile OS features are touch and gestures, sensors (GPS, accelerometer), power saving, constant connectivity, app sandboxing, and lightweight memory use unlike a desktop OS.
Asked: [7 marks] (Jun 2025) Explain in detail components of iPhone OS? List the special features of a Mobile OS.
Android etc.
<span style="display:inline-block;padding:.16em .6em;border:1.5px solid currentColor;border-radius:999px;font-size:.68em;font-weight:700;letter-spacing:.06em;text-transform:uppercase;opacity:.75">Low weight</span>
Definition. <mark>Android is Google's open-source, Linux-kernel-based mobile OS whose stack has five layers, and apps are built with the Android SDK.</mark>
Diagram. <figure class="ds-fig" style="margin:1.4rem 0;overflow-x:auto"><svg xmlns="http://www.w3.org/2000/svg" id="dsfig-u5-01" viewBox="0 0 252 338" width="252" height="338" role="img" aria-label="Android stack, top to bottom. App = Applications, Fw = Application Framework, Lib = Native Libraries, Art = Android Runtime, Ker = Linux Kernel"><style>#dsfig-u5-01 .e{stroke:#454C5A;stroke-width:1.4;fill:none}#dsfig-u5-01 .e.hi{stroke:#2340B8;stroke-width:2.6}#dsfig-u5-01 .n{fill:#FFFFFF;stroke:#16181D;stroke-width:1.4}#dsfig-u5-01 .n.hi{fill:#E3E9FC;stroke:#2340B8;stroke-width:2.2}#dsfig-u5-01 .n.rb-b{fill:#16181D;stroke:#16181D}#dsfig-u5-01 .n.rb-r{fill:#BD3227;stroke:#BD3227}#dsfig-u5-01 text{font-family:"JetBrains Mono",ui-monospace,Menlo,Consolas,monospace;font-size:13px}#dsfig-u5-01 .t{fill:#16181D;font-weight:500}#dsfig-u5-01 .t.inv{fill:#FFFFFF;font-weight:700}#dsfig-u5-01 .kd{stroke:#16181D;stroke-width:1.2}#dsfig-u5-01 .dot{fill:#16181D}#dsfig-u5-01 .ann{fill:#2340B8;font-size:11px;font-weight:700}#dsfig-u5-01 .lbl{fill:#6F7787;font-family:system-ui,-apple-system,sans-serif;font-size:12px;font-weight:700}#dsfig-u5-01 .ptr{fill:#2340B8;font-size:12px;font-weight:700}#dsfig-u5-01 .ah{fill:#454C5A}#dsfig-u5-01 .ah.hi{fill:#2340B8}#dsfig-u5-01 .wl rect{fill:#FFFFFF;stroke:#DCE0E7}#dsfig-u5-01 .wl .t{font-size:12px;font-weight:700}#dsfig-u5-01 .wl.hi rect{fill:#2340B8;stroke:#2340B8}#dsfig-u5-01 .wl.hi .t{fill:#FFFFFF}html.dark #dsfig-u5-01 .e{stroke:#B1B7C3}html.dark #dsfig-u5-01 .e.hi{stroke:#8FA3FF}html.dark #dsfig-u5-01 .n{fill:#161920;stroke:#E6E8ED}html.dark #dsfig-u5-01 .n.hi{fill:#1E2748;stroke:#8FA3FF}html.dark #dsfig-u5-01 .n.rb-b{fill:#E6E8ED;stroke:#E6E8ED}html.dark #dsfig-u5-01 .n.rb-r{fill:#FF7E71;stroke:#FF7E71}html.dark #dsfig-u5-01 .t{fill:#E6E8ED}html.dark #dsfig-u5-01 .t.inv{fill:#0F1115}html.dark #dsfig-u5-01 .kd{stroke:#E6E8ED}html.dark #dsfig-u5-01 .dot{fill:#E6E8ED}html.dark #dsfig-u5-01 .ann{fill:#8FA3FF}html.dark #dsfig-u5-01 .lbl{fill:#858D9C}html.dark #dsfig-u5-01 .ptr{fill:#8FA3FF}html.dark #dsfig-u5-01 .ah{fill:#B1B7C3}html.dark #dsfig-u5-01 .ah.hi{fill:#8FA3FF}html.dark #dsfig-u5-01 .wl rect{fill:#161920;stroke:#2A2E37}html.dark #dsfig-u5-01 .wl.hi rect{fill:#8FA3FF;stroke:#8FA3FF}html.dark #dsfig-u5-01 .wl.hi .t{fill:#0F1115}</style><defs><marker id="ah8" viewBox="0 0 10 10" refX="9" refY="5" markerWidth="7" markerHeight="7" orient="auto-start-reverse"><path class="ah" d="M0,1 L9,5 L0,9 z"/></marker><marker id="ahh8" viewBox="0 0 10 10" refX="9" refY="5" markerWidth="7" markerHeight="7" orient="auto-start-reverse"><path class="ah hi" d="M0,1 L9,5 L0,9 z"/></marker></defs><path class="e" d="M126,59 L126,105" marker-end="url(#ah8)"/><path class="e" d="M112.6,139.4 L54.8,197.2" marker-end="url(#ah8)"/><path class="e" d="M139.4,139.4 L197.2,197.2" marker-end="url(#ah8)"/><path class="e" d="M53.4,225.4 L111.2,283.2" marker-end="url(#ah8)"/><path class="e" d="M198.6,225.4 L140.8,283.2" marker-end="url(#ah8)"/><circle class="n" cx="126" cy="40" r="18"/><text class="t" x="126" y="40" dy=".35em" text-anchor="middle">App</text><circle class="n" cx="126" cy="126" r="18"/><text class="t" x="126" y="126" dy=".35em" text-anchor="middle">Fw</text><circle class="n" cx="40" cy="212" r="18"/><text class="t" x="40" y="212" dy=".35em" text-anchor="middle">Lib</text><circle class="n" cx="212" cy="212" r="18"/><text class="t" x="212" y="212" dy=".35em" text-anchor="middle">Art</text><circle class="n" cx="126" cy="298" r="18"/><text class="t" x="126" y="298" dy=".35em" text-anchor="middle">Ker</text></svg><figcaption style="font-size:.82em;opacity:.72;margin-top:.45rem">Android stack, top to bottom. App = Applications, Fw = Application Framework, Lib = Native Libraries, Art = Android Runtime, Ker = Linux Kernel</figcaption></figure>
Key points.
- Features: open source, free, customisable, multitasking, rich notifications, Google Play store, and wide device support.
- The Linux kernel manages drivers, memory, processes, power and security.
- Native libraries (SQLite, WebKit, OpenGL ES, libc) and the Android Runtime (ART, replacing Dalvik) sit above it.
- The application framework offers Activity, Content Provider and Notification managers, and Applications such as Phone and Browser run on top.
- The SDK contains the Java/Kotlin APIs, emulator, ADB, debugger and Android Studio; versions run from Cupcake to recent releases.
Asked: [7 marks] (Jun 2025) Explain about Android OS, features, software stack, SDK and their layers.
MCommerce : Structure
<span style="display:inline-block;padding:.16em .6em;border:1.5px solid currentColor;border-radius:999px;font-size:.68em;font-weight:700;letter-spacing:.06em;text-transform:uppercase;opacity:.75">Low weight</span>
Definition. <mark>M-commerce is buying, selling and paying for goods, services and information through wireless handheld devices such as mobile phones.</mark>
Key points.
- The structure has four parts: the mobile device (client), the wireless network (GSM, 4G, Wi-Fi), the gateway or middleware, and the host server with the merchant's database and payment system.
- A request flows from the device over the network and gateway to the web server and back.
- Pros are ubiquity, convenience and personalised location-based service.
- Cons are security risk, small screen and limited bandwidth.
- Examples are mobile banking, ticket booking, and shopping apps.
Asked: [7 marks] (Dec 2020) Explain structure, Pros and Cons of M-commerce.
Pros & Cons
<span style="display:inline-block;padding:.16em .6em;border:1.5px solid currentColor;border-radius:999px;font-size:.68em;font-weight:700;letter-spacing:.06em;text-transform:uppercase;opacity:.75">Low weight</span>
Definition. <mark>M-commerce is the transaction of business through mobile devices, and in India its value lies in reaching users who have phones but no computers.</mark>
| Pros in India | Cons in India |
|---|---|
| Ubiquity: over a billion phones give wide reach | Security: fraud, phishing and stolen phones |
| Convenience: shop and pay anywhere, any time | Small screen makes browsing and forms hard |
| UPI and wallets support cheap, instant payments | Poor connectivity and low bandwidth in villages |
| Reaches rural users with no bank branch or PC | Low digital literacy and language barriers |
| Location-based, personal offers | Battery limits and high data cost |
Asked: [7 marks] (Dec 2024) What is M commerce? Write its pros and cons in a developing country like India.
Mobile Payment System
<span style="display:inline-block;padding:.16em .6em;border:1.5px solid currentColor;border-radius:999px;font-size:.68em;font-weight:700;letter-spacing:.06em;text-transform:uppercase;opacity:.75">Not asked since 2022</span>
Definition. <mark>A mobile payment system lets a customer pay for goods and services with a mobile device instead of cash or cards.</mark>
Key points.
- Methods are mobile wallets (Paytm), UPI apps, SMS or USSD banking, NFC tap-to-pay and carrier billing.
- Workflow: the customer starts payment, the app sends it to the payment gateway, the bank verifies it with a PIN or OTP, and both sides receive confirmation.
- Security uses encryption, PIN, OTP and tokenisation; it is fast and cashless, but depends on network coverage.
- M-commerce types are mobile shopping, banking and ticketing, and current trends are UPI, QR and contactless payment.
Asked: [7 marks] (Jun 2025) Write short notes: i) M commerce ii) Mobile payment system
Security Issues
<span style="display:inline-block;padding:.16em .6em;border:1.5px solid currentColor;border-radius:999px;font-size:.68em;font-weight:700;letter-spacing:.06em;text-transform:uppercase;opacity:.75">Not asked since 2022</span>
Definition. <mark>Mobile security issues are the threats to a device, its data and its transactions from malware, theft and insecure networks.</mark>
Key points.
- Malware and malicious apps can steal data, so install apps only from trusted stores.
- Loss or theft of a device exposes data, so use screen locks, encryption and remote wipe.
- Insecure Wi-Fi allows eavesdropping and man-in-the-middle attacks, so use VPN and HTTPS.
- Phishing, SIM swap and weak authentication endanger payments, so use OTP and two-factor login.
Last-minute revision
- A mobile OS manages power, memory, touch, connectivity and apps on constrained devices.
- Constraints: limited battery, memory, CPU and screen; no swap disk.
- An SDK is compiler, APIs, emulator, debugger and documentation for one OS.
- iOS layers, top to bottom: Cocoa Touch, Media, Core Services, Core OS.
- Android stack: Applications, Framework, Libraries and ART, Linux kernel.
- DSR: source routing with RREQ, RREP and RERR.
- TCP is reliable and connection-oriented; UDP is fast and connectionless.
- M-commerce is transactions through wireless handheld devices.
- M-commerce pros: ubiquity and convenience; cons: security, small screen, bandwidth.
- Mobile payment methods: wallet, UPI, NFC, SMS or USSD.
Memory hooks
- iOS layers: "Can Mice Chew Oats" (Cocoa Touch, Media, Core Services, Core OS).
- Android stack: "All Frogs Like Kites" (Apps, Framework, Libraries, Kernel).
- M-commerce cons: "S-S-B" (Security, Small screen, Bandwidth).
- DSR messages: Request, Reply, Error.
Coverage checklist
- Special Constraints & Requirements: Dec 2024 constraints question.
- Commercial Mobile Operating Systems: Dec 2020 short notes (Mobile OS, SDK, DSR, UDP and TCP).
- Software Development Kit: iOS: Jun 2025 iPhone OS components and mobile OS features.
- Android etc.: Jun 2025 Android OS, stack and SDK.
- MCommerce : Structure: Dec 2020 structure, pros and cons.
- Pros & Cons: Dec 2024 M-commerce in India.
- Mobile Payment System: Jun 2025 short notes on M-commerce and payment.
- Security Issues: no past question.