IP Library Granted Patent US 10,691,425
Granted Patent B2
US 10,691,425 · App. 16/040,903 · Granted Jun 23, 2020

Method and mechanism for optimal scope evaluation in scope based hierarchical configuration using evaluated scope propagation technique

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,691,425
App. No.
16/040,903
Granted
Jun 23, 2020
Kind
B2
Abstract

A first and a second local scope definition for a first and a second node in a hierarchical application tree are received where the hierarchical application tree includes application instructions at nodes. A pruned version of the tree is determined by propagating the first local scope definition from the first node to the second, child node. If the two scope definitions are the same type, the second local scope definition is used instead of the first at the second node. Otherwise, both the first and second local scope definitions are used at the second node if they are independent types. Any nodes that are not relevant are pruned and a qualified application is generated using application instructions at the unpruned nodes.

Claims (76)

1. A system, comprising:

a processor; and

a memory coupled with the processor, wherein the memory is configured to provide the processor with instructions which when executed cause the processor to:

receive a first local scope definition associated with a first node in a hierarchical application tree and a second local scope definition associated with a second node in the hierarchical application tree, wherein the hierarchical application tree includes application instructions at one or more nodes within the hierarchical application tree;

determine a pruned version of the hierarchical application tree, including by:

propagating the first local scope definition from the first node to the second node which is a child of the first node, including by:

in the event the first local scope definition and the second local scope definition are associated with a same scope type, using the second local scope definition instead of the first local scope definition at the second node, wherein the second local scope definition is the same or narrower compared to the first local scope definition; and

in the event the first local scope definition and the second local scope definition are associated with independent scope types, using both the first local scope definition and the second local scope definition at the second node; and

pruning any nodes from the hierarchical application tree that are not relevant to a particular set of one or more local scope definitions at a given node in order to obtain the pruned version of the hierarchical application tree; and

generate a qualified application using those application instructions at the unpruned nodes in the pruned version of the hierarchical application tree, wherein:

in the event the first local scope definition and the second local scope definition are associated with a same scope type, the qualified application is relevant to the second local scope definition; and

in the event the first local scope definition and the second local scope definition are associated with independent scope types, the qualified application is relevant to the first local scope definition and the second local scope definition.

2. The system recited in claim 1 , wherein:

the memory is further configured to provide the processor with instructions which when executed cause the processor to receive an access context in response to a user initiating access; and

the qualified application is generated for the received access context.

3. The system recited in claim 1 , wherein:

the memory is further configured to provide the processor with instructions which when executed cause the processor to receive an access context in response to a user initiating access;

the qualified application is generated for the received access context; and

the received access context includes one or more of the following: a role associated with the user that initiated the access, a subscription plan associated with the user that initiated the access, or an access device used by the user to initiate the access.

4. The system recited in claim 1 , wherein:

the memory is further configured to provide the processor with instructions which when executed cause the processor to receive an access context in response to a user initiating access;

the qualified application is generated for the received access context; and

pruning includes comparing the received access context against the particular set of one or more local scope definitions at said given node in order to obtain the pruned version of the is hierarchical application tree.

5. The system recited in claim 1 , wherein:

the memory is further configured to provide the processor with instructions which when executed cause the processor to receive an access context in response to a user initiating access;

the qualified application is generated for the received access context; and

pruning includes comparing the received access context against the particular set of one or more local scope definitions at said given node in order to obtain the pruned version of the hierarchical application tree, including by pruning said given node in the event the particular set of one or more local scope definitions at said given node indicates that said given node is not relevant to the received access context.

6. A method, comprising:

receiving a first local scope definition associated with a first node in a hierarchical application tree and a second local scope definition associated with a second node in the hierarchical application tree, wherein the hierarchical application tree includes application instructions at one or more nodes within the hierarchical application tree;

determining a pruned version of the hierarchical application tree, including by:

propagating the first local scope definition from the first node to the second node which is a child of the first node, including by:

in the event the first local scope definition and the second local scope definition are associated with a same scope type, using the second local scope definition instead of the first local scope definition at the second node, wherein the second local scope definition is the same or narrower compared to the first local scope definition; and

in the event the first local scope definition and the second local scope definition are associated with independent scope types, using both the first local scope definition and the second local scope definition at the second node; and pruning any nodes from the hierarchical application tree that are not relevant to a particular set of one or more local scope definitions at a given node in order to obtain the pruned version of the hierarchical application tree; and

generate a qualified application using those application instructions at the unpruned nodes in the pruned version of the hierarchical application tree, wherein:

in the event the first local scope definition and the second local scope definition are associated with a same scope type, the qualified application is relevant to the second local scope definition; and

in the event the first local scope definition and the second local scope definition are associated with independent scope types, the qualified application is relevant to the first local scope definition and the second local scope definition.

7. The method recited in claim 6 , wherein:

the method further includes receiving an access context in response to a user initiating access; and

the qualified application is generated for the received access context.

8. The method recited in claim 6 , wherein:

the method further includes receiving an access context in response to a user initiating access;

the qualified application is generated for the received access context; and

the received access context includes one or more of the following: a role associated with the user that initiated the access, a subscription plan associated with the user that initiated the access, or an access device used by the user to initiate the access.

9. The method recited in claim 6 , wherein:

the method further includes receiving an access context in response to a user initiating access;

the qualified application is generated for the received access context; and

