Cloud based master data management architecture

• US 9,584,949 B2
• Filed: 01/27/2011
• Issued: 02/28/2017
• Est. Priority Date: 01/27/2011
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Korovin, Ievgenii, Malafeev, Alexander, Kukurudza, Dennis
• Primary Examiner(s): Homayounmehr, Farid
• Assistant Examiner(s): SARKER, SANCHIT K
• Application Number:
  US13/015,462
• Publication Number:
  US 20120198036A1
• Time in Patent Office: 2,224 Days
• Field of Search: 709/223
• US Class Current: 1/1
• CPC Class Codes: H04W 4/60 Subscription-based services using application servers or record carriers, e.g. SIM application toolkits

Abstract

A cloud based service architecture is used in providing Master Data Management (MDM) services to clients. The MDM cloud based architecture comprises a client architecture and a server architecture. The client architecture includes synchronization services that are used to interact with the MDM cloud based service. The server architecture comprises a public Application Programming Interface (API) and a portal for accessing different MDM functionality. For example, a client may access the server architecture to create/modify MDM workflows that are hosted by the cloud based service. The cloud based service architecture also provides access to different MDM services including MDM workflows, validation, transformation, and storage relating to master data. The cloud based architecture may be used to publish master data and/or subscribe to master data.

Claims

1. A system for managing master data using a cloud based architecture, comprising:

at least one processor;

memory, operatively connected to the at least one processor and storing computer-executable instructions that, when executed by the at least one processor, cause the at least one processor to perform a method, the method comprising;

receiving, through an Application Programming Interface (API), a first message from a first client of the plurality of clients, wherein the first message requests a first operation to be performed, and wherein the API is usable by a plurality of clients to interact with a cloud based Master Data Management (MDM) service that is configured to manage master data including changes to the master data for the plurality of clients;

determining that the first operation is associated with a first workflow, wherein the first workflow comprises a sequence of preconfigured blocks, and wherein each of the blocks are preconfigured to receive and process information relating to the master data in a predefined schema;

executing the first operation to create a customized workflow specific to the first client, wherein the first operation comprises at least one of the following;

removing a preconfigured block from the first workflow and adding a preconfigured block into the first workflow;

receiving, through the API, a second message from a second client of the plurality of clients, wherein the second message requests a second operation to be performed to cause a change to the master data;

executing the second operation, wherein executing the second operation comprises;

accessing the master data in a first schema compliant with a first application, and

transforming an item of the master data from the first schema to a second schema, the second schema compliant with a second application; and

notifying the first client of the change to the master data; and

a conflict storage storing conflict data that relates to a conflict caused by the second operation.

2. The system of claim 1, wherein the transformed item of the master data is available for consumption by the plurality of clients as determined by a validation service that is provided by a services layer that provides the MDM services to the plurality of clients.

3. The system of claim 1, further comprising a notification component that provides notifications to the first client of the change to the master data.

4. The system of claim 1, further comprising an endpoint component that couples different types of MDM applications.

5. The system of claim 1, wherein the first workflow comprises a default set of preconfigured blocks.

6. The system of claim 1, wherein the second message is received at a synchronization service from the second client, and wherein the synchronization services notifies the first client of the change to the master data.

7. The system of claim 1, further comprising a business rule component that stores business rules for the plurality of clients.

8. A method for managing master data using a cloud based architecture, comprising:

receiving, through an Application Programming Interface (API), a first message from a first client, the API usable by a plurality of clients to interact with a cloud based Master Data Management (MDM) service, wherein the first message requests a first operation to be performed;

determining that the first operation to be performed is associated with a first workflow, wherein the first workflow comprises a sequence of preconfigured blocks, and wherein each of the blocks are preconfigured to receive and process information relating to the master data in a predefined schema;

executing the first operation to create a customized workflow specific to the first client, wherein the first operation comprises at least one of the following;

removing a preconfigured block from the first workflow and adding a preconfigured block into the first workflow;

receiving, through the API, a second message from a second client of the plurality of clients, wherein the second message requests a second operation to be performed to cause a change the master data;

executing the second operation, wherein executing the second operation comprises;

accessing the master data in a first schema compliant with a first application, and

transforming an item of the master data from the first schema to a second schema, the second schema compliant with a second application;

notifying the first client of the change to the master data; and

storing conflict data within a conflict storage when a conflict is determined as a result of the requested second operation.

9. The method of claim 8, further comprising storing the master data that is available for consumption by the plurality of clients within the second data storage accessible to the plurality of clients.

10. The method of claim 8, further comprising accessing an endpoint component to determine a type of an MDM application that is associated with the first client.

11. The method of claim 8, wherein notifying the first client of the change comprises notifying by a synchronization service the first client of the change to the master data.

12. A computer storage device storing computer-executable instructions that, when executed by at least one processor, cause the at least one processor to perform a method for managing master data using a cloud based architecture, the method comprising:

receiving, through an Application Programming Interface (API), a first message from a first client, the API usable by a plurality of clients to interact with a cloud based Master Data Management (MDM) service, wherein the first message requests a first operation to be performed;

determining that the first operation is associated with a first workflow, wherein the first workflow comprises a sequence of preconfigured blocks and wherein each of the blocks are preconfigured to receive and process information relating to the master data in a predefined schema;

executing the first operation to create a customized workflow specific to the first client, wherein the first operation comprises at least one of the following;

removing a preconfigured block from the first workflow and adding a preconfigured block into the first workflow;

receiving, through the API, a second message from a second client of the plurality of clients, wherein the second message requests a second operation to be performed to cause a change the master data;

executing the second operation, wherein executing the second operation comprises;

accessing the master data in a first schema compliant with a first application, and

transforming an item of the master data from the first schema to a second schema, the second schema compliant with a second application;

notifying the first client of the change to the master data; and

storing conflict data within a conflict storage when a conflict is determined as a result of the requested second operation.

13. The computer storage device of claim 12, the method further comprising storing the master data that is available for consumption by the first client within a data storage.

14. The computer storage device of claim 12, the method further comprising accessing a transform service that transforms the master data processed by the first workflow from a first format to at least one other format and accessing an endpoint component to determine a type of an MDM application that is associated with the first client.