1. INTRODUCTION 1.

1 PROBLEM STATEMENT To develop a GPRS (General Packet Radio Service) based Personal Computer accessing system using mobile that enables user to access and modify data on the remote PC and to take complete control over it. The conventional systems use only the blue tooth technology. But our proposed system is designed to be operated over the GPRS which eliminates the distance measurement of the mobile from the PC except for the presence of GPRS facility. 1.2 EXPLANATION OF THE PROBLEM The system is developed using Sun Java application Server and J2ME midlet. The system is developed in different modules to enable reusability and flexibility of modification. The first module is to establish a http connection between the server and the client using the IP address and port number. The second module is to authenticate the user based upon the username and password given by the user. Once the connection and authentication is performed the next module is to respond to the client with the desktop images every t second time interval. In the succeeding module all the event capturing and event handling functions are implemented. Certain hot keys are provided for easy accessing of the various functions.

1

1.3 OBJECTIVE OF THE PROJECT The major objective of our project is to make the handheld devices more versatile and constructive by making it possible to access the remote PC from them using the GPRS technology. This empowers the user with access to his PC on the go from anywhere in the world with just a mobile. 1.4 SCOPE OF THE PROJECT The system is developed to serve as the empowering tool for the users. The system enables remote desktop access from just a GPRS enabled mobile. The connection can be established provided the system is in the switched on state and the server running on it. 1.5 ORGANIZATION OF THE REPORT CHAPTER 2: LITERATURE REVIEW This chapter gives an idea of the software and the tools used to develop our project. This chapter also explains briefly about the domain of the project. CHAPTER 3: SYSTEM DESIGN This chapter moves through the design phase of the project.It Illustrates the consummate structural frame work of the project. The various sequence of steps that takes place in order are
2

explained diagrammatically in this section. The scenarios are also illustrated pictorially. The individual functions along with the attributes are clearly explained. CHAPTER 4: IMPLEMENTATION This chapter gives a detailed description about the modules implemented in our project. It further includes the algorithms used to implement the modules. CHAPTER 5: CODING AND TESTING This chapter illustrates the various methods and classes used in the implementation of the project and the testing strategies adopted to test the software. CHAPTER 6: CONCLUSION AND FUTURE ENHANCEMENT This chapter gives an overview of the project completion and also about the future enhancements that shall be included in the project in the near future.

3

for CDMA based mobile phones (Qualcomm Inc. 2. and billing and payment. end-to-end solution for wireless applications development. 2003). They apply different approaches to accomplish the development of mobile applications. Various environments/languages are available for client-side handheld programming. (ii) J2ME.CHAPTER 2 LITERATURE SURVEY The mobile client must be loaded with an application which makes it possible to communicate with the server and access the Personal Computer.1 BREW (Binary Runtime Environment for Wireless) BREW is an application development platform created by Qualcomm Inc. BREW is a complete. 2. (iii) Palm OS. device configuration. BREW client software and porting tools for device manufacturers.. application distribution. CDMA is a digital wireless telephony transmission technique and its standards used for 2G mobile telephony are the IS-95 standards championed by Qualcomm. The complete BREW solution includes BREW SDK (software development kit) for application developers. and BREW Distribution System (BDS) that is controlled and managed by operators enabling them to easily get applications from developers to market and coordinate the billing and payment process. (iv) Symbian OS. Five of the most popular are (i) BREW. and (v) Windows Mobile.2 Palm OS 4 .

