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.


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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Mobile IP. GPRS subscriber terminals  Only GPRS terminals (TEs) can access GPRS Servers  GPRS enabled phones. PDAs with embedded GSM.  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.  The PCU provides a physical and logical data interface out of BSS for packet data traffic. 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). 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. It maintains routing necessary to tunnel the Protocol Data Units (PDUs) to the SGSN that service a particular MS (Mobile Subscriber). 19 . PC Cards for laptops  These terminals will be backward compatible with GSM for voice calls.

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

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

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

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

tgz file is usually called a tarball. which also uses DEFLATE. and then compressing that archive with gzip. The final . gzip is not to be confused with the ZIP archive format. Compressed archives are typically created by assembling collections of files into a single tar archive.gz or . 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). 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). 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. 24 .tar.


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.if the username and passwords are correct.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 .

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

modify are done • File open. 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.

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 .

5 System Architecture:- GPRS CLIENT SERVER Figure 4: System Architecture 38 .3.

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

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

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

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

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

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

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

 This is done by using the Color Quantization Technique  Helps to display images on low memory devices 46 . The Screen is captured as a bitmap image and the dimensions of the screen is obtained for resolution matching. 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.

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

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

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

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

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

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

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

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

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

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

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;

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

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

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

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

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

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

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

5 White box Test In the white box test temporary variables were used in the functional to test the execution of the process and the required output has been obtained 75 .2 TESTING The various testing strategies used in our code are: • Functional Test • Stress Test • Structure Test • Black box Test • White box Test 5.2. 5.#endif 5.2.2. 5.4 Black box Test In the black box test we found that for the given input values the required output values were obtained.1 Functional Test We have exercised the code with normal input values for which expected results were obtained.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. 5.3 Structure Test In the structure test we found the exact flow of the program and tested for incremental test cases. 5.2.

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

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

79 .

Sign up to vote on this title
UsefulNot useful