Auto incorporation of new components into a hierarchial network

FIELD OF THE INVENTION

The present invention relates generally to network management, and more particularly to the dynamic incorporation of new components into a hierarchical network.

BACKGROUND

Smarter City/Information Hub solutions are designed using the model of the customer's system either explicitly using the Reference Semantic Model, or implicitly in the Intelligent Operation Center. For a water network, the model can consist of water pipers, flow meters, pumps, reservoirs, and valves. For a public surveillance system, the network is CCTVs, lobbies, rooms, and areas. Regardless of the domain, a model is assumed, and the expectation is that the model is static. Once a snapshot of the physical model is taken, it is modeled and then used for all solutions: visualization, analytics, database, and reports. However, real life is not static. Changes are occurring all the time. New flow meters may get installed and positions of old flow meters may be modified to reflect reality on the ground. New CCTV cameras may be installed. Rooms and lobbies get reconfigured. Often changes such as these are critical because the new assets are intended to plug existing deficiencies. Currently, we go through a costly and time consuming upgrade of the domain model to integrate the new assets. The customer has to seek the developers help to upgrade the model and integrate new assets. Customers who are not covered by a necessary statement of work or are beyond the time horizon of the purchase made, need to go through a new purchase order approval, and that can itself be a time consuming process.

SUMMARY

Embodiments of the present invention provide a system, method, and program product to incorporate new components into a model. A first computing device receives one or more messages, wherein the one or more messages includes information regarding one or more components, wherein each component is part of one or more systems, and wherein each system includes one or more sub systems. The first computing device determines that a first system has changed based on the first computing device comparing the one or more messages to a hierarchical model, wherein the change to the first system includes a change associated with a first component of the first system. The first computing device determines a position of the first component within the first system and within one or more sub-systems of the first system based on the one or more messages. The first computing device updates the hierarchical model to include the first component in a hierarchical location that corresponds to the determined position of the first component.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

<figref idref="DRAWINGS">FIG. 1</figref> is a functional block diagram illustrating the hierarchical auto-updating system in accordance with an embodiment of the present invention.

<figref idref="DRAWINGS">FIG. 2</figref> is a flowchart depicting the operational steps of the hierarchical auto-updating program of <figref idref="DRAWINGS">FIG. 1</figref> in updating a hierarchical domain model based on received messages and user input, in accordance with an embodiment of the present invention.

<figref idref="DRAWINGS">FIG. 3</figref> is a block diagram depicting the hardware components of the auto-updating program of <figref idref="DRAWINGS">FIG. 1</figref>, in accordance with an embodiment of the invention.

DETAILED DESCRIPTION

As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method, or computer program product. Accordingly, aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.), or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module,” or “system.” Furthermore, aspects of the present invention may take the form of a computer program product embodied in one or more computer-readable medium(s) having computer-readable program code/instructions embodied thereon.

Any combination of one or more computer readable medium(s) may be utilized. The computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium. A computer-readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer-readable storage medium would include the following: an electrical connection having one or more wires, 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), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium may be any tangible medium that can contain or store a program for use by, or in connection with, an instruction execution system, apparatus, or device.

A computer-readable signal medium may include a propagated data signal with computer-readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer-readable signal medium may be any computer-readable medium that is not a computer-readable storage medium that can communicate, propagate, or transport a program for use by, or in connection with, an instruction execution system, apparatus, or device.

Program code embodied on a computer-readable medium may be transmitted using any appropriate medium including, but not limited to, wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java®, Smalltalk, C++ or the like, and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on a 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).

Aspects of the present invention are described below 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 program instructions. These computer 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.

The computer program instructions may also be stored in a computer-readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer-readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.

The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus, or other devices to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

Embodiments of the present invention will now be described in detail with reference to the accompanying Figures.

<figref idref="DRAWINGS">FIG. 1</figref> illustrates hierarchical auto-updating system <b>100</b>, in accordance with an embodiment of the present invention. In an exemplary embodiment, dynamic agent replacement system <b>100</b> includes system <b>110</b> and server <b>130</b>, all interconnected via network <b>120</b>.

In the exemplary embodiment, network <b>120</b> is the Internet, representing a worldwide collection of networks and gateways to support communications between devices connected to the Internet. Network <b>120</b> may include, for example, wired, wireless, or fiber optic connections. In other embodiments, network <b>120</b> may be implemented as an intranet, a local area network (LAN), or a wide area network (WAN). In general, network <b>120</b> can be any combination of connections and protocols that will support communications between system <b>110</b> and server <b>130</b>.

