New delivery mechanism for delevering the application serivces to mobile devices.
Publication Date: 2017-Feb-08
The IP.com Prior Art Database
This article challenges the very notion of 'Mobile Applications' which are monolithic and space consuming. It suggests an alternative apporach that converts User Engagements (Actions) from the Application. Whereas, the application itself is context aware, it triggers various events and each event translates into an action and each action would fetch a service metadata from the service host. The main benefit from this approach is it brings less weighted applications & agility for Enterprises to convert any service into an application.
New delivery mechanism for delevering the application serivces to mobile devices .
Mobile has become the most important platform and medium for commerce and interaction between consumers with businesses. Therefore today many enterprises are coming with mobile apps to deliver the business services. A typical Enterprise is aiming at delivering not less than 10 different applications on an average. This glut of mobile apps are intimidating to the mobile users and they generally only download & use a handful of these applications.
There are many businesses that provide services that are not used day to day by customers. The mobile applications that are provided by those businesses occupy disk space on the user's mobile phone where space is at a premium. Another aspect of the problem is that many businesses are rolling out applications to visitors to their campuses. These applications contain directions, site plan etc. The visitor needs this only inside the campus. Once outside he does not need the app at all.
So there needs to be a way for mobile users to access apps at a particular location without needing to install the app locally on their mobile and the app should only be available for the duration the user is in the vicinity of the location.
Hence, a new approach is required to deliver certain class of business applications through a model other than traditional mobile apps.
The main point here is to do away with the core concepts around traditional mobile applications and bring in a novel approach to define & represent a way to enable business services be made accessible on mobile devices without ever having to force the mobile user to install and keep the applications forever.
The core feature is to provide a mobilet container as a mobile OS capability or an application mold along with a trusted metadata repository store to host application services called mobilets. Unlike traditional user initiated applications, this article proposes a new approach where in the application services are launched based on external stimuli such as iBeacons, who carries URI information. The mobilet container, based on the URI, would in turn contact the respective metadata repository to load the mobilets and render them natively.
Mobilet container, in the proposed article, is thought out to be an intrinsic feature of a Mobile Operating System which can be externally stimulated through iBeacon, Bluetooth or any such mechanisms who could pass in data bits in the stimulation process. The point is to use this data exchange aspect of external devices to pass in service specific details from external stimulating devices to the Mobilet container in a URI format. The URI contains details about a service repository & service name to be
loaded in the current context. The service repository is a registry where an Enterprise put their applications in the prescribed format. It is just like a Google AppStore that hosts traditional mobile apps.