WO2007146708A2 - Edge server failover - Google Patents
Edge server failover Download PDFInfo
- Publication number
- WO2007146708A2 WO2007146708A2 PCT/US2007/070532 US2007070532W WO2007146708A2 WO 2007146708 A2 WO2007146708 A2 WO 2007146708A2 US 2007070532 W US2007070532 W US 2007070532W WO 2007146708 A2 WO2007146708 A2 WO 2007146708A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- server
- rfld
- rfid
- state
- edge
- 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.)
- Ceased
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1036—Load balancing of requests to servers for services different from user content provisioning, e.g. load balancing across domain name servers
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; 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/16—Error detection or correction of the data by redundancy in hardware
- G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
- G06F11/202—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant
- G06F11/2038—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant with a single idle spare processing component
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1031—Controlling of the operation of servers by a load balancer, e.g. adding or removing servers that serve requests
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; 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/16—Error detection or correction of the data by redundancy in hardware
- G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
- G06F11/202—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant
- G06F11/2023—Failover techniques
- G06F11/2028—Failover techniques eliminating a faulty processor or activating a spare
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/18—Service support devices; Network management devices
- H04W88/182—Network node acting on behalf of an other network entity, e.g. proxy
Definitions
- the present invention relates to Radio Frequency Identification (RlD) edge
- RFlD Tags are becoming more and more popular as a way of tracking objects.
- an RFID tag 102 is read by an RFlD reader 104.
- the RFlD data can then be transferred from the RFlD reader 104 to an RFID edge server 106 that can process the RFlD data.
- the RFID edge server 106 can send the RFID data to central server, such as RFID enterprise server 108
- Figure 1 illustrates an RFlD system.
- Figure 2 illustrates an RFlD system with edge server failover of one embodiment of the present invention.
- Figure 3 illustrates a failover system for an RFID system of one embodiment of the present invention.
- FIG. 2 shows a system where RFID server 202 provides for failover for a
- the RFlD edge servers 20) and 202 can determine what RFiD edge server should be connected to the RF ⁇ D readers 204, 206 and 208.
- the other RFlD edge i ⁇ servers can drop any of their connections to any of the RFID readers 204, 206 and 208.
- One embodiment is a system comprising a first RFJD edge server 201 and a second RFiD edge server 202 that arbitrate which RFID edge server will be active. f ⁇ OlOj Upon start up the first and second RFlD edge server 201 and 202 can race to get R.F ⁇ D readers, then the RFID server with the least number of RFfD readers can give up the
- JOOl IJ Automatic failover of the RF ⁇ D edge servers 20! and 202 can be done. Reader connections can be reset during failover.
- the first RFiD edge server can be associated with a failover agent that receives
- the failover agent can be a software component that starts, stops, and monitors the health of an application, and takes corrective actions to regain application availability upon failure
- 0014 ⁇ Failover can be a backup operation that automatically switches to a standby
- the failover agent or other code can receive heartbeats from first and second
- RFlD edge servers 201 and 202 Upon start up the first and second RFID edge server 201
- 30 and 202 can race to get RFlD readers 204. 206 and 208, and then arbitrate who will be connected to all of the RF ⁇ D readers.
- An administrator of a system running the RFlD edge server can set up the system so that a primary RFID edge server can failover to a secondary RFID edge server if the primary edge server fails or is shutdown.
- Automated failo ⁇ er support for the RFID edge server can allow for continuous and uninterrupted operations.
- the fail over solution can entai I the fo ⁇ low ing.
- FIG. 3 shows a primary and secondary server each am an RFlD Exlge Server and a Failover Agent Upon startup, each server can launch the failover agent. The failover agent determines whether or not to start the RFID server on that server based on telemetry heartbeats received from both RFiD edge server instances
- Each failover agent can receive telemetry heartbeats from both RFlD Edge
- one of the failover agents can start its RFID edge server instance.
- the RFID edge server instance can connect to all of the configured RFID readers and generate Electronic Product Code Information Service
- the fa ⁇ over agent can utilize the following, or an alternate, decision algorithm
- the arbitration can include a down state, an up state and a partial (1/2) up state.
- Telemetry Reports indicate 1 50% of readers are up. • HP State: Telemetry heartbeat has been received in the last « seconds and Tel emetry Reports indicate > 50 O/ ⁇ of readers are up.
- One embodiment includes a computer program product which is a storage medium (media) having instructions stored thereon/in which can be used to program a computer to perform any of the features present herein.
- the storage medium can include, but is not limited to, any type of disk including floppy disks, optical discs, DYD, CD-ROMs, micro drive, and magneto-optical disks, ROKIs, RAKIs, EPROMs, EEPROMs, DRAMs, Hash memory of media or device suitable for storing instaictions and/or data stored on any one of the computer readable medium (media), the present invention can include software for controlling both the hardware of the general purpose/specialized computer or microprocessor, and for enabling the computer or microprocessor to interact with a human user or other mechanism utilizing the results of the present invention.
- Such software may include, but is not limited to, device drivers, operating systems, execution environments/containers, and user applications.
- Embodiments of the present invention can include providing code for implementing processes of the present invention.
- the providing can include providing code to a user in any manner.
- the providing can include transmitting digital signals containing the code to a user; providing the code on a physical media to a user, or any other 5 method of making the code available.
- Embodiments of the present invention can include a computer implemented method for transmitting code which can be executed at a computer to perform any of the processes of embodiments of the present invention.
- the transmitting can include transfer through any portion of a network, such as the Internet; through wires, the atmosphere or id space; or any other type of transmission.
- the transmitting can include initiating a transmission of code; or causing the code to pass into any region or country from another region or country.
- transmitting includes causing the transfer of code through a portion of a network as a result of previously addressing and sending data including the code to a user.
- a transmission to a user can include any transmission received by the user in any
- the present invention can include a signal containing code which can be executed at a computer to perform any of the processes of embodiments of the present invention.
- the signal can be transmitted through a network, such as the Internet; through wires, the atmosphere or space; or any other type of transmission.
- the entire signal can be transmitted through a network, such as the Internet; through wires, the atmosphere or space; or any other type of transmission.
- the entire signal can be transmitted through a network, such as the Internet; through wires, the atmosphere or space; or any other type of transmission.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Hardware Redundancy (AREA)
- Computer And Data Communications (AREA)
Abstract
First and second RFID edge servers can interact with RFID tag readers. The first and second RFID edge servers can arbitrate which of the first and second RFID edge servers will be active upon start up or edge server failure.
Description
EDGE SERVER FAILOVER
Inventors. Iwao Hatanaka Kenneth Traub
CLAIM OF PRIORITY
[0001 ] This application claims priority to U S. Provisional Application No.
60/812,397 entitled "Εdge Server" by Traub et a!., filed June 9, 2006 [Atty Docket No BEAS-02086US0]; and U S, Provisional Application No. 60/812,460 entitled "Enterprise Server" by Traub et al , filed June 9, 2006 [Atty. Docket No BEAS-02087US0]; U.S. Provisional Application No 6O'B29,921 entitled "Edge Server Failover" by Traub et al , filed October 18, 2006 [Atty Docket No. BEAS-02101 USO]; and U.S. Utility Application No 1 1 /756,000 entitled "Edjje Server Failover" by Hatanaka et al., filed May 31, 2007 [Atty. Docket No BEAS-02101 US I j; \\ Inch are hereby incorporated by reference
COPYRIGHT NOTICE
[0002] A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.
BACKGROUND OF INVENTION
[0003] The present invention relates to Radio Frequency Identification (RlD) edge
Servers. RFlD Tags are becoming more and more popular as a way of tracking objects. Typically, as shown in figure 1, an RFID tag 102 is read by an RFlD reader 104. The RFlD data can then be transferred from the RFlD reader 104 to an RFID edge server 106 that can process the RFlD data.
[0001] The RFID edge server 106 can send the RFID data to central server, such as RFID enterprise server 108
BRIEF DESCRIPTION OF THE DRAWINGS
[0004] Figure 1 illustrates an RFlD system.
[0005] Figure 2 illustrates an RFlD system with edge server failover of one embodiment of the present invention.
|0006j Figure 3 illustrates a failover system for an RFID system of one embodiment of the present invention.
DETAILED DESCRIPTION
5 |0007 J One potential problem with the RFID system of figure ! is that if the RFID edge server 106 goes down the RFID tag 102 can not be tracked.
(0008] Figure 2 shows a system where RFID server 202 provides for failover for a
RFLD edge server 210. The RFlD edge servers 20) and 202 can determine what RFiD edge server should be connected to the RFΪD readers 204, 206 and 208. The other RFlD edge iθ servers can drop any of their connections to any of the RFID readers 204, 206 and 208.
|0009| One embodiment is a system comprising a first RFJD edge server 201 and a second RFiD edge server 202 that arbitrate which RFID edge server will be active. føOlOj Upon start up the first and second RFlD edge server 201 and 202 can race to get R.FΪD readers, then the RFID server with the least number of RFfD readers can give up the
S 5 RFID readers that it does have. In this way, the winning RFID server will be connected to all of the RFΪD readers.
JOOl IJ Automatic failover of the RFΪD edge servers 20! and 202 can be done. Reader connections can be reset during failover. |0012 j The first RFiD edge server can be associated with a failover agent that receives
20 heartbeats from both the first and second RFΪD edge servers 201 and 202. jOOI3| The failover agent can be a software component that starts, stops, and monitors the health of an application, and takes corrective actions to regain application availability upon failure |0014{ Failover can be a backup operation that automatically switches to a standby
25 server if the primary system fails or is shutdown. The system can be high availability such that it remains available despite the failure of one's components. fOOlSj The failover agent or other code can receive heartbeats from first and second
RFlD edge servers 201 and 202; and arbitrate which of the first and second RFID edge servers 201 and 202 will be active. Upon start up the first and second RFID edge server 201
30 and 202 can race to get RFlD readers 204. 206 and 208, and then arbitrate who will be connected to all of the RFΪD readers.
[0016} An administrator of a system running the RFlD edge server can set up the system so that a primary RFID edge server can failover to a secondary RFID edge server if
the primary edge server fails or is shutdown. Automated failo\er support for the RFID edge server can allow for continuous and uninterrupted operations. |0017| The fail over solution can entai I the foϊ low ing.
• Fail over agents deployed for each RFID edge server
5 ♦ Automatic faϋover of primary RFID sen er to secondary RFID server upon detection of edge server failure
♦ Decision algorithm utilized by failover agent to determine which edge server to stan/stop
* RFID Reader connections re-established with edge server during faϋover processing K) |001S| Figure 3 shows a primary and secondary server each am an RFlD Exlge Server and a Failover Agent Upon startup, each server can launch the failover agent. The failover agent determines whether or not to start the RFID server on that server based on telemetry heartbeats received from both RFiD edge server instances
[0019} Each failover agent can receive telemetry heartbeats from both RFlD Edge
!5 Servers Based on a decision algorithm documented, such as that below, one of the failover agents can start its RFID edge server instance. The RFID edge server instance can connect to all of the configured RFID readers and generate Electronic Product Code Information Service
(EPClS) event data
|0020J The faϋover agent can utilize the following, or an alternate, decision algorithm
20 upon receiving a telemetry heartbeat or upon a timer pop at a configured interval The arbitration can include a down state, an up state and a partial (1/2) up state.
|002i| hi one case.
25 where
* DOWN State: No telemetry heartbeat has been received in the last « seconds
* Partial ('•:> } UP State Telemetry heartbeat has been received in the last ;/ seconds, but
Telemetry Reports indicate 1 50% of readers are up.
• HP State: Telemetry heartbeat has been received in the last « seconds and Tel emetry Reports indicate > 50O/ό of readers are up.
If Server2 is in DOWN state, then fai lover agent 1 can always try to start RFlD edge server. If Server! is in UP state, then failover agent 1 will attempt to stop RFlD edge server. If Server2 is in 1^ UF state, then fail over agent 1 will perform the following:
• Stop RFID edge server? if Server? is in DOWN state
• Start RFTagAwarel if Server! is in IIP state
• Start or stop RFlD edge server 1 if Server ! is in partially '•': UP state
|0022| Ir-C Specs, subscriptions, and workflows can be configured ahead of time. The ALE API need not be used during normal operation (other than the delivery of EC Reports to existing subscriptions). f0023| An Administration console can display both primary and secondary edge server status (future enhancement would display only the active edge server) |0024j One embodiment may be implemented using a conventional general purpose of a specialized digital computer or microprocessors) programmed according to the teachings of the present disclosure, as will be apparent to those skilled in the computer art Appropriate software coding can readily be prepared by skilled programmers based on the teachings of the present discloser, as will be apparent to those skilled in the software art The invention may also be implemented by the preparation of integrated circuits or by interconnecting an appropriate network of conventional component circuits, as will be readily apparent to those skilled in the art,
|0025| One embodiment includes a computer program product which is a storage medium (media) having instructions stored thereon/in which can be used to program a computer to perform any of the features present herein. The storage medium can include, but is not limited to, any type of disk including floppy disks, optical discs, DYD, CD-ROMs, micro drive, and magneto-optical disks, ROKIs, RAKIs, EPROMs, EEPROMs, DRAMs, Hash memory of media or device suitable for storing instaictions and/or data stored on any one of the computer readable medium (media), the present invention can include software for controlling both the hardware of the general purpose/specialized computer or microprocessor, and for enabling the computer or microprocessor to interact with a human user or other mechanism utilizing the results of the present invention. Such software may include, but is not limited to, device drivers, operating systems, execution environments/containers, and user applications.
4
|0026| Embodiments of the present invention can include providing code for implementing processes of the present invention. The providing can include providing code to a user in any manner. For example, the providing can include transmitting digital signals containing the code to a user; providing the code on a physical media to a user, or any other 5 method of making the code available.
|0027| Embodiments of the present invention can include a computer implemented method for transmitting code which can be executed at a computer to perform any of the processes of embodiments of the present invention. The transmitting can include transfer through any portion of a network, such as the Internet; through wires, the atmosphere or id space; or any other type of transmission. The transmitting can include initiating a transmission of code; or causing the code to pass into any region or country from another region or country. For example, transmitting includes causing the transfer of code through a portion of a network as a result of previously addressing and sending data including the code to a user. A transmission to a user can include any transmission received by the user in any
S 5 region or country, regardless of the location from which the transmission is sent.
|0028| ϊϊmbodiments of the present invention can include a signal containing code which can be executed at a computer to perform any of the processes of embodiments of the present invention.. The signal can be transmitted through a network, such as the Internet; through wires, the atmosphere or space; or any other type of transmission. The entire signal
20 need not be in transit at the same time. The signal can extend in time over the period of its transfer. The signal is not to be considered as a snapshot of what is currently in transit. f0029| The forgoing description of preferred embodiments of the present invention has been provided for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and
25 variations will be apparent to one of ordinary skill in the relevant arts For example, steps preformed in the embodiments of the invention disclosed can be performed in alternate orders, certain steps can be omitted, and additional steps can be added. The embodiments where chosen and described in order to best explain the principles of the invention and its practical application, thereby enabling others skilled in the art to understand the invention for
30 various embodiments and with various modifications that are suited to the particular used contemplated. It is intended that the scope of the invention be defined by the claims and their equivalents.
Claims
1. A system comprising: a first RFID edge server adapted to interact with a RFlD fag reader; and
5 a second RFID edge server adapted to interact with the RFiD tag reader, wherein the first and second RFID edge server arbitrate which of the first and second RFiD edge servers wiH be active,
2. The system of claim 1, wherein the first RFlD edge server is associated with a failover id agent that receives heartbeats from the second RFID edge server.
3. The system of claim I , an automatic failover of the RFlD edge servers occurs between the first and second RFlD edge servers.
i 5 4. The system of claim 3, wherei n reader connects ons are reset during fail over.
5. The system of claim 3, wherein the arbitration includes a down state, an up state and a partially up state.
20 6. The system of claim 5, wherein a RFΪD server in the up state has priority over an RFiD server in the down state.
7. 'The system of claim 5, wherein a RFID server in the up state has priority over an RFlD server in the partially up state,
25
8. The system of claim 5, wherein a RFlD server in the partially up state will switch control if the other server is in the partially up state.
ζ>. The system of claim 5, wherein upon start up the first and second RFlD edge server 30 race to get RFlD readers, then arbitrate who will be connected to all of the RFlD readers.
10, A system comprising; a first RFID edge server adapted to interact with a RFiD tag reader; and a second RFID edge server adapted to interact with the RFf D tag reader, wherein the first and second RFID edge server arbitrate which of the first and second RFlD edge servers will be active; wherein upon start up the first and second RFID edge server race to get RFlD readers, then arbitrate who will be connected to ali of the RFID readers.
1 1. The system of claim 10, wherein the first RFID edge server is associated with a fai lover agent that receives heartbeats from the second RFlD edge server
12. The system of claim 10, an automatic failover of the RFID edge servers occurs between the first and second RFlD edge servers.
13 The system of claim 12. wherein reader connections are reset during fail over.
14. The system of claim 12. wherein the arbitration includes a down state, an up state and a partially up state.
15. The system of claim 14, wherein a RFID server in the υp state has priority over an RFlD server in the down state.
16. The system of claim 14, wherein a RFlD server in the up state has priority over an RFlD server in the partially up state.
17. The system of claim 14, wherein a RFf D server in the partially up state will switch control if the other server is in the partially up state.
18. A computer readable medium containing code to: receive heartbeats from first and second RFID edge servers, and arbitrate which of the first and second RFlD edge servers will be active; wherein upon start up the first and second RFlD edge server race to get RFlD readers, then arbitrate who will be connected to all of the RFID readers.
Applications Claiming Priority (8)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US81239706P | 2006-06-09 | 2006-06-09 | |
| US81246006P | 2006-06-09 | 2006-06-09 | |
| US60/812,397 | 2006-06-09 | ||
| US60/812,460 | 2006-06-09 | ||
| US82992106P | 2006-10-18 | 2006-10-18 | |
| US60/829,921 | 2006-10-18 | ||
| US11/756,000 | 2007-05-31 | ||
| US11/756,000 US7528697B2 (en) | 2006-06-09 | 2007-05-31 | Edge server failover |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| WO2007146708A2 true WO2007146708A2 (en) | 2007-12-21 |
| WO2007146708A3 WO2007146708A3 (en) | 2009-01-08 |
Family
ID=38832674
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/US2007/070532 Ceased WO2007146708A2 (en) | 2006-06-09 | 2007-06-06 | Edge server failover |
Country Status (2)
| Country | Link |
|---|---|
| US (1) | US7528697B2 (en) |
| WO (1) | WO2007146708A2 (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2010094983A1 (en) * | 2009-02-23 | 2010-08-26 | Traak Systems Limited | Event processing apparatus and methods |
| US20150019900A1 (en) * | 2013-07-11 | 2015-01-15 | International Business Machines Corporation | Tolerating failures using concurrency in a cluster |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2008098149A2 (en) * | 2007-02-07 | 2008-08-14 | Larotec Ltd. | Failover enabled telemetry systems |
| CN101729909B (en) * | 2008-10-23 | 2012-11-21 | 华为技术有限公司 | Streaming media business processing method, device and system |
| US9471877B1 (en) * | 2015-12-10 | 2016-10-18 | International Business Machines Corporation | Health checking a question answering cognitive computing system built on a baseline of ground truth virtual checksum |
| US10585784B2 (en) | 2015-12-10 | 2020-03-10 | International Business Machines Corporation | Regression testing question answering cognitive computing systems by applying ground truth virtual checksum techniques |
| US11343328B2 (en) * | 2020-09-14 | 2022-05-24 | Vmware, Inc. | Failover prevention in a high availability system during traffic congestion |
Family Cites Families (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5892441A (en) | 1996-06-26 | 1999-04-06 | Par Government Systems Corporation | Sensing with active electronic tags |
| US7035877B2 (en) | 2001-12-28 | 2006-04-25 | Kimberly-Clark Worldwide, Inc. | Quality management and intelligent manufacturing with labels and smart tags in event-based product manufacturing |
| JP4525074B2 (en) | 2003-12-24 | 2010-08-18 | 日本電気株式会社 | Product identification information management system |
| JP2005301442A (en) * | 2004-04-07 | 2005-10-27 | Hitachi Ltd | Storage device |
| US7466232B2 (en) | 2004-05-05 | 2008-12-16 | Trenstar Tracking Solutions, Inc. | Radio frequency identification asset management system and method |
| US7422152B2 (en) * | 2004-05-13 | 2008-09-09 | Cisco Technology, Inc. | Methods and devices for providing scalable RFID networks |
| US7512830B2 (en) | 2004-05-14 | 2009-03-31 | International Business Machines Corporation | Management module failover across multiple blade center chassis |
| US7161489B2 (en) | 2004-09-09 | 2007-01-09 | The Gillette Company | RFID system performance monitoring |
| US7481368B2 (en) | 2004-12-14 | 2009-01-27 | Siemens Corporate Research, Inc. | Systems, devices, and methods for managing RFID data |
| US7205897B2 (en) | 2005-03-01 | 2007-04-17 | Sap Aktiengesellschaft | Product flow based auto-ID infrastructure |
-
2007
- 2007-05-31 US US11/756,000 patent/US7528697B2/en active Active
- 2007-06-06 WO PCT/US2007/070532 patent/WO2007146708A2/en not_active Ceased
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2010094983A1 (en) * | 2009-02-23 | 2010-08-26 | Traak Systems Limited | Event processing apparatus and methods |
| US20150019900A1 (en) * | 2013-07-11 | 2015-01-15 | International Business Machines Corporation | Tolerating failures using concurrency in a cluster |
| US20150019901A1 (en) * | 2013-07-11 | 2015-01-15 | International Business Machines Corporation | Tolerating failures using concurrency in a cluster |
| US9176834B2 (en) * | 2013-07-11 | 2015-11-03 | Globalfoundries U.S. 2 Llc | Tolerating failures using concurrency in a cluster |
| US9176833B2 (en) * | 2013-07-11 | 2015-11-03 | Globalfoundries U.S. 2 Llc | Tolerating failures using concurrency in a cluster |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2007146708A3 (en) | 2009-01-08 |
| US20070296550A1 (en) | 2007-12-27 |
| US7528697B2 (en) | 2009-05-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7528697B2 (en) | Edge server failover | |
| EP1437658B1 (en) | Coordinating persistent status information with multiple file servers | |
| EP0950955B1 (en) | Method and apparatus for correct and complete transactions in a fault tolerant distributed database system | |
| US7194652B2 (en) | High availability synchronization architecture | |
| US7076689B2 (en) | Use of unique XID range among multiple control processors | |
| US7284236B2 (en) | Mechanism to change firmware in a high availability single processor system | |
| US20070180307A1 (en) | Method & system for resynchronizing data between a primary and mirror data storage system | |
| JP4976661B2 (en) | CHEAPAXOS | |
| US7188237B2 (en) | Reboot manager usable to change firmware in a high availability single processor system | |
| US20130138737A1 (en) | Managing a Message Subscription in a Publish/Subscribe Messaging System | |
| US8051321B2 (en) | Cluster system and node switching method | |
| US20110173495A1 (en) | Method and System for Reliable Intersystem Message Notification | |
| US7065673B2 (en) | Staged startup after failover or reboot | |
| GB2402769A (en) | Maintaining resource integrity without a unified transaction manager in a software environment | |
| GB2277178A (en) | Electronic dealing system. | |
| CN108958984A (en) | Dual-active based on CEPH synchronizes online hot spare method | |
| EP0175170B1 (en) | Off-line notification in communication networks | |
| JPH0341522A (en) | Message missing detecting and processing system | |
| JP3190880B2 (en) | Standby system, standby method, and recording medium | |
| CN112035071B (en) | Disk data reading method, device, computer equipment and storage medium | |
| JPH0879246A (en) | Distributed communication system and failure recovery method thereof | |
| JP3284823B2 (en) | Data communication device | |
| CN103618700A (en) | Method for determining leader server in server system and server system | |
| US20020124204A1 (en) | Guarantee of context synchronization in a system configured with control redundancy | |
| CN108599903A (en) | Single board starting control method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 07798183 Country of ref document: EP Kind code of ref document: A2 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| NENP | Non-entry into the national phase |
Ref country code: RU |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 07798183 Country of ref document: EP Kind code of ref document: A2 |