Showing posts with label sms. Show all posts
Showing posts with label sms. Show all posts

Thursday, June 10, 2010

TCS Text-Messaging (SMS) Patent - who is affected?


It seems strange to me that there is so little public discussion about the rather sweeping SMS patent enforcement campaign by Telecommunication Systems, Inc..

A little over a year ago, Telecommunications Systems (TCS) and their attorneys started sending out letters to SMS service providers and their clients across the country. TCS claimed that they were infringing on the “Smith” patents (US Patent #'s 6,891,811 and 7,355,990) that cover MO (mobile originated) SMS application-to-person (A2P) services.

I was curious so I downloaded both patents and spent a day going through them. The claim is that many SMS service providers are infringing on the patents because their services enable a person to send an SMS message to an application and receive a response. Pretty basic.

In a nutshell, the general scenario is:

  1. A cell phone subscriber sends an MO text message to a short code (its doesn't have to be a short code, but this is where TCS appears to be focusing)

  2. A "gateway" server receives the text message, inserts it into an HTTP request, and sends it to an application server over the internet

  3. The application server replies via HTTP with some piece of information

  4. The gateway server inserts the piece of information into a text message and sends it back to the cell phone

The key elements are that A) the mobile originated (MO) SMS must be inserted into an HTTP request, and B) the HTTP response must in turn be inserted into a mobile terminated (MT) SMS message and sent back to the cell phone, thus establishing a two-way communication.

There is some debate as to whether or not "prior art" exists bringing into question the validity of the patent. The most compelling case seems to be from Kannel.org, the open source SMS gateway provider. Kannel states “This technology has been Open-Source since at least 1999 and there is plenty of documentation to prove it publicly on Kannel.org.”

Nevertheless, TCS does have a registered patent with USPTO and they can and will attempt to enforce it. All technology firms using SMS communications should review their services in light of these patents and determine if they are at risk of an infringement claim.

For more information on the patent, industry comments, etc., there is a great article on mobilemarketer.com.


Steve

Thursday, April 15, 2010

Text Alerts – The Right Stuff

I was packing lunch for my son this morning when I received an unexpected text-message (not many people text me at 8am).

“Your auto policy is scheduled to be cancelled...”. It was from Progressive Direct, my insurance provider.

Hmmm...I thought I paid that. I went online and soon found that I had forgotten to pay the increased premium after adding a new vehicle to the policy. The policy would be canceled in 5 days if payment was not made. With a click of button I took care of it.

Progressive had sent email and letters to remind me, but with the ever increasing volume of both junk email and post, these communications fell through the cracks. But my text-message alert “safety net” saved the day.

I don't want to receive text-message alerts with news, weather, horoscopes, etc.*(see exception below). This information I get through other channels, and those channels are flooded with information every waking hour, so I do want text alerts when something important and time-sensitive requires action.

Instead of using text-messaging for mission critical alerts a lot of companies have resorted to the robo-callers. I get these calls sometimes, but they don't register in the same way. I'm not sure about you, but I only answer calls from unknown phone numbers when I'm in for a little grab-bag distraction. Sometimes these robots leave messages, sometimes they don't. It never seems really important.

For full disclosure, I originally signed up for text alerts from Progressive a few months ago when I wanted to test their system. Unwired Appeal provides the text-messaging infrastructure and database management for their service and I wanted to see how it worked.

This morning I found out.

-Steve Nye

*the one exception is surfing alerts - 365 days a year I want to know when there are triple overheads at Good Harbor Beach - now that's an actionable alert.

Wednesday, March 31, 2010

"This is twilio"

Text the word TWILIO to 617-744-9926 and you will receive a simple reply - “This is twilio”. At first glance this is a basic SMS auto-reply service, but underneath it may signal a major shift in SMS service provision in the USA.

People have been talking about twilio's new SMS service over the past month, so I decided I should check it out. Last week we started up a UA account and secured a local twilio number. Out of curiosity we performed a carrier lookup on the number and found that it is registered to Bandwidth.com, a VoIP service provider and national CLEC. Next we used twilio's API to connect the number to our mobile application platform and now we have a full suite of interactive SMS services running over a standard 10-digit phone number (aka long-code).

So why is this important or interesting? Because it gives people the ability to deploy a commercial SMS application or service without having to secure a short code! As I cited in an earlier post on vanity short codes, a dedicated short code costs $500-$1,000 per month just for the lease fee. Add on top of that the aggregator and service provider fees and the costs quickly mount. Not to mention that it takes 8-10 weeks to provision a new short code across the carrier networks.

Before using twilio for SMS services though, people should also take into account a couple of disadvantages compared to short code based services. First, the cost of messaging is most likely higher than when using a short code service (twilio currently charges 3cents per incoming/outgoing text-message). Second, the throughput is throttled to 1 message per second, where on a short code the throughput usually starts at around 5 messages p/s and goes up from there.

Shared short codes provide another alternative, but pricing for keyword routing is not exactly inexpensive, and there is always a possibility that the carriers will shut down a shared short code if one of the services is not in compliance (see recent case with Clickatel)

Will the carriers also try to disconnect twilio's SMS services? I am not an expert on the telecommunications regulations involved here, but I think it might land the carriers in hot water with the FCC if they tried.

-Steve Nye