USRE43933E1 - System for providing fault tolerant data warehousing environment by temporary transmitting data to alternate data warehouse during an interval of primary data warehouse failure - Google Patents

System for providing fault tolerant data warehousing environment by temporary transmitting data to alternate data warehouse during an interval of primary data warehouse failure Download PDF

Info

Publication number
USRE43933E1
USRE43933E1 US12/537,963 US53796309A USRE43933E US RE43933 E1 USRE43933 E1 US RE43933E1 US 53796309 A US53796309 A US 53796309A US RE43933 E USRE43933 E US RE43933E
Authority
US
United States
Prior art keywords
data
data warehouse
alternate
warehouse
premises
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.)
Active, expires
Application number
US12/537,963
Inventor
Bruce Alexander
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Intellectual Ventures Assets 122 LLC
Adeia Technologies Inc
Original Assignee
Hatoshi Investments JP LLC
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Priority to US12/537,963 priority Critical patent/USRE43933E1/en
Application filed by Hatoshi Investments JP LLC filed Critical Hatoshi Investments JP LLC
Application granted granted Critical
Publication of USRE43933E1 publication Critical patent/USRE43933E1/en
Assigned to CHEMTRON RESEARCH LLC reassignment CHEMTRON RESEARCH LLC MERGER (SEE DOCUMENT FOR DETAILS). Assignors: HATOSHI INVESTMENTS JP, LLC
Assigned to INTELLECTUAL VENTURES FUND 83 LLC reassignment INTELLECTUAL VENTURES FUND 83 LLC CORRECTIVE ASSIGNMENT TO CORRECT THE ASSIGNEE NAME PREVIOUSLY RECORDED AT REEL: 037275 FRAME: 0316. ASSIGNOR(S) HEREBY CONFIRMS THE MERGER. Assignors: HATOSHI INVESTMENTS JP, LLC
Assigned to CHEMTRON RESEARCH LLC reassignment CHEMTRON RESEARCH LLC ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: INTELLECTUAL VENTURES FUND 83 LLC
Assigned to HATOSHI INVESTMENTS JP, LLC reassignment HATOSHI INVESTMENTS JP, LLC ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: VIGILOS, INC
Assigned to INTELLECTUAL VENTURES ASSETS 122 LLC reassignment INTELLECTUAL VENTURES ASSETS 122 LLC NUNC PRO TUNC ASSIGNMENT (SEE DOCUMENT FOR DETAILS). Assignors: CHEMTRON RESEARCH LLC
Assigned to VIGILOS, INC. reassignment VIGILOS, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: ALEXANDER, BRUCE
Assigned to ROVI TECHNOLOGIES CORPORATION reassignment ROVI TECHNOLOGIES CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: ROVI CORPORATION
Assigned to ROVI CORPORATION reassignment ROVI CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: INTELLECTUAL VENTURES ASSETS 122 LLC, INTELLECTUAL VENTURES ASSETS 127 LLC
Assigned to HPS INVESTMENT PARTNERS, LLC, AS COLLATERAL AGENT reassignment HPS INVESTMENT PARTNERS, LLC, AS COLLATERAL AGENT SECURITY INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: ROVI GUIDES, INC., ROVI SOLUTIONS CORPORATION, ROVI TECHNOLOGIES CORPORATION, Tivo Solutions, Inc., VEVEO, INC.
Assigned to MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT reassignment MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT PATENT SECURITY AGREEMENT Assignors: ROVI GUIDES, INC., ROVI SOLUTIONS CORPORATION, ROVI TECHNOLOGIES CORPORATION, Tivo Solutions, Inc., VEVEO, INC.
Assigned to BANK OF AMERICA, N.A. reassignment BANK OF AMERICA, N.A. SECURITY INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: DTS, INC., IBIQUITY DIGITAL CORPORATION, INVENSAS BONDING TECHNOLOGIES, INC., INVENSAS CORPORATION, PHORUS, INC., ROVI GUIDES, INC., ROVI SOLUTIONS CORPORATION, ROVI TECHNOLOGIES CORPORATION, TESSERA ADVANCED TECHNOLOGIES, INC., TESSERA, INC., TIVO SOLUTIONS INC., VEVEO, INC.
Assigned to Tivo Solutions, Inc., ROVI TECHNOLOGIES CORPORATION, VEVEO, INC., ROVI SOLUTIONS CORPORATION, ROVI GUIDES, INC. reassignment Tivo Solutions, Inc. RELEASE BY SECURED PARTY (SEE DOCUMENT FOR DETAILS). Assignors: MORGAN STANLEY SENIOR FUNDING, INC.
Assigned to ROVI GUIDES, INC., ROVI SOLUTIONS CORPORATION, Tivo Solutions, Inc., VEVEO, INC., ROVI TECHNOLOGIES CORPORATION reassignment ROVI GUIDES, INC. RELEASE BY SECURED PARTY (SEE DOCUMENT FOR DETAILS). Assignors: HPS INVESTMENT PARTNERS, LLC
Active legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR 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
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/28—Databases characterised by their database models, e.g. relational or object models
    • G06F16/283—Multi-dimensional databases or data warehouses, e.g. MOLAP or ROLAP
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR 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
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR 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/2048—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 where the redundant components share neither address space nor persistent storage

