NO justification for the high monthly cellphone bill

I recently visited a local Verizon store to check out a new phone. Using the display model’s browser ( chrome or webkit ) i did some surfing and was really thrilled with the speed and clarity of the large screen. Then i inquired about the price for the unlimited plan –  at $120.00 per month Verizon’s unlimited plan represents an increase of $50.00  in comparison to my current, unlimited plan on a competitors network using an unlocked Nexus One. Exiting the store, resigned to another 6 months of   old n crappy phone boredom , without future prospects for sitting  over latte’s in the local coffee shops, buzzing about my rad technology gizmos, I sulked my way home.

Shuffling along 24th st. in the mission, still annoyed by the economic conundrum that 50 years along the downward slope of Moore’s law and the associated low-price expectations , somehow my cell phone bill continues on its gaseous ascent  into the stratosphere. Contemplating cracks in the sidewalk and my hemorrhaging bills, i stopped at 24th and Treat and looked up to see this new type of wireless tower antennae that is rolling out to phone poles across my neighborhood. Although wireless carriers have a point that crushing volumes of mobile app download data threaten network capacity and that someone has to pay fees supporting the investment in these new network technologies, I gazed at the pole loaded with network amplifiers topped by the new antennae and wondered about  the economics behind this new capital equipment and its bearing on my monthly phone bill.

What does it cost? what revenue could it generate?

$17,000.00 per telephone pole adds 150MB per second of new, network capacity  

IMO,  $7000.00 covers the hardware on the pole, including the amplifiers that push the digital signals received at the pole back to a central-office over a fiber, ‘back-haul’ link where the radio signals transit other hardware used for integrating phone radio signals with the rest of the telephone network. Add labor costs and incremental hardware costs in the phone company CO and you get to about $17,000 per pole. For example, in San Francisco, there is a million dollar project underway rolling out 60 of these new antennae to existing poles. While back-haul can be fiendishly expensive under some network scenarios, for the wireless carriers using phone poles in urban areas, existing fiber already connects the poles to the network backbone. There’s no need for microwave backhaul links, no need to dig million dollar per mile trenches for fiber lines, and no need to retrofit T1 technology that is still conveying lots of backhaul traffic across suburban and rural network segments.

Comparing radio signals to network packets, figuring out how volumes of data information transit a radio signal is not an easy process. The math used to do a low-level units translation for a comparison of radio antennae capacity to traditional, TCP  units of measure is best left to real geeks who will be all over this snip: Image 

 FWIW I found an alternative calculation in the radio network math for dummies in this chart where the far right colum displays the all important measure for ‘bits per second per Hertz’. Scrolling to the line in the table for  HSPDA the bandwidth is listed as 8.44 b/s/Hz. The maximum possible bits  type bandwidth per second per 1 Hertz of radio spectrum is 8 bits. Converted from bits-to-Bytes, multiplied times the corresponding total radio frequency amount advertised on the link for the antennae’s  spec sheet  ( 154/460 MHz ) this comes to approximately 150 MegaBytes per second of computer type bandwidth available per tower. When your talking or playing AngryBirds on your iPhone, 150 MBs  is a lot of bandwidth.

What cell phone subscriber revenue is represented by 150 MBs of capacity at the pole?

150 MBs of new bandwidth = $3.00 per Second in Customer Revenue

Capacity of 150 Megabytes per second on just one of these towers, theoretically  gets you 15,000 simultaneous phone calls (voice codec G.711 @ 64Kbs). Alternatively, using average 3G download rate of 5 Mbs, 100 simultaneous data downloads could take place on the single tower. Here is a list of cell phone plans. And data only plans are covered here. Reviewing these plans/prices, Its a little like pricing a rental car or an airline seat. Its safe to say that an extra 1 Gigabyte of monthly data priced at $20 by Verizon equates to the $3.00 per second figure mentioned above. From $3.00 per second, you get to a monthly total of  $7,776,000.00. If they could saturate that one tower completely peddling every single Byte of its capacity for the going consumer rate, the tower generates annual revenue over $93 Million.