and the abundant software available. such as its long battery life. and support for a broad range of screen resolutions including QVGA. 2.11b local wireless and GSM.Palm OS. Its popularity can be attributed to its many advantages. It is an independent.. standard operating system—Symbian OS—for data-enabled mobile phones (Symbian Ltd. 2005). approximately twice that of its rivals. Two major versions of PalmOS are currently under development: Palm OS Garnet: It is an enhanced version of Palm OS 5 and provides features such as dynamic input area. including Bluetooth and 802. Mobitex. Palm OS Cobalt: It is Palm OS 6. which focuses on enabling faster and more efficient development of smart phones and integrated wireless (WiFi/Bluetooth) handhelds.. is a software licensing company that develops and supplies the advanced. 2002). Symbian OS includes a multi-tasking multithreaded 5 . developed by Palm Source Inc. Palm OS runs on almost two out of every three PDAs. 32bit operating system running on handheld devices (Palm Source Inc. open.3 Symbian OS Symbian Ltd. The plain design of the Palm OS has resulted in a long battery life. It supports many important wireless standards. primarily for use in cellular telecommunication.. improved network communication. forprofit company whose mission is to establish Symbian OS as the world standard for mobile digital data systems. and CDMA wide area wireless networks. support for a wide variety of wireless standards. is a fully ARM-native.

games. Portable Media Centers: 6 . 2. it was not well received primarily because of batteryhungry hardware and limited functionality. However. 2005). into a voice-centric handset.. possibly due to the way that Windows CE was adapted for handheld devices from other Microsoft 32-bit desktop operating systems. which is a range of operating systems developed by Psion for handheld devices.4 Windows Mobile Windows Mobile is a compact operating system for mobile devices based on the Microsoft Win32 API (Microsoft Corp. In 1996.core. such as emails. It is a descendant of EPOC. music. contacts.5 Pocket PCs: Pocket PC enables you to store and retrieve e-mail. appointments. application engines. exchange text messages with MSN Messenger. a user interface framework. Windows Mobile includes three major kinds of software: 2. integrated PIM functionality. Smartphones: Smartphone supplies functions of a mobile phone. but also integratesPDA-type functionality. a version of the Microsoft Windows operating system designed specially for a variety of embedded products. data services enablers. It is designed to be similar to desktop versions of Windows. and wireless communications. instant messages. browse the Web. and so on. Microsoft launched Windows CE. including handheld devices. and Web surfing.

Some Smartphones provide PalmOS or Windows CE operating systems and user interfaces. pagers. and photos transferred from Microsoft Windows XP based PC anywhere. almost any application that could be imagined running on a PC will find adequate performance on a handheld device. What makes our project feasible? Handheld Device: A handheld device as a computerized. Manufacturers are pushing towards so-called Smartphones for which a variety of applications can be downloaded. Palm and PocketPC. the speed of the processors for handhelds. electronic machine that is designed to be held in one hand. which is as fast as the PCs of just 4 years ago. organizers. and most mobile phones today are capable of browsing the Internet and running a Java virtual machine.Portable Media Centers let users take recorded TV programs. just like for PDAs. Phone manufacturers are adding more functions and capabilities to phones. doubling about every year and a half. and the size of their memories. mobile phones (generally called ‘cell phones’ in the US). home videos. Processors in mobile phones are also getting faster. Therefore. music. and Personal Digital Assistants (PDAs) such as the Newton. The definition clearly includes calculators. is following the well-known Moore’s law for computers. In fact. though such devices usually have a larger form-factor than conventional mobile phones. Today’s PDAs often run at 400 MHz. Other devices run operating systems specially 7 . Advances with handhelds Handheld devices are getting more powerful. movies.

which first appeared around 1994. and other technologies. which is now also called ‘Wi-Fi’. and none had driver support for Wi-Fi cards until the Compaq iPaq. where the handheld may be at some distance from the device to be controlled. was that it could easily synchronize all of its data with a desktop computer using a one-button HotSynce. Eventually. The most popular version is 802. in about 2000. PalmOS devices had built-in infrared wireless communication starting about 1998. but did not become widespread until around 2000. Initially. Newer phones also include cameras. Often the sending and receiving devices need to be less than 2 ft apart. handhelds with built-in Wi-Fi appeared. released in 1996. however. Limitations of IR include that the handheld must be carefully aimed at the receiver. Advances with communication technology The first model of the Apple Newton only provided connectivity with other computers as an extra-cost option. getting Wi-Fi required using a PC card (also called PCMCIA) for a laptop. One reason for the great success of the first Palm.11. and smaller Wi-Fi cards (such as the CompactFlash form-factor) allowed Wi-Fi to be used with more handheld devices. voice recognition. A problem with Wi-Fi. Now. and may not be pointing to it. and the IR in handhelds tend to be very short ranged. laptops were starting to get access to wireless technologies such as 802.11b. Meanwhile.designed for mobile phones. which allowed Palms to ‘beam’ information to each other. This makes communicating using IR inappropriate for most of the scenarios described in this article. it is possible to get Wi-Fi access on many different kinds of PDAs. Few of the early handheld devices could accept a PC card. Using Wi-Fi communication on a current iPaq 5455 drains the 8 . such as Symbian. touch screens. continues to be its high power usage.

Other radio technologies have addressed the power problem. The mobile network is increasingly able to carry data. With the outburst in technology. and therefore is relevant to handhelds interfacing with other technology. the scenario has undergone a dramatic change. a comparatively bulkier hardware was needed. and are becoming particularly common in the mobile phone market.6. Currently. BlueTooth is used primarily for connecting one device to one other device— such as a handheld to a personal computer Another wireless technology is the mobile phone network or GPRS. with some phone companies offering about 100 kbps with specialized interface cards 2.2 kbps. which connects devices to the internet. the BlueTooth radio network technology was designed from the beginning to have low power usage. Handheld devices with built-in BlueTooth are now available. BlueTooth research started in 1994. Unlike Wi-Fi. the hardware size of handheld devices has gone down. Fascinatingly. this miniaturization has occurred not 9 .6 J2ME 2. thus leading to the advent of mobile devices such as PDAs.battery in less than an hour.1 EVOLUTION OF J2ME For the past decade or two. but the standard was not released until 1998 with the technology not becoming widespread until 2003. To deliver the cutting edge features in the PCs. the computing world was entirely dominated by desktop machines. it is easy to get data rates at 19. Initially these features sufficed the needs of end user. palmtops and to the extent mobile phones. This rendered the desktop PCs immobile. But today..

even with radical changes in the desktop PCs segment. user needs the technical assistance offered by the device manufactures. The storming entry of JAVA into the software industry broke the barrier of platform dependence. To do so. An application developed for a particular pattern may not be compatible with the other platforms. Many such devices for example a mobile phone has no option to download and install software beyond what was configured 10 . 2. the focus of developers was primarily to impart portability between the platforms. This is primarily due to the emergence of quite a number of operating systems like LINUX.2 J2ME –A GLANCE J2ME is aimed primarily at consumer devices with limited computational ability. MAC and SOLARIS etc. Since this is not the case for the mobile devices as each manufacturer prefer their own operating system in their devices. portability remained a big question mark. the end user cannot himself install applications to suit his needs. And moreover. The practical feasibility of the above procedure seemed cumbersome. This raised a question amidst the developers as to why java could not be ported into the mobile devices. hampering the portability. Java 2 Micro Edition was introduced. At this juncture.6. Till few years back. So a modified version of Java. This to an extent made the desktop PC applications portable. This has bridged the large gap that existed between the two dimensions of computing. The practical inability with the cloning of J2SE into a mobile device is the constraints looming over the memory.at the cost of reduction in their computational ability.

7 CONNECTED LIMITED DEVICE CONFIGURATION The Connected Limited Device Configuration (CLDC) is a specification of a framework for Java ME applications targeted at devices with very limited resources such as pagers and mobile phones. Unlike a web browser downloading Java applets. Now the Application installation became even simpler. on a device affords the option to browse. The various API’s available in CLDC are: Java. and mainstream personal digital assistants. This instigated the developers in developing applications for mobile devices which are far more portable. The parallel developments in high speed wireless data communication led to the introduction of GPRS. and graphical capabilities. The Connected Limited Device Configuration (CLDC) defines the base set of application programming interfaces and a virtual machine for resourceconstrained devices like mobile phones.io A streamlined version of the java. When coupled with a profile such as the Mobile Information Device Profile (MIDP). With the availability of GPRS. With the introduction of J2ME. 11 .io package found in the standard edition for doing Input/Output operations. 2. the user can also install and download from remote location. an implementation of J2ME. pagers. The user has to just plug in the mobile device to an application platform and he can install the required application.during the manufacturing process. “micro” devices no longer need to be “static” in nature. download or install Java Applications and its content. processing power. it provides a solid Java platform for developing applications to run on devices with limited memory.

LCDUI has a simple screen based approach where a single Displayable is always active at a time in the application user interface. a set of lower level programming interfaces. Java. For all displayable the device MIDP 12 . javax.util A streamlined version of the java. javax.io Contains the Java ME-specific classes used for I/O operations. This package contains the collection classes like Vector and Hash table.Java.microedition. math functions. Alert. Textbox. 2. MIDP is part of the Java Platform. system functions. Micro Edition (Java ME) framework and sits on top of Connected Limited Device Configuration.microedition. Lang Contains classes thought applicable to most java programs. threading and security functions. Form and Canvas.util collection library. This package contains standard java types like Integers and Strings as well as basic exceptions. LCDUI API provides a small set of displayable actions in mobile device user interfaces: List. It also contains calendar and date classes.lcdui Contains the Java ME-specific classes used for the GUI.8 MOBILE INFORMATION DEVICE PROFILE (MIDP) Mobile Information Device Profile (MIDP) is a specification published for the use of Java on embedded devices such as mobile phones and PDAs.

The application programmer uses API specified command types to indicate the usage or purpose of the command in application user interface. EXIT. The term LCDUI was actually a joke in JCP Expert Group that created it. Common types are BACK. The idea of the command abstraction is to make applications more portable between various mobile devices from different vendors.0.implementation has control over the presentation and layout of the displayable. The placement of commands added to a displayable is completely up to the device implementation of this toolkit. and device implementation then places the operation to the common location for a given type in device's specific user interface style. Micro Edition book gave this term out. LCDUI also has quite unique approach of abstract operations. called Commands. Canvas also supports a full-screen mode that allows to make full screen graphics. Other common definitions have appeared. The joke was that no-one else really knows what it stands for. Canvas is a low-level graphics surface for which an application has full control over what is rendered to it. Then later the Programming Wireless Devices with the Java 2 Platform. It has not been opened up in the MIDP specifications but stands for Limited Capability Device User Interface. and SCREEN. This may be e. "LCD UI" or “Liquid Crystal Display User Interface” would reflect the fact that mobile phones normally 13 . like "a back navigation key" for BACK commands or button on screen. although normally some space is reserved for system areas like screen title and indicators common in mobile device UIs. Application developers should use the command types properly to indicate the purpose of an operation. ITEM. In MIDP 2.g. which is especially useful for games. a specific key.

microedition.microedition.use LCD displays.game A gaming API aimed at simple 2D sprite based games.9 GPRS General Packet Radio Service (GPRS) is a packet oriented Mobile Data Service available to users of Global System for Mobile 14 .0 MIDP 2.lcdui. javax. javax.midlet Contains the base classes for Java ME applications. the API is not specifically tailored to this particular display technology. It is also said that "LCD UI" stands for "lowest common denominator" due to the fact the specific UI has simplest possible design. javax. 2.microedition. javax. however. javax.pki Authenticate APIs for secure connections. Specialized APIs added in MIDP 2.media Contains the base classes of the multimedia playback.microedition.0 saw the introduction of gaming and multimedia APIs and some optional packages.rms Record Management System Provides a form of persistent storage for Java ME.microedition.

independent of whether the user actually is utilizing the capacity or is in an idle state.Communications (GSM) and IS-136 mobile phones. GPRS is a best-effort packet switched service. GPRS data transfer is typically charged per megabyte of throughput. GPRS originally supported (in theory) Internet Protocol (IP). It provides moderate speed data transfer. GPRS is integrated into GSM Release 97 and newer releases. It provides data rates from 56 up to 114 kbps. a technology between the second (2G) and third (3G) generations of mobile telephony. and for Internet communication services such as email and World Wide Web access. GPRS can be used for services such as Wireless Application Protocol (WAP) access.25 connections. where a certain Quality of Service (QoS) is guaranteed during the connection for non-mobile users. Originally there was some thought to extend GPRS to cover other standards. while data communication via traditional circuit switching is billed per minute of connection time. Point-to-Point Protocol (PPP) and X. as opposed to circuit switching. so that GSM is the only kind of network where GPRS is in use. by using unused Time division multiple access (TDMA) channels in. The last has been typically used for applications like wireless payment terminals. but now by the 3rd Generation Partnership Project (3GPP). Multimedia Messaging Service (MMS). that is. the GSM system.5G". for example. It was originally standardized by European Telecommunications Standards Institute (ETSI). although it has been removed 15 . Short Message Service (SMS). but instead those networks are being converted to use the GSM standard. 2G cellular systems combined with GPRS is often described as "2.

new protocols. when the mobile built-in browser is used. or even over IP.Wireless Village Internet Applications for Smart Devices through Wireless Application Protocol (WAP) Point-to-point (PTP) service: internetworking with the Internet (IP protocols) Short Message Service (SMS) Future enhancements: flexible to add new functions. while IPv6 is not yet popular. but doing this requires either a router to perform encapsulation or intelligence built in to the end-device/terminal e. In practice. IPv4 is being utilized. X. Services Provided By GPRS GPRS upgrades GSM data services providing:     Multimedia Messaging Service (MMS) Push to talk over Cellular PoC / PTT Instant Messaging and Presence -.    16 . more users.25 can still be supported over PPP. new accesses.from the standard. But if the mobile is used as a modem to the connected computer. UE (User Equipment). In this mode PPP is often not supported by the mobile phone operator.g. This allows DHCP to assign an IP Address and then the use of IPv4 since IP addresses used by mobile equipment tend to be dynamic. new radio networks. PPP is used to tunnel IP to the phone. such as more capacity.

CLASSES Class A Can be connected to GPRS service and GSM service (voice. and then resumed automatically after the GSM service (voice call or SMS) has concluded. using both at the same time. but using only one or the other at a given time. 2. SMS). GPRS service is suspended. Must be switched manually between one or the other service.1 GPRS ARCHITECTURE Figure 1: GPRS ARCHITECTURE 17 . Such devices are known to be available today. During GSM service (voice call or SMS). Most GPRS mobile devices are Class B.9. Class C Are connected to either GPRS service or GSM service (voice. SMS). Class B Can be connected to GPRS service and GSM service (voice. SMS).

 GPRS uses most of existing GSM network elements. it carries out the role in GPRS equivalent to the Home Agent in 18 . Serving GPRS Support Node (SGSN): A Serving GPRS Support Node (SGSN) is responsible for the delivery of data packets from and to the mobile stations within its geographical service area. The location register of the SGSN stores location information (e.6 to 171 Kbps. address(es) used in the packet data network) of all GPRS users registered with this SGSN. mobility management (attach/detach and location management).g.. current cell. interface. plus new network elements. and protocols for building a packet-based mobile cellular network.. current VLR) and user profiles (e. and authentication and charging functions. IMSI. The GGSN is the anchor point that enables the mobility of the user terminal in the GPRS/UMTS networks. Addition of two Network elements : 1. Its tasks include packet routing and transfer.  Multiple users can share the same air-interface resources. 2.  The data overlay network provides packet data transport from 9.GPRS can be thought of as an overlay network onto the GSM network.g. logical link management. Gateway GPRS Support Node (GGSN): A Gateway GPRS Support Node (GGSN) is a network node that acts as a gateway between a GPRS wireless data network and other networks such as the Internet or private networks. In essence.

because existing GSM phones: cannot handle the enhanced air interface cannot packetize data directly GPRS BSS  A software upgrade is required in the existing Base Transceiver Station (BTS).Mobile IP. Databases (VLR and HLR)  All the databases involved in the network requires software upgrades to handle the new call models and functions introduced by GPRS. PC Cards for laptops  These terminals will be backward compatible with GSM for voice calls.  The PCU directs the data traffic to the GPRS network and can be a separate hardware element associated with BSC. It maintains routing necessary to tunnel the Protocol Data Units (PDUs) to the SGSN that service a particular MS (Mobile Subscriber).  The Base Station Controller (BSC) also requires software  Upgrade and the installation of a new piece of hardware called a packet control unit (PCU). GPRS subscriber terminals  Only GPRS terminals (TEs) can access GPRS Servers  GPRS enabled phones. 19 . PDAs with embedded GSM.  The PCU provides a physical and logical data interface out of BSS for packet data traffic.

with B representing a black pixel and W representing white: WWWWWWWWWWWWBWWWWWWWWWWWWBBBWWW WWWWWWWWWWWWWWWWWWWWWBWWWWWWWW WWWWWW If we apply the run-length encoding (RLE) data compression algorithm to the above hypothetical scan line. we get the following: 12WB12W3B24WB14W Interpret this as twelve W's. one B. rather than as the original run. 2. relatively simple graphic images such as icons. etc. This is most useful on data that contains many such runs: for example. three B's. line drawings. and animations. Let us take a hypothetical single scan line. There will be many long runs of white pixels in the blank space. The home Location Register (HLR) and Visitor Location Register (VLR) especially require upgrades to functionally service GPRS. 20 . sequences in which the same data value occurs in many consecutive data elements) are stored as a single data value and count. and many short runs of black pixels within the text.10 Run-length encoding (RLE) Run-length encoding (RLE) is a very simple form of data compression in which runs of data (that is. For example. twelve W's. consider a screen containing plain black text on a solid white background.

with occasional interruptions of black. newer compression methods such as DEFLATE often use LZ77based algorithms. Of course. Common formats for run-length encoded data include PackBits. file format specifications often dictate repeated bytes in files as padding space.The run-length code represents the original 67 characters in only 16. Run-length encoding is used in fax machines (combined with other techniques into Modified Huffman coding). although JPEG uses it quite effectively on the coefficients that remain after transforming and quantizing image blocks. Even binary data files can be compressed with this method. a generalization of run-length encoding that can take advantage of runs of strings of characters (such as BWWBWWBWWBWW). the actual format used for the storage of images is generally binary rather than ASCII characters like this. but the principle remains the same. Run-length encoding performs lossless data compression and is well suited to palette-based iconic images. It is relatively efficient because most faxed documents are mostly white space. Data that have long sequential runs of bytes (such as lower-quality sound samples) can be RLE compressed after applying a predictive filter such as delta encoding. However. It does not work well at all on continuoustone images such as photographs. 21 . PCX and ILBM.

2. any machine 22 . They are not put into your . The exports contains a list of functions and variables that the dll makes available to other programs.dll is the core file of the Windows NT family of operating systems that provides and handles the interaction of software and hardware via the Hardware Abstraction Layer. which means that they're linked into your program at run time instead of build time. Think of this as the list of "global" symbols. The import library is a regular UNIX-like . There are three parts to a DLL: • • • the exports the code and data the import library The code and data are the parts you write . you'd create this list by hand with a text editor. Without hal.a library. and put into the dll. Hal.functions. like if you were building one big object files.exe at all. etc. The dlltool program creates the exports section of the dll from your text file of exported symbols.exe. but it only contains the tiny bit of information needed to tell the OS how your program interacts with ("imports") the dll.dll being present. the rest being hidden. This is also generated by dlltool. All these are merged together. Normally. variables.11 DLL DLLs are Dynamic Link Libraries. but it's possible to do it automatically from the list of functions in your code. This information is linked into your .

at the time.dll user32. Generally speaking. limited the usability of compress and other popular archivers. ACPI vs. such as the original file name.vs. It is a core file for several versions of the Microsoft Windows operating system. DEFLATE was intended as a replacement for LZW and other patent-encumbered data compression algorithms which. containing a CRC-32 checksum and the length of the original uncompressed data 23 • • • . a version number and a timestamp optional extra headers. multi-processor CPU. and APIC vs. If this file is damaged or deleted. the appropriate HAL is chosen during the initial installation of Windows.dll is a DLL that implements the Windows User API Client Library. the operating system will not work. PIC. Windows includes several HALs to support different kinds of hardware. which is: • a 10-byte header.running a Windows NT based operating system will fail to function. “gzip” is often also used to refer to the gzip file format. 2. containing a DEFLATE-compressed payload an 8-byte footer. containing a magic number. non-ACPI. the determining factors for HAL selection are uni.12 Gzip: Gzip is based on the DEFLATE algorithm. User32. a body. if it even boots. which is a combination of LZ77 and Huffman coding.

tar. zlib is an abstraction of the DEFLATE algorithm in library form which includes support both for the gzip file format and a lightweight stream format in its API. which also uses DEFLATE. The ZIP format can hold collections of files without an external archiver. 24 .gz or . but is less compact than compressed tarballs holding the same data because it compresses files individually and cannot take advantage of redundancy between files (solid compression). gzip is not to be confused with the ZIP archive format. gzip is normally used to compress just single files. The final .Although its file format also allows for multiple such streams to be concatenated together (these are simply decompressed concatenated as if they were one). and then compressing that archive with gzip.tgz file is usually called a tarball. Compressed archives are typically created by assembling collections of files into a single tar archive.

1 USECASE DIAGRAM: Mobile Client 25 .CHAPTER 3 SYSTEM DESIGN 3.

Figure 2 use case diagram 1 26 .

Remote Server: Figure 3 use case diagram 2 \ 27 .

Use Case Description Authentication: Use Case Name Mobile Client Actors Description Flow of Events Alternative Flow Mobile phone The client can login and get connected to server (system). message is displayed Use Case Name Image Response Actor Server Description Flow of Event Server reduce Desktop image resolution and send it to mobile(client) • Desktop image response for every ‘t’ sec Image Response: 28 . • Login • Get Authenticated from server(system) If there is no such username and password connection is denied.if the username and passwords are correct.

Keys &Mouse events: 29 .Use Case Name Event Trigger Actors Description Flow of Events Server The Server Triggers the key event in HAL • • Typing Characters. Rightclick. Numbers. Mouse operation like leftclick.

file modification is carried out Desktop Capture: 30 .File Operation: Use Case Name File operation Actor Server Description Flow of Event The various file manipulation like open. modify are done • File open.

Use Case Name Mobile Client Actors Description Flow of Event Mobile phone The desktop image that is sent from the server is displayed in the mobile and updated every time interval Image decrypted Image Displayed according to resolution Image Updated 31 .

3.2Activity Diagram Login: 32 .

Image Response 33 .

Event Response 34 .

3.3 Sequence Diagram 35 .

Figure 5 Sequence Diagram 3.4 Deployment Diagram 36 .

Deployment Diagram 37 .J2ME <<client>> VEWS KERNEL <<server>> Figure 6 .

3.5 System Architecture:- GPRS CLIENT SERVER Figure 4: System Architecture 38 .

5 or above.CHAPTER 4 IMPLEMENTATION 4. 39 .1 SYSTEM REQUIREMENTS Operating System: Windows 98 or above or Linux Network Facilities: Good connection to the Internet facility and GPRS connection. JRE(Java Runtime Environment) Tool: Sun Java Wireless Toolkit. More suitable for static IP systems Server: Sun Java Application Server Platform: JDK 1.

which includes a set of tools and utilities and an emulator for creating Java applications that run on handheld devices. Figure 3 shows the Sun Java Wireless Toolkit©. 2. under Microsoft Windows XP: 1. and examples that developers need to bring efficient and successful wireless applications to market quickly. mainstream personal digital assistants. The following steps showing how to develop an MIDP application.html.4. and designed to run on cell phones. development environment KToolbar as shown in Figure 3 by selecting the following Windows commands: Start ► All Programs ► Sun Java Wireless Toolkit 2. documentation. World!” program.sun. The toolkit includes the emulation environments.com/products/sjwtoolkit/download-2_3.3 Beta. Other client-side handheld programming is similar to this. 2004). Run MIDlet. an MIDP application. and other small mobile devices.3 Beta ►KToolbar (Figure 7 step creating j2me application) 40 . performance optimization and tuning features..2 IMPLEMENTATION DETAILS Steps to develop J2ME Program This sub-section gives an example of J2ME programming (Sun Microsystem Inc. a simple “Hello. at http://java. Download Sun Java Wireless Toolkit 2. which is a toolbox for developing wireless applications that are based on J2ME's Connected Limited Device Configuration (CLDC) and Mobile Information Device Profile (MIDP).

Figure 7 shows an emulator displays the execution results of HelloSuite. 41 . application resource files. Create a J2ME source program and put it in the directory “C:\WTK23\apps\HelloSuite\src\. 6. and application library files.” 5. which tells where to put the Java source files. 4.3. World!” and a ticker with a message “Greeting. world. Build the project by clicking on the Build button. An emulator will be popped up and displays the execution results of the built project. Run the project by clicking on the Run button. After the project HelloSuite is created.” Figure 6 gives a J2ME example. the KToolbar will display the message shown in Figure 5. Create a new project by giving a project name such as HelloSuite and a class name such as HelloMIDlet as shown in Figure 4. For example. which displaysthe text “Hello. The Build includes compilation and pre-verifying.

The application requests the Connector class to open and return a connection to a network resource. The steps involved in connection establishment are: 1.open() factory method parses the URI and returns a Connection object. The returned Connection object holds references to input and output streams to the network resource. 42 . infrared ports. The application reads from the InputStream or writes to the OutputStream as part of its processing.3 CLIENT MODULES: 4. 2.7. Then for the Authentication purpose the user needs to provide the client with the username and password of the corresponding system which is going to be accessed. The server is located using the socket address which comprises of its IP address and its corresponding port number. 4. 4. Upload the application to handheld devices by using USB cables. 3. By using the above steps a J2ME application can be developed now let us see how the application is developed for our project. The Connector. or Bluetooth wireless technology. The connection is established in J2ME using the connector() function.1 Server Access This module enables the client to establish a connection with the server.3. The application obtains the InputStream or the OutputStream object from the Connection object.

43 . The various keys and its usages correspond to various events that need to be done on the server system.3.The application closes the Connection when finished.5.2 Corresponding Event Capture and transfer The various events triggered by the user is grasped and its corresponding request is sent to the client. Figure 8 connection establishment 4. So the events are captured and it is transferred to the server with the corresponding ASCII codes.

the three-way (or 3-step) handshake occurs: 1. Finally the client sends an ACK back to the server. The active open is performed by the client sending a SYN to the server. both the client and server have received an acknowledgment of the connection. the server must first bind to a port to open it up for connections: this is called a passive open. Once the passive open is established. 4.3.4. To establish a connection. 2.4. a client may initiate an active open. In response. Before a client attempts to connect with a server. The image to be displayed needs to be of proper resolution of the mobile and also decryption of the data needs to be done.4 SERVERMODULE 4. At this point.1 Connection Establishment To establish a connection. the server replies with a SYN-ACK. The decryption is done using gzip decompression. 44 .3 Updating Display The Display of the system on the client needs to be constantly updated and it is done by replacing the desktop image sent from the server every t seconds. 3. TCP uses a three-way handshake.

3 Desktop Capture & Resolution matching: The Screen capture is done from the kernel services. SYN_RECEIVED. Netstat provides statistics for the following: • Proto . LISTEN. the port number is shown as an asterisk (*). The names that corresponds to the IP address and the port are shown unless the -n parameter is specified.  The screen is captured for every t seconds and then t and t+1 images are compared using XOR technique. For more information about the states of a TCP connection. • • Foreign Address .2 Authentication The Server checks its Socket information and its status using the netstat.4.The IP address of the local computer and the port number being used. and TIME_WAIT.4. the port number is shown as an asterisk (*). FIN_WAIT_1. FIN_WAIT_2. CLOSED.4. ESTABLISHED. LAST_ACK. 4. The name of the local computer that corresponds to the IP address and the name of the port is shown unless the -n parameter is specified.The IP address and port number of the remote computer to which the socket is connected. If the port is not yet established. • State .The name of the protocol (TCP or UDP). If the port is not yet established. Local Address . The possible states are as follows: CLOSE_WAIT. 45 . SYN_SEND.Indicates the state of a TCP connection.

Desktop Capture Image Capture Snapshot at ‘t’ Second Snapshot at ‘t+1’ second Separate RGB Component Separate RGB Component Subtraction Final Screen Figure 9 Desktop capture  The Resolution of the Captured bitmap is reduced to 1/4th of its original resolution. The Screen is captured as a bitmap image and the dimensions of the screen is obtained for resolution matching.  This is done by using the Color Quantization Technique  Helps to display images on low memory devices 46 .

4.4.  Hal.dll is the core file of the Windows NT family of operating systems that provides and handles the interaction of software and hardware via the Hardware Abstraction Layer 47 .4 Event Handling:  The various Keyboard and Mouse events are handled by using the kernel level services  The event requests from the client are transferred to the HAL and it is then handled by the kernel itself.

5 Snapshot: Sun Java Application Server Figure 10 SJAS server 48 .4.

Login Page Server Connection Figure 11 Login Page &Server Connection 49 .

Desktop Capture Figure 12 Desktop Capture 50 .

Menu options Mouse Events 51 .

52 .

Figure 13 Menu Options & Mouse Events Keyboard Events Shortcut keys 53 .

Figure 14 Keyboard Events & Shortcut Keys Listing the Drives Opening the File 54 .

` Figure 15 Listing the Drives & Opening the File CHAPTER 5 CODING AND TESTING 55 .

out.getLength(). } 56 .open(url).close(). len).createImage(data. HttpConnection hc = null. Image img = null.getResponseCode() == HttpConnection. public Image getImageFromUrl(String url) { InputStream is = null. } catch (Exception e) { } } if (hc != null) { try { hc. byte[] data = new byte[len].read(data). int len = (int)hc. } finally { if (is != null) { try { is. if (hc.close().HTTP_OK) { is = hc. private Image image=null. private Display display. } } catch (Exception e) { System.1 CODING: CLIENT SIDE:  SERVER ACCESS private Command exit. private SM1 parent. int actual = is. img = Image.openInputStream(). 0.println("IO Exception+"+e).5. try { hc = (HttpConnection)Connector.

addCommand(cancel). "". connect = new Command("Connect". "". 10. form. login = new Command("Login". Command. Command. TextField.append(password). cancel = new Command("Cancel". password = new TextField("Password:". TextField. TextField.append(userName). form. "". display. ipaddr = new TextField("IP-ADDR:".catch (Exception e) { } } return img. 2). form1= new Form("Connect"). TextField. form = new Form("Sign in").getDisplay(this). 10. 2).OK.addCommand(login). Command.CANCEL. portno = new TextField("Port-NO::". 57 . "". Displayable s) { if (c == exitCommand) { destroyApp(false). notifyDestroyed(). 15. form. 2). 10. } } public LoginMidlets() { userName = new TextField("LoginID:".ANY).ANY). }  Corresponding Event Capture and transfer public void commandAction(Command c. form.ANY).setCommandListener(this). } else if(c == ScreenCommand){ nt = new ntclient(this).setCurrent(form). } public void startApp() { display = Display.OK. form.PASSWORD).

1:8080/MouseClick."http://127.0.4.setCommandListener(this).1:8080/MouseClick.NUMERIC). MouseForm. MouseForm. } else if(c==MLClickCommand){ mc = new MouseClient(this.} else if(c == MouseCommand){ MouseForm = new Form("Mouse Movement"). } else if(c==BackCommand){ Display.getString()+"&y="+ty. ty = new TextField("Enter y". MouseForm.1:8080/MouseClick.getDisplay(this). MouseForm.getString()+"&y="+ty. MouseForm.addCommand(MLDClickCommand). MouseForm.0.0.0. tx = new TextField("Enter x".getString()+"&y="+ty. MouseForm.setCommandListener(this). MouseForm.NUMERIC).getString()+"&type=move"). } 58 .getString()+"&type=right").getString()+"&y="+ty."http://127.0.addCommand(BackCommand).addCommand(MRClickCommand).1:8080/MouseClick.html? x="+tx.0.setCurrent(displayForm).addCommand(MLClickCommand).html? x="+tx.addCommand(MPressCommand).html? x="+tx. Display.TextField. MouseForm.setCommandListener(this).append(tx).setCommandListener(this)."http://127. } else if(c==MRClickCommand){ mc = new MouseClient(this. MouseForm.0."". } else if(c==MPressCommand){ mc = new MouseClient(this.html? x="+tx."http://127. MouseForm.setCurrent(MouseForm).getDisplay(this).append(ty). MouseForm.getString()+"&type=left"). } else if(c==MLDClickCommand){ mc = new MouseClient(this."".0.setCommandListener(this).getString()+"&type=left-double").4.TextField.

i++) { xoredBytes[i] = (byte)(xoredBytes[i] ^ x[i]). GZipStream gz = new GZipStream(ms.Close().Read(y.Decompress. i < k. gz. byte abyte1[]. } internal static void ExclusiveOR(byte[] x) { int k = x. MemoryStream ms = new MemoryStream(x). 59 . Console.Close(). gz. gz.WriteLine(" Buffer Length " + uncompressedBufferLength).Length). byte[] y = new byte[uncompressedBufferLength]. true). Updating Display uncompressedBufferLength = BitConverter.Dispose(). byte abyte2[]. ms. } public byte[] a(byte abyte0[]. return y.Dispose(). 0. for (i = 0. CompressionMode. ms. byte abyte6[] = new byte[48].0). int i1) throws am { byte abyte3[] = new byte[20]. byte abyte5[] = new byte[4].ToInt32(uncompressedBufferLengthBytes. int i. y.Length.

a(abyte0. 0. byte abyte4[] = F._mthdo().a(abyte2. 0. byte abyte2[]. F. 0. 20).a(abyte1. for(int j1 = 0.a(abyte5. 0. k1++) abyte5[k1] = (byte)(i1 + j1). 16).boolean flag = false. 0. _fldgoto. abyte0[2] = -98.arraycopy(_fldgoto. 16). abyte6. 32).a(abyte1. F. 0. } return abyte6. return _fldgoto. F.a(abyte2. j1++) { for(int k1 = 0. abyte0[1] = 38. } public void _mthdo(byte abyte0[]) { abyte0[0] = -47. int i1) throws am { _fldgoto. 0. F. 32). } public byte[] _mthif(byte abyte0[]. 0. byte abyte1[].a(abyte0. F. 32). 0. _fldgoto. _fldgoto. _fldgoto. k1 <= j1. System. j1 * 16._mthdo(). 48). j1 + 1).a(abyte4.a(abyte0._mthdo(). 48). } class MyCanvas extends Canvas implements CommandListener { private Command exit. 32)._mthif(). 60 . j1 < 3. i1.

Image img = null. if (hc. try { hc = (HttpConnection)Connector. public Image getImageFromUrl(String url) { InputStream is = null. } } public MyCanvas(SM1 parent) { this.open(url).getLength(). } catch (Exception e) { } } return img. private Image image=null.parent = parent.HTTP_OK) { is = hc. byte[] data = new byte[len]. private Display display.getResponseCode() == HttpConnection.close(). 61 .read(data). img = Image. len).out.private SM1 parent.openInputStream(). int len = (int)hc.close(). } catch (Exception e) { } } if (hc != null) { try { hc. int actual = is.createImage(data. } } catch (Exception e) { System.println("IO Exception+"+e). 0. HttpConnection hc = null. } finally { if (is != null) { try { is.

err. Command.1). } } public void commandAction(Command command.Displayable display) { if(command==exit) { Display."Can't open the image file".1:8080/screen.Graphics.null).printStackTrace(). } } protected void paint(Graphics g) { if(image!=null) { g.getDisplay(parent).TOP|Graphics. } } } SERVER  Connection Establishment & Authentication 62 .drawImage(image. try { image = getImageFromUrl("http://127. alert. } catch(Exception err) { Alert alert=new Alert("Failure".0.LEFT).displayForm). setCommandListener(this).setCurrent(alert).EXIT.exit=new Command("Exit".setTimeout(Alert.0.setCurrent(parent.getDisplay(parent).jpg").0. addCommand(exit). Display.FOREVER).0.null.

WriteLine("Binded Socket"). eventEndPoint = new IPEndPoint(ipAddress. } internal static void BindSocket(Socket s. s. } internal static void StartListening(Socket s) { 63 .WriteLine("IPEndPoints Created"). Console. SocketType.port1.Tcp). imageEndPoint = new IPEndPoint(ipAddress.eventPort).Any .NoDelay = true. eventSocketListener = new Socket(AddressFamily.port2. SocketType.WriteLine("TCPSockets Created"). ipAddress = IPAddress.internal static void CreateIPEndPoints() { imagePort = RDSController. Console.InterNetwork.Stream.Bind(ipEnd).SendBufferSize = 100000. } internal static void CreateTcpSockets() { imageSocketListener = new Socket(AddressFamily. Console.InterNetwork. ProtocolType. } internal static void SetSocketOptions(Socket s) { s.Stream. ProtocolType.IPEndPoint ipEnd) { s.imagePort).Tcp). eventPort = RDSController.

Socket Flags.responseBytes.Send(responseBytes.InitializeByteArrays(). Console. } internal static void AcceptSecondConnection(Socket s) { eventSocket = s.Length.out. } internal static void AcceptFirstConnection(Socket s) { imageSocket = s. EventProcessor.WriteLine("Connection Accepted").Listen(2). ImageProcessor. Console. true) == 0) { connectionAccepted = true.Accept().canContinue = true. if (String. #endif 64 . } }  Desktop Capture & Resolution matching:internal static byte[] ColorQuantize(Bitmap bmp) { #if IMAGE System.println("Color quantizing starts").Accept().ASCII.GetBytes(response). } internal static void SendResponse() { responseBytes = Encoding.WriteLine("Listening Started").canContinue = true.Compare(response. imageSocket.None). "ye". Console.s.0. EventProcessor.WriteLine("Connection Accepted").

byte[] bmpArray = new byte[bmp.Width * bmp.Height]; int w = bmp.Width; int h = bmp.Height; BitmapData bmpData;

{ byte* bmpPtr = (byte*)bmpData.Scan0.ToPointer(); for (int i = 0; i < bmpData.Height; i++) { int k = i * DesktopScreen.screenWidth ; for (int j = 0; j < bmpData.Width; j++) { bmpArray[k + j] = (byte)((32 * (bmpPtr[2] / 32)) + (4 * (bmpPtr[1] / 32)) + (bmpPtr[0] / 64)); bmpPtr += 3; } } } #if IMAGE System.out.println ("Length of the Array returned : " + bmpArray.Length ); #endif internal static byte[] ExclusiveOR(byte[] x, byte[] y) { byte[] xorBytes = new byte[DesktopScreen.screenWidth * DesktopScreen.screenHeight]; int j = DesktopScreen.screenWidth * DesktopScreen.screenHeight; for (int i = 0; i < j; i++) {
65

xorBytes[i] = (byte)(x[i] ^ y[i]); } #if IMAGE System.out.println ("EXORed Image Size : " + xorBytes.Length ); #endif return xorBytes; } internal static byte[] RLEEncoderShortBoundary(byte[] x) { #if IMAGE System.out.println ("RLE Encoder short boundary starts"); #endif int i = 0, j = 0, xl = x.Length; byte[] y = new byte[1024 * 1000]; byte f, s; ushort r = 0; f = x[i]; i += 1; s = x[i]; i += 1; while (i < xl) { if (f == s) { y[j] = f; j += 1; y[j] = s;
66

j += 1;

while (i < xl) { if (f == x[i] && r < 65535) { r += 1; i += 1; } else break; } byte[] t = BitConverter.GetBytes(r); y[j] = t[0]; j += 1; y[j] = t[1]; j += 1; r = 0; if (i < xl - 1) { f = x[i]; i += 1; s = x[i]; i += 1; } else if (i == xl - 1) { y[j] = x[i]; j += 1; break;
67

if (i < xl) { s = x[i]. j += 1.ConstrainedCopy(y. j += 1. 0.} } else { y[j] = f.Length). } } } byte[] output = new byte[j].println ("Length of the Array returned : : " + output. break.println ("RLEEncoder short boundary ends "). 0. } 68 . #endif #if IMAGE System. #endif return output. Array. i += 1. } else { y[j] = s.out. output.out. #if IMAGE System. j). f = s.

Length).Length. #endif return ms.println ("Length of the Array returned : " + ms. gz. #if IMAGE System.out.ToArray().internal static byte[] GzipCompress(byte[] data) { #if IMAGE System.Close().dll Import dkey1. 0.println ("GZipCompress ends ").println ("GZipCompress starts ").dll internal enum MouseEventFlags { LEFTDOWN = 0x00000002. #endif #if IMAGE System. MemoryStream ms = new MemoryStream(). LEFTUP = 0x00000004.dll Import hal.Write(data. #endif uncompressedBufferLength = data. true). 69 . data. gz.out. }  Event Handling: class EventProcessor { #region Fields Import dmouse1.ToArray().Length ). CompressionMode.out.Compress. GZipStream gz = new GZipStream(ms.

internal static byte[] mouseButtonBytes = null. MouseMove. internal static byte[] eventBytes = null. ABSOLUTE = 0x00008000. RIGHTUP = 0x00000010. MouseWheel } internal enum MButton { NotAssigned. Middle. MIDDLEUP = 0x00000040. 70 . KeyDown. MouseUp.NotAssigned . MOUSEWHEEL = 0x00000800 } internal enum InputEvent { NoEvent.NoEvent. Left. RIGHTDOWN = 0x00000008. internal static byte[] keyValueBytes = null.MIDDLEDOWN = 0x00000020. Right } internal static MButton mouseButton = MButton. MouseDown. KeyUp. internal static InputEvent inputEvent = InputEvent. MOVE = 0x00000001.

dll")] private static extern void mouse_event(uint dwFlags. internal static byte[] mouseDeltaBytes = null. internal volatile static bool shouldStop = false. 71 . [DllImport("user32. #endregion internal static void InitializeByteArrays() { eventBytes = new byte[1]. internal volatile static bool shouldExit = false. byte bScan. UIntPtr dwExtraInfo). keyValueBytes = new byte[1]. internal static byte[] syncBytes = null. mouseButtonBytes = new byte[1]. uint dy. UIntPtr dwExtraInfo). int dwData. uint dx. #endregion #region Methods #region DLLImport Methods [DllImport("user32.internal static byte[] mouseXposBytes = null. uint dwFlags. internal static Point point. internal static short mouseXpos = 0. internal volatile static bool pausedByClient = false. internal static short mouseYpos = 0. internal static short mouseDelta = 0. internal static byte[] mouseYposBytes = null.dll")] private static extern void keybd_event(byte bvk. internal volatile static bool canContinue = false.

} if (eventBytes[0] == 1) { inputEvent = InputEvent. #endif while (true) { (s. mouseYposBytes = new byte[2]. point = new Point().Receive(keyValueBytes. 0. } internal static void ReceiveEvent(Socket s) { if (RDSSocket.KeyUp. SocketFlags.Receive(eventBytes. SocketFlags. mouseDeltaBytes = new byte[2].Available > 0) { s. eventBytes. 0.Length.out. s.println ("Receiving Event ").connectionAccepted ) { #if EVENT System.None). keyValueBytes. syncBytes = new byte[1].mouseXposBytes = new byte[2].Length. break.None). } 72 .

None).MouseDown. } else if (mouseButtonBytes[0] == 3) { mouseButton = MButton. } 73 . 0. s. s. SocketFlags. 0. } else if (eventBytes[0] == 3) { inputEvent = InputEvent.Left. SocketFlags. if (mouseButtonBytes[0] == 1) { mouseButton = MButton.Receive(mouseButtonBytes.Length.Left.Receive(keyValueBytes.Receive(mouseButtonBytes.Right. 0.Length.None).Middle.else if (eventBytes[0] == 2) { inputEvent = InputEvent.MouseUp. mouseButtonBytes. s.None). } } else if (eventBytes[0] == 4) { inputEvent = InputEvent.Length.KeyDown. } else if (mouseButtonBytes[0] == 2) { mouseButton = MButton. mouseButtonBytes. SocketFlags. keyValueBytes. if (mouseButtonBytes[0] == 1) { mouseButton = MButton.

Middle. 0). } else if (mouseButtonBytes[0] == 3) { mouseButton = MButton. mouseYpos = BitConverter.None).X = mouseXpos.Length.Length.ToInt16(mouseDeltaBytes.ToInt16(mouseYposBytes.Y = mouseYpos.Receive(mouseXposBytes.Receive(mouseDeltaBytes. s. mouseYposBytes. 0. 0.ToInt16(mouseXposBytes.else if (mouseButtonBytes[0] == 2) { mouseButton = MButton.println (" Received Event : " + eventBytes[0]). } } else if (eventBytes[0] == 5) { inputEvent = InputEvent.None). mouseDeltaBytes. } else if (eventBytes[0] == 6) { inputEvent = InputEvent. s. 0). SocketFlags. 0). s.MouseMove. SocketFlags. SocketFlags. mouseXpos = BitConverter.Right. point. 74 .out.Receive(mouseYposBytes. mouseXposBytes.MouseWheel.Length. 0. mouseDelta = BitConverter. } #if EVENT System.None). point.

2. 5.2.4 Black box Test In the black box test we found that for the given input values the required output values were obtained. 5.2.2.2 Stress Test We are concerned with exercising the internal logic of the program and so we traversed particular execution paths and we exercised test cases. 5.5 White box Test In the white box test temporary variables were used in the functional to test the execution of the process and the required output has been obtained 75 .2 TESTING The various testing strategies used in our code are: • Functional Test • Stress Test • Structure Test • Black box Test • White box Test 5.#endif 5. 5.3 Structure Test In the structure test we found the exact flow of the program and tested for incremental test cases.1 Functional Test We have exercised the code with normal input values for which expected results were obtained.2.

The system uses GPRS as the medium through which the communication takes place.successfully. The mobile client is capable of accessing system from anywhere in the world provided there is GPRS 76 . We tested the code unit by unit and it was efficient in integrating into the required software product and finally performing the possible test scenarios performed the integration testing to the product and the perfect output was obtained without any error. CHAPTER 6 CONCLUSION AND FUTURE ENHANCEMENTS In this system the Personal Computer is accessed from remote location with just the handheld devices.

Thus this makes this remote desktop accessing system practically more viable. 77 . This can be done by calling on to the landline which is connected to the system and from the line a circuit is designed to induce a 5Volt trigger to boot the system on and the server is made default in the system startup services. it is possible to control and perform tasks on the system from remote locations on the move. Brad A. This system requires the system to be on.Myers ‘Using handhelds for wireless remote control of PCs’. unlike the existing systems which just makes use of Bluetooth connectivity and limits the communication distance to few meters which is practically of little use. The performance of the system is dependent on the GPRS bandwidth available. with the server running for establishing communication. In the future we have proposed to enhance this feature by using the mobile itself to switch on the system and then to establish the connection. CHAPTER 7 REFERENCES 1. Thus by running the server on the system and the client application on the mobile. June 2004.connectivity.

Wen-Chen Hu. CMWare. 3. Brad A.. 4. Chung-wei Lee. ‘Client side handheld computing and Java 2 platform Micro Edition’. “Inc White Paper: ‘The Emergence of PC Place Shifting’”. Soma Gosh ‘MIDlet deployment: Learn to deploy remotely and locally to J2ME devices’ April 2006. et al. ‘Using handhelds and PCs together’ by’.2. 2007. Copenhagen. November 2001. 5.Myers. “Inc White Paper: NetOp® Mobile”. Yapin Zhong. 78 . 6. September 2006.

79 .

Sign up to vote on this title
UsefulNot useful