G06F9/541

Quasi-volatile system-level memory

A high-capacity system memory may be built from both quasi-volatile (QV) memory circuits, logic circuits, and static random-access memory (SRAM) circuits. Using the SRAM circuits as buffers or cache for the QV memory circuits, the system memory may achieve access latency performance of the SRAM circuits and may be used as code memory. The system memory is also capable of direct memory access (DMA) operations and includes an arithmetic logic unit for performing computational memory tasks. The system memory may include one or more embedded processor. In addition, the system memory may be configured for multi-channel memory accesses by multiple host processors over multiple host ports. The system memory may be provided in the dual-in-line memory module (DIMM) format.

Methods and apparatuses for generating redo records for cloud-based database

Methods and apparatuses in a cloud-based database management system are described. Data in a database are stored in a plurality of pages in a page store of the database. A plurality of redo log records are received to be applied to the database. The redo log records within a predefined boundary are parsed to determine, for each given redo log record, a corresponding page to which the given log record is to be applied. The redo log records are reordered by corresponding page. The reordered redo log records are stored to be applied to the page store of the database.

Automated honeypot creation within a network

Systems and methods for managing Application Programming Interfaces (APIs) are disclosed. Systems may involve automatically generating a honeypot. For example, the system may include one or more memory units storing instructions and one or more processors configured to execute the instructions to perform operations. The operations may include receiving, from a client device, a call to an API node and classifying the call as unauthorized. The operation may include sending the call to a node-imitating model associated with the API node and receiving, from the node-imitating model, synthetic node output data. The operations may include sending a notification based on the synthetic node output data to the client device.

Activity detection in web applications
11582318 · 2023-02-14 · ·

An analytics server receives from client computing devices end-user events. Each client computing device is operated by an end-user to access an application at a web server based on the end-user events resulting in calls being passed through a proxy to the web server. The analytics server receives from the proxy the calls being made to the web server, and receives return responses from the web server being passed through the proxy. The return responses correspond to activities being performed within the application. The end-user events are correlated with the corresponding calls and return responses from the proxy. Respective correlated end-user events, calls and return responses are translated into respective event vectors. The respective event vectors are processed to determine similarities among the client computing devices. The similar activities are associated with a quality indicator to identify anomalies within the application for corrective action to be taken.

Processing rest API requests based on resource usage satisfying predetermined limits

A request manager analyzes API calls from a client to a host application for state and performance information. If current utilization of host application processing or memory footprint resources exceed predetermined levels, then the incoming API call is not forwarded to the application. If current utilization of the host application processing and memory resources do not exceed the predetermined levels, then the request manager quantifies the processing or memory resources required to report the requested information and determines whether projected utilization of the host application processing or memory resources inclusive of the resources required to report the requested information exceed predetermined levels. If the predetermined levels are not exceeded, then the request manager forwards the API call to the application for processing.

Dynamic service mesh

One example method includes receiving, from a microservice, a service request that identifies a service needed by the microservice, and an API of an endpoint that provides the service, evaluating the service request to determine whether the service request conforms to a policy, when the service request has been determined to conform with the policy, evaluating the endpoint to determine if endpoint performance meets established guidelines, and when it is determined that the endpoint performance does not meet the established guidelines, identifying an alternative endpoint that meets the established guidelines and that provides the requested service. Next, the method includes transforming the API of the service identified in the service request to an alternative API of the service provided by the alternative endpoint, and sending the service request and the alternative API to the alternative endpoint.

Transaction-enabled systems and methods for royalty apportionment and stacking

Transaction-enabled systems and methods for royalty apportionment and stacking are disclosed. An example system may include a plurality of royalty generating elements (a royalty stack) each related to a corresponding one or more of a plurality of intellectual property (IP) assets (an aggregate stack of IP). The system may further include a royalty apportionment wrapper to interpret IP licensing terms and apportion royalties to a plurality of owning entities corresponding to the aggregate stack of IP in response to the IP licensing terms and a smart contract wrapper. The smart contract wrapper is configured to access a distributed ledger, interpret an IP description value and IP addition request, to add an IP asset to the aggregate stack of IP, and to adjust the royalty stack.

Unified host-based data migration
11556265 · 2023-01-17 · ·

Methods, apparatus, and processor-readable storage media for unified host-based data migration are provided herein. An example computer-implemented method includes identifying a first storage array and a second storage array associated with a host device; determining a set of characteristics related to the host device for migrating data from the first storage array to the second storage array; and migrating the data based at least in part on the set of characteristics, wherein the migrating comprises: creating a set of target devices on the second storage array and provisioning the set of target devices to the host device; and moving the data from a set of source devices on the first storage array to the target devices on the second storage array.

Method and apparatus for real-time personalization

A computer-implemented, network-connected content recommender generating content recommendations for a plurality of content servers hosted by one or more customers, the content recommender comprising: one or more processors; a memory storing instruction that, when executed by the one or more processors, cause the recommender to perform operations comprising: receiving a plurality of content recommendation requests from a querying one of said customer content servers via a plurality of input streams, each input stream including a data repository; outputting data, from the memory, associated with the content recommendation requests; receiving some or all of the data associated with said content recommendation requests; generating a first model-specific recommendation result from a first set of the plurality of received data; generating a second model-specific recommendation result from a second set of the plurality of received data; combining the first model-specific recommendation results with the second model-specific results to generate an ensemble recommendation result; and transmitting the ensemble result from the content recommender to said querying customer content server.

Dynamic personalized API assembly

Methods, computer readable media, and devices for dynamic personalized API assembly are provided. One method may include receiving a data query from a client by a CDN, parsing the data query to generate a modified data query, transmitting the modified data query to an origin server, receiving a query response from the origin server, generating a modified query response based on the query response, and sending the modified query response to the client. Another method may include receiving an API call by an origin server, generating an API response by creating a payload file and adding markup directives indicating whether content is cacheable, and transmitting the API response.