Abstract: A legacy resource is virtualized as a virtualized resource defined by features and capabilities set by an individual through a front-end user interface. Access rules are set on the virtualized resource based on the features and capabilities. When an access is requested to the virtualized resource, the corresponding access rules are enforced. Assuming there is no violation in the access rules, virtualized legacy resource services are overlaid on legacy resource services to cause the legacy resource services to perform any needed access operations on the corresponding legacy resource associated with the virtualized resource without changing any workflows processed by the legacy resource services.

Abstract: During startup or boot of a device, software or firmware associated with a processor and/or microcontroller of the device slow walks the handover of control to critical initialization or steady-state functions to account for any instability due to an electrical transient that may cause the processor and/or microcontroller to perform erratically or non-deterministically during startup or boot. The wait time associated with the slow-walk handover of control is optimized to ensure that no instability due to transients is present when the wait time expires. In an embodiment, after the wait time expires, firmware/software associated with the bootloader and/or Basic Input/Output System (BIOS) may further continuously calculate a checksum value for the corresponding target software/firmware and compare the calculated value against an expected checksum value. When the calculated checksum matches the expected checksum, remaining portions of the firmware/software for the bootloader and/or BIOS are given control.

Abstract: An invoice-centric, payee-centric, and/or payer-payee neutral transaction service is provided. Subsets of the transaction data for the transaction can be received separately from the parties to the transaction. The subsets of transaction data are linked to the transaction and containerized within a hierarchy. Each container within the hierarchy can include its own separate and independent encryption, encoding, and/or access rights. An invoice associated with the transaction is presented to a payer for approval before the transaction is processed, and upon payer approval, the transaction is processed on behalf of the parties using one or more selected containers from the hierarchy. Both the payee and payer may be notified when the transaction is completed.

Abstract: A transaction is initiated between a first party and a second party. Transaction data for the transaction is obtained and segmented into a subset provided by the first party and a subset provided by the second party. Each subset is further segmented into portions. Each portion is assigned for transmission to a particular one of the parties. A determination is made as to whether each portion is to be encoded in a data structure, a sequence of data structures, or not encoded at all and an optimal channel of communication or multiple channels of communication are selected for transmitting the corresponding portion directly to the corresponding party. At least a portion of the transaction data is provided to a cloud-based transaction service that completes the transaction on behalf of the parties.

Abstract: Account-based resource management is provided. A resource is modeled within a resource data model. Attributes on fields of the data model are custom set by an owner who controls the resource. Access rules are assigned based on the attributes set on the fields. The corresponding rules associated with a given access request on the resource are enforced to ensure proper security during the access request. In an embodiment, a service is provided that performs a workflow for a given type of access request on behalf of the owner and at least one other party that is requesting access to the resource.