Device-type based content management

• US 10,116,701 B2
• Filed: 04/01/2014
• Issued: 10/30/2018
• Est. Priority Date: 04/01/2014
• Status: Active Grant

• Current Assignee: Ent Services Development Corporation LP (DXC Technology Company)
• Original Assignee: Ent Services Development Corporation LP (DXC Technology Company)
• Inventors: Balacheff, Boris, Cooper, James C., Penkler, David
• Primary Examiner(s): Song, Hosuk
• Application Number:
  US15/301,291
• Publication Number:
  US 20170026420A1
• Time in Patent Office: 1,673 Days
• Field of Search: 726 1, 726 2- 6, 709229
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: H04L 63/20 for managing network security; network security policies in general filtering policies H04L63/0227

Abstract

Examples of systems and methods for device-type content management are described herein. In an example, at least one of a community policy and a community-device type policy may be generated. The community policy may be generated for a community defined for an enterprise and may be enforced on a plurality of user devices registered with the community. Further, the device-community policy may be enforced on a user device, from among the plurality of user devices, based on a device-type of the user device. The device-community policy may indicate a management service to be used to realize the community policy. Further, a management service agent (MS agent) may be provided to the user device, based on the management service indicated by the device-community policy. The MS agent may provide for managing enterprise content on the user device as indicated by the community policy.

Claims

1. An enterprise content management system comprising:

a processor;

a community module coupled to the processor to generate;

a community policy for a community defined for an enterprise, wherein the community policy is enforced on a plurality of user devices registered with the community; and

a device-community policy associated with the community policy, wherein the device-community policy is enforced on a user device, from among the plurality of user devices, based on a device-type associated with the user device, the device-community policy being indicative of a management service to be used to enforce the community policy for the device-type; and

a domain module coupled to the processor to provide a management service agent (MS agent) to the user device, based on the management service, wherein the MS agent manages enterprise content on the user device as defined by the community policy and the device-community policy.

2. The enterprise content management system as claimed in claim 1, wherein the enterprise content management system further comprises an adapter coupled to the processor, wherein the adapter provides for configuration of the management service, based on the community policy.

3. The enterprise content management system as claimed in claim 1, wherein the domain module:

receives a request from the user device to register with the community;

identifies the device-community policy to be implemented on the user device, based on the device-type associated with the user device; and

configures the management service, based on a user-device pair, to generate the MS agent.

4. The enterprise content management system as claimed in claim 1, wherein the community module:

receives a request to create the community for the enterprise from a community administrator; and

defines the community policy for the community, based on details provided for community attributes, wherein the community attributes provide controlled access to the enterprise content.

5. The enterprise content management system as claimed in claim 1, wherein the community module:

provides a list of device-types associated with the community to a community administrator;

for each device-type selected by the community administrator, determines available management services; and

for each selected device-type, generates the device-community policy, based on the management service selected from the available management services.

6. The enterprise content management system as claimed in claim 1, wherein the domain module defines a default device-community policy for the community, wherein the default device-community policy is used to implement the community policy on the user device, when the device-community policy is not defined for the device-type.

7. A computer implemented method for device-type based content management comprising:

receiving a request from a user device to register with a community defined for an enterprise, wherein enterprise content on the user device registered with the community is managed based on a community policy defined for the community;

identifying a device-community policy associated with the community policy to be implemented on the user device, based on a device-type of the user device, the device-community policy being indicative of a management service to be used to enforce the community policy for the device-type; and

providing a management service agent (MS agent) to the user device, based on the device-community policy, wherein the MS agent is an instance of the management service indicated by the device-community policy and is configured based on the community policy and the device-community policy to manage the enterprise content on the user device.

8. The computer implemented method as claimed in claim 7, wherein providing the MS agent further comprises enrolling the user device and a user corresponding to the user device with the management service.

9. The computer implemented method as claimed in claim 7 further comprising:

ascertaining whether the user and the user device are registered with a content management domain, wherein the content management domain interfaces the user device with the community to provide access to the enterprise content;

registering the user and the user device, based on the ascertaining; and

linking the user device to the user in the content management domain to generate a user-device pair, when the user and the user device are not linked to each other, wherein the MS agent is configured, based on the user-device pair.

10. The computer implemented method as claimed in claim 7, wherein the method further comprises:

ascertaining whether the user is registered with the community and is not registered with a content management domain; and

generating dummy domain credentials to register the user and the user device with the content management domain, based on the ascertaining.

11. A non-transitory computer-readable medium comprising instructions executable by a processor to:

generate a community policy for a community defined for an enterprise, based on inputs provided for community attributes, the community policy being enforced on a plurality of user devices registered with the community, wherein the community attributes provide controlled access to enterprise content;

create a device-community policy associated with the community policy, the device-community policy being defined for each of a plurality of device-types associated with the community, wherein the device-community policy indicates a management service to be implemented to enforce the community policy on a user device of a device-type, from amongst the plurality of device-types; and

configure a management service agent (MS agent) to the user device based on the management service to manage enterprise content on the user device based on the community policy and the device-community policy.

12. The non-transitory computer-readable medium as claimed in claim 11, wherein the non-transitory computer-readable medium further comprises instructions executable by the processor to provide the MS agent to the user device to manage enterprise content on the user device, based on a user-device pair, wherein the MS agent is an instance of the management service.

13. The non-transitory computer-readable medium as claimed in claim 11, wherein the non-transitory computer-readable medium further comprises instructions executable by the processor to:

provide a list of communities to a domain administrator, the list comprising published communities and unpublished communities, wherein the published communities are available to users associated with the enterprise; and

publish community details pertaining to an unpublished community in a content management domain, based on inputs provided by the domain administrator, wherein the content management domain interfaces the user device with the community to provide access to the enterprise content.

14. The non-transitory computer-readable medium as claimed in claim 11, wherein the non-transitory computer-readable medium further comprises instructions executable by the processor to:

receive a request to add an application in an application store of a content management domain;

prompt a community administrator to provide common application data and application-device type data, the common application data including details for application parameters common to all device-types and the application-device type data including details pertaining to a device-type associated with the application; and

save the application, the common application data, and the application-device type data in the application store of the content management domain.

15. The non-transitory computer-readable medium as claimed in claim 14, wherein the non-transitory computer-readable medium further comprises instructions executable by the processor to:

receive a request to publish the application in an application store of the community;

for each device-type associated with the community, based on a corresponding device-community policy, identify an application management service to manage applications; and

configure the application in each application management service, based on corresponding application-device type data.