Credit utilization tracking and reporting

[0001] This application claims the benefit of priority under 35 U.S.C. § 119(e) of U.S. Provisional Application No. 61/785,946, filed Mar. 14, 2013, the entirety of which is hereby incorporated herein by reference.

[0002] A portion of disclosure of this patent document includes material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyrights whatsoever.

[0003] Credit utilization is generally an amount of credit used by a consumer compared to a total amount of credit available to the consumer.

[0004] Generally described, aspects of the present disclosure relate to a computer system which includes one or more processors and a tangible storage device storing a credit utilization tracking module configured for execution by the one or more computer processors. For each of a plurality of credit lines associated with a consumer, the credit utilization tracking module may store credit utilization at multiple points in time, and the credit utilization at each point in time may indicate a relationship between a total credit limit and an available credit amount for respective credit lines at respective points in time. The credit utilization tracking module may determine one or more thresholds for respective credit lines. The thresholds may indicate levels at which a credit score of the consumer may be affected by credit utilization above the respective thresholds. The levels at which a credit score of the consumer may be affected may be determined based on information accessed from one or more credit bureaus and one or more credit score formulae used by the one or more credit bureaus. For each of the plurality of credit lines, the credit utilization tracking module may, in response to determining that a most current credit utilization for the credit line exceeds a high threshold of the one or more thresholds, provide a notification to the consumer. The notification to the consumer may suggest lowering credit utilization for the credit line, switching to a credit line with lower credit utilization, or moving debt from the credit line exceeding the high threshold to one or more other credit lines.

[0005] As discussed herein, aspects of the present disclosure include a computer system which includes one or more computer processors configured to execute instructions in order to cause the computer to perform operations. The operations include, for each of a plurality of credit lines associated with a consumer, storing credit utilization (and/or data that is usable to determine credit utilization) at multiple points in time. The credit utilization at each point in time indicates a relationship between a total credit limit and an available credit amount for respective credit liens at respective points in time. The operations may include determining one or more thresholds for respective credit lines, the thresholds indicate levels at which a credit score of the consumer may be affected by credit utilization above the respective thresholds. The operations may also include for each of the plurality of credit lines, in response to determining that a most current credit utilization for the credit line exceeds a high threshold of the one or more thresholds, providing a notification to the consumer.

[0006] As discussed herein, aspects of the present disclosure include a non-transitory computer-readable storage medium, which includes computer-executable instructions. The computer-executable instructions may direct a computing system to store credit utilization at multiple points in time for each of a plurality of credit lines associated with a consumer. The credit utilization at each point in time may indicate a relationship between a total credit limit and an available credit amount for respective credit lines at respective points in time. The computer executable instructions may direct a computing system to determine one or more thresholds for respective credit lines. The thresholds may indicate levels at which a credit score of the consumer may be affected by credit utilization above the respective thresholds. The levels at which a credit score of the consumer may be affected may be determined based on information accessed from one or more credit bureaus and one or more credit score formulae used by the one or more credit bureaus. For each of the plurality of credit lines, the computer executable instructions may, in response to determining that a most current credit utilization for the credit line exceeds a high threshold of the one or more thresholds, provide a notification to the consumer suggesting the consumer to lower credit utilization for the credit line, switching to a credit line with lower credit utilization, or move available credit from other credit lines to the credit line exceeding the high threshold.

[0013] Various embodiments of systems, methods, processes, and data structures will now be described with reference to the drawings. Variations to the systems, methods, processes, and data structures which represent other embodiments will also be described. Certain aspects, advantages, and novel features of the systems, methods, processes, and data structures are described herein. It is to be understood that not necessarily all such advantages may be achieved in accordance with any particular embodiment. Accordingly, the systems, methods, processes, and/or data structures may be embodied or carried out in a manner that achieves one advantage or group of advantages as taught herein without necessarily achieving other advantages as may be taught or suggested herein.

[0014] Credit utilization may be determined based on all the credit lines of a consumer. For example, if a consumer has a total of four credit lines, the consumer's credit utilization may be determined as the total amount of credit used across all the four credit lines and the total amount of credit available across all four credit lines. Credit utilization may be tracked on a month-to-month basis, such as because most creditors report credit data to credit bureaus on a monthly basis.

[0015] Disclosed herein are systems and methods for tracking credit utilization on a per-credit-line basis, so that consumers can easily recognize potential impact to the consumer's credit score of high utilization of credit on a single credit line. Such credit utilization tracking may be used to make useful suggestions to consumers as to how to improve credit scores effectively.