That figure is ridiculous. What about the real world?

Under realistic network operating conditions, the network has to be really smart and really robust and does not perform at or anywhere near this theoretical max. Mobile handsets require that towers handoff connections to neighboring towers as the customer with the phone moves along the road/subway. Accommodation must be made for bursts of calls at 6PM on a busy friday as everyone leaves work. Legacy methods of communication like 2G have to coexist on the network providing support for older hardware. Dropping from the theoretical to a number representing the real world network still works out to a very nice profit for Verizon. Reducing the operating network load from the maximum theoretical by a factor of 1000 still provides $7000.00 per month of additional revenue on $17,000 investment.

Moore’s Law please… and fewer retail stores… my monthly bill declines?

In order to appreciate the effect of Moore’s law in action exerting what should be downward price pressure on the wireless network , take one more look at figures from that chart, comparing the 7 year period between 2002 (CDMA) and 2009 (LTE). The spectral efficiency of the network increased by a factor of 100 meaning that the power requirements to run the radio antennae on the towers also dropped by a factor of 100. In 7 years, a hundred times as many phone conversations could occur in the same segment of radio spectrum. In 2002, CDMA was capable of Max 0.1720 (fully loaded). By 2009, LTE technology increased spectral efficiency to Max.: 16.32. If a company other than Verizon could figure out the vast opportunity in a business model more focused on low cost radio networks that have realized a 100X efficiency increase in just 7 years and less reliant on marketing and the flashy phone retail stores, that could do wonders for my monthly bill. In the long run its all about moving data on the radio frequency – TCP packets saturating the radio spectrum to a greater degree , mobile handsets running VOIP apps pushing Megabytes of data across the wireless space that is just another network. At this point, im feeling no sympathy for Verizon and their $120.00 a month. 

Youtube audio only – technical

This is in response to a stack exchange post where i was not allowed a response with more than 2 links.

is Android single task or multitasking and multithreading?”

If you want an android app that would allow flexible management of the Youtube streaming protocols in a way that would support selection of just the audio portion of the media stream while discarding the video track, keep an eye on VLC for android. It is still ‘under developement’ but would probably address the ‘audio only’ feature.

From a more technical perspective, it helps to break the issue down into available Youtube network protocols for media streaming RTSP. RTSP specs allow a client to make a request using the DESCRIBE command to which the server responds with an SDP data segment (see details below). Youtube servers can respond in a variety of protocols , sending underlying streams that in turn use a variety of encodings -one for audio, one for video- to transfer the media bits across the network to the client. Over the mobile networks, a feature that goes to youtube in order to receive both audio and video tracks before discarding video while playing only audio is not a good practice because of the heavy network requirement for the unused video stream. You can get around the network inefficiency with some further technical drill-down.

RTSP and SDP standards observed by Youtube would allow a streaming client (android device) to request ONLY the Audio during the Client/Server handshake steps and negotiation steps around the network connection setup that will do the media streaming. In this case, no video would be sent and the android player would be configured on an audio only stream. Some CLI command details and some protocol details on this ‘youtube audio only’ scenario follow.

A youtube, format 1 audio only track for a particular video is available at the following RTSP URI:

rtsp://v8.cache8.c.youtube.com/CigLENy73wIaHwlcw_gs85OUchMYDSANFEgGUgx1c2VyX3VwbG9hZHMM/0/0/0/video.3gp

From the RTSP URI for the entire video (audio track plus video track) , the following CLI expression makes use of 2 media clients openRTSP and mPlayer going to Youtube where it then GETS/PLAYS just the Youtube audio track by requesting only channel=1.

./openRTSP -a rtsp://v8.cache8.c.youtube.com/CigLENy73wIaHwlcw_gs85OUchMYDSANFEgGUgx1c2VyX3VwbG9hZHMM/0/0/0/video.3gp | ./mplayer -cache 8092 - -rawaudio channels=1:rate=8000:samplesize=2:format=0x73616D72 

