Patent Application
20170344446
The present invention relates to data storage systems, and more specifically, this invention relates to recovery of data across a data storage system.
Data storage systems, e.g., networks, allow for data to potentially be stored in multiple different storage sites and/or across multiple storage devices. Despite being stored in various locations, all, subsets, some, etc. of the data included in a data storage system may be accessed from a plurality of different locations, e.g., terminals.
The development of multi-target peer-to-peer remote copy (PPRC) has introduced data storage network configurations which are able to perform multi-target metro/global mirror (MGM) operations. However, such developments have also introduced added complexity. When multi-target environments are introduced, processes such as failure recovery become more complicated. Previous implementations have resorted to making unnecessary duplicate copies of data across long distance links in order to perform data recovery, which again increases inefficiency.
A computer-implemented method, according to one embodiment, includes: using a supplemental data storage volume at a secondary location to track a first set of data updates to a primary data storage volume at a primary location in response to a failure event at the primary location; retrieving a second set of tracked data updates to the primary data storage volume stored in a secondary data storage volume at the secondary location; merging the second set of tracked data updates into the first set of tracked data updates in the supplemental data storage volume; and transitioning the merged data updates from the supplemental data storage volume at the secondary location to the primary data storage volume at the primary location.
A computer program product, according to another embodiment, includes a computer readable storage medium having program instructions embodied therewith. The computer readable storage medium is not a transitory signal per se. Moreover, the program instructions are readable and/or executable by a computer to cause the computer to: use, by the computer, data storage volumes at a secondary location to track data updates to a primary data storage volume at a primary location in response to a failure event at the primary location; transition, by the computer, the tracked data updates from the data storage volumes at the secondary location to the primary data storage volume at the primary location; and determine, by the computer, whether all of the tracked data updates have transitioned from the data storage volumes at a secondary location to the primary data storage volume at the primary location. The data storage volumes include a supplemental data storage volume and a secondary data storage volume. Accordingly, the program instructions are readable and/or executable by the computer to cause the computer to: copy, by the computer, data stored in the supplemental data storage volume to the secondary data storage volume in response to determining that all of the tracked data updates have transitioned from the data storage volumes at the secondary location to the primary data storage volume at the primary location.
A computer-implemented method, according to yet another embodiment, includes: sending, by the computer, data updates to a secondary volume at a secondary location in response to a failure event at a primary location; receiving, by the computer, a single set of merged data updates from a supplemental data storage volume at the secondary location; implementing, by the computer, the received set of merged data updates in the primary data storage volume at the primary location; receiving, by the computer, data updates to the primary data storage volume; and sending, by the computer, the received data updates to the secondary data storage volume at the secondary location.
Other aspects and embodiments of the present invention will become apparent from the following detailed description, which, when taken in conjunction with the drawings, illustrate by way of example the principles of the invention.
The following description is made for the purpose of illustrating the general principles of the present invention and is not meant to limit the inventive concepts claimed herein. Further, particular features described herein can be used in combination with other described features in each of the various possible combinations and permutations.
Unless otherwise specifically defined herein, all terms are to be given their broadest possible interpretation including meanings implied from the specification as well as meanings understood by those skilled in the art and/or as defined in dictionaries, treatises, etc.
It must also be noted that, as used in the specification and the appended claims, the singular forms “a,” “an” and “the” include plural referents unless otherwise specified. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
The following description discloses several preferred embodiments of systems, methods and computer program products for data recovery resulting from a failure event in a data storage network.
In one general embodiment, a computer-implemented method includes using a supplemental data storage volume at a secondary location to track a first set of data updates to a primary data storage volume at a primary location in response to a failure event at the primary location. A second set of tracked data updates are retrieved, the second set of tracked data updates being updates to the primary data storage volume stored in a secondary data storage volume at the secondary location. The second set of tracked data updates is merged into the first set of tracked data updates in the supplemental data storage volume. The merged data updates are transitioned from the supplemental data storage volume at the secondary location to the primary data storage volume at the primary location. The secondary data storage volume at the secondary location is used to track further data updates to the primary data storage volume made at the primary location.
In another general embodiment, a computer program product includes a computer readable storage medium having program instructions embodied therewith, the program instructions readable and/or executable by a computer to cause the computer to use, by the computer, data storage volumes at a secondary location to track data updates to a primary data storage volume at a primary location in response to a failure event at the primary location, wherein the data storage volumes include a supplemental data storage volume and a secondary data storage volume. The program instructions are also readable and/or executable by the computer to cause the computer to transition, by the computer, the tracked data updates from the data storage volumes at the secondary location to the primary data storage volume at the primary location; quiesce, by the computer, data updates to the primary data storage volume; determine, by the computer, whether all of the tracked data updates have transitioned from the data storage volumes at a secondary location to the primary data storage volume at the primary location; copy, by the computer, data stored in the supplemental data storage volume to the secondary data storage volume in response to determining that all of the tracked data updates have transitioned from the data storage volumes at the secondary location to the primary data storage volume at the primary location; and use, by the computer, the secondary data storage volume at the secondary location to track further data updates to the primary data storage volume made at the primary location.
In another general embodiment, a computer-implemented method includes sending, by the computer, data updates to a secondary volume at a secondary location in response to a failure event at a primary location, wherein the data updates correspond to a primary data storage volume at the primary location. A single set of merged data updates is received from a supplemental data storage volume at the secondary location. The received set of merged data updates is implemented in the primary data storage volume at the primary location. Data updates are quiesced to the primary data storage volume. Data stored in the primary data storage volume is copied to a tertiary data storage volume at the primary location. A determination is made as to whether all of the merged data updates have been implemented in the primary data storage volume. Data updates to the primary data storage volume are received in response to determining that all of the merged data updates have been implemented in the primary data storage volume. The received data updates are sent to the secondary data storage volume at the secondary location.
In use, the gateway 101 serves as an entrance point from the remote networks 102 to the proximate network 108. As such, the gateway 101 may function as a router, which is capable of directing a given packet of data that arrives at the gateway 101, and a switch, which furnishes the actual path in and out of the gateway 101 for a given packet.
Further included is at least one data server 114 coupled to the proximate network 108, and which is accessible from the remote networks 102 via the gateway 101. It should be noted that the data server(s) 114 may include any type of computing device/groupware. Coupled to each data server 114 is a plurality of user devices 116. User devices 116 may also be connected directly through one of the networks 104, 106, 108. Such user devices 116 may include a desktop computer, lap-top computer, hand-held computer, printer or any other type of logic. It should be noted that a user device 111 may also be directly coupled to any of the networks, in one embodiment.
A peripheral 120 or series of peripherals 120, e.g., facsimile machines, printers, networked and/or local storage units or systems, etc., may be coupled to one or more of the networks 104, 106, 108. It should be noted that databases and/or additional components may be utilized with, or integrated into, any type of network element coupled to the networks 104, 106, 108. In the context of the present description, a network element may refer to any component of a network.
According to some approaches, methods and systems described herein may be implemented with and/or on virtual systems and/or systems which emulate one or more other systems, such as a UNIX system which emulates an IBM z/OS environment, a UNIX system which virtually hosts a MICROSOFT WINDOWS environment, a MICROSOFT WINDOWS system which emulates an IBM z/OS environment, etc. This virtualization and/or emulation may be enhanced through the use of VMWARE software, in some embodiments.
In more approaches, one or more networks 104, 106, 108, may represent a cluster of systems commonly referred to as a “cloud.” In cloud computing, shared resources, such as processing power, peripherals, software, data, servers, etc., are provided to any system in the cloud in an on-demand relationship, thereby allowing access and distribution of services across many computing systems. Cloud computing typically involves an Internet connection between the systems operating in the cloud, but other techniques of connecting the systems may also be used.
The workstation shown in
The workstation may have resident thereon an operating system such as the Microsoft Windows® Operating System (OS), a MAC OS, a UNIX OS, etc. It will be appreciated that a preferred embodiment may also be implemented on platforms and operating systems other than those mentioned. A preferred embodiment may be written using XML, C, and/or C++ language, or other programming languages, along with an object oriented programming methodology. Object oriented programming (OOP), which has become increasingly used to develop complex applications, may be used.
Now referring to
The storage system manager 312 may communicate with the storage media 304, 308 on the higher storage tier(s) 302 and lower storage tier(s) 306 through a network 310, such as a storage area network (SAN), as shown in
In more embodiments, the storage system 300 may include any number of data storage tiers, and may include the same or different storage memory media within each storage tier. For example, each data storage tier may include the same type of storage memory media, such as HDDs, SSDs, sequential access media (tape in tape drives, optical disk in optical disk drives, etc.), direct access media (CD-ROM, DVD-ROM, etc.), or any combination of media storage types. In one such configuration, a higher storage tier 302, may include a majority of SSD storage media for storing data in a higher performing storage environment, and remaining storage tiers, including lower storage tier 306 and additional storage tiers 316 may include any combination of SSDs, HDDs, tape drives, etc., for storing data in a lower performing storage environment. In this way, more frequently accessed data, data having a higher priority, data needing to be accessed more quickly, etc., may be stored to the higher storage tier 302, while data not having one of these attributes may be stored to the additional storage tiers 316, including lower storage tier 306. Of course, one of skill in the art, upon reading the present descriptions, may devise many other combinations of storage media types to implement into different storage schemes, according to the embodiments presented herein.
According to some embodiments, the storage system (such as 300) may include logic configured to receive a request to open a data set, logic configured to determine if the requested data set is stored to a lower storage tier 306 of a tiered data storage system 300 in multiple associated portions, logic configured to move each associated portion of the requested data set to a higher storage tier 302 of the tiered data storage system 300, and logic configured to assemble the requested data set on the higher storage tier 302 of the tiered data storage system 300 from the associated portions.
Of course, this logic may be implemented as a method on any device and/or system or as a computer program product, according to various embodiments.
The development of multi-target peer-to-peer remote copy (PPRC) has introduced configurations which are able to perform multi-target metro/global mirror (MGM) operations. However, such developments have also introduced added complexity, and as a result, previous attempts to implement such developments have been largely inefficient.
When multi-target environments are introduced, processes such as failure recovery become more complicated. For instance, a recovery to a target at a given remote site uses a set of volumes that are not part of the remote copy relationships and thus cannot be used alone to simply recover data at the originally failed site, e.g., once it is repaired. Previous implementations have resorted to making unnecessary duplicate copies of data across long distance links in order to perform data recovery, which again increases inefficiency.
In sharp contrast, embodiments described herein may be able to perform efficient failure recoveries for multi-target systems, e.g., such that duplicate copies of data are not made and resources are preserved, as will be described in further detail below.
Looking to
As shown, data storage network 400 includes a primary location 402 and a secondary location 404. Secondary location 404 is preferably removed from (e.g., remote relative to) the primary location 402 in order to avoid a total data storage network 400 failure in the case that either locations 402, 404 experiences a failure event, e.g., a power loss.
Primary location 402 includes a primary data storage volume 406 and a tertiary data storage volume 408, which may be coupled using a short distance connection 450, e.g., at least relative to a long distance connection 452 between primary location 402 and secondary location 404. Moreover, a metro mirror relationship preferably exists between primary and tertiary volumes 406, 408, which establishes a short distance, synchronous replication relationship between the data storage volumes 406, 408, which has been represented by the opposite facing arrows as shown.
Secondary location 404 includes a secondary data storage volume 410 in addition to journal 412 and supplemental data storage volume 414. Journal 412 may be used to periodically store consistent copies of data on secondary data storage volume 410, e.g., which may be used to recover data after a failure event. Journal may store the consistent copies of data using journal entries and/or snapshots as would be appreciated by one skilled in the art upon reading the present description. Furthermore, in some approaches, supplemental data storage volume 414 may be a practice copy site, as will be described in further detail below.
Referring still to
In the event of a disaster (e.g., a power loss) at primary location 402, primary and tertiary data storage volumes 406, 408 may fail, thereby causing a campus failure at the primary location 402. Accordingly, steps are preferably taken to implement data storage operations at secondary location 404, e.g., to prevent inoperability of the network 400 as a whole. As mentioned above, some of the embodiments described herein include the ability to efficiently recover from a failure at a primary data storage location, and/or the ability to efficiently shift data storage back to a primary data storage location after recovering from a failure there, without making duplicate copies of data across long distance connections as plagued by previous attempts.
Looking to
Of course, more or less operations than those specifically described in
As shown in
A failover relationship is then established between the secondary volume at the secondary data storage location and the primary volume at the primary data storage location. See operation 508. According to an illustrative approach, establishing the failover relationship may include initiating a bitmap at the secondary volume which may be used to track updates to the data stored on the primary volume which is currently offline. Once the failover relationship has been established, data updates which correspond to the primary volume may be sent to the secondary volume at the secondary volume, e.g., as a result of the failure condition at the primary location. Therefore, the failover relationship may be used to catalogue updates to be implemented on the data stored in the primary volume once the primary volume has been restored.
Method 500 further includes using entries stored in the journal at the secondary location to restore (e.g., reverse restore) data stored in the secondary data storage volume. See operation 510. Thus, the consistent copies of data stored in the journal may be used to update (e.g., verify and recover) the data stored in the secondary volume. According to one approach, data may be revert restored on the secondary volume by performing commit revert logic. Moreover, fast reverse restores of flash copy pairs may be performed to reverse restore the data on the secondary volume in some approaches, as would be appreciated by one skilled in the art upon reading the present description.
Optional decision 512 determines whether the reverse restore of operation 510 has completed, e.g., whether the secondary volume has been updated with all data stored in the journal. As shown, method 500 may progress to operation 513 in response to determining that the reverse restore operation has not been completed. Operation 513 includes waiting for an amount of time to pass, whereby method 500 returns to decision 512 to again determine whether the reverse restore operation has completed. It should be noted that in other approaches, operation 513 may include waiting for a predetermined condition to be met, for a user input/request, etc., depending on the desired embodiment.
Method 500 proceeds to optional operation 514 in response to determining that the reverse restore operation has completed, where a Flash copy relationship is established between the secondary volume and the journal. In some instances, performing one or more of the previous operations may remove the Flash copy relationship which preferably exists between the secondary volume and the journal. Therefore, it may be desirable that a Flash copy relationship is reestablished therebetween.
Looking to operation 516, all restored data is copied from the secondary data storage volume to the supplemental data storage volume, e.g., by performing a full copy. Accordingly, the supplemental volume may desirably be supplemented to include all of the updated data stored in the secondary volume. Furthermore, operation 518 of
Accordingly, operation 520 includes using the supplemental data storage volume to track a first set of data updates to the primary data storage volume at the primary location, e.g., by updating an OOS bitmap as described above. Thus, updates which may be received from a host (e.g., a user), are tracked at the supplemental volume, ultimately in response to the initial failure event at the primary location. Under normal operation, host updates are preferably not implemented at a data storage volume removed from the primary location. In other words, it is preferred that host updates are implemented on the primary data storage volume rather than the secondary data storage volume, e.g., to achieve higher efficiency. However, in some approaches this preference may be overwritten such that host updates are implemented at the secondary data storage volume in response to a failure at the primary location.
It follows that operations 502 through 520 may be used to recover operations at the secondary location, preferably such that received data storage operations are implemented as quickly as possible following a failure event at a primary data storage location.
Once the primary volume at the primary data storage location has been repaired and is able to process I/O requests, the data and tracked data updates that have accumulated at the secondary location are preferably transferred back to the primary volume such that further I/O requests can be implemented directly by the primary volume. As mentioned above, previous attempts to implement data stored at a given location back to another location were inefficient.
However, processes described herein improve the efficiency of repairing the data at a primary location following a failure. Looking to operation 522, method 500 includes retrieving a second set of tracked data updates stored in the secondary data storage volume at the secondary location, while operation 523 includes merging the second set of tracked data updates into the first set of tracked data updates in the supplemental data storage volume. According to one approach, the supplemental volume and secondary volume may be effectively paired, e.g., using an AND logical operation. In a preferred approach, operation 522 may be performed by merging the data stored in the OOS bitmaps of the secondary and supplemental volumes. Merging the tracked data updates desirably improves efficiency when copying the data back to the primary data storage volume, as will soon become apparent.
According to an in-use example, which is in no way intended to limit the invention, a system storage may desirably know which storage volumes are pairs at the secondary location, e.g., which may be provided by a user (e.g., customer), an administrator, determined using a procedure and/or any of the processes described herein, etc.
Operation 524 further includes transitioning (e.g., copying) the merged tracked data updates from the supplemental data storage volume at the secondary location to the primary data storage volume at the primary location, while operation 526 transitions (e.g., copies) the merged tracked data updates from the primary data storage volume to the tertiary data storage volume. Thus, a single set of merged data updates is received at the primary location from the supplemental volume at the secondary location.
By merging the changes tracked on the secondary and supplemental volumes, repeat copies of tracked changes are deduplicated, and a simplified list of tracked changes is achieved at the supplemental volume. Thus, the simplified list of tracked changes may be copied back to the primary volume from a single location, with a reduced number of duplicate copies, thereby improving efficiency of the system as a whole, particularly in view of operation 524 being performed over a long distance connection between the secondary and primary volumes. In such embodiments where the merged tracked changes are achieved at the supplemental volume and copied to the primary volume therefrom, the system may operate with the proviso that transitioning the merged data updates from the supplemental data storage volume to the primary data storage volume does not include copying data from the secondary data storage volume to the primary data storage volume. As a result, the amount of bandwidth, time, processing power, etc. that is consumed while copying the data back to the primary data storage volume is reduced, thereby improving overall performance.
Once received, it is preferred that the merged set of data updates are implemented in the primary volume at the primary location, e.g., in order to update the primary volume. Similarly, looking to operation 528, inputs to the storage system are quiesced at the supplemental volume, thereby temporarily deactivating the storage system such that the transition back to the primary volume is achieved without error.
Moreover, looking to
As shown, method 500 may progress to operation 531 in response to determining that all of the merged tracked data updates have not yet been copied to the primary volume. Operation 531 includes waiting for an amount of time to pass, whereby method 500 returns to decision 530 to again determine whether operation 524 has been completed. It should again be noted that in other approaches, operation 531 may include waiting for a predetermined condition to be met, for a user input/request, etc., depending on the desired embodiment.
Method 500 proceeds to operation 532 in response to determining that all of the merged tracked data updates have been copied to the primary volume, where the failover relationship previously established (e.g., see operation 518) between the supplemental volume and the primary volume is terminated. According to one approach, the failover relationship may be terminated by deleting a bitmap, e.g., an out-of-sync (OOS) bitmap, at the supplemental volume which was previously used to track updates.
Moreover, the metro mirror relationship may be reestablished between the primary and tertiary volumes at the primary data storage location. See operation 534. Accordingly, all data stored in the primary volume is preferably copied to the tertiary volume at the primary location in response to implementing the received set of merged data updates in the primary volume. In one approach, the metro mirror relationship may be reestablished by removing the suspension placed on the relationship, e.g., see operation 506.
Method 500 further includes copying data stored in the supplemental data storage volume to the secondary data storage volume. See operation 536. Thus, operation 536 may include using the supplemental volume to reverse restore data on the secondary volume. According to one approach, the reverse restore may be performed by setting the secondary volume equal to the supplemental volume. As mentioned above, by merging the updates tracked by the secondary volume and the supplemental volume, redundant copy operations are avoided. This improvement is further outlined during operation 536 as the reverse restore operation may be performed over the short distance connection between the secondary and supplemental volumes, e.g., rather than over the long distance connection between the secondary and primary volumes. Thus, efficiency of the operation is improved and without sacrificing performance. Moreover, as mentioned above, data may be revert restored on the secondary volume by performing commit revert logic. According to some approaches, fast reverse restores of flash copy pairs may be performed to reverse restore the data on the secondary volume in some approaches, as would be appreciated by one skilled in the art upon reading the present description.
With continued reference to
Furthermore, operation 540 includes using the primary volume at the primary location to perform I/O requests, e.g., from a host.
As described above, the processes of method 500 may be used for efficiently recovering to a secondary data storage location in response to a failure at a primary data storage location. Moreover, method 500 includes processes which may be used to return data storage operations to the primary data storage location in response to the failure being overcome, while maintaining efficiency during the transfer of data. Moreover, any one or more of the processes described herein may be implemented by using existing system storage commands as would be appreciated by one skilled in the art upon reading the present description.
Moreover, embodiments described herein may also implement “practice” functionality which may be used to practice recovering from a simulated failure event. According to an exemplary embodiment, which is in no way intended to limit the invention, one such configuration may allow a user to implement a Flash copy relationship off of the global mirror (GM) secondary volume, which can be used to “practice” a transfer of production to the secondary volume site while still maintaining DR capabilities. A point in time copy of the data may be taken while the remote copy replication is restarted during the practice tests. The practice functionality may also be desirable as it allows a user (e.g., customer) to practice how they would recover from a real failure event. This means that the same Flash copy target volumes used to perform the steps of a practice test, may be the same ones that used during a real production site switch there, e.g., following a failure condition. As a result, potential issues may be reduced by ensuring the set of volumes used during a real failure condition are the same set of volumes used during practice. Accordingly, any one or more of the processes described herein may be implemented during a data storage system “practice” failure operations.
The present invention may be a system, a method, and/or a computer program product. The computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present invention.
The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.
Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.
Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++ or the like, and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention.
Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions.
These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.
The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.
The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.
Moreover, a system according to various embodiments may include a processor and logic integrated with and/or executable by the processor, the logic being configured to perform one or more of the process steps recited herein. By integrated with, what is meant is that the processor has logic embedded therewith as hardware logic, such as an application specific integrated circuit (ASIC), a FPGA, etc. By executable by the processor, what is meant is that the logic is hardware logic; software logic such as firmware, part of an operating system, part of an application program; etc., or some combination of hardware and software logic that is accessible by the processor and configured to cause the processor to perform some functionality upon execution by the processor. Software logic may be stored on local and/or remote memory of any memory type, as known in the art. Any processor known in the art may be used, such as a software processor module and/or a hardware processor such as an ASIC, a FPGA, a central processing unit (CPU), an integrated circuit (IC), a graphics processing unit (GPU), etc.
It will be clear that the various features of the foregoing systems and/or methodologies may be combined in any way, creating a plurality of combinations from the descriptions presented above.
It will be further appreciated that embodiments of the present invention may be provided in the form of a service deployed on behalf of a customer to offer service on demand.
While various embodiments have been described above, it should be understood that they have been presented by way of example only, and not limitation. Thus, the breadth and scope of a preferred embodiment should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents.
| Number | Date | Country | |
|---|---|---|---|
| Parent | 14960277 | Dec 2015 | US |
| Child | 15679036 | US |
