Vmware, Inc.

Airwatch LLC

Omnissa, LLC

Qualcomm Incorporated

Sap Se

Anthony Kueh

Ian Ragsdale

Adam Cianfichi

Andrew Everett Eye

Neal Foster

Rob Worsnop

Marshall Anne Busbee

Dan Zeck

Daniel Benjamin Quintas

Dan Quintas

Gerard T Murphy

Gaurav Arora

Deep Singh

Yugansh Arora

Kunal Muchhala

Sanjeet Mall

Scott W Strobel

Andrew Wai Lee

Raman Sethi

Marcus Pridham

Marc Waldthausen

Jonathan Li

Systems and methods are disclosed herein for dynamically applying information rights management ('IRM') policies to documents. An example system for dynamically applying IRM policies to documents can include a document repository, a proxy server, and a dynamic IRM wrapping service (also referred to herein as an IRM engine). A user can request a document on the document repository by, for example, attempting to access the document from a user device. The user device can be managed by a management server that enrolls the user device and enforces compliance rules and other policies at the user device. The user's request for the document can be received at the proxy server, and the proxy server can then request the document from the document repository.

Systems and methods for dynamically applying information rights management policies to documents

Disclosed are various approaches for generating a device posture token corresponding to a client device. The device posture token can be used by a verification computing device to determine whether the client device complies with the security policies of a particular facility.

Determining a device posture using a device posture token

Systems herein supply hero cards that display contextual information and actions based on backend systems. The information and actions are related to a trigger content item in an application that does not have access to the backend systems. A hero agent running a user device can communicate the trigger content to a hero server. The hero server can determine which connectors to backend systems relate to the user device, and then can retrieve result information from one or more of the backend systems. The result information populates the hero card, which the hero agent displays within the application. Action buttons on the hero card cause the hero agent to contact one or more of the backend systems to cause an action to take place there.

Hero cards that display contextual information and actions for backend systems

In one example of federated mobile device management, a first management service federates with a second management service based on an exchange of one or more identity authentication certificates. After the management services have federated or affiliated, the first service can enroll a client device for management based on federated management data, where the federated management data includes first device management data of the first management service and second device management data of the second management service. The first service can also identify a change in affiliation associated with at least one of the client device or the second management service and cause the client device to check in for a device management update based on the change in affiliation.

Federated mobile device management

In one example of federated mobile device management, a first management server federates with a second management server based on an exchange of one or more identity authentication certificates between them. After the first and second management servers have federated or affiliated, they can exchange mobile device management data, including compliance policies, rules, resources, etc., with each other. Based on a request from a client device for affiliated mobile device management, the first management server can request and receive device management data from the second management device. The first management server can evaluate the device management data received from the second management device for conformity with a baseline management policy. If it conforms, the first management server can use the device management data from the second management server, at least in part, to manage the client device.

In an example embodiment, a container is downloaded, the container being an application natively executable by a first operating system of the user device, the container including: a container service including one or more libraries of functions designed by a container designer to natively operate on the first operating system; a browser; container metadata defining functions of the application, the functions compatible with the container service for the first operating system and also compatible with a container service for a second operating system; and a plug-in including one or more additional libraries of functions designed by an entity other than the container designer to perform additional native operations on the first operating system. Then, the container metadata can be executed using the browser, causing function calls to the container service and plug-in and thus controlling native functions of the user device.

Dynamic containerization

A system and method for displaying an electronic program guide are disclosed. In one embodiment the method comprises receiving, for a plurality of first events, first event metadata comprising a first event description and a first logical channel number, receiving, for a plurality of second events, second event metadata comprising a second event description and a second logical channel number, assigning the first logical channel number associated with a particular first event to a particular second event, wherein the assignment is based on the first event metadata of the particular first event and the second event metadata of the particular second event, and displaying a program guide comprising at least a portion of the second event metadata of the particular second event.

System and method for displaying a mapping of channels in a program guide

Growing community of inventors

San Jose, CA, United States of America

Anthony Kueh