DOCSLIB.ORG

NGX R65 Release Notes

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
NGX R65 Release Notes Check Point NGX R65 Release Notes Revised: February 2, 2009 This Release Notes document provides essential operating requirements and describes known issues for VPN-1/FireWall-1 NGX R65. Review this information before setting up VPN-1/FireWall-1 NGX R65. Note - Before you begin installation, read the latest available version of these release notes at: http://www.checkpoint.com/support/ In This Document Information About This Release page 2 Resolved Limitations page 18 Clarifications and Limitations page 22 Documentation Feedback page 42 Copyright © February 2, 2009 Check Point Software Technologies, Ltd. All rights reserved 1 Information About This Release Information About This Release This document contains important information not included in the documentation. Review this information before setting up Check Point NGX R65. In This Section Build Numbers page 3 NGX Products, Supported by Platform page 4 NGX Clients, Supported by Platform page 5 Non-upgradable Products page 5 HFAs Included in this Release page 5 Minimum Hardware Requirements page 6 Maximum Number of Interfaces Supported by Platform page 14 Minimum Software Requirements page 15 The Regular Expression (RX) Library page 17 VPN-1/FireWall-1 NGX R65 Release Notes. Last Update — February 2, 2009 2 Build Numbers Build Numbers The following table lists all NGX R65 software products available, and the build numbers as they are distributed on the product CD. To verify each product’s build number, use the given command format or direction within the GUI. Product Build No.CLI Command / GUI Selection VPN-1 Power / UTM SecurePlatform fw ver /Linux 430 Sun 428 Windows 427 IPSO 436 SmartCenter Server 083 fwm ver Provider-1/SiteManager-1 620000292 CPvinfo $MDSDIR/lib/libmds.so | grep “Build Multi-Domain Server (MDS) Number” Endpoint Security Server 7.20.084.000 System configuration > Version information Endpoint Security Client 7.00.843.000 Right-click the System Tray icon and select About Eventia Reporter Server 239 SVRServer ver Eventia Analyzer Server 058 cpsemd ver SmartView Monitor Server 013 rtm ver UserAuthority Server 010 uas ver SecureClient Policy Server 008 dtps ver SVN Foundation 432 cpshared_ver IPSO 435 UTM-1 Edge 7.0.27x Displayed on the default portal page QoS 020 fgate ver SmartConsole Applications 620000380 Help > About Check Point <product name> (includes SmartDashboard, SmartView Tracker, SmartView Monitor, SmartLSM, Eventia Reporter Client, Eventia Analyzer Client, SecureClient Packaging Tool, SmartLSM, SmartUpdate) Solaris SmartConsole R65_motif Help > About Check Point <product name> B620000017_1 Provider-1/SiteManager-1 620000280 Help > About Check Point Provider-1/SiteManager-1 Multi-Domain GUI (MDG) SmartPortal 620000098 cpvinfo /opt/CPportal-R65/portal/bin/ smartportalstart Compatibility Packages: •NG 40 /opt/CPngcmp-R65/bin/fw_loader ver • R55W 17 /opt/CPR55WCmp-R65/bin/fw_loader ver •VSX NGX 508 /opt/CPvsxngxcmp-R65/bin/fw_loader ver • UTM-1 Edge 620000020 /opt/CPEdgecmp-R65/bin/fw ver SecuRemote/SecureClient 019 Help > About SecurePlatform 004 ver Performance Pack 030 sim ver -k VPN-1/FireWall-1 NGX R65 Release Notes. Last Update — February 2, 2009 3 NGX Products, Supported by Platform NGX Products, Supported by Platform Check Point Product Platform and Operating System RHEL Check Solaris Microsoft Windows 3.0 Point Nokia Ultra- Server 2000 2000 2000 XP Home kernel Secure IPSO SPARC 2003 Advanced Server Profes- & Profes- 2.4.21 Platform 4.1 - 8, 9 & (SP1-2) Server (SP1-4) sional sional 4.2 10 (SP1-4) (SP1-4) VPN-1 Power / UTM X XXX X X 1 X 2 SmartCenter Server X XXX XX X 3 Provider-1/SiteManager-1 X X 4 X .Server (MDS) VPN-1 Power VSX 5 X Endpoint Security Server X X X X X Eventia Suite 6 X XXX XX UserAuthority Server X XXXXXXX X 7 SSL Network Extender Server X XXX XXX SmartConsole Applications X 8 XXXXX Provider-1/SiteManager-1 MDG X XXXXX SmartPortal X XXX XX SmartLSM - Enabled .Management & Enabled X 9 XXX XXX .ROBO / CO Gateways ClusterXL X X 10 XX XX X 11 VPN-1 Accelerator Driver II X 12 VPN-1 Accelerator Driver III X XXX XX VPN-1 Accelerator Driver IV X X X Advanced Routing X X 13 Performance Pack XX X 14 SecureXL Turbocard X 15 OSE Supported Routers Nortel Versions: 7.x, 8.x, 9.x, 10.x, 11.x, 12.x, 13, 14 Cisco OS Versions: 9.x, 10.x, 11.x, 12.x Notes to Products by Platform Table 1. Anti Virus and Web Filtering are included on SecurePlatform. 2. Anti Virus and Web Filtering are supported on Nokia disk-based platforms running IPSO 4.2 Build 42 HF002 or later. 3. UTM-1 Edge devices cannot be managed from a SmartCenter server running on a Nokia IPSO platform. 4. Provider-1/SiteManager-1 supported on both RHEL 3.0 AS and ES. 5. VPN-1 Power VSX gateways are also supported on Crossbeam Systems X-Series Security Services Switches. 6. Eventia Suite includes Eventia Reporter Server, Eventia Analyzer Server, and the Eventia Analyzer Correlation Unit. 7. UserAuthority is not supported on Nokia flash-based platforms. 8. The following SmartConsole clients are not supported on Solaris UltraSPARC platforms: SmartView Monitor, SmartLSM, Eventia Reporter Client, Eventia Analyzer Client, and the SecureClient Packaging Tool. 9. Enabled ROBO Gateways are not supported on Solaris platforms. VPN-1/FireWall-1 NGX R65 Release Notes. Last Update — February 2, 2009 4 NGX Clients, Supported by Platform 10. HA Legacy mode is not supported on Windows Server 2003. 11. ClusterXL is supported only in third party mode with VRRP or IP Clustering. 12. VPN-1 Power Accelerator Driver II is supported on Solaris 8 only. 13. Nokia provides Advanced Routing as part of IPSO. 14. Nokia provides SecureXL as part of IPSO. 15. NGX-compatible Turbocard driver is available at http://www.checkpoint.com/downloads/quicklinks/downloads_tc.html. NGX Clients, Supported by Platform Check Point Product Operating System Windows Mac Linux Server 2000 Server 2000 Profes- Mobile OS 2003 / Advanced sional (SP1-4) 2003 "X" (SP1) Server / XP Home & 2003SE (SP1-4) Professional 5.0 SecuRemote X X X SecureClient X X X X SecureClient Mobile X SSL Network Extender X XX Endpoint Security Clients X X Non-upgradable Products The following Check Point products cannot be upgraded to NGX R65: • VPN-1 Power SmallOffice, VPN-1 Net • FireWall-1 4.1 HFAs Included in this Release This release includes fixes and improvements that were initially distributed as part of NGX R60 Hotfix Accumulator (HFA) R60_HFA_05. VPN-1/FireWall-1 NGX R65 Release Notes. Last Update — February 2, 2009 5 Minimum Hardware Requirements Minimum Hardware Requirements In This Section VPN-1 Power/UTM page 7 Provider-1/SiteManager-1 MDS page 7 Provider-1/SiteManager-1 MDG page 7 VPN-1 Power VSX page 8 Eventia Reporter page 8 Endpoint Security Server page 9 Endpoint Security Clients page 11 SmartConsole page 11 Check Point Clients page 11 SecurePlatform Supported Hardware page 12 Supported Nokia Platforms page 12 Supported SecureClient Mobile Hardware page 13 VPN-1/FireWall-1 NGX R65 Release Notes. Last Update — February 2, 2009 6 Minimum Hardware Requirements VPN-1 Power/UTM The following section shows the minimum hardware requirements for installing a VPN-1 gateway and SmartCenter Server: VPN-1 Gateway Windows & Linux Solaris SecurePlatform Processor Intel Pentium II UltraSparc III Intel Pentium III CPU 300MHz or equivalent 300MHz or equivalent processor processor Free Disk Space 300MB Installation - 100 MB 10GB Memory Windows: 256MB 128MB 256MB (512MB Linux: 256MB (512MB recommended) recommended) CD-ROM Drive Yes Yes Yes (bootable) Network Adapter One or more Yes One or more supported network adapter cards Video Adapter supports 800 x 600 supports 1024 x 768 resolution resolution SmartCenter Server Windows & Linux Solaris SecurePlatform Processor Intel Pentium III UltraSparc III Intel Pentium III CPU 800MHz or equivalent 800MHz or equivalent processor processor Free Disk Space Windows: 300MB 400MB 10GB (installation includes Linux: 512MB OS) Memory 512MB 512MB 512MB CD-ROM Drive Yes Yes Yes (bootable) Network Adapter One or more Yes One or more supported network adapter cards Provider-1/SiteManager-1 MDS The following table shows the minimum hardware requirements for installing a Provider-1/SiteManager-1 Multi Domain Server (MDS). Linux Solaris SecurePlatform CPU Intel Pentium III 1GHz or UltraSPARC III 900MHz Intel Pentium III 1GHz or equivalent processor equivalent processor Memory 1GB 1GB 1GB Disk Space 2GB 2GB 10GB (install includes OS) CD-ROM Drive Yes Yes Yes (bootable) Provider-1/SiteManager-1 MDG The following table shows the minimum hardware requirements for installing the Provider-1/SiteManager-1 Multi Domain GUI (MDG). Windows Solaris CPU Intel Pentium III 1GHz or equivalent processor UltraSparc III 900MHz Memory 512MB 512MB Disk Space 100MB 100 MB CD-ROM Drive Yes Yes Video Adapter supports at least 800 x 600 resolution supports at least 800 x 600 resolution VPN-1/FireWall-1 NGX R65 Release Notes. Last Update — February 2, 2009 7 Minimum Hardware Requirements VPN-1 Power VSX The following table shows the minimum hardware requirements for installing a VPN-1 Power VSX gateway. SecurePlatform CPU Intel Pentium III 450MHz or equivalent processor Memory 512MB Disk Space 9GB (install includes OS) CD-ROM Drive Yes (bootable) VPN-1 Power VSX gateways are also supported on Crossbeam Systems X-Series Security Services Switches. Eventia Reporter The hardware requirements presented below are designed for an Eventia Reporter server that will process at least 15GB of logs per day and generate reports according to the performance numbers. For deployments that will generate fewer logs per day, a machine with less CPU or memory can be used, with the caveat that this may cause degradation in the performance numbers. Windows & Linux Windows & Linux Recommended Solaris Minimum CPU Intel Pentium IV 2.0 GHz Dual CPU 3.0 GHz UltraSPARC III 900 MHz Memory 1GB 2GB 1GB Disk Space (on 2 physical disks) Installation: 80MB 80MB 80MB Database: 60GB (40GB for database, 100GB (60GB for database, 60GB (40GB for database, 20GB temp directory) 40GB for temp directory) 20GB for temp directory) CD-ROM Drive Yes Yes Yes Recommendations to Optimize Performance • Disable DNS resolution - consolidation performance may improve to 32GB of logs/day.
Load more

