Attribute scoping and hierarchy

Patent metadata

Field	Value
Publication number	US-9781187-B2
Application number	US-201213624921-A
Country	US
Kind code	B2
Filing date	Sep 22, 2012
Priority date	Sep 22, 2012
Publication date	Oct 3, 2017
Grant date	Oct 3, 2017

Abstract

Downloadable pluggable services and methods of distributing the same are described. The downloadable pluggable services may correspond to communication services that can be downloaded to upgrade a communication system. The downloadable pluggable services may include a number of component parts that can be distributed among various servers in the communication system being upgraded along with instructions that enable the component parts to instruct each server in the communication system to operate in a coordinated fashion so as to provide the downloaded service.

First claim

What is claimed is:

1. A method, comprising:
placing an order for a service to a service warehouse in an enterprise network, wherein the service is an application accessed through, to be implemented in, and executed on the enterprise network, wherein the service is a feature that is made available to a user within a single enterprise or within multiple enterprises;
before accessing the service, receiving an object, from an object generator, that defines a first level of attribute permissions associated with the service, the first level of attribute permissions defining a first set of rules controlling use of the service;
defining a second level of attribute permissions associated with the service, the second level of attribute permissions defining a second set of rules controlling use of the service, wherein the second set of rules are defined within the first set of rules and do not extend beyond the first set of rules, and wherein at least a first rule is included in the first set of rules that is not included in the second set of rules; and
building a data structure that controls user access to the service in accordance with both the first and second levels of attribute permissions, wherein the first level of attribute permissions correspond to permissions created by a provider of the service, wherein the second level of attribute permissions correspond to permissions created by an administrator of the enterprise network.

2. The method of claim 1 , wherein the first set of rules define a first and second option with respect to using the service and wherein the second set of rules define that the first option is not available to users of the service.

3. The method of claim 1 , wherein users of the enterprise network are allowed to select an attribute provided by the service within the scope of the first and second sets of rules.

4. The method of claim 1 , wherein users of the enterprise network are not allowed to select an attribute provided by the service that is outside the scope of the first and second sets of rules.

5. The method of claim 1 , wherein the data structure hierarchically orders the first level of attribute permissions and the second level of attribute permissions such that the second level of attribute permissions does not extend beyond the first level of attribute permissions.

6. The method of claim 1 , wherein the second level of attribute permissions are defined within the order for the service and wherein a provider of the service incorporates the first and second level of attribute permissions within the object that delivers the service.

7. The method of claim 1 , wherein the second level of attribute permissions is defined after the object is received.

8. The method of claim 7 , wherein at least some of the data structure is incorporated into a template that controls user access to the service.

9. The method of claim 1 , further comprising:
defining a third level of attribute permissions associated with the service, the third level of attribute permissions defining a third set of rules controlling use of the service, wherein the third set of rules are defined within the first and second set of rules and do not extend beyond the first and second set of rules; and
incorporating the third level of attribute permission into the data structure.

10. The method of claim 9 , wherein the third level of attribute permissions comprise user-defined rules.

11. A non-transitory computer-readable medium comprising processor-executable instructions that when executed by a processor cause a method to be performed, the method comprising:
placing an order for a service to a service warehouse in an enterprise network, wherein the service is an application accessed through, to be implemented in, and executed on the enterprise network, wherein the service is a feature that is made available to a user within a single enterprise or within multiple enterprises;
before accessing the service, receiving an object, from an object generator, that defines a first level of attribute permissions associated with the service, the first level of attribute permissions defining a first set of rules controlling use of the service;
defining a second level of attribute permissions associated with the service, the second level of attribute permissions defining a second set of rules controlling use of the service, wherein the second set of rules are defined within the first set of rules and do not extend beyond the first set of rules, and wherein at least a first rule is included in the first set of rules that is not included in the second set of rules; and
building a data structure that controls user access to the service in accordance with both the first and second levels of attribute permissions, wherein the first level of attribute permissions correspond to permissions created by a provider of the service, wherein the second level of attribute permissions correspond to permissions created by an administrator of the enterprise network.

12. The computer-readable medium of claim 11 , wherein the first set of rules define a first and second option with respect to using the service and wherein the second set of rules define that the first option is not available to users of the service.

13. The computer-readable medium of claim 11 , wherein users of the enterprise network are allowed to select an attribute provided by the service within the scope of the first and second sets of rules.

14. The computer-readable medium of claim 11 , wherein users of the enterprise network are not allowed to select an attribute provided by the service that is outside the scope of the first and second sets of rules.

15. The computer-readable medium of claim 11 , wherein the data structure hierarchically orders the first level of attribute permissions and the second level of attribute permissions such that the second level of attribute permissions does not extend beyond the first level of attribute permissions.

16. The computer-readable medium of claim 11 , wherein the second level of attribute permissions are defined within the order for the service and wherein a provider of the service incorporates the first and second level of attribute permissions within the object that delivers the service.

17. The computer-readable medium of claim 11 , wherein the second level of attribute permissions is defined after the object is received.

18. The computer-readable medium of claim 11 , wherein the method further comprises:
defining a third level of attribute permissions associated with the service, the third level of attribute permissions defining a third set of rules controlling use of the service, wherein the third set of rules are defined within the first and second set of rules and do not extend beyond the first and second set of rules; and
incorporating the third level of attribute permission into the data structure.

19. The computer-readable medium of claim 18 , wherein the third level of attribute permissions comprise user-defined rules.

20. A communication system, comprising:
at least one server including memory and a processor of an enterprise network, the server being configured to:
place an order for a service to a service warehouse in the enterprise network, wherein the service is an application, wherein the service is a feature that is made available to a user within a single enterprise or within multiple enterprises;
before accessing the service, receive an object, from an object generator, that defines a first level of attribute permissions associa

Assignees

• Avaya Inc

Inventors

• Meiners John
• Walker William T
• Haserodt Kurt

Classifications

• G06F2221/2117

  User registration · CPC title

• H04L63/102

  Entity profiles · CPC title

• G06F2221/2149

  Restricted operating environment · CPC title

• H04L67/34

  involving the movement of software or configuration parameters  (network booting or remote initial program loading [RIPL] G06F9/4416) · CPC title

• G06F21/6209

  to a single file or object, e.g. in a secure envelope, encrypted and accessed using a key, or with access control rules appended to the object itself · CPC title