DOCSLIB.ORG

MOBILE OPERATING SYSTEM 1)Introduction

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
MOBILE OPERATING SYSTEM 1)Introduction WWW.VIDYARTHIPLUS.COM MOBILE OPERATING SYSTEM 1)Introduction The Symbian OS it is the operating system developed and sold by Symbian Ltd. The OSis used primarily by Nokia with its S60 user interface and by Sony Ericsson with its UIQ user interface, but the Symbian OS is also used by a number of Japanese mobile phone manufacturers for handsets sold inside of Japan. RIM blackberry BlackBerry OS is a proprietary mobile operating system developed by BlackBerry Ltd for its BlackBerry line of smartphone handheld devices. The operating system provides multitasking and supports specialized input devices that have been adopted by WWW.VIDYARTHIPLUS.COM V+ TEAM WWW.VIDYARTHIPLUS.COM BlackBerry Ltd. for use in its handhelds, particularly the trackwheel, trackball, and most recently, the trackpad and touchscreen Android Android is a mobile operating system (OS) currently developed by Google, based on the Linux kernel and designed primarily for touchscreen mobile devices such as smartphones and tablets. Android's user interface is mainly based on direct manipulation, using touch gestures that loosely correspond to real-world actions, such as swiping, tapping and pinching, to manipulate on-screen objects, along with a virtual keyboard for text input. In addition to touchscreen devices, Google has further developed Android TV for televisions, Android Auto for cars, and Android Wear for wrist watches, each with a specialized user interface. Variants of Android are also used on notebooks, game consoles, digital cameras, and other electronics. 2)microkernel design in mobile os : microkernel assigns only a small number of essential processes to the kernel such as address space management ,inter process communication and scheduling and provides all other services in separate processes called servers. WWW.VIDYARTHIPLUS.COM V+ TEAM WWW.VIDYARTHIPLUS.COM Essential components and minimality : If the hardware provides multiple rings or CPU modes, the microkernel may be the only software executing at the most privileged level, which is generally referred to as supervisor or kernel mode. Traditional operating system functions, such as device drivers, protocol stacks and file systems, are typically removed from the microkernel itself and are instead run in user space Essential components and minimality[edit] As a microkernel must allow building arbitrary operating system services on top, it must provide some core functionality. At a minimum, this includes: some mechanisms for dealing with address spaces, required for managing memory protection some execution abstraction to manage CPU allocation, typically threads or scheduler activations inter-process communication, required to invoke servers running in their own address spaces This minimal design was pioneered by Brinch Hansen's Nucleus and the hypervisor of IBM's VM. It has since been formalised in Liedtke's minimality principle: A concept is tolerated inside the microkernel only if moving it outside the kernel, i.e., permitting competing implementations, would prevent the implementation of the system's required functionality.[11] Everything else can be done in a usermode program, although device drivers implemented as user programs may on some processor architectures require special privileges to access I/O hardware. Related to the minimality principle, and equally important for microkernel design, is the separation of mechanism and policy, it is what enables the construction of arbitrary systems on top of a minimal kernel. Any policy built into the kernel cannot be overwritten at user level and therefore limits the generality of the microkernel.[4] Policy implemented in user-level servers can be changed by replacing the servers (or letting the application choose between competing servers offering similar services). For efficiency, most microkernels contain schedulers and manage timers, in violation of the minimality principle and the principle of policy-mechanism separation. Start up (booting) of a microkernel-based system requires device drivers, which are not part of the kernel. Typically this means that they are packaged with the kernel in the boot image, and the kernel supports a bootstrap protocol that defines how the drivers are located and started; this is the traditional bootstrap procedure of L4 microkernels. Some microkernels simplify this by placing some key drivers inside the kernel (in WWW.VIDYARTHIPLUS.COM V+ TEAM WWW.VIDYARTHIPLUS.COM violation of the minimality principle), LynxOS and the original Minix are examples. Some even include a file system in the kernel to simplify booting. A microkernel-based system may boot via multiboot compatible boot loader. Such systems usually load statically- linked servers to make an initial bootstrap or mount an OS image to continue bootstrapping. A key component of a microkernel is a good IPC system and virtual-memory-manager design that allows implementing page-fault handling and swapping in usermode servers in a safe way. Since all services are performed by usermode programs, efficient means of communication between programs are essential, far more so than in monolithic kernels. The design of the IPC system makes or breaks a microkernel. To be effective, the IPC system must not only have low overhead, but also interact well with CPU scheduling. 3) Process and threads : ->Multi-asking – Symbian OS favors threads and is built around thread concept ->Thread support is based in nanorkernel with nanothreads ->Nanokernel provides nanokernel scheduling,interthread synchronization and timing services -> Nanothreads cannot run in user mode ◦->Nanothread needs minimal set of data location of its stack, how big stack is ◦ OS keeps control of everything else (e.g., code of each thread uses, stores thread’s context on tis runtime stack) ◦ Nanothread states: suspended, fast semaphore wait, DFC (Delayed Function Call) wait, sleep, other ◦ Processes are Symbian OS threads grouped together under single process control block structure with a single memory space ◦ Scheduling a process means scheduling a thread and initializing the right PCB to use for its data needs scheduling parameters, share memory space objects, including device and object descriptors process are terminated by kernel. WWW.VIDYARTHIPLUS.COM V+ TEAM WWW.VIDYARTHIPLUS.COM 4)client server resource access: are programs that OS runs to coordinate access to these resources ◦ Make connection to a file server ◦ Server acknowledges the connection ◦ Client requests ‘open’ request with the name of specific file ◦ Protects resources ◦ Is effective for managing multiple access to system resources ◦ Each server is easily upgradeable and swapped out for new designs 5)Memory Management virtual memory/swap space model mory, no disk drive ◦ RAM and flash memory ◦ RAM stores OS code ◦ Flash memory used for operating memory and permanent (file) storage ◦ Possible to add extra flash memory to device – exclusively for permanent concepts: ◦ Paging, address translations, virtual/physical address abstraction ◦ We have pages but pages cannot be swapped from memory to external storage ◦ Abstraction of memory pages is used ◦ Pages are replaced, but the page being replaced is just discarded backed on the flash memory Tasks of Memory Management 1. Management of application size ◦ Application size needs to be small and object-oriented design 2. Heap management ◦ Heap – space for dynamic memory allocation – must be managed WWW.VIDYARTHIPLUS.COM V+ TEAM WWW.VIDYARTHIPLUS.COM very tightly ◦ Heap space is bounded to force programmers to reclaim and reuse heap space 3. Execution in-place ◦ Flash memory is mapped into virtual address space and programs can be executed directly from flash memory without copying them into RAM first 4. Loading DLLs ◦ Loading all DLLs when application is first loaded into memory is more acceptable, but it is a choice. (users accept more DLL loading delays at the beginning when loading the app than during the app execution ) 5. Offload memory management to hardware ◦ If there is available MMU, use it – system performance is better -level page table strategy ◦ Kept in memory and is pointed to by TTBR (translation table base register) ◦ Points to second level of page table -to-physical memory address mapping calculation 6) file system in mobile os: Mobile file management (MFM) is a type of information technology (IT) software that allows businesses to manage transfers and storage of corporate files and other related items on a mobile device, and allows the business to oversee user access. Mobile file management software is typically installed on a corporate file server like Windows 2008, and on a mobile device such as tablet computers and smartphones, e.g., Android, iPad, iPhone, etc. Other features include the ability to remotely wipe a lost or stolen device, access, cache and store files on a mobile device and integrate with file permission solutions like those from Microsoft's Active Directory. A main advantage of modern mobile file management solutions is that they do not need a VPN connection for the mobile devices to connect to the corporate file servers. The connection between the mobile device and the WWW.VIDYARTHIPLUS.COM V+ TEAM WWW.VIDYARTHIPLUS.COM corporate file server is established via a cloud service. This way the corporate file server doesn't need to open incoming ports which would cause security issues. The files are transferred highly encrypted - e.g. according to AES 256 Bit industry standard. Only the company server and the mobile device keep the encryption key to be able to encrypt
Load more

