Multi-User Media Playback System
US-2024354051-A1 · Oct 24, 2024 · US
US9575979B1 · US · B1
| Field | Value |
|---|---|
| Publication number | US-9575979-B1 |
| Application number | US-201314107950-A |
| Country | US |
| Kind code | B1 |
| Filing date | Dec 16, 2013 |
| Priority date | Dec 16, 2013 |
| Publication date | Feb 21, 2017 |
| Grant date | Feb 21, 2017 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Techniques are described for automatically determining application composition and application ownership of an application that may include a plurality of files deployed to a plurality of host devices. The determination of application composition may be based on analyzing various types of metadata that may provide evidence of associations between deployed files, such as metadata describing the deployment of files to host devices, metadata describing the files tracked within a source control system, or other types of metadata. The determination of application ownership may also be based on analyzing the various types of metadata that provide evidence of associations between files and individuals or groups of individuals within an organization.
Opening claim text (preview).
What is claimed is: 1. A computer-implemented method, comprising: accessing deployment metadata describing deployment of a plurality of files to a plurality of computing devices, the deployment metadata further describing one or more computing device owners associated with one or more of the plurality of computing devices; based on the deployment metadata, determining that at least two files of the plurality of files are deployed to a subset of the plurality of computing devices; determining a relationship metric indicating a relationship between the at least two files, the relationship metric based at least partly on a number of the subset of computing devices to which the at least two files are deployed, the relationship metric varying substantially inversely to the number of computing devices to which the at least two files are deployed in the subset of computing devices, wherein the at least two files deployed to the subset of computing devices are more strongly related when deployed to a common set of computing devices that are fewer in number compared to a total number of the plurality of computing devices; based on the relationship metric being above a threshold level, determining that the at least two files are components of an application; accessing source control metadata describing changes to source code files corresponding to the at least two files, the changes recorded using a source control module that generates the source control metadata, the source control metadata further describing one or more source control users who made the changes; and determining one or more application owners who are at least partly responsible for the application, based on the one or more source control users who made the changes and the one or more computing device owners associated with the subset of computing devices. 2. The method of claim 1 , wherein: the source control metadata further describes one or more relationships among the plurality of files, including whether the source code files corresponding to the at least two files are included in a same branch of a source tree; and the determining of the relationship metric is further based on whether the source code files are included in the same branch, as described in the source control metadata. 3. The method of claim 1 , wherein: the deployment metadata further describes one or more deployment requesting users who requested the deployment of the at least two files to the subset of computing devices; and the determining of the one or more application owners is further based on the one or more deployment requesting users. 4. The method of claim 1 , wherein the plurality of files includes one or more of: a binary executable module; a binary library; a resource file; a configuration file; or a security credential. 5. A system, comprising: at least one computing device configured to implement one or more services, wherein the one or more services are configured to: access deployment metadata describing deployment of a plurality of files to a plurality of computing devices; based on the deployment metadata, determine that at least two files of the plurality of files are deployed to a common subset of the plurality of computing devices; determine a relationship metric indicating a relationship between the at least two files, the relationship metric based at least partly on a number of computing devices in the subset of computing devices to which the at least two files are commonly deployed; based on the relationship metric being above a threshold level, determine that the at least two files are components of an application; and determine one or more owners of the application based on source control metadata associated with the at least two files; wherein the relationship metric varies substantially inversely with the number of computing devices in the subset of computing devices to which the at least two files are deployed. 6. The system of claim 5 , wherein the at least two files deployed to the subset of computing devices are more strongly related when deployed to a common set of computing devices that are fewer in number compared to a total number of the plurality of computing devices. 7. The system of claim 5 , wherein the determining that the at least two files are components of the application is further based on the at least two files being deployed to one of the plurality of computing devices. 8. The system of claim 5 , wherein the determining that the at least two files are components of the application is further based on the at least two files being deployed to the subset of computing devices that exhibit one or more of: a substantially similar software configuration, as described by the metadata; a substantially similar hardware configuration, as described by the metadata; or a substantially similar function, as described by the metadata. 9. The system of claim 5 , wherein: the metadata further describes one or more computing device owners associated with one or more of the plurality of computing devices; and the one or more services are further configured to determine one or more application owners associated with the application, the one or more application owners being determined based at least partly on the one or more computing device owners associated with the subset of computing devices to which the at least two files are deployed. 10. The system of claim 5 , wherein: the metadata further describes one or more deployment requesting users who requested the deployment of the at least two files to the subset of computing devices; and the one or more services are further configured to determine one or more application owners associated with the application, the one or more application owners being determined based at least partly on the one or more deployment requesting users. 11. The system of claim 5 , wherein: the metadata further describes changes to source code files corresponding to the at least two files, the changes recorded using a source control module; the metadata further describes one or more source control users who made the changes; and the one or more services are further configured to determine one or more application owners associated with the application, the one or more application owners being determined based at least partly on the one or more source control users who made the changes to the source code files. 12. The system of claim 11 , wherein the one or more application owners are determined based at least partly on the one or more source control users who made a highest number of changes to the source code files within a period of time. 13. The system of claim 11 , wherein: the metadata further describes one or more relationships among the plurality of files, including whether the source code files corresponding to the at least two files are included in a same branch of a source tree; and the determining of the relationship metric is further based on whether the source code files are included in the same branch, as described in the metadata. 14. One or more non-transitory computer-readable media storing instructions which, when executed by at least one processor, instruct the at least one processor to perform actions comprising: accessing deployment metadata describing deployment of a plurality of files to a plurality of computing devices; based on the deployment metadata, determining that at least two files of the plurality of files are deployed to a common subset of the plurality of computing devices; determining a relationship metric indicating a relationship between the at least two files, the rel
Tools and structures for managing or administering access control systems · CPC title
Physics · mapped topic
to a system of files or objects, e.g. local or distributed file system or database · CPC title
Test or assess a computer or a system · CPC title
using file content signatures, e.g. hash values · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.