In the exemplary embodiment, system <b>110</b> includes component <b>112</b><i>a</i>, component <b>112</b><i>b</i>, and component <b>112</b><i>c</i>. In the exemplary embodiment, system <b>110</b> is a system such as a water network or public surveillance system which is comprised of a plurality of components. While, in the exemplary embodiment, system <b>110</b> is depicted to include only components <b>112</b><i>a</i>, <b>112</b><i>b</i>, and <b>112</b><i>c</i>; in other embodiments, system <b>110</b> may include a plurality of other components. In addition, system <b>110</b> may include a central server which monitors and gathers information, such as status updates, from a plurality of components <b>112</b><i>a</i>, <b>112</b><i>b</i>, and <b>112</b><i>c</i>. Alternatively, system <b>110</b> may include a cluster of computing devices, working together or working separately to perform the functions of the central server, i.e., monitor and gather information from components <b>112</b><i>a</i>, <b>112</b><i>b</i>, and <b>112</b><i>c. </i>

In the exemplary embodiment, components <b>112</b><i>a</i>, <b>112</b><i>b</i>, and <b>112</b><i>c </i>are the components that make up system <b>110</b>. For example, if system <b>110</b> is a water system, components <b>112</b><i>a</i>, <b>112</b><i>b</i>, and <b>112</b><i>c </i>may consist of the water pipes, flow meters, pumps, reservoirs and valves. In the exemplary embodiment, components <b>112</b><i>a</i>, <b>112</b><i>b</i>, and <b>112</b><i>c </i>are capable of communicating (i.e., receiving or transmitting information) with other computing devices, such as server <b>130</b>, via network <b>120</b>. The information transmitted by components <b>112</b><i>a</i>, <b>112</b><i>b</i>, and <b>112</b><i>c </i>to system <b>110</b> may include changes in function e.g., a malfunction or offline component notification, a notification message which may include the latitude and longitude coordinates of the component, status information, manufacturer information, specification information, or other information relevant to the component.

In the exemplary embodiment, server <b>130</b> may be a laptop computer, tablet computer, notebook computer, personal computer (PC), a desktop computer, a personal digital assistant (PDA), a smart phone, or any programmable electronic device capable of communication with system <b>110</b> via network <b>120</b>. In the exemplary embodiment, server <b>130</b> includes user interface <b>132</b>, auto-updating program <b>134</b>, domain model <b>136</b>, and reference directory <b>138</b>. In addition, server <b>130</b> is capable of communicating with system <b>110</b>, such as requesting and receiving information regarding the status of components <b>112</b>. In other embodiments, server <b>130</b> may be capable of communicating with components <b>112</b> directly. Server <b>130</b> may include internal and external hardware components, as depicted and described in further detail with respect to <figref idref="DRAWINGS">FIG. 3</figref>.

In the exemplary embodiment, user interface <b>132</b> includes components used to receive input from a user of server <b>130</b> and transmit the input to auto-updating program <b>134</b> and domain model <b>136</b>. User interface <b>132</b> uses a combination of technologies, such as device drivers, to provide a platform to enable users to interact with auto-updating program <b>134</b> and domain model <b>136</b>.

In the exemplary embodiment, auto-updating program <b>134</b> is software capable of receiving and transmitting information to other computing devices, such as system <b>110</b>, via network <b>120</b>. Auto-updating program <b>134</b> is also capable of creating or updating domain model <b>136</b> based on information, such as information received from system <b>110</b> or input by a user of server <b>130</b>. For example, auto-updating program <b>134</b> receives information from the components of system <b>110</b> and determines, based on the received information, whether there have been new components added to system <b>110</b> and/or if there are any problems with the components of system <b>110</b>. Auto-updating program <b>134</b> is discussed in further detail with regard to <figref idref="DRAWINGS">FIG. 2</figref>.

In the exemplary embodiment, domain model <b>136</b> is a software model or digital representation of system <b>110</b> and describes the hierarchical location of the components of system <b>110</b>, i.e., components <b>112</b><i>a</i>, <b>112</b><i>b</i>, and <b>112</b><i>c</i>. For example, if system <b>110</b> is a vehicle transportation and road system, a road sensor may be placed in a certain location within domain model <b>136</b> based on, for example, the city, particular zone, or specific intersection the sensor belongs to. Therefore, by way of examination of domain model <b>136</b>, a user can determine the location of the road sensor within the context of one or more hierarchical categories (zone, intersections, cities, etc.). In addition, maintenance systems that monitor the components of system <b>110</b>, may also refer to domain model so that the components of system <b>110</b> are monitored in an accurate fashion. The correlation between system <b>110</b> and maintenance systems that may use domain model <b>136</b> to monitor or maintain system <b>110</b> is described in further details below. In the exemplary embodiment, domain model <b>136</b> is a part of auto-updating program <b>134</b> and may be updated by auto-updating program <b>134</b> on a scheduled basis, e.g., weekly or daily.

