Method and apparatus for identifying an IMS service
US-9210196-B2 · Dec 8, 2015 · US
US9438645B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9438645-B2 |
| Application number | US-201313775205-A |
| Country | US |
| Kind code | B2 |
| Filing date | Feb 24, 2013 |
| Priority date | Dec 4, 2012 |
| Publication date | Sep 6, 2016 |
| Grant date | Sep 6, 2016 |
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.
According to one aspect of the present disclosure, a method and technique for correlating computing network events is disclosed. The method includes: receiving a plurality of events at an event manager residing on a host computing system; identifying a first resource associated with a first event; identifying a second resource associated with a second event; determining whether the first resource is associated with a deployment pattern; determining whether the second resource is associated with a deployment pattern; and responsive to determining that the first and second resources are each associated with a deployment pattern, correlating the first and second events responsive to the first and second resources being associated with a common deployment pattern.
Opening claim text (preview).
What is claimed is: 1. A method, comprising: receiving a plurality of events at an event manager residing on a host computing system; identifying a first resource associated with a first event; identifying a second resource associated with a second event; determining whether the first resource is associated with a first deployment pattern, the first deployment defined by a first template of resources provisioned for a first computing service; determining whether the second resource is associated with a second deployment pattern, the second deployment pattern defined by a second template of resources provisioned for a second computing service; and responsive to determining that the first and second resources are each associated with the respective first and second deployment patterns, correlating the first and second events responsive to the first and second resources being associated with a common deployment pattern. 2. The method of claim 1 , further comprising providing an indication of the correlated events. 3. The method of claim 1 , further comprising: responsive to a request to deploy the first or second resource, identifying the respective first or second deployment pattern corresponding to the request; identifying a target resource for the deployment based on the identified deployment pattern; deploying the target resource; and storing an association of the deployed first or second resource with the respective first or second deployment pattern. 4. The method of claim 2 , wherein providing the indication comprises condensing a plurality of indications of correlated events to a single indication. 5. The method of claim 2 , wherein providing the indication comprises providing a visual indication of the correlated events. 6. A method, comprising: identifying computing resources to be deployed; receiving an identification of a correlation pattern comprising a set of the resources to be deployed; assigning a correlation identifier to the correlation pattern; and configuring each resource of the correlation pattern to include the correlation identifier with an event generated by the respective resource. 7. The method of claim 6 , further comprising: receiving a plurality of events from deployed resources; identifying a correlation identifier associated with each of the plurality of received events; and correlating the events having a common correlation identifier. 8. The method of claim 7 , further comprising providing an indication of the correlated events. 9. The method of claim 6 , further comprising associating the correlation pattern with a deployed application. 10. The method of claim 6 , further comprising providing the correlation identifier to the respective resources of the correlation pattern upon deployment of the respective resources.
based on generic templates · CPC title
Additional information in the notification, e.g. enhancement of specific meta-data · CPC title
by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure · CPC title
involving logical or physical relationship, e.g. grouping and hierarchies · CPC title
for initial configuration or provisioning, e.g. plug-and-play · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.