Definitions

  • the present invention relates generally to data storage systems, and in particular, to a method for providing fault-tolerant data warehousing.
  • Data warehousing refers to the various activities involved in the acquisition, management, and aggregation of data from various sources into a centralized repository, such as a database.
  • the database may be hosted by one or more servers, at least some of which may be physically proximate.
  • the central data warehouse may be a virtualized central repository in which a number of distributed servers pool and share data.
  • a data warehouse stores time-oriented data that may be gathered from disparate sources.
  • Data warehousing may be distinguished from the broader category of data archival in that the data warehouse maintains the stored data in a static manner.
  • warehoused data cannot be modified (only added to or deleted) it may be used for analysis over time or by type.
  • the data warehouse may also include metadata used to organize and characterize the data.
  • many database storage solutions also include some type of data restoration process or system that enable data recovery in the event of a hardware and/or software failure. This is generally referred to as storage recovery.
  • One embodiment for storage recovery relates to “mirrored” storage solutions in which one or more identical, redundant data repositories are maintained to replicate, or mirror, the archived data contained in a primary repository. In the event some or all of the data is lost from the primary repository, one or more complete copies of the data exists in the mirrored storage repositories.
  • mirrored storage solutions provide for data recovery in the event that the primary storage repository fails to replicate previously stored data.
  • the data warehouse cannot continue to collect new data. Accordingly, any new data transmitted to the data warehouse would be lost, or the data processing system may have to shut down.
  • failover support relates to the use of a clustered database to transfer data to an alternate collection point in the event of a primary repository failure.
  • a database is installed across two or more servers that are linked together, such that each server in the clustered database is logically viewed as a node on the network.
  • the server nodes do not share processing resources. Environments in which storage and processing resources are not shared between nodes are generally referred to as “shared nothing” architectures. Shared-nothing environments are better suited to large, complex databases supporting unpredictable queries, as in data warehousing.
  • a method and system utilizing one or more data generating computing devices as default data warehouses in the event of a primary data warehouse failure are provided.
  • a data warehouse provides an environment in which data from one or more data servers in one or more locations, or premises, is aggregated in a central database.
  • a warehouse ticket file stored on secure, distributed ticket servers, is used to identify and initialize at least one of the data servers as a failover data warehouse. Once communication between the premises and its primary data warehouse is restored, the data collected during the failover is transferred to the primary data warehouse and purged from the failover data warehouse.
  • a fault tolerant data warehousing method may be implemented in a data collection and processing system including two or more premises servers for collecting data and transmitting the data to a primary data warehouse.
  • a premises server obtains a set of data to be transmitted to a primary data warehouse.
  • the premises server obtains an indication that the primary data warehouse is inoperable to receive the set of data.
  • the premises server then obtains a set of data identifying an alternate data warehouse and transmits the set of data to the identified alternate data warehouse.
  • the alternate data warehouse is selected from the two or more premises servers.
  • a method for providing fault tolerant data warehousing is provided.
  • the method is implemented in a data collection and processing system including two or more premises servers for collecting data and transmitting the data to a primary data warehouse.
  • a premises server obtains a set of data to be transmitted to a primary data warehouse and an indication that the primary data warehouse is inoperable to receive the set of data.
  • the premises server accesses a database associated with a premises server to obtain an identification of an alternate data warehouse associated with the premises server.
  • the premises server suspends the transmission of data between the premises server and the primary data warehouse and transmits premises data to the alternate data warehouse.
  • the alternate data warehouse is selected from the two or more premises servers.
  • a system for providing fault tolerant data warehousing includes two or more premises servers in communication with a number of data generating devices.
  • the premises servers transmit collected data for storage.
  • the system also includes a primary data warehouse for receiving the collected data from the premises servers.
  • the system further includes a database server in communication with the premises server for providing an identification of an alternate data warehouse upon a failure of the primary data warehouse.
  • the alternate data warehouse is selected from the two or more premises servers.
  • FIG. 1 is a block diagram of a representative portion of the Internet
  • FIG. 2A is a block diagram illustrative of a premises including a premises server, monitoring devices, a number of databases, and a client computer in accordance with the present invention
  • FIG. 2B is a block diagram illustrative of a fault-tolerant data warehouse architecture including one or more premises, one or more data repositories, and at least one ticket server formed in accordance with the present invention
  • FIG. 3 is a block diagram depicting an illustrative premises server architecture formed in accordance with the present invention.
  • FIG. 4 is a block diagram depicting an illustrative data warehouse architecture formed in accordance with the present invention.
  • FIG. 5 is a block diagram depicting an illustrative ticket server architecture formed in accordance with the present invention.
  • FIGS. 6A and 6B are flow diagrams of an illustrative fault-tolerant data warehouse process implemented in accordance with the present invention.
  • Internet refers to the collection of networks and routers that use the Transmission Control Protocol/Internet Protocol (“TCP/IP”) to communicate with one another.
  • TCP/IP Transmission Control Protocol/Internet Protocol
  • FIG. 1 A representative section of the Internet 20 is shown in FIG. 1 , where a plurality of local area networks (“LANs”) 24 and a WAN 26 are interconnected by routers 22 .
  • the routers 22 are special purpose computers used to interface one LAN or WAN to another.
  • Communication links within the LANs may be wireless, twisted wire pair, coaxial cable, or optical fiber, while communication links between networks may utilize 56 Kbps analog telephone lines, 1 Mbps digital T-1 lines, 45 Mbps T-3 lines or other communications links known to those skilled in the art.
  • computers 28 and other related electronic devices can be remotely connected to either the LANs 24 or the WAN 26 via a digital communications device, modem and temporary telephone, or a wireless link.
  • the Internet 20 comprises a vast number of such interconnected networks, computers, and routers and that only a small, representative section of the Internet 20 is shown in FIG. 1 .
  • the Internet has recently seen explosive growth by virtue of its ability to link computers located throughout the world. As the Internet has grown, so has the WWW.
  • the WWW is a vast collection of interconnected or “hypertext” documents written in HyperText Markup Language (“HTML”), or other markup languages, that are electronically stored at or dynamically generated by “WWW sites” or “Web sites” throughout the Internet.
  • client-side software programs that communicate over the Web using the TCP/IP protocol are part of the WWW, such as JAVA® applets, instant messaging, e-mail, browser plug-ins, Macromedia Flash, chat and others.
  • Interactive hypertext environments may include proprietary environments such as those provided in America Online or other online service providers, as well as the “wireless Web” provided by various wireless networking providers, especially those in the cellular phone industry. It will be appreciated that the present invention could apply in any such interactive communication environments, however, for purposes of discussion, the Web is used as an exemplary interactive hypertext environment with regard to the present invention.
  • a Web site is a server/computer connected to the Internet that has massive storage capabilities for storing hypertext documents and that runs administrative software for handling requests for those stored hypertext documents as well as dynamically generating hypertext documents.
  • Embedded within a hypertext document are a number of hyperlinks, i.e., highlighted portions of text which link the document to another hypertext document possibly stored at a Web site elsewhere on the Internet.
  • Each hyperlink is assigned a Uniform Resource Locator (“URL”) that provides the name of the linked document on a server connected to the Internet.
  • URL Uniform Resource Locator
  • a Web server may also include facilities for storing and transmitting application programs, such as application programs written in the JAVA® programming language from Sun Microsystems, for execution on a remote computer.
  • a Web server may also include facilities for executing scripts and other application programs on the web server itself.
  • a remote access user may retrieve hypertext documents from the World Wide Web via a Web browser program.
  • a Web browser such as Netscape's NAVIGATOR® or Microsoft's Internet Explorer, is a software application program for providing a user interface to the WWW.
  • the Web browser Upon request from the remote access user via the Web browser, the Web browser requests the desired hypertext document from the appropriate web server using the URL for the document and the HyperText Transport Protocol (“HTTP”).
  • HTTP is a higher-level protocol than TCP/IP and is designed specifically for the requirements of the WWW.
  • HTTP runs on top of TCP/IP to transfer hypertext documents and user-supplied form data between server and client computers.
  • the WWW browser may also retrieve programs from the web server, such as JAVA applets, for execution on the client computer.
  • the WWW browser may include optional software components, called plug-ins, that run specialized functionality within the browser.
  • the fault tolerant data warehouse environment 200 provides for fault tolerant data warehousing functionality. More specifically, the data warehouse environment 200 can provide one or more components operable to direct the transmission of data to an alternate, or substitute, data warehouse repository in response to a system failure or interruption. More specifically, in the event that a system fault prevents the collection of data by a primary data warehouse, the data warehouse environment 200 is operable to designate one or more of the system components as alternative data warehouses and redirect the flow of the data to the alternative data warehouses.
  • the data warehouse environment 200 may initiate the redirection of data to an alternative data warehouse upon receipt of a user request.
  • a system administrator may initiate the redirection of data to an alternative data warehouse to provide for maintenance of the primary data warehouse.
  • the fault tolerant data warehouse environment 200 is illustrative in nature and should not be construed as limiting.
  • the fault tolerant data warehouse environment 200 includes a number of premises 202 , such as a building, or group of buildings, that are associated with an identifiable logical location on a network. Each logical location can generate data to be transferred to a data warehouse, such as for archival purposes.
  • a premises 202 can correspond to a geographic location that can be viewed as a single logical location within the fault tolerant data warehouse environment 200 .
  • each premises 202 is associated with a premises server 204 .
  • the premises server 204 may be local to each premises 202 or otherwise in communication with a premises 202 .
  • Each premises server 204 may be in communication with a number of monitoring devices 205 operable to generate data to be archived.
  • the monitoring devices 205 can include one or more biometric identification devices, including, but not limited to, voice identification devices, image capture devices (e.g., video motion capture and still image capture), microphones, fingerprint identification devices, retinal identification devices, DNA identification devices, and the like.
  • the monitoring devices 205 can also include smoke, fire and carbon monoxide detectors.
  • the monitoring devices 205 can further include door and window access detectors, glass break detectors, motion detectors, audio detectors, metal detectors, explosive detectors and/or infrared detectors. Still further, the monitoring devices 205 may include pressure-sensitive mats or planar surfaces. Still further, the monitoring devices 205 can include conventional panic buttons, global positioning satellite (“GPS”) locators, other geographic locators, medical indicators, and vehicle information systems. The monitoring devices 205 can also be integrated with other existing information systems, such as inventory control systems, accounting systems, reservation systems, point-of-sale terminals/systems, and the like. It will be apparent to one skilled in the relevant art that additional or alternative monitoring devices 205 corresponding to a specific monitoring function may be practiced with the present invention.
  • GPS global positioning satellite
  • the device data can include binary, textual, graphical, and any combination thereof generated by a monitoring device 205 .
  • the device data can include raw data originating from a monitoring device 205 or data processed by the monitoring device 205 after it is captured, by the premises server 204 , or any other computing device. Additionally, the premises server 204 may obtain data to be archived from other sources, such as third-party monitoring systems, and the like.
  • the premises server 204 may also be in communication with a local data repository 206 , a data warehouse ticket location database 208 , a data warehouse identity ticket database 210 , and a data warehouse control data database 212 . Further, the premises 202 can include a client computer 214 operable to communicate with the premises server 204 and additional components of the fault tolerant data warehouse environment 200 .
  • the fault tolerant data warehouse environment 200 may also include a number of data warehouses 216 that are operable to obtain and store data from the premises servers 204 of the environment and that are physically, and or logically, remote from a premises server.
  • the premises server 204 may interact, such as sending and receiving data, with a single data warehouse 216 at one time.
  • a data warehouse 216 may interact, or otherwise be associated, with multiple premises servers 204 .
  • the data warehouse 216 may maintain a data repository 218 and a data warehouse ticket location database 220 .
  • the fault tolerant data warehouse environment 200 may also include a number of ticket servers 220 222.
  • the ticket servers 220 222 are logically remote from the data warehouse 216 .
  • the ticket server 222 maintains a data warehouse identity database 222 224 that includes a number of data warehouse identity tickets.
  • the data warehouse identity tickets includes information operable to identify and initialize a data warehouse 216 with which a given premises server 204 may interact.
  • the ticket server 222 provides a secure repository of the data warehouse tickets stored in ticket files.
  • the various components of the fault tolerant data warehouse environment 200 may communicate via a global communication network, such as Internet 20 .
  • a global communication network such as Internet 20 .
  • some or all of the components may communicate via private or semi-private communication networks.
  • FIG. 3 is a block diagram depicting an illustrative architecture for a premises server 204 .
  • the premises server 204 includes many more components than those shown in FIG. 3 . However, it is not necessary that all of these generally conventional components be shown in order to disclose an illustrative embodiment for practicing the present invention.
  • the premises server 204 includes a network interface 300 for connecting directly to a LAN or a WAN, or for connecting remotely to a LAN or WAN.
  • the network includes the necessary circuitry for such a connection, and is also constructed for use with the TCP/IP protocol, the particular network configuration of the LAN or WAN it is connecting to, and a particular type of coupling medium.
  • the premises server 204 may also be equipped with a modem for connecting to the Internet through a point-to-point protocol (“PPP”) connection or a serial-line Internet protocol (“SLIP”) connection as known to those skilled in the art.
  • PPP point-to-point protocol
  • SLIP serial-line Internet protocol
  • the premises server 204 also includes a processing unit 302 , an optional display 304 , a device interface 306 and a mass memory 308 , all connected via a communication bus, or other communication device.
  • the device interface 306 includes hardware and software components that facilitate interaction with a variety of the monitoring devices via a variety of communication protocols including TCP/IP, X10, digital I/O, RS-232, RS-485 and the like. Additionally, the device interface 306 facilitates communication via a variety of communication mediums including telephone land lines, wireless networks (including cellular, digital and radio networks), cable networks and the like. In an actual embodiment of the present invention, the device interface 306 is implemented as a layer between the server hardware and software applications utilized to control the individual monitoring devices. It will be understood by one skilled in the relevant art that alternative interface configurations may be practiced with the present invention.
  • the mass memory 308 generally comprises a RAM, ROM, and a permanent mass storage device, such as a hard disk drive, tape drive, optical drive, floppy disk drive, or combination thereof.
  • the mass memory 308 stores an operating system 310 for controlling the operation of the premises server 204 . It will be appreciated that this component may comprise a general-purpose server operating system as is known to those skilled in the art, such as UNIX, LINUXTM, or Microsoft WINDOWS NT®.
  • the mass memory 308 also stores program code and data for interfacing with various monitoring devices 206 and for transmitting the monitoring device data. More specifically, the mass memory 308 stores a device interface application 312 in accordance with the present invention for obtaining monitoring device data from a variety of devices and for manipulating the data for processing.
  • the device interface application 312 comprises computer-executable instructions which, when executed by the premises server 204 obtains and transmits device data as will be explained below in greater detail.
  • the mass memory 308 also stores an output interface application program 314 for transmitting processed device data to one or more external system components, including the data warehouse 216 and the ticket server 222 .
  • the operation of the output interface application 314 will be described in greater detail below. It will be appreciated that these components may be stored on a computer-readable medium and loaded into the memory of the premises server using a drive mechanism associated with the computer-readable medium, such as a floppy, CD-ROM, DVD-ROM drive, or network drive 300 .
  • FIG. 4 is a block diagram depicting an illustrative architecture for a data warehouse 216 .
  • the data warehouse 216 includes many more components than those shown in FIG. 4 . However, it is not necessary that all of these generally conventional components be shown in order to disclose an illustrative embodiment for practicing the present invention.
  • the data warehouse 216 includes a network interface 400 for connecting directly to a LAN or a WAN, or for connecting remotely to a LAN or WAN.
  • the network interface 400 includes the necessary circuitry for such a connection, and is also constructed for use with the TCP/IP protocol, the particular network configuration of the LAN or WAN it is connecting to, and a particular type of coupling medium.
  • the data warehouse 216 also includes a processing unit 402 , an optional display 404 and a mass memory 406 , all connected via a communication bus, or other communication device.
  • the mass memory 406 generally comprises a RAM, ROM, and a permanent mass storage device, such as a hard disk drive, tape drive, optical drive, floppy disk drive, or combination thereof.
  • the mass memory 406 stores an operating system 408 for controlling the operation of the data warehouse 216 . It will be appreciated that this component may comprise a general-purpose server operating system.
  • the mass memory 406 also stores program code and data for interfacing with various premises servers 204 and processing the monitoring device data received from the premises servers. More specifically, the mass memory 406 stores a premises server interface application 410 in accordance with the present invention for communicating with a number of premises servers 204 .
  • the premises server interface application 410 includes computer-executable instructions that, when executed by the data warehouse 216 obtains and transmits device data as will be explained below in greater detail.
  • the mass memory 406 also stores a data processing application 412 for processing data received by the data warehouse 416 216. The operation of the data processing application 412 will be described in greater detail below. It will be appreciated that these components may be stored on a computer-readable medium and loaded into the memory of the premises server using a drive mechanism associated with the computer-readable medium, such as a floppy, CD-ROM, DVD-ROM drive, or network drive 400 .
  • FIG. 5 is a block diagram depicting an illustrative architecture for a ticket server 222 .
  • the ticket server 222 includes many more components then those shown in FIG. 5 . However, it is not necessary that all of these generally conventional components be shown in order to disclose an illustrative embodiment for practicing the present invention.
  • the ticket server 222 includes a network interface 500 for connecting directly to a LAN or a WAN, or for connecting remotely to a LAN or WAN.
  • the network interface 500 includes the necessary circuitry for such a connection, and is also constructed for use with the TCP/IP protocol, the particular network configuration of the LAN or WAN it is connecting to, and a particular type of coupling medium.
  • the ticket server 222 also includes a processing unit 502 , an optional display 504 and a mass memory 506 , all connected via a communication bus, or other communication device.
  • the mass memory 506 generally comprises a RAM, ROM, and a permanent mass storage device, such as a hard disk drive, tape drive, optical drive, floppy disk drive, or combination thereof.
  • the mass memory 506 stores an operating system 508 for controlling the operation of the central server. It will be appreciated that this component may comprise a general-purpose server operating system.
  • the mass memory 506 also stores program code and data for interfacing with various premises servers 204 and associating a data warehouse for each premises server. More specifically, the mass memory 506 stores a premises server interface application 510 in accordance with the present invention for communicating with a number of premises servers 204 .
  • the premises server interface application 510 includes computer-executable instructions which, when executed by the data warehouse 216 obtains and transmits data warehouse assignments as will be explained below in greater detail.
  • the mass memory 506 also stores a data processing application 512 for processing data warehouse assignments for a number of premises servers 204 . The operation of the data processing application 512 will be described in greater detail below. It will be appreciated that these components may be stored on a computer-readable medium and loaded into the memory of the premises server using a drive mechanism associated with the computer-readable medium, such as a floppy, CD-ROM, DVD-ROM drive, or network drive 400 .
  • each premises server 204 is associated with at least one data warehouse 216 for transmitting monitoring device data for storage.
  • a data warehouse 216 is designated as the primary data repository for a premises server 204 .
  • the premises server 204 may transmit data as it is generated by the various monitoring devices 205 . Additionally, the premises server 204 may initiate a transfer of data upon the occurrence of a condition, such as a pre-established time period, or a detected event.
  • the premises server 204 may encode the data to facilitate its transmission over the communication network 20 . Additionally, the premises server 204 may also utilize various types of additional encoding for securing the transmission of data.
  • transmission of data to a data warehouse 216 may include additional implementation details.
  • one or more events may occur that prevent a premises server 204 from transmitting data to a designated primary data warehouse 216 .
  • hardware, software, and/or communication media errors may prevent a premises server 204 from establishing reliable communications with the designated primary data warehouse 216 .
  • a data warehouse 216 may detect an error and attempt to transmit an error notification to its assigned premises servers 204 .
  • a premises server 204 may detect an inability to confirm the proper transmission of data and transmit an error notification to other premises servers.
  • one or more users from a client computer 214 may implement a reassignment of a data warehouse 216 .
  • a system administrator may implement a reassignment of a data warehouse 216 to perform scheduled maintenance.
  • a system administrator may implement a reassignment of a data warehouse 216 to perform scheduled maintenance.
  • one or more premises servers 204 upon the detection of an event that may prevent a premises server 204 from transmitting data, one or more premises servers 204 will be reassigned as alternative data warehouses to allow for the continuous processing of data by any number of premises servers in the fault tolerant data warehouse environment 200 .
  • an error message is generated and sent to a ticket server 222 .
  • the error message may be generated by the data warehouse 216 upon the detection of an error condition.
  • the error message may also be generated by the premises server 204 upon the detection of a fault.
  • the error message may be generated by an authorized user, such as a system administrator, utilizing a client computer 214 .
  • the data processing application 512 of the ticket server 222 identifies an alternative data warehouse available for a given premises server 204 associated with the data warehouse 216 .
  • the data processing application 512 obtains a warehouse ticket file corresponding to the premises server 204 that indicates another premises server in the fault tolerant data warehouse environment 200 that will serve as an alternative data warehouse.
  • the warehouse ticket file may be a static file that includes pre-assigned alternative premises servers 204 .
  • the warehouse ticket file may be dynamically generated based upon a variety of factors, including available memory resources of a variety of premises servers 204 , communication network availability, and the like.
  • the warehouse ticket file may also indicate that a particular premises server 204 may serve as its own alternative data warehouse.
  • the ticket server 222 transmits the identified alternative data warehouse to all applicable premises servers 204 .
  • the ticket server 222 may transmit an alternative data warehouse to a single premises server 204 .
  • the ticket server 222 may transmit an alternative data warehouse to any number of premises servers 204 that are affected by the event. For example, if only a portion of the communication network is not available, the ticket server 222 may transmit alternative data warehouses for all premises servers 204 affected by the communication network unavailability.
  • the premises server(s) obtain the transmitted data warehouse ticket and attempt to contact the designated alternate data warehouse at block 610 .
  • the warehouse ticket can include control and contact information that allows the premises server 204 to contact the alternate data warehouse. Additionally, the control and contact information may also include special processing information for a particular alternate data warehouse. Additionally, some or all of the control information may be stored in the warehouse control archive database 210 .
  • a test is conducted to determine whether the alternate data warehouse is available. If the alternative data warehouse is not available, the routine 600 returns to block 604 , where the ticket server 222 attempts to identify another alternate data warehouse. With reference to FIG. 6B , if the alternate data warehouse is available, the premises server 204 begins transmitting data to the alternate warehouse at block 614 .
  • a test is conducted to determine whether primary data warehouse 216 is available.
  • the premises server 204 may periodically test the communication network to determine whether the primary data warehouse 216 is available. Alternatively, the data warehouse 216 may transmit a notification when it is available. If the primary data warehouse 216 remains unavailable, the routine 600 returns to block 614 . If the primary data warehouse 216 is available, at block 618 , the premises server 204 is instructed to begin transmitting data to the primary data warehouse. At block 620 , the alternate data warehouse transmits the temporarily stored data to the primary data warehouse. At block 622 , the routine 600 terminates.

