Tag Archives: Mobile Hardware

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.

Mobile Devices, Larger RAM, Multi-level caches, and Multi-core chips

As with everyone else on the market creating these devices, it occurs to me that as mobile devices contain more and more memory, e.g. 1 GB RAM on the Samsung Galaxy S III and Apple iPhone 5 as well as adding CPU cores, especially with touchscreen keys  and gestures, as well as ‘core or bundled applications’, it IS increasingly important to manage memory in mobile systems the way desktop or server systems manage memory. See Multi-level cache and Multi-core chips in the Wikipedia article CPU cache as two levels of complexity in working with expanding CPU and RAM sets.  A person is already able to create delays in touch typing in these cool new devices as they have several to many applications running in parallel processing data. Beyond expanding the capacity of these devices, CPU and memory management has to be a key factor in maintaining the stability of these devices. Maybe this is already implement although not transparent in the specifications I have seen.  Although at present, not as important, or glitzy in marketing literature to sell more devices, or currently negligible to the non-power user, it will become increasing transparent.  At this stage, we are just ‘throwing bodies’ at the problem, i.e. adding more CPU and Memory capacity.