会员体验
专利管家(专利管理)
工作空间(专利管理)
风险监控(情报监控)
数据分析(专利分析)
侵权分析(诉讼无效)
联系我们
交流群
官方交流:
QQ群: 891211   
微信请扫码    >>>
现在联系顾问~
热词
    • 3. 发明申请
    • Device for continuous calibration of a gas mass flow measurement device
    • 用于连续校准气体质量流量测量装置的装置
    • US20070043976A1
    • 2007-02-22
    • US10557077
    • 2003-06-11
    • Timothy CunninghamTimothy PattenCharles GrayDean Standiford
    • Timothy CunninghamTimothy PattenCharles GrayDean Standiford
    • G06F11/00
    • G01F1/84G01F25/003G01F25/0053
    • A gas test system (300) is disclosed comprised of a flow loop (302), a blower system (304), a temperature control system (306), a reference meter system (308), and a unit under test (UUT) system (310). The UUT system connects a unit under test (UUT) to the flow loop. The blower system receives the gas under pressure at an inlet (321), and generates a high flow rate of the gas out of an outlet (322) while generating a low pressure rise from the inlet to the outlet. The temperature control system receives the flow of gas from the blower system and controls the temperature of the gas. The reference meter system and the UUT in the UUT system measure a property of the gas circulating through the flow loop. The measurements of the reference meter system can be compared to the measurements of the UUT to calibrate the UUT.
    • 公开了一种气体测试系统(300),其包括流动回路(302),鼓风机系统(304),温度控制系统(306),参考仪表系统(308)和被测单元(UUT)系统 (310)。 UUT系统将被测单元(UUT)连接到流量回路。 鼓风机系统在入口(321)处接收压力下的气体,并且从出口(322)产生高气体流量,同时产生从入口到出口的低压力升高。 温度控制系统接收来自鼓风机系统的气体流并控制气体的温度。 UUT系统中的参考仪表系统和UUT测量通过流动回路循环的气体的性质。 可以将参考仪表系统的测量值与UUT的测量值进行比较,以校准UUT。
    • 5. 发明申请
    • System, device, and method for address management in a distributed communication environment
    • US20050190754A1
    • 2005-09-01
    • US10606847
    • 2003-06-26
    • Sandeep GolikeriDa-Hai DingNicholas IlyadisTimothy CunninghamManish Patel
    • Sandeep GolikeriDa-Hai DingNicholas IlyadisTimothy CunninghamManish Patel
    • H04L12/56H04L29/12H04Q11/00
    • H04L29/12047H04L29/12009H04L45/742H04L49/351H04L61/15
    • A distributed address database management technique involves maintaining an address database by each of a number of interconnected modules. Each module maintains a number of locally owned address entries and a number of remotely owned address entries in the address database. Each module monitors the status of its locally owned address entries, maintains the locally owned address entries based upon the status, and provides the status to the other interconnected modules. Each module maintains the remotely owned address entries based upon the status received from the other interconnected modules. When a module adds a locally owned address entry to its address database, the module notifies the other interconnected modules, which in turn add a corresponding remotely owned address entry to their respective address databases. When a module purges a locally owned address entry from its address database, the module notifies the other interconnected modules, which in turn purge the corresponding remotely owned address entries from their respective address databases. Each module may periodically send a keep-alive message including a list of active addresses to the other interconnected modules, which maintain a persistence timer for each of the remotely owned address entries and purge a particular remotely owned address entry if the corresponding persistence timer expires before receiving a keep-alive message identifying the remotely owned address entry as an active remotely owned address entry. Upon receiving a keep-alive message, a module adds a remotely owned address entry for a particular address to its address database if such a remotely owned address entry is not already maintained in the address database. A module purges all remotely owned address entries from its address database if the module is reconfigured to operate in a stand-alone mode. A module purges all remotely owned address entries associated with a particular interconnected module if that particular interconnected module is removed.
    • 8. 发明授权
    • System, device, and method for address management in a distributed communication environment
    • US06597700B2
    • 2003-07-22
    • US09340477
    • 1999-06-30
    • Sandeep P. GolikeriDa-Hai DingNicholas IlyadisTimothy CunninghamManish Patel
    • Sandeep P. GolikeriDa-Hai DingNicholas IlyadisTimothy CunninghamManish Patel
    • H04L1256
    • H04L29/12047H04L29/12009H04L45/742H04L49/351H04L61/15
    • A distributed address database management technique involves maintaining an address database by each of a number of interconnected modules. Each module maintains a number of locally owned address entries and a number of remotely owned address entries in the address database. Each module monitors the status of its locally owned address entries, maintains the locally owned address entries based upon the status, and provides the status to the other interconnected modules. Each module maintains the remotely owned address entries based upon the status received from the other interconnected modules. When a module adds a locally owned address entry to its address database, the module notifies the other interconnected modules, which in turn add a corresponding remotely owned address entry to their respective address databases. When a module purges a locally owned address entry from its address database, the module notifies the other interconnected modules, which in turn purge the corresponding remotely owned address entries from their respective address databases. Each module may periodically send a keep-alive message including a list of active addresses to the other interconnected modules, which maintain a persistence timer for each of the remotely owned address entries and purge a particular remotely owned address entry if the corresponding persistence timer expires before receiving a keep-alive message identifying the remotely owned address entry as an active remotely owned address entry. Upon receiving a keep-alive message, a module adds a remotely owned address entry for a particular address to its address database if such a remotely owned address entry is not already maintained in the address database. A module purges all remotely owned address entries from its address database if the module is reconfigured to operate in a stand-alone mode. A module purges all remotely owned address entries associated with a particular interconnected module if that particular interconnected module is removed.