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.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

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.


and billing and payment. 2. 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. for CDMA based mobile phones (Qualcomm Inc.2 Palm OS 4 . and (v) Windows Mobile.1 BREW (Binary Runtime Environment for Wireless) BREW is an application development platform created by Qualcomm Inc. 2. (iv) Symbian OS.. end-to-end solution for wireless applications development. 2003).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. BREW client software and porting tools for device manufacturers. BREW is a complete. (iii) Palm OS. CDMA is a digital wireless telephony transmission technique and its standards used for 2G mobile telephony are the IS-95 standards championed by Qualcomm. Various environments/languages are available for client-side handheld programming. application distribution. (ii) J2ME. Five of the most popular are (i) BREW. They apply different approaches to accomplish the development of mobile applications. device configuration. The complete BREW solution includes BREW SDK (software development kit) for application developers.

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

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

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

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

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

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

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

2. This package contains standard java types like Integers and Strings as well as basic exceptions. javax. For all displayable the device MIDP 12 . It also contains calendar and date classes.util collection library. 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.io Contains the Java ME-specific classes used for I/O operations.Java.microedition. javax. This package contains the collection classes like Vector and Hash table.microedition. math functions.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. Form and Canvas. Micro Edition (Java ME) framework and sits on top of Connected Limited Device Configuration. Lang Contains classes thought applicable to most java programs.lcdui Contains the Java ME-specific classes used for the GUI.util A streamlined version of the java. Alert. MIDP is part of the Java Platform. threading and security functions. LCDUI API provides a small set of displayable actions in mobile device user interfaces: List. system functions. Textbox.

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

javax. It is also said that "LCD UI" stands for "lowest common denominator" due to the fact the specific UI has simplest possible design. javax.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 .use LCD displays.microedition. Specialized APIs added in MIDP 2. javax.microedition.0 saw the introduction of gaming and multimedia APIs and some optional packages. however.media Contains the base classes of the multimedia playback.microedition.0 MIDP 2. the API is not specifically tailored to this particular display technology.lcdui.rms Record Management System Provides a form of persistent storage for Java ME. javax.midlet Contains the base classes for Java ME applications. 2. javax.microedition.microedition.pki Authenticate APIs for secure connections.

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

new protocols. PPP is used to tunnel IP to the phone. more users. or even over IP. 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. In practice. new radio networks. when the mobile built-in browser is used.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. UE (User Equipment). but doing this requires either a router to perform encapsulation or intelligence built in to the end-device/terminal e. In this mode PPP is often not supported by the mobile phone operator.25 can still be supported over PPP. while IPv6 is not yet popular. such as more capacity. new accesses. 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 -.g.from the standard. IPv4 is being utilized.    16 . But if the mobile is used as a modem to the connected computer.

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

g. Its tasks include packet routing and transfer.6 to 171 Kbps..  GPRS uses most of existing GSM network elements. 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.. plus new network elements.g. and authentication and charging functions. IMSI. Addition of two Network elements : 1. mobility management (attach/detach and location management). The location register of the SGSN stores location information (e. interface. 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.GPRS can be thought of as an overlay network onto the GSM network. current cell. 2. current VLR) and user profiles (e. it carries out the role in GPRS equivalent to the Home Agent in 18 .  Multiple users can share the same air-interface resources. In essence. logical link management.  The data overlay network provides packet data transport from 9. address(es) used in the packet data network) of all GPRS users registered with this SGSN. and protocols for building a packet-based mobile cellular network. The GGSN is the anchor point that enables the mobility of the user terminal in the GPRS/UMTS networks.

PC Cards for laptops  These terminals will be backward compatible with GSM for voice calls. 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. PDAs with embedded GSM. It maintains routing necessary to tunnel the Protocol Data Units (PDUs) to the SGSN that service a particular MS (Mobile Subscriber). GPRS subscriber terminals  Only GPRS terminals (TEs) can access GPRS Servers  GPRS enabled phones.  The PCU provides a physical and logical data interface out of BSS for packet data traffic. 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. 19 .  The Base Station Controller (BSC) also requires software  Upgrade and the installation of a new piece of hardware called a packet control unit (PCU).  The PCU directs the data traffic to the GPRS network and can be a separate hardware element associated with BSC.

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