Recommended publications
  • Validated Products List, 1995 No. 3: Programming Languages, Database
    NISTIR 5693 (Supersedes NISTIR 5629) VALIDATED PRODUCTS LIST Volume 1 1995 No. 3 Programming Languages Database Language SQL Graphics POSIX Computer Security Judy B. Kailey Product Data - IGES Editor U.S. DEPARTMENT OF COMMERCE Technology Administration National Institute of Standards and Technology Computer Systems Laboratory Software Standards Validation Group Gaithersburg, MD 20899 July 1995 QC 100 NIST .056 NO. 5693 1995 NISTIR 5693 (Supersedes NISTIR 5629) VALIDATED PRODUCTS LIST Volume 1 1995 No. 3 Programming Languages Database Language SQL Graphics POSIX Computer Security Judy B. Kailey Product Data - IGES Editor U.S. DEPARTMENT OF COMMERCE Technology Administration National Institute of Standards and Technology Computer Systems Laboratory Software Standards Validation Group Gaithersburg, MD 20899 July 1995 (Supersedes April 1995 issue) U.S. DEPARTMENT OF COMMERCE Ronald H. Brown, Secretary TECHNOLOGY ADMINISTRATION Mary L. Good, Under Secretary for Technology NATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY Arati Prabhakar, Director FOREWORD The Validated Products List (VPL) identifies information technology products that have been tested for conformance to Federal Information Processing Standards (FIPS) in accordance with Computer Systems Laboratory (CSL) conformance testing procedures, and have a current validation certificate or registered test report. The VPL also contains information about the organizations, test methods and procedures that support the validation programs for the FIPS identified in this document. The VPL includes computer language processors for programming languages COBOL, Fortran, Ada, Pascal, C, M[UMPS], and database language SQL; computer graphic implementations for GKS, COM, PHIGS, and Raster Graphics; operating system implementations for POSIX; Open Systems Interconnection implementations; and computer security implementations for DES, MAC and Key Management.
    [Show full text]
  • Interrupts and Exceptions CPU Modes and Address Spaces Dual-Mode Of
    CPU Modes and Address Spaces There are two processor (CPU) modes of operation: • Kernel (Supervisor) Mode and • User Mode The processor is in Kernel Mode when CPU mode bit in Status Interrupts and Exceptions register is set to zero. The processor enters Kernel Mode at power-up, or as result of an interrupt, exception, or error. The processor leaves Kernel Mode and enters User Mode when the CPU mode bit is set to one (by some instruction). Memory address space is divided in two ranges (simplified): • User address space – addresses in the range [0 – 7FFFFFFF16] Studying Assignment: A.7 • Kernel address space Reading Assignment: 3.1-3.2, A.10 – addresses in the range [8000000016 – FFFFFFFF16] g. babic Presentation B 28 g. babic 29 Dual-Mode of CPU Operation MIPS Privilege Instructions • CPU mode bit indicates the current CPU mode: 0 (=kernel) With CPU in User Mode, the program in execution has access or 1 (=user). only to the CPU and FPU registers, while when CPU operates • When an interrupt occurs, CPU hardware switches to the in Kernel Mode, the program has access to the full capabilities kernel mode. of processor including CP0 registers. • Switching to user mode (from kernel mode) done by setting CPU mode bit (by an instruction). Privileged instructions can not be executed when the Exception/Interrupt processor is in User mode, they can be executed only when the processor is in Kernel mode. kernel user Examples of MIPS privileged instructions: Set user mode • any instruction that accesses Kernel address space • all instructions that access any of CP0 registers, e.g.
    [Show full text]
  • RTI Data Distribution Service Platform Notes
    RTI Data Distribution Service The Real-Time Publish-Subscribe Middleware Platform Notes Version 4.5c © 2004-2010 Real-Time Innovations, Inc. All rights reserved. Printed in U.S.A. First printing. June 2010. Trademarks Real-Time Innovations and RTI are registered trademarks of Real-Time Innovations, Inc. All other trademarks used in this document are the property of their respective owners. Copy and Use Restrictions No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form (including electronic, mechanical, photocopy, and facsimile) without the prior written permission of Real- Time Innovations, Inc. The software described in this document is furnished under and subject to the RTI software license agreement. The software may be used or copied only under the terms of the license agreement. Technical Support Real-Time Innovations, Inc. 385 Moffett Park Drive Sunnyvale, CA 94089 Phone: (408) 990-7444 Email: [email protected] Website: http://www.rti.com/support Contents 1 Supported Platforms.........................................................................................................................1 2 AIX Platforms.....................................................................................................................................3 2.1 Changing Thread Priority.......................................................................................................3 2.2 Multicast Support ....................................................................................................................3
    [Show full text]
  • Research Purpose Operating Systems – a Wide Survey
    GESJ: Computer Science and Telecommunications 2010|No.3(26) ISSN 1512-1232 RESEARCH PURPOSE OPERATING SYSTEMS – A WIDE SURVEY Pinaki Chakraborty School of Computer and Systems Sciences, Jawaharlal Nehru University, New Delhi – 110067, India. E-mail: [email protected] Abstract Operating systems constitute a class of vital software. A plethora of operating systems, of different types and developed by different manufacturers over the years, are available now. This paper concentrates on research purpose operating systems because many of them have high technological significance and they have been vividly documented in the research literature. Thirty-four academic and research purpose operating systems have been briefly reviewed in this paper. It was observed that the microkernel based architecture is being used widely to design research purpose operating systems. It was also noticed that object oriented operating systems are emerging as a promising option. Hence, the paper concludes by suggesting a study of the scope of microkernel based object oriented operating systems. Keywords: Operating system, research purpose operating system, object oriented operating system, microkernel 1. Introduction An operating system is a software that manages all the resources of a computer, both hardware and software, and provides an environment in which a user can execute programs in a convenient and efficient manner [1]. However, the principles and concepts used in the operating systems were not standardized in a day. In fact, operating systems have been evolving through the years [2]. There were no operating systems in the early computers. In those systems, every program required full hardware specification to execute correctly and perform each trivial task, and its own drivers for peripheral devices like card readers and line printers.
    [Show full text]
  • Vxworks OS Changer Gives Developers the Ability to Reuse Vxworks Applications on Diff Erent Operating Systems
    VxWorks® OS Changer Change Your OS - Keep Your Code The OS Changer family of products gives developers the freedom to switch operating systems while leveraging on their existing code and knowledge base to protect their software investment. VxWorks OS Changer gives developers the ability to reuse VxWorks applications on diff erent operating systems. VxWorks OS Changer Highlights Protect your software investment by re-using your VxWorks code Reduce time to market by migrating VxWorks code to a standard OS interface architecture Protect your knowledge-base by using familiar APIs and eliminate the learning curve on the new OS platform Eliminate dependency on a single OS vendor and switch to - An OS that meets your performance and memory footprint needs - An OS that off ers better tools, middleware/drivers and support - An OS that supports your next generation silicon Reduce ongoing development and maintenance cost - Develop target specifi c code on a host platform - Re-use one set of code across multiple host & target OS platforms - Break down VxWorks applications into manageable pieces to reduce complexity and add module protection - Use same APIs for inter-task and inter-process communications OS Changer is highly optimized for each specifi c OS platform Eclipse-based host environment is available to port VxWorks applications using OS Changer in OS PAL (refer to the OS PAL datasheet) OS Changer includes access to the BASE OS Abstractor API features to allow development of highly portable applications (refer to the OS Abstractor datasheet) Additionally, POSIX or open source Linux code can be reused on a new OS platform with POSIX OS Abstractor (refer to the POSIX OS Abstractor datasheet) VxWorks OS Changer is off ered royalty-free with source code Using VxWorks OS Changer OS Changer is designed for use as a C library.
    [Show full text]
  • 5 Things You Need to Know About Ipad® in the Enterprise
    WHITE PAPER 5 Things You Need to Know About iPad® in the Enterprise Introduction Without a doubt, iPads® are one of the fastest adopted computing platforms in history. And, not just for consumers desiring to play Angry Birds. These tablets, with an entirely new browsing and usability paradigm, are rapidly making inroads into the enterprise, being used, according to Apple®, by nearly all of the Fortune 500.1 Aside from direct acquisition of the devices by the enterprises themselves, end-users are bringing them to work and using them in a variety of ways, intent on increasing productivity and making their work lives—and their personal lives—more efficient through easily accessible information away from a computer. While iPad presents the potential to bring a wealth of measurable and profitable benefits to the enterprise as well as happier, and, hence, more productive employees, it also brings a number of challenges and risks that threaten to lead to security breaches and compliance violations, regardless of industry. In this white paper, we’ll the discuss the top 5 Things you NEED to know about iPads and integrating them into an enterprise environment so you can protect and maximize existing IT and corporate assets, mitigate security and compliance risks, and keep IT in control, all while ensuring employees are happy and at their most productive. WHITE PAPER WHITE PAPER 1 - iPads are Already in the Enterprise (like it or not) With or without IT’s blessing, iPad users are using their devices for work purposes (95% of employees say they use personally purchased devices for work use).2 That means without a native file system on the device and enterprise security and management capability, users are employing the “work around,” putting the enterprise and its assets at risk and compromising compliance efforts.
    [Show full text]
  • RTA-OSEK Binding Manual: TMS470/TI
    RTA-OSEK Binding Manual: TMS470/TI Contact Details ETAS Group www.etasgroup.com Germany USA ETAS GmbH ETAS Inc. Borsigstraße 14 3021 Miller Road 70469 Stuttgart Ann Arbor, MI 48103 Tel.:+49 (711) 8 96 61-102 Tel.: +1 (888) ETAS INC Fax:+49 (711) 8 96 61-106 Fax: +1 (734) 997-94 49 www.etas.de www.etasinc.com Japan France ETAS K.K. ETAS S.A.S. Queen's Tower C-17F, 1, place des États-Unis 2-3-5, Minatomirai, Nishi-ku, SILIC 307 Yokohama, Kanagawa 94588 Rungis Cedex 220-6217 Japan Tel.: +33 (1) 56 70 00 50 Tel.: +81 (45) 222-0900 Fax: +33 (1) 56 70 00 51 Fax: +81 (45) 222-0956 www.etas.fr www.etas.co.jp Korea Great Britain ETAS Korea Co. Ltd. ETAS UK Ltd. 4F, 705 Bldg. 70-5 Studio 3, Waterside Court Yangjae-dong, Seocho-gu Third Avenue, Centrum 100 Seoul 137-889, Korea Burton-upon-Trent Tel.: +82 (2) 57 47-016 Staffordshire DE14 2WQ Fax: +82 (2) 57 47-120 Tel.: +44 (0) 1283 - 54 65 12 www.etas.co.kr Fax: +44 (0) 1283 - 54 87 67 www.etas-uk.net Copyright Notice © 2001 - 2007 LiveDevices Ltd. All rights reserved. Version: M00088-001 No part of this document may be reproduced without the prior written consent of LiveDevices Ltd. The software described in this document is furnished under a license and may only be used or copied in accordance with the terms of such a license. Disclaimer The information in this document is subject to change without notice and does not represent a commitment on any part of LiveDevices.
    [Show full text]
  • Bringing Virtualization to the X86 Architecture with the Original Vmware Workstation
    12 Bringing Virtualization to the x86 Architecture with the Original VMware Workstation EDOUARD BUGNION, Stanford University SCOTT DEVINE, VMware Inc. MENDEL ROSENBLUM, Stanford University JEREMY SUGERMAN, Talaria Technologies, Inc. EDWARD Y. WANG, Cumulus Networks, Inc. This article describes the historical context, technical challenges, and main implementation techniques used by VMware Workstation to bring virtualization to the x86 architecture in 1999. Although virtual machine monitors (VMMs) had been around for decades, they were traditionally designed as part of monolithic, single-vendor architectures with explicit support for virtualization. In contrast, the x86 architecture lacked virtualization support, and the industry around it had disaggregated into an ecosystem, with different ven- dors controlling the computers, CPUs, peripherals, operating systems, and applications, none of them asking for virtualization. We chose to build our solution independently of these vendors. As a result, VMware Workstation had to deal with new challenges associated with (i) the lack of virtual- ization support in the x86 architecture, (ii) the daunting complexity of the architecture itself, (iii) the need to support a broad combination of peripherals, and (iv) the need to offer a simple user experience within existing environments. These new challenges led us to a novel combination of well-known virtualization techniques, techniques from other domains, and new techniques. VMware Workstation combined a hosted architecture with a VMM. The hosted architecture enabled a simple user experience and offered broad hardware compatibility. Rather than exposing I/O diversity to the virtual machines, VMware Workstation also relied on software emulation of I/O devices. The VMM combined a trap-and-emulate direct execution engine with a system-level dynamic binary translator to ef- ficiently virtualize the x86 architecture and support most commodity operating systems.
    [Show full text]
  • Altaapi Software User's Manual
    AltaAPI™ Software User’s Manual Part Number: 14301-00000-I4 Cage Code: 4RK27 ● NAICS: 334118 Alta Data Technologies LLC 4901 Rockaway Blvd, Building A Rio Rancho, NM 87124 USA (tel) 505-994-3111 ● www.altadt.com i AltaAPI™ Software User’s Manual ● 14301-00000-I4 Alta Data Technologies LLC ● www.altadt.com CUSTOMER NOTES: Document Information: Alta Software Version: 2.6.5.0 Rev I4 Release Date: November 10, 2014 Note to the Reader and End-User: This document is provided for information only and is copyright by © Alta Data Technologies LLC. While Alta strives to provide the most accurate information, there may be errors and omissions in this document. Alta disclaims all liability in document errors and any product usage. By using an Alta product, the customer or end user agrees (1) to accept Alta’s Standard Terms and Conditions of Sale, Standard Warranty and Software License and (2) to not hold Alta Members, Employees, Contractors or Sales & Support Representatives responsible for any loss or legal liability, tangible or intangible, from any document errors or any product usage. The product described in this document is not US ITAR controlled. Use of Alta products or documentation in violation of local usage, waste discard and export control rules, or in violation of US ITAR regulations, voids product warranty and shall not be supported. This document may be distributed to support government programs and projects. Third party person, company or consultant distribution is not allowed without Alta’s written permission. AltaCore, AltaCore-1553, AltaCore-ARINC, AltaAPI, AltaAPI-LV, AltaView, AltaRTVal, ENET- 1553, ENET-A429 & ENET-1553-EBR are Trademarks of Alta Data Technologies LLC, Rio Rancho, New Mexico USA Contact: We welcome comments and suggestions.
    [Show full text]
  • Introduction to Bioinformatics Introduction to Bioinformatics
    Introduction to Bioinformatics Introduction to Bioinformatics Prof. Dr. Nizamettin AYDIN [email protected] Introduction to Perl http://www3.yildiz.edu.tr/~naydin 1 2 Learning objectives Setting The Technological Scene • After this lecture you should be able to • One of the objectives of this course is.. – to enable students to acquire an understanding of, and understand : ability in, a programming language (Perl, Python) as the – sequence, iteration and selection; main enabler in the development of computer programs in the area of Bioinformatics. – basic building blocks of programming; – three C’s: constants, comments and conditions; • Modern computers are organised around two main – use of variable containers; components: – use of some Perl operators and its pattern-matching technology; – Hardware – Perl input/output – Software – … 3 4 Introduction to the Computing Introduction to the Computing • Computer: electronic genius? • In theory, computer can compute anything – NO! Electronic idiot! • that’s possible to compute – Does exactly what we tell it to, nothing more. – given enough memory and time • All computers, given enough time and memory, • In practice, solving problems involves are capable of computing exactly the same things. computing under constraints. Supercomputer – time Workstation • weather forecast, next frame of animation, ... PDA – cost • cell phone, automotive engine controller, ... = = – power • cell phone, handheld video game, ... 5 6 Copyright 2000 N. AYDIN. All rights reserved. 1 Layers of Technology Layers of Technology • Operating system... – Interacts directly with the hardware – Responsible for ensuring efficient use of hardware resources • Tools... – Softwares that take adavantage of what the operating system has to offer. – Programming languages, databases, editors, interface builders... • Applications... – Most useful category of software – Web browsers, email clients, web servers, word processors, etc..
    [Show full text]
  • Programming Fundamentals - I Basic Concepts Fall-Semester 2016
    Programming Fundamentals - I Basic Concepts Fall-Semester 2016 Prepared By: Rao Muhammad Umer Lecturer, Web: raoumer.github.io Department of Computer Science & IT, The University of Lahore. What is computer? The term "computer" was originally given to humans who performed numerical calculations using mechanical calculators, such as the abacus and slide rule. The term was later given to a mechanical device as they began replacing the human computers. Today's computers are electronic devices that accept data such as numbers, text, sound, image, animations, video, etc., (input), process that data (converts data to information) , produce output, and then store (storage) the results. A basic computer consists of 4 components: 1. Input devices 2. Central Processing Unit or CPU 3. Output devices 4. Memory Input Devices are used to provide input to the computer basic input devices include keyboard, mouse, touch screens etc. Central Processing Unit acts like a brain, it processes all instructions and data in the computer, the instructions are computer commands, these commands are given to CPU by input devices, some of the instructions are generated by the computer itself Output devices are used to receive computer output, the output, some basic output devices are hard drive disk (HDD, commonly known as hard disk), printers, computer screens (Monitors and LCDs) The computer memory is a temporary storage area. It holds the data and instructions that the Central Processing Unit (CPU) needs. Before a program can be run, the program is loaded from some storage device such as into the memory, the CPU loads the program or part of the program from the memory and executes it.
    [Show full text]
  • Mobile Security Top Five Security Threats for the Mobile Enterprise
    WHITE PAPER Mobile Security Top Five Security Threats for the Mobile Enterprise and How to Address Them WHITE PAPER WHITE PAPER Today’s countless mobile devices present tangible opportunities to drive measurable and substantial value for the enterprise. Field service workers, executives on the go, sales reps, project managers and others all have a need for mobile access to applications and enterprise files. It’s no question that the advent of the iPad® and other mobile computing devices brings substantial benefits to the enterprise. However, these benefits also come with new security risks that enterprise IT departments must be ever vigilant about, lest critical data be compromised. The consumerization of IT and BYOD (bring your own device) programs in the workplace make mobile file management (MFM) solutions more important than ever before.1 In this white paper, we’ll cover the latest security threats to the mobile enterprise, as well as solutions to overcome them. Solutions that allow enterprises to make the most of the benefits iPads and other mobile devices bring to the company while safeguarding security, and help to foster happy employees, increased productivity, and streamlined, managed workflows are increasingly critical in today’s enterprise IT landscape. Security threats include: 1. Unsecure File Transfer 2. Lost/Stolen Devices 3. Open Wi-Fi Networks and Public Hotspots 4. Malware and Viruses 5. Unclear Corporate Policies WHITE PAPER WHITE PAPER Unsecure File Transfer Problem: iPads and other tablets make mobile file management a bigger issue than ever before due to the lack of native file storage on the devices. Employees typically opt for consumer-driven workarounds and synching solutions, which, according to recent filings with the FTC, do not live up to their guarantees of secure, encrypted file transfer and storage.2 Solution: Mobile file management provides simple, secure and managed access to enterprise files on mobile devices.
    [Show full text]