Amazon Integrates Twitter

It increasingly looks as though Twitter's business model will rely, in large part, on marketing services of various types.

A recent study by professors at Penn State University found that 20 percent of tweets contain requests for product information or responses to the requests, says Jim Jansen, associate professor of information science and technology in the College of Information Sciences and Technology at Penn State.

Separately, Amazon.com has introduced a new feature that allows Amazon Associate members to broadcast links to Amazon products via their Twitter accounts.

Amazon Associates is the partner program the company uses as part of its affiliate advertising programs, allowing customers to make money advertising Amazon products.

Associates can now simply click a link in the toolbar to send a link and text to Twitter as part of their shopping and selling experience. Amazon gets a sale, Twitter gets traffic, and the associate gets revenue share.

Smartphones are Changing the Wi-Fi Hotspot Business

Smartphones are changing the nature of the hotspot business, it now appears. Originally envisioned as a way to provide "outside the home" and "outside the office" connections for laptop and notebook PC users, hotspots now are becoming important sources of broadband connections for smartphones.

One example: iPass, which used to focus on managing PC authentication processes for traveling enterprise workers, now finds it is focusing more attention on managing authentication processes for enterprise smartphones, says Rick Bilodeau iPass VP.

"Smartphones are the new thing," he says. "Now it is smartphones and Blackberries." The software is available for BlackBerry, Symbian and iPhone at the moment, and iPass is watching the Android, though it hasn't seen enterprise demand for that device yet.

As a firm that manages broadband access for hundreds of Fortune 2000 companies, iPass has to manage connections created on hundreds of global networks, but now scores of smartphone devices as well.

To make that process easier, it created an "Open Device Framework," a standardized interface to iPass client software that allows enterprises to write their own XML scripts for the specific dongles, phones and other devices they want to support.

The company also now preconfigures Mi-Fi routers, loading SSID information directly into the boxes before they are delivered to their users, for example. The iPass log-on software also can be preloaded. "We're first to do this, we think," says Bilodeau.

ODF is available now and the Mi-Fi featuers will be available in December 2009, he says.

BlackBerry and iPhone Users are Different, Just Not Wildly So

BlackBerry users are different from iPhone users, a new study by Retrevo Gadgetology suggests. Some of the differences are amusing, perhaps intentionally so, as the questions asked of younger BlackBerry and iPhone users included some that observers might find frivolous, or intended to evoke humorous responses.

Apple iPhone say they find cool gadgets, “most attractive,” about a person, in fact, three times more than they find a college degree attractive.

BlackBerry owners think a college degree is more attractive than the mobile device they use.

About 34 percent of iPhone owners and 29 percent of BlackBerry owners think old gadgets on a potential partner are a turn off. Some 33 percent of iPhone owners say they have broken up with someone  using text messaging, compared to 22 percent of BlackBerry users.

A quarter of iPhone users say they have broken off a relationship because their partner spent too much time on their mobile, compared to 17 percent of BlackBerry users.

The Retrevo Gadgetology report surveyed 445 iPhone and BlackBerry owners distributed across gender, age, income and location in the United States.

"Surprising" AT&T Stance on Net Neutrality?

Some people might be shocked to learn that AT&T complies with existing Federal Communications Commission rules. Some people might be shocked to learn that AT&T actually already agrees that "best effort" Internet services ought to treat every packet the same as every other.

“We use the principle of ‘us on us,’” says AT&T  CTO John Donovan. “If we take an external developer and ourselves, we should not be advantaged in how long it takes or how much expertise is required."

"I don’t think it needs to be that complicated," he says. Does any application run by any third party work as well on the network as an AT&T-provided application?

"Outside applications need to be on an equal footing with our own applications," Donovan says.

But that's part of the problem with net neutrality. It is very hard to define and covers a range of business discrimination issues, network management and performance practices as well as potential future services that consumers might very well want to buy, that provide value precisely because they allow users to specify which of their applications take priority when the network is congested.

As a working definition, net neutrality is the idea that ISPs cannot "discriminate" between packets based on the owner or sender of packets, or on the type of lawful application, or block lawful packets.

The latter principle already applies to fixed broadband access connections, and the new change might be the extension of such rules to wireless providers. What is "new" in the current net neutrality debate is that concept that no packet can be afforded expedited handling, compared to another.

At some level, this is common sense. One wouldn't want video packets or voice packets sold by a third party to be disadvantaged, compared to video packets sold by the Internet access provider, for example.

