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.


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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

although JPEG uses it quite effectively on the coefficients that remain after transforming and quantizing image blocks.The run-length code represents the original 67 characters in only 16. It does not work well at all on continuoustone images such as photographs. Even binary data files can be compressed with this method. but the principle remains the same. 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. Of course. It is relatively efficient because most faxed documents are mostly white space. 21 . a generalization of run-length encoding that can take advantage of runs of strings of characters (such as BWWBWWBWWBWW). However. Run-length encoding performs lossless data compression and is well suited to palette-based iconic images. file format specifications often dictate repeated bytes in files as padding 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. PCX and ILBM. Common formats for run-length encoded data include PackBits. newer compression methods such as DEFLATE often use LZ77based algorithms. with occasional interruptions of black.

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

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

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


Figure 2 use case diagram 1 26 .

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

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

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

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 .

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. 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.1 SYSTEM REQUIREMENTS Operating System: Windows 98 or above or Linux Network Facilities: Good connection to the Internet facility and GPRS connection.

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

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

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

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

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

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

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.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.4.  Hal.

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 .

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

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

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

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

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

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

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

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

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

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;

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

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

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

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

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

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

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

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

successfully. The system uses GPRS as the medium through which the communication takes place. The mobile client is capable of accessing system from anywhere in the world provided there is GPRS 76 . 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.

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

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

79 .

Sign up to vote on this title
UsefulNot useful