Abstract

A method and system utilizing one or more data generating computing devices as default data warehouses in the event of a primary data warehouse failure are provided. A data warehouse provides an environment in which data from one or more data servers in one or more locations, or premises, is aggregated in a central database. In the event of a system failure, in which communication between the data warehouse and one or more servers is disrupted, a warehouse ticket file, stored on secure, distributed ticket servers, is used to identify and initialize at least one of the data servers as a failover data warehouse. Once communication between the premises and its primary data warehouse is restored, the data collected during the failover is transferred to the primary data warehouse and purged from the failover data warehouse.

Description

CROSS-REFERENCE TO RELATED APPLICATION
This application claims the benefit of U.S. Provisional Application No. 60/371,273, entitled System and Method for Providing A Fault-Tolerant Data Warehouse Environment, and filed on Apr. 9, 2002. U.S. Provisional Application No. 60/371,273 is incorporated by reference herein.
FIELD OF THE INVENTION
The present invention relates generally to data storage systems, and in particular, to a method for providing fault-tolerant data warehousing.
BACKGROUND OF THE INVENTION
Generally described, most corporate and governmental entities utilize computer systems, computer networks, and integrated devices that generate vast amounts of electronic data. In some cases, data is generated, processed, and discarded after serving an intended purpose. In other cases, corporate, governmental, or other entities require that data be stored and maintained for future use. Such storage methods and systems may be generically referred to as “archival.” Accordingly, many data generating users look for storage solutions that correspond to the type and amount of data to be archived.
A growing category of archival is known as data warehousing. Data warehousing refers to the various activities involved in the acquisition, management, and aggregation of data from various sources into a centralized repository, such as a database. The database may be hosted by one or more servers, at least some of which may be physically proximate. Additionally, the central data warehouse may be a virtualized central repository in which a number of distributed servers pool and share data. In a typical application, a data warehouse stores time-oriented data that may be gathered from disparate sources. Data warehousing may be distinguished from the broader category of data archival in that the data warehouse maintains the stored data in a static manner. Because warehoused data cannot be modified (only added to or deleted) it may be used for analysis over time or by type. The data warehouse may also include metadata used to organize and characterize the data. In addition to the ability to store and retrieve data, many database storage solutions also include some type of data restoration process or system that enable data recovery in the event of a hardware and/or software failure. This is generally referred to as storage recovery. One embodiment for storage recovery relates to “mirrored” storage solutions in which one or more identical, redundant data repositories are maintained to replicate, or mirror, the archived data contained in a primary repository. In the event some or all of the data is lost from the primary repository, one or more complete copies of the data exists in the mirrored storage repositories. Accordingly, mirrored storage solutions provide for data recovery in the event that the primary storage repository fails to replicate previously stored data. However, once the primary storage repository fails, the data warehouse cannot continue to collect new data. Accordingly, any new data transmitted to the data warehouse would be lost, or the data processing system may have to shut down.
One attempt to provide additional data warehouse fault tolerance, referred to generally as failover support, relates to the use of a clustered database to transfer data to an alternate collection point in the event of a primary repository failure. In accordance with this embodiment, a database is installed across two or more servers that are linked together, such that each server in the clustered database is logically viewed as a node on the network. To provide for true failover support, the server nodes do not share processing resources. Environments in which storage and processing resources are not shared between nodes are generally referred to as “shared nothing” architectures. Shared-nothing environments are better suited to large, complex databases supporting unpredictable queries, as in data warehousing. Although a shared-nothing environment potentially allows for continued data collection in the event of a failure, the costs involved in providing and maintaining multiple servers for storage redundancy are prohibitive for many potential users. Accordingly, a clustered database approach may not present an affordable solution for many data warehouse applications.
Therefore, there is a need for a resource-efficient, fault-tolerant solution for data warehousing that will provide continuity of the data warehouse function in the event of a network, hardware, or software failure.
SUMMARY OF THE INVENTION
A method and system utilizing one or more data generating computing devices as default data warehouses in the event of a primary data warehouse failure are provided. A data warehouse provides an environment in which data from one or more data servers in one or more locations, or premises, is aggregated in a central database. In the event of a system failure, in which communication between the data warehouse and one or more servers is disrupted, a warehouse ticket file, stored on secure, distributed ticket servers, is used to identify and initialize at least one of the data servers as a failover data warehouse. Once communication between the premises and its primary data warehouse is restored, the data collected during the failover is transferred to the primary data warehouse and purged from the failover data warehouse.
In accordance with an aspect of the present invention, a fault tolerant data warehousing method is provided. The method may be implemented in a data collection and processing system including two or more premises servers for collecting data and transmitting the data to a primary data warehouse. In accordance with the present invention, a premises server obtains a set of data to be transmitted to a primary data warehouse. The premises server obtains an indication that the primary data warehouse is inoperable to receive the set of data. The premises server then obtains a set of data identifying an alternate data warehouse and transmits the set of data to the identified alternate data warehouse. The alternate data warehouse is selected from the two or more premises servers.
In accordance with a further aspect of the present invention, a method for providing fault tolerant data warehousing is provided. The method is implemented in a data collection and processing system including two or more premises servers for collecting data and transmitting the data to a primary data warehouse. In accordance with the method, a premises server obtains a set of data to be transmitted to a primary data warehouse and an indication that the primary data warehouse is inoperable to receive the set of data. The premises server accesses a database associated with a premises server to obtain an identification of an alternate data warehouse associated with the premises server. The premises server suspends the transmission of data between the premises server and the primary data warehouse and transmits premises data to the alternate data warehouse. The alternate data warehouse is selected from the two or more premises servers.
In accordance with a further aspect of the present invention, a system for providing fault tolerant data warehousing is provided. The system includes two or more premises servers in communication with a number of data generating devices. The premises servers transmit collected data for storage. The system also includes a primary data warehouse for receiving the collected data from the premises servers. The system further includes a database server in communication with the premises server for providing an identification of an alternate data warehouse upon a failure of the primary data warehouse. The alternate data warehouse is selected from the two or more premises servers.
BRIEF DESCRIPTION OF THE DRAWINGS
The foregoing aspects and many of the attendant advantages of this invention will become more readily appreciated as the same become better understood by reference to the following detailed description, when taken in conjunction with the accompanying drawings, wherein:
FIG. 1 is a block diagram of a representative portion of the Internet;
FIG. 2A is a block diagram illustrative of a premises including a premises server, monitoring devices, a number of databases, and a client computer in accordance with the present invention;
FIG. 2B is a block diagram illustrative of a fault-tolerant data warehouse architecture including one or more premises, one or more data repositories, and at least one ticket server formed in accordance with the present invention;
FIG. 3 is a block diagram depicting an illustrative premises server architecture formed in accordance with the present invention;
FIG. 4 is a block diagram depicting an illustrative data warehouse architecture formed in accordance with the present invention;
FIG. 5 is a block diagram depicting an illustrative ticket server architecture formed in accordance with the present invention; and
FIGS. 6A and 6B are flow diagrams of an illustrative fault-tolerant data warehouse process implemented in accordance with the present invention.
 DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT
