Classifications

• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
  • G06Q10/00—Administration; Management
  • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F11/00—Error detection; Error correction; Monitoring
  • G06F11/30—Monitoring
  • G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
  • G06F11/3006—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F11/00—Error detection; Error correction; Monitoring
  • G06F11/30—Monitoring
  • G06F11/3065—Monitoring arrangements determined by the means or processing involved in reporting the monitored data
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F11/00—Error detection; Error correction; Monitoring
  • G06F11/30—Monitoring
  • G06F11/3089—Monitoring arrangements determined by the means or processing involved in sensing the monitored data, e.g. interfaces, connectors, sensors, probes, agents
• • 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/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
  • G06F2201/805—Real-time
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
  • G06F2201/86—Event-based monitoring

Definitions

• the present invention relates generally to enterprise level data collection.
• the present invention seeks to provide an efficient system and methodology for enterprise level data collection.
• an enterprise data collection system including at least one database for receiving over a network and storing data collected from data resources at a plurality of physical sites located at disparate locations, a plurality of remotely synchronizable probes (RSPs) located at the plurality of physical sites, the remotely synchronizable probes (RSPs) performing at least one of the following data collection functions: real time event collection, file system crawling for data structure and permissions, data content analysis, data indexing, data tagging and event triggered alerts, and at least one RSP manager located remotely from at least one of the plurality of remotely synchronizable probes and being operative to govern the operation of and orchestrate data collection and transmission by the plurality of remotely synchronizable probes (RSPs).
• RSPs remotely synchronizable probes
• the at least one RSP coordinates the timing of at least some data collection functions carried out on multiple ones of the data resources, which functions may occur simultaneously.
• the at least one RSP manager coordinates the timing of data collection by multiple ones of the plurality of RSPs on the basis of at least one of the following criteria: network latency, network bandwidth, time of day/day of week at the RSP, size of data resource, type of data resource, prioritization of certain data resources over other data resources and user defined prioritization of data resources.
• the prioritization of certain data resources over other data resources is based at least partially on characteristics of at least one of: real time event collection, file system crawling for data structure and permissions, data content analysis, data indexing, data tagging and event triggered alerts.
• the at least one RSP manager coordinates the timing of data transmission from multiple ones of the plurality of RSPs, which transmission may occur simultaneously.
• the at least one RSP manager coordinates the timing of data transmission from multiple ones of the plurality of RSPs on the basis of at least one of the following criteria: network latency, network bandwidth, time of day/day of week at the RSP, time of day/day of week at the at least one database, amount of data to be transmitted, prioritization of certain RSPs over other RSPs and user defined prioritization of data resources.
• the prioritization of certain RSPs over other RSPs is based at least partially on characteristics of at least one of: real time event collection, file system crawling for data structure and permissions, data content analysis, data indexing, data tagging and event triggered alerts.
• an enterprise data collection method including transmitting and receiving over a network and storing data collected from data resources at a plurality of physical sites located at disparate locations, performing at the plurality of physical sites at least one of the following data collection functions: real time event collection, file system crawling for data structure and permissions, data content analysis, data indexing, data tagging and event triggered alerts, and governing and orchestrating data collection at the plurality of physical sites and transmission and receiving of the data over the network.
• the method also includes coordinating the timing of at least some data collection functions carried out on multiple ones of the data resources, which functions may occur simultaneously.
• the coordinating includes coordinating the timing of data collection from data resources at the plurality of physical sites on the basis of at least one of the following criteria: network latency, network bandwidth, time of day/day of week at the physical site, size of data resource, type of data resource, prioritization of certain data resources over other data resources and user defined prioritization of data resources.
• the prioritization of certain data resources over other data resources is based at least partially on characteristics of at least one of real time event collection, file system crawling for data structure and permissions, data content analysis, data indexing, data tagging and event triggered alerts.
• the method also includes coordinating the timing of data transmission from multiple ones of the plurality of physical sites which transmission may occur simultaneously.
• the coordinating the timing of data transmission from multiple ones of the plurality of physical sites is on the basis of at least one of the following criteria: network latency, network bandwidth, time of day/day of week at the physical site, time of day/day of week at the at least one database, amount of data to be transmitted, prioritization of certain physical sites over other physical sites and user defined prioritization of data resources.
• the prioritization of certain physical sites over other physical sites is based at least partially on characteristics of at least one of real time event collection, file system crawling for data structure and permissions, data content analysis, data indexing, data tagging and event triggered alerts.
• Fig. 1 is a simplified illustration of a system and methodology for enterprise level data collection at a plurality of physical sites located at disparate locations including real time event collection, file system crawling for data structure and permissions, data content analysis, data indexing, data tagging and event triggered alerts;
• Fig. 2 is a simplified illustration of part of the system and methodology illustrated in Fig. 1, showing coordination of the timing of at least some of the data collection from multiple data resources at one of the plurality of physical sites;
• Fig. 3A is a simplified illustration of part of the system and methodology illustrated in Fig. 1 and Fig. 2, showing coordination of the timing of data collection by multiple ones of said plurality of RSPs on the basis of time of day/day of week at the RSP;
• Fig. 3B is a simplified illustration of part of the system and methodology illustrated in Fig. 1 and Fig. 2, showing coordination of the timing of data collection by multiple ones of said plurality of RSPs showing prioritization of certain data resources over other data resources based at least partially on characteristics of real time event collection and of file system;
• Fig. 4A is a simplified illustration of part of the system and methodology illustrated in Fig. 1 and Fig. 2, showing coordination of the timing of data collection by multiple ones of said plurality of RSPs on the basis of the amount of data to be collected from the data resources monitored thereby and on the basis of type of the data resources monitored thereby;
• Fig. 4B is a simplified illustration of part of the system and methodology illustrated in Fig. 1 and Fig. 2, showing coordination of the timing of data collection by multiple ones of said plurality of RSPs on the basis of type of data resource and on the basis of user defined prioritization of RSPs located in various physical sites
• Fig. 4C is a simplified illustration of part of the system and methodology illustrated in Fig. 1 and Fig. 2, showing coordination of the timing of data collection by multiple ones of the plurality of RSPs on the basis of size of data resource and on the basis of type of data resource and showing prioritization of certain data resources over other data resources based at least partially on characteristics of real time event collection and of file system crawling for data structure and permissions;
• Fig. 5A is a simplified illustration of part of the system and methodology illustrated in Fig. 1 and Fig. 2, showing coordination of the timing of data transmission by multiple ones of said plurality of RSPs on the basis of network latency;
• Fig. 5B is a simplified illustration of part of the system and methodology illustrated in Fig. 1 and Fig. 2, showing coordination of the timing of data transmission by multiple ones of said plurality of RSPs on the basis of network bandwidth;
• Fig. 5C is a simplified illustration of part of the system and methodology illustrated in Fig. 1 and Fig. 2, showing coordination of the timing of data transmission by multiple ones of said plurality of RSPs on the basis of the amount of collected data to be transmitted;
• Fig. 5D is a simplified illustration of part of the system and methodology illustrated in Fig. 1 and Fig. 2, showing coordination of the timing of data transmission by multiple ones of said plurality of RSPs on the basis of type of data resource;
• Fig. 5E is a simplified illustration of part of the system and methodology illustrated in Fig. 1 and Fig. 2, showing coordination of the timing of data transmission by multiple ones of said plurality of RSPs on the basis of user defined prioritization of RSPs located in various physical sites;
• Fig. 5F is a simplified illustration of part of the system and methodology illustrated in Fig. 1 and Fig. 2, showing coordination of the timing of data transmission by multiple ones of said plurality of RSPs on the basis of time of day/day of week at the RSP;
• Fig. 5G is a simplified illustration of part of the system and methodology illustrated in Fig. 1 and Fig. 2, showing coordination of the timing of data transmission by multiple ones of said plurality of RSPs on the basis of user defined prioritization of data resources
• Fig. 5H is a simplified illustration of part of the system and methodology illustrated in Fig. 1 and Fig. 2, showing coordination of the timing of data transmission by multiple ones of said plurality of RSPs on the basis of time of day/day of week at the RSP and on the on the basis of the amount of collected data to be transmitted;
• Fig. 6A is a simplified illustration of part of the system and methodology illustrated in Fig. 1 and Fig. 2, showing coordination of the timing of data collection by multiple ones of the plurality of RSPs on the basis of size of data resource and on the basis of type of data resource and showing prioritization of certain data resources over other data resources based at least partially on characteristics of real time event collection and of file system crawling for data structure and permissions and showing coordination of the timing of at least some of the data transmission from ones of the plurality of RSPs on the basis of time of day/day of week at the RSP;
• Fig. 6B is a simplified illustration of part of the system and methodology illustrated in Fig. 1 and Fig. 2, showing coordination of the timing of data collection by multiple ones of the plurality of RSPs on the basis of size of data resource and on the basis of type of data resource and showing prioritization of certain data resources over other data resources based at least partially on characteristics of real time event collection and of file system crawling for data structure and permissions and based on prioritization of certain RSPs over other RSPs; and
• Fig. 7 is a simplified illustration of part of the system and methodology illustrated in Fig. 1 and Fig. 2, showing coordination of the timing of data collection by multiple ones of the plurality of RSPs on the basis of size of data resource and on the basis of type of data resource and showing prioritization of certain data resources over other data resources based at least partially on characteristics of real time event collection and of file system crawling for data structure and permissions and based on prioritization of certain RSPs over other RSPs and showing coordination of the timing of at least some of the data transmission from ones of the plurality of RSPs on the basis of time of day/day of week at the RSP.
• DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS
• FIG. 1 is a simplified illustration of a system and methodology for enterprise level data collection at a plurality of physical sites located at disparate locations including real time event collection, file system crawling for data structure and permissions, data content analysis, data indexing, data tagging and event triggered alerts.
• a system for enterprise level data collection at a plurality of physical sites located at disparate locations including real time event collection, file system crawling for data structure and permissions, data content analysis, data indexing, data tagging and event triggered alerts.
• the system of Fig. 1 preferably includes at least one database for receiving over a network and storing data collected from data resources at a plurality of physical sites located at disparate locations.
• the network may be any suitable network such a conventional enterprise wide network including disparately located database systems, servers, routers, computers and other network devices.
• the data resources may be any suitable data resources such as file systems, databases, NAS devices, WINDOWS® UNIX® file servers, MICROSOFT® SHAREPOINT® servers and Exchange servers, ERP systems and CRM systems.
• data resources 110, 112 and 114 are shown located in London
• data resources 120, 122 and 124 are shown located in Paris
• data resources 130, 132 and 134 are shown located in Rome.
• Data resources 140, 142 and 144 are shown located in Seattle and data resources 150, 152 and 154 are shown located in Beijing.
• Data resources 160, 162 and 164 are shown located in Delhi.
• a plurality of remotely synchronizable probes are located at the plurality of physical sites.
• RSPs 171, 172 and 173 are located in London, Paris and Rome respectively
• RSPs 174 and 175 are located in Seattle and Beijing respectively
• RSP 176 is located in Delhi.
• remotely synchronizable probes (RSPs) 171 - 176 each perform at least one of the following data collection functions:
• At least one RSP manager located remotely from at least one of the plurality of remotely synchronizable probes, is operative to govern the operation of and orchestrate data collection and transmission by the plurality of remotely synchronizable probes (RSPs).
• RSPs remotely synchronizable probes
• a single RSP manager 180 typically a server, is located at an RSP Manager Site in New York, which also houses database 100.
• the RSP manager 180 governs the operation of and orchestrates data collection and transmission by remotely synchronizable probes (RSPs) 171 - 176, which are located in disparate locations geographically distant therefrom.
• RSP manager 180 sends out various types of instructions to RSPs 171 - 176.
• RSP manager 180 sends a Start Event Collection instruction to RSP 171 in London, a Start Data Content Analysis instruction to RSP 172 in Paris and a Start Data Tagging instruction to RSP 173 in Rome.
• the RSP manager 180 typically also sends a Start File System Crawling instruction to RSP 174 in Seattle, receives an Alert from RSP 175 in Beijing and sends a Start Data Indexing instruction to RSP 176 in Delhi.
• FIG. 2 is a simplified illustration of part of the system and methodology illustrated in Fig. 1, showing coordination of the timing of at least some of the data collection from multiple data resources at one of the plurality of physical sites.
• RSP 173 located in Rome coordinates the timing of at least some data collection functions carried out by multiple ones of data resources monitored thereby, which functions may occur simultaneously.
• RSP 173 instructs file servers 130, 132 and 134 monitored thereby to perform various data collection functions at specific times.
• RSP 173 instructs file server 130 to crawl a file system located thereon.
• RSP 173 also instructs file server 132 to analyze the data content thereof.
• RSP 173 instructs file server 134 to index the data stored thereon.
• Fig. 3A is a simplified illustration of part of the system and methodology illustrated in Fig. 1 and Fig. 2, showing coordination of the timing of data collection by multiple ones of said plurality of RSPs on the basis of time of day/day of week at the RSP.
• a management rule is implemented by RSP Manager 180 whereby RSPs are instructed to collect data from their respective data resources at times when those data resources have low utilization rates, such as during the local nighttime hours thereat.
• Fig. 3A Implementation of this rule in the context of an embodiment of the present invention is shown in Fig. 3A as follows: At 12:00 midnight local London time, RSP Manager 180 instructs RSP 171 located in London to collect data from servers 110, 112 and 114 monitored thereby. Thereafter, at 2:00 AM local Paris time RSP Manager 180 instructs RSP 172 located in Paris to collect data from servers 120, 122 and 124 monitored thereby. Simultaneously, at 2:00 AM local Rome time RSP Manager 180 instructs RSP 130 located in Rome to collect data from servers 130, 132 and 134 monitored thereby.
• RSP Manager 180 instructs RSP 175 located in Beijing to collect data from servers 150, 152 and 154 monitored thereby.
• RSP Manager 180 instructs RSP 160 located in Delhi to collect data from servers 160, 162 and 164 monitored thereby.
• RSP Manager 180 instructs RSP 174 located in Seattle to collect data from servers 140, 142 and 144 monitored thereby.
• Fig. 3B is a simplified illustration of part of the system and methodology illustrated in Fig. 1 and Fig. 2, showing coordination of the timing of data collection by multiple ones of said plurality of RSPs showing prioritization of certain data resources over other data resources based at least partially on characteristics of real time event collection and of file system.
• a management rule is implemented by RSP Manager 180 whereby priority is given to data collection from data resources with respect to which access events have occurred.
• RSP Manager 180 becomes aware of access events relating to various data resources, as by periodic querying the various RSPs. Immediately upon becoming aware of such an access event relating to server 160 monitored by RSP 176 located in Delhi, RSP manager 180 initially instructs RSP 176 to collect data from server 160. Typically thereafter, the RSP Manager 180, responsive to an earlier access event relating to server 130 monitored by RSP 173, located in Rome, instructs RSP 173 to collect data from server 130. Typically thereafter, the RSP Manager 180, responsive to an even earlier access event relating to server 112 monitored by RSP 171, located in London, instructs RSP 110 to collect data from server 112.
• the RSP Manager 180 responsive to a still earlier access event relating to server 152 monitored by RSP 175, located in Beijing, instructs RSP 175 to collect data from server 152.
• the RSP Manager 180 responsive to a yet earlier access event relating to server 120 monitored by RSP 172, located in Paris, instructs RSP 172 to collect data server 120.
• the RSP Manager 180 responsive to an even earlier access event relating to server 142 monitored by RSP 174, located in Seattle, instructs RSP 174 to collect data from server 142.
• prioritization may be based not only on access events, but additionally and/or alternatively on more or more of the following:
• FIG. 4A is a simplified illustration of part of the system and methodology illustrated in Fig. 1 and Fig. 2, showing coordination of the timing of data collection by multiple ones of said plurality of RSPs on the basis of the amount of data to be collected from the data resources monitored thereby and on the basis of type of the data resources monitored thereby.
• Fig. 4A The amount of data to be collected data is symbolized in Fig. 4A by a number of file cabinets containing data.
• the type of data resource is indicated by the following typical abbreviations: EXS - Exchange server, WIN FS - WINDOWS® File Server, NAS - Network Attached Storage Device, SP - SHAREPOINT® Servers and UX FS - UNIX® File Server.
• RSP Manager 180 two management rules are implemented by RSP Manager 180, namely:
• RSPs which monitor data resources having greater real time criticality are instructed to collect data before RSPs which monitor data resources having lesser real time criticality;
• RSPs which have a greater amount of data to transmit are instructed to collect before RSPs having a lesser amount of data to transmit.
• RSP Manager 180 initially instructs RSP 176 located in Delhi, which monitors multiple Exchange Servers that have a relatively high real time criticality, to collect a relatively large amount of data from the data resources monitored thereby.
• RSP Manager 180 instructs RSP 173 located in Rome, which monitors multiple WINDOWS® File Servers that have yet a slightly lesser real time criticality, to collect a slightly lesser amount of data from the data resources monitored thereby.
• RSP Manager 180 instructs RSP 175 located in Beijing, which monitors multiple Network Attached Storage Device that have yet a slightly lower high real time criticality, to collect a similar amount of data from the data resources monitored thereby.
• RSP Manager 180 instructs RSP 171 located in London, which monitors multiple SHAREPOINT® Servers that have yet a slightly lower high real time criticality, to collect a similar amount of data from the data resources monitored thereby.
• RSP Manager 180 instructs RSP 172 located in Paris, which also monitors multiple SHAREPOINT® Servers, to collect a relatively small amount of data from the data resources monitored thereby. Thereafter, RSP Manager 180 instructs RSP 174 located in Seattle, which monitors multiple UNIX® File Server that have a slightly lower high real time criticality, to collect a similar amount of data from the data resources monitored thereby.
• FIG. 4B is a simplified illustration of part of the system and methodology illustrated in Fig. 1 and Fig. 2, showing coordination of the timing of data collection by multiple ones of said plurality of RSPs on the basis of type of data resource and on the basis of user defined prioritization of RSPs located in various physical sites.
• Fig. 4B The type of data resource from which data is to be collected is indicated in Fig. 4B by the following typical abbreviations: EXS - Exchange server, WIN FS - WINDOWS® File Server, NAS - Network Attached Storage Device, SP - SHAREPOINT® Servers and UX FS - UNIX® File Server.
• RSP Manager 180 two management rules are implemented by RSP Manager 180, namely:
• RSPs which monitor data resources having greater real time criticality are instructed to collect data before RSPs which monitor data resources having lesser real time criticality;
• RSPs having higher user defined priorities are instructed to collect data before RSPs having lower user defined priorities.
• RSP Manager 180 initially instructs RSP 171 located in London which has a high user-defined priority and which monitors multiple Exchange Servers which have a relatively high real time criticality, to collect data from the data resources monitored thereby.
• RSP Manager 180 instructs RSP 176 located in Delhi which has a slightly lower user-defined priority and which monitors multiple WINDOWS® File Servers which have a slightly lower real time criticality, to collect data from the data resources monitored thereby.
• RSP Manager 180 instructs RSP 173, located in Rome which has yet an even more slightly lower user-defined priority and which also monitors multiple WINDOWS® File Servers, to collect data from the data resources monitored thereby.
• RSP Manager 180 instructs RSP 174 located in Seattle which has yet an even more slightly lower user-defined priority and which also monitors multiple WINDOWS® File Servers, to collect data from the data resources monitored thereby.
• RSP Manager 180 instructs RSP 172 located in Paris which has yet an even more slightly lower user-defined priority and which monitors multiple SHAREPOINT® Servers which have a relatively low real time criticality, to collect data from the data resources monitored thereby.
• RSP Manager 180 instructs RSP 175, which is located in Beijing which has yet an even more slightly lower user- defined priority and which monitors multiple UNIX® File Servers which have even a slightly lower high real time criticality, to collect data from the data resources monitored thereby.
• Fig. 4C is a simplified illustration of part of the system and methodology illustrated in Fig. 1 and Fig. 2, showing coordination of the timing of data collection by multiple ones of the plurality of RSPs on the basis of size of data resource and on the basis of type of data resource and showing prioritization of certain data resources over other data resources based at least partially on characteristics of real time event collection and of file system crawling for data structure and permissions.
• the amount of data to be collected data is symbolized in Fig. 4C by a number of file cabinets containing data.
• the type of data resource is indicated by the following typical abbreviations: EXS - Exchange server, WIN FS - WINDOWS® File Server, NAS - Network Attached Storage Device, SP - SHAREPOINT® Servers and UX FS - UNIX® File Server.
• RSP Manager 180 In the example of Fig. 4C, four management rules are implemented by RSP Manager 180, namely:
• RSPs which monitor data resources having greater real time criticality are instructed to collect data before RSPs which monitor data resources having lesser real time criticality;
• RSPs which have a greater amount of data to transmit are instructed to collect before RSPs having a lesser amount of data to transmit;
• priority is given to data collection from data resources with respect to which access events have occurred; and whereby priority is given to data collection from data resources with respect to which file system crawling for data structure and permissions have recently occurred.
• RSP Manager 180 becomes aware of access events and recent file system crawling for data structure and permissions relating to various data resources, as by periodic querying the various RSP. Immediately upon become aware of such an access event relating to a data resource monitored by RSP 176 located in Delhi, and for which data resource a file system crawling was recently performed, RSP manager 180 instructs RSP 176, which monitors multiple Exchange Servers that have a relatively high real time criticality, to collect a relatively large amount of data from the data resources monitored thereby.
• RSP Manager 180 responsive to an earlier access event relating to a data resource monitored by RSP 173 located in Rome, and to an earlier file system crawl of a data resource monitored by RSP 173, instructs RSP, which monitors multiple WINDOWS® File Servers which have a slightly lower real time criticality, to collect a slightly lesser amount of data from the data resources monitored thereby.
• RSP Manager 180 responsive to an even earlier access event relating to a data resource monitored by RSP 171 located in London, and to an earlier file system crawl of a data resource monitored by RSP 171, instructs RSP 171, which monitors multiple Network Attached Storage Device that have a slightly lower high real time criticality, to collect a slightly lesser amount of data from the data resources monitored thereby.
• RSP Manager 180 responsive to an even earlier access event relating to a data resource monitored by RSP 172 is located in Paris, and to a yet earlier file system crawl of a data resource monitored by RSP 172, instructs RSP 1 2, which monitors multiple SHAREPOINT® Servers that have a slightly lower high real time criticality, to collect a slightly lesser amount of data from the data resources monitored thereby.
• RSP Manager 180 responsive to an even earlier access event relating to a data resource monitored by RSP 175 located in Beijing, and to a yet earlier file system crawl of a data resource monitored by RSP 175, instructs RSP 175, which monitors multiple UNIX® File Servers that have a slightly lower high real time criticality, to collect a slightly less amount of data from the data resources monitored thereby.
• RSP Manager 180 responsive to an even earlier access event relating to a data resource monitored by RSP 174 located in Seattle, and to a yet earlier file system crawl of a data resource monitored by RSP 174, instructs RSP 174, which also monitors multiple SHAREPOINT® Servers, to collect a similar amount of data from the data resources monitored thereby.
• Fig. 5A is a simplified illustration of part of the system and methodology illustrated in Fig. 1 and Fig. 2, showing coordination of the timing of data collection by multiple ones of said plurality of RSPs on the basis of network latency.
• Network latency is symbolized in Fig. 5 A by traffic congestion, the greater the congestion the greater the latency.
• a management rule is implemented by RSP Manager 180 whereby network connections having lesser latency are utilized before network connections having greater latency.
• RSP Manager 180 initially instructs RSP 176 located in Delhi to transmit data collected thereby to the RSP Manager 180 over a network connection 306 which has relatively low latency. Thereafter, RSP Manager 180 instructs RSP 174 located in Seattle to transmit data collected thereby to the RSP Manager 180 over a network connection 315 which has slightly higher latency than network connection 306. Thereafter, RSP Manager 180 instructs RSP 175 located in Beijing to transmit data collected thereby to the RSP Manager 180 over a network connection 324, which has slightly higher latency than network connection 315.
• RSP Manager 180 instructs RSP 171 located in London to transmit data collected thereby to the RSP Manager 180 over a network connection 331, which has slightly higher latency than network connection 324. Thereafter, RSP Manager 180 instructs RSP 172 located in Paris to transmit data collected thereby to the RSP Manager 180 over a network connection 332, which has slightly higher latency than network connection 331. Thereafter, RSP Manager 180 instructs RSP 173 located in Rome to transmit data collected thereby to the RSP Manager 180 over a network connection 333, which has slightly higher latency than network connection 332.
• Fig. 5B is a simplified illustration of part of the system and methodology illustrated in Fig. 1 and Fig.
• Network bandwidth is symbolized in Fig. 5B by a number of traffic lanes, the greater the number of lanes the greater the bandwidth.
• a management rule is implemented by RSP Manager 180 whereby network connections having greater bandwidth are utilized before network connections having lesser bandwidth.
• RSP Manager 180 initially instructs RSP 176 located in Delhi to transmit data collected thereby to the RSP Manager 180 over a network connection 336 which has relatively high bandwidth. Thereafter, RSP Manager 180 instructs RSP 174 located in Seattle to transmit data collected thereby to the RSP Manager 180 over a network connection 345 which has slightly lower bandwidth than network connection 336. Thereafter or simultaneously, RSP Manager 180 instructs RSP 175 located in Beijing to transmit data collected thereby to the RSP Manager 180 over a network connection 354, which has bandwidth similar to that of network connection 345.
• RSP Manager 180 instructs RSP 171 located in London to transmit data collected thereby to the RSP Manager 180 over a network connection 361, which has slightly lower bandwidth than network connection 354. Thereafter or simultaneously, RSP Manager 180 instructs RSP 172 located in Paris to transmit data collected thereby to the RSP Manager 180 over a network connection 362, which has bandwidth similar to that of network connection 361. Thereafter, RSP Manager 180 instructs RSP 173 located in Rome to transmit data collected thereby to the RSP Manager 180 over a network connection 363, which has slightly lower bandwidth than network connection 362.
• Fig. 5C is a simplified illustration of part of the system and methodology illustrated in Fig. 1 and Fig. 2, showing coordination of the timing of data transmission by multiple ones of said plurality of RSPs on the basis of the amount of collected data to be transmitted.
• the amount of collected data to be transmitted is symbolized in Fig. 5C by a number of file cabinets containing data.
• a management rule is implemented by RSP Manager 180 whereby RSPs which have a greater amount of data to transmit are instructed to transmit before RSPs having a lesser amount of data to transmit.
• RSP Manager 180 initially instructs RSP 176 located in Delhi to transmit a relatively large amount of data collected thereby to RSP Manager 180. Thereafter, RSP Manager 180 instructs RSP 173 located in Rome to transmit a slightly lesser amount of data collected thereby to RSP Manager 180. Thereafter, RSP Manager 180 instructs RSP 171 located in London to transmit an even lesser amount of data collected thereby to RSP Manager 180.
• RSP Manager 180 instructs RSP 175 located in Beijing to transmit an even smaller amount of data collected thereby to RSP Manager 180. Thereafter or simultaneously, RSP Manager 180 instructs RSP 172 located in Paris to transmit a similar amount of data collected thereby to the RSP Manager 180. Thereafter, RSP Manager 180 instructs RSP 174 located in Seattle to transmit a yet smaller amount of data collected thereby to RSP Manager 180.
• Fig. 5D is a simplified illustration of part of the system and methodology illustrated in Fig. 1 and Fig. 2, showing coordination of the timing of data transmission by multiple ones of said plurality of RSPs on the basis of type of data resources monitored by the RSPs.
• the type of data resource is indicated by the following typical abbreviations: EXS - Exchange server, WIN FS - WINDOWS® File Server, NAS - Network Attached Storage Device, SP - SHAREPOINT® Servers and UX FS - UNIX® File Server.
• a management rule is implemented by RSP Manager 180 whereby RSPs which monitor data resources having greater real time criticality, are instructed to transmit before RSPs which monitor data resources having lesser real time criticality.
• RSP Manager 180 initially instructs RSP 171, which monitors multiple Exchange Servers, which are determined, for example, to have relatively high real time criticality, to transmit data collected thereby to RSP Manager 180. Thereafter, RSP Manager 180 instructs RSP 176, which monitors multiple WINDOWS® File Servers, which are determined, for example, to have slightly lower real time criticality, to transmit data collected thereby to RSP Manager 180. Thereafter, RSP Manager 180 instructs RSP 173, which monitors multiple NAS devices, which are determined, for example, to have even lower real time criticality, to transmit data collected thereby to RSP Manager 180.
• RSP Manager 180 instructs RSP 174, which monitors multiple SHAREPOINT® File Servers, which are determined, for example, to have still lower real time criticality, to transmit data collected thereby to RSP Manager 180.
• RSP Manager 180 instructs RSP 172, which monitors multiple UNIX® File Servers, which are determined, for example, to have yet lower real time criticality, to transmit data collected thereby to RSP Manager 180.
• RSP Manager 180 instructs RSP 175, which also monitors multiple UNIX® File Servers, which are determined, for example, to have similarly low real time criticality, to transmit data collected thereby to the RSP Manager 180.
• FIG. 5E is a simplified illustration of part of the system and methodology illustrated in Fig. 1 and Fig. 2, showing coordination of the timing of data transmission by multiple ones of said plurality of RSPs on the basis of user defined prioritization of RSPs located in various physical sites.
• a management rule is implemented by RSP Manager 180 whereby RSPs having higher user defined priorities are instructed to transmit before RSPs having lower user defined priorities.
• RSPs which are located in locations having higher user-defined priorities, are instructed to transmit before RSPs which are located in locations having lower user- defined priorities.
• RSP Manager 180 initially instructs RSP 175 located in Beijing, which has the highest user-defined priority, to transmit data collected thereby to the RSP Manager 180. Thereafter, RSP Manager 180 instructs RSP 174 located in Seattle, which has the next-highest user-defined priority, to transmit data collected thereby to the RSP Manager 180. Thereafter, RSP Manager 180 instructs RSP 176 located in Delhi, which has the third highest user-defined priority, to transmit data collected thereby to the RSP Manager 180. Thereafter, RSP Manager 180 instructs RSP 172 located in Paris, which has the fourth-highest user-defined priority, to transmit data collected thereby to the RSP Manager 180.
• RSP Manager 180 instructs RSP 171 located in London, which has the fifth-highest user-defined priority, to transmit data collected thereby to the RSP Manager 180. Thereafter RSP Manager 180 instructs RSP 173 located in Rome which has the next highest user-defined priority, to transmit data collected thereby to the RSP Manager 180.
• Fig. 5F is a simplified illustration of part of the system and methodology illustrated in Fig. 1 and Fig. 2, showing coordination of the timing of data transmission by multiple ones of said plurality of RSPs on the basis of time of day/day of week at the RSP.
• a management rule is implemented by RSP Manager 180 whereby RSPs are instructed to transmit data at times when data resources have low utilization rates, such as during the local nighttime hours thereat.
• Fig. 5F Implementation of this rule in the context of an embodiment of the present invention is shown in Fig. 5F as follows: At 12:00 midnight local London time, RSP Manager 180 instructs RSP 171 located in London to transmit data collected from servers 110, 112 and 114 monitored thereby. Thereafter, at 2:00 AM local Paris time RSP Manager 180 instructs RSP 172 located in Paris to transmit data collected from servers 120, 122 and 124 monitored thereby. Simultaneously, at 2:00 AM local Rome time RSP Manager 180 instructs RSP 173 located in Rome to transmit data collected from servers 130, 132 and 134 monitored thereby.
• RSP Manager 180 instructs RSP 175 located in Beijing to transmit data collected from servers 150, 152 and 154 monitored thereby.
• RSP Manager 180 instructs RSP 176 located in Delhi to transmit data collected from servers 160, 162 and 164 monitored thereby.
• RSP Manager 180 instructs RSP 174 located in Seattle to transmit data collected from servers 140, 142 and 144 monitored thereby.
• FIG. 5G is a simplified illustration of part of the system and methodology illustrated in Fig. 1 and Fig. 2, showing coordination of the timing of data transmission by multiple ones of said plurality of RSPs on the basis of user defined prioritization of data resources.
• a management rule is implemented by RSP Manager 180 whereby RSPs having higher user defined priorities are instructed to transmit data before RSPs having lower user defined priorities.
• RSPs which are located in locations having higher user-defined priorities, are instructed to collect data to be transmitted before RSPs which are located in locations having lower user-defined priorities.
• RSP Manager 180 initially instructs RSP 171 located in London which has a high user-defined priority to transmit data collected from the data resources monitored thereby.
• RSP Manager 180 instructs RSP 176 located in Delhi which has a slightly lower user-defined priority to transmit data collected from the data resources monitored thereby. Thereafter, RSP Manager 180 instructs RSP 173, located in Rome which has yet an even more slightly lower user-defined priority to transmit data collected from the data resources monitored thereby. Yet thereafter, RSP Manager 180 instructs RSP 174 located in Seattle which has yet an even more slightly lower user-defined priority, to transmit data collected from the data resources monitored thereby.
• RSP Manager 180 instructs RSP 172 located in Paris which has yet an even more slightly lower user-defined priority, to transmit data collected from the data resources monitored thereby. Thereafter, RSP Manager 180 instructs RSP 175, which is located in Beijing which has yet an even more slightly lower user-defined priority to transmit data collected from the data resources monitored thereby.
• Fig. 5H is a simplified illustration of part of the system and methodology illustrated in Fig. 1 and Fig. 2, showing coordination of the timing of data transmission by multiple ones of said plurality of RSPs on the basis of on the basis of time of day/day of week at the RSP and on the basis of the amount of collected data to be transmitted.
• the amount of collected data to be transmitted is symbolized in Fig. 5H by a number of file cabinets containing data.
• RSP Manager 180 two management rules are implemented by RSP Manager 180, namely:
• RSPs are instructed to transmit data collected from their respective data resources at times the network connections to those RSPs have low utilization rates, such as during the local nighttime hours thereat;
• RSPs which have a greater amount of data to transmit are instructed to transmit before RSPs having a lesser amount of data to transmit.
• RSP Manager 180 instructs RSP 171, located in London, to transmit data collected from the data resources monitored thereby. Thereafter, at 2:00 AM local Paris time, RSP Manager 180 instructs RSP 172, located in Paris, to transmit a relatively large amount of data collected from the data resources monitored thereby. Since RSP 173 in Rome has less data to transmit than does the RSP 172, located in Paris, the data transmission from the RSP 130 in Rome is set to be later than the data transmission from the RSP 172, located in Paris. Accordingly, at 2:30 AM local Rome time, RSP Manager 180 instructs RSP 173, located in Rome, to transmit data collected from the data resources monitored thereby.
• RSP Manager 180 instructs RSP 175 located in Beijing to transmit data collected from the data resources monitored thereby.
• RSP Manager 180 instructs RSP 176 located in Delhi to transmit data collected from the data resources monitored thereby.
• RSP Manager 180 instructs RSP 174 located in Seattle to transmit data collected from the data resources monitored thereby.
• Fig. 6A is a simplified illustration of part of the system and methodology illustrated in Fig. 1 and Fig. 2, showing coordination of the timing of data collection by multiple ones of the plurality of RSPs on the basis of size of data resource and on the basis of type of data resource and showing prioritization of certain data resources over other data resources based at least partially on characteristics of real time event collection and of file system crawling for data structure and permissions and showing coordination of the timing of at least some of the data transmission from ones of the plurality of RSPs on the basis of time of day/day of week at the RSP.
• the amount of data to be collected data is symbolized in Fig. 6A by a number of file cabinets containing data.
• the type of data resource is indicated by the following typical abbreviations: EXS - Exchange server, WIN FS - WINDOWS® File Server, NAS - Network Attached Storage Device, SP - SHAREPOINT® Servers and UX FS - UNIX® File Server.
• RSP Manager 180 five management rules are implemented by RSP Manager 180, namely :
• RSPs which monitor data resources having greater real time criticality are instructed to collect data before RSPs which monitor data resources having lesser real time criticality;
• RSPs which have a greater amount of data to transmit are instructed to collect before RSPs having a lesser amount of data to transmit;
• RSPs are instructed to transmit data at times when data resources have low utilization rates, such as during the local nighttime hours thereat.
• RSP Manager 180 becomes aware of access events and recent file system crawling for data structure and permissions relating to various data resources, as by periodic querying the various RSP. Upon become aware of such an access event relating to a data resource monitored by RSP 171, located in London and for which data resource a file system crawling was recently performed, the RSP manager 180 instructs RSP 171, which monitors multiple Exchange Servers which have a relatively high real time criticality, to collect a relatively large amount of data from the data resources monitored thereby at 12:00 midnight local London time.
• RSP Manager 180 responsive to an earlier access event relating to a data resource monitored by RSP 172 located in Paris and to an earlier file system crawl of a data resource monitored by RSP 172, instructs RSP 172, which monitors multiple WINDOWS® File Servers that have a slightly lower real time criticality, to collect a slightly lesser amount of data from the data resources monitored thereby at 2:00 AM local Paris time.
• RSP Manager 180 responsive to an even earlier access event relatmg to a data resource monitored by RSP 173 located in Rome and to an earlier file system crawl of a data resource monitored by RSP 173, instructs RSP 173, which monitors multiple Network Attached Storage Device that have a slightly lower high real time criticality, to collect a slightly lesser amount of data from the data resources monitored thereby.
• RSP Manager 180 responsive to an even earlier access event relating to a data resource monitored by RSP 175 located in Beijing and to a yet earlier file system crawl of a data resource monitored by RSP 175, instructs RSP 175, which monitors multiple SHAREPOINT® Servers that have a slightly lower high real time criticality, to collect a similar amount of data from the data resources monitored thereby at 12:00 midnight the next day local Beijing time.
• RSP Manager 180 responsive to an even earlier access event relating to a data resource monitored by RSP 176 located in Delhi and to a yet earlier file system crawl of a data resource monitored by RSP 176, instructs RSP 176, which monitors multiple UNIX® File Servers that have a slightly lower high real time criticality, to collect a slightly less amount of data from the data resources monitored thereby at 12:00 midnight local Delhi time.
• the RSP Manager 180 responsive to an even earlier access event relating to a data resource monitored by RSP 174 located in Seattle and to a yet earlier file system crawl of a data resource monitored by RSP 174, instructs RSP 174, which monitors multiple SHAREPOINT® Servers that have a slightly lower high real time criticality, to collect a similar amount of data from the data resources monitored thereby.
• Fig. 6B is a simplified illustration of part of the system and methodology illustrated in Fig. 1 and Fig. 2, showing coordination of the timing of data collection by multiple ones of the plurality of RSPs on the basis of size of data resource and on the basis of type of data resource and showing prioritization of certain data resources over other data resources based at least partially on characteristics of real time event collection and of file system crawling for data structure and permissions and based on prioritization of certain RSPs over other RSPs.
• the amount of data to be collected data is symbolized in Fig. 6B by a number of file cabinets containing data.
• the type of data resource is indicated by the following typical abbreviations: EXS - Exchange server, WIN FS - WINDOWS® File Server, NAS - Network Attached Storage Device, SP - SHAREPOINT® Servers and UX FS - UNIX® File Server.
• RSP Manager 180 five management rules are implemented by RSP Manager 180, namely:
• RSPs which monitor data resources having greater real time criticality are instructed to collect data before RSPs which monitor data resources having lesser real time criticality;
• RSPs which have a greater amount of data to transmit are instructed to collect before RSPs having a lesser amount of data to transmit;
• RSPs having higher user defined priorities are instructed to transmit before RSPs having lower user defined priorities.
• RSP Manager 180 becomes aware of access events and recent file system crawling for data structure and permissions relating to various data resources, as by periodic querying the various RSP. Immediately upon become aware of such an access event relating to a data resource monitored by RSP 176, located in Delhi which has the highest user-defined priority and for which data resource a file system crawling was recently performed, the RSP manager 180 instructs RSP 176, which is located in Delhi and which monitors multiple Exchange Servers that have a relatively high real time criticality, to collect a relatively large amount of data from the data resources monitored thereby.
• RSP Manager 180 responsive to an earlier access event relating to a data resource monitored by RSP 173 and to an earlier file system crawl of a data resource monitored by RSP 173 which has the next-highest user-defined priority, instructs RSP 173 located in Rome, which monitors multiple WINDOWS® File Servers that have a relatively high real time criticality, to collect a slightly lesser amount of data from the data resources monitored thereby.
• the RSP Manager 180 responsive to an even earlier access event relating to a data resource monitored by RSP 171 and to an earlier file system crawl of a data resource monitored by RSP 171, instructs RSP 171 located in London, which has the third highest user-defined priority, which monitors multiple Network Attached Storage Device that have a slightly lower high real time criticality, to collect a slightly lesser amount of data from the data resources monitored thereby.
• the RSP Manager 180 responsive to an even earlier access event relating to a data resource monitored by RSP 172 and to a yet earlier file system crawl of a data resource monitored by RSP 172, instructs RSP 172 located in Paris, which has the fourth-highest user-defined priority, and which monitors multiple SHAREPOINT® Servers that have a slightly lower high real time criticality, to collect a similar amount of data from the data resources monitored thereby.
• the RSP Manager 180 responsive to an even earlier access event relating to a data resource monitored by RSP 175 and to a yet earlier file system crawl of a data resource monitored by RSP 175, instructs RSP 175 located in Beijing, which has the fifth-highest user-defined priority, and which monitors multiple UNIX® File Servers that have a slightly lower high real time criticality, to collect a slightly less amount of data from the data resources monitored thereby.
• the RSP Manager 180 responsive to an even earlier access event relating to a data resource monitored by RSP 174 and to a yet earlier file system crawl of a data resource monitored by RSP 174, instructs RSP 174 located in Seattle, which has the next highest user-defined priority, and which also monitors multiple UNIX® File, to collect a similar amount of data from the data resources monitored thereby.
• Fig. 7 is a simplified illustration of part of the system and methodology illustrated in Fig. 1 and Fig. 2, showing coordination of the timing of data collection by multiple ones of the plurality of RSPs on the basis of size of data resource and on the basis of type of data resource and showing prioritization of certain data resources over other data resources based at least partially on characteristics of real time event collection and of file system crawling for data structure and permissions and based on prioritization of certain RSPs over other RSPs and showing coordination of the timing of at least some of the data transmission from ones of the plurality of RSPs on the basis of time of day/day of week at the RSP.
• the amount of data to be collected data is symbolized in Fig. 7 by a number of file cabinets containing data.
• the type of data resource is indicated by the following typical abbreviations: EXS - Exchange server, WIN FS - WINDOWS® File Server, NAS - Network Attached Storage Device, SP - SHAREPOINT® Servers and UX FS - UNIX® File Server.
• RSP Manager 180 six management rules are implemented by RSP Manager 180, namely:
• RSPs which monitor data resources having greater real time criticality are instructed to collect data before RSPs which monitor data resources having lesser real time criticality;
• RSPs which have a greater amount of data to transmit are instructed to collect before RSPs having a lesser amount of data to transmit;
• RSPs are instructed to transmit data at times when data resources have low utilization rates, such as during the local nighttime hours thereat;
• RSPs having higher user defined priorities are instructed to transmit before RSPs having lower user defined priorities.
• RSP Manager 180 becomes aware of access events and recent file system crawling for data structure and permissions relating to various data resources, as by periodic querying the various RSP. Upon become aware of such an access event relating to a data resource monitored by RSP 171, located in London which has the highest user-defined priority and for which data resource a file system crawling was recently performed, the RSP manager 180 instructs RSP 171, which monitors multiple Exchange Servers which have a relatively high real time criticality, to collect a relatively large amount of data from the data resources monitored thereby at 12:00 midnight local London time.
• RSP Manager 180 responsive to an earlier access event relating to a data resource monitored by RSP 172 located in Paris and to an earlier file system crawl of a data resource monitored by RSP 172 which has the next-highest user- defined priority, instructs RSP 172, which monitors multiple WINDOWS® File Servers which have a slightly lower real time criticality, to collect a slightly lesser amount of data from the data resources monitored thereby at 2:00 AM local Paris time.
• RSP Manager 180 responsive to an even earlier access event relating to a data resource monitored by RSP 173 located in Rome and to an earlier file system crawl of a data resource monitored by RSP 173, instructs RSP 173, which has the third highest user- defined priority, which monitors multiple Network Attached Storage Device which have a slightly lower high real time criticality, to collect a slightly lesser amount of data from the data resources monitored thereby.
• the RSP Manager 180 responsive to an even earlier access event relating to a data resource monitored by RSP 175 located in Beijing and to a yet earlier file system crawl of a data resource monitored by RSP 175, instructs RSP 175, which has the fourth-highest user-defined priority, which monitors multiple SHAREPOINT® Servers which have a slightly lower high real time criticality, to collect a similar amount of data from the data resources monitored thereby at 12:00 midnight the next day local Beijing time.
• the RSP Manager 180 responsive to an even earlier access event relating to a data resource monitored by RSP 176 located in Delhi and to a yet earlier file system crawl of a data resource monitored by RSP 176, instructs RSP 176, which has the fifth-highest user-defined priority, which monitors multiple UNIX® File Servers which have a slightly lower high real time criticality, to collect a slightly less amount of data from the data resources monitored thereby at 12:00 midnight local Delhi time.
• the RSP Manager 180 responsive to an even earlier access event relating to a data resource monitored by RSP 174 located in Seattle and to a yet earlier file system crawl of a data resource monitored by RSP 174, instructs RSP 174, which has the next highest user-defined priority, and which also monitors multiple UNIX® File Servers, to collect a similar amount of data from the data resources monitored thereby.