In the exemplary embodiment, reference directory <b>138</b> contains information regarding how specific hierarchies are defined. For example, zones for water or electricity systems may be defined by geographical coordinates (latitude/longitude) and also may include the components and functions of the components that make up each system. In addition, reference directory <b>138</b> may correlate a component to a specific hierarchical location within domain model <b>136</b> based on information such as the type of component, the model of the component, the function of the component, etc. In addition, an entry in reference directory <b>138</b> may correspond to a specific component of a system, with the specific component being assigned a unique ID or identifier. For example, a component may have an associated unique identifier in the form XXX-YYY-ZZZ ZZZ, where XXX may designate a division of the component (such as a city), YYY may designate a sub-division and zone of the component, and ZZZ ZZZ may be a numerical identifier describing the device type. For example, the numerical identifier may be a number designated by the manufacturer or by a system administrator.

<figref idref="DRAWINGS">FIG. 2</figref> is a flowchart, illustrating the operational steps of auto-updating program <b>134</b> in updating the domain model based on received messages from the components of system <b>110</b>, in accordance with an embodiment of the invention. In the exemplary embodiment, auto-updating program <b>134</b> monitors system <b>110</b> and receives status update messages from components <b>112</b><i>a</i>, <b>112</b><i>b</i>, and <b>112</b><i>c </i>of system <b>110</b> (step <b>202</b>). In the exemplary embodiment, the status update messages are received periodically from the components of system <b>110</b> (such as weekly, monthly, etc.), and may include information such as changes in function (such as a malfunction or offline component notification), notification that a connected component has been removed from system <b>110</b>, and the latitude and longitude coordinates of components in system <b>110</b>. For example, if auto-updating program <b>134</b> monitors a water system, and a new flow meter is added to the water system, auto-updating program <b>134</b> may receive a status update from the new flow meter indicating information about itself such as latitude/longitude, model number, specifications and/or subdivision zone that the new flow meter is located in. In addition, in one embodiment, status update messages may include a unique ID or identifier, as described above. Furthermore, in one embodiment, status update messages may include identification information which uniquely identifies the component and may also include necessary attributes of the component. In other embodiments, auto-updating program <b>134</b> may request status updates from the components of system <b>110</b> periodically and receive status updates from the components in response to the request. In further embodiments, for devices not capable of communicating status updates over a network (non-smart devices), a user of a computing device that is associated or a part of system <b>110</b> may input the status update information into the computing device via a user interface. The status update information input into the computing device may then be transmitted to server <b>130</b> periodically, or server <b>130</b> may request the status update information periodically.

Auto-updating program <b>134</b> then compares the status update messages received from components <b>112</b><i>a</i>, <b>112</b><i>b</i>, and <b>112</b><i>c </i>to domain model <b>136</b> to determine if there have been any changes to system <b>110</b> that require domain model <b>136</b> to be updated (decision <b>204</b>). For example, referring to the example of the water system described above, if a new water flow meter comes online in system <b>110</b>, auto-updating program receives status update messages periodically from the components of system <b>110</b>, including the new water flow meter. Auto-updating program <b>134</b> then compares the status update messages to domain model <b>136</b> and determines that the information provided in the status update message sent by the new flow meter does not match up with a component in domain model <b>136</b>. Auto-updating program <b>136</b> then determines that a new component has been added to system <b>110</b> and, therefore, a new component must also be added to domain model <b>136</b>. In other embodiments, where auto-updating program <b>134</b> receives status update messages containing a unique ID or identifier for the component, such as the new water flow meter described above, auto-updating program <b>134</b> utilizes reference directory <b>138</b> and determines the type of component and the corresponding location information of the component (such as division/sub-division/zone) associated with the unique ID or identifier. For example, as described above, the unique ID may be in the following format: XXX-YYY-ZZZ ZZZ, where XXX may designate a division of the component (such as a city), YYY may designate a sub-division and zone of the component, and ZZZ ZZZ may be a numerical identifier describing the device type. Auto-updating program <b>134</b> utilizes reference directory <b>138</b> to determine the type of component that corresponds with ZZZ ZZZ, the division that corresponds to XXX, and the sub-division/zone that corresponds to YYY.

