US 10,782,962 B2Granted

Component design security through restriction of a design component dependency tree

AssigneeMethodics, Inc.

InventorsVishal Moondhra, Fergus Slorach

Life of this patent

Estimating the term…

Loading patent…

Abstract

Disclosed is a method, a device, a system and/or a manufacture of component design security through restriction of a design component dependency tree. In one embodiment, a request for retrieval of a dependency tree of a root version of a component is processed. A client device is authenticated, and a permission profile is extracted. Unique identifier of the root version and each version of the dependency tree is compared to the permission profile of the user and/or a security profile to determine an authorization status for each. Dependency reference following is terminated at unauthorized versions to result in a terminated branch of the dependency tree. Unique identifier of the authorized version are stored in a restricted tree data to result in a continuing branch of the dependency tree. The restricted tree data of the root version is returned to the client device for retrieving workfiles to generate a design workspace.

Claims20

Dependent claims

A computer-implemented method for selectively securing design data, the method comprising:

receiving a first request for retrieval of a dependency tree of a version of a component, the first request generated by a client device of a user and comprising a unique identifier of the user and a unique identifier of the version of the component as a root version of the dependency tree;
authenticating at least one of the user and the client device of the user;
extracting a permission profile associated with the unique identifier of the user;
generating a second request for retrieval of the dependency tree of the root version of the component, the second request comprising the permission profile and the unique identifier of the root version of the component;
querying the root version of the component with the unique identifier of the root version;
following a first dependency reference to a version of a first sub-component of the component and a second dependency reference to a version of a second sub-component of the component;
extracting a security profile associated with the first sub-component;
comparing the permission profile of the user to the security profile associated with the first sub-component to determine exclusion of the version of the first sub-component from the dependency tree of the root version;
terminating a dependency reference following at the version of the first sub-component to result in a terminated branch of the dependency tree of the root version;
storing the unique identifier of the version of the second sub-component in a restricted tree data to result in a continuing branch of the dependency tree of the root version;
and
returning the restricted tree data of the root version to the client device of the user.

9 more elements

A computer-implemented method for selectively securing design data, the method comprising:

receiving a first request for retrieval of a dependency tree of a version of a component, the first request comprising a unique identifier of a user generating the request and a unique identifier of the version of the component as a root version of the dependency tree,
extracting a permission profile associated with the user generating the first request;
submitting the unique identifier of the version of the component as a query to a design database comprising a set of dependency references defining a directed acyclic graph stored in a computer memory,
wherein, the directed acyclic graph comprising a set of components as nodes of the directed acyclic graph and a set of dependency references of at least one of the set of components and a set of the versions of the set of components drawn between the nodes as directed edges of the directed acyclic graph;
starting at the root node, following the set of dependency references of the version of the component and the set of dependency references of a version of each of a set of sub-components of the component;
comparing the unique identifier of the version of the component and the unique identifier of the version of each of the set of sub-components to the permission profile of the user to determine an authorization status for the root version and each of the versions of the set of sub-components;
and
storing a restricted tree data comprising a unique identifier of the root version and the unique identifier of each version of the set of sub-components having both:
(i) a positive authorization status and (ii) a connection to the root version of the component through a dependency chain of versions, each version in the dependency chain having the positive authorization status.

6 more elements

A system comprising:

a coordination server comprising:
a processor of the coordination server,
a memory of the coordination server,
a request agent comprising computer executable instructions that when executed on the processor of the coordination server receives a first request for retrieval of a dependency tree of a version of a component, the first request comprising a unique identifier of the user and a unique identifier of the version of the component as a root version of the dependency tree,
an authentication module comprising computer executable instructions that when executed on the processor of the coordination server authenticates at least one of a user and a client device of the user generating the request,
a tree query engine comprising computer executable instructions that when executed on the processor of the coordination server, starting at the root node, follows a set of dependency references of the version of the component and a set of dependency references of a version of each of a set of sub-components of the component to assemble a tree data;
a tree restriction engine comprising:
(i) a profile comparison module comprising computer executable instructions that when executed on the processor of the coordination server extracts a permission profile associated with the unique identifier of the user and compares the unique identifier of the version of the component and the unique identifier of the version of each of the set of sub-components of the tree data to the permission profile of the user;
(ii) a node authorization module that determines an authorization status for the root version and each of the versions of the set of sub-components;
and
(iii) a node selection module of the coordination server comprising computer executable instructions that when executed on the processor of the coordination server stores a restricted tree data comprising a unique identifier of the root version and the unique identifier of each version of the set of sub-components having both:
(a) a positive authorization status and (b) a connection to the root version of the component through a dependency chain of versions, each version in the dependency chain having the positive authorization status, and
a network.

10 more elements

Dependencies are inferred from the claim text.

Facts

Application: 16/403,571Filed 5 May 2019 · us provisional application
Priority: 6 May 2018
Published: US 2019/0339966 A17 Nov 2019
Granted: 22 Sep 2020
Term ends: Not estimatedThe source records don’t support an estimate.

Classification5 codes

G06F 8/71
Software maintenance or management: version control ; Configuration management
G06F 8/433
Checking; Contextual analysis: dependency analysis; Data or control flow analysis
G06F 16/9027
Indexing; Data structures therefor; Storage structures: trees
G06F 16/903
Details of database functions independent of the retrieved data types: querying