Landscapes

• Engineering & Computer Science (AREA)
• Theoretical Computer Science (AREA)
• Physics & Mathematics (AREA)
• General Physics & Mathematics (AREA)
• General Engineering & Computer Science (AREA)
• Quality & Reliability (AREA)
• Databases & Information Systems (AREA)
• Computing Systems (AREA)
• Business, Economics & Management (AREA)
• Human Resources & Organizations (AREA)
• Economics (AREA)
• Data Mining & Analysis (AREA)
• Entrepreneurship & Innovation (AREA)
• Strategic Management (AREA)
• Marketing (AREA)
• Game Theory and Decision Science (AREA)
• Educational Administration (AREA)
• Operations Research (AREA)
• Development Economics (AREA)
• Tourism & Hospitality (AREA)
• General Business, Economics & Management (AREA)
• Mathematical Physics (AREA)
• Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
• Information Transfer Between Computers (AREA)
• Data Exchanges In Wide-Area Networks (AREA)
• Computer And Data Communications (AREA)

Priority Applications (4)

Applications Claiming Priority (1)

Publications (1)

Family

ID=49300076

Family Applications (1)

Country Status (4)

Cited By (1)

Citations (4)

Family Cites Families (7)

• 2012
  • 2012-04-04 IN IN8967DEN2014 patent/IN2014DN08967A/en unknown
  • 2012-04-04 CN CN201280073661.6A patent/CN104335203B/zh not_active Expired - Fee Related
  • 2012-04-04 WO PCT/IL2012/000153 patent/WO2013150508A1/en active Application Filing
  • 2012-04-04 EP EP12873565.1A patent/EP2834751A4/en not_active Ceased

Patent Citations (4)

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events