If auto-updating program <b>134</b> determines that there are no changes to system <b>110</b> that require domain model <b>136</b> to be updated (decision <b>204</b>, “NO” branch), then auto-updating program <b>134</b> does not modify domain model <b>136</b>.

If auto-updating program <b>134</b> determines that there have been changes to system <b>110</b> that require domain model <b>136</b> to be updated (decision <b>204</b>, “YES” branch), auto-updating program <b>134</b> then determines the correct hierarchical locations of the components of system <b>110</b> (step <b>206</b>). In the exemplary embodiment, auto-updating program <b>134</b> compares the status update messages with reference directory <b>138</b> in order to determine the correct hierarchical locations of the components of system <b>110</b>. For example, once again referring to the example above, auto-updating program <b>134</b> utilizes the information in the status update messages received from the new flow meter to determine the hierarchical locations of the new flow meter. For instance, if reference directory <b>138</b> specifies a flow meter that is located within certain geographical coordinates (latitude/longitude) is located in zone <b>1</b> of city A, and the geographic information contained in the status update message received from the new flow meter specify a location that lies within the bounds of the certain geographical coordinates, auto-updating program <b>134</b> determines that the new flow meter belongs in a hierarchical location (such as hierarchical location one) of domain model <b>136</b> that corresponds to zone <b>1</b> of city A. In this example, the hierarchical location (hierarchical location one) may include several hierarchical categories. For example, hierarchical location may describe a first hierarchical category, such as a city, the new flow meter is located in, as well as a second hierarchical category, such as a zone within the city that the new flow meter is located in. Therefore, auto-updating program <b>134</b> may determine, based on the geographic location information for the new flow meter in the received status update message, that the new flow meter is in zone <b>1</b> (hierarchical location two) of Columbus, Ga. (hierarchical location one), and update domain model <b>136</b> accordingly. In addition, auto-updating program <b>134</b> may utilize reference directory <b>138</b> to determine that a component corresponds to a specific hierarchical location based on information such as the type of component, the model of the component, the function of the component, etc. In other embodiments, auto-updating program <b>134</b> may determine the hierarchical location of a component based on comparison of the status update messages of the component to a set of predefined rules that may be input via user interface <b>132</b> by a user or administrator of server <b>130</b>. Predefined rules may include information such as a list of unique IDs or identifiers which correspond to specific components and component locations. Therefore, auto-updating program <b>134</b> may compare the unique ID information from a status update message to the list contained in the predefined rules to determine a component's hierarchical location. In this other embodiment, the predefined rules may be updated periodically or on an as needed basis by a system administrator.

Auto-updating program <b>134</b> then updates domain model <b>136</b> based on the determined correct hierarchical locations of the components of system <b>110</b> (step <b>208</b>). In addition, auto-updating program <b>134</b> may determine the hierarchical location of one or more components of system <b>110</b> are incorrect based on comparison of a status update message regarding the component to reference directory <b>138</b>. Auto-updating program <b>134</b> then updates domain model <b>136</b> accordingly. For example, if the location information of a component (received in a status update message) does not match the geographic location corresponding to the hierarchy (defined in reference directory <b>138</b>) which the component belongs to, auto-updating program <b>134</b> may update domain model <b>136</b> by moving the component into the correct hierarchical location, as defined by reference directory <b>138</b>. In other words, if auto-updating program <b>134</b> receives a status update message from component <b>112</b><i>a </i>which indicates that the location of the component is zone <b>21</b> but domain model <b>136</b> shows the location of component <b>112</b><i>a </i>as zone <b>25</b>, auto-updating program <b>134</b> updates domain model <b>136</b> to reflect the location of component <b>112</b><i>a </i>(zone <b>21</b>) as described in the received status update message.

Once domain model <b>136</b> is updated, maintenance systems associated with system <b>110</b> will be able to refer to domain model so that system <b>110</b> can be maintained and managed in the most accurate fashion. For example, referring to the example above, with a new flow meter being added to a water system, several maintenance systems may be associated with system <b>110</b> (the water system) such as hydraulic systems for maintaining water pressure, advanced asset maintenance systems for keeping track of when a component of system <b>110</b> is due for maintenance, and a SCADA (supervisory control and data acquisition) system that acquires readings from flow meters, pressure gauges, and similar components. Each of these maintenance systems references domain model <b>136</b> in order to determine which components to monitor or gather information from. For example, if a new flow meter is added to a specific zone/location and domain model <b>136</b> is updated to reflect that, a SCADA system assigned to monitor and take readings from flow meters in that zone will be aware of the presence of the new flow meter by referring to the updated domain model <b>136</b>.