This CLI expression is further described in a link at the bottom.

Youtube ‘feeds’ describe the available stream formats for any Youtube video, including the RTSP URI’s mentioned above. For a Tech explanation of Youtube streaming formats see the entry for ‘format’ 1,5,6 in the long table.

The following request gets a feed from Youtube that includes the variously formatted RTSP URI’s that are available for that particular video:

http://gdata.youtube.com/feeds/api/users/rowntreerob/uploads?vq=cpST8yz4w1w&prettyprint='true'

The gory details of a connnected RTSP SESSION in which the full SDP description is requested for a particular youtube video so that just the audio track could be streamed/played are here
Key to numbered lines in above link

  • 82 – the RTSP DESCRIBE request
  • 101 – the SDP response
  • 103 – video track’s format
  • 116 – the attributes describing the audio track
  • line 165 – the audio track setup by the player
  • 184 – the audio-only playback
  • 201 – using a separate CLI expression this is playback of a previous download on just the audio track

Nexus and competition over mobile standards

In becoming a hardware merchant, Google will exert greater influence over the emergence of a number of aspects of mobile technology. The ‘Nexus’ phone announcement represents an acceleration of an ongoing mobile strategy – a stepped up effort to prevail in a series of disruptive technology trends in mobile ads, voip, and graphics. Which connection method will be used to get rich media ads to the phone. What runtime display format will be used for displaying ads on the handset. What options will exist for VOIP and for back door calls made over IP and not made on the carriers native networks for switched calls. These are examples of the kinds of things Google wants to be able to influence.

The leading smartphone vendors each push differing standards for the graphics engine that will control the display of rich media ads on phones. Adobe is pushing flex-lite. Apple has its own approach and has been reluctant to adopt anything Flash-like on the iphone. Microsoft’s Silverlight will soon support mobile so that Windows ME and Silverlight will be their closed solution for display.

Google is pushing 2 open standards, svg and HTML 5 in a way that will support the delivery of plain old html with tags for rich media ads handled as SVG. Unlike Silverlight and Flash, SVG does not require another IDE and a compile step to produce the actual media files. Mobile phones would not need anything more than a browser for ad display. No Flex-light plugin or microsoft silverlight plugin. Ad inventory ( rich media ads ) distributed by the major ad networks is currently all Flash . However, Google’s recent AdMob acquisition should allow them to introduce and drive conversion to a new ad format not in wide use today – (Html 5 + SVG). Any handset with an HTML 5 browser will render rich media ads. Google has been working on JavaScript libraries that will fill out the web ecosystem around http, html and svg. Google’s intent may be to more strongly support an open solution for mobile rich media advertising by selling hardware that requires only a browser.

Google’s support for VOIP adoption and for open standards (IP for call connection protocols) is far more disruptive to existing carriers. Consumers will now have the option to buy and use an unlocked phone without a 2 year carrier commitment. This move may serve to turn cell towers into a commodity type of infrastructure rather than a critical part of carriers competitive strategy. If 2 friends each get unlocked phones loaded with the proper software , a carrier contract is not needed in order to make phone calls. VOIP, Skype, SIP client software support a number of different connection scenarios where voice calls occur without going thru the main internals of a carrier network. Some of the Google voice features allow carrier networks to be integrated in a way that may permit outside callers from traditional networks to call a google voice number and to reach the handset via SIP interfaces connecting the last mile of the call via IP protocol. Without a carrier contract, outbound calls to traditional networks can be handled by connecting first to Google voice on IP then bridging to the traditional carrier network. There would no longer be carrier subsidies of the handset purchase. There would no longer be a compelling need for a carrier. An IP connection alone would be sufficient. Gizmo5 offers IP based calling features like forwarding , message handling, SIP binding. With enhancements built on these features, it would be possible for friends to call one another using email addresses, URLs in place of traditional phone numbers. Anything that SIP could bind to the handset IP would be sufficient for making a connection to the phone.

