Service dependencies based on relationship network graph

US2024259252A1 · US · A1

Patent metadata
FieldValue
Publication numberUS-2024259252-A1
Application numberUS-202318162374-A
CountryUS
Kind codeA1
Filing dateJan 31, 2023
Priority dateJan 31, 2023
Publication dateAug 1, 2024
Grant date

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

Dependencies between services are determined based on the relationships between entities responsible for the services. The relationships are found based on past interactions between the entities. A relationship network graph having nodes representing entities and edges is built representing interactions between respective entities. The relationship network graph is analyzed to identify pairs of nodes having a relationship based on an evaluation between edge paths between the pairs of nodes compared to edge paths between other pairs of nodes. Associations are built between services owned by entities represented by the nodes of a pair of nodes identifying that nodes are dependent on one another.

First claim

Opening claim text (preview).

1 . A method, comprising: building a relationship network graph having nodes representing entities and edges representing interactions between respective entities, wherein each of the entities represents a respective person, a team, or an organization of people; analyzing the relationship network graph to identify a pair of nodes having a relationship based on an evaluation between edge paths between the pair of nodes compared to edge paths between other pairs of nodes; and creating at least one association between services owned by entities represented by the nodes of the pair of nodes identifying that the services owned by the entities are dependent on one another. 2 . The method of claim 1 , further comprising: receiving records of the interactions between the respective entities; receiving contextual information providing context for the interactions between the entities; and building interaction information based on the records of the interactions between the respective entities and the contextual information, wherein the relationship network graph is built from the interaction information. 3 . The method of claim 2 , wherein edges between the entities are weighted based on the contextual information. 4 . The method of claim 1 , further comprising: generating a service incident alert for a first service associated with a first entity represented by a first node of a the pair of nodes, wherein the service incident alert includes an identification of a second service associated with a second entity represented by a second node of the pair of nodes; and sending the service incident alert to the first entity. 5 . The method of claim 1 , further comprising: sending a first message for a first service associated with a first entity represented by a first node of a the pair of nodes; and sending a second message for a second service associated with a second entity represented by a second node of the pair of nodes based on the association between the nodes. 6 . The method of claim 5 , wherein the first message is a service incident alert and wherein the second message is a related service incident alert. 7 . The method of claim 1 , wherein relationships among the entities are identified based on weighted paths between the entities surpassing a threshold level. 8 . The method of claim 1 , further comprising: sending information describing the at least one association between the services to an entity represented by one of the nodes of the pair of nodes. 9 . An apparatus, comprising: a memory, and a processor configured to execute instructions stored in the memory to: build a relationship network graph having nodes representing entities and edges representing interactions between respective entities, wherein each of the respective entities represents a respective person, a team, or an organization of people; analyze the relationship network graph to identify a pair of nodes having a relationship based on an evaluation between edge paths between the pair of nodes compared to edge paths between other pairs of nodes; and create at least one association between services owned by entities represented by the nodes of a the pair of nodes identifying that the services owned by the entities are dependent on one another. 10 . The apparatus of claim 9 , wherein the processor further executes instructions stored in the memory to: receive records of the interactions; receive contextual information providing context for the interactions; and build interaction information based on the records of the interactions and the contextual information, wherein the relationship network graph is built from the interaction information. 11 . The apparatus of claim 10 , wherein edges between the entities are weighted based on the contextual information. 12 . The apparatus of claim 9 , wherein the processor further executes instructions stored in the memory to: generate a service incident alert for a first service associated with a first entity represented by a first node of the pair of nodes, wherein the service incident alert includes an identification of a second service associated with a second entity represented by a second node of the pair of nodes; and send the service incident alert to the first entity. 13 . The apparatus of claim 12 , wherein relationships among the entities are identified based on weighted paths between the entities surpassing a threshold level. 14 . The apparatus of claim 9 , wherein the processor further executes instructions stored in the memory to: generate a first message for a first service associated with a first node of the pair of nodes; and generate a second message for a second service associated with a second node of the pair of nodes based on the association between the services. 15 . The apparatus of claim 14 , wherein the first message is a service incident alert and wherein the second message is a related service incident alert. 16 . The apparatus of claim 9 , wherein the processor further executes instructions stored in the memory to: deliver information describing at least one association between services to an entity represented by one of the nodes of the pair of nodes. 17 . A system comprising: a memory, and a processor configured to execute instructions stored in the memory to implement services, comprising: an event monitoring service configured to; receive event messages from at least one organization; generate service incidents for services based on the event messages; and send service incident alerts for service incidents, wherein at least one service incident identifies a service based on the event messages and at least one other dependent service; an interaction monitoring service configured to; extract interaction records from communication records of the at least one organization to generate interaction information containing information describing interactions, wherein each of the entities represents a respective person, a team, or an organization of people; a relationship graph builder service configured to; build a relationship graph from the interaction information, the relationship graph comprising nodes representing entities and edges representing interactions between the entities; and a relationship graph analyzer service configured to; identify dependent relations between pairs of nodes in the relationship graph and associate services to entities represented by the pairs of nodes, wherein the event monitoring service identifies the at least one other dependent service based on the at least one other dependent service being associated with a first entity represented by a first node in a pair of nodes and the service identified based on the event messages being represented by a second node in the pair of nodes. 18 . The system of claim 17 , wherein the interaction monitoring service receives contextual information providing context for the interactions between the entities, builds interaction information based on the interaction information and contextual information and the relationship graph builder service includes the contextual information as edge weights in the relationship graph. 19 . The system of claim 17 , wherein the event monitoring service generates secondary service incident alerts for a second entity based on the second entity being represented by the second node in the pair of nodes. 20 . The system of claim 17 , wherein relationships among the entities are identified based on weighted paths

Assignees

Inventors

Classifications

  • involving logical or physical relationship, e.g. grouping and hierarchies · CPC title

  • based on the type or category of the network elements · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US2024259252A1 cover?
Dependencies between services are determined based on the relationships between entities responsible for the services. The relationships are found based on past interactions between the entities. A relationship network graph having nodes representing entities and edges is built representing interactions between respective entities. The relationship network graph is analyzed to identify pairs of…
Who is the assignee on this patent?
Pagerduty Inc
What technology area does this patent fall under?
Primary CPC classification H04L41/0613. Mapped technology areas include Electricity.
When was this patent published?
Publication date Thu Aug 01 2024 00:00:00 GMT+0000 (Coordinated Universal Time) (A1). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 12 related publications on this page (citations in our corpus or others sharing the same primary CPC).