9.7 Mobile Content Management


The data related to mobile applications can be voice, video, images, charts, and text. Therefore, it is
appropriately referred to as "content" rather than data.
   
Mobile contents have three separate challenges: sourcing of contents, ensuring their secure storage,
and provisioning or "mining" of contents by applications and services.



Figure 9-7: Mobile contents: provision and consumption based on networks.





9.7 Mobile Content Management


Content providers comprise not only the organizational providers but also individual users who give
information through their mobile devices as well as, many a times unwittingly, their locations.
   
The consumers include users as well as other mobile businesses that rely on the contents sent by the
provider.
   
The movement of contents depends on the availability of networks that they may belong to an entirely
different business with which the transitioning business may have to partner.
   
The foci of mobile contents continue to be location independence and personalization.
   
Real-time updating and sharing of contents takes place for multiple applications that use a multitude of
databases such as a CMS.





9.7 Mobile Content Management




Figure 9-8: Mapping Mobile applications to a combination of contents.





9.7 Mobile Content Management


CMSs, as shown in Figure 9-8, could themselves be residing in a variety of locations, such as internal
networks, the Internet, and also specific mobile databases.
   
The many-to-many mapping between applications and databases leads to issues regarding data
integrity, as multiple updates can occur simultaneously from mobile users in real-time.
   
For example, the moment the user moves his or her location, the location-specific information
(e.g., the location itself) of the source changes.
   
Mobile applications that use location specific information need to handle not only the conflicts resulting
from multiple updates but also identify-in the first place-that there is a conflict even when the sources of data are at two different locations.
   
Mobile database architectures need to reconcile the movement of the client especially when there are
multiple entries in a database by one client who is moving.





9.7 Mobile Content Management


Further challenges of mobile database architectures are that they have to handle the randomness of
user connections, ensure the reliability of connections, and maintain the progressive storage and retrieval of data as the applications are executed.