The foregoing description of various embodiments of the present invention has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed. Many modifications and variations are possible. Such modifications and variations that may be apparent to a person skilled in the art of the invention are intended to be included within the scope of the invention, as defined by the accompanying claims.

<figref idref="DRAWINGS">FIG. 3</figref> depicts a block diagram of respective components of server <b>130</b> in accordance with an illustrative embodiment of the present invention. It should be appreciated that <figref idref="DRAWINGS">FIG. 3</figref> provides only an illustration of one implementation and does not imply any limitations with regard to the environments in which different embodiments may be implemented. Many modifications to the depicted environment may be made.

Server <b>130</b> includes respective communications fabric <b>302</b>, which provides communications between computer processor(s) <b>304</b>, memory <b>306</b>, persistent storage <b>308</b>, communications unit <b>312</b>, and input/output (I/O) interface(s) <b>314</b>. Communications fabric <b>302</b> can be implemented with any architecture designed for passing data and/or control information between processors (such as microprocessors, communications and network processors, etc.), system memory, peripheral devices, and any other hardware components within a system. For example, communications fabric <b>302</b> can be implemented with one or more buses.

Memory <b>306</b> and persistent storage <b>308</b> are computer-readable storage media. In this embodiment, memory <b>306</b> includes random access memory (RAM) <b>316</b> and cache memory <b>318</b>. In general, memory <b>306</b> can include any suitable volatile or non-volatile computer-readable storage media.

The programs auto-updating <b>134</b>, user interface <b>132</b>, domain model <b>136</b>, and reference directory <b>138</b> stored in server <b>130</b> is stored in persistent storage <b>308</b> for execution and/or access by one or more of the respective computer processors <b>304</b> via one or more memories of memory <b>306</b>. In this embodiment, persistent storage <b>308</b> includes a magnetic hard disk drive. Alternatively, or in addition to a magnetic hard disk drive, persistent storage <b>308</b> can include a solid state hard drive, a semiconductor storage device, read-only memory (ROM), erasable programmable read-only memory (EPROM), flash memory, or any other computer-readable storage media that is capable of storing program instructions or digital information.

The media used by persistent storage <b>308</b> may also be removable. For example, a removable hard drive may be used for persistent storage <b>308</b>. Other examples include optical and magnetic disks, thumb drives, and smart cards that are inserted into a drive for transfer onto another computer-readable storage medium that is also part of persistent storage <b>308</b>.

Communications unit <b>312</b>, in these examples, provides for communications with other data processing systems or devices. In these examples, communications unit <b>312</b> includes one or more network interface cards. Communications unit <b>312</b> may provide communications through the use of either or both physical and wireless communications links. The programs auto-updating <b>134</b>, user interface <b>132</b>, domain model <b>136</b>, and reference directory <b>138</b> in server <b>130</b> may be downloaded to persistent storage <b>308</b> through communications unit <b>312</b>.

I/O interface(s) <b>314</b> allows for input and output of data with other devices that may be connected to server <b>130</b>. For example, I/O interface <b>314</b> may provide a connection to external devices <b>320</b> such as a keyboard, keypad, a touch screen, and/or some other suitable input device. External devices <b>320</b> can also include portable computer-readable storage media such as, for example, thumb drives, portable optical or magnetic disks, and memory cards. Software and data used to practice embodiments of the present invention, e.g., the programs auto-updating <b>134</b>, user interface <b>132</b>, domain model <b>136</b>, and reference directory <b>138</b> in server <b>130</b>, can be stored on such portable computer-readable storage media and can be loaded onto persistent storage <b>308</b> via I/O interface(s) <b>314</b>. I/O interface(s) <b>314</b> can also connect to a display <b>322</b>.

Display <b>322</b> provides a mechanism to display data to a user and may be, for example, a computer monitor.

The programs described herein are identified based upon the application for which they are implemented in a specific embodiment of the invention. However, it should be appreciated that any particular program nomenclature herein is used merely for convenience and, thus, the invention should not be limited to use solely in any specific application identified and/or implied by such nomenclature.

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 code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, 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 combinations of special purpose hardware and computer instructions.