CN103562863A - Creating a correlation rule defining a relationship between event types - Google Patents
Creating a correlation rule defining a relationship between event types Download PDFInfo
- Publication number
- CN103562863A CN103562863A CN201180071393.XA CN201180071393A CN103562863A CN 103562863 A CN103562863 A CN 103562863A CN 201180071393 A CN201180071393 A CN 201180071393A CN 103562863 A CN103562863 A CN 103562863A
- Authority
- CN
- China
- Prior art keywords
- event
- event type
- relevant
- relation
- configuration
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0751—Error or fault detection not based on redundancy
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/079—Root cause analysis, i.e. error or fault diagnosis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0706—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
- G06F11/0709—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
- H04L41/064—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis involving time analysis
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
- H04L41/065—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis involving logical or physical relationship, e.g. grouping and hierarchies
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
- G06F2201/86—Event-based monitoring
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Health & Medical Sciences (AREA)
- Biomedical Technology (AREA)
- Debugging And Monitoring (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
Plural clusters or occurrences of a pattern of event types are identified (304). Based on configuration items relating to events associated with the event types, a correlation rule is created (308) to define a relationship between the event types.
Description
Technical field
The infotech of enterprise (IT) infrastructure (for example, company, Education Organization, government organs etc.) can comprise relatively large arrangement of components.The IT keeper of enterprise can be assigned the task of managing I T infrastructure together together with other task, comprise the basic reason of the problem that identification detects.Yet it may be complicated managing relatively large IT infrastructure.
Accompanying drawing explanation
About the following drawings, described some embodiment:
Fig. 1 illustrates the example dependency rule that use case correlator creates that passes through according to some embodiments;
Fig. 2 illustrates the sequential chart along with the generation of time according to the event that can process by use case correlator of some embodiments;
Fig. 3 and 4 is according to the process flow diagram of the processing of being carried out by event correlator of some embodiments; And
Fig. 5 is the block diagram being incorporated to according to the example system of the event correlator of some embodiments.
Embodiment
Infotech (IT) infrastructure comprises arrangement of components, the all nextport hardware component NextPorts in this way of described assembly (for example, computing machine, storage server, communicator etc.), component software (for example, application, operating system, driver etc.), database component (for example, related data base management system, unstructured data storehouse system etc.) and/or other assembly., can there is variety of event in the part as the integrated operation of IT infrastructure, described event comprises the event relevant with a difficult problem, fault, problem, or the activity relevant with assembly in IT infrastructure.
Routinely, when being presented the event relevant with a difficult problem, fault, problem or activity, IT keeper is assigned with identification or determines the task of the basic reason of this type of event.Yet for relatively large IT infrastructure, the basic reason of event artificial determines it may is to expend time in and error-prone.
According to some embodiments, provide for automatically creating mechanism or the technology of the dependency rule of the relation between the event that is defined in two or more type separately.By using dependency rule, system can automatically be identified in the correlativity between event type, make system can for given event determine other one or more what caused this given event.By this way, the basic reason of the event relevant with problem, fault, problem or activity can effectively and accurately be identified.
Dependency rule can be specified the reason event of a type as the reason of the sign event of a type.More generally, dependency rule can be specified the reason event as one or more types of the reason of the sign event of one or more types.Reason event refers to the event that causes another event.Sign event is the event being produced by the generation of another event." event " can refer to a difficult problem, fault, problem, activity, operation, input, output or any other generation in IT infrastructure.Event can be classified as dissimilar.For example, one of event type is that database is out of order.The another kind of type of event is that mail service starts.The another kind of type again of event is that application server is shown mistake.There are many other examples of event type.
The example of dependency rule 100 is described in Fig. 1.For example, dependency rule 100 can be presented in display device with graphic form.Dependency rule 100 comprises that its example in Fig. 1 of reason event type 102(is that storer uses rank-approach capacity), described reason event type 102 is that its example in Fig. 1 of sign event type 104(is caching performance-low) reason.In Fig. 1 example, reason event type 102 is associated with allocation of computer project (CI), and sign event type 104 is associated with sql server configuration project.The configuration of configuration project definitions component, such as any other assembly of nextport hardware component NextPort, component software, database component or IT infrastructure." configuration " can comprise the attribute being associated with assembly.Usually, configuration project represents the discrete unit of the configuration relevant with assembly.Configuration project can be relevant with another configuration project (or a plurality of other configuration project).
Fig. 1 also shows the diagrammatic representation 106 of computing machine CI 108, and described computing machine CI 108 is by being related to that 110 are linked to sql server CI 112.In the example of Fig. 1, be related to that 110 is container links, in other words its instruct computer CI 108 comprises sql server 112(, sql server is comprised in computing machine).The dependency rule 100 of Fig. 1 provides the correlativity between event type 102 and 104, event type 102,104 is associated with configuration project 108,112 separately, and has identified the relation between configuration project 108,112 separately.Configuration project (and more specifically, the relevance of the event type configuration project category such as computing machine CI classification 108 and sql server classification 112) and separately provides topological constraints, for be considered relevant corresponding event type according to dependency rule, must meet described topological constraints.
Although the specific example of the form of dependency rule is shown in Figure 1, note, in other embodiments, can use other form of dependency rule.
Information based on dependency rule 100, the special event occurring on (representing as the computing machine CI in Fig. 1) computing machine (using ranks-approach capacity such as 102 storeies that represent in Fig. 1) is likely the reason of the sign event that occurs together with (as the sql server CI 112 in Fig. 1 represents) sql server (for example, 104 caching performances that represent in Fig. 1-low).
According to some embodiments, in order automatically to create dependency rule, can analyze event stream.For example, Fig. 2 illustrates the timeline of event along with the time.In the example of Fig. 2, the transverse axis of four time intervals (t0, t1, t2 and t3) along timeline is identified.In IT infrastructure, event can be grouped into the time interval separately.For example, as shown in FIG. 2, triangle symbol represents the event separately having occurred along with the time.In time interval t0, two events have been there are; In time interval t1, three events have been there are; In time interval t2, five events have been there are; And in time interval t3, three events have been there are.As represented by legend 210,212 and 214, triangle symbol has for representing the different fill pattern of dissimilar event.The event of the first type (210) is the database event type that is out of order, and the event of the second type (212) is that mail server starts event type, and the event of the third type (214) is application server error event type.
For the object of example provides the quantity of illustrated event and the type of event in Fig. 2.In relatively large IT infrastructure, can there is the quantity of much bigger event and the quantity of event type.
Although Fig. 2 has described event to be divided in the time interval, in other embodiments, event can be divided in the division of other type that is different from the time interval.Other division can comprise the division that division that event occurs in different machines or machine group, event occur in the different part of enterprise or department, division that event occurs in different geographic areas etc.
As shown in Figure 2, there is event type pattern, that is, comprise database be out of order event type and pattern application server error event type in time toward each other closely (for example,, within the identical time interval) occur.Each event is associated with event type information, to allow mechanism to determine the type of each event having occurred according to some embodiments.In addition, event also can be associated with the configuration item object information of indicating timestamp that when event occurs and identification to be associated.
As described in Fig. 2, real oval 202A, 202B, 202C and 202D have represented the generation separately of special event type that may be relevant each other (database in the example of Fig. 2 be out of order event type and application server error event type) pattern.Each generation of this event type pattern is the one group of potential relevant event type occurring within the time interval separately substantially.
Notice to be, Fig. 2 also shows the event that the mail server being present in time interval t1, t2 and t3 starts event type.In the example of Fig. 2, mail server starts event and has been confirmed as that with shown in figure 2 other event type is not relevant, and is not therefore identified as a part for the group of relevant event type.For example, because a variety of causes, mail server starts event type can be identified as noise.Event correlator can determine that mail server starts event type and occurs so frequently (with certain the predefine number percent more than the time interval, occurring), makes mail server start event type and is considered to noise and therefore should be not relevant to other event type.Event correlator therefore detection noise event type (than certain predefine threshold value event type more continually) and the relation of other event type is ordinary, and so should not be considered to be correlated with.Alternatively or additionally, event correlator can determine formerly generation that mail server starts event type not to database be out of order event type or application server error event type relevant because the darker analysis of the information being associated with these event types has been indicated to the relation not existing between mail server startup event type and other event type.
Although only show a kind of pattern of (being represented by group 202A-202D) event type in Fig. 2.But note, in other example, can have the various modes of event type.
Fig. 3 is according to for creating the process flow diagram of process of some embodiments of dependency rule.The process of Fig. 3 can be carried out by event correlator, is further discussed below.The reception event (at 302 places) along with past time, all events of describing in the timeline of Fig. 2 in this way of described event.The event receiving can be the archives of event or a part for other collection.
Event correlator is identified the repeatedly generation (group) (at 304 places) of event type pattern in received event according to some embodiments.Event correlator can call group technology being likely the set grouping of relevant event, because they occur together continually or are occurring in special time frame.The kinds of properties of event can be used for event to be divided into a plurality of groups of event type (for example, as shown in Figure 2 the group 202A-202D in a plurality of time intervals).
Then, event correlator is analyzed (at 306 places) and the information that configuration project is associated, and described configuration project is relevant with the event of this event type pattern.Then, in response to determining the dependency rule that creates relation between (at 308 places) definition event type in the analysis of the relation between correspondence configuration project.
Fig. 4 illustrates the further details of the analysis of carrying out at 306 places.In Fig. 4, what event correlator was determined (at 402 places) event type pattern repeatedly meets predefine standard, and described event type pattern comprises the be out of order pattern of event type and application server error event type of database in the example of Fig. 2.The single of special event type pattern occurs or relatively little generation quantity unlikely represents to exist the relation between event type.Yet if the quantity repeatedly occurring of event type pattern or the generation rate of event type pattern have surpassed predetermined threshold value, that can be the event type relevant indication each other of this pattern.In such example, " predefine standard " comprises the generation quantity of this pattern that surpasses predefine threshold value or the generation rate of this pattern.In other example, " predefine standard " can be another kind of standard.
The dependency rule creation task (308) of execution graph 3 in response to the event correlator that repeatedly meets predefine standard of deterministic model.If the repeatedly generation of pattern does not meet predefine standard, event correlator is by the dependency rule creation task (308) of execution graph 3 not.
For each group of event type, this of event correlator identification (at 404 places) and event type organized the set (for example, to) of relevant particular event.Noting, is that particular event is associated with configuration project, makes the identification of the set of particular event allow to access the configuration item object information that (at 406 places) are associated.In the example of Fig. 2 that relates to " database is out of order " event and " application server mistake " event, each " database is out of order " event can be associated with the example of database CI, and each " application server mistake " event can be associated with the example of application server CI.
Next, event correlator determine (at 408 places) particular event associated to configuration project whether be actual relevant.For example, can be for the configuration project implementation Shortest Path Searching of the particular event (particular event) each event centering.If there is not the path between the configuration project being associated in predetermined quantity (zero's or larger) jumping, Shortest Path Searching Algorithm is cancelled the right qualification of event separately.In other example, can use other technology that whether has relation for determining between configuration project.
The information repository that more generally, can be described in the relation between configuration project based on access determines whether (checking) relation between configuration project exists.For example, information repository can be the topological database that is identified in the central topological relation of configuration project.Topological database can be the form of chart, and described chart has corresponding to configuration item destination node separately and the link that is defined in the relation between configuration project.The node of topology chart can be directly link, or by other node indirect link.Two nodes that are directly linked to each other mean that configuration project separately arrives each other by a Path Connection of jumping.Configuration project is jumped and is linked to self by zero degree.If first node is connected to Section Point by the 3rd node, the configuration project separately being associated with the first and second nodes is considered to arrive each other by having the Path Connection of a jumping.More generally, if there is n-1 node between corresponding to a pair of configuration item destination node, this is jumped (n >=1) to configuration project by n and is connected to each other.
In other embodiments, information repository can comprise semantic database, and described semantic database comprises the information that is defined in the relation between configuration project.
Time interval t2 in Fig. 2 illustrates another special problem of the part solution that can be used as analysis (306).If the Multi-instance of the event type pattern of analyzing occurs in short time interval (such as in t2), which in the unclear event being associated is relevant.The candidate that such problem can be used for all possible composition of matter by establishment is to solving, wherein, if configuration project is not separately relevant, those candidate's Disqualifies.In the example of Fig. 2, right imaginary ellipse shape 204A and the 204B of " database is out of order " and " application server mistake " event is cancelled qualification, because the configuration project being associated is not relevant.
In the example of Fig. 2, four pairs of particular events (every pair comprise database be out of order event and application server error event) have been identified.Every pair and the special example of database CI and application server CI in event, and the path-dependent between two CI examples.
Next, different CI examples is abstracted into (at 410 places) CI classification rank to (and their path relation).Each example in configuration project has classification character, described classification property definition configuration item object classification.The dependency rule creating according to some embodiment operation techniques makes configuration item object classification relevant, but not makes configuration item object particular instance relevant.
As an abstract part, also determine the topology of the relation between the configuration project being associated with relevant event type.For example, relevant event type can be associated with the configuration project with relation of inclusion (a configuration project comprises another), or alternatively, determines, a configuration project is relevant with another configuration project by medium object.Determining like this can allow created dependency rule to specify in the topological relation between configuration project category.The form of the dependency rule completing such as the chart 106 with shown in Fig. 1 comprises the information of the relevant event type of identification and the information that relevant configuration project category (with together with their topological relation) is described.Allow topological constraints to be included in dependency rule the comprising of information that relates to relevant configuration item order classification.This topological constraints of dependency rule can be by checking that when determining that whether event type is relevant configuration item types and the relation configuring between item types verify.
According to the technology of some embodiments or mechanism, also can solve about losing the user's concern to the control of system.In order to win IT personnel's acceptance, rule can be generated and is embedded in regular creation instrument.Proposed dependency rule can be presented to user, described user can select to accept dependency rule, the dependency rule that proposes of refusal or revise and/or explain the dependency rule proposing according to present appearance, but not can't help the in the situation that user checking, automatically to inject dependency rule.
Fig. 5 is the block diagram comprising according to the example system 500 of the event correlator 502 of some embodiments, wherein, event correlator 502 is configured to information based on catching in event archives 506 and at database 512(for example, Configuration Management Database (CMDB) or CMDB) in CI information 514 automatically create dependency rule 504.Event archives 506 are included in event 508 on life-span (or certain predefined time interval) of IT infrastructure.The configuration project that CMDB 512 comprises the assembly separately that represents IT infrastructure.
The event 508 being included in event archives 506 can comprise various types of information, such as: problem describe or be associated with each event other describe, the information relevant with user, timestamp, kinds of properties and about the information of associated CI.The kinds of properties being associated with the information that relates to event provides the information about event type.
The event archives 506, database 512 and any dependency rule 504 that by event correlator 502, are created are stored in storage medium 510, described storage medium 510 can be realized with one or more memory storages, the memory storage of all memory storages based on disk in this way of described one or more memory storages, integrated circuit memory storage and/or other type.
System 500 also comprises one or more processors 516, and event correlator 502 is executable on one or more processors 516.In addition, system 500 comprises that network interface 518 communicates by letter with remote system by data network with permission system 500, and all events that produces in this way of described remote system are to be stored in the system in event archives 506.
Although event archives 506 and CMDB 512 are stored in the storage medium of system 500, note, in the example of replacing, event archives 506 and/or CMDB 512 can be stored in remote storage subsystem (or a plurality of remote storage subsystem).
By can automatically creating dependency rule 504, can reduce the professional knowledge that IT keeper or other user expect for the object of the basic reason of identification event.By can automatically creating the dependency rule 504 of the reason that can help automatically to determine sign event, can complete the improvement of efficiency and the reduction of cost in managing I T infrastructure.
The machine readable instructions of event correlator 502 is loaded for carrying out on one or more processors 516.Processor can comprise microprocessor, microcontroller, processor module or subsystem, programmable integrated circuit, programmable gate array or another control or calculation element.
Data and instruction are stored in memory storage separately, and described memory storage is implemented as one or more computer-readables or machinable medium.Storage medium comprises multi-form storer, and it comprises the semiconductor memory system such as dynamic or static random-access memory (DRAM or SRAM), erasable and programmable ROM (read-only memory) (EPROM), electric erasable and programmable ROM (read-only memory) (EEPROM) and flash memories; Disk such as fixed disk, floppy disk and removable disk; Other magnetic medium that comprises tape; Light medium such as CD (CD) or digital video disk (DVD); Or the memory storage of other type.What note is, can in a computer-readable or machine-readable storage media, provide instruction discussed above, or provide instruction discussed above on a plurality of computer-readables that alternatively, can be in being distributed in the large scale system probably with a plurality of nodes or machinable medium.This computer-readable or machine-readable storage media or medium are considered to the part of article (or article of manufacturing).The article of article or manufacture can refer to single component or a plurality of assembly of any manufacture.Storage medium or medium can be arranged in the machine of operation machine readable instructions, or are positioned at remote site place, can from described remote site, download machine readable instructions for execution by network.
In description above, state that many details are to provide the understanding to theme disclosed herein.Yet, can be in the situation that do not have some or all in these details to put into practice embodiment.Other embodiment can comprise the modifications and variations from details discussed above.Be intended that, claims cover this modifications and variations.
Claims (15)
1. a method, comprising:
By the system with processor, receive (302) a plurality of events;
The plural number of being identified (304) event type pattern by described system in received event occurs;
By described systematic analysis (306) configuration item object information, this configuration project is relevant with the event that is associated with described event type pattern; And
In response to the analysis of determining the relation between corresponding configuration project, by described system creation (308), be defined in the dependency rule of the relation between described event type.
2. method claimed in claim 1, further comprises:
Whether the described plural number time generation of determining described event type pattern meets predefine standard,
Wherein, in response to occurring, carries out the described plural number that meets the described pattern of described predefine standard described establishment.
3. method claimed in claim 2, wherein, the described plural number that meets the described pattern of described predefine standard comprises that quantity that the described plural number of described pattern occurs or speed are over predefine threshold value.
4. method claimed in claim 1, wherein, identifies inferior a plurality of groups of comprising the described event type of identification of described plural number of described event type pattern.
5. method claimed in claim 4, wherein, identifies and in described a plurality of groups of time intervals that are included in separately of described event type, identifies described a plurality of groups of described event type.
6. method claimed in claim 1, further comprises:
For each generation of described event type pattern, the correspondence set of identification particular event separately; And
Described in the relevant configuration item object of the described particular event of access in gathering with described in each, information is to carry out described analysis.
7. method claimed in claim 6, wherein, the information described in described configuration item object of analyzing comprises: for the configuration project being associated with set described in each of particular event, determine between described configuration project and whether have path, and wherein, if described path exists, there is relation in described analysis indication between described corresponding configuration project.
8. method claimed in claim 7, wherein, if described path does not exist, there is not relation in described analysis indication between described corresponding configuration project.
9. method claimed in claim 7, wherein, determines and determines between described configuration project whether have the path in predefine jumping figure whether existing described path to comprise between described configuration project.
10. article that comprise at least one machine-readable storage media of storing instruction, described instruction makes the system with processor carry out according to the method for any one in claim 1-9 when carrying out.
11. 1 kinds of systems, comprising:
Storage medium (510), is used for storing the collection of event in infrastructure; And
At least one processor (516), is used for:
Identify at least relevant with the subset of described event special event type pattern a plurality of groups;
The configuration project of the particular event in the described event that access is associated with each group in described a plurality of groups; And
Configuration project based on accessed determines between described event type, whether there is relation; And
According to described definite establishment dependency rule to be defined in the relation between described event type.
System described in 12. claims 11, wherein, described at least one processor is configured to access topology or semantic database exists described relation with checking between described event type.
, wherein, if there is the path in predefined number of rings between accessed configuration project, there is described relation in the system described in 13. claims 12.
System described in 14. claims 11, wherein, described at least one processor will be further:
The configuration item object classification that identification is accessed,
Wherein, described dependency rule makes described in accessed configuration item object classification relevant and make described event type relevant, and wherein, and classification provides the topological constraints that are verified described in the configuration item object of accessing, to determine that whether event type is relevant.
System described in 15. claims 11, wherein, described at least one processor will determine that noise event type is not relevant to other event type.
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/US2011/031056 WO2012138319A1 (en) | 2011-04-04 | 2011-04-04 | Creating a correlation rule defining a relationship between event types |
Publications (1)
Publication Number | Publication Date |
---|---|
CN103562863A true CN103562863A (en) | 2014-02-05 |
Family
ID=46969462
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201180071393.XA Pending CN103562863A (en) | 2011-04-04 | 2011-04-04 | Creating a correlation rule defining a relationship between event types |
Country Status (4)
Country | Link |
---|---|
US (2) | US9612892B2 (en) |
EP (1) | EP2695057A4 (en) |
CN (1) | CN103562863A (en) |
WO (1) | WO2012138319A1 (en) |
Cited By (79)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107491929A (en) * | 2016-06-11 | 2017-12-19 | 苹果公司 | The natural language event detection of data-driven and classification |
CN107832446A (en) * | 2017-11-22 | 2018-03-23 | 联动优势科技有限公司 | A kind of searching method and computing device of configuration item information |
CN108346032A (en) * | 2017-01-23 | 2018-07-31 | 霍尼韦尔国际公司 | The system and method for having the coherent event of the homogeneity in time limit for the trigger process in access control host system |
CN110868472A (en) * | 2019-11-20 | 2020-03-06 | 厦门梓蔓生物科技有限公司 | A project integration system based on IoT PaaS cloud platform and its integration method |
US10720160B2 (en) | 2018-06-01 | 2020-07-21 | Apple Inc. | Voice interaction at a primary device to access call functionality of a companion device |
US10741185B2 (en) | 2010-01-18 | 2020-08-11 | Apple Inc. | Intelligent automated assistant |
US10741181B2 (en) | 2017-05-09 | 2020-08-11 | Apple Inc. | User interface for correcting recognition errors |
US10748546B2 (en) | 2017-05-16 | 2020-08-18 | Apple Inc. | Digital assistant services based on device capabilities |
CN111954857A (en) * | 2018-04-11 | 2020-11-17 | 西门子股份公司 | Determination of the cause of the abnormal event |
US10878809B2 (en) | 2014-05-30 | 2020-12-29 | Apple Inc. | Multi-command single utterance input method |
US10909171B2 (en) | 2017-05-16 | 2021-02-02 | Apple Inc. | Intelligent automated assistant for media exploration |
US10930282B2 (en) | 2015-03-08 | 2021-02-23 | Apple Inc. | Competing devices responding to voice triggers |
US10978090B2 (en) | 2013-02-07 | 2021-04-13 | Apple Inc. | Voice trigger for a digital assistant |
US11009970B2 (en) | 2018-06-01 | 2021-05-18 | Apple Inc. | Attention aware virtual assistant dismissal |
US11010127B2 (en) | 2015-06-29 | 2021-05-18 | Apple Inc. | Virtual assistant for media playback |
US11037565B2 (en) | 2016-06-10 | 2021-06-15 | Apple Inc. | Intelligent digital assistant in a multi-tasking environment |
US11070949B2 (en) | 2015-05-27 | 2021-07-20 | Apple Inc. | Systems and methods for proactively identifying and surfacing relevant content on an electronic device with a touch-sensitive display |
US11087759B2 (en) | 2015-03-08 | 2021-08-10 | Apple Inc. | Virtual assistant activation |
US11120372B2 (en) | 2011-06-03 | 2021-09-14 | Apple Inc. | Performing actions associated with task items that represent tasks to perform |
US11126400B2 (en) | 2015-09-08 | 2021-09-21 | Apple Inc. | Zero latency digital assistant |
US11133008B2 (en) | 2014-05-30 | 2021-09-28 | Apple Inc. | Reducing the need for manual start/end-pointing and trigger phrases |
US11140099B2 (en) | 2019-05-21 | 2021-10-05 | Apple Inc. | Providing message response suggestions |
US11152002B2 (en) | 2016-06-11 | 2021-10-19 | Apple Inc. | Application integration with a digital assistant |
US11169616B2 (en) | 2018-05-07 | 2021-11-09 | Apple Inc. | Raise to speak |
US11217251B2 (en) | 2019-05-06 | 2022-01-04 | Apple Inc. | Spoken notifications |
US11237797B2 (en) | 2019-05-31 | 2022-02-01 | Apple Inc. | User activity shortcut suggestions |
US11257504B2 (en) | 2014-05-30 | 2022-02-22 | Apple Inc. | Intelligent assistant for home automation |
US11269678B2 (en) | 2012-05-15 | 2022-03-08 | Apple Inc. | Systems and methods for integrating third party services with a digital assistant |
US11289073B2 (en) | 2019-05-31 | 2022-03-29 | Apple Inc. | Device text to speech |
US11307752B2 (en) | 2019-05-06 | 2022-04-19 | Apple Inc. | User configurable task triggers |
US11348582B2 (en) | 2008-10-02 | 2022-05-31 | Apple Inc. | Electronic devices with voice command and contextual data processing capabilities |
US11348573B2 (en) | 2019-03-18 | 2022-05-31 | Apple Inc. | Multimodality in digital assistant systems |
US11360641B2 (en) | 2019-06-01 | 2022-06-14 | Apple Inc. | Increasing the relevance of new available information |
US11380310B2 (en) | 2017-05-12 | 2022-07-05 | Apple Inc. | Low-latency intelligent automated assistant |
US11388291B2 (en) | 2013-03-14 | 2022-07-12 | Apple Inc. | System and method for processing voicemail |
US11405466B2 (en) | 2017-05-12 | 2022-08-02 | Apple Inc. | Synchronization and task delegation of a digital assistant |
US11423886B2 (en) | 2010-01-18 | 2022-08-23 | Apple Inc. | Task flow identification based on user intent |
US11423908B2 (en) | 2019-05-06 | 2022-08-23 | Apple Inc. | Interpreting spoken requests |
US11431642B2 (en) | 2018-06-01 | 2022-08-30 | Apple Inc. | Variable latency device coordination |
US11468282B2 (en) | 2015-05-15 | 2022-10-11 | Apple Inc. | Virtual assistant in a communication session |
US11467802B2 (en) | 2017-05-11 | 2022-10-11 | Apple Inc. | Maintaining privacy of personal information |
US11475884B2 (en) | 2019-05-06 | 2022-10-18 | Apple Inc. | Reducing digital assistant latency when a language is incorrectly determined |
US11475898B2 (en) | 2018-10-26 | 2022-10-18 | Apple Inc. | Low-latency multi-speaker speech recognition |
US11488406B2 (en) | 2019-09-25 | 2022-11-01 | Apple Inc. | Text detection using global geometry estimators |
US11496600B2 (en) | 2019-05-31 | 2022-11-08 | Apple Inc. | Remote execution of machine-learned models |
US11500672B2 (en) | 2015-09-08 | 2022-11-15 | Apple Inc. | Distributed personal assistant |
US11516537B2 (en) | 2014-06-30 | 2022-11-29 | Apple Inc. | Intelligent automated assistant for TV user interactions |
US11526368B2 (en) | 2015-11-06 | 2022-12-13 | Apple Inc. | Intelligent automated assistant in a messaging environment |
US11532306B2 (en) | 2017-05-16 | 2022-12-20 | Apple Inc. | Detecting a trigger of a digital assistant |
US11580990B2 (en) | 2017-05-12 | 2023-02-14 | Apple Inc. | User-specific acoustic models |
US11599331B2 (en) | 2017-05-11 | 2023-03-07 | Apple Inc. | Maintaining privacy of personal information |
US11638059B2 (en) | 2019-01-04 | 2023-04-25 | Apple Inc. | Content playback on multiple devices |
US11656884B2 (en) | 2017-01-09 | 2023-05-23 | Apple Inc. | Application integration with a digital assistant |
US11657813B2 (en) | 2019-05-31 | 2023-05-23 | Apple Inc. | Voice identification in digital assistant systems |
US11671920B2 (en) | 2007-04-03 | 2023-06-06 | Apple Inc. | Method and system for operating a multifunction portable electronic device using voice-activation |
US11696060B2 (en) | 2020-07-21 | 2023-07-04 | Apple Inc. | User identification using headphones |
US11710482B2 (en) | 2018-03-26 | 2023-07-25 | Apple Inc. | Natural assistant interaction |
US11727219B2 (en) | 2013-06-09 | 2023-08-15 | Apple Inc. | System and method for inferring user intent from speech inputs |
US11755276B2 (en) | 2020-05-12 | 2023-09-12 | Apple Inc. | Reducing description length based on confidence |
US11765209B2 (en) | 2020-05-11 | 2023-09-19 | Apple Inc. | Digital assistant hardware abstraction |
US11790914B2 (en) | 2019-06-01 | 2023-10-17 | Apple Inc. | Methods and user interfaces for voice-based control of electronic devices |
US11798547B2 (en) | 2013-03-15 | 2023-10-24 | Apple Inc. | Voice activated device for use with a voice-based digital assistant |
US11809483B2 (en) | 2015-09-08 | 2023-11-07 | Apple Inc. | Intelligent automated assistant for media search and playback |
US11809783B2 (en) | 2016-06-11 | 2023-11-07 | Apple Inc. | Intelligent device arbitration and control |
US11838734B2 (en) | 2020-07-20 | 2023-12-05 | Apple Inc. | Multi-device audio adjustment coordination |
US11853536B2 (en) | 2015-09-08 | 2023-12-26 | Apple Inc. | Intelligent automated assistant in a media environment |
US11853647B2 (en) | 2015-12-23 | 2023-12-26 | Apple Inc. | Proactive assistance based on dialog communication between devices |
US11854539B2 (en) | 2018-05-07 | 2023-12-26 | Apple Inc. | Intelligent automated assistant for delivering content from user experiences |
US11886805B2 (en) | 2015-11-09 | 2024-01-30 | Apple Inc. | Unconventional virtual assistant interactions |
US11893992B2 (en) | 2018-09-28 | 2024-02-06 | Apple Inc. | Multi-modal inputs for voice commands |
US11914848B2 (en) | 2020-05-11 | 2024-02-27 | Apple Inc. | Providing relevant data items based on context |
US11928604B2 (en) | 2005-09-08 | 2024-03-12 | Apple Inc. | Method and apparatus for building an intelligent automated assistant |
US12010262B2 (en) | 2013-08-06 | 2024-06-11 | Apple Inc. | Auto-activating smart responses based on activities from remote devices |
US12014118B2 (en) | 2017-05-15 | 2024-06-18 | Apple Inc. | Multi-modal interfaces having selection disambiguation and text modification capability |
US12051413B2 (en) | 2015-09-30 | 2024-07-30 | Apple Inc. | Intelligent device identification |
US12067985B2 (en) | 2018-06-01 | 2024-08-20 | Apple Inc. | Virtual assistant operations in multi-device environments |
US12073147B2 (en) | 2013-06-09 | 2024-08-27 | Apple Inc. | Device, method, and graphical user interface for enabling conversation persistence across two or more instances of a digital assistant |
US12197817B2 (en) | 2016-06-11 | 2025-01-14 | Apple Inc. | Intelligent device arbitration and control |
US12223282B2 (en) | 2016-06-09 | 2025-02-11 | Apple Inc. | Intelligent automated assistant in a home environment |
Families Citing this family (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11068954B2 (en) | 2015-11-20 | 2021-07-20 | Voicemonk Inc | System for virtual agents to help customers and businesses |
US9298538B2 (en) * | 2012-08-16 | 2016-03-29 | Vmware, Inc. | Methods and systems for abnormality analysis of streamed log data |
US9172621B1 (en) * | 2013-04-01 | 2015-10-27 | Amazon Technologies, Inc. | Unified account metadata management |
US10552746B2 (en) | 2014-09-25 | 2020-02-04 | International Business Machines Corporation | Identification of time lagged indicators for events with a window period |
US10616040B2 (en) | 2015-11-10 | 2020-04-07 | Telefonaktiebolaget Lm Ericsson (Publ) | Managing network alarms |
JP2017182441A (en) * | 2016-03-30 | 2017-10-05 | 富士通株式会社 | Work condition processing apparatus, method, and program |
US10469309B1 (en) * | 2016-04-28 | 2019-11-05 | Servicenow, Inc. | Management of computing system alerts |
US20170315855A1 (en) * | 2016-05-02 | 2017-11-02 | Agt International Gmbh | Method of detecting anomalies on appliances and system thereof |
CN108322320B (en) * | 2017-01-18 | 2020-04-28 | 华为技术有限公司 | Business survivability analysis method and device |
KR101965839B1 (en) | 2017-08-18 | 2019-04-05 | 주식회사 티맥스 소프트 | It system fault analysis technique based on configuration management database |
KR101910926B1 (en) | 2017-09-13 | 2018-10-23 | 주식회사 티맥스 소프트 | Technique for processing fault event of it system |
US10805144B1 (en) * | 2019-06-18 | 2020-10-13 | Cisco Technology, Inc. | Monitoring interactions between entities in a network by an agent for particular types of interactions and indexing and establishing relationships of the components of each interaction |
US20250045140A1 (en) * | 2023-08-01 | 2025-02-06 | Servicenow, Inc. | Alert filtering based on service to facilitate triage |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1332867A (en) * | 1998-12-31 | 2002-01-23 | 联合想象计算机公司 | System and method for dynamic correlation of events |
TW200821960A (en) * | 2006-11-08 | 2008-05-16 | Inst Information Industry | Method and system for complex event processing |
US20110055138A1 (en) * | 2009-08-27 | 2011-03-03 | Vaibhav Khanduja | Method and system for processing network activity data |
Family Cites Families (25)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5528516A (en) | 1994-05-25 | 1996-06-18 | System Management Arts, Inc. | Apparatus and method for event correlation and problem reporting |
US5483637A (en) * | 1994-06-27 | 1996-01-09 | International Business Machines Corporation | Expert based system and method for managing error events in a local area network |
US6154849A (en) * | 1998-06-30 | 2000-11-28 | Sun Microsystems, Inc. | Method and apparatus for resource dependency relaxation |
GB0127551D0 (en) * | 2001-11-16 | 2002-01-09 | Abb Ab | Analysing events |
US7089250B2 (en) * | 2003-10-08 | 2006-08-08 | International Business Machines Corporation | Method and system for associating events |
US20050091356A1 (en) * | 2003-10-24 | 2005-04-28 | Matthew Izzo | Method and machine-readable medium for using matrices to automatically analyze network events and objects |
US20050222810A1 (en) * | 2004-04-03 | 2005-10-06 | Altusys Corp | Method and Apparatus for Coordination of a Situation Manager and Event Correlation in Situation-Based Management |
US7631222B2 (en) * | 2004-08-23 | 2009-12-08 | Cisco Technology, Inc. | Method and apparatus for correlating events in a network |
US7730494B1 (en) * | 2005-04-20 | 2010-06-01 | At&T Corp. | Methods and apparatus for service and network management event correlation |
US8661113B2 (en) | 2006-05-09 | 2014-02-25 | International Business Machines Corporation | Cross-cutting detection of event patterns |
US20080103847A1 (en) | 2006-10-31 | 2008-05-01 | Mehmet Sayal | Data Prediction for business process metrics |
US8655623B2 (en) * | 2007-02-13 | 2014-02-18 | International Business Machines Corporation | Diagnostic system and method |
US7889666B1 (en) | 2007-12-26 | 2011-02-15 | At&T Intellectual Property Ii, L.P. | Scalable and robust troubleshooting framework for VPN backbones |
US20090177692A1 (en) | 2008-01-04 | 2009-07-09 | Byran Christopher Chagoly | Dynamic correlation of service oriented architecture resource relationship and metrics to isolate problem sources |
US20090183030A1 (en) * | 2008-01-14 | 2009-07-16 | Bethke Bob | Episodic cause analysis |
US20100070981A1 (en) | 2008-09-16 | 2010-03-18 | Computer Associates Think, Inc. | System and Method for Performing Complex Event Processing |
US20100131315A1 (en) | 2008-11-25 | 2010-05-27 | International Business Machines Corporation | Resolving incident reports |
US8069374B2 (en) * | 2009-02-27 | 2011-11-29 | Microsoft Corporation | Fingerprinting event logs for system management troubleshooting |
US8464279B2 (en) * | 2009-12-18 | 2013-06-11 | Hewlett-Packard Development Company, L.P. | Domain event correlation |
JP5564941B2 (en) * | 2009-12-28 | 2014-08-06 | 富士通株式会社 | Fault location estimation system, fault location estimation apparatus, and fault location estimation method |
JP5428934B2 (en) * | 2010-02-22 | 2014-02-26 | 富士通株式会社 | Failure pattern generation program and failure pattern generation device |
JPWO2011111599A1 (en) * | 2010-03-11 | 2013-06-27 | 日本電気株式会社 | Failure analysis rule extraction device, failure analysis rule extraction method, and storage medium |
US9213590B2 (en) * | 2012-06-27 | 2015-12-15 | Brocade Communications Systems, Inc. | Network monitoring and diagnostics |
US9229898B2 (en) * | 2012-07-30 | 2016-01-05 | Hewlett Packard Enterprise Development Lp | Causation isolation using a configuration item metric identified based on event classification |
US9558056B2 (en) * | 2013-07-28 | 2017-01-31 | OpsClarity Inc. | Organizing network performance metrics into historical anomaly dependency data |
-
2011
- 2011-04-04 US US14/008,940 patent/US9612892B2/en active Active
- 2011-04-04 EP EP11863207.4A patent/EP2695057A4/en not_active Withdrawn
- 2011-04-04 WO PCT/US2011/031056 patent/WO2012138319A1/en active Application Filing
- 2011-04-04 CN CN201180071393.XA patent/CN103562863A/en active Pending
-
2017
- 2017-03-16 US US15/460,608 patent/US20170185468A1/en not_active Abandoned
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1332867A (en) * | 1998-12-31 | 2002-01-23 | 联合想象计算机公司 | System and method for dynamic correlation of events |
TW200821960A (en) * | 2006-11-08 | 2008-05-16 | Inst Information Industry | Method and system for complex event processing |
US20110055138A1 (en) * | 2009-08-27 | 2011-03-03 | Vaibhav Khanduja | Method and system for processing network activity data |
Cited By (139)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11928604B2 (en) | 2005-09-08 | 2024-03-12 | Apple Inc. | Method and apparatus for building an intelligent automated assistant |
US11671920B2 (en) | 2007-04-03 | 2023-06-06 | Apple Inc. | Method and system for operating a multifunction portable electronic device using voice-activation |
US11979836B2 (en) | 2007-04-03 | 2024-05-07 | Apple Inc. | Method and system for operating a multi-function portable electronic device using voice-activation |
US11348582B2 (en) | 2008-10-02 | 2022-05-31 | Apple Inc. | Electronic devices with voice command and contextual data processing capabilities |
US11900936B2 (en) | 2008-10-02 | 2024-02-13 | Apple Inc. | Electronic devices with voice command and contextual data processing capabilities |
US12165635B2 (en) | 2010-01-18 | 2024-12-10 | Apple Inc. | Intelligent automated assistant |
US12087308B2 (en) | 2010-01-18 | 2024-09-10 | Apple Inc. | Intelligent automated assistant |
US10741185B2 (en) | 2010-01-18 | 2020-08-11 | Apple Inc. | Intelligent automated assistant |
US11423886B2 (en) | 2010-01-18 | 2022-08-23 | Apple Inc. | Task flow identification based on user intent |
US11120372B2 (en) | 2011-06-03 | 2021-09-14 | Apple Inc. | Performing actions associated with task items that represent tasks to perform |
US11321116B2 (en) | 2012-05-15 | 2022-05-03 | Apple Inc. | Systems and methods for integrating third party services with a digital assistant |
US11269678B2 (en) | 2012-05-15 | 2022-03-08 | Apple Inc. | Systems and methods for integrating third party services with a digital assistant |
US11862186B2 (en) | 2013-02-07 | 2024-01-02 | Apple Inc. | Voice trigger for a digital assistant |
US10978090B2 (en) | 2013-02-07 | 2021-04-13 | Apple Inc. | Voice trigger for a digital assistant |
US11636869B2 (en) | 2013-02-07 | 2023-04-25 | Apple Inc. | Voice trigger for a digital assistant |
US11557310B2 (en) | 2013-02-07 | 2023-01-17 | Apple Inc. | Voice trigger for a digital assistant |
US12009007B2 (en) | 2013-02-07 | 2024-06-11 | Apple Inc. | Voice trigger for a digital assistant |
US11388291B2 (en) | 2013-03-14 | 2022-07-12 | Apple Inc. | System and method for processing voicemail |
US11798547B2 (en) | 2013-03-15 | 2023-10-24 | Apple Inc. | Voice activated device for use with a voice-based digital assistant |
US11727219B2 (en) | 2013-06-09 | 2023-08-15 | Apple Inc. | System and method for inferring user intent from speech inputs |
US12073147B2 (en) | 2013-06-09 | 2024-08-27 | Apple Inc. | Device, method, and graphical user interface for enabling conversation persistence across two or more instances of a digital assistant |
US12010262B2 (en) | 2013-08-06 | 2024-06-11 | Apple Inc. | Auto-activating smart responses based on activities from remote devices |
US11670289B2 (en) | 2014-05-30 | 2023-06-06 | Apple Inc. | Multi-command single utterance input method |
US11133008B2 (en) | 2014-05-30 | 2021-09-28 | Apple Inc. | Reducing the need for manual start/end-pointing and trigger phrases |
US11699448B2 (en) | 2014-05-30 | 2023-07-11 | Apple Inc. | Intelligent assistant for home automation |
US12118999B2 (en) | 2014-05-30 | 2024-10-15 | Apple Inc. | Reducing the need for manual start/end-pointing and trigger phrases |
US12067990B2 (en) | 2014-05-30 | 2024-08-20 | Apple Inc. | Intelligent assistant for home automation |
US10878809B2 (en) | 2014-05-30 | 2020-12-29 | Apple Inc. | Multi-command single utterance input method |
US11810562B2 (en) | 2014-05-30 | 2023-11-07 | Apple Inc. | Reducing the need for manual start/end-pointing and trigger phrases |
US11257504B2 (en) | 2014-05-30 | 2022-02-22 | Apple Inc. | Intelligent assistant for home automation |
US11838579B2 (en) | 2014-06-30 | 2023-12-05 | Apple Inc. | Intelligent automated assistant for TV user interactions |
US11516537B2 (en) | 2014-06-30 | 2022-11-29 | Apple Inc. | Intelligent automated assistant for TV user interactions |
US12200297B2 (en) | 2014-06-30 | 2025-01-14 | Apple Inc. | Intelligent automated assistant for TV user interactions |
US11087759B2 (en) | 2015-03-08 | 2021-08-10 | Apple Inc. | Virtual assistant activation |
US12236952B2 (en) | 2015-03-08 | 2025-02-25 | Apple Inc. | Virtual assistant activation |
US10930282B2 (en) | 2015-03-08 | 2021-02-23 | Apple Inc. | Competing devices responding to voice triggers |
US11842734B2 (en) | 2015-03-08 | 2023-12-12 | Apple Inc. | Virtual assistant activation |
US12001933B2 (en) | 2015-05-15 | 2024-06-04 | Apple Inc. | Virtual assistant in a communication session |
US12154016B2 (en) | 2015-05-15 | 2024-11-26 | Apple Inc. | Virtual assistant in a communication session |
US11468282B2 (en) | 2015-05-15 | 2022-10-11 | Apple Inc. | Virtual assistant in a communication session |
US11070949B2 (en) | 2015-05-27 | 2021-07-20 | Apple Inc. | Systems and methods for proactively identifying and surfacing relevant content on an electronic device with a touch-sensitive display |
US11947873B2 (en) | 2015-06-29 | 2024-04-02 | Apple Inc. | Virtual assistant for media playback |
US11010127B2 (en) | 2015-06-29 | 2021-05-18 | Apple Inc. | Virtual assistant for media playback |
US11809483B2 (en) | 2015-09-08 | 2023-11-07 | Apple Inc. | Intelligent automated assistant for media search and playback |
US11550542B2 (en) | 2015-09-08 | 2023-01-10 | Apple Inc. | Zero latency digital assistant |
US11853536B2 (en) | 2015-09-08 | 2023-12-26 | Apple Inc. | Intelligent automated assistant in a media environment |
US12204932B2 (en) | 2015-09-08 | 2025-01-21 | Apple Inc. | Distributed personal assistant |
US11126400B2 (en) | 2015-09-08 | 2021-09-21 | Apple Inc. | Zero latency digital assistant |
US11500672B2 (en) | 2015-09-08 | 2022-11-15 | Apple Inc. | Distributed personal assistant |
US11954405B2 (en) | 2015-09-08 | 2024-04-09 | Apple Inc. | Zero latency digital assistant |
US12051413B2 (en) | 2015-09-30 | 2024-07-30 | Apple Inc. | Intelligent device identification |
US11526368B2 (en) | 2015-11-06 | 2022-12-13 | Apple Inc. | Intelligent automated assistant in a messaging environment |
US11809886B2 (en) | 2015-11-06 | 2023-11-07 | Apple Inc. | Intelligent automated assistant in a messaging environment |
US11886805B2 (en) | 2015-11-09 | 2024-01-30 | Apple Inc. | Unconventional virtual assistant interactions |
US11853647B2 (en) | 2015-12-23 | 2023-12-26 | Apple Inc. | Proactive assistance based on dialog communication between devices |
US12223282B2 (en) | 2016-06-09 | 2025-02-11 | Apple Inc. | Intelligent automated assistant in a home environment |
US11657820B2 (en) | 2016-06-10 | 2023-05-23 | Apple Inc. | Intelligent digital assistant in a multi-tasking environment |
US12175977B2 (en) | 2016-06-10 | 2024-12-24 | Apple Inc. | Intelligent digital assistant in a multi-tasking environment |
US11037565B2 (en) | 2016-06-10 | 2021-06-15 | Apple Inc. | Intelligent digital assistant in a multi-tasking environment |
US12197817B2 (en) | 2016-06-11 | 2025-01-14 | Apple Inc. | Intelligent device arbitration and control |
US10521466B2 (en) | 2016-06-11 | 2019-12-31 | Apple Inc. | Data driven natural language event detection and classification |
CN107491929A (en) * | 2016-06-11 | 2017-12-19 | 苹果公司 | The natural language event detection of data-driven and classification |
US11152002B2 (en) | 2016-06-11 | 2021-10-19 | Apple Inc. | Application integration with a digital assistant |
US11809783B2 (en) | 2016-06-11 | 2023-11-07 | Apple Inc. | Intelligent device arbitration and control |
US11749275B2 (en) | 2016-06-11 | 2023-09-05 | Apple Inc. | Application integration with a digital assistant |
US12260234B2 (en) | 2017-01-09 | 2025-03-25 | Apple Inc. | Application integration with a digital assistant |
US11656884B2 (en) | 2017-01-09 | 2023-05-23 | Apple Inc. | Application integration with a digital assistant |
CN108346032A (en) * | 2017-01-23 | 2018-07-31 | 霍尼韦尔国际公司 | The system and method for having the coherent event of the homogeneity in time limit for the trigger process in access control host system |
CN108346032B (en) * | 2017-01-23 | 2023-07-11 | 霍尼韦尔国际公司 | System and method for time-limited homogeneous coherence events triggering a procedure in an access control host system |
US10741181B2 (en) | 2017-05-09 | 2020-08-11 | Apple Inc. | User interface for correcting recognition errors |
US11599331B2 (en) | 2017-05-11 | 2023-03-07 | Apple Inc. | Maintaining privacy of personal information |
US11467802B2 (en) | 2017-05-11 | 2022-10-11 | Apple Inc. | Maintaining privacy of personal information |
US11862151B2 (en) | 2017-05-12 | 2024-01-02 | Apple Inc. | Low-latency intelligent automated assistant |
US11380310B2 (en) | 2017-05-12 | 2022-07-05 | Apple Inc. | Low-latency intelligent automated assistant |
US11837237B2 (en) | 2017-05-12 | 2023-12-05 | Apple Inc. | User-specific acoustic models |
US11538469B2 (en) | 2017-05-12 | 2022-12-27 | Apple Inc. | Low-latency intelligent automated assistant |
US11405466B2 (en) | 2017-05-12 | 2022-08-02 | Apple Inc. | Synchronization and task delegation of a digital assistant |
US11580990B2 (en) | 2017-05-12 | 2023-02-14 | Apple Inc. | User-specific acoustic models |
US12014118B2 (en) | 2017-05-15 | 2024-06-18 | Apple Inc. | Multi-modal interfaces having selection disambiguation and text modification capability |
US10909171B2 (en) | 2017-05-16 | 2021-02-02 | Apple Inc. | Intelligent automated assistant for media exploration |
US12254887B2 (en) | 2017-05-16 | 2025-03-18 | Apple Inc. | Far-field extension of digital assistant services for providing a notification of an event to a user |
US10748546B2 (en) | 2017-05-16 | 2020-08-18 | Apple Inc. | Digital assistant services based on device capabilities |
US12026197B2 (en) | 2017-05-16 | 2024-07-02 | Apple Inc. | Intelligent automated assistant for media exploration |
US11532306B2 (en) | 2017-05-16 | 2022-12-20 | Apple Inc. | Detecting a trigger of a digital assistant |
US11675829B2 (en) | 2017-05-16 | 2023-06-13 | Apple Inc. | Intelligent automated assistant for media exploration |
CN107832446B (en) * | 2017-11-22 | 2020-07-14 | 联动优势科技有限公司 | Configuration item information searching method and computing device |
CN107832446A (en) * | 2017-11-22 | 2018-03-23 | 联动优势科技有限公司 | A kind of searching method and computing device of configuration item information |
US11710482B2 (en) | 2018-03-26 | 2023-07-25 | Apple Inc. | Natural assistant interaction |
US12211502B2 (en) | 2018-03-26 | 2025-01-28 | Apple Inc. | Natural assistant interaction |
CN111954857A (en) * | 2018-04-11 | 2020-11-17 | 西门子股份公司 | Determination of the cause of the abnormal event |
US11854539B2 (en) | 2018-05-07 | 2023-12-26 | Apple Inc. | Intelligent automated assistant for delivering content from user experiences |
US11487364B2 (en) | 2018-05-07 | 2022-11-01 | Apple Inc. | Raise to speak |
US11907436B2 (en) | 2018-05-07 | 2024-02-20 | Apple Inc. | Raise to speak |
US11900923B2 (en) | 2018-05-07 | 2024-02-13 | Apple Inc. | Intelligent automated assistant for delivering content from user experiences |
US11169616B2 (en) | 2018-05-07 | 2021-11-09 | Apple Inc. | Raise to speak |
US12061752B2 (en) | 2018-06-01 | 2024-08-13 | Apple Inc. | Attention aware virtual assistant dismissal |
US12080287B2 (en) | 2018-06-01 | 2024-09-03 | Apple Inc. | Voice interaction at a primary device to access call functionality of a companion device |
US11360577B2 (en) | 2018-06-01 | 2022-06-14 | Apple Inc. | Attention aware virtual assistant dismissal |
US11009970B2 (en) | 2018-06-01 | 2021-05-18 | Apple Inc. | Attention aware virtual assistant dismissal |
US11431642B2 (en) | 2018-06-01 | 2022-08-30 | Apple Inc. | Variable latency device coordination |
US10984798B2 (en) | 2018-06-01 | 2021-04-20 | Apple Inc. | Voice interaction at a primary device to access call functionality of a companion device |
US12067985B2 (en) | 2018-06-01 | 2024-08-20 | Apple Inc. | Virtual assistant operations in multi-device environments |
US11630525B2 (en) | 2018-06-01 | 2023-04-18 | Apple Inc. | Attention aware virtual assistant dismissal |
US10720160B2 (en) | 2018-06-01 | 2020-07-21 | Apple Inc. | Voice interaction at a primary device to access call functionality of a companion device |
US11893992B2 (en) | 2018-09-28 | 2024-02-06 | Apple Inc. | Multi-modal inputs for voice commands |
US11475898B2 (en) | 2018-10-26 | 2022-10-18 | Apple Inc. | Low-latency multi-speaker speech recognition |
US11638059B2 (en) | 2019-01-04 | 2023-04-25 | Apple Inc. | Content playback on multiple devices |
US11783815B2 (en) | 2019-03-18 | 2023-10-10 | Apple Inc. | Multimodality in digital assistant systems |
US11348573B2 (en) | 2019-03-18 | 2022-05-31 | Apple Inc. | Multimodality in digital assistant systems |
US12136419B2 (en) | 2019-03-18 | 2024-11-05 | Apple Inc. | Multimodality in digital assistant systems |
US12216894B2 (en) | 2019-05-06 | 2025-02-04 | Apple Inc. | User configurable task triggers |
US11307752B2 (en) | 2019-05-06 | 2022-04-19 | Apple Inc. | User configurable task triggers |
US12154571B2 (en) | 2019-05-06 | 2024-11-26 | Apple Inc. | Spoken notifications |
US11705130B2 (en) | 2019-05-06 | 2023-07-18 | Apple Inc. | Spoken notifications |
US11217251B2 (en) | 2019-05-06 | 2022-01-04 | Apple Inc. | Spoken notifications |
US11675491B2 (en) | 2019-05-06 | 2023-06-13 | Apple Inc. | User configurable task triggers |
US11423908B2 (en) | 2019-05-06 | 2022-08-23 | Apple Inc. | Interpreting spoken requests |
US11475884B2 (en) | 2019-05-06 | 2022-10-18 | Apple Inc. | Reducing digital assistant latency when a language is incorrectly determined |
US11888791B2 (en) | 2019-05-21 | 2024-01-30 | Apple Inc. | Providing message response suggestions |
US11140099B2 (en) | 2019-05-21 | 2021-10-05 | Apple Inc. | Providing message response suggestions |
US11496600B2 (en) | 2019-05-31 | 2022-11-08 | Apple Inc. | Remote execution of machine-learned models |
US11657813B2 (en) | 2019-05-31 | 2023-05-23 | Apple Inc. | Voice identification in digital assistant systems |
US11237797B2 (en) | 2019-05-31 | 2022-02-01 | Apple Inc. | User activity shortcut suggestions |
US11289073B2 (en) | 2019-05-31 | 2022-03-29 | Apple Inc. | Device text to speech |
US11360739B2 (en) | 2019-05-31 | 2022-06-14 | Apple Inc. | User activity shortcut suggestions |
US11790914B2 (en) | 2019-06-01 | 2023-10-17 | Apple Inc. | Methods and user interfaces for voice-based control of electronic devices |
US11360641B2 (en) | 2019-06-01 | 2022-06-14 | Apple Inc. | Increasing the relevance of new available information |
US11488406B2 (en) | 2019-09-25 | 2022-11-01 | Apple Inc. | Text detection using global geometry estimators |
CN110868472A (en) * | 2019-11-20 | 2020-03-06 | 厦门梓蔓生物科技有限公司 | A project integration system based on IoT PaaS cloud platform and its integration method |
CN110868472B (en) * | 2019-11-20 | 2022-06-07 | 厦门梓蔓生物科技有限公司 | Project integration system based on Internet of things PaaS cloud platform and integration method thereof |
US12197712B2 (en) | 2020-05-11 | 2025-01-14 | Apple Inc. | Providing relevant data items based on context |
US11765209B2 (en) | 2020-05-11 | 2023-09-19 | Apple Inc. | Digital assistant hardware abstraction |
US11914848B2 (en) | 2020-05-11 | 2024-02-27 | Apple Inc. | Providing relevant data items based on context |
US11924254B2 (en) | 2020-05-11 | 2024-03-05 | Apple Inc. | Digital assistant hardware abstraction |
US11755276B2 (en) | 2020-05-12 | 2023-09-12 | Apple Inc. | Reducing description length based on confidence |
US11838734B2 (en) | 2020-07-20 | 2023-12-05 | Apple Inc. | Multi-device audio adjustment coordination |
US11750962B2 (en) | 2020-07-21 | 2023-09-05 | Apple Inc. | User identification using headphones |
US11696060B2 (en) | 2020-07-21 | 2023-07-04 | Apple Inc. | User identification using headphones |
US12219314B2 (en) | 2020-07-21 | 2025-02-04 | Apple Inc. | User identification using headphones |
Also Published As
Publication number | Publication date |
---|---|
WO2012138319A1 (en) | 2012-10-11 |
EP2695057A4 (en) | 2015-07-01 |
US20170185468A1 (en) | 2017-06-29 |
US20140025998A1 (en) | 2014-01-23 |
EP2695057A1 (en) | 2014-02-12 |
US9612892B2 (en) | 2017-04-04 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN103562863A (en) | Creating a correlation rule defining a relationship between event types | |
US10067788B2 (en) | Automated invalidation of job output data in a job processing system | |
US11061756B2 (en) | Enabling symptom verification | |
US20160196201A1 (en) | Module specific tracing in a shared module environment | |
US20070214391A1 (en) | Method and apparatus for testing software | |
CN111800450A (en) | Multidimensional tag namespaces for cloud resource management | |
CN111240876B (en) | Fault positioning method and device for micro-service, storage medium and terminal | |
Mancini et al. | Anytime system level verification via random exhaustive hardware in the loop simulation | |
US20130212155A1 (en) | Processing event instance data in a client-server architecture | |
Sadeghianasl et al. | A contextual approach to detecting synonymous and polluted activity labels in process event logs | |
KR20150118963A (en) | Queue monitoring and visualization | |
CN107832446B (en) | Configuration item information searching method and computing device | |
JP2011138405A (en) | System, apparatus and method for estimating failure part | |
US20130036367A1 (en) | Updating a user Interface | |
CN102567185A (en) | Monitoring method of application server | |
Ali et al. | [Retracted] Classification and Prediction of Software Incidents Using Machine Learning Techniques | |
CN116756021A (en) | Fault location methods, devices, electronic equipment and media based on event analysis | |
US20170032300A1 (en) | Dynamic selection of resources on which an action is performed | |
Allcock et al. | Challenges of hpc monitoring | |
US20130173777A1 (en) | Mining Execution Pattern For System Performance Diagnostics | |
US12158828B1 (en) | Correlating application performance to external events | |
CN113742116A (en) | Abnormity positioning method, abnormity positioning device, abnormity positioning equipment and storage medium | |
Wang et al. | Minimal functional routes in directed graphs with dependent edges | |
Kumar | Software Engineering for Big Data Systems | |
CN112463570B (en) | Log statistics method, device and system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
C06 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
WD01 | Invention patent application deemed withdrawn after publication | ||
WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20140205 |