Example Credit Utilization Tracking Environment and Data Flow

[0016] FIG. 1 is a flow diagram 100 illustrating one embodiment a credit utilization tracking system 130 in communication with a credit bureau 110 and a consumer 120. Credit Bureau 110 may include credit bureaus and other credit counseling, credit repairing, and/or credit monitoring services and entities that help consumers keep track of credit utilization. Although the word “consumer” is used, consumer 120 may include individual consumers, groups of individuals (e.g., married couple, family, group of friends, etc.) small businesses, large business entities, and so forth.

[0017] In the embodiment of FIG. 1, the credit bureau 110 may send credit data 140 to a credit utilization tracking system 130 through a network 150. Credit data 140 may include information that is usable to calculate utilization of various financial instruments, such as credit cards, mortgage loans, car loans, lines of credit from financial lenders, home equity line of credit, and so forth. Credit data 140 may also include payment terms, payment history information, interest rates, delinquency records, and so forth. The network 150 may comprise one or more of a LAN, WAN, and/or the Internet. The network 150 communicates with various modules, computing devices and/or other electronic devices via wired or wireless communication links, and/or combination of wired and wireless communication links.

[0018] Credit utilization tracking system 130 may receive the credit data 140 from a credit bureau 110, and process the received information using the utilization tracking module 132. In some embodiments, the utilization tracking module 132 may parse the received credit data into a format that may be processed by the credit utilization tracking system 130. Furthermore, the utilization tracking module 132 may calculate credit utilization for a particular credit line based on the received credit data.

[0019] In some embodiments, the utilization tracking module 132 calculates a credit utilization ratio for a particular credit line using a formula such as: credit utilization ratio=Amount of Credit Used/Total Amount of Available. Thus, as the amount of credit used changes from day to day (for most consumers), the credit utilization for a particular credit card (or other credit line) also changes from day to day.

[0020] A credit report, for example, may include the amount of credit used and a total amount of credit available for respective credit lines of a consumer, such that credit utilization may be calculated using the information in a credit report. Credit issuers typically report account data for any particular consumer once a month (or other predetermined time period). Thus, credit utilization for a particular consumer on a particular credit line may be updated about once a month based on credit data of the consumer in the consumer's credit data. If credit data is obtained directly from a credit issuer, credit utilization for such a credit line may be updated on a daily basis, or even more frequently on a transaction basis, such that after each transaction on the credit line and updated credit utilization may be calculated. For certain embodiments discussed herein, credit utilization is calculated on a monthly basis, such as based on information that is updated monthly in consumer credit data. However, in other embodiments credit utilization may be calculated on any other frequency, and/or based on data from other sources (e.g. instead of, or in addition to, credit data).

[0021] In other embodiments, a different formula can be used to calculated credit utilization ratio that is different from the formula above. For example, credit utilization may be calculated in a way that gives more weight to credit used on cash advances versus otherwise.

[0022] Credit utilization ratio may be represented as a percentage between 0% and 100%, a number between 0 and 1, on an academic scale from A-F, in the format of a bar chart, a pie chart, or in any other manner.

[0023] The utilization tracking module 132 may calculate a credit utilization ratio for an individual credit line based on historical credit information in data store 138 at multiple points in time. For example, the utilization tracking system 130 may have tracked a particular consumer's credit line utilization data for 5 years on a daily, weekly, bi-weekly, monthly, and/or yearly basis. Thus, for a particular credit line the utilization tracking module 132 may have stored (and/or may calculated based on stored historical credit data) the consumer's credit utilization ratio for any day during the 5-year period using the total amount of credit available of a particular day and the total amount of available credit on the same day.

[0024] Depending on the embodiment, the data store 138 may store credit line utilization data every day, every 2 weeks, every month, and/or other period. In some embodiments, credit utilization data 145 is not stored by the data store 138, but rather, the data store 138 stores the credit line account information that is usable to calculate the consumers credit utilization of any previous point in time.

[0025] In some cases, credit utilization data 145 is reported by a credit bureau on a monthly basis, but more fine-grained data may be available in the format of a statement and/or a credit report. In some other cases, credit utilization data 145 is reported bi-weekly. The credit utilization system may extract credit data 140 from statements, and/or credit reports sent from credit bureau 110 via network 150.

