Systems and methods for mobility server administration

• US 9,201,669 B2
• Filed: 04/30/2010
• Issued: 12/01/2015
• Est. Priority Date: 05/03/2009
• Status: Active Grant

• Current Assignee: Malikie Innovations Limited (Key Patent Innovations Limited)
• Original Assignee: Blackberry Limited
• Inventors: Schneider, Kenneth Cyril, Hon, Lenny Kwok-Ming, Wang, Qiusheng
• Primary Examiner(s): JACOBS, LASHONDA T
• Application Number:
  US12/771,364
• Publication Number:
  US 20100281487A1
• Time in Patent Office: 2,041 Days
• Field of Search: 709201-230, 718102-106, 718/762
• US Class Current: 1/1
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files
• CPC Class Codes: G06F 9/44526 Plug-ins; Add-ons
• CPC Class Codes: G06F 9/44536 Selecting among different versions
• CPC Class Codes: G06F 9/44552 Conflict resolution, i.e. enabling coexistence of conflicting executables
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 63/20 for managing network security; network security policies in general filtering policies H04L63/0227

Abstract

An administration server of an administration service assigns attributes to objects by a plug-in of the administration service. The plug-in implements a method of a functionality set and the method is callable by the administration service to perform the assigning. Additionally or alternatively, the administration server triggers a reconciliation event by changing the assignment of an attribute of the users that comprise objects of plug-ins; determines a scope of the users and which objects are affected by changing the assignment; and reconciles conflicting assignments. Additionally or alternatively, the administration server adds tasks by the plug-ins to a job created by the plug-ins with the tasks performing the assigning; and removes tasks from the job to optimize it.

Claims

1. A method of an administration server comprising:

assigning a first attribute to one or more objects by a plug-in of an administration service of the administration server;

adding one or more tasks by one or more plug-ins to a job created by one of the one or more plug-ins, wherein a plurality of system throttling parameters and job throttling parameters of the job and the one or more tasks determine a number of tasks that can be executed at a same time, and wherein each task can only be executed when it has been granted a system slot and a job slot; and

wherein the plug-in implements a method of a functionality set to extend the one or more objects with the first attribute transparently to the administration server, the method being callable by the administration service to perform the assigning.

2. The method of claim 1 wherein the assigning is in response to the first attribute being assigned to one of a group, a server, a service, and a domain, and wherein the plurality of system throttling parameters quantify a number of system slots to limit a total number of tasks executing simultaneously all jobs of the administration service, and the job throttling parameters quantify a number of job slots to limit the execution of a task of a job.

3. The method of claim 2, further comprising:

displaying the first attribute on a graphical user interface (GUI) of the administration service at an integration point defined by the administration service and identified by the plug-in, and wherein the job and the one or more tasks each comprise a scheduling parameter and a throttling parameter, the scheduling parameter schedules an execution date, and the throttling parameter quantifies a number of job slots used to limit the execution of a task of a job.

4. The method of claim 1, wherein the first attribute is one of a policy, a software configuration, a required application, an optional application, a disallowed application, a device software configuration, a device software bundle, a native application setting, or an application setting.

5. The method of claim 2, wherein the one or more objects inherit a second attribute from the one of the group, the server, the service, and the domain.

6. The method of claim 5, further comprising reconciling the assignment of the first attribute with the assignment of the second attribute when the first attribute conflicts with the second attribute.

7. The method of claim 5, further comprising reducing a number of duplicate tasks that assign the first attribute and the second attribute to the one or more objects when the first attribute is similar to the second attribute and is assigned to a same one of the one or more objects.

21. The method as claimed in claim 1, further comprising:

triggering a reconciliation event by changing an assignment of the first attribute of one or more users comprising the one or more objects of one or more plug-ins;

determining a scope of the one or more users affected by changing the assignment;

determining one or more objects of the one or more plug-ins that are affected by changing the assignment;

reconciling the assignment with any conflicting assignments via one or more reconciliation objects, the conflicting assignments determined from one of the scope and the one or more objects determined to be affected; and

adding one or more tasks by one or more plug-ins to a job created by one of the one or more plug-ins, wherein a plurality of system throttling parameters and job throttling parameters of the job and the one or more tasks determine a number of tasks that can be executed at a same time, and wherein each task can only be executed when it has been granted a system slot and a job slot.

22. The method as claimed in claim 21, wherein the changing an assignment of the first attribute is via changing the association of a user to at least one of a group, a service, a server, or a domain.

23. The method as claimed in claim 21, wherein the changing an assignment of the first attribute is via directly changing the first of at least one of a user, a group, a service, a server, and a domain.

24. The method as claimed in claim 21, wherein the triggering a reconciliation event is caused by changing a ranking of the one or more reconciliation objects.

25. The method as claimed claim 21, wherein one of the one or more reconciliation objects is one of deleted and modified.

26. The method as claimed in claim 21, wherein the triggering a reconciliation event is caused by one of activating a first wireless mobile device, changing from the first wireless mobile device to a second wireless mobile device, setting a personal identification number (PIN) for the wireless mobile device, moving to a different server of a mobility service, and changing an operating system (OS) bundle of the first wireless mobile device.

27. The method as claimed in claim 1, further comprising:

adding one or more tasks by one or more plug-ins to a job created by one of the one or more plug-ins, the one or more tasks performing the assigning;