As described above, aspects of the present invention may be embodied in a WWW or Web site accessible via the Internet. As is well known to those skilled in the art, the term “Internet” refers to the collection of networks and routers that use the Transmission Control Protocol/Internet Protocol (“TCP/IP”) to communicate with one another. A representative section of the Internet 20 is shown in FIG. 1, where a plurality of local area networks (“LANs”) 24 and a WAN 26 are interconnected by routers 22. The routers 22 are special purpose computers used to interface one LAN or WAN to another. Communication links within the LANs may be wireless, twisted wire pair, coaxial cable, or optical fiber, while communication links between networks may utilize 56 Kbps analog telephone lines, 1 Mbps digital T-1 lines, 45 Mbps T-3 lines or other communications links known to those skilled in the art.
Furthermore, computers 28 and other related electronic devices can be remotely connected to either the LANs 24 or the WAN 26 via a digital communications device, modem and temporary telephone, or a wireless link. It will be appreciated that the Internet 20 comprises a vast number of such interconnected networks, computers, and routers and that only a small, representative section of the Internet 20 is shown in FIG. 1.
The Internet has recently seen explosive growth by virtue of its ability to link computers located throughout the world. As the Internet has grown, so has the WWW. As is appreciated by those skilled in the art, the WWW is a vast collection of interconnected or “hypertext” documents written in HyperText Markup Language (“HTML”), or other markup languages, that are electronically stored at or dynamically generated by “WWW sites” or “Web sites” throughout the Internet. Additionally, client-side software programs that communicate over the Web using the TCP/IP protocol are part of the WWW, such as JAVA® applets, instant messaging, e-mail, browser plug-ins, Macromedia Flash, chat and others. Other interactive hypertext environments may include proprietary environments such as those provided in America Online or other online service providers, as well as the “wireless Web” provided by various wireless networking providers, especially those in the cellular phone industry. It will be appreciated that the present invention could apply in any such interactive communication environments, however, for purposes of discussion, the Web is used as an exemplary interactive hypertext environment with regard to the present invention.
A Web site is a server/computer connected to the Internet that has massive storage capabilities for storing hypertext documents and that runs administrative software for handling requests for those stored hypertext documents as well as dynamically generating hypertext documents. Embedded within a hypertext document are a number of hyperlinks, i.e., highlighted portions of text which link the document to another hypertext document possibly stored at a Web site elsewhere on the Internet. Each hyperlink is assigned a Uniform Resource Locator (“URL”) that provides the name of the linked document on a server connected to the Internet. Thus, whenever a hypertext document is retrieved from any Web server, the document is considered retrieved from the World Wide Web. Known to those skilled in the art, a Web server may also include facilities for storing and transmitting application programs, such as application programs written in the JAVA® programming language from Sun Microsystems, for execution on a remote computer. Likewise, a Web server may also include facilities for executing scripts and other application programs on the web server itself.
A remote access user may retrieve hypertext documents from the World Wide Web via a Web browser program. A Web browser, such as Netscape's NAVIGATOR® or Microsoft's Internet Explorer, is a software application program for providing a user interface to the WWW. Upon request from the remote access user via the Web browser, the Web browser requests the desired hypertext document from the appropriate web server using the URL for the document and the HyperText Transport Protocol (“HTTP”). HTTP is a higher-level protocol than TCP/IP and is designed specifically for the requirements of the WWW. HTTP runs on top of TCP/IP to transfer hypertext documents and user-supplied form data between server and client computers. The WWW browser may also retrieve programs from the web server, such as JAVA applets, for execution on the client computer. Finally, the WWW browser may include optional software components, called plug-ins, that run specialized functionality within the browser.
Referring now to FIGS. 2A and 2B, an actual embodiment of a fault tolerant data warehouse environment 200 formed in accordance with the present invention will be described. In accordance with an illustrative embodiment of the present invention, the fault tolerant data warehouse environment 200 provides for fault tolerant data warehousing functionality. More specifically, the data warehouse environment 200 can provide one or more components operable to direct the transmission of data to an alternate, or substitute, data warehouse repository in response to a system failure or interruption. More specifically, in the event that a system fault prevents the collection of data by a primary data warehouse, the data warehouse environment 200 is operable to designate one or more of the system components as alternative data warehouses and redirect the flow of the data to the alternative data warehouses. Additionally, the data warehouse environment 200 may initiate the redirection of data to an alternative data warehouse upon receipt of a user request. For example, a system administrator may initiate the redirection of data to an alternative data warehouse to provide for maintenance of the primary data warehouse. However, one skilled in the relevant art will appreciate that the fault tolerant data warehouse environment 200 is illustrative in nature and should not be construed as limiting.
With reference now to FIG. 2A, the fault tolerant data warehouse environment 200 includes a number of premises 202, such as a building, or group of buildings, that are associated with an identifiable logical location on a network. Each logical location can generate data to be transferred to a data warehouse, such as for archival purposes. For example, a premises 202 can correspond to a geographic location that can be viewed as a single logical location within the fault tolerant data warehouse environment 200.
In an illustrative embodiment of the present invention, each premises 202 is associated with a premises server 204. The premises server 204 may be local to each premises 202 or otherwise in communication with a premises 202. Each premises server 204 may be in communication with a number of monitoring devices 205 operable to generate data to be archived. In an illustrative embodiment of the present invention, the monitoring devices 205 can include one or more biometric identification devices, including, but not limited to, voice identification devices, image capture devices (e.g., video motion capture and still image capture), microphones, fingerprint identification devices, retinal identification devices, DNA identification devices, and the like. The monitoring devices 205 can also include smoke, fire and carbon monoxide detectors. The monitoring devices 205 can further include door and window access detectors, glass break detectors, motion detectors, audio detectors, metal detectors, explosive detectors and/or infrared detectors. Still further, the monitoring devices 205 may include pressure-sensitive mats or planar surfaces. Still further, the monitoring devices 205 can include conventional panic buttons, global positioning satellite (“GPS”) locators, other geographic locators, medical indicators, and vehicle information systems. The monitoring devices 205 can also be integrated with other existing information systems, such as inventory control systems, accounting systems, reservation systems, point-of-sale terminals/systems, and the like. It will be apparent to one skilled in the relevant art that additional or alternative monitoring devices 205 corresponding to a specific monitoring function may be practiced with the present invention. Additionally, the device data can include binary, textual, graphical, and any combination thereof generated by a monitoring device 205. The device data can include raw data originating from a monitoring device 205 or data processed by the monitoring device 205 after it is captured, by the premises server 204, or any other computing device. Additionally, the premises server 204 may obtain data to be archived from other sources, such as third-party monitoring systems, and the like.
The premises server 204 may also be in communication with a local data repository 206, a data warehouse ticket location database 208, a data warehouse identity ticket database 210, and a data warehouse control data database 212. Further, the premises 202 can include a client computer 214 operable to communicate with the premises server 204 and additional components of the fault tolerant data warehouse environment 200.
With reference now to FIG. 2B, the fault tolerant data warehouse environment 200 may also include a number of data warehouses 216 that are operable to obtain and store data from the premises servers 204 of the environment and that are physically, and or logically, remote from a premises server. In an illustrative embodiment of the present invention, the premises server 204 may interact, such as sending and receiving data, with a single data warehouse 216 at one time. Conversely, a data warehouse 216 may interact, or otherwise be associated, with multiple premises servers 204. In an illustrative embodiment of the present invention, the data warehouse 216 may maintain a data repository 218 and a data warehouse ticket location database 220.
With continued reference to FIG. 2B, the fault tolerant data warehouse environment 200 may also include a number of ticket servers 220 222. In an illustrative embodiment of the present invention, the ticket servers 220 222 are logically remote from the data warehouse 216. The ticket server 222 maintains a data warehouse identity database 222 224 that includes a number of data warehouse identity tickets. The data warehouse identity tickets includes information operable to identify and initialize a data warehouse 216 with which a given premises server 204 may interact. In an actual embodiment of the present invention the ticket server 222 provides a secure repository of the data warehouse tickets stored in ticket files.
In an actual embodiment of the present invention the various components of the fault tolerant data warehouse environment 200 may communicate via a global communication network, such as Internet 20. Alternatively, some or all of the components may communicate via private or semi-private communication networks.
FIG. 3 is a block diagram depicting an illustrative architecture for a premises server 204. Those of ordinary skill in the art will appreciate that the premises server 204 includes many more components than those shown in FIG. 3. However, it is not necessary that all of these generally conventional components be shown in order to disclose an illustrative embodiment for practicing the present invention. As shown in FIG. 3, the premises server 204 includes a network interface 300 for connecting directly to a LAN or a WAN, or for connecting remotely to a LAN or WAN. Those of ordinary skill in the art will appreciate that the network includes the necessary circuitry for such a connection, and is also constructed for use with the TCP/IP protocol, the particular network configuration of the LAN or WAN it is connecting to, and a particular type of coupling medium. The premises server 204 may also be equipped with a modem for connecting to the Internet through a point-to-point protocol (“PPP”) connection or a serial-line Internet protocol (“SLIP”) connection as known to those skilled in the art.
The premises server 204 also includes a processing unit 302, an optional display 304, a device interface 306 and a mass memory 308, all connected via a communication bus, or other communication device. The device interface 306 includes hardware and software components that facilitate interaction with a variety of the monitoring devices via a variety of communication protocols including TCP/IP, X10, digital I/O, RS-232, RS-485 and the like. Additionally, the device interface 306 facilitates communication via a variety of communication mediums including telephone land lines, wireless networks (including cellular, digital and radio networks), cable networks and the like. In an actual embodiment of the present invention, the device interface 306 is implemented as a layer between the server hardware and software applications utilized to control the individual monitoring devices. It will be understood by one skilled in the relevant art that alternative interface configurations may be practiced with the present invention.
The mass memory 308 generally comprises a RAM, ROM, and a permanent mass storage device, such as a hard disk drive, tape drive, optical drive, floppy disk drive, or combination thereof. The mass memory 308 stores an operating system 310 for controlling the operation of the premises server 204. It will be appreciated that this component may comprise a general-purpose server operating system as is known to those skilled in the art, such as UNIX, LINUX™, or Microsoft WINDOWS NT®.
The mass memory 308 also stores program code and data for interfacing with various monitoring devices 206 and for transmitting the monitoring device data. More specifically, the mass memory 308 stores a device interface application 312 in accordance with the present invention for obtaining monitoring device data from a variety of devices and for manipulating the data for processing. The device interface application 312 comprises computer-executable instructions which, when executed by the premises server 204 obtains and transmits device data as will be explained below in greater detail. The mass memory 308 also stores an output interface application program 314 for transmitting processed device data to one or more external system components, including the data warehouse 216 and the ticket server 222. The operation of the output interface application 314 will be described in greater detail below. It will be appreciated that these components may be stored on a computer-readable medium and loaded into the memory of the premises server using a drive mechanism associated with the computer-readable medium, such as a floppy, CD-ROM, DVD-ROM drive, or network drive 300.
FIG. 4 is a block diagram depicting an illustrative architecture for a data warehouse 216. Those of ordinary skill in the art will appreciate that the data warehouse 216 includes many more components than those shown in FIG. 4. However, it is not necessary that all of these generally conventional components be shown in order to disclose an illustrative embodiment for practicing the present invention. The data warehouse 216 includes a network interface 400 for connecting directly to a LAN or a WAN, or for connecting remotely to a LAN or WAN. Those of ordinary skill in the art will appreciate that the network interface 400 includes the necessary circuitry for such a connection, and is also constructed for use with the TCP/IP protocol, the particular network configuration of the LAN or WAN it is connecting to, and a particular type of coupling medium.
The data warehouse 216 also includes a processing unit 402, an optional display 404 and a mass memory 406, all connected via a communication bus, or other communication device. The mass memory 406 generally comprises a RAM, ROM, and a permanent mass storage device, such as a hard disk drive, tape drive, optical drive, floppy disk drive, or combination thereof. The mass memory 406 stores an operating system 408 for controlling the operation of the data warehouse 216. It will be appreciated that this component may comprise a general-purpose server operating system.
The mass memory 406 also stores program code and data for interfacing with various premises servers 204 and processing the monitoring device data received from the premises servers. More specifically, the mass memory 406 stores a premises server interface application 410 in accordance with the present invention for communicating with a number of premises servers 204. The premises server interface application 410 includes computer-executable instructions that, when executed by the data warehouse 216 obtains and transmits device data as will be explained below in greater detail. The mass memory 406 also stores a data processing application 412 for processing data received by the data warehouse 416 216. The operation of the data processing application 412 will be described in greater detail below. It will be appreciated that these components may be stored on a computer-readable medium and loaded into the memory of the premises server using a drive mechanism associated with the computer-readable medium, such as a floppy, CD-ROM, DVD-ROM drive, or network drive 400.
FIG. 5 is a block diagram depicting an illustrative architecture for a ticket server 222. Those of ordinary skill in the art will appreciate that the ticket server 222 includes many more components then those shown in FIG. 5. However, it is not necessary that all of these generally conventional components be shown in order to disclose an illustrative embodiment for practicing the present invention. The ticket server 222 includes a network interface 500 for connecting directly to a LAN or a WAN, or for connecting remotely to a LAN or WAN. Those of ordinary skill in the art will appreciate that the network interface 500 includes the necessary circuitry for such a connection, and is also constructed for use with the TCP/IP protocol, the particular network configuration of the LAN or WAN it is connecting to, and a particular type of coupling medium.
The ticket server 222 also includes a processing unit 502, an optional display 504 and a mass memory 506, all connected via a communication bus, or other communication device. The mass memory 506 generally comprises a RAM, ROM, and a permanent mass storage device, such as a hard disk drive, tape drive, optical drive, floppy disk drive, or combination thereof. The mass memory 506 stores an operating system 508 for controlling the operation of the central server. It will be appreciated that this component may comprise a general-purpose server operating system.
The mass memory 506 also stores program code and data for interfacing with various premises servers 204 and associating a data warehouse for each premises server. More specifically, the mass memory 506 stores a premises server interface application 510 in accordance with the present invention for communicating with a number of premises servers 204. The premises server interface application 510 includes computer-executable instructions which, when executed by the data warehouse 216 obtains and transmits data warehouse assignments as will be explained below in greater detail. The mass memory 506 also stores a data processing application 512 for processing data warehouse assignments for a number of premises servers 204. The operation of the data processing application 512 will be described in greater detail below. It will be appreciated that these components may be stored on a computer-readable medium and loaded into the memory of the premises server using a drive mechanism associated with the computer-readable medium, such as a floppy, CD-ROM, DVD-ROM drive, or network drive 400.
In one aspect of the present invention, each premises server 204 is associated with at least one data warehouse 216 for transmitting monitoring device data for storage. In an illustrative embodiment of the present invention, a data warehouse 216 is designated as the primary data repository for a premises server 204. The premises server 204 may transmit data as it is generated by the various monitoring devices 205. Additionally, the premises server 204 may initiate a transfer of data upon the occurrence of a condition, such as a pre-established time period, or a detected event. The premises server 204 may encode the data to facilitate its transmission over the communication network 20. Additionally, the premises server 204 may also utilize various types of additional encoding for securing the transmission of data. One skilled in the relevant art will appreciate that transmission of data to a data warehouse 216 may include additional implementation details.
In accordance with the present invention, one or more events may occur that prevent a premises server 204 from transmitting data to a designated primary data warehouse 216. In one aspect of the present invention, hardware, software, and/or communication media errors may prevent a premises server 204 from establishing reliable communications with the designated primary data warehouse 216. For example, a data warehouse 216 may detect an error and attempt to transmit an error notification to its assigned premises servers 204. In another example, a premises server 204 may detect an inability to confirm the proper transmission of data and transmit an error notification to other premises servers. In another aspect of the present invention, one or more users from a client computer 214 may implement a reassignment of a data warehouse 216. For example, a system administrator may implement a reassignment of a data warehouse 216 to perform scheduled maintenance. As will be explained in greater detail below, upon the detection of an event that may prevent a premises server 204 from transmitting data, one or more premises servers 204 will be reassigned as alternative data warehouses to allow for the continuous processing of data by any number of premises servers in the fault tolerant data warehouse environment 200.
With reference now to FIGS. 6A and 6B, a routine 600 for the utilization of a fault tolerant data warehouse environment will be described. With reference to FIG. 6A, in response to a disruption between a premises server 204 and a data warehouse 216, at block 602, an error message is generated and sent to a ticket server 222. In an illustrative embodiment of the present invention, the error message may be generated by the data warehouse 216 upon the detection of an error condition. The error message may also be generated by the premises server 204 upon the detection of a fault. Still further, the error message may be generated by an authorized user, such as a system administrator, utilizing a client computer 214.
At block 604, the data processing application 512 of the ticket server 222 identifies an alternative data warehouse available for a given premises server 204 associated with the data warehouse 216. In an illustrative embodiment of the present invention, the data processing application 512 obtains a warehouse ticket file corresponding to the premises server 204 that indicates another premises server in the fault tolerant data warehouse environment 200 that will serve as an alternative data warehouse. The warehouse ticket file may be a static file that includes pre-assigned alternative premises servers 204. Alternatively, the warehouse ticket file may be dynamically generated based upon a variety of factors, including available memory resources of a variety of premises servers 204, communication network availability, and the like. In one embodiment, the warehouse ticket file may also indicate that a particular premises server 204 may serve as its own alternative data warehouse.
At block 606, the ticket server 222 transmits the identified alternative data warehouse to all applicable premises servers 204. In one embodiment of the present invention, the ticket server 222 may transmit an alternative data warehouse to a single premises server 204. Additionally, the ticket server 222 may transmit an alternative data warehouse to any number of premises servers 204 that are affected by the event. For example, if only a portion of the communication network is not available, the ticket server 222 may transmit alternative data warehouses for all premises servers 204 affected by the communication network unavailability.
At block 608, the premises server(s) obtain the transmitted data warehouse ticket and attempt to contact the designated alternate data warehouse at block 610. In an illustrative embodiment of the present invention, the warehouse ticket can include control and contact information that allows the premises server 204 to contact the alternate data warehouse. Additionally, the control and contact information may also include special processing information for a particular alternate data warehouse. Additionally, some or all of the control information may be stored in the warehouse control archive database 210. At decision block 612, a test is conducted to determine whether the alternate data warehouse is available. If the alternative data warehouse is not available, the routine 600 returns to block 604, where the ticket server 222 attempts to identify another alternate data warehouse. With reference to FIG. 6B, if the alternate data warehouse is available, the premises server 204 begins transmitting data to the alternate warehouse at block 614.
At decision block 616, a test is conducted to determine whether primary data warehouse 216 is available. In an illustrative embodiment of the present invention, the premises server 204 may periodically test the communication network to determine whether the primary data warehouse 216 is available. Alternatively, the data warehouse 216 may transmit a notification when it is available. If the primary data warehouse 216 remains unavailable, the routine 600 returns to block 614. If the primary data warehouse 216 is available, at block 618, the premises server 204 is instructed to begin transmitting data to the primary data warehouse. At block 620, the alternate data warehouse transmits the temporarily stored data to the primary data warehouse. At block 622, the routine 600 terminates.
While illustrative embodiments of the invention have been illustrated and described, it will be appreciated that various changes can be made therein without departing from the spirit and scope of the invention.

