会员体验
专利管家(专利管理)
工作空间(专利管理)
风险监控(情报监控)
数据分析(专利分析)
侵权分析(诉讼无效)
联系我们
交流群
官方交流:
QQ群: 891211   
微信请扫码    >>>
现在联系顾问~
热词
    • 2. 发明申请
    • EMPLOYING POWER OVER ETHERNET FOR AUXILIARY POWER IN COMPUTER SYSTEMS
    • 在计算机系统中为辅助电源使用以太网供电
    • US20140258738A1
    • 2014-09-11
    • US13786611
    • 2013-03-06
    • Paul GreenwaltPatrick ConnorScott P. DubalChris Pavlas
    • Paul GreenwaltPatrick ConnorScott P. DubalChris Pavlas
    • G06F1/26
    • H04L12/40045G06F1/3206G06F1/3278Y02D10/157Y02D30/30Y02D30/32
    • Methods and apparatus for implementing Power over Ethernet (PoE) for auxiliary power in computer systems. Under aspects of the methods, one or more voltage inputs comprising standard power input is employed by a power control component in a network interface in an apparatus such as a network adaptor board, a System on a Chip (SoC), computer server or server blade to supply power to a network controller on the apparatus when the apparatus is operating at a normal power state. To enable the apparatus to maintain network communication when operating at a reduced power state, a PoE power input derived from at least one PoE signal received at at least one Ethernet jack of the apparatus is employed to provide power to the network controller absent use or availability of the standard power input. Accordingly, the PoE power input facilitates an auxiliary power function that may be used alone or in combination with existing (as applicable) auxiliary power input when apparatus are operated in reduced power states.
    • 用于在计算机系统中实现辅助电源的以太网供电(PoE)的方法和装置。 在所述方法的方面,包括标准功率输入的一个或多个电压输入由诸如网络适配器板,片上系统(SoC),计算机服务器或服务器刀片的装置中的网络接口中的功率控制部件采用 当设备在正常功率状态下工作时向设备上的网络控制器供电。 为了使装置能够在以降低的功率状态工作时维持网络通信,在从设备的至少一个以太网插孔处接收到的至少一个PoE信号导出的PoE功率输入被用来向网络控制器提供电力,而不使用或可用性 的标准电源输入。 因此,当设备以降低的功率状态工作时,PoE功率输入有助于单独使用或与现有的(适用的)辅助功率输入组合使用的辅助功率功能。
    • 3. 发明授权
    • Dynamic receive queue balancing with high and low thresholds
    • 动态接收队列平衡,具有高低阈值
    • US08346999B2
    • 2013-01-01
    • US12638538
    • 2009-12-15
    • Scott P. DubalPatrick ConnorMallikarjuna R. Chilakala
    • Scott P. DubalPatrick ConnorMallikarjuna R. Chilakala
    • G06F3/00G06F11/00
    • H04L47/125H04L47/122H04L47/26H04L47/29H04L47/30
    • A method according to one embodiment includes the operations of assigning a network application to at least one first core processing unit, from among a plurality of core processing unit. The method of this embodiment also includes the operations of assigning a first receive queue to said first core processing unit, wherein the first receive queue is configured to receive packet flow associated with the network application; defining a high threshold for the first receive queue; and monitoring the packet flow in the first receive queue and comparing a packet flow level in the first receive queue to the high threshold; wherein if the packet flow level exceeds the threshold based on the comparing, generating a queue status message indicating that the packet flow level in the first queue has exceeded the queue high threshold.
    • 根据一个实施例的方法包括从多个核心处理单元中的至少一个第一核心处理单元分配网络应用程序的操作。 该实施例的方法还包括将第一接收队列分配给所述第一核心处理单元的操作,其中所述第一接收队列被配置为接收与所述网络应用相关联的分组流; 定义第一接收队列的高阈值; 以及监视所述第一接收队列中的分组流,并将所述第一接收队列中的分组流级别与所述高阈值进行比较; 其中如果所述分组流量级别基于所述比较超过所述阈值,则生成指示所述第一队列中的分组流量级别已经超过所述队列高阈值的队列状态消息。
    • 4. 发明申请
    • UPDATING MACHINES WHILE DISCONNECTED FROM AN UPDATE SOURCE
    • 从更新源断开连接的更新机器
    • US20100082841A1
    • 2010-04-01
    • US12547344
    • 2009-08-25
    • Scott P. DubalDouglas D. BoomElizabeth M. KapplerMark V. Montecalvo
    • Scott P. DubalDouglas D. BoomElizabeth M. KapplerMark V. Montecalvo
    • G06F9/44G06F15/16G06F1/32
    • G06F8/65Y02D10/42
    • Disclosed are exemplary embodiments for updating a networked machine having at least a dormant state and an active state. In various embodiments, when the machine it is a dormant state, it listens to a network for candidate updates, that is, updates that may be applicable to the machine. In some embodiments, determining the candidate update is an applicable update for the machine may be based at least in part on a variety of reasons, including testing if it has already been applied, does not actually update some aspect of the machine, conflicts with an existing configuration of the machine, conflicts with a policy of the machine, etc. The machine may cache some or all of the candidate updates or applicable updates, where a variety of rationales or policies may be used to control update retention. When the machine enters an active state, such as a power on or non-sleep mode, or other active state, the machine may validate integrity of an applicable update if not done while the machine was dormant, and optionally choose to install it.
    • 公开了用于更新具有至少休眠状态和活动状态的联网机器的示例性实施例。 在各种实施例中,当机器处于休眠状态时,它监听用于候选更新的网络,即可适用于机器的更新。 在一些实施例中,确定候选更新是机器的适用更新可以至少部分地基于各种原因,包括测试是否已被应用,实际上不更新机器的某些方面,与 机器的现有配置,与机器的策略等冲突。机器可以缓存候选更新或适用的更新中的一些或全部,其中可以使用各种理由或策略来控制更新保留。 当机器进入活动状态(如开机或非睡眠模式)或其他活动状态时,如果机器处于休眠状态,则机器可能会验证适用更新的完整性,如果在机器处于休眠状态,则可以选择安装。
    • 6. 发明授权
    • Updating machines while disconnected from an update source
    • 在与更新源断开连接时更新计算机
    • US07581029B2
    • 2009-08-25
    • US11157334
    • 2005-06-20
    • Scott P. DubalDouglas D. BoomElizabeth M. KapplerMark V. Montecalvo
    • Scott P. DubalDouglas D. BoomElizabeth M. KapplerMark V. Montecalvo
    • G06F15/16
    • G06F8/65Y02D10/42
    • Disclosed are exemplary embodiments for updating a networked machine having at least a dormant state and an active state. In various embodiments, when the machine it is a dormant state, it listens to a network for candidate updates, that is, updates that may be applicable to the machine. In some embodiments, determining the candidate update is an applicable update for the machine may be based at least in part on a variety of reasons, including testing if it has already been applied, does not actually update some aspect of the machine, conflicts with an existing configuration of the machine, conflicts with a policy of the machine, etc. The machine may cache some or all of the candidate updates or applicable updates, where a variety of rationales or policies may be used to control update retention. When the machine enters an active state, such as a power on or non-sleep mode, or other active state, the machine may validate integrity of an applicable update if not done while the machine was dormant, and optionally choose to install it.
    • 公开了用于更新具有至少休眠状态和活动状态的联网机器的示例性实施例。 在各种实施例中,当机器处于休眠状态时,它监听用于候选更新的网络,即可适用于机器的更新。 在一些实施例中,确定候选更新是机器的适用更新可以至少部分地基于各种原因,包括测试是否已被应用,实际上不更新机器的某些方面,与 机器的现有配置,与机器的策略等冲突。机器可以缓存候选更新或适用的更新中的一些或全部,其中可以使用各种理由或策略来控制更新保留。 当机器进入活动状态(如开机或非睡眠模式)或其他活动状态时,如果机器处于休眠状态,则机器可能会验证适用更新的完整性,如果在机器处于休眠状态,则可以选择安装。
    • 8. 发明授权
    • Method for running diagnostic utilities in a multi-threaded operating system environment
    • 在多线程操作系统环境中运行诊断实用程序的方法
    • US06976193B2
    • 2005-12-13
    • US09957947
    • 2001-09-20
    • Scott P. Dubal
    • Scott P. Dubal
    • G06F11/22H04L1/24G06F11/00
    • G06F11/2247
    • A method for running diagnostic utilities so as to prevent system disruptions. During initialization of a diagnostic utility, a resource monitoring thread is spawned as a background process to monitor system resource conditions, such as CPU and memory availability and loads. In one embodiment, the resource conditions are continuously monitored by querying performance data written to the system's registry on a periodic basis. In response to user requests to perform diagnostics, the resource monitoring thread (or files written thereby) is/are queried to determined the current resource conditions. If enough resources are available to run the utility's diagnostic routine(s), they are allowed to run. If it is determined that not enough resources are available, the running of the diagnostics is delayed until it is determined that enough resources are available. Alternately, a subset of the diagnostics may be run based on the current resource conditions determined by the resource monitoring thread.
    • 一种用于运行诊断实用程序以防止系统中断的方法。 在诊断实用程序的初始化期间,资源监视线程被产生为后台进程,以监视系统资源状况,例如CPU和内存可用性和负载。 在一个实施例中,通过周期性地查询写入系统注册表的性能数据来连续地监视资源条件。 响应于用户执行诊断的请求,查询资源监视线程(或由此写入的文件)以确定当前的资源状况。 如果有足够的资源可用于运行实用程序的诊断例程,则可以运行它们。 如果确定没有足够的资源可用,则诊断的运行被延迟,直到确定有足够的资源可用。 或者,可以基于由资源监视线程确定的当前资源条件来运行诊断的子集。