[0026] In some embodiments, credit data 140 regarding a consumer may be non-consecutive, such as when credit data 140 is missing for a particular period of time. The utilization tracking module 132 may still use a formula, including the formula discussed above, to calculate a credit utilization ratio using the available credit data regarding a particular credit line. However, the utilization tracking module 132 may not be able to calculate credit utilization ratio regarding a particular credit line for days that credit data about the particular credit line is not available.

[0027] In some embodiments, the utilization tracking module 132 calculates historical credit utilization ratio for a particular credit line of a business and/or an organization at multiple points in time. The business and/or organization's credit data, such as amount of credit used and total amount of available credit for a particular credit line, may be stored in data store 138. In some embodiments, the business and/or organization's credit data is not stored at the data store 138, but rather, the data store 138 stores the credit line account information that is usable to calculate the business and/or organization's credit utilization of any previous point in time.

[0028] In one embodiment, the user interface module 134 generates and presents user interfaces to consumers. The user interface module 134 may also enable features on user interfaces so that consumers may customize the user interfaces presented to them. Details regarding the generation, presentation, and customization of user interfaces are discussed further below. In conjunction with the reporting and alert module 136, the user interface module may also allow consumers to set their own credit utilization thresholds and configure when they wish to receive alerts and/or messages regarding credit utilization.

[0029] The reporting and alert module 136 may generate reports, messages, and/or alerts that may be sent to a consumer. The reports, messages, and/or alerts may be presented in the format of a webpage, a text message, an e-mail, and/or a mobile application, and so forth. The generation of the reports, messages, and/or alerts may be triggered when a consumer's credit utilization ratio for a particular credit card, for example, exceeds a particular credit utilization threshold, as discussed further below.

[0030] In some embodiments, the data store 138 may be implemented using a relational database, such as Sybase, Oracle, CodeBase and Microsoft® SQL Server as well as other types of databases such as, for example, a flat file database, an entity-relationship database, and object-oriented database, a record-based database, and/or an unstructured database.

[0031] FIG. 2 is a block diagram illustrating example components of one embodiment of the credit utilization tracking system 130. The computing system 130 may be used to implement systems and methods described in this disclosure.

[0032] The computing system 130 includes, for example, a computer that may be IBM, Macintosh, or Linux/Unix compatible or a server or workstation. In one embodiment, the computing system 130 comprises a server, desktop computer, a tablet computer, or laptop computer, for example. In one embodiment, the exemplary computing system 130 includes one or more central processing units (“CPUs”) 204, which may each include a conventional or proprietary microprocessor. The computing system 130 further includes one or more memory 206, such as random access memory (“RAM”) for temporary storage of information, one or more read only memory (“ROM”) for permanent storage of information, and one or more mass storage device 201, such as a hard drive, diskette, solid state drive, or optical media storage device. Typically, the modules of the computing system 130 are connected to the computer using a standard based bus system 208. In different embodiments, the standard based bus system could be implemented in Peripheral Component Interconnect (“PCP”), Microchannel, Small Computer System Interface (“SCSI”), Industrial Standard Architecture (“ISA”) and Extended ISA (“EISA”) architectures, for example. In addition, the functionality provided for in the components and modules of computing system 130 may be combined into fewer components and modules or further separated into additional components and modules.

[0033] The computing system 130 is generally controlled and coordinated by operating system software, such as Windows XP, Windows Vista, Windows 7, Windows 8, Windows Server, Unix, Linux, SunOS, Solaris, or other compatible operating systems. In Macintosh systems, the operating system may be any available operating system, such as MAC OS X. In other embodiments, the computing system 130 may be controlled by a proprietary operating system. Conventional operating systems control and schedule computer processes for execution, perform memory management, provide file system, networking, I/O services, and provide a user interface, such as a graphical user interface (“GUI”), among other things.

[0034] The exemplary computing system 130 may include one or more commonly available input/output (I/O) devices and interfaces 205, such as a keyboard, mouse, touchpad, and printer. In one embodiment, the I/O devices and interfaces 205 include one or more display devices, such as a monitor, that allows the visual presentation of data to a user. More particularly, a display device provides for the presentation of GUIs, application software data, and multimedia presentations, for example. The computing system 130 may also include one or more multimedia devices, such as speakers, video cards, graphics accelerators, and microphones, for example.