Of course. Common formats for run-length encoded data include PackBits. a generalization of run-length encoding that can take advantage of runs of strings of characters (such as BWWBWWBWWBWW). with occasional interruptions of black.The run-length code represents the original 67 characters in only 16. 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. However. It does not work well at all on continuoustone images such as photographs. 21 . PCX and ILBM. newer compression methods such as DEFLATE often use LZ77based algorithms. although JPEG uses it quite effectively on the coefficients that remain after transforming and quantizing image blocks. file format specifications often dictate repeated bytes in files as padding space. Even binary data files can be compressed with this method. but the principle remains the same. 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. Run-length encoding is used in fax machines (combined with other techniques into Modified Huffman coding). the actual format used for the storage of images is generally binary rather than ASCII characters like this.

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

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

24 .tar. gzip is not to be confused with the ZIP archive format.gz or . Compressed archives are typically created by assembling collections of files into a single tar archive. and then compressing that archive with gzip. 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. gzip is normally used to compress just single files. The final . 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). which also uses DEFLATE. The ZIP format can hold collections of files without an external archiver.Although its file format also allows for multiple such streams to be concatenated together (these are simply decompressed concatenated as if they were one).tgz file is usually called a tarball.


Figure 2 use case diagram 1 26 .

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

• Login • Get Authenticated from server(system) If there is no such username and password connection is denied.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 .if the username and passwords are correct.

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

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

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 Sequence Diagram 35 .3.

4 Deployment Diagram 36 .Figure 5 Sequence Diagram 3.

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

and examples that developers need to bring efficient and successful wireless applications to market quickly.3 Beta ►KToolbar (Figure 7 step creating j2me application) 40 .html.sun. 2. Download Sun Java Wireless Toolkit 2. at http://java. a simple “Hello. performance optimization and tuning features. under Microsoft Windows XP: 1..4. documentation.2 IMPLEMENTATION DETAILS Steps to develop J2ME Program This sub-section gives an example of J2ME programming (Sun Microsystem Inc. Figure 3 shows the Sun Java Wireless Toolkit©. Run MIDlet. an MIDP application.com/products/sjwtoolkit/download-2_3. and other small mobile devices. The following steps showing how to develop an MIDP application. 2004).3 Beta. 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. 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). mainstream personal digital assistants. World!” program. Other client-side handheld programming is similar to this. which includes a set of tools and utilities and an emulator for creating Java applications that run on handheld devices. The toolkit includes the emulation environments.

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

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

Figure 8 connection establishment 4.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. So the events are captured and it is transferred to the server with the corresponding ASCII codes.3. The various keys and its usages correspond to various events that need to be done on the server system.The application closes the Connection when finished. 43 .

In response. Finally the client sends an ACK back to the server. Before a client attempts to connect with a server. a client may initiate an active open.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. 4. To establish a connection. The active open is performed by the client sending a SYN to the server. Once the passive open is established. 2. 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.4. The decryption is done using gzip decompression. the server replies with a SYN-ACK. the three-way (or 3-step) handshake occurs: 1. TCP uses a three-way handshake. 3.4.1 Connection Establishment To establish a connection. the server must first bind to a port to open it up for connections: this is called a passive open.3. both the client and server have received an acknowledgment of the connection. 44 . At this point.

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

 This is done by using the Color Quantization Technique  Helps to display images on low memory devices 46 . 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.

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.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 .

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

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

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

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

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

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

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

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

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

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++) {

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;

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;

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

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

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

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

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

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

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

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 . 5.2.#endif 5.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 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.2.2.1 Functional Test We have exercised the code with normal input values for which expected results were obtained.2. 5. 5.3 Structure Test In the structure test we found the exact flow of the program and tested for incremental test cases.2 TESTING The various testing strategies used in our code are: • Functional Test • Stress Test • Structure Test • Black box Test • White box Test 5.

CHAPTER 6 CONCLUSION AND FUTURE ENHANCEMENTS In this system the Personal Computer is accessed from remote location with just the handheld devices. 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. 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 .

77 . Brad A. 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. The performance of the system is dependent on the GPRS bandwidth available.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. June 2004. This system requires the system to be on. Thus by running the server on the system and the client application on the mobile. with the server running for establishing communication. Thus this makes this remote desktop accessing system practically more viable. CHAPTER 7 REFERENCES 1. 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.connectivity. it is possible to control and perform tasks on the system from remote locations on the move.

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

79 .

Sign up to vote on this title
UsefulNot useful