Contrasts between correlation and traditional search

Two very different web-based activities involve traditional content search ( google ) versus automatic delivery of a filtered version of the web, condensed and focused according to your personal interests and preferences – Search versus correlation. This article contrasts the automatic delivery model with search in order to provide an understanding why stream correlation and delivery of matched content is a viable alternative to search.

Automatic delivery of filtered streams of web content, greatly condensed through a process using correlation and matching, is a compelling technique for “bringing the web to you”. Whereas search is “pull”, correlation and matching done by Real Time Matrix is “push”. Like a newspaper thats delivered to your door, edited and reduced in order to retain only those articles that are relevant to your interests, correlation with push is convenient. There is no need for newsstands and generic versions of the paper when you have an alternative for delivery of a version of the same paper condensed in such a way that each item is likely to match your interests? Over the last 2 years RSS has provided a number of technical components that complement the process of web delivery of news. Under the covers, RSS is powered by streams, rivers of data more mobile and more flexible than the analogous web pages utilized by search engines.

The remainder of the post describes stream processing for web content as it has been adopted by Real Time Matrix and in doing so, contrasts traditional search with matching and correlation performed on “live” data underlying the river of new web pages, as those pages are posted to the web. For the purpose of making a general comparison, without getting too involved in low-level technical details, the web can be represented by a freeway lined with a series of billboards. To use an example, the New York Times has a series of bill boards representing sections of the news. The NYT Sports Section can be percieived as a billboard represented by a deep stack of pages – a multi page billboard in which every sports article is represented by a billboard page, organized in LIFO order so that the “hot off the press” articles float to the top of the page stack. In will be of particular interest to examine search and correlation techniques as theyrelate to a single, new page as it is “posted” to the web.

Search builds an Index for the new page

The existence of an entry for the new page of content within a search index is a prerequisite. Before the new articles page is indexed, before that new index gets added back to existing indices for NYT Sports, noone can see the new page via search. Index building and pre-processing is not religious about “fresh content” and whats sits at the top of the page stack in the billboard. In building and refreshing its indices, Google employs crawlers on 10s of thousands of servers. The Crawlers act as robots that know the location of every billboard and how to schedule re-visits in order to pick up changes posted to each billboard. Reoccurring visits follow their own schedule, determined by Google algorythms that may miss by weeks the exact time of posting of freshest page. When they visit a site like NYT Sports,

Crawlers focus on the HTML formats of data in a page ( more on HTML data formats and RSS data formats below). Any new page that has appeared since the last visit gets processed by the indexer, links to and from other web pages get analyzed, meta information on the page is read, the page is scanned for key words to be included in an index entry for a new page. Before this new entry can update the main Google search indexes, before the new page can begin showing up among results presented as “hits” pages for web queries, the new index entry needs to be shipped along the freeway to the nearest Google data center where it can be included with other new index entry’s and scheduled for a process that will eventually update the main search indices. After all these pre-processing steps are complete, a sports search could include the new page within the list of search “hits.”

RSS Sample Data , Streaming Data

To understand the streaming data approach, look more closely at the example of a new Sports page article as it is posted to the NYTimes web site. As described above, there are two different data formats that can be used (  html or rss ) to represent the sample page from NYT sports. This html link is the data used by the crawlers described above. Besides this format, there is another data format of the same page that is more mobile, more easily distributed, and more easily exchanged with other cooperating computer systems. The Sports RSS Feed , also from the NYTimes, contains the same articles as the html links, but these articles are organized in a very different data format – see the sample of RSS format data below :

