Abstract: Embodiments of the invention are directed to systems, methods and computer program products for use in streamlining customer finance and customer money management platforms and providing electronic financial management. An exemplary apparatus may be configured to provide access to a funds transfer management portal that interfaces with at least one database to access a customer's financial information for use in presenting account activity associated with at least one of the customer's accounts maintained by a financial institution. The system receives a request to view account activity in which the request specifies a format for viewing the account activity. In response to receiving the request, the system retrieves data related to one or more funds transfers associated with the at least one account and present the account activity in the requested format for viewing the account activity.

Abstract: Embodiments of the invention are directed to systems, methods and computer program products for use in streamlining customer finance and customer money management platforms and providing electronic financial management. An exemplary apparatus may be configured to provide access to a funds transfer management portal that interfaces with at least one database to access a customer's financial information for use in presenting account activity associated with at least one of the customer's accounts maintained by a financial institution. The system receives a request to view account activity in which the request specifies a format for viewing the account activity. In response to receiving the request, the system retrieves data related to one or more funds transfers associated with the at least one account and present the account activity in the requested format for viewing the account activity.

Abstract: Embodiments of the invention are directed to systems, methods and computer program products for use in streamlining customer finance and customer money management platforms and providing electronic financial management. An exemplary apparatus may be configured to provide access to a funds transfer management portal that interfaces with at least one database to access a customer's contact information and external account information for use in presenting contact and accounts associated with the customer. The system presents a consolidated view of both the customer's contacts and external account. Transfers are then processed using at least one of the contact information associated with the one or more contacts and the account information associated with the one or more external accounts.

Abstract: An intuitive and consolidated platform for managing fund transfers is disclosed. The comprehensive platform allows a customer to make fund transfers between their financial accounts, both internal and external, including domestic and international, as well as, transfers to third-party accounts (e.g., family, friends, business and the like), including accounts held domestically and internationally. The intuitive aspect of the platform provides transfer options specific to the selected transfer type and the selected transfer account.

Abstract: An intuitive layout of a user-interface, otherwise referred to as a GUI or digital form, within a platform for managing fund transfers. The invention provides for customers to select a transferor account and a transferee account and/or recipient and, in response to selection, be presented with display of transfer options that are specific to the transfer type and/or transfer accounts. Moreover, the transfer information that is displayed is positioned within the user-interface so as to provide the customer with a clear indication of what information needs to be inputted or otherwise selected to manage the transfer of funds. As such the present invention provides a consolidated and simplified approach to managing fund transfer requests; thus making it easy for customers to conduct and schedule fund transfers.

Abstract: Efficient and easy scheduling of future transfers and, specifically, recurring future transfers is provided for within a consolidated fund transfer management platform. In this regard, the platform is configured to identify transfer patterns based on a customer's historical fund transfers and the customer's current transfer request inputs, such as transferor account, transferee/transferee account, transfer amount and the like. In response to identifying the transfer pattern, the platform is configured to suggest to the customer setting-up a recurring transfer, such that future transfers indicated in the pattern will occur automatically on a recurring basis. Once the customer has selected the suggested recurring transfer option the customer is presented with applicable frequency and duration options for establishing the recurring transfer. In this regard, the platform is highly intuitive to the user, such that the user can easily configure future transfers and, specifically, future recurring transfers.

Abstract: A data structure used by an operating system to refer to a filesystem object includes information that permits the structure to be associated with filesystem objects having different filesystem implementations. The data structure is associated with a filesystem object that is linked into different directories that have different filesystem implementations. Therefore, the data structure includes respective information within it about each different link. As a result, a filesystem object, such as a directory, having one filesystem implementation may be created in or moved to another directory having a different filesystem implementation; or, a file may be linked in multiple directories having different implementations.