Claims (41)

1. In a data collection and processing system including two or more premises servers for collecting data and transmitting the data to a primary data warehouse, a method for providing fault tolerant data warehousing, the method comprising:
obtaining a set of data to be transmitted to a primary data warehouse;
obtaining an indication that the primary data warehouse is inoperable to receive the set of data;
obtaining information identifying an alternate data warehouse to receive the set of data; and
transmitting the set of data to the identified alternate data warehouse;
wherein the alternate data warehouse is selected from the two or more premises servers;
obtaining an indication that the primary data warehouse can receive data;
transmitting data to the primary data warehouse upon obtaining the indication; and
suspending data transmission to the alternate data warehouse.
2. The method as recited in claim 1 further comprising obtaining information for initializing the alternate data warehouse, and initializing the designated alternate data warehouse prior to transmitting the set of data.
3. The method as recited in claim 1, wherein obtaining information identifying an alternate data warehouse includes:
transmitting a request to obtain an alternate data warehouse including one or more selection attributes; and
obtaining information identifying an alternate data warehouse based upon a processing of the selection attributes.
4. The method as recited in claim 3, wherein the selection attributes correspond to the collected data.
5. The method as recited in claim 3, wherein the selection attributes correspond to the premises server transmitting the collected data.
6. The method as recited in claim 3, wherein obtaining information identifying an alternate data warehouse based upon a processing of the selection attributes includes obtaining a pre-assigned alternate data warehouse corresponding to the selection attributes.
7. The method as recited in claim 3, wherein obtaining information identifying an alternate data warehouse based upon a processing of the selection attributes includes obtaining a dynamically assigned alternate data warehouse corresponding to the selection attributes.
8. The method as recited in claim 1, wherein the identified alternate data warehouse is not operable to receive data until being assigned as the alternate data warehouse.
9. The method as recited in claim 1, wherein transmitting the set of data to the identified alternate data warehouse includes storing the data locally as the identified alternate data warehouse.
10. A computer-readable medium storage device having computer-executable instructions for performing the method recited in claim 1.
11. A computer system having a processor, a memory and an operating environment, the computer system operable to perform the method recited in claim 1.
12. In a data collection and processing system including two or more premises servers for collecting data and transmitting the data to a primary data warehouse, a method for providing fault tolerant data warehousing, the method comprising:
obtaining a set of data to be transmitted to a primary data warehouse;
obtaining an indication that the primary data warehouse is inoperable to receive the set of data;
accessing a database associated with a premises server to obtain an identification of an alternate data warehouse associated with the premises server;
suspending transmission of data between the premises server and the primary data warehouse;
transmitting premises data to the alternate data warehouse;
wherein the alternate data warehouse is selected from the two or more premises servers;
obtaining an indication that the primary data warehouse can receive data;
transmitting data to the primary data warehouse upon obtaining the indication; and
suspending data transmission to the alternate data warehouse.
13. The method as recited in claim 1 further comprising accessing the database associated with a premises server to obtain information for initializing the alternate data warehouse from the database, and initializing the designated alternate data warehouse prior to transmitting the set of data.
14. The method as recited in claim 12, wherein accessing a database associated with a premises server to obtain an identification of an alternate data warehouse associated with the premises server includes:
transmitting a request to obtain an alternate data warehouse including one or more selection attributes; and
obtaining information identifying an alternate data warehouse based upon a processing of the selection attributes.
15. The method as recited in claim 14, wherein the selection attributes correspond to the premises data.
16. The method as recited in claim 14, wherein the selection attributes correspond to the premises server transmitting the premises data.
17. The method as recited in claim 14, wherein obtaining information identifying an alternate data warehouse based upon a processing of the selection attributes includes obtaining a pre-assigned alternate data warehouse corresponding to the selection attributes.
18. The method as recited in claim 14, wherein obtaining information identifying an alternate data warehouse based upon a processing of the selection attributes includes obtaining a dynamically assigned alternate data warehouse corresponding to the selection attributes.
19. The method as recited in claim 12, wherein the identified alternate data warehouse is not operable to receive data until being assigned as the alternate data warehouse.
20. The method as recited in claim 12, wherein transmitting the set of data to the identified alternate data warehouse includes storing the premises data locally as the identified alternate data warehouse.
21. The method as recited in claim 12, wherein the database associated with a premises server is an external database common to all premises in the data collection and processing system.
22. A computer-readable medium storage device having computer-executable instructions for performing the method recited in claim 12.
23. A computer system having a processor, a memory and an operating environment, the computer system operable to perform the method recited in claim 12.
24. A system for providing fault tolerant data warehousing comprising:
two or more premises servers in communication with a number of data generating devices, wherein the premises servers transmit collected data for storage;
a primary data warehouse for receiving the collected data from transmitted by the premises servers;
a database server in communication with the premises server for:
providing an identification of an alternate data warehouse upon a failure of the primary data warehouse;
causing data to be transmitted to the alternate data warehouse upon providing the identification of the failure;
providing an identification that the primary data warehouse can receive data;
suspending data transmission to the alternate data warehouse upon the identification that the primary data warehouse can receive data;
causing data to be transmitted to the primary data warehouse; and
wherein the alternate data warehouse is selected from the two or more premises servers.
25. The system as recited in claim 24, wherein the premises server is logically remote from the alternate data warehouse prior to an identification of the alternate warehouse.
26. The system as recited in claim 24, wherein the primary data warehouse is physically remote from the alternate data warehouse.
27. The system as recited in claim 24, wherein the alternate data warehouse is preselected to correspond to a particular premises server.
28. The system as recited in claim 27, wherein the system includes at least two alternate data warehouses.
29. The system as recited in claim 24, wherein the alternate data warehouse is dynamically selected to correspond to a particular premises server.
30. The system as recited in claim 24, wherein a premises server serves as its own alternate data warehouse.
31. In a data collection and processing system including two or more premises servers for collecting data and transmitting the data to a primary data warehouse, a method for providing fault tolerant data warehousing, the method comprising:
obtaining information identifying an alternate data warehouse to receive a set of data when a primary data warehouse is inoperable to receive the set of data;
transmitting the set of data to the identified alternate data warehouse;
wherein the alternate data warehouse is selected from the two or more premises servers;
obtaining an indication that the primary data warehouse can receive data;
transmitting data to the primary data warehouse upon obtaining the indication; and
suspending data transmission to the alternate data warehouse.
32. A computer-readable storage device having stored thereon, computer-executable instructions that, if executed by a computing device, cause the computing device to perform the method of claim 31.
33. In a data collection and processing system including two or more premises servers for collecting data and transmitting the data to a primary data warehouse, a method for providing fault tolerant data warehousing, the method comprising:
suspending transmission of data between a premises server and a primary data warehouse when the primary data warehouse is inoperable to receive data from the premises server;
accessing a database associated with the premises server to obtain an identification of an alternate data warehouse associated with the premises server;
transmitting premises data to the alternate data warehouse;
wherein the alternate data warehouse is selected from the two or more premises servers;
obtaining an indication that the primary data warehouse can receive data;
transmitting data to the primary data warehouse upon obtaining the indication; and;
suspending data transmission to the alternate data warehouse.
34. A computer-readable storage device having stored thereon, computer-executable instructions that, if executed by a computing device, cause the computing device to perform the method of claim 33.
35. A method for providing fault tolerant data warehousing, the method comprising:
obtaining an indication that a primary data warehouse is inoperable to receive data from a first premises server;
identifying an alternate data warehouse to receive the data;
transmitting information identifying the alternate data warehouse to the first premises server, wherein:
if the primary data warehouse is inoperable to receive data, the first premises server attempts to establish contact with and transmit data to the identified alternate data warehouse; and
if the primary data warehouse is subsequently available to receive data, the first premises server transmits data to the primary data warehouse; and suspends data transmission to the alternate data warehouse.
36. A computer-readable storage device having stored thereon, computer-executable instructions that, if executed by a computing device, cause the computing device to perform the method of claim 35.
37. The method of claim 35, wherein identifying an alternate data warehouse comprises obtaining a static file that includes a pre-assigned alternate data warehouse for the first premises server.
38. The method of claim 35, wherein identifying an alternate data warehouse comprises obtaining a dynamically-generated warehouse ticket file that identifies the alternate data warehouse based upon at least one factor.
39. The method of claim 38, wherein the at least one factor includes at least one of:
available memory resources at a plurality of potential alternate data warehouses; or
availability of a corresponding communication network.
40. The method of claim 35, wherein the alternate data warehouse comprises a first alternate data warehouse, the method further comprising:
obtaining an indication that the first premises server is unable to establish contact with and transmit data to the identified first alternate data warehouse;
identifying a second alternate data warehouse to receive the data; and
transmitting information identifying the second alternate data warehouse to the first premises server.
41. The method of claim 35, wherein the primary data warehouse is inoperable to receive data from the first premises server due to a system fault making the primary data warehouse inoperable to receive data from a subset of a plurality of premises servers, the method further comprising:
identifying a corresponding alternate data warehouse to receive data from each of the subset of the plurality of premises servers; and
transmitting information identifying the corresponding alternate data warehouse to each of the subset of the plurality of premises server.
US12/537,963 2002-04-09 2009-08-07 System for providing fault tolerant data warehousing environment by temporary transmitting data to alternate data warehouse during an interval of primary data warehouse failure Active 2025-08-09 USRE43933E1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US12/537,963 USRE43933E1 (en) 2002-04-09 2009-08-07 System for providing fault tolerant data warehousing environment by temporary transmitting data to alternate data warehouse during an interval of primary data warehouse failure

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US37127302P 2002-04-09 2002-04-09
US10/411,504 US7254640B2 (en) 2002-04-09 2003-04-09 System for providing fault tolerant data warehousing environment by temporary transmitting data to alternate data warehouse during an interval of primary data warehouse failure
US12/537,963 USRE43933E1 (en) 2002-04-09 2009-08-07 System for providing fault tolerant data warehousing environment by temporary transmitting data to alternate data warehouse during an interval of primary data warehouse failure

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US10/411,504 Reissue US7254640B2 (en) 2002-04-09 2003-04-09 System for providing fault tolerant data warehousing environment by temporary transmitting data to alternate data warehouse during an interval of primary data warehouse failure

