Method and system for selectively displaying calendar information on secure calendar
Abstract
A method and system for selectively displaying calendar information on a secure calendar application in an environment designed to restrict secure applications from processing requests from non-secure applications are described herein. In particular, calendar information can be selectively accessed from a non-secure calendar application in accordance with a sync setting that is enforceable against the calendar information. The calendar information from the non-secure calendar application can be imported into a secure calendar application. In addition, the imported calendar information can be displayed as part of the user interface of the secure calendar application when the secure calendar application is activated.
Claims
exact text as granted — not AI-modified1 - 20 . (canceled)
21 . A method of selectively displaying calendar information on a secure calendar application that is loaded on a computing device, comprising:
in an environment designed to restrict secure applications from processing requests from non-secure applications, by the computing device, selectively accessing calendar information from a non-secure calendar application in accordance with a sync setting that is enforceable against the calendar information; by the computing device, importing the calendar information from the non-secure calendar application into the secure calendar application, wherein the information is personal information that is associated with a user of the non-secure calendar application; by the computing device, displaying the imported calendar information as part of a user interface of the secure calendar application when the secure calendar application is activated, on a restricted basis such that some part of the personal information of the user is displayed as part of the secure calendar application and some part of the personal information is prevented from being displayed as part of the secure calendar application; by the computing device, disallowing the imported calendar information to be edited when the imported calendar information is displayed as part of the secure calendar application; by the computing device, determining whether an appointment on the non-secure calendar application is a medical appointment; responsive to making a determination that the appointment is not a medical appointment, by the computing device, sharing the appointment with the secure calendar application; and responsive to making a determination that the appointment is a medical appointment, by the computing device, not sharing the appointment with the secure calendar application.
22 . The method according to claim 21 , wherein the imported calendar information shows details related to a personal schedule of the user.
23 . The method according to claim 22 , further comprising displaying enterprise calendar information that is organic to the secure calendar application.
24 . The method according to claim 21 , wherein selectively accessing the calendar information comprises accessing all fields of the calendar information for a particular event from the non-secure application such that all the fields of the calendar information for the particular event are imported and displayed as part of the secure calendar application.
25 . The method according to claim 21 , wherein selectively accessing the calendar information comprises accessing only certain fields of the calendar information for a particular event from the non-secure application such that only the certain fields of the calendar information are imported and displayed as part of the secure calendar application.
26 . The method according to claim 25 , wherein the certain fields are a date field and a time field.
27 . The method according to claim 21 , further comprising providing an indication that edits to the imported calendar information are required to be performed through the non-secure calendar application.
28 . The method according to claim 21 , wherein the non-secure calendar application is loaded on the computing device.
29 . The method according to claim 21 , further comprising incorporating the imported calendar information into a scheduling assistant that provides an indication as to availability of the user for a particular time slot.
30 . The method according to claim 21 , wherein the computing device comprises a company-issued mobile device.
31 . A method of selectively displaying information from a first non-secure calendar application as part of a first secure calendar application, comprising:
in an environment designed to restrict secure applications from processing requests from non-secure applications, by a computing device, retrieving data from the first non-secure calendar application, wherein the data is personal data that is associated with a user of the first non-secure calendar application; by the computing device, displaying the retrieved data as part of the first secure calendar application on a restricted basis such that some part of the personal data that is associated with the user is displayed as part of the first secure calendar application and some part of the personal data is prevented from being displayed as part of the first secure calendar application; by the computing device, disallowing the retrieved data to be edited when the retrieved data is displayed as part of the first secure calendar application; by the computing device, determining whether an appointment on the first non-secure calendar application is a medical appointment; by the computing device, responsive to determining that the appointment is not a medical appointment, sharing the appointment with the first secure calendar application; and by the computing device, responsive to determining that the appointment is a medical appointment, not sharing the appointment with the first secure calendar application.
32 . The method according to claim 31 , wherein the first secure calendar application corresponds to the first non-secure calendar application such that the first secure calendar application is a secure version of the first non-secure calendar application.
33 . The method according to claim 31 , wherein the computing device comprises a company-issued mobile device.
34 . The method according to claim 31 , wherein the part of the personal data that is displayed as part of the first secure calendar application relates to temporal information from an event that is scheduled in the non-secure calendar application and the part of the personal data that is prevented from being displayed as part of the first secure calendar application relates to information that describes the event that is scheduled in the non-secure calendar application.
35 . A computing device that supports an environment designed to restrict secure applications from processing requests from non-secure applications, comprising:
a display unit that is configured to display the secure applications and the non-secure applications, wherein one of the secure applications is a secure calendar application and one of the non-secure applications is a non-secure calendar application; and a processor that is configured to:
cause the display unit to present:
a first sync setting through which a user can elect to have temporal data and event details for a calendar entry imported into the secure calendar application from the non-secure calendar application;
a second sync setting through which the user can elect to have the temporal data for the calendar entry imported into the secure calendar application from the non-secure calendar application without importation of the event details for the calendar entry; and
a third sync setting through which the user can elect not to import the temporal data and the event details for the calendar entry into the secure calendar application from the non-secure calendar application;
selectively import calendar information from the non-secure calendar application into the secure calendar application in accordance with a sync setting selection;
cause the display unit to display the imported calendar information as part of the secure calendar application;
cause the display unit to display other calendar information that is organic to the secure calendar application; and
disallow editing of the imported calendar information which is displayed as part of the secure calendar application.
36 . The computing device according to claim 35 , wherein the processor is further configured to:
determine whether an appointment on the non-secure calendar application is a medical appointment; responsive to determining that the appointment is not a medical appointment, share the appointment with the secure calendar application; and responsive to determining that the appointment is a medical appointment, not share the appointment with the secure calendar application.
37 . The computing device according to claim 35 , wherein the processor is further configured to provide the user with a plurality of designations that specify types of appointments on the non-secure calendar application and how much information relating to the specified types of appointments is to be shared with the secured calendar application, and
wherein at least one of the designations designates medical appointments on the non-secured calendar application and prevents designated medical appointments from being shared with the secured calendar application.
38 . The computing device according to claim 35 , wherein the computing device comprises a company-issued mobile device.
39 . The computing device according to claim 38 , wherein the processor is further configured to cause the display unit to present a notification asking the user if the user approves publication in the secure calendar application of information that the processor has retrieved from the non-secure calendar application so the user can block publication of the retrieved information.
40 . The computing device according to claim 38 , wherein the secure calendar application is a secure version of the non-secure calendar application.Join the waitlist — get patent alerts
Track US2018189742A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.