No, you are not about to read some Luddite rant about how smart phones are destroying our society. I love smart phones and most of you do too. Itâ€™s remarkable how quickly we have gone from arguing over the definition of a smart phone to not being able to live without them. In fact, the rapid adoption of smart phones has led to the problem I am going to talk about: smart phones can overwhelm dumb wireless networks.
Many of the networks that carry the wireless data to and from our smart phones are built with chips that were designed before Apple announced the first iPhoneÂ® in June of 2007. It takes a year or two to get a new semiconductor chip designed and built. Then another year or two for network equipment manufacturers to get their products into the market. By the time that new equipment has been deployed into networks around the world, five or six years have passed since chip designers decided what features their networking chips would have.
Even the latest 4G networks are built with chips that were designed before Apple invited everyone to store their music libraries in the cloud and before Vine enabled every kid with a phone to create and distribute videos. Todayâ€™s networks were not designed with these wireless data applications in mind and they are struggling to keep up.
Making dumb networks smarter
The problem is proving hard to solve because data traffic is growing faster than the obvious ways to cope with it. Network operators canâ€™t simply deliver more network capacity. Available spectrum is limited as is the capital to invest in expanded networks. The seemingly inevitable improvements in technology performance arenâ€™t enough to solve the problem either. Demand for data traffic is growing faster than Mooreâ€™s law can answer. Doing more of the same thing or doing the same thing faster isnâ€™t enough. Networking companies need to figure out new ways to handle data. We need to make dumb networks smarter.
When I say â€śdumb networks,â€ť I am referring to the fact that most of the existing wireless data networks were designed to move a packet of data from point A to point B in a reasonably short time. Thatâ€™s a fine approach when wireless networks can easily carry occasional stock updates and photo uploads from a few million early adopters. But now, when 90% of handset sales are iPhones or AndroidÂ® phones, the networks have become overwhelmed with data. Treating data packets with equal importanceÂ â€“ whether they are part of a VOIP phone call, business critical data or the 40 thousandth download of a cute panda video â€“ doesnâ€™t make sense anymore.
Prioritizing data for higher speed
As networks get smarter, they will be able to triage data â€“ for example, identifying voice packets to maintain call quality. Smart networks will know if the same video has been downloaded 5 times in the last minute, and will store it locally to speed the next download. Smart networks will know if a business user has contracted for a guaranteed level of service and prioritize those packets accordingly. Smart networks will know if an application update can wait until times of the day when the volume of network trafficÂ is lower. Smart networks will know if a flow of packets contains virus software that could damage your phone or the network itself.
To be smart about the data being transported, networks need a higher level of real-time analytical intelligence. We are now seeing the introduction of networking chips and equipment designed in the era of the smart phone. Networks are now gaining the ability to distinguish the nature of the data contained in a packet and to make smart decisions about the way the data is delivered. Networks are, in a word, becoming smarter â€“ better able to manage the crush of data coursing through them every day. Smart networks mayÂ soon be able to stand up to smartphones, and perhapsÂ even outwit them.
Have you ever seen the old BBC TV show â€śConnectionsâ€ť? Itâ€™s a little old now, but I loved how it followed threads through time, and I marveled at the surprising historical depth of important â€śinventions.â€ť I think we need to remember that as engineers and technologists. We get caught up in the short-term tactical delivery of technology. We donâ€™t see the sometimes immense ripples in society from our work â€“ even years later.
I got a flurry of emails yesterday, arranging an anniversary get-together in August at the Apple campus. Why? Itâ€™s the 20th anniversary of the Newton. Ok â€“ so this has nothing to do with LSI really, but it does have a lot to do with our everyday lives. More than you think.
So you either know the Newton and think it was a failure (think Trudeauâ€™s famous handwriting cartoon), or you donâ€™t and youâ€™re wondering what the *bleep* Iâ€™m talking about. Sometimes things that donâ€™t seem very significant early on end up having profound consequences.Â And I admit, the Newton was a failure, too expensive and not quite good enough, and the world couldnâ€™t even get the concept of a general-purpose computer in your hand.
But oh â€“ you could smell the future and get a tantalizing hint of what it would be. Remember â€“ weâ€™re talking 1993 here.
First â€“ why does Rob Ober care? Itâ€™s personal. While I didnâ€™t remotely help create the Newton, I did help bring it to market, mature the technology, and set the stage for the future (well â€“ itâ€™s not the future any more â€“ itâ€™s now). I was at Apple wrapping up the creation of the PowerPC processor and architecture, and the first Power Macs. I have a great memory around that time of getting the first Power Mac booted. Someone had the great idea of running the beta 68K emulator (to run standard Mac stuff). That was great, it worked, and then someone else said â€“ wait â€“ I have an Apple II emulator for the 68K Mac. So we had the very first PowerPC Mac running 68K code as a Mac to emulate a 6502 as an Apple II â€¦ and we played for hours. I also have a very clear memory of that PowerPC Mac standing shoulder-to-shoulder with the Robotron game in the Valley Green 5 building break room. It was a state-of-the-art video game and looked like this.
Yea, that shows you it was a while ago. (But it was a good game.)
A guy named Shane Robison pulled me over (yea, the same HP CTO, now CEO of FusionIO) to come fix some things on the super-hush Newton program. In the end, I took over responsibility for the processors, custom chips, communication stacks and hardware, plastics and tooling, display, touch screen, power supply, wireless, NiMH and LiION batteriesâ€¦ Â A lot. Â We pushed the limits of state of the art on all those fronts. It was a really important wonderful/terrible part of my career. I learned an amazing amount.
(If youâ€™re interested in viewing a Newton from todayâ€™s perspective, there is a fascinating review here: http://techland.time.com/2012/06/01/newton-reconsidered/)
Let me start with some boring effects. We were using the ARM processor because of its low power. But. It wasnâ€™t perfect, and ARM itself was on the edge of insolvency. We invested a sizable chunk of money, and gave it guidance on how to transition from ARM 6 to 7 to 9. ARM is alive today because of that, and the ARM 9 is still in 100â€™s of millions of products. And we also worked with DEC to create the StrongARM processor family, which became XScale at Intel, then went to Marvel, and also bootstrapped Atom, and, andâ€¦
The Newton needed non-volatile storage. Disks were immense, expensive and power-hungry. 2-1/2â€ť disk? Didnâ€™t exist. Â 3-1/2â€ť was small. The only remotely cost-effective technology was called NAND flash, which was fundamentally incompatible with program execution, and nightmarish for data storage/retrieval, and unbelievably expensive per bit. I think the early Newtons were 8 Mbytes? (thatâ€™s mega not gigaâ€¦). The team figured out how to make that work. Yep â€“ that was the first use of Toshiba NAND for program/data. (Iâ€™ve been playing with flash for storage since then.)
Then some more interesting thingsâ€¦
I wired the Apple campus with wireless LAN base stations (it would be 6 years until Wifi, and 802.11 wasnâ€™t even dreamt up yet) and built the wireless LAN receivers into Newtons, gave them to the Apple execs and set up their mail to be forwarded. You couldnâ€™t even do that on laptops. We could be anywhere in the campus and instantly receive and send emails. More â€“ we could browse the (rudimentary) web. I also worked with RIM (yea â€“ Research In Motion â€“ Blackberry) and Metricom to use their wireless wide area net technology to give Newtons access to email and the Web anywhere in the Bay Area. Quite a few times I was driving to meetings, wasnâ€™t sure where to go, so pulled over and looked up the meeting in my Newton calendar, then checked the address on my browser with MapQuest. 1995. Sound familiar?
We also spent time with FedEx pitching it on the idea of a Newton-based tablet to manage inventory (integrated bar code scanner), accept signatures on screen with tablet/pen (even the upside down thing to hand it to the customer), show route maps, and cellularly send all that info back and forth for live tracking. FedEx was stunned by the concept. Sound familiar? I still have the proposal book with industrial designs in my garage. Yes, another Silicon Valley garage. Hereâ€™s what it rolled out 10 years laterâ€¦ which is ultimately pretty similar to our proposal.
And donâ€™t forget Object Programming. (You remember when OOPS was a high-tech term?) Iâ€™m not really a software guy â€“ just not my thing â€“ but I loved programming on the Newton. In 10 minutes you could actually bang out a useful, great-looking program. Personally, I think the world would have been way better off if those object libraries had been folded into the Java object library. Even so, I get a nostalgic feel when I do iOS programming.
I even built a one-off proto that had cellphone guts inside the plastic of the Newton. (OK â€“ it was chunky, but the smallest phones at the time were HUGE). I could make phone calls from the contacts or calendar or emails, send and receive SMS messages, and rudimentary MMS messages before there was such a thing â€“ used just like a very overweight iPhone (OK â€“ more like the big Samsung galaxy phones). I could even, in a pinch, do data over the GSM network â€“ email, web, etc. It was around that time Nokia came calling and asked about our UI, our OS, our ability to used data over the GSM networkâ€¦ Those talks fell apart, but it was serious enough I made trips to Nokiaâ€™s mothership in Helsinki and Tampere a few times. (Thatâ€™s north even for a Canadian boyâ€¦)
And then years later I got a phone call from one of the key people at Apple â€“ Mike Culbert (who, sadly, recently passed away) â€“ to ask about cellular/baseband chipsets and solutions. He knew I knew the technology. I introduced him to my friends at Infineon (now Intel Mobile) for a discussion on a mystery projectâ€¦ Those parts ended up in the iPhone. A lot of the same people and technology, just way more advancedâ€¦
iPad? Sure. A lot of the same people were involved in a Newton that never saw the light of day. The BIC. Here it is with the iPad. Again â€“ 15 years apart.
And you remember the $100 laptop (OLPC?). As a founding board member, I brought an eMate kids Newton laptop to show the team early on. And of course the debate on disk vs. flash followed the same path as it had in Newton. Â Here they are together, separated by more than 10 years. And then of course, OLPC has direct genetic parentage of netbooks, which then lead to Ultrabooksâ€¦ (Did you know at one point Apple was considering joining OLPC and offering Darwin/OSX as the OS? Didnâ€™t last long.)
And then there are the people. Off the top of my head there were founders or key movers of Palm, Xbox, Kindle, Hotmail, Yahoo,Â Netscape, Android, WebTV (think most set-top boxes), Danger phone (you remember the sidekick?), Evernote, Mercedes research and a bunch of others. And some friends who became well-known VCs.Â And I still have a lot of super-talented friends from that time, many of whom are still at Apple.
Sometimes things that donâ€™t seem very significant have profound follow-on consequences. I think we need to remember that as engineers and technologists. We donâ€™t see the sometimes immense ripples in society from our work â€“ even years later. Today weâ€™re planting the seeds for all those great things in the future. I admit, the Newton was a failure, but oh â€“ you could smell the future and get a tantalizing hint of what it would be. Remember â€“ weâ€™re talking 1993 here.
Tags: 802.11, Android, Apple, Apple II, ARM, BIC, Blackberry, Darwin, DEC, eMate, Evernote, FedEx, FusionIO, Hotmail, HP, Intel, iPad, iPhone, Kindle, Marvel, Mercedes, Metricom, Mike Culbert, MMS, Netscape, Newton, Nokia, object programming, OLPC, Palm, Power Mac, PowerPC, Research in Motion, Robotron, Shane Robison, SMS, StrongARM, Toshiba, Ultrabook, Web TV, Wifi, Xbox, XScale, Yahoo