Abstract: System, method, and computer program product are provided for a user to send and receive P2P payments using a mobile device. Through the use of the mobile device, a user may access accounts the user has at a financial institution and direct payments to other individuals or entities using the other individuals or entities alias. Electronic document(s) may be communicated in conjunction with a payment and/or request for payment between financial institutions. For example, a sending financial institution may send a payment having a document or pointer to a document that provides an explanation of a payment or disbursement. The sender may send funds to a recipient along with a pointer or may simply send a pointer and upload a document that is stored at a location identified by the pointer. The document may be an invoice remittance, explanation of payment/reimbursement and/or explanation of benefits.

Abstract: System, method, and computer program product are provided for a user to send and receive expedited P2P payments. In some embodiments, payment instructions may be sent from one financial institution to another financial institution, and based on those instructions and a “promise to pay”, the receiving FI posts the payment to the recipient's account within a short period of time, such as within minutes. Actual settlement of the payment may occur during the next settlement cycle or at some future time or cycle as agreed. This benefits the customer because the customer has the ability to send funds to a recipient in an expedited timeframe.

Abstract: A filesystem conversion process converts a filesystem from one implementation type to another type while the filesystem remains active and fully accessible. The conversion process builds a list of directories in the filesystem that are of the old filesystem type and then converts each directory until the entire filesystem is converted. Instead of the filesystem being shutdown to perform the conversion, the conversion process may run as a background thread that does not interfere with normal filesystem operations.

Abstract: A data structure used by an operating system to refer to a filesystem object includes information that permits the structure to be associated with filesystem objects having different filesystem implementations. The data structure is associated with a filesystem object that is linked into different directories that have different filesystem implementations. Therefore, the data structure includes respective information within it about each different link. As a result, a filesystem object, such as a directory, having one filesystem implementation may be created in or moved to another directory having a different filesystem implementation; or, a file may be linked in multiple directories having different implementations.

Abstract: Embodiments of the present invention provide techniques for protecting critical sections of code being executed in a lightweight kernel environment suited for use on a compute node of a parallel computing system. These techniques avoid the overhead associated with a full kernel mode implementation of a network layer, while also allowing network interrupts to be processed without corrupting shared memory state. In one embodiment, a fast user-space function sets a flag in memory indicating that interrupts should not progress and also provides a mechanism to defer processing of the interrupt.

Abstract: Embodiments of the present invention provide techniques for protecting critical sections of code being executed in a lightweight kernel environment suited for use on a compute node of a parallel computing system. These techniques avoid the overhead associated with a full kernel mode implementation of a network layer, while also allowing network interrupts to be processed without corrupting shared memory state. In one embodiment, a system call may be used to disable interrupts upon entry to a routine configured to process an event associated with the interrupt.

Abstract: Multiple links to the same object are managed by storing the attributes of the object in only one place. Each directory which links to the object has an object attribute table; each table has a number of entries all capable of storing the attributes of the files linked to the directory. One of the entries in a directory linked to a file stores the attributes of that file, called the master entry; other entries in the same or other directories that also link to the same file have slave entries capable of storing the attributes but not storing the attributes in their respective object attribute table. The file need only address the master entry. The master entry may point to the other slave entries which may point back to the master or to other slave entries as determined by a pointer protocol. When the master entry is to be deallocated, another of the qualified slave entries receives the attribute information and the file is updated to reflect that a new master has been declared.

Abstract: Multiple links to the same object are managed by storing the attributes of the object in only one place. Each directory which links to the object has an object attribute table; each table has a number of entries all capable of storing the attributes of the files linked to the directory. One of the entries in a directory linked to a file stores the attributes of that file, called the master entry; other entries in the same or other directories that also link to the same file have slave entries capable of storing the attributes but not storing the attributes in their respective object attribute table. The file need only address the master entry. The master entry may point to the other slave entries which may point back to the master or to other slave entries as determined by a pointer protocol. When the master entry is to be deallocated, another of the qualified slave entries receives the attribute information and the file is updated to reflect that a new master has been declared.