<div> <pre> Bryant Barred for One Game After Hard Hit http://www.nytimes.com/2007/01/31/sports/basketball/31suspended.html?ex=1327899600&en=7ccd90d2e67129e2&ei=5088&partner=rssnyt&emc=rss The N.B.A. has shown little tolerance this season for any action that is illegal and overtly ugly. LIZ ROBBINS http://www.nytimes.com/2007/01/31/sports/basketball/31suspended.html Wed, 31 Jan 2007 01:33:30 EDT</pre></div>

Visualize the data above, drawn from an rss sample with itunes type NameSpace additions, as a stream. Scan each data line starting with <itms:artist> placed in one, long line. Next, animate that one big data line like a ticker-tape so the data scrolls across a given place. A ticker tape is a data stream containing words or items that can be correlated to other patterns. Look closely at the animated version of the sample data above – at some point , you would see the words Jack Johnson. If you were interested in music works by Jack, these 2 words could be found among the ticker stream, “matched” by correlation process on your behalf.

RSS Capabilities , Advantages

In contrast to the static html form of the page used by traditional crawlers, the RSS version of a page is fast and flexible. For the purpose of this example, the stream of rss data mentioned above “flows between” arbitrary source and destination points on the freeway. What does that mean? Mobile stream data, Rss friendly, leverages “Feed-enabled” software from any number of 3rd parties compatible with even more 3rd party device types. Equipped with a “reader” that consumes Rss, my phone can locate itself at a suitable off ramp, “subscribing” to just the data that has been correlated and matched to me, streaming past the off-ramp among a much larger “firehose” of generic data. Infrastructure supporting rss distribution is built into the phone and it just works.

In addition, the Rss form of newly posted content does its own PR. As articles post to the NYTimes sports pages, the Rss format has the ability to inject itself into the syndication infrastructure with an announcement that simply says “I’ve arrived”. That simple statement triggers data flows and complementary filtering or “personalization” of the data in transit. The practical result is that relevant data arrives where it is supposed to go on an intelligent freeway. Again with the aid of ots of 3rd party software supporting announcement pings and the feedMesh, company’s like Technorati, syndic8 respond to the data that was just posted with all sorts of automated, “just arrived” type tools. The discovery method for newly posted Html is very different, involving higher cost and greater latency.

Compared to streaming Rss data, moving immediately out to the interested consumer from the billboard at the same time that the article is posted, traditional search indices can make you wait. You wait after the post while the crawlers are idle for a period of time determined by the algorythms at google. For example, if you have small traffic e-commerce site and you begin offering new categories of merchandise in your on-line catalog, it may be 30 days befor the new category gets picked up by crawlers and added to the indices for your site. NYtimes sports, although larger and of more interest to the dispatchers behind the crawlers, is still going to be affected by considerable latency between standard practice for CMS and newly posted Rss versions of articles calls for a notice of the post and a concurrent flow of data that mimics email. Registered parties and groups of people will be notified immediately after the Rss version of the article arrives on the web.

technorati tags:, , , , ,

Blogged with Flock

Lotus Connections with Web20

As announced in BusinessWeek IBM’s recent enhancements to Lotus Connections validate some Web20 software approaches and may comprise a vanguard in corporate middleware employing  a new stack thats quicker and easier for software developers. Sites like TechCrunch have reported all the details of the Web20 fad among companies whose revenue is considerably smaller than IBM’s 95 billion. If the Elephant is ready to dance once again, there are  lessons for enterprise Software vendors under the covers of the Web20 culture in software development.

The salient points of the Lotus Connections press releases point out things like easier blogs, personal profiles, and autonomous communities as new features employing software practices now the main religion at lots of startups like Flickr and Delicious. Users of these newer web sites take no time at all to grow a new community of 25 or 2500 users (autonomous workgroups), whose members cooperate and interoperate, sharing data, applying tags to the data without assistance from System Administrators or programmers or application owners. Flickr and Delicious support the general proposition that, on the web, songs and pictures can “just find you” based on your interests and on your membership in a group. These “smart network” characteristics come to the enterprise with high value and very low cost.

