Motorola StarTAC Digital Data Microbrowser

Comments? ryang@trideja.com


Wireless Circuit Switched Data

The Motorola StarTAC has the cool ability to connect it to the computer, and use it as a circuit-switched wireless modem. Depending on your provider, you will get either 9600bps, or 14,400bps over the wireless link. You can dial any landline modem data number, and it is extremely reliable, and uses the same amount of battery power as a digital voice call. The data cable even has a jack on the side of the phone connector, so you can even charge the phone while it is connected to a computer or PDA.

It may be technically incorrect to call the phone a 'modem' while on a digital data call, because it is more like an ISDN terminal adapter - it merely converts the serial data from the computer into the form needed to pass over the packetized digital CDMA network. The beauty of this is that you can utilize you're full channel bandwidth for data transmission and reception. When you dial a regular land-line modem or ISP number, the service provider will have one of their land-line modems make the call to the other modem. This process takes between 20 to 30 seconds to setup the call before your computer receives the 'connect' message and can begin to transfer data, but you used 20 to 30 seconds of airtime to wait for the land-line modems to connect.

This may be just fine if you are connecting to a service that is only accessible via modem, but if you are connecting to the Internet, you can use a feature that many CDMA service providers offer, called 'Quick Net Connect'. This feature allows you to connect to an Internet connection provided by the mobile company, within about three seconds, and without a pair of land-line modems in between. This also reduces the latency of the connection to about half of the other method, and saves waiting for the modem negotiation!

Once connected, you will see a screen similar to that on the right, which will show you the current data transfer mode, the number dialed, connect time, and current transmit and receive activity. I have run a wireless webcam at some events that worked quite well using dialup networking and the quick net connect service, allowing me to connect, upload a webcam image via FTP, and disconnect within 20 seconds. And when you are billed by the second, that means three uploads for one minute of airtime!

Telus Mobility in British Columbia and Alberta allows you to utilize this service by having your computer dial #777 to the phone. The username and password are just QNC. I believe the username is lowercase for Bell Mobility in eastern Canada. There was also someone who managed to acquire a data cable for a phone on the ClearNET PCS network, and with their surf plan the user could also dial #777, and QNC to connect to the Internet from his computer. The interesting thing about this connection, is that it appears to be the same one that the microbrowsers use to connect so quickly.

Sprint PCS in the US also now offers the Quick Net Connect ability. On their network, the dialup number becomes #2932, and the username and password are 'web'


The Microbrowser

Many new north-american mobile phones are equipped with a microbrowser developed by OpenWave. The current generation of browsers is version 3.1, and relies on an up.link server run by the wireless provider to act as the gateway to pass properly formatted and compressed data to the mobile phone. Many people can not see the need for such a feature, but I am telling you, that is exactly what people were saying about the Internet six years ago. It may be a bit clunky now, but there are some features worth taking a look at.

Tired of paying 95 cents for a single directory assistance listing, where you can only get the phone number? Take a minute to do the search using a 411 search using your minibrowser, and you can get multiple listings, name, address, and phone number. Telus mobility currently charges 15 cents per minute to use this service, so even if you stayed online for 5 minutes to do it, you still come out ahead because you get more information. With practice, you can do it in less than 30 seconds of airtime, costing only 7 cents.

I have used the service to setup links to my server to allow me to stop and start NT services, check the logon times of users, and send & receive e-mail when I won't be near a computer for a while, and need someone to know I'm aware of their issue.

When microbrowser service is setup on your account, you must enter the up.link server IP address your provider has setup. On the StarTACs, you enter IPADDRESS FCN FCN, and you will see Link.A. Press STO, you will see IP Addr 1. Press STO. By default you will see 000.000.000.000. For Telus Mobility in BC, this address is 209.052.079.118.

To easily access sites, you can add them to bookmarks. Then, you can access the corresponding bookmark by holding down the number key associated with it. This allows you to jump straight to say, your e-mail, or favourite information site.

My friend Rog and is working on some content for Microbrowsers. There is now a mobile-playable gateway for Gates Motel!

A related newsgroup posting of mine:

Tue, 25 Jul 2000 22:18:03 -0700

I use Telus Mobility on a Motorola StarTAC 7860W in Vancouver BC Canada which uses 800Mhz CDMA, and rather than dialing my conventional ISP, I can dial Telus' Quick Net Connect (I just set the computer to dial #777) and I'm connected and logged on in 4 seconds. It connects directly to their Internet connection.