Publications (1)

Publication Number Publication Date
USRE43933E1 true USRE43933E1 (en) 2013-01-15

Family

ID=28678400

Family Applications (2)

Application Number Title Priority Date Filing Date
US10/411,504 Ceased US7254640B2 (en) 2002-04-09 2003-04-09 System for providing fault tolerant data warehousing environment by temporary transmitting data to alternate data warehouse during an interval of primary data warehouse failure
US12/537,963 Active 2025-08-09 USRE43933E1 (en) 2002-04-09 2009-08-07 System for providing fault tolerant data warehousing environment by temporary transmitting data to alternate data warehouse during an interval of primary data warehouse failure

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US10/411,504 Ceased US7254640B2 (en) 2002-04-09 2003-04-09 System for providing fault tolerant data warehousing environment by temporary transmitting data to alternate data warehouse during an interval of primary data warehouse failure

Country Status (1)

Country Link
US (2) US7254640B2 (en)

Families Citing this family (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7254640B2 (en) 2002-04-09 2007-08-07 Vigilos, Inc. System for providing fault tolerant data warehousing environment by temporary transmitting data to alternate data warehouse during an interval of primary data warehouse failure
US7523184B2 (en) * 2002-12-31 2009-04-21 Time Warner Cable, Inc. System and method for synchronizing the configuration of distributed network management applications
US8326990B1 (en) * 2005-07-15 2012-12-04 Symantec Operating Corporation Automated optimal workload balancing during failover in share-nothing database systems
US8775460B2 (en) * 2005-12-08 2014-07-08 International Business Machines Corporation Managing changes to computer system
US20070250524A1 (en) * 2006-04-19 2007-10-25 Jian Le Method and apparatus for workload and model based materialized query table or view recommendation technique
US8930310B2 (en) * 2007-11-27 2015-01-06 The Boeing Company Proxy server for distributing aircraft software parts
US8442751B2 (en) 2007-11-27 2013-05-14 The Boeing Company Onboard electronic distribution system
US8490074B2 (en) * 2007-11-27 2013-07-16 The Boeing Company Aircraft software part library
US20090138873A1 (en) * 2007-11-27 2009-05-28 The Boeing Company Method and Apparatus for Loadable Aircraft Software Parts Distribution
US9208308B2 (en) 2007-11-27 2015-12-08 The Boeing Company Alternate parts signature list file
CN101226527B (en) * 2007-12-28 2011-06-08 中国移动通信集团四川有限公司 Data synchronization method for double-nucleus library
JP2009193502A (en) * 2008-02-18 2009-08-27 Hitachi Ltd Computer system, storage device, and processing alternative method
US7917541B2 (en) * 2008-03-31 2011-03-29 Microsoft Corporation Collecting and aggregating data using distributed resources
US8135838B2 (en) * 2008-04-08 2012-03-13 Geminare Incorporated System and method for providing data and application continuity in a computer system
US8275907B2 (en) 2008-06-26 2012-09-25 Microsoft Corporation Adding individual database failover/switchover to an existing storage component with limited impact
US9110968B2 (en) 2010-04-14 2015-08-18 At&T Intellectual Property I, L.P. Removal of invisible data packages in data warehouses
US10102687B1 (en) 2010-08-17 2018-10-16 The Boeing Company Information management system for ground vehicles
US8984328B2 (en) 2011-03-11 2015-03-17 Microsoft Technology Licensing, Llc Fault tolerance in a parallel database system
US9237022B2 (en) 2013-05-07 2016-01-12 The Boeing Company Use of multiple digital signatures and quorum rules to verify aircraft information
US9160543B2 (en) 2013-05-07 2015-10-13 The Boeing Company Verification of aircraft information in response to compromised digital certificate

Citations (48)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4216375A (en) 1979-03-12 1980-08-05 A-T-O Inc. Self-contained programmable terminal for security systems
US4218690A (en) 1978-02-01 1980-08-19 A-T-O, Inc. Self-contained programmable terminal for security systems
US4581634A (en) 1982-11-18 1986-04-08 Williams Jarvis L Security apparatus for controlling access to a predetermined area
US4714995A (en) 1985-09-13 1987-12-22 Trw Inc. Computer integration system
US4721954A (en) 1985-12-18 1988-01-26 Marlee Electronics Corporation Keypad security system
US4816658A (en) 1983-01-10 1989-03-28 Casi-Rusco, Inc. Card reader for security system
US4837568A (en) 1987-07-08 1989-06-06 Snaper Alvin A Remote access personnel identification and tracking system
US4839640A (en) 1984-09-24 1989-06-13 Adt Inc. Access control system having centralized/distributed control
US4962473A (en) 1988-12-09 1990-10-09 Itt Corporation Emergency action systems including console and security monitoring apparatus
US4998279A (en) 1984-11-30 1991-03-05 Weiss Kenneth P Method and apparatus for personal verification utilizing nonpredictable codes and biocharacteristics
US5097505A (en) 1989-10-31 1992-03-17 Securities Dynamics Technologies, Inc. Method and apparatus for secure identification and verification
US5210873A (en) 1990-05-25 1993-05-11 Csi Control Systems International, Inc. Real-time computer system with multitasking supervisor for building access control or the like
US5367624A (en) 1993-06-11 1994-11-22 Consilium, Inc. Interface for controlling transactions in a manufacturing execution system
US5475375A (en) 1985-10-16 1995-12-12 Supra Products, Inc. Electronic access control systems
US5475378A (en) 1993-06-22 1995-12-12 Canada Post Corporation Electronic access control mail box system
US5544062A (en) 1995-01-31 1996-08-06 Johnston, Jr.; Louie E. Automated system for manufacturing of customized military uniform insignia badges
US5600368A (en) 1994-11-09 1997-02-04 Microsoft Corporation Interactive television system and method for viewer control of multiple camera viewpoints in broadcast programming
WO1997007486A1 (en) 1995-08-21 1997-02-27 Prism Video, Inc. Event monitoring
US5614890A (en) 1993-12-27 1997-03-25 Motorola, Inc. Personal identification system
US5629981A (en) 1994-07-29 1997-05-13 Texas Instruments Incorporated Information management and security system
US5654696A (en) 1985-10-16 1997-08-05 Supra Products, Inc. Method for transferring auxillary data using components of a secure entry system
US5678039A (en) 1994-09-30 1997-10-14 Borland International, Inc. System and methods for translating software into localized versions
US5680328A (en) 1995-05-22 1997-10-21 Eaton Corporation Computer assisted driver vehicle inspection reporting system
US5682142A (en) 1994-07-29 1997-10-28 Id Systems Inc. Electronic control system/network
EP0804031A2 (en) 1996-04-23 1997-10-29 Canon Kabushiki Kaisha Image display apparatus, camera control apparatus and method
US5729471A (en) 1995-03-31 1998-03-17 The Regents Of The University Of California Machine dynamic selection of one video camera/image of a scene from multiple video cameras/images of the scene in accordance with a particular perspective on the scene, an object in the scene, or an event in the scene
US5742286A (en) 1995-11-20 1998-04-21 International Business Machines Corporation Graphical user interface system and method for multiple simultaneous targets
US5768119A (en) 1996-04-12 1998-06-16 Fisher-Rosemount Systems, Inc. Process control system including alarm priority adjustment
US5870733A (en) 1996-06-14 1999-02-09 Electronic Data Systems Corporation Automated system and method for providing access data concerning an item of business property
US5903455A (en) 1996-02-06 1999-05-11 Fisher-Rosemount Systems, Inc. Interface controls for use in a field device management system
US5923264A (en) 1995-12-22 1999-07-13 Harrow Products, Inc. Multiple access electronic lock system
US5960174A (en) 1996-12-20 1999-09-28 Square D Company Arbitration method for a communication network
US6064723A (en) 1994-09-16 2000-05-16 Octel Communications Corporation Network-based multimedia communications and directory system and method of operation
WO2001028251A1 (en) 1999-10-12 2001-04-19 Vigilos, Inc. System and method for controlling the storage and remote retrieval of surveillance video images
US6233588B1 (en) 1998-12-02 2001-05-15 Lenel Systems International, Inc. System for security access control in multiple regions
US20010044879A1 (en) * 2000-02-18 2001-11-22 Moulton Gregory Hagan System and method for distributed management of data storage
US20020019945A1 (en) 2000-04-28 2002-02-14 Internet Security System, Inc. System and method for managing security events on a network
US20020029263A1 (en) 2000-07-07 2002-03-07 International Business Machines Corporation Network system, device management system, device management method, data processing method, storage medium, and internet service provision method
US6356949B1 (en) 1999-01-29 2002-03-12 Intermec Ip Corp. Automatic data collection device that receives data output instruction from data consumer
US20020044879A1 (en) 2000-08-30 2002-04-18 Kabushiki Kaisha Kobe Seiko Sho (Kobe Steel, Ltd.) Machine structure steel superior in chip disposability and mechanical properties
US20020059423A1 (en) * 2000-07-15 2002-05-16 Ibm Method for availability monitoring via a shared database
US20020072934A1 (en) * 1996-07-08 2002-06-13 Ross James E. Medical records, documentation, tracking and order entry system
US20020116389A1 (en) 1999-01-15 2002-08-22 Metaedge Coporation System and method for providing a data warehouse in accordance with a virtual schema
US20020138427A1 (en) * 2001-03-20 2002-09-26 Trivedi Prakash A. Systems and methods for communicating from an integration platform to a billing unit
US6587857B1 (en) 1998-06-30 2003-07-01 Citicorp Development Center, Inc. System and method for warehousing and retrieving data
US20030191773A1 (en) 2002-04-09 2003-10-09 Vigilos, Inc. System and method for providing a fault-tolerant data warehouse environment
US20030208572A1 (en) * 2001-08-31 2003-11-06 Shah Rajesh R. Mechanism for reporting topology changes to clients in a cluster
US7003560B1 (en) * 1999-11-03 2006-02-21 Accenture Llp Data warehouse computing system

Patent Citations (49)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4218690A (en) 1978-02-01 1980-08-19 A-T-O, Inc. Self-contained programmable terminal for security systems
USRE35336E (en) 1978-02-01 1996-09-24 Casi-Rusco, Inc. Self-contained programmable terminal for security systems
US4216375A (en) 1979-03-12 1980-08-05 A-T-O Inc. Self-contained programmable terminal for security systems
US4581634A (en) 1982-11-18 1986-04-08 Williams Jarvis L Security apparatus for controlling access to a predetermined area
US4816658A (en) 1983-01-10 1989-03-28 Casi-Rusco, Inc. Card reader for security system
US4839640A (en) 1984-09-24 1989-06-13 Adt Inc. Access control system having centralized/distributed control
US4998279A (en) 1984-11-30 1991-03-05 Weiss Kenneth P Method and apparatus for personal verification utilizing nonpredictable codes and biocharacteristics
US4714995A (en) 1985-09-13 1987-12-22 Trw Inc. Computer integration system
US5475375A (en) 1985-10-16 1995-12-12 Supra Products, Inc. Electronic access control systems
US5654696A (en) 1985-10-16 1997-08-05 Supra Products, Inc. Method for transferring auxillary data using components of a secure entry system
US4721954A (en) 1985-12-18 1988-01-26 Marlee Electronics Corporation Keypad security system
US4837568A (en) 1987-07-08 1989-06-06 Snaper Alvin A Remote access personnel identification and tracking system
US4962473A (en) 1988-12-09 1990-10-09 Itt Corporation Emergency action systems including console and security monitoring apparatus
US5097505A (en) 1989-10-31 1992-03-17 Securities Dynamics Technologies, Inc. Method and apparatus for secure identification and verification
US5210873A (en) 1990-05-25 1993-05-11 Csi Control Systems International, Inc. Real-time computer system with multitasking supervisor for building access control or the like
US5367624A (en) 1993-06-11 1994-11-22 Consilium, Inc. Interface for controlling transactions in a manufacturing execution system
US5475378A (en) 1993-06-22 1995-12-12 Canada Post Corporation Electronic access control mail box system
US5614890A (en) 1993-12-27 1997-03-25 Motorola, Inc. Personal identification system
US5682142A (en) 1994-07-29 1997-10-28 Id Systems Inc. Electronic control system/network
US5629981A (en) 1994-07-29 1997-05-13 Texas Instruments Incorporated Information management and security system
US6064723A (en) 1994-09-16 2000-05-16 Octel Communications Corporation Network-based multimedia communications and directory system and method of operation
US5678039A (en) 1994-09-30 1997-10-14 Borland International, Inc. System and methods for translating software into localized versions
US5600368A (en) 1994-11-09 1997-02-04 Microsoft Corporation Interactive television system and method for viewer control of multiple camera viewpoints in broadcast programming
US5544062A (en) 1995-01-31 1996-08-06 Johnston, Jr.; Louie E. Automated system for manufacturing of customized military uniform insignia badges
US5729471A (en) 1995-03-31 1998-03-17 The Regents Of The University Of California Machine dynamic selection of one video camera/image of a scene from multiple video cameras/images of the scene in accordance with a particular perspective on the scene, an object in the scene, or an event in the scene
US5680328A (en) 1995-05-22 1997-10-21 Eaton Corporation Computer assisted driver vehicle inspection reporting system
WO1997007486A1 (en) 1995-08-21 1997-02-27 Prism Video, Inc. Event monitoring
US5742286A (en) 1995-11-20 1998-04-21 International Business Machines Corporation Graphical user interface system and method for multiple simultaneous targets
US5923264A (en) 1995-12-22 1999-07-13 Harrow Products, Inc. Multiple access electronic lock system
US5903455A (en) 1996-02-06 1999-05-11 Fisher-Rosemount Systems, Inc. Interface controls for use in a field device management system
US5768119A (en) 1996-04-12 1998-06-16 Fisher-Rosemount Systems, Inc. Process control system including alarm priority adjustment
EP0804031A2 (en) 1996-04-23 1997-10-29 Canon Kabushiki Kaisha Image display apparatus, camera control apparatus and method
US5870733A (en) 1996-06-14 1999-02-09 Electronic Data Systems Corporation Automated system and method for providing access data concerning an item of business property
US20020072934A1 (en) * 1996-07-08 2002-06-13 Ross James E. Medical records, documentation, tracking and order entry system
US5960174A (en) 1996-12-20 1999-09-28 Square D Company Arbitration method for a communication network
US6587857B1 (en) 1998-06-30 2003-07-01 Citicorp Development Center, Inc. System and method for warehousing and retrieving data
US6233588B1 (en) 1998-12-02 2001-05-15 Lenel Systems International, Inc. System for security access control in multiple regions
US20020116389A1 (en) 1999-01-15 2002-08-22 Metaedge Coporation System and method for providing a data warehouse in accordance with a virtual schema
US6356949B1 (en) 1999-01-29 2002-03-12 Intermec Ip Corp. Automatic data collection device that receives data output instruction from data consumer
WO2001028251A1 (en) 1999-10-12 2001-04-19 Vigilos, Inc. System and method for controlling the storage and remote retrieval of surveillance video images
US7003560B1 (en) * 1999-11-03 2006-02-21 Accenture Llp Data warehouse computing system
US20010044879A1 (en) * 2000-02-18 2001-11-22 Moulton Gregory Hagan System and method for distributed management of data storage
US20020019945A1 (en) 2000-04-28 2002-02-14 Internet Security System, Inc. System and method for managing security events on a network
US20020029263A1 (en) 2000-07-07 2002-03-07 International Business Machines Corporation Network system, device management system, device management method, data processing method, storage medium, and internet service provision method
US20020059423A1 (en) * 2000-07-15 2002-05-16 Ibm Method for availability monitoring via a shared database
US20020044879A1 (en) 2000-08-30 2002-04-18 Kabushiki Kaisha Kobe Seiko Sho (Kobe Steel, Ltd.) Machine structure steel superior in chip disposability and mechanical properties
US20020138427A1 (en) * 2001-03-20 2002-09-26 Trivedi Prakash A. Systems and methods for communicating from an integration platform to a billing unit
US20030208572A1 (en) * 2001-08-31 2003-11-06 Shah Rajesh R. Mechanism for reporting topology changes to clients in a cluster
US20030191773A1 (en) 2002-04-09 2003-10-09 Vigilos, Inc. System and method for providing a fault-tolerant data warehouse environment

Non-Patent Citations (20)

* Cited by examiner, † Cited by third party
Title
Axis Communications, publication entitled "Axis 200+ Web Camera."
Axis Communications, publication entitled "Axis 240 Camera Server."
Axis Communications, ww.axis.se/products/camera-servers/cam-app-sol.htm, "Network Cameras Applications and Solutions," printed Sep. 28, 1999.
Axis Communications, ww.axis.se/products/camera—servers/cam—app—sol.htm, "Network Cameras Applications and Solutions," printed Sep. 28, 1999.
Axis Communications, www.axis.se/products/cam-240/, "30 Frames/Second," printed Sep. 28, 1999.
Axis Communications, www.axis.se/products/cam—240/, "30 Frames/Second," printed Sep. 28, 1999.
Axis Communications, www.axis.se/products/camera-servers/cam-app-sol.htm, "Network Cameras applications and Solutions," printed Sep. 28, 1999.
Axis Communications, www.axis.se/products/camera—servers/cam—app—sol.htm, "Network Cameras applications and Solutions," printed Sep. 28, 1999.
Axis Communications, www.axis.se/products/camera-servers/cam-fb.html, "Features and Benefits," printed Sep. 28, 1999.
Axis Communications, www.axis.se/products/camera—servers/cam—fb.html, "Features and Benefits," printed Sep. 28, 1999.
Axis Communications, www.axis.se/products/camera-servers/cam-fb.html, "Features and Benefits," printed Sep. 8, 1999.
Axis Communications, www.axis.se/products/camera—servers/cam—fb.html, "Features and Benefits," printed Sep. 8, 1999.
EyeCast Announces Eye Capture Services, Press Release dated Jul. 8, 1998.
EyeCast.com Adds 360-degree Continuous Pan Rotation Cameras to It's[sic] Eye View Service, Press Release dated Mar. 15, 1999.
EyeCast.com Announces Eye View Control, Press Release dated Oct. 12, 1998.
EyeCast.com Introduces School Cast Services for School Safety Officials and Law Enforcement Agencies, Press Release dated Apr. 28, 1999.
EyeCast.com Introduces SchoolCast services for School Safety Officials and Law Enforcement Agencies, Press Release dated Apr. 28, 1999.
EyeCast.com, "EyeCast Secures Deals . . . ," Washington Business Journal, Aug. 13-19, 1999, Tech Section, p. 16.
EyeCast.com, Inc., Providing Live Interactive Video for Surveillance & Monitoring Over the Internet.
Screen Printing from www.remotecams.com, "Take a Step Into the Future . . . " printed Sep. 17, 1999.

Also Published As

Publication number Publication date
US20030191773A1 (en) 2003-10-09
US7254640B2 (en) 2007-08-07

Similar Documents

Publication Publication Date Title
USRE43933E1 (en) System for providing fault tolerant data warehousing environment by temporary transmitting data to alternate data warehouse during an interval of primary data warehouse failure
US8239347B2 (en) System and method for customizing the storage and management of device data in a networked environment
US10397224B2 (en) Network personal digital video recorder system (NPDVR)
DK1620778T3 (en) SYSTEM FOR REGISTRATION, TRANSMISSION AND Persisting OF BACKUP AND RECOVERY METADATA
CN1095264C (en) High-availability computer server system
US7818607B2 (en) Arrangement for recovery of data by network nodes based on retrieval of encoded data distributed among the network nodes
US7047377B2 (en) System and method for conducting an auction-based ranking of search results on a computer network
US7587467B2 (en) Managed peer-to-peer applications, systems and methods for distributed data access and storage
US20070198789A1 (en) System to capture, transmit and persist backup and recovery meta data
US8140887B2 (en) System and method for providing data services via a network
WO2002052381A2 (en) System and method for intelligently distributing content over a communications network
US20040133629A1 (en) Methods, systems and devices for automated web publishing and distribution
US20070076228A1 (en) System and method for providing data services via a network
WO1999005631A1 (en) Workflow systems and methods
US7555558B1 (en) Method and system for fault-tolerant transfer of files across a network
WO2011133299A2 (en) Automated recovery and escalation in complex distributed applications
WO2001035272A2 (en) Apparatus and method for selective routing of users to experts over a network of computers
US7337234B2 (en) Retry technique for multi-tier network communication systems
JP2012079350A (en) Content collection
US7281027B2 (en) Distributed processing system and network monitoring system
US20020078182A1 (en) Failover service method and system
WO2002088909A9 (en) Methods, systems and devices for automated web publishing and distribution
Wang et al. The SIMBA user alert service architecture for dependable alert delivery
Siddique et al. AGENT TRACKER: CENTERALIZED AGENT SERVER FOR MANAGING AND SERVICING MOBILE AGENT

Legal Events

Date Code Title Description
CC Certificate of correction
FPAY Fee payment

Year of fee payment: 8

AS Assignment

Owner name: CHEMTRON RESEARCH LLC, DELAWARE

Free format text: MERGER;ASSIGNOR:HATOSHI INVESTMENTS JP, LLC;REEL/FRAME:037275/0316

Effective date: 20150826

AS Assignment

Owner name: INTELLECTUAL VENTURES FUND 83 LLC, NEVADA

Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE ASSIGNEE NAME PREVIOUSLY RECORDED AT REEL: 037275 FRAME: 0316. ASSIGNOR(S) HEREBY CONFIRMS THE MERGER;ASSIGNOR:HATOSHI INVESTMENTS JP, LLC;REEL/FRAME:038612/0375

Effective date: 20150826

AS Assignment

Owner name: CHEMTRON RESEARCH LLC, DELAWARE

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:INTELLECTUAL VENTURES FUND 83 LLC;REEL/FRAME:041469/0177

Effective date: 20161230

AS Assignment

Owner name: HATOSHI INVESTMENTS JP, LLC, DELAWARE

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:VIGILOS, INC;REEL/FRAME:047799/0070

Effective date: 20080530

AS Assignment

Owner name: INTELLECTUAL VENTURES ASSETS 122 LLC, DELAWARE

Free format text: NUNC PRO TUNC ASSIGNMENT;ASSIGNOR:CHEMTRON RESEARCH LLC;REEL/FRAME:047923/0215

Effective date: 20190107

AS Assignment

Owner name: VIGILOS, INC., WASHINGTON

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:ALEXANDER, BRUCE;REEL/FRAME:048137/0431

Effective date: 20030220

Owner name: ROVI CORPORATION, CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:INTELLECTUAL VENTURES ASSETS 127 LLC;INTELLECTUAL VENTURES ASSETS 122 LLC;REEL/FRAME:048143/0615

Effective date: 20181227

Owner name: ROVI TECHNOLOGIES CORPORATION, CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:ROVI CORPORATION;REEL/FRAME:048143/0607

Effective date: 20190115

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 12TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1553); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 12