The trend regarding some of this web20 plumbing is to increasing adoption by the enterprise; a logical consequence could be disruption in some of the technical aspects of the traditional Enterprise middleware stack. Compared to traditional corporate stacks,the Web20 software stacksare lean, present everywhere,  and very easy to deploy. Http and REST are software cornerstones supporting alot of functionality at startups that predates the lotus community announcements. For software developers at these firms,  there are no requirements for dealing with with WebServices Utiliitys,no UDDI, no complicated service endpoint xml schema abstracts. With REST, its  just URL’s, user interaction with those urls, and Httpprotocol. There are no extra libraries for programmers  to download ,no preliminary deployment utility steps to be run or library/repository entries to be maintained. The Web20 stack is better, faster, and way cheaper.

The following section provides business and technology details that support the notion of continued disruption as traditional business process software and work group software  adopts best practices and additional plumbing from web20 practices.

RSS & ATOM  present each worker with “their data”

In the same method that these 2 data formats are heavily used for syndication of web news and  weblogs,   business workgroup documents, selected database fragments can be wrapped or enclosed and then distributed to just the people that need to receive it. The snips of data in the <item>  below show 2 examples :

  • RSS “encloses” a spreadsheet using enclosure
  • RSS “encloses”  some data selected from a database in CDATA

<item>
 <title>The Overnightscape #143 (3/14/05)</title>
 <pubDate>Mon, 14 Mar 2005 09:51:43 GMT</pubDate>
 <enclosure url=”http://xyzcorp.intranet.com/xls/billing/Overnightscape_receipts0143.xls”
    length=”10802740″ type=”application/x-excel”/>

 <category>payable</category>

 <category>unapproved</category>

</item>

<item>
 <title>The Overnightscape #143 (3/14/05)</title>
 <pubDate>Mon, 14 Mar 2005 09:51:43 GMT</pubDate>

 <content:encoded><![CDATA[
      <parameters applicable-location="point1">
         <temperature type='maximum' units="Fahrenheit" time-layout="k-p24h-n7-1">
            <name>Daily Maximum Temperature</name>
            <value>34</value>
            <value>43</value>
            <value>39</value>
            <value>39</value>
            <value>47</value>
            <value>48</value>
            <value>41</value>
         </temperature>
         <temperature type='minimum' units="Fahrenheit" time-layout="k-p24h-n6-2">
            <name>Daily Minimum Temperature</name>
            <value>16</value>
            <value>31</value>
            <value>26</value>
            <value>26</value>
            <value>32</value>
            <value>31</value>
         </temperature>
      </parameters>
   ] ]></content:encoded>

</item>

Enclosed in RSS ,  business data now gets a free ride for a better, faster, cheaper experience. The enclosing RSS stream of data can be routed anywhere using only http and a  network – there is an assumption that the enclosed documents are URL-accessible on a web-server or intranet. Any phone, PDA laptop can get access to the data as easily as these devices access the web. Http plumbing is everywhere and imposes very low admin costs. Atom and RSS are universally recognized formats which means that the only system requirement is to deliver data to the target application. Absolutely no requirement exists to write a UI or to develop user applications to manipulate the data because all kinds of software already exists that processes RSS/Atom and that manuipulates the enclosed data objects according to their mime type. In summary, things i dont need todo:

  • No messaging layer or MOM needed
  • No ESB needed
  • No PUB/SUB framework needed
  • No SOAP  Web/services infrastructure needed
  • No presentation layer or application needed

Document Flow and Notification

Now that i’ve completed my work or updates to the documents that are of interest to my workgroup, i need to signal that im done and that subsequent work by others in the group may commence. Millions of dollars of complex software with functionality mentioned at the above link above has been sold to customers needing to cover this somewhat complex functional requirement. At the risk of oversimplifying things, the Web20 stack is a growing presence with decent capabilities for “eventing and notification” so that when your task is complete, i get an alert and can begin my task. Workflow/document related functions such as Creates, Reads, Updates, and Deletes are covered by REST , and as in the data excerpt above you may update the metadata in the <category> tag to indicate status changes. Those status changes can be picked up by observing or polling the data stream that encloses the document. Although not quite ready for prime, dojo’s comet is utilized in web20 contexts and purports to support http push in an environment where pieces of distributed software components communicate at a low level and with alot of intelligence using nothing more than http.