But that isn't the issue in the current round of discussions and the possible FCC rulemaking. The issue is more an issue of  whether "affirmative" packet handling, as opposed to "negative" packet handling, will be lawful in the future.

"Negative" packet handling is sort of a "thou shalt not" approach: application providers should have a reasonable expectation that their best-effort Internet traffic will be handled the same way as any other application provider's traffic is treated. So ISPs "shalt not" provide any quality-of-experience advantage for their own application bits, as compared to any other bits delivered over the network.

All that sounds fair and reasonable, and in fact ISPs (after a few notable cases of interference), have concluded it is not worth the public outrage to block or delay any packets to heavy users, even when networks are congested, for the purpose of maintaining overall user experience for all the other users.

But there are several issues here. Good public policy would forbid business discrimination, a situation where any ISP could attempt to favor its own applications over those provided by its competitors. Back in the "old days," an example might have been a refusal by one telephone company to deliver calls from a rival.

But the network neutrality debate is far more complicated than that. There is a broad area where network management policies designed to maintain performance might be construed as business discrimination, even when the purpose is simply to protect 95 percent of users from heavy demand created by five percent of users.

Under heavy load, real-time applications such as video and voice suffer the most. So either end users might want, or ISPs might prefer, to give priority to those sorts of applications, at peak load, and slow down packets less sensitive to delay.

The problem with crudely-crafted net neutrality rules is that they might make illegal such efforts to maintain overall network performance for most applications and most users. One can hope that will not be the result, but it remains a danger.

The other issue is creation of new services or applications that can take advantage of expedited handling. Users might want their video or voice packets to have highest priority when there is network congestion. Crude net neutrality rules might make that impossible. But one can hope policymakers will take that sort of thing into consideration.

Net neutrality is a very-complicated issue with multiple facets. Ironically, end users might, in some cases, actually want packet discrimination.

More U.K. Mobile than Fixed Broadband Users in 2011?

More people will use mobile broadband rather than fixed line broadband by 2011, mobileSquared predicts. It's the sort of shocking prediction that makes for a great headline, but also is misleading. The forecast, for the U.K. market, might lead one to conclude that users are disconnecting fixed broadband lines and using mobile instead.

But that is not what the forecast assumes. Rather, it primarily assumes continued growth of smartphone connections.

By 2011 the number of active 3G "smartphone" type devices in the UK will be 36.3 million. There also will be 6.4 million dongles and embedded devices in use, taking the total number of mobile broadband connections to 42.7 million compared to a base of fixed broadband connections of 42.5 million, mobile Squared projects.

To be sure, over time there will be more Internet access occuring from broadband-capable smartphones.
The firm estimates that between one percent and 10 percent of enterprise Internet traffic is already being generated from a mobile device, for example.

But most observers, and most users, likely would say that mobile broadband and fixed broadband are complementary, more than substitutes.

That noted, the application profile for mobile broadband likely will be distinctive. “Mobile will become the primary access point for brands and businesses communicating with its consumers within two years,” says Nick Lane, mobileSquared chief analyst. “Mobile is always-on, and the average user carries their device for an average of 16 hours a day. So if a company or brand is not already considering how to use mobile, then they need to because their customers are.”

As the typical mobile "phone" becomes a multi-purpose broadband device, it will be used for Internet applications. That is not to say the typical smartphone will replace a PC, or a fixed broadband connection. The application profile and mode of use will start to overlap. But each mode will retain key advantages for the bulk of usage. People will talk more on their mobile phones than on their PCs.

They will engage in research, document, calculation or process intensive operations, plus most long-form TV, on a PC or a notebook equipped for broadband access. But people will rely increasingly on their mobiles for social networking updates, location-related apps, real-time information and brief entertainment episodes, and sometimes for long-form video.

The point is that mobile broadband now consists of two distinct segments: smartphones and PC dongles. And while both overlap at times with fixed broadband, they are distinct. Wireless broadband used to connect PCs generally is a complement to fixed broadband access, not a substitute, though that will happen at times.

So the mobileSqured forecast, which essentially lumps all smartphone data accounts with PC dongle accounts to reach the conclusion that mobile broadband will be a bigger business than fixed broadband, is correct in one sense, but wrong in another. In fact, all forms of broadband access are increasing.

Order of Magnitude Increase in Mobile Bandwidth by 2015

U.S. mobile carrier traffic reach 724 TBytes per month in 2015, up from 15 TB per month in 2009, says Coda Research Consultancy, an overall compound annual growth rate of 90 percent. As you might expect, video is behind the sharp rise, growing 104 percent.

(click image for larger view)

