Microsoft Technology Licensing, LLC

Mehmet Kadri Umay

Imran Siddique

Nayana Singh Patel

Jyothsna Devi Bijjam

Anirudh Badam

Philipp Andre Witte

Daniel Keith Scholl

Shikha Garg

A computing system that includes one or more server computing devices including one or more processors configured to execute instructions for a domain extensibility module that provides software development tools for building domain extensions for a database platform, and a data ingestion module that provides software development tools for defining a metadata schema for extracting metadata from data files. The one or more processors are configured to receive a set of data from a user computing device, define a target metadata schema that includes one or more metadata fields that will be populated during a data ingestion process, define a target domain extension that defines one or more data types for storing the received set of data after performing the data ingestion process, and ingest the received set of data using a metadata extraction pipeline to generate metadata files based on the target metadata schema.

Extensible data platform with database domain extensions

Data from data sources may be processed at an edge device. The edge device may generate a local processing result, filter the data, and/or prioritize the data. Accordingly, data is transmitted from the edge device to the data platform, where it may be processed further. For example, a local processing result may be processed at the data platform, such that processing is performed without all of the data source data. In examples, at least a part of such data may remain at an edge device. The edge device may maintain a manifest of data stored by the edge device. The data platform may generate an aggregated manifest using manifests from associated edge devices, such that it may be determined where data is stored. As a result, the data platform may redirect requests to an associated edge device when it is determined that requested data is remote from the data platform.

Decentralized data platform

In examples, streaming data is received from a data source (e.g., by an edge device associated with a data platform) and is queued and aggregated. Batch data may similarly be received from a data source. The batch data and the aggregated streaming data may be processed to generate metadata accordingly. The data and metadata may be provided to the data platform, where the metadata may be used to update an index and the data may be stored in association with the index. In some instances, the data may be stored in chunks to facilitate subsequent retrieval of the data. In response to a request for the data, the index may be used to identify relevant data, which may include data associated with batch and/or streaming data formats, thereby enabling the client device to access data having any of a variety of formats from the data platform.

Heterogeneous data platform

A remote server computing system is configured to deploy a cloud-service-managed control plane and a cloud service data plane spanning the remote server computing system, a local edge computing device, and a local on-premises computing device connected in a hybrid cloud environment. Energy-related training data is received including a plurality of energy-related training data pairs. A machine learning function is trained using the plurality of training data pairs to predict a classified label for restricted energy-related data that is not accessible to the remote server computing system. The trained machine learning function is deployed to the one or more of the local edge computing device and the local on-premises computing device via the cloud service data plane. The remote server computing system is further configured to receive, via the cloud service data plane, classified output of the trained machine learning function.

Growing community of inventors

Redmond, WA, United States of America

Mehmet Kadri Umay