technorati tags:, ,

Blogged with Flock

Net Neutrality – rolling new revenue without K-Street

Recent developments related to the ATT / SBC merger and the details in the consent decree that was part of FCC approval for the merger shows some movement away from the pipe owners like ATT back in favor of content providers like Google in the Net Neutrality  debate. A single abstention on the 5 member FCC board altered the neutrality dynamic in favor of the grass roots despite the counter argument by the pipe owners that necessary capital improvements make it imperative that they charge content providers like google and apple for all the new videos moving accross the net. Absent the changes that alter the web in the direction of cable TV, the pipe owners predict  capital improvement deficits and rising broadband congestion as bittorrent and itunes tv shows and netflix movies clog the network.

Google exemplifies the enormous valuations attached to content providers who can shake the money tree of sponsored advertising as they deliver applications and content thru the pipes owned by the likes of ATT. The number of page views served directly by Google and also by partners involved in affiliate programs where ad money flows back to google is money tree. The last i saw is that the front-end revenue for google sponsored ads was averaging $1.44 per click. Google disrupted the advertising market by evolving the AdWords marketplace and by extending the equation with web browsers, adding sponsored links to the search results pages served up by google to users trying to find stuff on the web.

Rather than paying K-street lobbys and using leverage in neutrality regulations to come up with rules allowing them to loot the pockets of Google, the pipe owners like ATT ought to be surveying the web advertising markets looking for an innovation of their own in order to print money like google does. For example, instead of looking on in envy at Googles 120 billion market cap and the growth of AdSense, the Pipe owners could be saying “hey i have a money tree of my own because I own the user IP and Im positioned to add the holy grail to that IP – individual user demographics.” Good demographics, added to the activities currently incorporated into Google’s ad words market would probably double the value to advertisors. Was that search on “mortgage insurance” submitted by a 36 year old in Greenwich with income of 450K or was it submitted by an 18 year old finance student at the state university? There is a difference.

When i do a search on a google sponsored site that is using AdSense, the relative value of the Ads that i will see along with my search results is determined by an auction whose market places a value on keywords without knowing anything about my demographic. User at IP 192.0.0.1 submitted a query on “mortgage insurance”. The IP is naked. There is very little in terms of marketing demographic or segmented audience based on age, address, and income associated with that IP address.

For the sake of argument, lets just say that im that 36 year old looking for mortgage products. I have  2 teenagers who are iTunes addicted. ATT is my ISP and they have offered me an opt-in program where i divulge some sensitive personal information that i can control and that allows me or my children  access to a new kind of cookie jar built on the $$$ associated with my demographic data. With the demographic, my click on a sponsored link accompanying the mortgage search is worth $3.50 not $1.44. That is because the DNA of marketers is in demographics and if they know just a little more about the person they are reaching thru AdSense rather than just the IP, they will pay.

Going with the future scenario, say that a partnership among ATT, Google , and iTunes works like this: ATT says that this month , in return for access to my demographic, they will credit my account $15 for free iTunes downloads for my kids. ATT has told Google that AdSense activity placing ads in front of me will be augmented by my demographic and as a result, Googles monthly revenue resulting from my “click” will double. Some of that delta revenue is charged back from Google by ATT. Everybody makes more. iTunes get more action that is subsidized by ATT’s bonus offer to me. So ATT is subsidizing my kids use of iTunes. ATT is collecting some piece of the AdSense money by allowing Google access to the demographic associated with my IP. Google is paying ATT a portion of the delta AdSense revenue.

