Tag Archives: Wireless Carriers

Wireless Data Plans, Packet Protocols, Granular Reporting

6 Days Left of my Billing Cycle: 0.3 GB Left (out of 10 GB)

Are you kidding me?! I login to AT&T’s Wireless, myAT&T portal to dive into where is all our data going?  I am able to see quite easily what mobile phone number is eating up our plan, but no additional granular information.  AT&T has a great site with lots of good information to help their customers manage their plans.

However, it seems wireless providers leave it up to the handset manufacturers to interpret the usage of the phones. Makes some sense on an individual level, but as multi line / family wireless plans continue to evolve, the growth of wireless services management portals should be spent on providing consumers transparency into their usage, aggregated and granular.

Packets of [wireless] data, bits of information, have a ‘signature’ as they travel through the Internet ether.  Packet protocol defines where the data/information originates, and it’s destination, as well as any other required information by the application sending / receiving the data.  Wireless carriers’, services management portal should allow consumers to slice and drill down to see how data is being used. For example,

Wireless plans of 10 GB is not a lot with teenagers.  You may want to target areas to curtail usage so you aren’t ‘bleeding data’.  At this time, there is not enough transparency on how data is being used from the wireless provider’s usage platform. The provider should be able to parse data packets to quantify how data is being used, and provide reports, e.g.

June 2015 Snapshot for 212-555-1212

231 songs streamed from ABC, N MB; 23 videos watched on YouTube, 2.3 GB; 34 streamed videos from Netflix, 3.2 GB; 345 emails downloaded, 90 MB;

DAM on wireless services:  Application data packet objects may have visibility through Digital Asset Management (DAM), all objects that can be managed, phone calls to chats from Facebook (except where encrypted).

Now take a piece of paper, write privacy on it, then rip it in half and toss it in the garbage.

Where is My .fon Generic Top-Level Domain (gTLD)? .tel doesn’t cut it.

Every phone number in the world should have an IP address and a domain name associated with it, hence the gTLD proposal for .fon for every phone number.  Things like us.emergency.fon = 911 would be possible.   In addition, a group of cloud vendors would be awarded management of sections of these domains, which may be aligned to the phone number carrier, or if they don’t have the capability, they can ‘sell’ or ‘lease’ out the resource to a third party Internet Provider and Cloud Vendor, similar to the way we sell mortgages, or the mortgage companies sell off our mortgage.

Not only would the service of management of the domain name correlated to an IP address and a phone number, but each IP would have a virtual image managed in the cloud, which could provide to the consumer, cloud storage for storing public and private documents, as well as a ‘home page’, cloud computing cycles for the consumers public and private applications, as well as enabling the services: VoIP, text and email messaging.

These services may be provided free for some basic subset, and the extended subset would charge the customer, e.g. for additional cloud storage space.  In addition, the client may choose to move their service to another provider.  A public index.html home page, and a private index.html home page could be created, so a person may design their own portal, e.g. containing widgets, frequently used numbers, news widgets, etc.  These pages scale downward to a mobile device or up to a high resolution image, e.g. addressable HD television.