Talk:Mobile Top
From EDeskWiki
Why view information on your Mobile Top ?
Use your mobile phone to access your virtual Desktop.
Is there any security issues that one should be careful about ?
eDeskOnline uses JAVA language for programming the applications. Information on your mobile will be fine even whilst using these 'office applications.
How does one go about it ?
eDeskOnline provides you with all the tools that you may need, when you are not in front of your desktop computer.
Additional features: Simply install the eDeskOnline application on your mobile
- You can now be on the move; and access all your information through eDeskOnline.
- Enjoy synchronisation with your eDeskOnline.
- No need to maintain two sets of information.
. .
- Calendar synchronization :
..Your secretary sets an alert on eDeskOnline using her computer.
..Synchronization takes place between eDeskOnline and your mobile.
..The meetings your secretary set up now show up on your mobile. . .
Handset compatibility requirements
- Java MIDP 2.0 / CLDC 1.2
- JSR75 (PIM)
- GPRS / WAP
- 2MB Memory
- Support for minimum 500Kb Jar Files
. . ( Such mobile handsets are commonly available at US $ 100 onwards ) . .
Click here to see a list of Supported Handsets
. .
Software Requirements
- a GPRS / WAP connection
. . ( Such facilities are comonly available from cell operators at 25 cents onwards upto a maximum of US $ 2 for unlimited usage )
.
.
Then on a day to day basis ...
You can run the application from here whenever you wish . .
Mobile Interface to the office
- The interface should run on a basic GPRS enabled handset.
- Assumption: that only the basic browser is available
- For J2ME, assume CLDC 1.1 and MIDP 2.0 are available.
Mobile Application (J2ME)
User interface runs on a Java based application. Client side programming is possible. Interaction with the hardware is possible. Can have push based code execution via the Push Registry.
The MIDP 2.0 Push Registry
Push ... refers to the mechanism or ability to receive and act on information asynchronously, as information becomes available, instead of forcing the application to use synchronous polling techniques that increase resource use or latency.
The Push Registry enables MIDlets to set themselves up to be launched automatically, without user initiation. The push registry manages network- and timer-initiated MIDlet activation; that is, it enables an inbound network connection or a timer-based alarm to wake a MIDlet up. For example, you can write a workgroup application that employs network activation to wake up and process newly received email, or new appointments that have been scheduled. Or you can use timer-based activation to schedule your MIDlet to synchronize with a server every so often then go to sleep.
http://developers.sun.com/mobility/midp/articles/pushreg/
Operating Bands/Frequency:
- GSM 900/1800/1900 MHz
- EDGE 850/1800/1900 MHz
- CDMA 1900 (CDMA 1.0)
- WCDMA 2100 MHz
.
.
.
Nokia Development Platform:
Series 40 - (Older one - supports all the basic j2me features which we are looking for including synchronisation; supports CDMA handsets) S60 - (Latest one - nokia moving all new phones to this platform - advanced java features supported. i could not find any CDMA handsets with S60. All were W-CDMA2100 phones) www.s60.com
Since we are looking to cover both GSM and CDMA networks, we will target to support the nokia series 40 platform. Although this does not mean that we will run only on nokia. Since j2me is platform independent, we will also be compliant with other handsets like motorola, sony ericson etc. As we move along, we will also get to know which motorola, sony handsets we will be able to support. But one thing is sure that most of the new handsets will be supported.
- Nokia requests Reliance to deploy new WCDMA networks
http://www.expressindia.com/news/fullstory.php?newsid=54624
Helsinki, Finland, September 14: Finnish telecom equipment major Nokia is talking to operators in India, including Reliance, for migrating them to the WCDMA technology.
.
.
- TRAI Recomendations on 3G
Mobile Web / Internet
The Mobile Web refers to the World Wide Web as accessed from mobile devices such as Mobile phone / cell phones, Personal digital assistant / PDAs, and other portable gadgets connected to a public network. Access does not require a desktop computer.
Today, many more people have access to mobile devices than a desktop computer.
However, Mobile Web access today still suffers from interoperability and usability problems. This is partly due to the small physical size of the screens of mobile devices and partly due to the incompatibility of many mobile devices with not only computer operating systems, but also the format of much of the information available on the Internet.
http://en.wikipedia.org/wiki/Mobile_Internet
Mobile browser
A mobile browser is a web browser designed for use on a mobile device such as a mobile phone.. Mobile browsers are optimised so as to display Web content most effectively for small screens on portable devices. Mobile browser software must be small and efficient to accommodate the low memory capacity and low-bandwidth of wireless handheld devices. Typically they were stripped-down web browsers, but as of 2006 some mobile browsers can handle latest technologies like Cascading Style Sheets / CSS 2.1, JavaScript and Ajax programming.
User Interface runs on your XHTML mobile browser. User Interface is XHTML based. Standard mobile browsers do not support client side scripting and hence no client side programming is possible. Hence smart user interfaces not possible. All code execution takes place only on server.
The Underlying technology is that the mobile browser ...connects via a cellular network, or increasingly via Wireless LAN, using standard HTTP over TCP/IP and displays web pages written in HTML, XHTML Mobile Profile (WAP 2.0), or Wireless Markup Language (WAP 1.3 which was based on Handheld Device Markup Language). WML and HDML are stripped-down formats suitable for transmission across limited bandwidth, and wireless data connection called Wireless Application Protocol (WAP).
http://en.wikipedia.org/wiki/Mobile_browser
Wireless Application Protocol
WAP is an open international standard for applications that use wireless communication. Its principal application is to enable access to the Internet from a mobile phone or PDA.
A WAP browser provides all of the basic services of a computer based web browser but simplified to operate within the restrictions of a mobile phone. WAP is now the protocol used for the majority of the world's mobile internet sites known as WAP sites. The Japanese i-mode system is another major competing wireless data protocol.
WAP sites, are websites written in, or dynamically converted to, WML (Wireless Markup Language) and accessed via the WAP browser.
Before the introduction of WAP, service providers had extremely limited opportunities to offer interactive data services. Interactive data applications are required to support now commonplace activities such as:
- email by mobile phone
- tracking of stock market prices
- sports results
- news headlines
- music downloads
http://en.wikipedia.org/wiki/Wireless_Application_Protocol
Non-messaging mobile content (NMMC): different business model scenarios
- Dumb pipe;
- On-portal; and
- Smart pipe,
http://www.juniperresearch.com/shop/viewreport.php?id=91
.mobi
DotMobi domain names were made available for public registration .. 2006... .mobi has already made headlines with several 6-figure domain sales, including Flowers.mobi for $200,000, Sportsbook.mobi .., and Fun.mobi ..., possibly indicating the confidence developers have in this young extension.
http://en.wikipedia.org/wiki/.mobi
Other important background material
nokia.com CDMA devices/3125
Device Specification: http://www.forum.nokia.com/devices/3125
handset supports xHTML browser........................supports R-World. should support edeskonline.mobi if R-World allows surfing on this handset.
J2ME: MIDP 1.0 CLDC 1.0 version is same as the LG handset - so synchronisation will not work.