references:

at&t consent decree

see “net neutrality” pg 9

NetNeutrality by lessig

technorati tags:, , , ,

Blogged with Flock

Reading Lists with state

Although easy to store on the web , and easy to use to  share your feed list,  OPML Reading Lists need new features including server-side, stored, state information and access to a networked valueHolder object type version of readingList state. A reading list user would then be able to seamlessly use any instance of any feedReading client to pick up the feeds encapsulated by specific list exactly where that specific user last left the list.  Lets say that there are 50 new feed items belonging to 10 of my ReadingList’s URLs in the morning. On my laptop at home, i manage to read 10 . Then, in my car on the way to work, via a Reader equipped satellite radio, i listen to 5 more podcaste items before arriving at work where i scan the remaining 35 feed items. This scenario involves 3 clients and 3 separate feedReaders that in today’s world are each capable of subscribing to and downloading all 50 feeds in triplicate. Today, there is no way for these readers to share state, to share the data that progressively updates as i wade through the 50 feeds. What i want is a seamless handoff off an updated awareness of both read and  unread items as my presence shifts among the devices on the way to work. The rest of the post is a discussion what and how for one possible solution that extends reading lists and that adds an app server that can update and hold values of these networked list objects.

If you use reading lists and just 1 client to check for feeds there is no need for new features. That single client would be the only location needed for storage of important meta information regarding the feeds and the delivery of items on those feeds. For any given feed or url in the list, the client knows when it needs to poll,  requesting a pull of new feeds from that url.  As long as you always use the same client the reading list entries are handled correctly regarding last visited  state and with respect to dupes because a single client knows how to avoid duplicate feeds on the url. It can diff the meta data just received against data from older items. Now introduce a 2nd feedReader client by sharing the reading lists on your PC with the reader installed on your phone and see what happens. Everything gets pulled twice. Without access to the same internal state information  used by the first client, the phone has no visibility into what time each url in the list was last requested and no access to meta data like the most recent pubDate on items just pulled by the other client. Nor does it have any information on duplicates. On the phone, you can get your feeds but it will be just as if you are using an email account where you save all mail items on the server while using multiple mail clients. Each client downloads the entire list of mail in the inbox even thou you may have already read the mail.

A shared folder of MyFeeds as I last accessed them , stored server-side where it associates users (myself) and lists (mylist) with a 1 : 1 cardinality is one solultion to the problem. The virtual folder encapsulates client state information like the last time that i read a particular &LT;title> belonging to a feed URL, storing server-side attributes like "last_access_date" on the feed and "has_been_read" on each title in the feed. Any feedReading client on any device has access to the folder and to accurate context covering details on what i last read and when.  All that i have to do to use the reading list in a consistent fashion is get access to the web on a device with a reader capable of accessing this shared folder.

Assume that you have  http://code.google.com/apis/gdata/protocol.html providing "shared folder" features. Look at the Gdata link for "Inserting-a-new-entry". Its focused on the provider and not the consumers of feeds, but it is so close to being a compelling example that some speculation around the fringe of the supported functionality is merited. This is scalable and it supports a full Rest   interface. In the details of the "201 Created" section you can see the xml code excerpt below:

<id>1 </id>

<link rel="edit" xhref="http://example.com/myFeed/1/1/"/>

<updated>2006-01-23T16:26:03-08:00 </updated> 

The link and the id above are pretty close to what you would need to have a uuid on the association between the user (myself) and the <entry.title> where you want to store the attribute "read or unread". Once someone convinces google to extend this initial offering for rss in the GData api, support for the reading list with shared state is done. Any feedReader on any device marks a title to "has-been-read", generating a local event that delegates to a proxy to GData where a POST/UPDATE occurs on the URI and data entry representing the distributed object encapsulating the state of my interaction with the collection of titles that belong to a specific feed. I could switch devices and do a GET to access the shared folder in the state where i left off while i previously was accessing my reading list.