Otherwise, when you dial your conventional ISP, a land-line modem somewhere has to dial out to establish the data connection, wasting air time for it to connect, and your also increasing you're LAG with the additional modem in the loop. Check out the traceroute that I get with my QNC Connection:

 1 608 ms  398 ms  407 ms 198.229.143.1
 2 409 ms  400 ms  401 ms 198.228.43.2053
 3 404 ms  400 ms  860 ms 204.174.123.121
 4 394 ms  400 ms  400 ms 204.174.123.117
 <snip>
17 394 ms  399 ms  400 ms 209.247.11.14
18 394 ms  400 ms  400 ms 209.244.13.46
19 395 ms  400 ms  399 ms 63.210.199.10
20 421 ms  499 ms  499 ms 209.247.208.45

400-600 average compared to your 800-900 average... I would hope sprint has some similar feature!

It's great to use with my webcam on my laptop when I'm out and about... I can set it to connect, FTP an image to my website, and disconnect within 20 seconds (and when its 15c per minute billed by the second, its great being able to maximize the time spent connected!)

Ryan.

John Navas <spamfilter@navasgrp.dublin.ca.us> wrote in message
news:8lkc7a0ms5@enews1.newsguy.com...
> In <397D6D3E.A644FCCD@ieee.org>, "Lassi Hippeläinen"
> <"lahippel$does-not-eat-canned-food"@ieee.org> wrote:
>
> >> On Mon, 24 Jul 2000 23:50:37 -0700, John Navas
> >> <spamfilter@navasgrp.dublin.ca.us> wrote:
>
> >> >| 13 914 ms 1017 ms 1198 ms www.cisco.com [198.133.219.25]
>
> >One second ping is about normal. There is that nasty loop delay in the
> >air interface, typically a few hundred millisecs in either way.
>
> Seems high to me (e.g., as compared to even geosync satellite).
>
> >> >B. Throughput was erratic and poor on FTP download tests. Although a
> >> >14.4 bps modem connection should be able to sustain over 1500 cps, I
> >> >found that speed fluctuated all over the place, with an average of only
> >> >about 750 cps. (That may have been due to my particular location -- I
> >> >have not yet run tests in other areas.)
> >
> >Typical payload rate for GSM phones, for example, is about a third of
> >the nominal rate. This is mainly due to two reasons:
> >1) The loop delay. Any protocol that waits for handshakes will spend
> >some time waiting for a response. Like TCP.
>
> That depends on the size of the Receive Window, since TCP is a windowed
> protocol. I was using a Receive Window of 8192 bytes, which is
> sufficient to keep sending for almost 5 seconds without an
> acknowledgement even at maximum 14.4 Kbps throughput. With round-trip
> latency of about 1 second, that should be sufficient to prevent
> interruption of the data flow (even with an error-correction spike up to
> 2.5 seconds). Nevertheless, I do plan to run tests with a larger
> Receive Window to see it that makes any difference.
>
> >2) TCP has the congestion detection and slow start feature. In practice
> >it sets speed to highest _stable_ throughput. As your traceroute log
> >shows, you had quite a lot of jitter in the delay. TCP dares not use the
> >faster moments.
>
> TCP does not tune that rapidly, particularly when fluctuations occur
> within the timeframe of the Receive Window. Slow (re)start during a
> transfer depends on lost packets (likewise congestion avoidance), not
> latency per se. See RFC 2001.
>
> >Since you still got as much as 750 cps, the compression algorithm must
> >have helped :-)
>
> I was testing FTP with incompressible data, so compression couldn't have
> been a factor.
>
> >> >C. I was able to surf the web with my notebook computer, and the phone
> >> >maintained the data connection. Large pages of course loaded slowly.
> >
> >It would be interesting to compare the experience with surfing through a
> >WAP gateway, which is (better) suited for wireless access.
>
> That should indeed cut down the amount of data, at the expense of the
> full Internet experience. The other techniques I was using to optimize
> surfing (e.g., ad filtering, not loading images unless necessary) were
> sufficient for my purposes.
>
> --
> Best regards,
> John Navas <http://navasgrp.home.att.net/>


Return to Main Page

Ryan Goolevitch - ryang@trideja.com
Last Modified August 22, 2001