Training detection model using output of language model applied to event information
US-2024419941-A1 · Dec 19, 2024 · US
US11080648B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11080648-B2 |
| Application number | US-201715648783-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jul 13, 2017 |
| Priority date | Jul 13, 2017 |
| Publication date | Aug 3, 2021 |
| Grant date | Aug 3, 2021 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A data recovery system (apparatus) includes first management hardware at a first location and second management hardware at a second location. The first management hardware includes or executes a corresponding primary order manager to process first orders. The second management hardware includes or executes a primary manager to process second orders. Each of the first management hardware and the second management hardware includes auxiliary resources to execute functions on behalf of each other in the event of a failure. For example, the first management hardware executes an auxiliary order manager to process the second orders during conditions in which the primary order manager of the second management hardware is unable to process the second orders; the second management hardware executes an auxiliary order manager to process the first orders during conditions in which the primary order manager of the first management hardware is unable to process the first orders.
Opening claim text (preview).
We claim: 1. A system comprising: first management hardware including first primary hardware and first backup hardware, the first primary hardware including an order flow manager to route orders and a primary order manager to process first orders, the first management hardware disposed at a first geographical location; second management hardware including second primary hardware and second backup hardware, the second primary hardware including an order flow manager to route orders and a primary order manager to process second orders, the second management hardware disposed at a second geographical location; a synchronizer configured to synchronize storage of data between the first management hardware and the second management hardware; and wherein the first backup hardware is substantially a replica of the second primary hardware, and the second backup hardware is substantially a replica of the first primary hardware; and wherein during: first conditions, the order flow manager of the first primary hardware is configured to: i) forward the first orders to the primary order manager of the first primary hardware for execution, and ii) forward the second orders to the primary order manager of the second primary hardware for execution, wherein the order flow manager of the second primary hardware is inactive during the first conditions; and second conditions, the order flow manager of the second primary hardware is configured to: i) forward the first orders to an auxiliary order manager of the second backup hardware for execution, and ii) forward the second orders to the primary order manager of the second primary hardware for execution, wherein the order flow manager of the first primary hardware is inactive during the second conditions. 2. The system as in claim 1 , wherein the first primary hardware includes a first primary repository; wherein the first backup hardware includes a first auxiliary repository; wherein the second primary hardware includes a second primary repository; wherein the second backup hardware includes a second auxiliary repository; wherein the first auxiliary repository is operable to store a copy of order data stored in the second primary repository as first backup order data; and wherein the second auxiliary repository is operable to store a copy of order data stored in the first primary repository as second backup order data. 3. The system as in claim 2 further comprising: a first data synchronizer resource operable to copy an updated rendition of the first backup order data from the first auxiliary repository to the second primary repository in response to detecting that the second primary hardware becomes operable again after a failure; and a second data synchronizer resource operable to copy an updated rendition of the second backup order data from the second auxiliary repository to the first primary repository in response to detecting that the first primary hardware becomes operable again after a failure. 4. The system as in claim 1 , wherein the first management hardware includes a primary repository and an auxiliary repository; wherein the second management hardware includes a primary repository and an auxiliary repository; wherein the auxiliary repository of the first management hardware is operable to store: i) a copy of order data stored in the primary repository of the first management hardware, and ii) a copy of order data stored in the primary repository of the second management hardware; and wherein the auxiliary repository of the second management hardware is operable to store: i) a copy of order data stored in the primary repository of the second management hardware, and ii) a copy of order data stored in the primary repository of the first management hardware. 5. The system as in claim 1 , wherein the first orders are received from a first vendor; and wherein the second orders are received from a second vendor. 6. The system as in claim 5 , wherein the order flow manager of the first primary hardware is operative to: forward the first orders and the second orders based on corresponding account information to which a respective order pertains. 7. The system as in claim 1 , wherein the first management hardware includes a primary repository and an auxiliary repository; wherein the second management hardware includes a primary repository and an auxiliary repository; wherein the auxiliary repository of the first management hardware is operable to store a copy of order data stored in the primary repository of the second management hardware as first backup order data; wherein the auxiliary repository of the second management hardware is operable to store a copy of order data stored in the primary repository of the first management hardware as second backup order data; and wherein an auxiliary order manager of the first management hardware is operative to process the second orders using the first backup order data in the auxiliary repository of the first management hardware during third conditions in which the primary order manager of the second management hardware is unable to process the second orders. 8. The system as in claim 7 , wherein the auxiliary order manager of the first management hardware stores data associated with processing of the second orders in the auxiliary repository of the first management hardware during the third conditions. 9. The system as in claim 8 , wherein the first management hardware includes a first data synchronizer resource operative to communicate the first backup order data and the data associated with processing of the second orders to the primary repository of the second management hardware in response to detecting that the primary order manager of the second management hardware no longer experiences a failure. 10. The system as in claim 1 , wherein the first conditions are non-fault conditions in which neither the first management hardware nor the second management hardware experiences a failure. 11. The system as in claim 10 , wherein the second conditions are fault conditions in which the first management hardware experiences a failure and the second management hardware does not experience a failure. 12. The system as in claim 1 , wherein the auxiliary order manager of the second backup hardware is substantially a replica of the primary order manager of the first primary hardware. 13. The system as in claim 1 , wherein the first primary hardware and the second primary hardware operate in an active mode during the first conditions in which neither the first management hardware nor the second management hardware experiences a failure mode; and wherein the first backup hardware and the second backup hardware operate in a standby mode during the first conditions. 14. The system as in claim 1 , wherein the synchronizer is operative to, in response to switching from the second conditions back to the first conditions, copy and store order data generated by the second backup hardware as primary order data stored in the first primary hardware. 15. The system as in claim 1 , wherein the synchronizer is operative to copy and store data generated by the first primary hardware as backup data in a repository of the second backup hardware during the first conditions. 16. A method comprising: implementing first management hardware including first primary hardware and first backup hardware, the first primary hardware including an order flow manager to route orders and a primary order manager to process first orders, the first management hardware disposed at a first geographical location; implementing second ma
Data re-synchronization of a redundant component, or initial sync of replacement, additional or spare unit · CPC title
with a single idle spare processing component · CPC title
maintaining the standby controller/processing unit updated (initialisation or re-synchronisation thereof G06F11/1658 and subgroups) · CPC title
Failover techniques · CPC title
where the redundant components share neither address space nor persistent storage · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.