会员体验
专利管家(专利管理)
工作空间(专利管理)
风险监控(情报监控)
数据分析(专利分析)
侵权分析(诉讼无效)
联系我们
交流群
官方交流:
QQ群: 891211   
微信请扫码    >>>
现在联系顾问~
热词
    • 1. 发明授权
    • Root cause problem identification through event correlation
    • 通过事件相关的根本原因问题识别
    • US08060782B2
    • 2011-11-15
    • US12714842
    • 2010-03-01
    • Ziv CaspiRon E. Dar ZivYifat OrlinAlexander SloutskyItai Frenkel
    • Ziv CaspiRon E. Dar ZivYifat OrlinAlexander SloutskyItai Frenkel
    • G06F11/00
    • G06F11/079G06F11/0709G06F11/0715H04L41/064H04L41/0686
    • Correlating activity events to identify a root cause of a process failure. Activity event data is received from a process executing on a computing device. The activity event data corresponds to a plurality of activity events. Each of the activity events has a correlation identifier, a resolution status, and an occurrence time value associated therewith. Each of the activity events are assigned to one of a plurality of event groups based on the correlation identifier of the activity event. Thereafter, at least one of the event groups is determined to have an activity event with a resolution status indicating failure of the process. One of the activity events within the determined event group is selected as a root cause activity event based on the occurrence time values. In some embodiments, the root cause activity event is identified to a user of the computing device.
    • 关联活动事件以识别过程失败的根本原因。 从在计算设备上执行的进程接收活动事件数据。 活动事件数据对应于多个活动事件。 每个活动事件具有相关标识符,分辨率状态和与其相关联的发生时间值。 基于活动事件的相关标识符,将活动事件分配给多个事件组中的一个。 此后,确定事件组中的至少一个具有活动事件,其中解决状态指示过程失败。 基于发生时间值,将所确定的事件组中的活动事件之一选择为根本原因活动事件。 在一些实施例中,根本原因活动事件被识别给计算设备的用户。
    • 2. 发明申请
    • ROOT CAUSE PROBLEM IDENTIFICATION THROUGH EVENT CORRELATION
    • ROOT通过事件关联引起问题的识别
    • US20110214020A1
    • 2011-09-01
    • US12714842
    • 2010-03-01
    • Ziv CaspiRon E. Dar ZivYifat OrlinAlexander SloutskyItai Frenkel
    • Ziv CaspiRon E. Dar ZivYifat OrlinAlexander SloutskyItai Frenkel
    • G06F11/07
    • G06F11/079G06F11/0709G06F11/0715H04L41/064H04L41/0686
    • Correlating activity events to identify a root cause of a process failure. Activity event data is received from a process executing on a computing device. The activity event data corresponds to a plurality of activity events. Each of the activity events has a correlation identifier, a resolution status, and an occurrence time value associated therewith. Each of the activity events are assigned to one of a plurality of event groups based on the correlation identifier of the activity event. Thereafter, at least one of the event groups is determined to have an activity event with a resolution status indicating failure of the process. One of the activity events within the determined event group is selected as a root cause activity event based on the occurrence time values. In some embodiments, the root cause activity event is identified to a user of the computing device.
    • 关联活动事件以识别过程失败的根本原因。 从在计算设备上执行的进程接收活动事件数据。 活动事件数据对应于多个活动事件。 每个活动事件具有相关标识符,分辨率状态和与其相关联的发生时间值。 基于活动事件的相关标识符,将活动事件分配给多个事件组中的一个。 此后,确定事件组中的至少一个具有活动事件,其中解决状态指示过程失败。 基于发生时间值,将所确定的事件组中的活动事件之一选择为根本原因活动事件。 在一些实施例中,根本原因活动事件被识别给计算设备的用户。
    • 3. 发明授权
    • Transparently extensible firewall cluster
    • 透明的可扩展防火墙集群
    • US08353020B2
    • 2013-01-08
    • US11453778
    • 2006-06-14
    • Amit FinkelsteinAvihai LifschitzYosef DinersteinZiv Caspi
    • Amit FinkelsteinAvihai LifschitzYosef DinersteinZiv Caspi
    • H04L29/06
    • H04L63/0227
    • A generic master-slave mechanism enables a single processor of a cluster of firewall processors to define the behavior of the other processors in the cluster for a specific logical connection. The cluster of firewall processors utilizes virtual adapters representing physical adapters on other processors in the firewall cluster. This virtualization allows each cluster member to act as though it is a standalone machine that owns all local IP addresses of the entire cluster. When traffic is received by a firewall processor, the firewall processor determines if there is a master associated with the logical connection for the traffic. If so, the traffic is routed to the master. If no master is associated, in an example configuration, the receiving firewall processor becomes the master. A message traffic logical connection has a single master. A master remains the master of a logical connection until the connection is terminated.
    • 通用主从机制使得防火墙处理器群集的单个处理器可以定义集群中其他处理器的特定逻辑连接的行为。 防火墙处理器集群利用虚拟适配器代表防火墙集群中其他处理器上的物理适配器。 这种虚拟化允许每个集群成员就像是拥有整个集群的所有本地IP地址的独立机器一样。 当防火墙处理器接收到流量时,防火墙处理器确定是否存在与流量的逻辑连接相关联的主机。 如果是,则流量被路由到主服务器。 如果没有与主机相关联,则在示例配置中,接收防火墙处理器成为主设备。 消息流量逻辑连接具有单个主服务器。 在连接终止之前,主器件保持逻辑连接的主器件。
    • 5. 发明申请
    • Transparently extensible firewall cluster
    • 透明的可扩展防火墙集群
    • US20070294754A1
    • 2007-12-20
    • US11453778
    • 2006-06-14
    • Amit FinkelsteinAvihai LifschitzYosef DinersteinZiv Caspi
    • Amit FinkelsteinAvihai LifschitzYosef DinersteinZiv Caspi
    • G06F15/16
    • H04L63/0227
    • A generic master-slave mechanism enables a single processor of a cluster of firewall processors to define the behavior of the other processors in the cluster for a specific logical connection. The cluster of firewall processors utilizes virtual adapters representing physical adapters on other processors in the firewall cluster. This virtualization allows each cluster member to act as though it is a standalone machine that owns all local IP addresses of the entire cluster. When traffic is received by a firewall processor, the firewall processor determines if there is a master associated with the logical connection for the traffic. If so, the traffic is routed to the master. If no master is associated, in an example configuration, the receiving firewall processor becomes the master. A message traffic logical connection has a single master. A master remains the master of a logical connection until the connection is terminated.
    • 通用主从机制使得防火墙处理器群集的单个处理器可以定义集群中其他处理器的特定逻辑连接的行为。 防火墙处理器集群利用虚拟适配器代表防火墙集群中其他处理器上的物理适配器。 这种虚拟化允许每个集群成员就像是拥有整个集群的所有本地IP地址的独立机器一样。 当防火墙处理器接收到流量时,防火墙处理器确定是否存在与流量的逻辑连接相关联的主机。 如果是,则流量被路由到主服务器。 如果没有与主机相关联,则在示例配置中,接收防火墙处理器成为主设备。 消息流量逻辑连接具有单个主服务器。 在连接终止之前,主器件保持逻辑连接的主器件。