[0035] In the embodiment of FIG. 4, the I/O devices and interfaces 205 provide a communication interface to various external devices. In the embodiment of FIG. 2, the computing system 130 also includes a utilization tracking module 132 that may be stored in the mass storage device 201 as executable software codes that are executed by the CPU 204. This module may include, by way of example, components, such as software components, object-oriented software components, class components and task components, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables. In the embodiment shown in FIG. 2, the computing system 130 is also configured to execute the reporting and alert module 136 and user interface module 134 in order to implement functionality described elsewhere herein. For example, the processing module may perform methods described with reference to any of various modules described above with reference to the information management system 110 and/or the credit report generation system 130, depending on the embodiment.

[0036] In general, the word “module,” as used herein, refers to logic embodied in hardware or firmware, or to a collection of software instructions, possibly having entry and exit points, written in a programming language, such as, for example, Java, Lua, C or C++. A software module may be compiled and linked into an executable program, installed in a dynamic link library, or may be written in an interpreted programming language such as, for example, BASIC, Perl, or Python. It will be appreciated that software modules may be callable from other modules or from themselves, and/or may be invoked in response to detected events or interrupts. Software modules configured for execution on computing devices may be provided on a computer readable medium, such as a compact disc, digital video disc, flash drive, or any other tangible medium. Such software code may be stored, partially or fully, on a memory device of the executing computing device, such as the computing system 130, for execution by the computing device. Software instructions may be embedded in firmware, such as an EPROM. It will be further appreciated that hardware modules may be comprised of connected logic units, such as gates and flip-flops, and/or may be comprised of programmable units, such as programmable gate arrays or processors. The modules described herein are preferably implemented as software modules, but may be represented in hardware or firmware. Generally, the modules described herein refer to logical modules that may be combined with other modules or divided into sub-modules despite their physical organization or storage.

[0037] In some embodiments, one or more computing systems, data stores and/or modules described herein may be implemented using one or more open source projects or other existing platforms. For example, one or more computing systems, data stores and/or modules described herein may be implemented in part by leveraging technology associated with one or more of the following: Drools, Hibernate, JBoss, Kettle, Spring Framework, NoSQL (such as the database software implemented by MongoDB) and/or DB2 database software.

[0038] FIG. 3 is an example user interface 300 that may be generated and presented to a user to indicate historical credit utilization of particular credit lines. In this example, the credit utilization tracking system 130 tracks credit usage information regarding three credit lines of a consumer. The three credit lines in this example include a Discover® account, a Gold Visa® account, and an American Express® account.

[0039] In this particular example, historical credit utilization of the consumer's three credit lines is represented monthly from Dec. 16, 2012 to May 16, 2013. A credit utilization ratio for each credit line over the time period is displayed, including monthly credit utilization of the consumer's Discover® account (305), monthly credit utilization of the consumer's Gold Visa® account (310), and monthly credit utilization of the consumer's American Express® account (315). Credit utilization ratios between each month, represented in this example as percentage values, are connected in a line graph. In other embodiments, other types of visualizations may be provided to show the user's historical credit utilization for each of one or more credit lines.

[0040] The user interface 300 may also display one or more credit utilization thresholds. In some embodiments, the user interface 300 may include a high utilization threshold and a low utilization threshold. In some embodiments, more thresholds are displayed. In this particular example, the high threshold 320 represents 75% credit utilization and the low threshold 325 represents 25% credit utilization. In some other cases, a different high threshold 320 and/or a different low threshold 325 may be used in the user interface 300.

[0041] In some cases, the credit utilization tracking system 130 automatically generates one or more credit utilization threshold based on historical credit utilization of a particular credit line of a consumer. For example, based on calculations performed by the utilization tracking module, the average credit utilization ratio of a consumer for the past 12 months may be 35%. Accordingly, the credit utilization tracking system may set a credit utilization threshold of 35% (or slightly above) for the consumer. Although the duration of 12 months is used in this example, any other duration may also be used to calculate the average credit utilization ratio of a consumer for any period of time for which credit utilization data is available.

[0042] In another example, based on calculations performed by the utilization tracking module, the consumer's 25^th percentile of credit utilization ratio for the past 3 years is 45%, and the consumer's 75^th percentile of credit utilization ratio for the past 3 years is 80%. Accordingly, the credit utilization tracking system may select 45% and 80% as the low credit utilization threshold and the high credit utilization threshold for the consumer, respectively. Although the duration of 3 years is used in this example, any other duration may also be used to calculate the average credit utilization ratio of a consumer for any period of time for which credit utilization data is available.

