A mobile terminal including a body; a touchscreen provided to a front and extending to side of the body and configured to display content; and a controller configured to detect one side of the body comes into contact with one side of an external terminal, display a first area on the touchscreen corresponding to a contact area of the body and the external terminal and a second area including the content, receive an input of moving the content displayed in the second area to the first area, display the content in the first area, and share the content in the first area with the external terminal.

Mobile terminal and method for controlling the same

Improved techniques for managing enterprise applications on mobile devices are described herein. Each enterprise mobile application running on the mobile device has an associated policy through which it interacts with its environment. The policy selectively blocks or allows activities involving the enterprise application in accordance with rules established by the enterprise. Together, the enterprise applications running on the mobile device form a set of managed applications. Managed applications are typically allowed to exchange data with other managed applications, but are blocked from exchanging data with other applications, such as the user's own personal applications. Policies may be defined to manage data sharing, mobile resource management, application specific information, networking and data access solutions, device cloud and transfer, dual mode application software, enterprise app store access, and virtualized application and resources, among other things.

Policy-Based Application Management

Although a large volume of literature is available on mobile commerce (m-commerce), the topic is still under development and offers potential opportunities for further research and applications. Since the subject is at the stage of development, a review of the literature on m-commerce with the objective of bringing to the fore the state-of-art in m-commerce research and applications will initiate further research on the growth of m-commerce technologies. This paper reviews the literature on m-commerce and applications using a suitable classification scheme to identify the gap between theory and practice and future research directions. The 149 m-commerce articles are classified and the results of these are presented based on a scheme that consists of five distinct categories: m-commerce theory and research, wireless network infrastructure, mobile middleware, wireless user infrastructure, and m-commerce applications and cases. A comprehensive list of references is presented. We hope that the findings of this research will provide useful insights into the anatomy of m-commerce literature and be a good source for anyone who is interested in m-commerce. The paper also provides some future directions for research.

A review for mobile commerce research and applications

Display screen or portion thereof with graphical user interface

Pervasive computing environments pose unique service discovery challenges. We have developed a taxonomy of existing protocols as a basis for analyzing their approaches and identifying problems and open issues relative to service discovery in pervasive computing environments.

/pdf/service-discovery-in-pervasive-computing-environments-1vyy4uy1a6.pdf

Service discovery in pervasive computing environments

The proliferation of mobile devices and the pervasiveness of wireless technology have provided a major impetus to replicate the network-based service discovery technologies in wireless and mobile networks. However, existing service discovery protocols and delivery mechanisms fall short of accommodating the complexities of the ad-hoc environment. They also place emphasis on device capabilities as services rather than device independent software services, making them unsuitable for m-commerce oriented scenarios. Konark is a service discovery and delivery protocol designed specifically for ad-hoc, peer-to-peer networks, and targeted towards device independent services in particular. It has two major aspects - service discovery and service delivery. For discovery, Konark uses a completely distributed, peer-to-peer mechanism that provides each device the ability to advertise and discover services in the network. The approach towards service description is XML based. It includes a description template that allows services to be described in a human and software understandable forms. A micro-HTTP server present on each device handles service delivery, which is based on SOAP. Konark provides a framework for connecting isolated services offered by proximal pervasive devices over a wireless medium.

Konark - a service discovery and delivery protocol for ad-hoc networks

Various aspects of the disclosure relate to configuring and providing policies that manage execution of mobile applications. In some embodiments, a user interface may be generated that allows an IT administrator or other operator to set, change and/or add to policy settings. The policy settings can be formatted into a policy file and be made available for download to a mobile device, such as via an application store or to be pushed to the mobile device as part of a data push service. The mobile device, based on the various settings included in the policy file, may perform various actions to enforce the security constraints that are represented by the policy. The various settings that can be included in a policy are numerous and some examples and variations thereof are described in connection with the example embodiments discussed herein.

Configuring and providing profiles that manage execution of mobile applications

Various aspects of the disclosure relate to providing secure containers or data vaults for data of one or more managed applications. In some embodiments, each managed application may be assigned its own private data vault and/or may be assigned a shared data vault that is accessible to at least one other managed application. As the managed application executes, calls for access to the data may be intercepted and redirected to the secure containers. Data stored in a secure container may be encrypted according to a policy. Other aspects relate to deleting data from a secure container, such as via a selective wipe of data associated with a managed application. Further aspects relate to configuring and creating the secure containers, retrieving key information required to encrypt/decrypt the data stored in the secure containers, and publishing the managed applications, policy information and key information for download to a mobile device.

Controlling mobile device access to secure data

Various aspects of the disclosure relate to providing a per-application policy-controlled virtual private network (VPN) tunnel. In some embodiments, tickets may be used to provide access to an enterprise resource without separate authentication of the application and, in some instances, can be used in such a manner as to provide a seamless experience to the user when reestablishing a per-application policy controlled VPN tunnel during the lifetime of the ticket. Additional aspects relate to an access gateway providing updated policy information and tickets to a mobile device. Other aspects relate to selectively wiping the tickets from a secure container of the mobile device. Yet further aspects relate to operating applications in multiple modes, such as a managed mode and an unmanaged mode, and providing authentication-related services based on one or more of the above aspects.

Nitin Desai

Papers

Policy-Based Application Management

Konark - a service discovery and delivery protocol for ad-hoc networks

Configuring and providing profiles that manage execution of mobile applications

Controlling mobile device access to secure data

Providing Virtualized Private Network Tunnels