Abstract
The data storage in mobile cloud computing domain is an important subject because of the large amount of data devices can provide. Different kinds of sensors retrieve information and send them to data storages. But the storage location can move even dynamically during their uses. So, these changes must be managed at runtime. In the other part, Android devices are good computers to acquire information and send them to a storage area. These devices are well-known, ergonomic and useful machines sorely used. In this paper, we present a software architecture from Android devices to Cloud storage areas to put down data when the data stores are dynamically moving. The different parts of these distributed applications are built around Android with JSON messages for REST services and moving NoSQL databases in the Google app engine. The exchanges between the cloud and the Android devices use the Google Cloud Messaging (GCM) protocol. Furthermore, even without network access, the saving is made locally in the smartphone. The synchronization with distant databases is automatically made when the network becomes again available.
Highlights
Cloud infrastructure give hardware, data storages, APIs to manage them and so we can develop software for customers to put in it
Data storages, APIs to manage them and so we can develop software for customers to put in it. We can use it as virtual supply and these parts are well known as Infrastructure as a Service (IaaS), Platform as a service (PaaS), Software as a Service (SaaS) [1]
We prove in this paper that we can save data coming from mobile devices to moving databases
Summary
Data storages, APIs to manage them and so we can develop software for customers to put in it. In the context of mobile applications, the Cloud access is a crucial feature It ensures the business data access when the network is available. Our architecture is useful for example, when a user or a device need to obtain many data and store them in data storages Such a solution helps to continue mobile users to keep a shopping session and more generally to manage a working context. These sensors are linked with micro programs inside micro-controllers put for example on Arduino card or microcomputers as Raspberry card In these all cases, the local database is a kind of cache we use temporally to be flushed when the network is already available. We propose an architecture were these problems (network availability, dynamic databases changes) are solved. We indicate some futures works and ideas on the subject in the sixth section and draw a conclusion
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