[0043] In some embodiments, the credit utilization tracking system 130 may automatically generates one or more credit utilization thresholds based on whether using more credit over the one or more thresholds would negatively impact the consumer's credit score. The credit utilization tracking system 130 may calculate the one or more credit utilization thresholds and how the consumer's credit score may be impacted by increased credit utilization based on statistical analysis of historical credit utilization data about a consumer, the consumer's credit lines, and other related information. In some embodiments, the credit utilization tracking system 130 may use a formula or information from a consumer's credit report to calculate the one or more credit utilization thresholds. In some embodiments, information from one or more credit bureaus is accessed in order to determine a credit utilization that causes a negative impact (or positive impact) on a consumer's credit score based on one or more credit score formulas used by the one or more credit bureaus. Thus, thresholds may be set based on information obtained from the one or more credit bureaus. In the example of FIG. 3, a high and low credit threshold are the same for each of the three credit cards, where the high utilization threshold may indicate a level at which the consumers credit score begins to be impacted.

[0044] In this particular example illustrated in FIG. 3, a flag 330 is shown for the Discover account on Mar. 16, 2013. This indicates that the credit utilization ratio on Mar. 16, 2013 has exceeded the high threshold of 75% as indicated by the high threshold 320. If a consumer clicks the flag, the interface 300 may display a note to the consumer. For example, if spending more money using the credit line would negatively impact a consumer's credit score, the note may inform the consumer that his or her credit score might be lowered, and he or she should consider using other credit lines if available.

[0045] In some cases, the interface 300 may display a note that not only informs the consumer that he or she has reached one or more credit utilization thresholds, but also suggests which other credit lines with lower credit utilization ratio might be available. For example, in the particular case shown in FIG. 3, the interface 300 may generate and display a note to the consumer indicating that credit utilization of the Discover credit line has exceeded the high threshold 320 on Mar. 16, 2013. Moreover, the interface 300 may suggest that the consumer consider using the American Express credit line because credit utilization of the American Express credit line is the lowest among the consumer's three available credit lines. In addition, for Mar. 16, 2013, the credit utilization of the American Express credit line is lower than the low credit utilization threshold. In one embodiment, the user interface may simulate in effect on the user's credit score if credit utilization increases above the high threshold. For example, user interface may indicate that if the user spends a certain amount of money on the Discover credit card and increases the credit utilization to 80%, the consumer's credit score may draw from 630 to 629. Other similar simulations of impacts to consumer credit scores based on credit utilization may also be provided. Based on the simulations, a consumer may be provided with a recommendation to move some amount of debt from one credit line to another credit line, if possible. In some embodiments, a suggestion to move a portion of available credit on a credit line to another credit line in order to improve (e.g., reduce) credit utilization of the credit line that has a high credit utilization. For example, if multiple credit lines are associated with a credit issuer, the credit issuer may allow transfer of available credit between credit lines.

[0046] FIGS. 4A and 4B illustrate example user interfaces that may be provided for display on a user device to provide information regarding credit utilization. In FIG. 4A, a mobile user interface 410 is shown. The mobile user interface 410 in this example includes a message/alert. Message/alert 415 informs a consumer that the consumer's credit utilization of Visa® card ending in 7273 for the month of November is above the 70% credit utilization threshold. The user interface 410 may be a text messaging user interface (and the alert 415 may be a text message), a standalone application, a browser, and/or any other user interface.

[0047] Depending on the embodiment, the user may have options to specify that alerts are sent when the consumer's credit utilization has exceeded one or more credit utilization thresholds. Alternatively, the consumer may wish to receive alerts only when credit utilization ratio is high enough to negatively impact credit score or the increase of credit utilization ratio is sharp enough to indicate probability of fraudulent activities.

[0048] Depending on the embodiment, the consumer may set preferences for delivery of alerts in any available manner, such as via text messages, email, telephone call and/or messages, smart phone application notifications, etc. In some embodiments, alerts may include links to further information regarding the consumer's credit utilization. For example, in embodiment of FIG. 4A, the consumer may click on the credit utilization alert link in message/alert 415 and navigate to a webpage that displays the credit utilization details, such as the total amount of credit available and the amount of credit used for the particular credit line over a period of time.

[0049] In FIG. 4B, a mobile user interface 420 is shown. In this embodiment, the user interface 425 includes a message/alert 425 sent from the credit utilization tracking system 130. The message/alert 425 lets a consumer know that the consumer's credit utilization of Visa® card ending in 7273 has increased by 30% over the last week.

[0050] Depending on the embodiment, the consumer may set a threshold for a percentage of increase in credit utilization that triggers an alarm/alert. The credit utilization tracking system 130 may, in some embodiments, automatically generate a threshold for a percentage of increase in credit utilization that triggers an alarm/alert.

