# US 2016/0012081 A1 · Relationship Model for Modeling Relationships Between Equivalent Objects Accessible Over a Network

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2016/0012081 A1
- Document ID: US20160012081A1
- Status: Published application
- Kind: A1
- Application number: 14/858,573
- Filed: 2015-09-18
- Published: 2016-01-14
- Earliest claimed: 2008-11-07
- Assignees: Cloudlock, Inc.
- Applicants: CloudLock, Inc.
- Inventors: Gil Zimmermann; Ron Zalkind; Tsahy Shapsa
- Web page: https://patentgrep.com/patent/US20160012081A1

## CPC

- G06F 16/211: {Schema design and management}
- G06F 16/148: {File search processing}
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A relationship model system automatically recognizes relationships among data in a local IT environment. Such data may be derived from multiple sources, such as multiple devices and/or software applications of different types. Such data are collected automatically, remotely, and transparently from the local IT environment. Relationships among the data are recognized automatically by correlating data from the multiple sources. Records of such relationships are stored remotely in a relationship model. The system may draw conclusions based on the recognized relationships and take actions in response to those conclusions.

## Claims

### Claim 1

A method performed by at least one computer processor executing computer program instructions tangibly stored in a computer-readable medium, the method comprising:
(A) obtaining, over a network, first data maintained by a first resource;
(B) obtaining, over the network, second data maintained by a second resource;
(C) identifying a first portion of the first data, wherein the first portion relates to a first object;
(D) identifying a second portion of the second data, wherein the second portion relates to a second object;
(E) determining whether the first object and the second object are equivalent to each other; and
(F) if it is determined that the first object and the second object are equivalent to each other, then:
(F1) storing an indication of a relationship between the first portion and the second portion remotely from the first and second resources.