Recommended publications
  • Understanding Human-Battery Interaction on Mobile Phones
    Understanding Human-Battery Interaction on Mobile Phones Ahmad Rahmati, Angela Qian, and Lin Zhong Department of Electrical & Computer Engineering Rice University, Houston, TX 77005 {rahmati, qangela, lzhong}@rice.edu ABSTRACT human users deal with limited battery lifetime, which we call Mobile phone users have to deal with limited battery lifetime human-battery interaction (HBI). Human-battery interaction is a through a reciprocal process we call human-battery interaction reciprocal process. On one hand, modern mobile phones provide (HBI). We conducted three user studies in order to understand users with indicators of the battery charge level, as well as user HBI and discover the problems in existing mobile phone designs. interfaces for changing power-saving settings, such as display The studies include a large-scale international survey, a one- brightness reduction. We refer to these indicators and user month field data collection including quantitative battery logging interfaces collectively as the battery interface. On the other hand, and qualitative inquiries from ten mobile phone users, and human users can react to the dropping battery charge level by structured interviews with twenty additional mobile phone users. changing the power-saving settings, altering usage patterns, and We evaluated various aspects of HBI, including charging charging the phone. behavior, battery indicators, user interfaces for power-saving Understanding HBI will provide valuable insight into the settings, user knowledge, and user reaction. We find that mobile effectiveness of the battery interface, and how mobile users deal phone users can be categorized into two types regarding HBI and with limited battery lifetime, prioritize and make tradeoffs. often have inadequate knowledge regarding phone power Knowledge regarding HBI will essentially help design better characteristics.
    [Show full text]
  • Transaction / Regular Paper Title
    IEEE TRANSACTIONS ON MOBILE COMPUTING, MANUSCRIPT ID 1 Context-Based Network Estimation for Energy-Efficient Ubiquitous Wireless Connectivity Ahmad Rahmati, Student Member, and Lin Zhong, Member, IEEE Abstract— Context information brings new opportunities for efficient and effective system resource management of mobile devices. In this work, we focus on the use of context information to achieve energy-efficient, ubiquitous wireless connectivity. Our field-collected data show that the energy cost of network interfaces poses a great challenge to ubiquitous connectivity, despite decent availability of cellular networks. We propose to leverage the complementary strengths of Wi-Fi and cellular interfaces by automatically selecting the more efficient one based on context information. We formulate the selection of wireless interfaces as a statistical decision problem. The challenge is to accurately estimate Wi-Fi network conditions without powering up its network interface. We explore the use of different context information, including time, history, cellular network conditions, and device motion, to statistically estimate Wi-Fi network conditions with negligible overhead. We evaluate several context- based algorithms for the estimation and prediction of current and future network conditions. Simulations using field-collected traces show that our network estimation algorithms can improve the average battery lifetime of a commercial mobile phone for an ECG reporting application by 40%, very close to the estimated theoretical upper bound of 42%. Further, our most effective algorithm can predict Wi-Fi availability for one and ten hours into the future with 95% and 90% accuracy, respectively. Index Terms— Network Architecture and Design, Local and Wide-Area Networks. —————————— —————————— 1 INTRODUCTION merging mobile applications in healthcare and mul- energy per MB transfer.
    [Show full text]
  • HTC SPV MDA G1 Zdalny Unlock Kodem Po IMEI - Również DESIRE
    GSM-Support ul. Bitschana 2/38, 31-420 Kraków mobile +48 608107455, NIP PL9451852164 REGON: 120203925 www.gsm-support.net HTC SPV MDA G1 zdalny unlock kodem po IMEI - również DESIRE Jest to usługa pozwalająca na zdjęcie simlocka z telefonów HTC / SPV / QTEK / MDA / G1-Google / Xperia poprzez kod - łącznie z najnowszą bazą! Kod podawany jest na podstawie numeru IMEI, modelu oraz sieci, w której jest simlock. Numer IMEI można sprawdzić w telefonie poprzez wybranie na klawiaturze *#06#. Do każdego numeru IMEI przyporządkowany jest jeden kod. W polu na komentarz prosimy podać model, IMEI oraz kraj i nazwę sieci, w której jest załozony simlock. Czas oczekiwania na kod to średnio 2h. Nie zdejmujemy simlocków kodem z HTC Touch HD z sieci Play, HTC Touch Pro z Orange Polska i innych, które wyraźnie są wymienione na samym dole opisu! Usługa obejmuje modele: DOPOD 310 (HTC Oxygen) DOPOD 535 (HTC Voyager) DOPOD 565 (HTC Typhoon) DOPOD 566 (HTC Hurricane) DOPOD 575 (HTC Feeler) DOPOD 577W (HTC Tornado) DOPOD 585 (HTC Amadeus) DOPOD 586 (HTC Hurricane) DOPOD 586W (HTC Tornado) DOPOD 595 (HTC Breeze) DOPOD 686 (HTC Wallaby) DOPOD 696 (HTC Himalaya) DOPOD 696i (HTC Himalaya) DOPOD 699 (HTC Alpine) DOPOD 700 (HTC Blueangel) DOPOD 710 (HTC Startrek) DOPOD 710+ (HTC Startrek) DOPOD 818 (HTC Magician) DOPOD 818 Pro (HTC Prophet) DOPOD 818C (HTC Wave) DOPOD 828 (HTC Magician) DOPOD 828+ (HTC Magician) DOPOD 830 (HTC Prophet) DOPOD 838 (HTC Wizard) DOPOD 838 Pro (HTC Hermes) DOPOD 900 (HTC Universal) DOPOD C500 (HTC Vox) DOPOD C720 (HTC Excalibur) DOPOD C720W
    [Show full text]
  • Context-Sensitive Energy-Efficient Wireless Data Transfer
    Context-for-Wireless: Context-Sensitive Energy-Efficient Wireless Data Transfer Ahmad Rahmati and Lin Zhong Department of Electrical & Computer Engineering Rice University, Houston, TX 77005 {rahmati, lzhong}@rice.edu ABSTRACT Keywords Ubiquitous connectivity on mobile devices will enable numerous Energy-efficient wireless, multiple wireless interfaces, context- new applications in healthcare and multimedia. We set out to for-wireless check how close we are towards ubiquitous connectivity in our daily life. The findings from our recent field-collected data from 1. INTRODUCTION an urban university population show that while network Emerging mobile applications in healthcare and multimedia availability is decent, the energy cost of network interfaces poses demand ubiquitously available wireless network connectivity. a great challenge. Based on our findings, we propose to leverage Despite of the wide deployment of 2.5G & 3G cellular networks the complementary strength of Wi-Fi and cellular networks by and an increasing number of Wi-Fi hot-spots, it is still an open choosing wireless interfaces for data transfers based on network question how close we are towards achieving ubiquitous condition estimation. We show that an ideal selection policy can connectivity in our everyday life. In this work, we present our more than double the battery lifetime of a commercial mobile findings from our recent field collected data about wireless phone, and the improvement varies with data transfer patterns and network availability and energy cost, and investigate context- Wi-Fi availability. based Wi-Fi estimation for energy-efficient wireless data transfer. We formulate the selection of wireless interfaces as a As a reality check and case study, we gathered field data statistical decision problem.
    [Show full text]
  • Context-Sensitive Energy-Efficient Wireless Data Transfer
    Context-for-Wireless: Context-Sensitive Energy-Efficient Wireless Data Transfer Ahmad Rahmati and Lin Zhong Department of Electrical & Computer Engineering Rice University, Houston, TX 77005 {rahmati, lzhong}@rice.edu ABSTRACT Keywords Ubiquitous connectivity on mobile devices will enable numerous Energy-efficient wireless, multiple wireless interfaces, context- new applications in healthcare and multimedia. We set out to for-wireless check how close we are towards ubiquitous connectivity in our daily life. The findings from our recent field-collected data from 1. INTRODUCTION an urban university population show that while network Emerging mobile applications in healthcare and multimedia availability is decent, the energy cost of network interfaces poses demand ubiquitously available wireless network connectivity. a great challenge. Based on our findings, we propose to leverage Despite of the wide deployment of 2.5G & 3G cellular networks the complementary strength of Wi-Fi and cellular networks by and an increasing number of Wi-Fi hot-spots, it is still an open choosing wireless interfaces for data transfers based on network question how close we are towards achieving ubiquitous condition estimation. We show that an ideal selection policy can connectivity in our everyday life. In this work, we present our more than double the battery lifetime of a commercial mobile findings from our recent field collected data about wireless phone, and the improvement varies with data transfer patterns and network availability and energy cost, and investigate context- Wi-Fi availability. based Wi-Fi estimation for energy-efficient wireless data transfer. We formulate the selection of wireless interfaces as a As a reality check and case study, we gathered field data statistical decision problem.
    [Show full text]
  • Building Aggressively Duty-Cycled Platforms to Achieve Energy Efficiency
    UNIVERSITY OF CALIFORNIA, SAN DIEGO Building Aggressively Duty-Cycled Platforms to Achieve Energy Efficiency A dissertation submitted in partial satisfaction of the requirements for the degree Doctor of Philosophy in Computer Science (Computer Engineering) by Yuvraj Agarwal Committee in charge: Rajesh Gupta, Chair Paramvir Bahl William Hodgkiss Stefan Savage Alex Snoeren Geoff Voelker 2009 Copyright Yuvraj Agarwal, 2009 All rights reserved. The dissertation of Yuvraj Agarwal is approved, and it is acceptable in quality and form for publication on mi- crofilm and electronically: Chair University of California, San Diego 2009 iii DEDICATION To Dadi, Shyam Babaji, Papa and Ma. iv TABLE OF CONTENTS Signature Page .................................. iii Dedication ..................................... iv Table of Contents ................................. v List of Figures .................................. ix List of Tables ................................... xi Acknowledgements ................................ xii Vita and Publications .............................. xv Abstract of the Dissertation ........................... xvi Chapter 1 Introduction ............................ 1 1.1 Reducing the Energy Consumption of Computing Devices 3 1.2 Using Collaboration to Aggressively Duty-Cycle Platforms 5 1.3 Contributions ........................ 7 1.4 Organization ......................... 8 Chapter 2 Background and Related Work .................. 9 2.1 Mobile Platforms ...................... 9 2.2 Power and Energy ...................... 12 2.2.1 Measuring Power and Energy Consumption .... 13 2.3 Related Work ........................ 14 2.3.1 Power Management in Mobile Devices ....... 14 2.3.2 Power Management in Laptops and Desktop PCs 17 Chapter 3 Radio Collaboration - Cellular and LAN Data Radios ..... 20 3.1 Overview of a VoIP Deployment .............. 23 3.2 Alternatives to VoIP over Wi-Fi Radios .......... 24 3.2.1 Cellular Data vs. Wi-Fi .............. 25 3.2.2 Smartphone Power Measurements ......... 28 3.3 Cell2Notify Architecture .................
    [Show full text]
  • Myexperience
    June 12th, 2007 MobiSys : Mobile Systems, Applications and Services myexperience A System for In Situ Tracing and Capturing of User Feedback on Mobile Phones Jon Froehlich1 Mike Chen2, Sunny Consolvo2, design: 2 1,2 use: Beverly Harrison , and James Landay build: 1 university of washington 2 Intel Research, Seattle mobile computing Mobile devices are used in a variety of contexts 2 lab methods For example, past research has looked at translating lab- based methods into a “mobile setting” 3 goal . Create a software tool that collects data about real device usage & context in the field . Data can be used to • Better understand actual device/system usage − E.g., how mobility patterns affect access to WiFi • Inform the design of future systems − E.g., optimize battery utilization algorithms based on charging behaviors 4 research challenges 1. Coverage: collect rich information about features of interest 2. Scale: collect large amounts of data over long periods of time 3. Extensible: easily add new data collecting capabilities 4. Situated: collect real usage data in its natural setting 5. Robustness: protect or backup data collected in the field 5 the myexperience tool Device usage and environmentUsers respond to short context- state are automatically sensedtriggered surveys on their mobile and logged. device. sensors user + Technique scales well+ Can gather otherwise – Cannot capture user intention,imperceptible data perception, or reasoning– Lower sampling rate than + sensors= context self-report myexperience MyExperience combines automatic sensor data traces with contextualized self- report to assist in the design and evaluation of mobile technology sensors, triggers, actions Sensors Triggers Actions trigger 15 0 Example Sensor: Example Triggers: Example Actions: DeviceIdleSensor DeviceIdle > 15 mins SurveyAction PhoneCallSensor PhoneCall.Outgoing == true ScreenshotAction RawGpsSensor Gps.Longitude == “N141.23” VibrationAction PlaceSensor Place.State == “Home” SmsSendAction WiFiSensor WiFi.State == “Connected” DatabaseSyncAction xml / scripting interface .
    [Show full text]
  • Check Point Secureclient Mobile R65 HFA1 Release Notes & What's
    Check Point SecureClient Mobile R65 HFA1 Release Notes & What’s New In This Document Information About This Release page 1 What’s New page 1 Software and Hardware Requirements page 1 Clarifications and Limitations page 3 Resolved Issues page 5 Frequently Asked Questions page 6 Information About This Release This document contains important information not included in the documentation. Review this information before setting up SecureClient Mobile. What’s New • SecureClient Mobile now supports Windows Mobile 6.0. • Many resolved issues. See “Resolved Issues” on page 5 for more details. • Interoperability with Pointsec Mobile. Software and Hardware Requirements In This Section Supported Devices page 1 Unsupported Devices page 3 Supported Communication Cards page 3 Supported Devices This section covers supported operating systems, processors, and tested devices. Supported Operating Systems • Any Pocket PC device running Windows Mobile 2003/2003 SE or Windows Mobile 5.0 Copyright © 2007 Check Point Software Technologies, Ltd. All rights reserved 1 Software and Hardware Requirements • Any Smartphone device running Windows Mobile 5.0 • Any device running Windows Mobile 6.0 (classic, standard, professional) Supported Processors • Intel ARM/StrongARM/XScale/PXA Series Processor family • Texas Instrument OMAP processor family. Tested Devices The devices in Table 1 have been tested and proved working. Table 1 Tested Devices Operating System Tested Devices PocketPC running • HP/Compaq iPAQ Pocket PC 2003 - series Windows Mobile 4150,4350,3950,5450,
    [Show full text]
  • Myexperience: a System for in Situ Tracing and Capturing of User Feedback on Mobile Phones Jon Froehlich1, Mike Y
    MyExperience: A System for In situ Tracing and Capturing of User Feedback on Mobile Phones Jon Froehlich1, Mike Y. Chen2*, Sunny Consolvo3, Beverly Harrison3, James A. Landay1,3 1Computer Science and Engineering 2Ludic Labs 3Intel Research Seattle University of Washington 107 South B Street, Suite 200 1100 NE 45th Street, 6th Floor Seattle, WA 98195 San Mateo, CA 94401 Seattle, WA 98105 {jfroehli, landay}@ [email protected] {beverly.harrison, cs.washington.edu sunny.consolvo}@intel.com ABSTRACT 1. INTRODUCTION This paper presents MyExperience, a system for capturing both Mobile computing has become an integral part of everyday life objective and subjective in situ data on mobile computing for many people, providing ubiquitous information access, activities. MyExperience combines the following two techniques: entertainment, and helping people stay connected to work, 1) passive logging of device usage, user context, and friends, and families. The most popular mobile device, the mobile environmental sensor readings, and 2) active context-triggered phone, has been adopted faster than any other technology in user experience sampling to collect in situ, subjective user human history [9]. In 20061, the number of mobile phone feedback. MyExperience currently runs on mobile phones and subscribers surpassed 2.5 billion and has more than twice the supports logging of more than 140 event types, including: 1) number of PC users worldwide. device usage such as communication, application usage, and Researchers are struggling to catch up. Tools and techniques media capture, 2) user context such as calendar appointments, and that have long been refined for studies of static computing 3) environmental sensing such as Bluetooth and GPS.
    [Show full text]
  • Energy Management Techniques in Modern Mobile Handsets Narseo Vallina-Rodriguez and Jon Crowcroft, Fellow, IEEE
    This article has been accepted for inclusion in a future issue of this journal. Content is final as presented, with the exception of pagination. IEEE COMMUNICATIONS SURVEYS & TUTORIALS, ACCEPTED FOR PUBLICATION 1 Energy Management Techniques in Modern Mobile Handsets Narseo Vallina-Rodriguez and Jon Crowcroft, Fellow, IEEE Abstract—Managing energy efficiently is paramount in modern cellular network providers, content providers, cloud service smartphones. The diverse range of wireless interfaces and sen- providers, hardware manufacturers and OS vendors) compete sors, and the increasing popularity of power-hungry applications to retain their share of the mobile business. that take advantage of these resources can reduce the battery life of mobile handhelds to few hours of operation. The research In this survey we analyse and compare general solutions for community, and operating system and hardware vendors found energy efficiency on mobile devices at the software level on six interesting optimisations and techniques to extend the battery life major axes: from operating system solutions to energy savings of mobile phones. However, the state of the art of lithium-ion via process migration to the cloud and protocol optimisations. batteries clearly indicates that energy efficiency must be achieved Our main contribution is to classify and provide a short both at the hardware and software level. In this survey, we will cover the software solutions that can be found in the research summary of the multiple efforts on studying, modeling and literature between 1999 and May 2011 at six different levels: reducing energy consumption in mobile devices. The work we energy-aware operating systems, efficient resource management, consider in this study are ones published between 1999 and the impact of users’ interaction patterns with mobile devices May 2011.
    [Show full text]