In fact, by 2015, video is forecast to represent about two thirds of all traffic, or 459 TB a month, Coda Research says.

That could be a problem. Sprint and Clearwire, for example, argue their new WiMAX networks will provide three times to five times the bandwidth of 3G networks. That's all well and good, but this forecast suggests aggregate demand will grow 10 times from present levels.

Several issues: is there enough spectrum to handle all this growth? What is the cost of upgrading facilities, even if there is enough spectrum? Is there any video revenue model that pays for the investments? Will the mobile regulatory framework provide incentives or disincentives for investment?

Those are the big challenges. But the report has other nuggets for some parts of the mobile ecosystem.

Handsets will drive 68 percent of mobile carrier traffic by 2015, while netbooks will represent 14 percent.
Coda also estimates that mobile ad revenues will total $5.05 billion in 2015.

By 2015, mobile data revenue will grow to 47 percent of mobile service provider revenues, while voice generates 53 percent of revenue. This last prediction is important, as it suggests how and when mobile service providers will cope with the ultimate shift away from mobile voice business models.

How Not to Sell Hosted VoIP to Smaller Businesses

The single biggest mistake retail providers make when trying to sell hosted IP telephony to small and mid-sized businesses is that salespeople start with features, when they should start by reassuring buyers that “it is a reliable phone system,” Savatar VP Mike Ahearn told an audience of small telcos and cable companies attending a MetaSwitch marketing seminar.

The sales pitch has to begin with “it’s a high-quality phone system that is reliable and lets you keep your phone number,” says Chris Carabello, Meta Switch marketing director. In fact, establishing this lead proposition is so important retail sales personnel should establish that fact even before going to the “it will save you money” pitch.

Only after those two positioning efforts should sales personnel then add that hosted IP telephony “makes your life simpler.” The very last thing that should be discussed is that IP telephony offers new features.

And even then, when working with small business customers, even the discussion of new features should focus on a few new features that might appeal to the particular prospect.

That often is the reverse of the pitch made by many sales people, who lead with features first, says Carabello. The key message sometimes occurs at the very end of a discussion, but it needs to be delivered right up front, he adds.

It might seem unnecessary to emphasize that the product is “a managed, hosted IP telephony service that allows you to make and receive calls on IP phones or your computer,” but potential buyers are being asked to make a change in behavior that automatically raises the question of how well it will work.

And though there is greater understanding now that hosted IP telephony actually works, possibly 22 percent of potential buyers continue to think VoIP suffers from major quality of service issues, says Ahearn. As many as 28 percent to 32 percent of potential buyers with 100 or fewer employees might believe that, so take the issue head on, right away, he adds.

The important implication is that every prospect has to be reassured, right up front, that “it works.” Conversely, “cost savings” are generally seen as an IP telephony value.

And though hosted IP telephony obviously provides a path to selling many other services that could range from Web hosting to email and data services, “make the hosted telephony sale first, then up-sell later,” suggests Carabello.

The generic pitch should begin with the notion that hosted IP telephony “is an easy to manage phone system that will save money and help you run your business more efficiently,” says Ahearn.

Only after that is established should the salesperson move to the fact that it uses the Internet connection to make calls. And since most small businesses buy on the basis of a basic “cost per employee per month,” emphasize that hosted IP telephony offers a lower cost per user per month than the existing solution.

But there is one prevalent fact that suggests a simple SIP trunking offer will resonate with small businesses who already have invested in IP PBX gear. Ahearn points out that the trunk-to-phone ratio for smaller businesses is pretty close to 1:1. But an IP phone system really does quite well with a 4:1 concentration ratio.

Firms with four to seven employees report buying one to 1.2 trunk lines for every phone in use. Firms with eight to 10 employees report having 0.6 to 0.7 trunk lines for every phone in service.

Organizations with 11 to 20 employees report having 0.5 to 0.6 trunk lines for every phone. Firms with 20 or more employees say they have about 0.4 trunk lines for every phone.

The implications are fairly clear. Organizations that need to support between a few trunks and 14 PBX trunks are vastly over-provisioning trunk capacity. The typical organization using IP phones can get along fine with a 4:1 ratio of phones to trunks.

For a firm supporting six phones, and buying six trunks, an alternative SIP trunk strategy could save as much as $1,915 a year.

An organization requiring 14 trunks could save $2,205 a year by swapping SIP trunks with a 4:1 concentration ratio for PRI trunks that are provisioned at a 0.4 concentration ratio of phones to trunks.

The clear implication is that a small organization can save money immediately by replacing PBX trunks with SIP trunks.