removing one or more of the one or more tasks from the job to optimize the job based on a set of rules; and

performing the assigning by the plug-in.

28. The method as claimed in claim 27, further comprising:

closing the job before the removing;

reopening the job after the removing;

adding at least one additional task to the job; and

closing the job after the adding.

29. The method as claimed in claim 27, wherein the job and the one or more tasks each comprise a scheduling parameter and a throttling parameter, the scheduling parameter schedules an execution date, and the throttling parameter quantifies a number of job slots used to limit the execution of a task of a job.

30. The method as claimed in claim 29, wherein a plurality of system throttling parameters and the job throttling parameters of the job and the one or more tasks determine a number of tasks that can be executed at a same time.

31. The method as claimed in claim 30, wherein each task can only be executed when it has been granted a system slot and a job slot, the plurality of system throttling parameters quantify a number of system slots to limit a total number of tasks executing simultaneously all jobs of the administration service, and the job throttling parameters quantify a number of job slots to limit the execution of a task of a job.

32. A server configured to perform the method of claim 1.

33. A non-transitory computer readable medium storing a set of instructions configured to perform the steps of claim 1.

8. A method of an administration server comprising:

triggering a reconciliation event by changing an assignment of an attribute of one or more users that each comprise one or more objects of one or more plug-ins by the one or more plug-ins to extend the one or more objects with the changed assignment of an attribute transparently to the administration server;

determining a scope of the one or more users affected by changing the assignment;

determining one or more objects of the one or more plug-ins that are affected by changing the assignment;

reconciling the assignment with any conflicting assignments via one or more reconciliation objects, the conflicting assignments determined from one of the scope and the one or more objects that are affected; and

adding one or more tasks by one or more plug-ins to a job created by one of the one or more plug-ins, wherein a plurality of system throttling parameters and job throttling parameters of the job and the one or more tasks determine a number of tasks that can be executed at a same time, and wherein each task can only be executed when it has been granted a system slot and a job slot.

9. The method of claim 8, wherein changing the assignment of the attribute is via changing the association of a user to at least one of a group, a service, a server, or a domain, and wherein the plurality of system throttling parameters quantify a number of system slots to limit a total number of tasks executing simultaneously all jobs of the administration server and the job throttling parameters quantify a number of job slots to limit the execution of a task of a job.

10. The method of claim 9, wherein the changing the assignment of the attribute is via directly changing the attribute of at least one of a user, a group, a service, a server, and a domain, and wherein the job and the one or more tasks each comprise a scheduling parameter and a throttling parameter, the scheduling parameter schedules an execution date, and the throttling parameter quantifies a number of job slots used to limit the execution of a task of a job.

11. The method of claim 8, wherein the attribute is one of a policy, a software configuration, a required application, an optional application, a disallowed application, a device software configuration, a device software bundle, a native application setting, or an application setting.

12. The method of claim 8, wherein the triggering a reconciliation event is caused by changing a ranking of the one or more reconciliation objects.

13. The method of claim 8, wherein one of the one or more reconciliation objects is one of deleted and modified.

14. The method of claim 8, wherein the triggering a reconciliation event is caused by one of activating a first wireless mobile device, changing from the first wireless mobile device to a second wireless mobile device, setting a personal identification number (PIN) for the wireless mobile device, moving to a different server of a mobility service, and changing an operating system (OS) bundle of the first wireless mobile device.

15. A method of an administration server comprising:

assigning an attribute to an object of one or more users via an administration service;

adding one or more tasks by one or more plug-ins to a job created by one of the one or more plug-ins, the one or more tasks performing the assigning;

removing one or more of the one or more tasks from the job to optimize the job based on a set of rules;

performing the assigning by the one or more plug-ins to extend the one or more objects with the attribute transparently to the administration server; and

adding one or more tasks by one or more plug-ins to a job created by one of the one or more plug-ins, wherein a plurality of system throttling parameters and job throttling parameters of the job and the one or more tasks determine a number of tasks that can be executed at a same time, and wherein each task can only be executed when it has been granted a system slot and a job slot.

16. The method of claim 15, further comprising:

closing the job before the removing;

reopening the job after the removing;

adding at least one additional task to the job; and

closing the job after the adding.

17. The method of claim 15, wherein the attribute is one of a policy, a software configuration, a required application, an optional application, a disallowed application, a device software configuration, a device software bundle, a native application setting, or an application setting, and wherein the plurality of system throttling parameters quantify a number of system slots to limit a total number of tasks executing simultaneously all jobs of the administration service, and the job throttling parameters quantify a number of job slots to limit the execution of a task of a job.

18. The method of claim 17, wherein the job and the one or more tasks each comprise scheduling parameter and a throttling parameter, the scheduling parameter schedules an execution date, and the throttling parameter quantifies a number of job slots used to limit the execution of a task of a job.

19. The method of claim 18, wherein a plurality of system throttling parameters and the job throttling parameters of the job and the one or more tasks determine a number of tasks that can be executed at a same time.

20. The method of claim 19, wherein each task can only be executed when it has been granted a system slot and a job slot, the plurality of system throttling parameters quantify a number of system slots to limit a total number of tasks executing simultaneously all jobs of the administration service, and the job throttling parameters quantify a number of job slots to limit the execution of a task of a job.