[0051] In this embodiment, the user interface 420 may also include a link in the message/alert 425 that takes the consumer directly to a webpage that shows information related to the credit utilization increase, such as the total amount of credit available and the amount of credit used for the particular credit line in a short period of time.

[0052] In some cases, the link in the message/alert 425 also includes one or more recommended actions. For example, if the credit utilization tracking system 130 or the consumer detects a risk of fraudulent activities, contact information may be displayed or provided to initiate an investigation. The recommended actions may also include, for example, using another credit line to minimize any possible damaging effects to the consumer's credit score and credit history, and/or moving part of the available credit (or actual outstanding debt) from one credit line to another credit line, if possible. In one embodiment, the credit utilization system selects a best credit card for use on a particular transaction, based on current credit utilization of multiple credit cards of the consumer and with a goal of decreasing likelihood of any one credit card reaching a utilization level that would negatively impact the consumer's credit score.

[0053] FIG. 5 is an example user interface 500 that may be generated and presented to a user to customize credit utilization thresholds. In FIG. 5, the user interface 500 displays a consumer's three credit lines—a Gold Visa® credit line, a Discover® credit line, and an American Express® credit line. In this embodiment, two default credit utilization thresholds generated by the credit utilization tracking system 130 are displayed. The two default credit utilization thresholds include: (1) a default low credit utilization threshold 505, corresponding to a 30% credit utilization ratio in this example; and (2) a default high credit utilization threshold 510, corresponding to a 70% credit utilization ratio in this example. In other embodiments, different default credit utilization thresholds may be generated by the credit utilization tracking system 130.

[0054] The user interface 500 allows consumers to customize credit utilization thresholds based on their own choices. For example, consumers may use sliders provided in the user interface 500 to increase and/or decrease the high and/or low thresholds. In the example shown in FIG. 5, the Gold Visa® credit line uses default thresholds. A consumer has configured the Discover credit line to be associated with a consumer-customized low credit utilization threshold that is higher than the default 30% low credit utilization threshold, as indicated by the slider 515. The Discover® credit line is configured to be associated with a consumer-customized high credit utilization threshold that is lower than the default 70% credit utilization threshold, as indicated by the slider 520. A consumer has moved the slider 525 so that the consumer's American Express® credit line has a low credit utilization threshold that is higher than the default. The consumer has also associated the American Express® credit line with a high credit utilization threshold that is higher than the default high credit utilization threshold using the slider 530.

[0055] In some embodiments, credit utilization above the default high credit utilization threshold may impact a consumer's credit score. In some cases, the user interface 500 is also configured to allow consumers to add more thresholds with a user interface element 535. In the user interface 500, consumers may add a threshold by selecting “Yes’ next to a credit line. Depending on embodiments, an additional slider may be added to the interface 500 after a consumer indicates that he or she wishes to add more thresholds.

[0056] Although the foregoing systems and methods have been described in terms of certain embodiments, other embodiments will be apparent to those of ordinary skill in the art from the disclosure herein. Additionally, other combinations, omissions, substitutions and modifications will be apparent to the skilled artisan in view of the disclosure herein. While some embodiments of the inventions have been described, these embodiments have been presented by way of example only, and are not intended to limit the scope of the inventions. Indeed, the novel methods and systems described herein may be embodied in a variety of other forms without departing from the spirit thereof. Further, the disclosure herein of any particular feature, aspect, method, property, characteristic, quality, attribute, element, or the like in connection with an embodiment can be used in all other embodiments set forth herein.

[0057] All of the processes described herein may be embodied in, and fully automated via, software code modules executed by one or more general purpose computers or processors. The code modules may be stored in any type of computer-readable medium or other computer storage device. Some or all the methods may alternatively be embodied in specialized computer hardware. In addition, the components referred to herein may be implemented in hardware, software, firmware or a combination thereof.

[0058] Conditional language such as, among others, “can,” “could,” “might” or “may,” unless specifically stated otherwise, are otherwise understood within the context as used in general to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without user input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment.

[0059] Any process descriptions, elements or blocks in the flow diagrams described herein and/or depicted in the attached figures should be understood as potentially representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or elements in the process. Alternate implementations are included within the scope of the embodiments described herein in which elements or functions may be deleted, executed out of order from that shown, or discussed, including substantially concurrently or in reverse order, depending on the functionality involved as would be understood by those skilled in the art.