Typically, individuals have several financial institution accounts, including, but not limited to, savings accounts, checking accounts, credit card accounts, and the like. While some of these accounts may be with the same financial institution, many times individuals have one account with one financial institution and another account with a different financial institution.
More often, individuals wish to transfer funds from one account to another account. For example, an individual may wish to transfer funds from a savings account into his/her checking account to make a large purchase. Because of recent online and mobile banking technologies, this transfer is usually easy for the individual to accomplish. This is especially true when the two accounts associated with the transfer are managed by the same financial institution. However, if the accounts are associated with multiple financial institutions, the transfer typically requires more individual interaction. Many times these transactions require an individual accessing both financial institutions' on-line or mobile banking applications to complete a transfer and/or physically conducting the transaction in a branch.
Embodiments of the present invention address the above needs and/or achieve other advantages by providing apparatuses (e.g., a system, computer program product and/or other devices) and methods for creating and managing a user financial institution account network, that allows a user to easily visualize, transact, and link multiple financial institution accounts (from multiple financial institutions) at a single location. As such, the invention provides a facilitated access and transaction capabilities to all user financial institution accounts consolidated into one reliable source.
Embodiments of the present invention provide a system for linking user financial accounts into one accessible location. As such, providing the user with a central node through which he/she can manage his/her entire financial ecosystem. Specifically, embodiments of the invention allow for enrolling in a mobile banking application managed by a first financial institution, determining user financial accounts associated with the first financial institution, determining user financial accounts associated with one or more other financial institutions, linking the financial accounts from the various financial institutions, allowing a user to view, access, review, transaction, and the like all user financial accounts from one location.
In some embodiments, the system may be associated with a financial institution managing a user's mobile banking application. As such, the system may allow the user to enroll in a mobile banking application via a user device. In this way, the user's financial accounts associated with the financial institution managing the user's mobile banking application may be viewable via that application. As such, the user may view account data, history, balances, and the like.
The system may then determine other financial accounts the user may have. These financial accounts may be with one or more other financial institutions that are not providing the user with the mobile banking application. The system may determine these financial accounts and communicate with the financial institutions that are managing the accounts. In this way, the system may obtain information associated with the financial accounts, such as account numbers, balances, and the like.
The system may then link the financial accounts from the various financial institutions onto one accessible location to provide the user with a financial account network. In some embodiments, the system may provide the accessible location via an application displayable on a user device.
The system allows a user to view, access, review, transaction, transfer funds, and the like between the linked financial accounts. For example, if a user would like to transfer funds from a checking account he/she has with Bank 1 to a savings account he/she has with Bank 2, the user may access the application and direct funds from the checking account to the savings account. In this way, by accessing a single application a user may be able to manipulate funds across several different accounts managed by one or more financial institutions. Furthermore, the user may be able to manage all of the accounts from the application. In some embodiments, the application may be interactive, such that the user may be able to swipe, move, icon, scroll, or the like between the accounts and/or financial institutions associated therewith in order to manage each of the various financial accounts linked by the system.
Furthermore, the system allows a user to use any one of the linked financial accounts to transaction with an outside vendor if necessary. As such, the system may link to one or more of the user's financial accounts to allow a user to transact using the account.
Embodiments of the invention relate to systems, methods, and computer program products for a link between one or more financial accounts, the invention comprising: receive an indication that a user accesses a first one or more financial accounts electronically, wherein accessing the first one or more financial accounts electronically includes accessing the first one or more financial accounts via online or mobile accessing capabilities, wherein the first one or more financial accounts are managed by a first financial institution; receive information of a second one or more financial accounts associated with the user, wherein the second one or more financial accounts are managed by one or more other financial institutions; determine, based on received information, an account type and the one or more other financial institutions managing the second one or more financial accounts; communicate with the first financial institution and the one or more other financial institutions; link the first one or more financial accounts with the second one or more financial accounts together into a single application; allow for transacting between the linked first one or more financial accounts and the second one or more financial accounts; and provide viewable indication of the transaction and effects of the transaction on the first one or more financial accounts and the second one or more financial accounts via the single application.
In some embodiments, determining an account type and the one or more other financial institutions managing the second one or more financial accounts comprises recognizing user input of financial accounts information associated with the second one or more financial accounts, wherein financial account information includes one or more of an account number, routing number, or account identification number. In other embodiments, determining an account type and the one or more other financial institutions managing the second one or more financial accounts comprises recognizing the second one or more financial accounts when a statement associated with the second one or more financial accounts is sent to the user, wherein the one or more other financial institutions sends the statement to the user electronically. In yet other embodiments, determining an account type and the one or more other financial institutions managing the second one or more financial accounts comprises recognizing a captured image of an article comprising financial accounts information associated with the second one or more financial accounts, wherein the captured image is captured via an image capture device, such as a camera, wherein financial account information includes one or more of an account number, routing number, or account identification number.
In some embodiments, communicating with the first financial institution and the one or more other financial institutions further comprises communicating with the first financial institution and the one or more other financial institutions to receive authorization to transact using the first one or more financial accounts and the second one or more financial accounts associated with the user.
In some embodiments, the invention is further configured to allow for tracking between the first one or more financial accounts and the second one or more financial accounts associated with the user, such that the tracking allows for transferring of funds across the first one or more financial accounts and the second one or more financial accounts.
In some embodiments, the invention is further configured to allow transacting with third party entities using the linked first one or more financial accounts and the second one or more financial accounts using a single application, wherein the transaction occurs independent of managing financial institution.
In some embodiments, providing viewable indication of the transaction and effects of the transaction on the first one or more financial accounts and the second one or more financial accounts via the single application further comprises displaying financial account information such as account balance associated with each of the first one or more financial accounts and the second one or more financial accounts on single viewable application.
In some embodiments, the invention is further configured to allow for visual overlaid circles including a managing financial institution in one circle and a one or more financial accounts from the managing financial institution overlaid in a second or more circles.
In some embodiments, the invention is further configured to notify the user of any changes in the linked first one or more financial accounts and the second one or more financial accounts, wherein changes include account balance changes or transactions occurring using the linked first one or more financial accounts or the second one or more financial accounts.
In some embodiments, the invention is further configured to monitor the linked first one or more financial accounts and the second one or more financial accounts statement history for the user.
The features, functions, and advantages that have been discussed may be achieved independently in various embodiments of the present invention or may be combined with yet other embodiments, further details of which can be seen with reference to the following description and drawings.
Having thus described embodiments of the invention in general terms, reference will now be made to the accompanying drawings, wherein:
Embodiments of the present invention will now be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all, embodiments of the invention are shown. Indeed, the invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. Like numbers refer to elements throughout. Where possible, any terms expressed in the singular form herein are meant to also include the plural form and vice versa, unless explicitly stated otherwise. A “financial account” or “account” as used herein may refer to any checking, savings, money market, certified deposit, credit card, line of credit, debit account, and/or the like that a user may have with a financial institution or similar entity. Furthermore, a “vendor” as used herein may refer to any third party that a user may have transacted with for products, services, or the like. In this way, a vendor may be a merchant, service provider, contractor, business, individual or entity that may have transacted with the user.
Some portions of this disclosure are written in terms of a financial institution's unique position with respect to payment account and payment device providers. As such, a financial institution may be able to utilize its unique position to facilitate some of the functionality for the financial account networking program to operate.
Next, as illustrated in block 104, the system may determine user financial accounts from the financial institution to add to the user's application. In this way, the user may have one or more accounts, such as a checking account, savings account, credit card, debit account, or the like with the financial institution. Once those accounts are determined, they may be added to the application.
As illustrated in block 106, after the user has enrolled and has his/her accounts from the financial institution on a mobile banking application, the system may determine user financial accounts from one or more other financial institutions not associated with the application. In this way, if the user has a mobile banking application with Bank 1, the system may also determine accounts the user has with Bank 2, Bank 3, Bank 4, and the like.
Next, as illustrated in block 108, the system may link the user financial accounts associated with both the financial institution associated with the mobile banking application and the one or more other financial institutions. In this way, all of the user financial accounts, irrespective of what financial institution the financial account is managed by, may be linked together.
Next, because all financial accounts of a user are linked, the system may provide information associated with all of the user's linked financial accounts, as illustrated in block 110. In this way, the user may be able to view, in one location, all information associated with each of the user's financial accounts. The information includes, but is not limited to, account numbers, account balances, account history, and the like.
Finally, as illustrated in block 112, the system allows for transactions by or between the financial accounts within a single application, independent of the financial institution associated with the financial account. In some embodiments, the system may allow for transactions via an interactive interface which may include sliding, texting, voice activation, swiping, and the like. For example, a user may be able to transfer funds between a checking account managed by Bank 1 and a savings account managed by Bank 2. In this way, the financial account networking system allows for viewing and transferring funds between financial accounts via a single location.
The network 201 may be a global area network (GAN), such as the Internet, a wide area network (WAN), a local area network (LAN), or any other type of network or combination of networks. The network 201 may provide for wireline, wireless, or a combination wireline and wireless communication between devices on the network.
In some embodiments, the user 202 is an individual that may have one or more financial accounts with one or more financial institutions. As such, in some embodiments, the user 202 may have made one or more transaction accounts, such as a savings account, checking account, certificate of deposit, stock, or the like. The user 202 may also have one or more of a credit card account, debit card account, or the like with a financial institution. Furthermore, in some embodiments, the user 202 may be an entity or a person, employee, agent, independent contractor, or the like acting on behalf of the entity to us an entity associated financial account.
As illustrated in
The processing device 248 is operatively coupled to the communication device 246 and the memory device 250. The processing device 248 uses the communication device 246 to communicate with the network 201 and other devices on the network 201, such as, but not limited to the other financial institution server 210 and the user device 204. As such, the communication device 246 generally comprises a modem, server, or other device for communicating with other devices on the network 201.
As further illustrated in
In the embodiments illustrated in
The financial account network application 258 may determine user financial accounts. In some embodiments, the user financial accounts may be from the financial institution providing the financial account networking program. In some embodiments, the financial institution accounts may be from one or more other financial institutions providing financial accounts. In some embodiments, the financial account network application 258 may determine user financial accounts automatically. In other embodiments, the financial account network application 258 may determine user financial accounts based on user input of information associated with the financial account, such as financial institution associated with the account, account number, routing number, and/or the like.
In some embodiments, the user financial accounts may be from the financial institution providing the financial account networking program. As such, the user 202 may bank with the financial institution associated with the financial institution server 208. In this way, the financial account network application 258 may already have access to the financial account information for the user financial account associated with the financial institution associated with the financial institution server 208. In some embodiments, the user financial accounts may be from one or more other financial institutions, wherein the other financial institutions are not providing the financial account networking program. In this way, the system may, in some embodiments, receive financial account information from other financial institutions automatically, via other financial institution servers 210 via a network 201. In this way, the financial account network application 258 may communicate using the communication device 246 with other systems on the network 201, such as the other financial institution servers 210 to access user financial accounts associated with the user 202. In other embodiments, the user 202 may manually input, via his/her user device 204, the financial account information. In this way, the financial account network application 258 may receive financial accounts directly from other financial institutions, from the user 202, or from the financial institution providing the financial account networking program.
Once the user's financial accounts are determined, the financial account network application 258 may be able to track and communicate with the financial institution providing the financial account. In this way, the financial account network application 258 may be able to access the information associated with the financial account and be able to provide the user 202 with real-time information associated with the financial account.
Next, the financial account network application 258 may link user financial accounts. In this way, the financial account network application 258 may link financial accounts associated with the financial institution providing the financial account networking program and/or financial accounts associated with other financial institutions. This linkage allows the financial account network application 258 to link all user 202 financial accounts into one location, such that a user 202 may be able to visualize information associated with each of his/her financial accounts at one time via his/her user device 204. The linking further allows the user 202 to transfer funds across accounts using the linkage.
The financial account network application 258, once linking the financial accounts, the financial account network application 258 may be able to provide information associated with each of the user financial accounts. Because of the linkage, the financial account network application 258 through the communication device 246 may communicate via a network 201 to the other financial institution servers 210 in order to receive, in real-time, information associated with the user financial accounts. The information includes, but is not limited to, account history, account balance, and/or the like. In this way, the system may be able to provide the user 202 with a visual representation of the user's accounts in one holistic view for easy monitoring and account manipulation.
Next, the financial account network application 258 may allow for transactions between the financial accounts on the financial account networking system and/or allow for transactions using the financial accounts. In some embodiments, the financial account network application 258 may allow for transactions between the financial accounts. In this way, the financial account network application 258 may link the user's financial accounts and using this linkage allow for transactions between the financial accounts. In this way, the financial account network application 258 may allow a user to track a linkage to send/receive funds at various one or more financial accounts. For example, a user 202 may wish to move funds from a checking account at Bank 1 to a savings account at Bank 2. As such, the user 202 may track the linkage between Bank 1 and Bank 2 created by the financial account networking program to make the transfer. In this way, the user 202 may use an interface on his/her user device 204 to track or selection the different accounts to transact between. Importantly, the accounts may be displayed to the user 202 on one screen, such that the user 202 may be able to transaction between some or all of his/her financial accounts using a single screen associated with the interface, as further illustrated in the interfaces of
Furthermore, the financial account network application 258, in other embodiments, may allow for the user 202 to transact using any of the financial accounts with another entity. In this way, because of the linkage, the financial account network application 258 is able to link a user 202 via the interface, to any one of the financial accounts associated with the user 202. In this way, a user 202 may be able to select a financial account using the financial account networking program and be able to use that financial account to transact with an outside entity. For example, a user 202 may wish to use his/her credit card account from Bank 3 to provide payment for a bill. The user 202 may select the credit card account using his/her financial account networking program and direct a payment to the entity associated with the bill.
Finally, the financial account network application 258 may allow a user 202 to confirm a transaction between or with user financial accounts on the financial account network. In this way, the financial account network application 258 may allow a user 202 to select and make a transaction using an interface associated with the financial account network program, and subsequently confirm the transaction via his/her user device 204. As such, the financial account network application 258 may communicate the transaction to the financial institution server managing the financial account, via either other financial institution servers 210 or the financial institution server 208 over the network 201. The user 202 may be provided the confirmation by the financial account network application 258 using the communication device 246 through the network 201 to the user device 204.
As further illustrated in
In some embodiments, the user application 222 allows a user 202 to utilize his/her user device 204 as a financial account networking interface to access, provide input, receive information associated with financial accounts, and conduct transactions by/between the user's financial accounts.
The user application 222 may allow a user 202 to utilize his/her user device 204 to access user financial accounts from one or more financial institutions. As such, the user application 222 may communicate using the network 201 with the financial institution server 208 to access the user's financial account networking program. In this way, the user application 222 may authorize the user device 204 as being associated with the user 202 such that the user device 204 may be able to securely access the user's financial account networking program.
The user application 222 may also allow a user 202 to add information to his/her user financial account networking program. In this way, the user 202 may be able to input financial accounts, financial institutions associated with financial accounts, and/or the like. The user 202 may be able to input this data via text, voice, image recognition, or the like. The user device 204 may communicate the information associated with the added data via the communication device 212 through a network 201 to the financial institution server 208.
The user application 222 may also receive information associated with financial accounts via the financial account networking program. In this way, the user 202 may be able to monitor all of his/her financial accounts, balances, transfers, history, and the like associated with the user financial accounts on the user's financial account networking program.
Finally, the user application 222 allows the user 202 to utilize the user device 204 to conduct transactions by/between the user's financial accounts. In this way, the user 202 may use his/her user device 204 to transfer funds between financial accounts and transact with other entities utilizing the same interface associated with the financial account networking program.
Furthermore, the other financial institution server 210 communicate with the financial institution server 208 to send real-time updates regarding financial accounts, such that the system may provide these updates to the user 202 via his/her financial account networking program.
It is understood that the servers, systems, and devices described herein illustrate one embodiment of the invention. It is further understood that one or more of the servers, systems, and devices can be combined in other embodiments and still function in the same or similar way as the embodiments described herein.
There are three main ways of determining financial accounts 302 for a user 202 financial account networking program. As illustrated in block 304, one way of receiving user financial accounts for the user's financial account networking program is to receive user input, such as account number, routing number, financial institution associated therewith, and/or the like. In this way, the system may receive user 202 inputted data from a user device 204 or the like in order to populate financial accounts on the user financial account networking program. The user 202 inputted financial accounts may be from any of one or more financial institutions.
As illustrated in block 306, one way to determine financial accounts for the financial account networking program is to recognize financial institution statements sent to a user 202. In some embodiments, the statements may be recognized because they are sent electronically to the user device 204 over a network 201 in which the system may monitor and recognize the statements. This electronic sending may be via email, text message, or other electronic means of transmitting the statement. In other embodiments, the user 202 may request the financial institution send the statements directly to the system. In this way, the system may recognize the statement as being associated with the user 202 and link the financial account associated with the statement to the user's financial account networking program. For example, the system may recognize a financial statement sent to a user 202 via email. Once identified, the system may determine the statement originating financial institution, the financial account number, and the like, and automatically retrieve the financial account from the user's email and add it to the user's financial account networking program.
As illustrated in block 308 another way to determine financial accounts associated with a user 202 is by recognizing captured images of information associated with a financial account. This information may include a statement, check, deposit slip, receipt, credit card, debit card, and/or any other image that may comprise information associated with a financial account, such as an account number or the like. The captured images may be captured by a user 202 using an image capture device, such as a camera, user device 204, or the like. In other embodiments, the user 202 may be using a text capture device, such as a scanner or facsimile. Once the system receives a captured image or text associated with a financial account, the system may recognize the financial institution, the financial account number, and the like. The system may then add the determined information to the user's financial account networking program.
In all of the ways to determine financial accounts for a user 202 illustrated in
Next, as illustrated in block 504, the system may determine the financial institution associated with the financial account received. This includes determining the financial institution, financial institution contact information, and information associated with the financial account, such as, but not limited to, type of account, balance, transaction history, transaction reoccurrences, and the like.
After the system has determined the financial institution associated with a received financial account, the system may, as illustrated in block 506, communication with the financial institution managing/providing the received financial account. In some embodiments, this step of contacting the financial institution directly may need to be authorized by the user 202 prior to the system reaching out to the financial institution. In other embodiments, the system may contact the financial institution automatically to create a link for the financial account associated with the financial institution and/or receive real-time information associated with the financial account.
Next, as illustrated in block 508, the system may link the user financial accounts from various financial institutions into a financial account networking program. In this way, the system may allow for the linking of financial accounts from different financial institutions, such as Bank 1, Bank 2, Bank 3, and the like into one location, such that account information for all financial accounts may be viewable in that location. Furthermore, because of the linkage, the system allows a user to track the linkage to transact between financial accounts, such as transfer funds and/or the like.
Next, as illustrated in block 510, once the system has linked the financial accounts from the various financial institutions, the system may provide financial account information for all accounts associated with the user 202. In this way, because of the linkage, the system may provide the user 202 with information associated with all of his/her financial accounts via the financial account networking program. As such, a user 202 may be able to view each of his/her financial account in one location for easy balance review, transaction review, transacting, account manipulation, or the like.
Next, as illustrated in block 512 the system may allow for transactions with or between all linked financial accounts independent of the financial institution associated with the account. In this way, using the linkage, the system may allow a user 202 to track funds between each of the one or more financial accounts now linked on the user's financial account networking program.
As illustrated in section 601, the transactions by or between the linked financial accounts include, but are not limited to transferring funds between accounts within the financial account networking program, as illustrated in block 604. In block 606 the system allows for the user 202 to make payments via the accounts on the financial account networking program. In some embodiments, the system allows for payments from one account to another account on the financial account networking program. In other embodiments, the system allows a user 202 to make a payment using an account on the financial account networking program to tender payment to an entity not associated with the program. As illustrated in block 605, the system is set up such that it may be able to perform any other transaction such as those that are typically done via online or mobile banking. As illustrated in block 608, the system may also allow the user 202 to set up schedules between accounts. These schedules may include, but are not limited to, payment schedules, transfer schedules, or the like. As such, the user 202 may be able to set a time or date for a type of transaction to occur. The system may complete the transaction based on the set time or date without any further user 202 input. Finally, the system, as illustrated in block 610 may communicate with the financial institution managing the financial account. In this way, the system may receive real-time data from the financial institution associated with the financial accounts. As such, the user 202 may be able to view all user financial accounts associated with all financial institutions in a single location.
Next, as illustrated in block 706 of
Once the user 202 has enrolled in a mobile or online banking application and provided information associated with his/her financial accounts, the system may communicate with the other financial institutions associated with the user's accounts. As such, the system may be able to provide real-time data associated with the financial accounts independent of what financial institution is providing the account. The user 202 may now, as illustrated in decision block 710, decide to access his/her mobile or online application. If the user 202 does not decide to access his/her application, then the process 700 terminates. If the user 202 does access his/her application then the system may display information associated with all of the user's financial accounts, including accounts from any financial institution, within the user's financial account networking program, as illustrated in block 712.
Referring back to
As will be appreciated by one of ordinary skill in the art, the present invention may be embodied as an apparatus (including, for example, a system, a machine, a device, a computer program product, and/or the like), as a method (including, for example, a business process, a computer-implemented process, and/or the like), or as any combination of the foregoing. Accordingly, embodiments of the present invention may take the form of an entirely software embodiment (including firmware, resident software, micro-code, or the like), an entirely hardware embodiment, or an embodiment combining software and hardware aspects that may generally be referred to herein as a “system.” Furthermore, embodiments of the present invention may take the form of a computer program product that includes a computer-readable storage medium having computer-executable program code portions stored therein. As used herein, a processor may be “configured to” perform a certain function in a verity of ways, including, for example, by having one or more general-purpose circuits perform the functions by executing one or more computer-executable program code portions embodied in a computer-readable medium, and/or having one or more application-specific circuits perform the function.
It will be understood that any suitable computer-readable medium may be utilized. The computer-readable medium may include, but is not limited to, a non-transitory computer-readable medium, such as a tangible electronic, magnetic, optical, infrared, electromagnetic, and/or semiconductor system, apparatus, and/or device. For example, in some embodiments, the non-transitory computer-readable medium includes a tangible medium such as 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 compact disc read-only memory (CD-ROM), and/or some other tangible optical and/or magnetic storage device. In other embodiments of the present invention, however, the computer-readable medium may be transitory, such as a propagation signal including computer-executable program code portions embodied therein.
It will also be understood that one or more computer-executable program code portions for carrying out operations of the present invention may include object-oriented, scripted, and/or unscripted programming languages, such as, for example, Java, Perl, Smalltalk, C++, SAS, SQL, Python, Objective C, and/or the like. In some embodiments, the one or more computer-executable program code portions for carrying out operations of embodiments of the present invention are written in conventional procedural programming languages, such as the “C” programming languages and/or similar programming languages. The computer program code may alternatively or additionally be written in one or more multi-paradigm programming languages, such as, for example, F#.
It will further be understood that some embodiments of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of systems, methods, and/or computer program products. It will be understood that each block included in the flowchart illustrations and/or block diagrams, and combinations of blocks included in the flowchart illustrations and/or block diagrams, may be implemented by one or more computer-executable program code portions. These one or more computer-executable program code portions may be provided to a processor of a general purpose computer, special purpose computer, and/or some other programmable data processing apparatus in order to produce a particular machine, such that the one or more computer-executable program code portions, which execute via the processor of the computer and/or other programmable data processing apparatus, create mechanisms for implementing the steps and/or functions represented by the flowchart(s) and/or block diagram block(s).
It will also be understood that the one or more computer-executable program code portions may be stored in a transitory or non-transitory computer-readable medium (e.g., a memory, or the like) that can direct a computer and/or other programmable data processing apparatus to function in a particular manner, such that the computer-executable program code portions stored in the computer-readable medium produce an article of manufacture including instruction mechanisms which implement the steps and/or functions specified in the flowchart(s) and/or block diagram block(s).
The one or more computer-executable program code portions may also be loaded onto a computer and/or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer and/or other programmable apparatus. In some embodiments, this produces a computer-implemented process such that the one or more computer-executable program code portions which execute on the computer and/or other programmable apparatus provide operational steps to implement the steps specified in the flowchart(s) and/or the functions specified in the block diagram block(s). Alternatively, computer-implemented steps may be combined with operator and/or human-implemented steps in order to carry out an embodiment of the present invention.
While certain exemplary embodiments have been described and shown in the accompanying drawings, it is to be understood that such embodiments are merely illustrative of, and not restrictive on, the broad invention, and that this invention not be limited to the specific constructions and arrangements shown and described, since various other changes, combinations, omissions, modifications and substitutions, in addition to those set forth in the above paragraphs, are possible. Those skilled in the art will appreciate that various adaptations and modifications of the just described embodiments can be configured without departing from the scope and spirit of the invention. Therefore, it is to be understood that, within the scope of the appended claims, the invention may be practiced other than as specifically described herein.