Paypal, Inc.

Vinesh Chirakkil

Srinivasan Manoharan

Harish Nalagandla

Christopher S Purdum

Girish Sharma

Sahil Dahiya

Gurinder Grewal

Pankaj Sarin

Jun Zhu

Chun Kiat Ho

Lin Song

Yuehao Wu

Thomas Anthony Doran

Junhua Zhao

Matthew Fundus

Xiaoying Han

Premila Viswanathan

Systems and techniques that facilitate computing touchpoint journey recommendations are provided. In various embodiments, an input component can receive a computing context of a client and a computing profile of a client. In various instances, the client can be engaged in a computing touchpoint journey. In various embodiments, a prediction component can predict, via a first machine learning classifier, a negative event likely to occur on the computing touchpoint journey. In various cases, the first machine learning classifier can receive as input the computing context and the computing profile and can generate as output the predicted negative event. In various embodiments, a decision component can recommend in real-time, via a second machine learning classifier, a computing touchpoint to which to transfer the client. In various aspects, the second machine learning classifier can receive as input the computing context, the computing profile, and the predicted negative event and produce as output the recommended computing touchpoint. In various embodiments, an execution component can transfer the client to the recommended computing touchpoint. In various embodiments, a computing touchpoint journey component can record computing touchpoint journeys traversed by various clients and trains the first and second machine learning classifiers on the recorded computing touchpoint journeys.

Dynamic computing touchpoint journey recommendation platform

Methods and systems are presented for providing a container orchestration framework for facilitating development and deployment of software applications across different operating environments within an enterprise system. Upon receiving a service request for processing a set of data is received, the container orchestration framework determines one or more machines that store the set of data. Instead of processing the set of data remotely, the container orchestration framework deploys a container that encapsulates an application on the one or more machines. Each application instance running on the one or more machines are executed to process a corresponding subset of data stored on the machine locally. The container orchestration framework obtains the output data from executing the applications on each of the one or more machines, and present the output data as a response to the service request.

Container orchestration framework

Methods and systems for using machine learning to automatically determine a data loading configuration for a computer-based rule engine are presented. The computer-based rule engine is configured to use rules to evaluate incoming transaction requests. Data of various data types may be required by the rule engine when evaluating the incoming transaction requests. The data loading configuration specifies pre-loading data associated with at least a first data type and lazy-loading data associated with at least a second data type. Statistical data such as use rates and loading times associated with the various data types may be supplied to a machine learning module to determine a particular loading configuration for the various data types. The computer-based rule engine then loads data according to the data loading configuration when evaluating a subsequent transaction request.

Self learning data loading optimization for a rule engine

Methods and systems are presented for providing concurrent data retrieval and risk processing while evaluating a risk source of an online service provider. Upon receiving a request to evaluate the risk source, a risk analysis module may initiate one or more risk evaluation sub-processes to evaluate the risk source. Each risk evaluation sub-process may require different data related to the risk source to perform the evaluation. The risk analysis module may simultaneously retrieve the data related to the risk source and perform the one or more risk evaluation sub-processes such that the risk analysis module may complete a risk evaluation sub-process whenever the data required by the risk evaluation sub-process is made available.

Systems and methods for providing concurrent data loading and rules execution in risk evaluations

Methods and systems for automatically discovering data types required by a computer-based rule engine for evaluating a transaction request are presented. Multiple potential paths for evaluating the transaction request according to the rule engine are determined. An abstract syntax tree may be generated based on the rule engine to determine the multiple potential paths. Based on an initial set of data extracted from the transaction request, one or more potential paths that are determined to be irrelevant to evaluating the transaction request are identified. Types of data required to evaluate the transaction request according to the remaining potential paths are determined. Only data that corresponds to the determined types of data is retrieved to evaluate the transaction request.

Automatic discovery of data required by a rule engine

Growing community of inventors

San Jose, CA, United States of America

Vinesh Chirakkil