AS Assignment

Owner name: HPS INVESTMENT PARTNERS, LLC, AS COLLATERAL AGENT,

Free format text: SECURITY INTEREST;ASSIGNORS:ROVI SOLUTIONS CORPORATION;ROVI TECHNOLOGIES CORPORATION;ROVI GUIDES, INC.;AND OTHERS;REEL/FRAME:051143/0468

Effective date: 20191122

Owner name: HPS INVESTMENT PARTNERS, LLC, AS COLLATERAL AGENT, NEW YORK

Free format text: SECURITY INTEREST;ASSIGNORS:ROVI SOLUTIONS CORPORATION;ROVI TECHNOLOGIES CORPORATION;ROVI GUIDES, INC.;AND OTHERS;REEL/FRAME:051143/0468

Effective date: 20191122

AS Assignment

Owner name: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL

Free format text: PATENT SECURITY AGREEMENT;ASSIGNORS:ROVI SOLUTIONS CORPORATION;ROVI TECHNOLOGIES CORPORATION;ROVI GUIDES, INC.;AND OTHERS;REEL/FRAME:051110/0006

Effective date: 20191122

Owner name: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT, MARYLAND

Free format text: PATENT SECURITY AGREEMENT;ASSIGNORS:ROVI SOLUTIONS CORPORATION;ROVI TECHNOLOGIES CORPORATION;ROVI GUIDES, INC.;AND OTHERS;REEL/FRAME:051110/0006