pruning includes comparing the received access context against the particular set of one or more local scope definitions at said given node in order to obtain the pruned version of the hierarchical application tree.

10. The method recited in claim 6 , wherein:

the method further includes receiving an access context in response to a user initiating access;

the qualified application is generated for the received access context; and

pruning includes comparing the received access context against the particular set of one or more local scope definitions at said given node in order to obtain the pruned version of the hierarchical application tree, including by pruning said given node in the event the particular set of one or more local scope definitions at said given node indicates that said given node is not relevant to the received access context.

11. A computer program product, the computer program product being embodied in a non-transitory computer readable storage medium and comprising computer instructions for:

receiving a first local scope definition associated with a first node in a hierarchical application tree and a second local scope definition associated with a second node in the hierarchical application tree, wherein the hierarchical application tree includes application instructions at one or more nodes within the hierarchical application tree;

determining a pruned version of the hierarchical application tree, including by:

propagating the first local scope definition from the first node to the second node which is a child of the first node, including by:

in the event the first local scope definition and the second local scope definition are associated with a same scope type, using the second local scope definition instead of the first local scope definition at the second node, wherein the second local scope definition is the same or narrower compared to the first local scope definition; and

in the event the first local scope definition and the second local scope definition are associated with independent scope types, using both the first local scope definition and the second local scope definition at the second node; and

pruning any nodes from the hierarchical application tree that are not relevant to a particular set of one or more local scope definitions at a given node in order to obtain the pruned version of the hierarchical application tree; and

generate a qualified application using those application instructions at the unpruned nodes in the pruned version of the hierarchical application tree, wherein:

in the event the first local scope definition and the second local scope definition are associated with a same scope type, the qualified application is relevant to the second local scope definition; and

in the event the first local scope definition and the second local scope definition are associated with independent scope types, the qualified application is relevant to the first local scope definition and the second local scope definition.

12. The computer program product recited in claim 11 , wherein:

the computer program product further includes computer instructions for receiving an access context in response to a user initiating access; and

the qualified application is generated for the received access context.

13. The computer program product recited in claim 11 , wherein:

the computer program product further includes computer instructions for receiving an access context in response to a user initiating access;

the qualified application is generated for the received access context; and

the received access context includes one or more of the following: a role associated with the user that initiated the access, a subscription plan associated with the user that initiated the access, or an access device used by the user to initiate the access.

14. The computer program product recited in claim 11 , wherein:

the computer program product further includes computer instructions for receiving an access context in response to a user initiating access;

the qualified application is generated for the received access context; and

pruning includes comparing the received access context against the particular set of one or more local scope definitions at said given node in order to obtain the pruned version of the hierarchical application tree.

15. The computer program product recited in claim 11 , wherein:

the computer program product further includes computer instructions for receiving an access context in response to a user initiating access;

the qualified application is generated for the received access context; and

pruning includes comparing the received access context against the particular set of one or more local scope definitions at said given node in order to obtain the pruned version of the hierarchical application tree, including by pruning said given node in the event the particular set of one or more local scope definitions at said given node indicates that said given node is not relevant to the received access context.

Assignments (9)
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (053546/0001) Recorded Jun 23, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL MARKETING L.P. (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO CREDANT TECHNOLOGIES, INC.); DELL INTERNATIONAL L.L.C.; DELL PRODUCTS L.P.; DELL USA L.P.; EMC CORPORATION; DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO FORCE10 NETWORKS, INC. AND WYSE TECHNOLOGY L.L.C.); EMC IP HOLDING COMPANY LLC
Reel/Frame 071642/0001 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (047648/0422) Recorded May 20, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL PRODUCTS L.P.; EMC CORPORATION; EMC IP HOLDING COMPANY LLC
Reel/Frame 060160/0862 →
RELEASE OF SECURITY INTEREST AT REEL 047648 FRAME 0346 Recorded Nov 2, 2021
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: DELL PRODUCTS L.P.; EMC CORPORATION; EMC IP HOLDING COMPANY LLC
Reel/Frame 058298/0510 →
SECURITY AGREEMENT Recorded Apr 22, 2020
From: CREDANT TECHNOLOGIES INC.; DELL INTERNATIONAL L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL USA L.P.; EMC CORPORATION; FORCE10 NETWORKS, INC.; WYSE TECHNOLOGY L.L.C.; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
Reel/Frame 053546/0001 →
SECURITY AGREEMENT Recorded Mar 21, 2019
From: CREDANT TECHNOLOGIES, INC.; DELL INTERNATIONAL L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL USA L.P.; EMC CORPORATION; FORCE10 NETWORKS, INC.; WYSE TECHNOLOGY L.L.C.; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
Reel/Frame 049452/0223 →
PATENT SECURITY AGREEMENT (CREDIT) Recorded Oct 12, 2018
From: DELL PRODUCTS L.P.; EMC CORPORATION; EMC IP HOLDING COMPANY LLC
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 047648/0346 →
PATENT SECURITY AGREEMENT (NOTES) Recorded Oct 12, 2018
From: DELL PRODUCTS L.P.; EMC CORPORATION; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT
Reel/Frame 047648/0422 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 20, 2018
From: EMC CORPORATION
To: EMC IP HOLDING COMPANY LLC
Reel/Frame 046418/0442 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 20, 2018
From: TOTALE, SACHIN G.
To: EMC CORPORATION
Reel/Frame 046418/0429 →