Effective date: 20191122

AS Assignment

Owner name: BANK OF AMERICA, N.A., NORTH CAROLINA

Free format text: SECURITY INTEREST;ASSIGNORS:ROVI SOLUTIONS CORPORATION;ROVI TECHNOLOGIES CORPORATION;ROVI GUIDES, INC.;AND OTHERS;REEL/FRAME:053468/0001

Effective date: 20200601

AS Assignment

Owner name: TIVO SOLUTIONS, INC., CALIFORNIA

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:HPS INVESTMENT PARTNERS, LLC;REEL/FRAME:053458/0749

Effective date: 20200601

Owner name: ROVI SOLUTIONS CORPORATION, CALIFORNIA

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:HPS INVESTMENT PARTNERS, LLC;REEL/FRAME:053458/0749

Effective date: 20200601

Owner name: ROVI TECHNOLOGIES CORPORATION, CALIFORNIA

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:HPS INVESTMENT PARTNERS, LLC;REEL/FRAME:053458/0749

Effective date: 20200601

Owner name: ROVI GUIDES, INC., CALIFORNIA

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:HPS INVESTMENT PARTNERS, LLC;REEL/FRAME:053458/0749

Effective date: 20200601

Owner name: VEVEO, INC., CALIFORNIA

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:HPS INVESTMENT PARTNERS, LLC;REEL/FRAME:053458/0749

Effective date: 20200601

Owner name: ROVI TECHNOLOGIES CORPORATION, CALIFORNIA

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:MORGAN STANLEY SENIOR FUNDING, INC.;REEL/FRAME:053481/0790

Effective date: 20200601

Owner name: VEVEO, INC., CALIFORNIA

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:MORGAN STANLEY SENIOR FUNDING, INC.;REEL/FRAME:053481/0790

Effective date: 20200601

Owner name: ROVI SOLUTIONS CORPORATION, CALIFORNIA

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:MORGAN STANLEY SENIOR FUNDING, INC.;REEL/FRAME:053481/0790

Effective date: 20200601

Owner name: TIVO SOLUTIONS, INC., CALIFORNIA

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:MORGAN STANLEY SENIOR FUNDING, INC.;REEL/FRAME:053481/0790

Effective date: 20200601

Owner name: ROVI GUIDES, INC., CALIFORNIA

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:MORGAN STANLEY SENIOR FUNDING, INC.;REEL/FRAME:053481/0790

Effective date: 20200601